# 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:** 20\ **Page:** 1
**Author:** ![dekeoboe](https://avatars.discourse-cdn.com/v4/letter/d/bbce88/32.png) [@dekeoboe](https://community.solid-run.com/u/dekeoboe)\ **Post date:** [March 3, 2022, 10:35pm UTC](https://community.solid-run.com/t/cubox-m-not-responding/253/1 "2022-03-03T22:35:32Z")
I have tried multiple image files to get the CuBox M to boot - no response. I see no response from the keyboard or mouse so I cannot even tell if the SolidRun power supply is working. I have flashed SD cards from a MacBook (2017) using the DD Utility App (after figuring out I had to expand the .xz files before flashing) as well as the WIndows flash capabilities. I have reviewed the user guide and found nothing amiss in what I have done. I cannot get the CuBox to show up on the COM ports (adding the FTDI drivers to both host computers) so I’m wondering if the box I have has been DOA all along. I also see that there is supposed to be a GPIO button somewhere on the CuBox M but I can’t locate it. Any help would be much appreciated. ---
**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:** [March 4, 2022, 7:54am UTC](https://community.solid-run.com/t/cubox-m-not-responding/253/2 "2022-03-04T07:54:53Z")
Can you please verify that you see a faint red glow in the window when you connect power? This will verify that the device is powered. Additionally regarding the micro USB serial port connection. Make sure that it is plugging all the way in. Many micro USB cables have a stress relief on the connector that can interfere with the opening on the case. ---
**Author:** ![dekeoboe](https://avatars.discourse-cdn.com/v4/letter/d/bbce88/32.png) [@dekeoboe](https://community.solid-run.com/u/dekeoboe)\ **Post date:** [March 4, 2022, 9:38pm UTC](https://community.solid-run.com/t/cubox-m-not-responding/253/3 "2022-03-04T21:38:28Z")
Jon, No glow from the window after the unit is connected to power, hdmi, usb keyboard and mouse, and uUSB to Windows computer. i confirmed the uUSB is fully plugged in. ---
**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:** [March 7, 2022, 12:35pm UTC](https://community.solid-run.com/t/cubox-m-not-responding/253/4 "2022-03-07T12:35:33Z")
Could you please download and test this dev Image for the latest BSP. [imx-image-full-imx8mpsolidrun.wic.bz2 - Google Drive](https://drive.google.com/file/d/1MnBxwx6-D_oHr-9V17GV6r-2ZWBOhsem/view?usp=sharing) This is just a temporary image for your testing, and will be removed once the official images are down being built as part of our CI. By default this image boots with HummingBoard as the default device-tree. If the Image is working you can use the serial port to change to a CuBox-M device tree by editing the u-boot env variable fdtfile and changing it. ---
**Author:** ![dekeoboe](https://avatars.discourse-cdn.com/v4/letter/d/bbce88/32.png) [@dekeoboe](https://community.solid-run.com/u/dekeoboe)\ **Post date:** [March 7, 2022, 6:06pm UTC](https://community.solid-run.com/t/cubox-m-not-responding/253/5 "2022-03-07T18:06:31Z")
Jon, Image booted up - I now have HDMI, keyboard and mouse connected. Wayland terminal and NXP Demo show up on the list of apps. We had confirmed over the weekend we were getting a faint glow by removing the case and powering the device up - also used PoE power to see if that made any difference but it did not. We also confirmed the image files were properly flashed to the SD card but they still were not booting - we could see the serial connection but were unable to get any information through that port. This was all done using a linux machine (previously I was working with Windows and Macbook. I’ll now keep fiddling with the other images to see if I can get them to boot. Strange to me this was the only one I could boot. John ---
**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:** [March 7, 2022, 6:49pm UTC](https://community.solid-run.com/t/cubox-m-not-responding/253/6 "2022-03-07T18:49:23Z")
Which other images are you attempting to boot? ---
**Author:** ![dekeoboe](https://avatars.discourse-cdn.com/v4/letter/d/bbce88/32.png) [@dekeoboe](https://community.solid-run.com/u/dekeoboe)\ **Post date:** [March 7, 2022, 10:16pm UTC](https://community.solid-run.com/t/cubox-m-not-responding/253/7 "2022-03-07T22:16:46Z")
I tried those listed under the CuBox M - Android 10, Debian bullseye, and a couple others (I’ve since deleted the image files). All were listed for the CuBox M - some are from the SolidRun site, some are out on GitHub under Solidrun. ---
**Author:** ![dekeoboe](https://avatars.discourse-cdn.com/v4/letter/d/bbce88/32.png) [@dekeoboe](https://community.solid-run.com/u/dekeoboe)\ **Post date:** [March 8, 2022, 2:07am UTC](https://community.solid-run.com/t/cubox-m-not-responding/253/8 "2022-03-08T02:07:26Z")
[https://solid-run-images.sos-de-fra-1.exo.io/IMX8/Debian/sr-imx8-debian-bullseye-20210706-cli-imx8mp-sdhc-cubox-pulse.img.xz](https://solid-run-images.sos-de-fra-1.exo.io/IMX8/Debian/sr-imx8-debian-bullseye-20210706-cli-imx8mp-sdhc-cubox-pulse.img.xz) This is the image listed in the CuBox M quick start guide for Debian . I just flashed it to a micro-SD again, inserted it into the CuBox, powered it up and got no response. Keyboard and mouse do not respond, no HDMI video output and I cannot see anything on the serial monitor. ---
**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:** [March 8, 2022, 7:18am UTC](https://community.solid-run.com/t/cubox-m-not-responding/253/9 "2022-03-08T07:18:17Z")
So those older images wouldn’t boot because they were originally produced when only the 3GB SOM variant was available. The CuBox-M devices originally shipped with 1GB SOMs which were different than the developer models and needed modifications to boot correctly. ---
**Author:** ![dekeoboe](https://avatars.discourse-cdn.com/v4/letter/d/bbce88/32.png) [@dekeoboe](https://community.solid-run.com/u/dekeoboe)\ **Post date:** [March 8, 2022, 10:30am UTC](https://community.solid-run.com/t/cubox-m-not-responding/253/10 "2022-03-08T10:30:13Z")
Jon, Mine was ordered as the 4GB SOM but due to availability changed to the 3 GB SOM - here’s the SN NG0020060C854E3 and SKU is SRMP8QDWB1D03GE008X00CE which I thought was correct for the 3GB SOM. I just checked the SolidRun site and found the indeed it’s keyed out as a 3GB SOM with 8 GB eMMC. ---
**Author:** ![dekeoboe](https://avatars.discourse-cdn.com/v4/letter/d/bbce88/32.png) [@dekeoboe](https://community.solid-run.com/u/dekeoboe)\ **Post date:** [March 10, 2022, 7:27pm UTC](https://community.solid-run.com/t/cubox-m-not-responding/253/11 "2022-03-10T19:27:26Z")
Jon, After much experimentation I finally bit the bullet and wiped an old laptop, installed Ubuntu and now I can see the Cubox M boot sequence from the USB using Minicom terminal program. What I cannot do is break into the boot sequence (regardless of keys pressed) and the boot halts after several failed attempts at running /scripts/local-block. This seems to happen regardless of which Debian image I load (I figured out that DD does not handle compressed images on the MacOS so I flashed these using Ubuntu). Here’s the last bit of the Minicom output when the fatal termination happens. ``` 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=297a4a1c-01 does not exist. Dropping to a shell! BusyBox v1.30.1 (Debian 1:1.30.1-6+b2) built-in shell (ash) Enter 'help' for a list of built-in commands. ``` ---
**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:** [March 11, 2022, 6:23am UTC](https://community.solid-run.com/t/cubox-m-not-responding/253/12 "2022-03-11T06:23:34Z")
Turn off hardware flow control for the serial port setup of minicom. ---
**Author:** ![dekeoboe](https://avatars.discourse-cdn.com/v4/letter/d/bbce88/32.png) [@dekeoboe](https://community.solid-run.com/u/dekeoboe)\ **Post date:** [March 11, 2022, 11:29am UTC](https://community.solid-run.com/t/cubox-m-not-responding/253/13 "2022-03-11T11:29:56Z")
It is turned off. ---
**Author:** ![dekeoboe](https://avatars.discourse-cdn.com/v4/letter/d/bbce88/32.png) [@dekeoboe](https://community.solid-run.com/u/dekeoboe)\ **Post date:** [April 5, 2022, 8:56pm UTC](https://community.solid-run.com/t/cubox-m-not-responding/253/14 "2022-04-05T20:56:05Z")
Jon, What file is the PARTUUID specified in? I found a few conf files but could not identify which was the source for the UUID. Cubox M keeps aborting at the same point due to non-existent PARTUUID. I tried GREP command but did not have success. Thanks. John ---
**Author:** ![Josua](https://avatars.discourse-cdn.com/v4/letter/j/e47774/32.png) [@Josua](https://community.solid-run.com/u/Josua)\ **Post date:** [April 6, 2022, 8:03am UTC](https://community.solid-run.com/t/cubox-m-not-responding/253/15 "2022-04-06T08:03:37Z")
> [@jnettlet](#): > > The CuBox-M devices originally shipped with 1GB SOMs which were different than the developer models and needed modifications to boot correctly. This is probably a hint why it does not work. We have tested the Debian image you are using with the CuBox-M last year - and the device we tested with was functional. We are now preparing a new release based on the latest Linux support developed by @jnettlet; I suggest you wait a few days - hopefully the release will be timely. > [@dekeoboe](#): > > What file is the PARTUUID specified in It would be somewhere inside the initramfs at /conf/conf.d/default\_root But I think the real issue is reading the mmc device from Linux, not a wrong uuid. You can probably get more detailed logs by interrupting u-boot and adding below boot-args: ```auto setenv bootargs log_level=9 verbose boot ``` ---
**Author:** ![dekeoboe](https://avatars.discourse-cdn.com/v4/letter/d/bbce88/32.png) [@dekeoboe](https://community.solid-run.com/u/dekeoboe)\ **Post date:** [April 6, 2022, 2:40pm UTC](https://community.solid-run.com/t/cubox-m-not-responding/253/16 "2022-04-06T14:40:18Z")
Josua, Below is a snippit from the log - showing the 3GiB DRAM but the curious thing to me is the CRC error. I modified the default\_root (had done so previously) and that did not help. Still get the same PARTUUID error - default\_root reverted to the failed PARTUUID after a reboot . Will wait until I see the updated release on the images list. Thanks! As a side note, the PARTUUID declaration is the only line in the default\_root file… John CPU: i.MX8MP[8] rev1.1 1800 MHz (running at 1200 MHz) CPU: Commercial temperature grade (0C to 95C) at 30C Reset cause: POR Model: NXP i.MX8MPlus LPDDR4 SolidRun board DRAM: 3 GiB MMC: FSL\_SDHC: 1, FSL\_SDHC: 2 Loading Environment from MMC… \*\*\* Warning - bad CRC, using default environment ---
**Author:** ![Josua](https://avatars.discourse-cdn.com/v4/letter/j/e47774/32.png) [@Josua](https://community.solid-run.com/u/Josua)\ **Post date:** [April 7, 2022, 4:33pm UTC](https://community.solid-run.com/t/cubox-m-not-responding/253/17 "2022-04-07T16:33:12Z")
> [@dekeoboe](#): > > Will wait until I see the updated release on the images list. Here you go, it is finally done: [https://github.com/SolidRun/documentation/blob/bsp/imx8/debian-11\_sr9.md#Download](https://github.com/SolidRun/documentation/blob/bsp/imx8/debian-11_sr9.md#Download) This version should be functional with all variants of the i.MX8M Plus SoMs, and the latest CuBox-M. Feel free to report back in case you still see problems … ---
**Author:** ![dekeoboe](https://avatars.discourse-cdn.com/v4/letter/d/bbce88/32.png) [@dekeoboe](https://community.solid-run.com/u/dekeoboe)\ **Post date:** [April 10, 2022, 8:32pm UTC](https://community.solid-run.com/t/cubox-m-not-responding/253/18 "2022-04-10T20:32:58Z")
Josua, I still get the “dropping to shell” due to the UUID not being available. The system seems to get further since the display driver now starts and i get the 4 linux penquins and flashing cursor. I modified the default\_root PARTUUID to the UUID provided by blkid with no change and the default\_root reverts to the UUID previously unavailable after power reset. (i interrupted u-boot to make the env changes). I have changed the fdtfile and fdt\_file to cubox-m without any change in behaviour. I’m struggling to get the img files flashed to the eMMC which may resolve the problems. I tried to wget the img from solidrun but only get the “bad address” in return. John ---
**Author:** ![Josua](https://avatars.discourse-cdn.com/v4/letter/j/e47774/32.png) [@Josua](https://community.solid-run.com/u/Josua)\ **Post date:** [April 11, 2022, 6:41am UTC](https://community.solid-run.com/t/cubox-m-not-responding/253/19 "2022-04-11T06:41:00Z")
That is unfortunate ☹ I will suggest that you try collecting complete debug output, from power-on till failure of mounting root, from the serial console. Perhaps it contains a hint somewhere on what exactly is going wrong. Please 1. open the serial console and start capturing to a log file 2. power-on device, then interrupt U-Boot when the 3 seconds timer shows up: 3. enable verbose kernel messages, then continue boot 4. post here the complete log, hopefully I can spot a hint then. ---
**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/20 "2022-04-11T10:34:21Z")
Josua, Thank you for looking at this. Posting in two parts due to msg limit of 36k char; (initramfs) U-Boot SPL 2020.04-00022-g332c0bf3 (Apr 07 2022 - 15:57:48 +0000) Training for 3GByte Micron DDRINFO: start DRAM init DDRINFO: DRAM rate 3000MTS DDRINFO:ddrphy calibration done DDRINFO: ddrmix config done Normal Boot Trying to boot from BOOTROM image offset 0x8000, pagesize 0x200, ivt offset 0x0 NOTICE: BL31: v2.2(release):rel\_imx\_5.4.70\_2.3.0-0-gf1d7187f2 NOTICE: BL31: Built : 10:39:24, Apr 4 2022 U-Boot 2020.04-00022-g332c0bf3 (Apr 07 2022 - 15:57:48 +0000) CPU: i.MX8MP[8] rev1.1 1800 MHz (running at 1200 MHz) CPU: Commercial temperature grade (0C to 95C) at 42C Reset cause: POR Model: NXP i.MX8MPlus LPDDR4 SolidRun board DRAM: 3 GiB MMC: FSL\_SDHC: 1, FSL\_SDHC: 2 Loading Environment from MMC… \*\*\* Warning - bad CRC, using default environment [\*]-Video Link 0probe video device failed, ret -2 ``` [0] lcd-controller@32e80000, video [1] mipi_dsi@32e60000, video_bridge [2] adv7535@39, panel ``` probe video device failed, ret -2 In: serial Out: serial Err: serial BuildInfo: - ATF f1d7187 - U-Boot 2020.04-00022-g332c0bf3 switch to partitions #0, OK mmc1 is current device get\_tlvinfo\_from\_eeprom: failed to read from eeprom! board\_late\_init: could not identify board, defaulting to CuBox-M! board\_late\_init: could not identify som, defaulting to i.MX8M Plus Revision 1.1! flash target is MMC:1 Net: get\_tlvinfo\_from\_eeprom: failed to read from eeprom! Warning: ethernet@30bf0000 (eth1) using random MAC address - 0e:09:b1:94:9b:28 eth1: ethernet@30bf0000 [PRIME] Fastboot: Normal Normal Boot Hit any key to stop autoboot: 0 u-boot=\> setenv bootargs verbose log\_level=9 u-boot=\> boot switch to partitions #0, OK mmc1 is current device 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… ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Using Device Tree in place at 0000000043000000, end 0000000043010bab probe video device failed, ret -2 Starting kernel … [0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [0.000000] Linux version 5.10.72-imx8-sr (josua@arm64-debian-builder) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for De2 [0.000000] Machine model: SolidRun i.MX8MP CuBox-M [0.000000] efi: UEFI not found. [0.000000] Reserved memory: created CMA memory pool at 0x0000000072000000, size 512 MiB [0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool [0.000000] Reserved memory: created DMA memory pool at 0x0000000094300000, size 1 MiB [0.000000] OF: reserved mem: initialized node vdev0buffer@94300000, compatible id shared-dma-pool [0.000000] NUMA: No NUMA configuration found [0.000000] NUMA: Faking a node at [mem 0x0000000040000000-0x00000000ffffffff] [0.000000] NUMA: NODE\_DATA [mem 0xffa4a700-0xffa4cfff] [0.000000] Zone ranges: [0.000000] DMA [mem 0x0000000040000000-0x00000000ffffffff] [0.000000] DMA32 empty [0.000000] Normal empty [0.000000] Movable zone start for each node [0.000000] Early memory node ranges [0.000000] node 0: [mem 0x0000000040000000-0x00000000923fffff] [0.000000] node 0: [mem 0x0000000092400000-0x00000000a43fffff] [0.000000] node 0: [mem 0x00000000a4400000-0x00000000ffffffff] [0.000000] Initmem setup node 0 [mem 0x0000000040000000-0x00000000ffffffff] [0.000000] psci: probing for conduit method from DT. [0.000000] psci: PSCIv1.1 detected in firmware. [0.000000] psci: Using standard PSCI v0.2 function IDs [0.000000] psci: MIGRATE\_INFO\_TYPE not supported. [0.000000] psci: SMC Calling Convention v1.1 [0.000000] percpu: Embedded 23 pages/cpu s56152 r8192 d29864 u94208 [0.000000] Detected VIPT I-cache on CPU0 [0.000000] CPU features: detected: ARM erratum 845719 [0.000000] CPU features: detected: GIC system register CPU interface [0.000000] Built 1 zonelists, mobility grouping on. Total pages: 774144 [0.000000] Policy zone: DMA [0.000000] Kernel command line: verbose log\_level=9 console=ttymxc1,115200 log\_level=7 net.ifnames=0 [0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes, linear) [0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes, linear) [0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off [0.000000] Memory: 2231216K/3145728K available (15936K kernel code, 1332K rwdata, 5836K rodata, 2496K init, 507K bss, 390224K reserved, 5) [0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [0.000000] rcu: Preemptible hierarchical RCU implementation. [0.000000] rcu: RCU event tracing is enabled. [0.000000] rcu: RCU restricting CPUs from NR\_CPUS=256 to nr\_cpu\_ids=4. [0.000000] Trampoline variant of Tasks RCU enabled. [0.000000] Tracing variant of Tasks RCU enabled. [0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies. [0.000000] rcu: Adjusting geometry for rcu\_fanout\_leaf=16, nr\_cpu\_ids=4 [0.000000] NR\_IRQS: 64, nr\_irqs: 64, preallocated irqs: 0 [0.000000] GICv3: GIC: Using split EOI/Deactivate mode [0.000000] GICv3: 160 SPIs implemented [0.000000] GICv3: 0 Extended SPIs implemented [0.000000] GICv3: Distributor has no Range Selector support [0.000000] GICv3: 16 PPIs implemented [0.000000] GICv3: CPU0: found redistributor 0 region 0:0x0000000038880000 [0.000000] ITS: No ITS available, not enabling LPIs [0.000000] random: get\_random\_bytes called from start\_kernel+0x318/0x4d4 with crng\_init=0 [0.000000] arch\_timer: cp15 timer(s) running at 8.00MHz (phys). [0.000000] clocksource: arch\_sys\_counter: mask: 0xffffffffffffff max\_cycles: 0x1d854df40, max\_idle\_ns: 440795202120 ns [0.000003] sched\_clock: 56 bits at 8MHz, resolution 125ns, wraps every 2199023255500ns [0.000405] Console: colour dummy device 80x25 [0.000468] Calibrating delay loop (skipped), value calculated using timer frequency.. 16.00 BogoMIPS (lpj=32000) [0.000479] pid\_max: default: 32768 minimum: 301 [0.000545] LSM: Security Framework initializing [0.000601] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes, linear) [0.000618] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes, linear) [0.001884] rcu: Hierarchical SRCU implementation. [0.002986] EFI services will not be available. [0.003154] smp: Bringing up secondary CPUs … [0.003509] Detected VIPT I-cache on CPU1 [0.003534] GICv3: CPU1: found redistributor 1 region 0:0x00000000388a0000 [0.003572] CPU1: Booted secondary processor 0x0000000001 [0x410fd034] [0.004037] Detected VIPT I-cache on CPU2 [0.004056] GICv3: CPU2: found redistributor 2 region 0:0x00000000388c0000 [0.004077] CPU2: Booted secondary processor 0x0000000002 [0x410fd034] [0.004438] Detected VIPT I-cache on CPU3 [0.004454] GICv3: CPU3: found redistributor 3 region 0:0x00000000388e0000 [0.004472] CPU3: Booted secondary processor 0x0000000003 [0x410fd034] [0.004530] smp: Brought up 1 node, 4 CPUs [0.004548] SMP: Total of 4 processors activated. [0.004556] CPU features: detected: 32-bit EL0 Support [0.004564] CPU features: detected: CRC32 instructions [0.004571] CPU features: detected: 32-bit EL1 Support [0.012635] CPU: All CPU(s) started at EL2 [0.012659] alternatives: patching kernel code [0.013781] devtmpfs: initialized [0.021189] KASLR disabled due to lack of seed [0.021332] clocksource: jiffies: mask: 0xffffffff max\_cycles: 0xffffffff, max\_idle\_ns: 7645041785100000 ns [0.021346] futex hash table entries: 1024 (order: 4, 65536 bytes, linear) [0.035114] pinctrl core: initialized pinctrl subsystem [0.035590] DMI not present or invalid. [0.035967] NET: Registered protocol family 16 [0.043145] DMA: preallocated 512 KiB GFP\_KERNEL pool for atomic allocations [0.044236] DMA: preallocated 512 KiB GFP\_KERNEL|GFP\_DMA pool for atomic allocations [0.045399] DMA: preallocated 512 KiB GFP\_KERNEL|GFP\_DMA32 pool for atomic allocations [0.045485] audit: initializing netlink subsys (disabled) [0.045696] audit: type=2000 audit(0.044:1): state=initialized audit\_enabled=0 res=1 [0.046165] thermal\_sys: Registered thermal governor ‘step\_wise’ [0.046169] thermal\_sys: Registered thermal governor ‘power\_allocator’ [0.046460] cpuidle: using governor menu [0.046677] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers. [0.046756] ASID allocator initialised with 65536 entries [0.047753] Serial: AMBA PL011 UART driver [0.047808] imx mu driver is registered. [0.047827] imx rpmsg driver is registered. [0.077098] imx8mp-pinctrl 30330000.pinctrl: initialized IMX pinctrl driver [0.092442] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [0.092455] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages [0.092464] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [0.092472] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages [0.093377] cryptd: max\_cpu\_qlen set to 1000 [0.096859] iommu: Default domain type: Translated [0.097013] vgaarb: loaded [0.097296] SCSI subsystem initialized [0.097588] usbcore: registered new interface driver usbfs [0.097636] usbcore: registered new interface driver hub [0.097663] usbcore: registered new device driver usb [0.098737] mc: Linux media interface: v0.10 [0.098761] videodev: Linux video capture interface: v2.00 [0.098824] pps\_core: LinuxPPS API ver. 1 registered [0.098831] pps\_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti [giometti@linux.it](mailto:giometti@linux.it) [0.098844] PTP clock support registered [0.099002] EDAC MC: Ver: 3.0.0 [0.100028] FPGA manager framework [0.100450] Bluetooth: Core ver 2.22 [0.100479] NET: Registered protocol family 31 [0.100486] Bluetooth: HCI device and connection manager initialized [0.100495] Bluetooth: HCI socket layer initialized [0.100502] Bluetooth: L2CAP socket layer initialized [0.100517] Bluetooth: SCO socket layer initialized [0.101462] clocksource: Switched to clocksource arch\_sys\_counter [0.101625] VFS: Disk quotas dquot\_6.6.0 [0.101672] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [0.107599] NET: Registered protocol family 2 [0.107747] IP idents hash table entries: 65536 (order: 7, 524288 bytes, linear) [0.109211] tcp\_listen\_portaddr\_hash hash table entries: 2048 (order: 3, 32768 bytes, linear) [0.109283] TCP established hash table entries: 32768 (order: 6, 262144 bytes, linear) [0.109510] TCP bind hash table entries: 32768 (order: 7, 524288 bytes, linear) [0.109964] TCP: Hash tables configured (established 32768 bind 32768) [0.110072] UDP hash table entries: 2048 (order: 4, 65536 bytes, linear) [0.110151] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes, linear) [0.110335] NET: Registered protocol family 1 [0.110689] RPC: Registered named UNIX socket transport module. [0.110696] RPC: Registered udp transport module. [0.110700] RPC: Registered tcp transport module. [0.110707] RPC: Registered tcp NFSv4.1 backchannel transport module. [0.111393] PCI: CLS 0 bytes, default 64 [0.111544] Unpacking initramfs… [0.401563] Freeing initrd memory: 7428K [0.402168] hw perfevents: enabled with armv8\_pmuv3 PMU driver, 7 counters available [0.402755] kvm [1]: IPA Size Limit: 40 bits [0.404000] kvm [1]: GICv3: no GICV resource entry [0.404006] kvm [1]: disabling GICv2 emulation [0.404024] kvm [1]: GIC system register CPU interface enabled [0.404087] kvm [1]: vgic interrupt IRQ9 [0.404192] kvm [1]: Hyp mode initialized successfully [0.407055] Initialise system trusted keyrings [0.407164] workingset: timestamp\_bits=42 max\_order=20 bucket\_order=0 [0.413015] squashfs: version 4.0 (2009/01/31) Phillip Lougher [0.413618] NFS: Registering the id\_resolver key type [0.413647] Key type id\_resolver registered [0.413652] Key type id\_legacy registered [0.413725] nfs4filelayout\_init: NFSv4 File Layout Driver Registering… [0.413732] nfs4flexfilelayout\_init: NFSv4 Flexfile Layout Driver Registering… [0.413757] jffs2: version 2.2. (NAND) �© 2001-2006 Red Hat, Inc. [0.414100] 9p: Installing v9fs 9p2000 file system support [0.450092] Key type asymmetric registered [0.450100] Asymmetric key parser ‘x509’ registered [0.450129] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 241) [0.450136] io scheduler mq-deadline registered [0.450142] io scheduler kyber registered [0.451998] samsung-hdmi-phy 32fdff00.hdmiphy: failed to get phy apb clk: -517 [0.458615] clk: failed to reparent gic to sys\_pll2\_500m: -16 [0.462263] mxs-dma 33000000.dma-apbh: initialized [0.464010] Bus freq driver module loaded [0.466034] reg-userspace-consumer power-usb-ports: Failed to get supplies: -517 [0.469747] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [0.471876] 30860000.serial: ttymxc0 at MMIO 0x30860000 (irq = 30, base\_baud = 5000000) is a IMX [0.472007] serial serial0: tty port ttymxc0 registered [0.472565] 30880000.serial: ttymxc2 at MMIO 0x30880000 (irq = 31, base\_baud = 5000000) is a IMX [0.473114] 30890000.serial: ttymxc1 at MMIO 0x30890000 (irq = 32, base\_baud = 1500000) is a IMX [1.500127] printk: console [ttymxc1] enabled [1.506647] imx-lcdifv3 32fc6000.lcd-controller: No irq get, ret=-517 [1.515675] imx-hdmi-pavi 32fc4000.hdmi-pai-pvi: No pvi clock get [1.531785] loop: module loaded [1.535978] megasas: 07.714.04.00-rc1 [1.540897] imx ahci driver is registered. [1.547972] libphy: Fixed MDIO Bus: probed [1.552323] tun: Universal TUN/TAP device driver, 1.6 [1.558335] e1000: Intel(R) PRO/1000 Network Driver [1.563228] e1000: Copyright (c) 1999-2006 Intel Corporation. [1.569013] e1000e: Intel(R) PRO/1000 Network Driver [1.573988] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. [1.579944] igb: Intel(R) Gigabit Ethernet Network Driver [1.585348] igb: Copyright (c) 2007-2014 Intel Corporation. [1.590954] igbvf: Intel(R) Gigabit Virtual Function Network Driver [1.597225] igbvf: Copyright (c) 2009 - 2012 Intel Corporation. [1.603204] usbcore: registered new interface driver r8152 [1.608891] VFIO - User Level meta-driver version: 0.3 [1.620310] ehci\_hcd: USB 2.0 ‘Enhanced’ Host Controller (EHCI) Driver [1.626865] ehci-pci: EHCI PCI platform driver [1.631351] ehci-platform: EHCI generic platform driver [1.636765] ohci\_hcd: USB 1.1 ‘Open’ Host Controller (OHCI) Driver [1.642974] ohci-pci: OHCI PCI platform driver [1.647454] ohci-platform: OHCI generic platform driver [1.653414] usbcore: registered new interface driver uas [1.658772] usbcore: registered new interface driver usb-storage [1.664810] usbcore: registered new interface driver usb\_ehset\_test [1.674502] snvs\_rtc 30370000.snvs:snvs-rtc-lp: registered as rtc1 [1.680911] i2c /dev entries driver [1.688023] EDAC MC: ECC not enabled [1.692798] sdhci: Secure Digital Host Controller Interface driver [1.699009] sdhci: Copyright(c) Pierre Ossman [1.703639] Synopsys Designware Multimedia Card Interface Driver [1.710260] sdhci-pltfm: SDHCI platform and OF driver helper [1.716844] sdhci-esdhc-imx 30b40000.mmc: voltage-ranges unspecified [1.723263] ledtrig-cpu: registered to indicate activity on CPUs [1.730318] usbcore: registered new interface driver usbhid [1.735906] usbhid: USB HID core driver [1.743772] imx-dsp-rproc 3b6e8000.dsp: Failed to get clock dsp\_clk1 [1.750149] imx-dsp-rproc 3b6e8000.dsp: failed on imx\_dsp\_rproc\_clk\_get [1.757448] remoteproc remoteproc0: releasing imx-dsp-rproc [1.768562] Galcore version 6.4.3.p2.336687 [1.879663] [drm] Initialized vivante 1.0.0 20170808 for 40000000.mix\_gpu\_ml on minor 0 [1.889345] hantrodec 0 : module inserted. Major = 510 [1.895141] hantrodec 1 : module inserted. Major = 510 [1.901511] hantroenc: HW at base \<0000000038320000\> with ID \<0x80006200\> [1.908433] hx280enc: module inserted. Major \<509\> [1.914005] NET: Registered protocol family 26 [1.918882] NET: Registered protocol family 10 [1.924593] Segment Routing with IPv6 [1.928316] NET: Registered protocol family 17 [1.933482] Bluetooth: RFCOMM TTY layer initialized [1.938370] Bluetooth: RFCOMM socket layer initialized [1.943539] Bluetooth: RFCOMM ver 1.11 [1.947318] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [1.952641] Bluetooth: BNEP filters: protocol multicast [1.957878] Bluetooth: BNEP socket layer initialized [1.962850] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [1.968786] Bluetooth: HIDP socket layer initialized [1.974990] NET: Registered protocol family 41 [1.980248] 9pnet: Installing 9P2000 support [1.984573] tsn generic netlink module v1 init… [1.989358] Key type dns\_resolver registered [1.994524] registered taskstats version 1 [1.998636] Loading compiled-in X.509 certificates [2.083452] nxp-pca9450 0-0025: pca9450bc probed. [2.088500] i2c i2c-0: IMX I2C adapter registered [2.094706] i2c i2c-2: IMX I2C adapter registered [2.100667] i2c i2c-3: IMX I2C adapter registered [2.106383] imx8mq-usb-phy 381f0040.usb-phy: supply vbus not found, using dummy regulator [2.114932] imx8mq-usb-phy 382f0040.usb-phy: supply vbus not found, using dummy regulator [2.123374] samsung-hdmi-phy 32fdff00.hdmiphy: failed to get phy apb clk: -517 [2.143280] SoC: i.MX8MP revision 1.1 [2.147220] imx-cpufreq-dt imx-cpufreq-dt: cpu speed grade 5 mkt segment 0 supported-hw 0x20 0x1 [2.158288] imx-lcdifv3 32fc6000.lcd-controller: No irq get, ret=-517 [2.166353] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller [2.171882] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 1 [2.179890] xhci-hcd xhci-hcd.1.auto: hcc params 0x0220fe6c hci version 0x110 quirks 0x0000002021810010 [2.189326] xhci-hcd xhci-hcd.1.auto: irq 63, io mem 0x38100000 [2.195377] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller [2.200882] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 2 [2.208563] xhci-hcd xhci-hcd.1.auto: Host supports USB 3.0 SuperSpeed [2.215944] hub 1-0:1.0: USB hub found [2.219750] hub 1-0:1.0: 1 port detected [2.223955] usb usb2: We don’t know the algorithms for LPM for this host, disabling LPM. [2.232778] hub 2-0:1.0: USB hub found [2.236582] hub 2-0:1.0: 1 port detected [2.241931] xhci-hcd xhci-hcd.2.auto: xHCI Host Controller [2.247456] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus number 3 [2.255461] xhci-hcd xhci-hcd.2.auto: hcc params 0x0220fe6c hci version 0x110 quirks 0x0000002021810010 [2.264905] xhci-hcd xhci-hcd.2.auto: irq 64, io mem 0x38200000 [2.270957] xhci-hcd xhci-hcd.2.auto: xHCI Host Controller [2.276457] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus number 4 [2.284126] xhci-hcd xhci-hcd.2.auto: Host supports USB 3.0 SuperSpeed [Next page](https://community.solid-run.com/t/cubox-m-not-responding/253.md?page=2)