Hello,
I am using kernel 3.17.2-x with U-boot 2014.04 .
When I try to load the kernel on my Sabre lite board it hangs at following line.
* Starting set console font[ OK ]
* Stopping set console font[ OK ]
* Starting userspace bootsplash[ OK ]
* Stopping userspace bootsplash[ OK ]
* Starting Send an event to indicate plymouth is up[ OK ]
* Stopping Send an event to indicate plymouth is up[ OK ]
* Starting configure network device security[ OK ]
* Starting configure network device security[ OK ]
* Starting configure network device[ OK ]
* Starting configure network device[ OK ]
* Stopping cold plug devices[ OK ]
* Starting configure network device security[ OK ]
* Stopping log initial device creation[ OK ]
* Starting Mount network filesystems[ OK ]
* Stopping Mount network filesystems[ OK ]
* Starting configure network device[ OK ]
* Starting Bridge socket events into upstart[ OK ]
The disk drive for / is not ready yet or not present.
keys:Continue to wait, or Press S to skip mounting or M for manual recovery
I tried the following fstab settings
Setting 1:
#UNCONFIGUreD FSTAB FOR BASE SYSTEM
/dev/mmcblk0p2 / auto errors=remount-ro 0 1
/dev/mmcblk0p1 /boot/uboot auto defaults 0 2
Setttings 2:
with UUID values
I don't find the reason why my kernel is not loading.
It was working before with same configuration, we just loaded the same with new SD card.
Hi Venkata
may be useful to check which branches supported for BD
GitHub - boundarydevices/linux-imx6: Boundary Devices Kernel tree for i.MX6
Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Nothings works...
Kernel : 3.17.2-arm7-x3
U-boot : 2014.04
Board : Sabre Lite
[ 3.603993] hidraw: raw HID events driver (C) Jiri Kosina
[ 3.605180] mmcblk0: mmc0:aaaa SL08G 7.40 GiB
[ 3.614939] usbcore: registered new interface driver usbhid
[ 3.620572] usbhid: USB HID core driver
[ 3.620640] mmcblk0: p1 p2
[ 3.627972] ashmem: initialized
[ 3.633146] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 3.639810] [drm] No driver support for vblank timestamp query.
[ 3.645881] imx-drm display-subsystem: bound imx-ipuv3-crtc.0 (ops ipu_crtc_ops)
[ 3.653379] imx-drm display-subsystem: bound imx-ipuv3-crtc.1 (ops ipu_crtc_ops)
[ 3.660909] imx-drm display-subsystem: bound imx-ipuv3-crtc.4 (ops ipu_crtc_ops)
[ 3.664759] usb 1-1: new high-speed USB device number 2 using ci_hdrc
[ 3.675001] imx-drm display-subsystem: bound imx-ipuv3-crtc.5 (ops ipu_crtc_ops)
[ 3.682671] imx-drm display-subsystem: bound 2000000.aips-bus:ldb@020e0008 (ops imx_ldb_ops)
'
'
'
* Starting Mount filesystems on boot[ OK ]
* Starting Populate /dev filesystem[ OK ]
* Stopping Populate /dev filesystem[ OK ]
* Star[ 5.526462] imx-sgtl5000 sound: ASoC: CPU DAI (null) not registered
ting Populate and link to /run filesystem[ OK ]
* Stopping Populate and link to /run fil[ 5.541962] imx-sgtl5000 sound: snd_soc_register_card failed (-517)
esystem[ OK ]
* Stopping Track if upstart is running in a container[ OK ]
* Sta[ 5.556577] imx-sgtl5000 sound: ASoC: CODEC (null) not registered
rting Initialize or finalize reso[ 5.563776] imx-sgtl5000 sound: snd_soc_register_card failed (-517)
lvconf[ OK ]
* Starting set console keymap[ OK ]
* Starting Signal sysvinit that virtual filesystems are mounted[ OK ]
* Starting Signal sysvinit that virtual filesystems are mounted[ OK ]
* Starting Bridge udev events into upstart[ OK ]
* Stopping set console keymap[ OK ]
* Starting Signal sysvinit that remote filesystems are mounted[ OK ]
* Starting device node and kernel event manager[ OK ]
* Starting load modules from /etc/modules[ OK ]
* Starting cold plug devices[ OK ]
* Starting log initial device creation[ OK ]
* Stopping load modules from /etc/modules[ OK ]
* Starting set console font[ OK ]
* Stopping set console font[ OK ]
* Starting userspace bootsplash[ OK ]
* Stopping userspace bootsplash[ OK ]
* Starting Send an event to indicate plymouth is up[ OK ]
* Stopping Send an event to indicate plymouth is up[ OK ]
* Starting configure network device security[ OK ]
* Starting configure network device security[ OK ]
* Stopping cold plug devices[ OK ]
* Stopping log initial device creation[ OK ]
* Starting configure network device[ OK ]
* Starting configure network device[ OK ]
* Starting configure network device security[ OK ]
* Starting Mount network filesystems[ OK ]
* Stopping Mount network filesystems[ OK ]
* Starting configure network device[ OK ]
* Starting Bridge socket events into upstart[ OK ]
The disk drive for / is not ready yet or not present.
keys:Continue to wait, or Press S to skip mounting or M for manual recovery
Still I am getting the same issue...
Please any body help.
Hi,
Why are you using a 3.17 kernel? Boundary Devices only supports nxp-based kernels (3.0.35/3.10.x/3.14.x/4.1.15).
Otherwise I suggest trying latest mainline kernel which is known to work too (4.9.9).
Regards,
Gary
Hello,
Hi Gary Bisson,
with kernel 4.9.9-armv7-x4 with U-Boot 2014.04-00123-g63ae4a5 (May 14 2014 - 17:09:55)
After kernel Loading the final message is as follows.
* Stopping System V runlevel compatibility[ OK ]
I think kernel failed !!!
Any known issue ?
Hi,
No, kernel 4.9.9 has been tested no later than last week and is working perfectly.
I guess the issue comes from your user-space.
Regards,
Gary