# NVMe CLI issues on opensuse15.5/15.4 **URL:** \ **Category:** General\ **Created:** [September 4, 2023, 11:06am UTC](https://forums.suse.com/t/nvme-cli-issues-on-opensuse15-5-15-4/41428 "2023-09-04T11:06:01Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![khokha](https://avatars.discourse-cdn.com/v4/letter/k/8491ac/32.png) [@khokha](https://forums.suse.com/u/khokha)\ **Post date:** [September 4, 2023, 11:06am UTC](https://forums.suse.com/t/nvme-cli-issues-on-opensuse15-5-15-4/41428/1 "2023-09-04T11:06:01Z")
Hi, I use nvme cli for testing of NVMe drives and some of my testing requires the use of nvme cli to send commands to the drives. I have made sure that I am using the latest revision of nvme cli (2.4) so my issue is not related to that. ![image](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/2/247a60f63abe81b7c091614b2a93877b05ac798a.png) when I run the command “nvme show-regs /dev/nvme0n1” I get an invalid argument error but if I run the same command in our older centos systems it returns the correct/expected output. The older centOS system is running an older rev of nvme cli also. Is this a known bug? What would anyone advise here? Happy to provide more info if needed. Thanks, Ankush ---
**Author:** ![malcolmlewis1](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis1/32/10022_2.png) [@malcolmlewis1](https://forums.suse.com/u/malcolmlewis1)\ **Post date:** [September 4, 2023, 1:26pm UTC](https://forums.suse.com/t/nvme-cli-issues-on-opensuse15-5-15-4/41428/2 "2023-09-04T13:26:33Z")
@khokha Hi what does the following show on a system that works `zcat /proc/config.gz | grep CONFIG_IO_STRICT_DEVMEM` I suspect that it’s the older kernel and changes (more lockdown, secure boot etc) with newer ones… On openSUSE it’s `CONFIG_IO_STRICT_DEVMEM=y` ---
**Author:** ![khokha](https://avatars.discourse-cdn.com/v4/letter/k/8491ac/32.png) [@khokha](https://forums.suse.com/u/khokha)\ **Post date:** [September 4, 2023, 1:38pm UTC](https://forums.suse.com/t/nvme-cli-issues-on-opensuse15-5-15-4/41428/3 "2023-09-04T13:38:47Z")
> [@malcolmlewis1](#): > > zcat /proc/config.gz | grep CONFIG\_IO\_STRICT\_DEVMEM ![image](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/6/60eef6520ac4ade2bae740b717dd5aa0a83d6430.png) @malcolmlewis1 no such file exists on a working centos system ---
**Author:** ![khokha](https://avatars.discourse-cdn.com/v4/letter/k/8491ac/32.png) [@khokha](https://forums.suse.com/u/khokha)\ **Post date:** [September 4, 2023, 1:41pm UTC](https://forums.suse.com/t/nvme-cli-issues-on-opensuse15-5-15-4/41428/4 "2023-09-04T13:41:16Z")
Hi @malcolmlewis1 should CONFIG\_IO\_STRICT\_DEVMEM be disabled? ---
**Author:** ![malcolmlewis1](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis1/32/10022_2.png) [@malcolmlewis1](https://forums.suse.com/u/malcolmlewis1)\ **Post date:** [September 4, 2023, 1:54pm UTC](https://forums.suse.com/t/nvme-cli-issues-on-opensuse15-5-15-4/41428/5 "2023-09-04T13:54:18Z")
@khokha No… you need to find out where a Centos kernel config is stored and check. But I suspect the issue is later kernel changes from a security perspective. What is your end game with this nvme command, as in what details of the device do you require? ---
**Author:** ![khokha](https://avatars.discourse-cdn.com/v4/letter/k/8491ac/32.png) [@khokha](https://forums.suse.com/u/khokha)\ **Post date:** [September 4, 2023, 1:59pm UTC](https://forums.suse.com/t/nvme-cli-issues-on-opensuse15-5-15-4/41428/6 "2023-09-04T13:59:36Z")
the command is part of a larger test script, I am checking to see what controller registers are supported by the drive. ![image](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/8/85ec176428c299510a89ab12a77ca29a19be3bad.png) found the config kernel on the centos ---
**Author:** ![malcolmlewis1](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/malcolmlewis1/32/10022_2.png) [@malcolmlewis1](https://forums.suse.com/u/malcolmlewis1)\ **Post date:** [September 4, 2023, 2:18pm UTC](https://forums.suse.com/t/nvme-cli-issues-on-opensuse15-5-15-4/41428/7 "2023-09-04T14:18:25Z")
@khokha So I suspect that is why it works… But you may wish to create a bug report to confirm, or look for alternatives. Times are changing, secure boot, more kernel lock down features enabled etc… [https://en.opensuse.org/openSUSE:Submitting\_bug\_reports](https://en.opensuse.org/openSUSE:Submitting_bug_reports) ---
**Author:** ![khokha](https://avatars.discourse-cdn.com/v4/letter/k/8491ac/32.png) [@khokha](https://forums.suse.com/u/khokha)\ **Post date:** [September 4, 2023, 2:46pm UTC](https://forums.suse.com/t/nvme-cli-issues-on-opensuse15-5-15-4/41428/8 "2023-09-04T14:46:53Z")
Thanks for your help and input!