# Linux hangs on NVMe detection **URL:** \ **Category:** NXP LX2160\ **Created:** [August 16, 2022, 11:07am UTC](https://community.solid-run.com/t/linux-hangs-on-nvme-detection/427 "2022-08-16T11:07:36Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![elahav](https://avatars.discourse-cdn.com/v4/letter/e/ecc23a/32.png) [@elahav](https://community.solid-run.com/u/elahav)\ **Post date:** [August 16, 2022, 11:07am UTC](https://community.solid-run.com/t/linux-hangs-on-nvme-detection/427/1 "2022-08-16T11:07:36Z")
Trying to switch back to Linux for a quick test, the board doesn’t complete the kernel boot sequence: ```auto [4.842384] No soundcards found. [4.849762] hub 3-1.3:1.0: 4 ports detected [64.742150] nvme nvme0: I/O 0 QID 0 timeout, completion polled [126.182157] nvme nvme0: I/O 24 QID 0 timeout, completion polled [166.358143] random: crng init done [187.622136] nvme nvme0: I/O 25 QID 0 timeout, completion polled [249.062142] nvme nvme0: I/O 1 QID 0 timeout, completion polled ``` The drive is formatted for QNX, not Linux, but that shouldn’t matter as I don’t believe it is trying to mount anything at this point. The Debian system should be on the eMMC, per the instructions in the Getting Started guide for the Honeycomb. Is there an option to suppress NVMe detection that can be added to the u-boot command? –Elad ---
**Author:** ![jnettlet](https://dub1.discourse-cdn.com/flex005/user_avatar/community.solid-run.com/jnettlet/32/62_2.png) [@jnettlet](https://community.solid-run.com/u/jnettlet)\ **Post date:** [August 16, 2022, 11:23am UTC](https://community.solid-run.com/t/linux-hangs-on-nvme-detection/427/2 "2022-08-16T11:23:24Z")
you can add something like `initcall_blacklist=nvme_init` to your kernel command-line args ---
**Author:** ![elahav](https://avatars.discourse-cdn.com/v4/letter/e/ecc23a/32.png) [@elahav](https://community.solid-run.com/u/elahav)\ **Post date:** [August 16, 2022, 12:11pm UTC](https://community.solid-run.com/t/linux-hangs-on-nvme-detection/427/3 "2022-08-16T12:11:02Z")
I tried adding that to the `bootargs` u-boot environment variable, but I think it gets ignored. ```auto Scanning mmc 1:1... Found /extlinux/extlinux.conf Retrieving file: /extlinux/extlinux.conf 331 bytes read in 9 ms (35.2 KiB/s) 1: primary kernel Retrieving file: /boot/Image 42017280 bytes read in 1974 ms (20.3 MiB/s) append: console=ttyAMA0,115200 earlycon=pl011,mmio32,0x21c0000 default_hugepagesz=1024m hugepagesz=1024m hugepages=2 pci=pcie_bus_perf root=PARTUUID=3 0303030-01 rw rootwait ``` I assume that command line comes from somewhere else. –Elad ---
**Author:** ![jnettlet](https://dub1.discourse-cdn.com/flex005/user_avatar/community.solid-run.com/jnettlet/32/62_2.png) [@jnettlet](https://community.solid-run.com/u/jnettlet)\ **Post date:** [August 16, 2022, 12:16pm UTC](https://community.solid-run.com/t/linux-hangs-on-nvme-detection/427/4 "2022-08-16T12:16:09Z")
it may be hard-coded in your extlinux.conf I am not sure what Debian does for this. ---
**Author:** ![elahav](https://avatars.discourse-cdn.com/v4/letter/e/ecc23a/32.png) [@elahav](https://community.solid-run.com/u/elahav)\ **Post date:** [August 16, 2022, 12:20pm UTC](https://community.solid-run.com/t/linux-hangs-on-nvme-detection/427/5 "2022-08-16T12:20:51Z")
Yes, there doesn’t seem to be a way to update that file without booting the system, which is a bit unfortunate. Anyway, after a few attempts it finally booted. Not sure what changed, but it’s good enough for me. Thanks for the help. –Elad ---
**Author:** ![elahav](https://avatars.discourse-cdn.com/v4/letter/e/ecc23a/32.png) [@elahav](https://community.solid-run.com/u/elahav)\ **Post date:** [August 16, 2022, 12:40pm UTC](https://community.solid-run.com/t/linux-hangs-on-nvme-detection/427/6 "2022-08-16T12:40:16Z")
For the record, though, once it booted I modified `/extlinux/extlinux.conf` to update the command line per your suggestion. It then took effect on the next boot. –Elad