[opensuse-arm] Root device not found
Hi, I'm trying to boot my udoo quad board (imx6) but it fails because the root device is not found: [1454973205.868008] Searching for boot device... [1454973205.922481] Waiting for device /dev/mmcblk0p2 to settle... [1454973207.943315] Waiting for device /dev/mmcblk0p2 to settle... [1454973209.964210] Waiting for device /dev/mmcblk0p2 to settle... [1454973211.985181] Waiting for device /dev/mmcblk0p2 to settle... [1454973214.005732] Waiting for device /dev/mmcblk0p2 to settle... [1454973216.026237] Waiting for device /dev/mmcblk0p2 to settle... [1454973218.047048] Waiting for device /dev/mmcblk0p2 to settle... [1454973220.067520] Waiting for device /dev/mmcblk0p2 to settle... [1454973266.552193] Specified root device /dev/mmcblk0p2 not found. Found devices: [1454973267.286059] root device not found... fatal ! Looking at the full log I see that the problem may be that the mmc module is not loaded. I unpacked the initram and there are some modules, but I don't know which one is for the imx6 platform: mmc/card: total 80 -rw-r--r-- 1 oscar users 51882 feb 10 00:31 mmc_block.ko -rw-r--r-- 1 oscar users 25090 feb 10 00:31 sdio_uart.ko mmc/core: total 192 -rw-r--r-- 1 oscar users 195402 feb 10 00:31 mmc_core.ko mmc/host: total 848 -rw-r--r-- 1 oscar users 13766 feb 10 00:31 dw_mmc-exynos.ko -rw-r--r-- 1 oscar users 10746 feb 10 00:31 dw_mmc-k3.ko -rw-r--r-- 1 oscar users 47662 feb 10 00:31 dw_mmc.ko -rw-r--r-- 1 oscar users 9662 feb 10 00:31 dw_mmc-pltfm.ko -rw-r--r-- 1 oscar users 12670 feb 10 00:31 dw_mmc-rockchip.ko -rw-r--r-- 1 oscar users 31746 feb 10 00:31 mmci.ko -rw-r--r-- 1 oscar users 4338 feb 10 00:31 mmci_qcom_dml.ko -rw-r--r-- 1 oscar users 32278 feb 10 00:31 mtk-sd.ko -rw-r--r-- 1 oscar users 23894 feb 10 00:31 mvsdio.ko -rw-r--r-- 1 oscar users 25982 feb 10 00:31 mxcmmc.ko -rw-r--r-- 1 oscar users 41634 feb 10 00:31 omap_hsmmc.ko -rw-r--r-- 1 oscar users 29522 feb 10 00:31 omap.ko -rw-r--r-- 1 oscar users 33522 feb 10 00:31 rtsx_usb_sdmmc.ko -rw-r--r-- 1 oscar users 13990 feb 10 00:31 sdhci-bcm-kona.ko -rw-r--r-- 1 oscar users 8046 feb 10 00:31 sdhci-dove.ko -rw-r--r-- 1 oscar users 25314 feb 10 00:31 sdhci-esdhc-imx.ko -rw-r--r-- 1 oscar users 11086 feb 10 00:31 sdhci_f_sdh30.ko -rw-r--r-- 1 oscar users 11574 feb 10 00:31 sdhci-iproc.ko -rw-r--r-- 1 oscar users 63518 feb 10 00:31 sdhci.ko -rw-r--r-- 1 oscar users 14966 feb 10 00:31 sdhci-msm.ko -rw-r--r-- 1 oscar users 10978 feb 10 00:31 sdhci-of-arasan.ko -rw-r--r-- 1 oscar users 10030 feb 10 00:31 sdhci-of-at91.ko -rw-r--r-- 1 oscar users 15682 feb 10 00:31 sdhci-of-esdhc.ko -rw-r--r-- 1 oscar users 13890 feb 10 00:31 sdhci-pltfm.ko -rw-r--r-- 1 oscar users 18354 feb 10 00:31 sdhci-s3c.ko -rw-r--r-- 1 oscar users 11770 feb 10 00:31 sdhci-spear.ko -rw-r--r-- 1 oscar users 13054 feb 10 00:31 sdhci-st.ko -rw-r--r-- 1 oscar users 11382 feb 10 00:31 sdhci-tegra.ko -rw-r--r-- 1 oscar users 35430 feb 10 00:31 sh_mmcif.ko -rw-r--r-- 1 oscar users 15674 feb 10 00:31 sh_mobile_sdhi.ko -rw-r--r-- 1 oscar users 23906 feb 10 00:31 sunxi-mmc.ko -rw-r--r-- 1 oscar users 38210 feb 10 00:31 tmio_mmc_core.ko -rw-r--r-- 1 oscar users 7730 feb 10 00:31 tmio_mmc.ko -rw-r--r-- 1 oscar users 35670 feb 10 00:31 usdhi6rol0.ko -rw-r--r-- 1 oscar users 12182 feb 10 00:31 ushc.ko -rw-r--r-- 1 oscar users 43886 feb 10 00:31 vub300.ko -rw-r--r-- 1 oscar users 18750 feb 10 00:31 wmt-sdmmc.ko Can I set a debug flag or something to see why the modules are not being loading? Thanks! -- Oscar -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi Oscar,
I'm trying to boot my udoo quad board (imx6) but it fails because the root device is not found:
Yeah, unfortunately all relevant kernel modules are missing from the current images :-/
Looking at the full log I see that the problem may be that the mmc module is not loaded. I unpacked the initram and there are some modules, but I don't know which one is for the imx6 platform:
I believe that would be sdhci-esdhc-imx.ko (which is missing).
Can I set a debug flag or something to see why the modules are not being loading?
yes, kiwidebug=1 passed to the command line (e.g. by editing the boot.script and recompiling it into the boot.scr) will give you a shell once it failed, from there you can debug further. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
El 2016-02-12 14:36, Dirk Müller escribió:
Hi Oscar,
Looking at the full log I see that the problem may be that the mmc module is not loaded. I unpacked the initram and there are some modules, but I don't know which one is for the imx6 platform:
I believe that would be sdhci-esdhc-imx.ko (which is missing).
Well, that file (an others) are included in the initram: (none):/lib/modules/4.4.0-3-default/kernel/drivers # find mmc -name *imx* mmc/host/sdhci-esdhc-imx.ko
Can I set a debug flag or something to see why the modules are not being loading?
yes, kiwidebug=1 passed to the command line (e.g. by editing the boot.script and recompiling it into the boot.scr) will give you a shell once it failed, from there you can debug further.
Thanks, i didn't know that option. It could be nice if the firstboot had that option by default. That way it would be easier to debug boot problems. Unfortunately, manually loading the mmc module does not solve the problem. The module is correctly loaded and the reader seems to be recognized, but the card is not (tried another card with the same result): (none):/lib/modules/4.4.0-3-default/kernel/drivers/mmc/host # modprobe sdhci-esdhc-imx [ 418.121862] sdhci: Secure Digital Host Controller Interface driver [ 418.128108] sdhci: Copyright(c) Pierre Ossman [ 418.133722] sdhci-pltfm: SDHCI platform and OF driver helper [ 418.141531] /soc/aips-bus@02100000/usdhc@02198000: voltage-ranges unspecified [ 418.148717] sdhci-esdhc-imx 2198000.usdhc: could not get ultra high speed state, work on normal mode [ 418.158235] sdhci-esdhc-imx 2198000.usdhc: No vmmc regulator found [ 418.164540] sdhci-esdhc-imx 2198000.usdhc: No vqmmc regulator found [ 418.204572] mmc0: SDHCI controller on 2198000.usdhc [2198000.usdhc] using ADMA [ 418.215337] imx-gpc 20dc000.gpc: failed to get pu regulator: -517 (none):/lib/modules/4.4.0-3-default/kernel/drivers/mmc/host # [ 418.257316] mmc0: host does not support reading read-only switch, assuming write-enable [ 418.271478] mmc0: new high speed SDHC card at address 0007
Greetings, Dirk
Thanks! -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi, same problem for the OLinuXino sunxi boards. Booting with kiwidebug=1 cat /proc/partitions give me: major minor #blocks name 1 0 131072 ram0 1 1 131072 ram1 1 2 131072 ram2 1 3 131072 ram3 1 4 131072 ram4 1 5 131072 ram5 1 6 131072 ram6 1 7 131072 ram7 1 8 131072 ram8 1 9 131072 ram9 1 10 131072 ram10 1 11 131072 ram11 1 12 131072 ram12 1 13 131072 ram13 1 14 131072 ram14 1 15 131072 ram15 The mmc driver is included in the initrd and it can be loaded: modprobe sunxi_mmc [ 161.333212] sunxi-mmc 1c0f000.mmc: No vqmmc regulator found [ 161.340189] sunxi-mmc 1c0f000.mmc: Got CD GPIO [ 161.374529] sunxi-mmc 1c0f000.mmc: base:0xf1328000 irq:26 (none):/ # [ 161.407866] mmc0: host does not support reading read-only switch, assuming write-enable [ 161.418645] mmc0: new high speed SDHC card at address b00e But still the same partitions available, no mmc partitions or devices visible. Br, Frank -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 14.02.2016 um 12:51 schrieb Frank Kunz:
But still the same partitions available, no mmc partitions or devices visible.
After loading modprobe mmc_block [ 874.002929] mmcblk0: mmc0:b00e SU08G 7.40 GiB [ 874.009336] mmcblk0: p1 p2 the mmc devices are there. Br, Frank -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi Frank,
2016-02-14 19:35 GMT+01:00 Frank Kunz
attached the /var/log/boot.kiwi
Thanks, found the problem. It was an (ARM local) patch in our systemd (the one that was added to fix the kiwi builds for armv6) that entirely breaks all armv7/v8 images. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
El 2016-02-15 23:02, Dirk Müller escribió:
Hi Frank,
2016-02-14 19:35 GMT+01:00 Frank Kunz
: attached the /var/log/boot.kiwi
Thanks, found the problem. It was an (ARM local) patch in our systemd (the one that was added to fix the kiwi builds for armv6) that entirely breaks all armv7/v8 images.
Greetings, Dirk
Thank you both. I did the same thing has Frank (in my case, sdhci-esdhc-imx and mmc_block) but I got another error when kiwi tried to resize the partitions. I will give it another try once the images are built again with the patches. -- Cheers -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (3)
-
Dirk Müller
-
Frank Kunz
-
Oscar C