# Cubox M not responding **URL:** \ **Category:** NXP i.MX8M Plus\ **Created:** [March 3, 2022, 10:35pm UTC](https://community.solid-run.com/t/cubox-m-not-responding/253 "2022-03-03T22:35:32Z")\ **Posts on this page:** 4\ **Page:** 2
**Author:** ![dekeoboe](https://avatars.discourse-cdn.com/v4/letter/d/bbce88/32.png) [@dekeoboe](https://community.solid-run.com/u/dekeoboe)\ **Post date:** [April 11, 2022, 10:34am UTC](https://community.solid-run.com/t/cubox-m-not-responding/253/21 "2022-04-11T10:34:39Z")
[2.291457] hub 3-0:1.0: USB hub found [2.295262] hub 3-0:1.0: 1 port detected [2.299464] usb usb4: We don’t know the algorithms for LPM for this host, disabling LPM. [2.308323] hub 4-0:1.0: USB hub found [2.312135] hub 4-0:1.0: 1 port detected [2.318443] sdhci-esdhc-imx 30b50000.mmc: Got CD GPIO [2.319518] sdhci-esdhc-imx 30b40000.mmc: voltage-ranges unspecified [2.319896] remoteproc remoteproc0: imx-dsp-rproc is available [2.321988] imx-drm display-subsystem: bound imx-lcdifv3-crtc.0 (ops lcdifv3\_crtc\_ops) [2.322243] dwhdmi-imx 32fd8000.hdmi: Detected HDMI TX controller v2.13a with HDCP (samsung\_dw\_hdmi\_phy2) [2.323264] dwhdmi-imx 32fd8000.hdmi: registered DesignWare HDMI I2C bus driver [2.324819] imx-drm display-subsystem: bound 32fd8000.hdmi (ops dw\_hdmi\_imx\_ops) [2.329985] sdhci-esdhc-imx 30b40000.mmc: allocated mmc-pwrseq [2.336145] [drm] Initialized imx-drm 1.0.0 20120507 for display-subsystem on minor 1 [2.365466] mmc2: SDHCI controller on 30b60000.mmc [30b60000.mmc] using ADMA [2.368694] mmc1: SDHCI controller on 30b50000.mmc [30b50000.mmc] using ADMA [2.374193] mmc0: SDHCI controller on 30b40000.mmc [30b40000.mmc] using ADMA [2.425358] random: fast init done [2.438111] mmc1: host does not support reading read-only switch, assuming write-enable [2.439458] mmc0: queuing unknown CIS tuple 0x80 (2 bytes) [2.453237] mmc0: queuing unknown CIS tuple 0x80 (3 bytes) [2.459351] mmc2: new HS400 Enhanced strobe MMC card at address 0001 [2.462006] mmc0: queuing unknown CIS tuple 0x80 (3 bytes) [2.466277] mmcblk2: mmc2:0001 8GTF4R 7.28 GiB [2.475849] mmcblk2boot0: mmc2:0001 8GTF4R partition 1 4.00 MiB [2.476577] mmc0: queuing unknown CIS tuple 0x80 (7 bytes) [2.481792] usb 1-1: new low-speed USB device number 2 using xhci-hcd [2.490520] mmc0: queuing unknown CIS tuple 0x80 (6 bytes) [2.493842] mmcblk2boot1: mmc2:0001 8GTF4R partition 2 4.00 MiB [2.505241] mmcblk2rpmb: mmc2:0001 8GTF4R partition 3 512 KiB, chardev (511:0) [2.561481] usb 3-1: new low-speed USB device number 2 using xhci-hcd [2.573559] mmc1: new ultra high speed SDR104 SDXC card at address aaaa [2.581803] mmcblk1: mmc1:aaaa SD128 119 GiB [2.591092] mmcblk1: p1 [2.630961] mmc0: new ultra high speed SDR104 SDIO card at address 0001 [2.674536] Console: switching to colour frame buffer device 240x67 [2.683341] input: PixArt USB Optical Mouse as /devices/platform/soc@0/32f10100.usb/38100000.dwc3/xhci-hcd.1.auto/usb1/1-1/1-1:1.0/0003:090 [2.683489] hid-generic 0003:093A:2510.0001: input: USB HID v1.11 Mouse [PixArt USB Optical Mouse] on usb-xhci-hcd.1.auto-1/input0 [2.748299] imx-drm display-subsystem: [drm] fb0: imx-drmdrmfb frame buffer device [2.758475] cfg80211: Loading compiled-in X.509 certificates for regulatory database [2.774480] input: Microsoft Microsoft�® Digital Media Pro Keyboard as /devices/platform/soc@0/32f10108.usb/38200000.dwc3/xhci-hcd.2.auto/1 [2.780591] cfg80211: Loaded X.509 cert ‘benh@debian.org: 577e021cb980e0e820821ba7b54b4961b8b4fadf’ [2.801043] cfg80211: Loaded X.509 cert ‘romain.perier@gmail.com: 3abbc6ec146e09d1b6016ab9d6cf71dd233f0328’ [2.811287] cfg80211: Loaded X.509 cert ‘sforshee: 00b28ddf47aef9cea7’ [2.817903] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [2.826527] platform regulatory.0: Falling back to sysfs fallback for: regulatory.db [2.841076] Freeing unused kernel memory: 2496K [2.850107] hid-generic 0003:045E:00B0.0002: input: USB HID v1.11 Keyboard [Microsoft Microsoft�® Digital Media Pro Keyboard] on usb-xhci-0 [2.853515] Run /init as init process [2.881422] input: Microsoft Microsoft�® Digital Media Pro Keyboard Consumer Control as /devices/platform/soc@0/32f10108.usb/38200000.dwc32 Loading, please wait… Starting version 247.3-7 [2.958085] input: Microsoft Microsoft�® Digital Media Pro Keyboard System Control as /devices/platform/soc@0/32f10108.usb/38200000.dwc3/x3 [2.976282] hid-generic 0003:045E:00B0.0003: input: USB HID v1.11 Device [Microsoft Microsoft�® Digital Media Pro Keyboard] on usb-xhci-hc1 [3.150317] cfg80211: failed to load regulatory.db [3.181350] imx-dwmac 30bf0000.ethernet: IRQ eth\_lpi not found [3.185869] rtc-ds1307 2-0032: registered as rtc0 [3.188811] imx-dwmac 30bf0000.ethernet: no reset control found [3.204000] imx-dwmac 30bf0000.ethernet: User ID: 0x10, Synopsys ID: 0x51 [3.206976] imx-sdma 30bd0000.dma-controller: firmware found. [3.212199] imx-dwmac 30bf0000.ethernet: DWMAC4/5 [3.218750] imx-sdma 30bd0000.dma-controller: loaded firmware 4.5 [3.221737] imx-dwmac 30bf0000.ethernet: DMA HW capability register supported [3.235203] imx-dwmac 30bf0000.ethernet: RX Checksum Offload Engine supported [3.243086] rtc-ds1307 2-0032: setting system clock to 2022-04-11T10:38:16 UTC (1649673496) [3.243555] imx-dwmac 30bf0000.ethernet: TX Checksum insertion supported [3.260858] imx-dwmac 30bf0000.ethernet: Wake-Up On Lan supported [3.262577] imx-sdma 30e10000.dma-controller: firmware found. [3.267093] imx-dwmac 30bf0000.ethernet: Enable RX Mitigation via HW Watchdog Timer [3.280507] imx-dwmac 30bf0000.ethernet: device MAC address d6:3d:d3:fd:22:6c [3.287710] imx-dwmac 30bf0000.ethernet: Enabled Flow TC (entries=8) [3.294146] imx-dwmac 30bf0000.ethernet: Enabling HW TC (entries=256, max\_off=256) [3.301742] imx-dwmac 30bf0000.ethernet: Using 34 bits DMA width [3.308196] libphy: stmmac: probed Begin: Loading essential drivers … done. Begin: Running /scripts/init-premount … done. Begin: Mounting root file system … Begin: Running /scripts/local-top … done. Begin: Running /scripts/local-premount … done. Begin: Waiting for root file system … Begin: Running /scripts/local-block … done. Begin: Running /scripts/local-block … done. Begin: Running /scripts/local-block … done. Begin: Running /scripts/local-block … done. Begin: Running /scripts/local-block … done. Begin: Running /scripts/local-block … done. Begin: Running /scripts/local-block … done. Begin: Running /scripts/local-block … done. Begin: Running /scripts/local-block … done. Begin: Running /scripts/local-block … done. Begin: Running /scripts/local-block … done. Begin: Running /scripts/local-block … done. Begin: Running /scripts/local-block … done. Begin: Running /scripts/local-block … done. Begin: Running /scripts/local-block … done. Begin: Running /scripts/local-block … done. Begin: Running /scripts/local-block … done. Begin: Running /scripts/local-block … done. Begin: Running /scripts/local-block … done. Begin: Running /scripts/local-block … done. Begin: Running /scripts/local-block … done. Begin: Running /scripts/local-block … done. Begin: Running /scripts/local-block … done. Begin: Running /scripts/local-block … done. [28.438475] random: crng init done Begin: Running /scripts/local-block … done. Begin: Running /scripts/local-block … done. Begin: Running /scripts/local-block … done. Begin: Running /scripts/local-block … done. Begin: Running /scripts/local-block … done. Begin: Running /scripts/local-block … done. done. Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Missing modules (cat /proc/modules; ls /dev) ALERT! PARTUUID=97ec091b-01 does not exist. Dropping to a shell! BusyBox v1.30.1 (Debian 1:1.30.1-6+b3) built-in shell (ash) Enter ‘help’ for a list of built-in commands. (initramfs) ---
**Author:** ![Josua](https://avatars.discourse-cdn.com/v4/letter/j/e47774/32.png) [@Josua](https://community.solid-run.com/u/Josua)\ **Post date:** [May 1, 2022, 8:22am UTC](https://community.solid-run.com/t/cubox-m-not-responding/253/22 "2022-05-01T08:22:44Z")
Thank you for the full log. There were a few parts I was looking out for: ```auto Scanning mmc 1:1… Found U-Boot script /boot/boot.scr 2544 bytes read in 17 ms (145.5 KiB/s) Executing script at 40480000 26333696 bytes read in 1108 ms (22.7 MiB/s) 56236 bytes read in 33 ms (1.6 MiB/s) 7607178 bytes read in 332 ms (21.9 MiB/s) Booting Debian 5.10.72-imx8-sr from mmc 1:1… ... [2.573559] mmc1: new ultra high speed SDR104 SDXC card at address aaaa [2.581803] mmcblk1: mmc1:aaaa SD128 119 GiB [2.591092] mmcblk1: p1 ... ALERT! PARTUUID=97ec091b-01 does not exist. Dropping to a shell! ``` So that indicates - the system is booting from microsd - u-boot can read kernel and initramfs from rootfs - linux finds the microSD card and a partition on it - the uuid is not found, which is very weird indeed … Almost as if the partition table has been changed! Has it? Did you encounter a situation where a partition was mounted during writing the image to sdcard, or strange error messages? One thing you can do while you are inside this initramfs shell is inspect the folder `/dev/disk/by-uuid/` to see what exists. E.g.: `ls -lh /dev/disk/by-uuid/` As a workaround I think you can overwrite by what name the rootfs is searched for, simply adding `root=/dev/mmcblk1p1` to the bootargs variable similar to `verbose` and `log_level` - should let you further, though I am not quite sure by how much exactly. We have been trying to reproduce your situation, but we can’t reproduce this behaviour … ---
**Author:** ![dekeoboe](https://avatars.discourse-cdn.com/v4/letter/d/bbce88/32.png) [@dekeoboe](https://community.solid-run.com/u/dekeoboe)\ **Post date:** [May 1, 2022, 10:43am UTC](https://community.solid-run.com/t/cubox-m-not-responding/253/23 "2022-05-01T10:43:52Z")
Thanks Josua, Nothing indicated that the partition was changed during writing the image - the micro sd was not mounted that I can tell. The writing process went as normal. I’ll write a new SD card to see if I see anything out of the ordinary. I’ll also modify the bootargs as you suggested to see how far that gets. When I tried to modify the UUID in bootargs it reverted to the UUID that was not found sometime during boot. John ---
**Author:** ![dekeoboe](https://avatars.discourse-cdn.com/v4/letter/d/bbce88/32.png) [@dekeoboe](https://community.solid-run.com/u/dekeoboe)\ **Post date:** [May 1, 2022, 2:35pm UTC](https://community.solid-run.com/t/cubox-m-not-responding/253/24 "2022-05-01T14:35:06Z")
Here is the result of ls -lh above; (initramfs) ls -lh /dev/disk/by-uuid total 0 lrwxrwxrwx 1 0 0 15 May 1 13:54 7854af42-f5ac-4939-ae07-e5f3f334dea7 → …/…/mmcblk1p1 (initramfs) I then changed the bootargs as suggested and got all the way through to login. I log in and there is a statement “there are run-once jobs scheduled. it is advised to reboot as soon as possible to let these jobs complete!” Every time I reboot the system returns to the previous issue of UUID not found, dropping to shell. Of note, I can log in either via the terminal app or through the keyboard/display attached to the CuBox M after modifying the bootargs and booting the system using a power cycle. FYI I’m using the Ubuntu disk manager to write the files to the microSD - it shows that the card is not mounted when I write the image to it so that doesn’t appear to the source of the problem. I will experiment more when I have a moment. Thank you again for looking at this. It’s perplexing that you cannot duplicate the issue - so it could be there is something amiss in my setup. Cheers! John [Previous page](https://community.solid-run.com/t/cubox-m-not-responding/253.md?page=1)