Le 18/06/2015 03:03, Fabian Vogt a écrit :
Am Mittwoch, 17. Juni 2015, 21:11:38 schrieb Freek de Kruijf:
Op woensdag 17 juni 2015 14:32:27 schreef Guillaume Gardet:
Do you have any explanation why the boot process had stopped?
I think it is not stopped but it is slowly loading the initrd which is much
bigger than the kernel which was slowly loaded (75.2 KiB/s) just before.
So, just wait some minutes. I would say 10 minutes or maybe more I am
afraid. :(
I do not know why load is so slow on u-boot for the Raspberry Pi.
Guillaume
I had the same problem and needed to wait 10 minutes before I could have
access via ssh. In my view the problem is the partitioning, which is done
initially. So it may take longer if you have a larger SD card.
Actually, there's a fix for this very annoying issue:
http://lists.denx.de/pipermail/u-boot/2015-June/216852.html
It's working just fine (1.4 MiB/s), but I haven't tested it thoroughly.
I'm currently trying to get it to build in my OBS project
to have a proper RPM, but OBS is pretty busy ATM.
Thanks for the link to this patch.
I can push this patch to our Factory u-boot packages once someone will have
tested it.
To get some kernel output, append "console=tty0" to the bootargs line
in /boot/boot.script and use mkimage to generate the boot.scr file
for u-boot. Or just use the serial port, the serial console is active by
default.
I think that there are kernel messages on screen too, by default. No?
Also, make sure that an initrd exists at all, one image I downloaded had
a broken initrd symlink.
Best of luck,
Fabian
(This is my first message to this list, I don't know whether I sent it
correctly.
Replying to mails on the web doesn't work directly so I had to play
around with KMail and message-ids)
Seems ok to me. :)
Guillaume
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
