[opensuse-arm] R:R:I am Lost: No Boot
Hi Raspi-Friends. First thanks to Alex, Freek et remerciements pour Guillaume.for indicating the Repos for the various files for the Raspi B and Raspi 2 and pointing out the different versionS JeoS; XCFE and LXQT. I have downloaded the there xz.files and installed them on a sd-stick. But when, I get the folowing messages: > Net: Net initialization skipped > No ethernet found ---------> Cable was connected to an HDLC-Router > hit any key to stop autoboot: 2 > 1 > 0 > switch to partitions #0: OK > mmc0 is current device > scanning mmc0:1... > Found U-Boot script /boot.scr > reading /boot.src
115 bytes read in 420 ms (0 Bytes/s) # executing script at 00000000 2708 bytes read in 420 ms (1000 Bytes/s) # executing script at 00000200 4389568 bytes read in 56550 ms (75.2 KiB/s)
No further reaction Do you have any explanation why the boot process had stopped? Thanks for you assistance. Edgar, DJ3PU, Munich P.S. I am preparing an article to be included in Magazine of the German Amateur Radio Club (DARC) on implementing Ham Radio Programs into the Rasberry Pi, succeding up to today with Debian-Squeeze, but with OpenSUSE ??? -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On Wed, Jun 17, 2015 at 02:01:05PM +0200, Edgar Dombrowski wrote:
> Net: Net initialization skipped > No ethernet found ---------> Cable was connected to an HDLC-Router > hit any key to stop autoboot: 2 > 1 > 0 > switch to partitions #0: OK > mmc0 is current device > scanning mmc0:1... > Found U-Boot script /boot.scr > reading /boot.src
115 bytes read in 420 ms (0 Bytes/s) # executing script at 00000000 2708 bytes read in 420 ms (1000 Bytes/s) # executing script at 00000200 4389568 bytes read in 56550 ms (75.2 KiB/s)
No further reaction
Do you have any explanation why the boot process had stopped?
Incidentally, a few week ago I saw this behaviour. I installed the LXQT image and got stuck at the same place. I was blaming the SD card for the low speed, so used another one. Same result, but the reported speed was higher. The IO speed reported during writing the image on my notebook was in range of megabytes, though not the expected speed of the SD card under streaming write. Next I've tried the JEOS image, the messages were the same, but after some time (up to 10 minutes iirc) the yast first boot screen appeared and I've finished the installation. My conclusion was a slow sd card and the amount of data being read before the installation showed sign of progress. Doing a manual installation of the GUI took a lot of time so it kind of supported the conclusion. -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Hi, Le 17/06/2015 14:01, Edgar Dombrowski a écrit :
Hi Raspi-Friends.
First thanks to Alex, Freek et remerciements pour Guillaume.for indicating the Repos for the various files for the Raspi B and Raspi 2 and pointing out the different versionS JeoS; XCFE and LXQT.
I have downloaded the there xz.files and installed them on a sd-stick.
But when, I get the folowing messages:
Net: Net initialization skipped No ethernet found ---------> Cable was connected to an HDLC-Router hit any key to stop autoboot: 2 > 1 > 0 switch to partitions #0: OK mmc0 is current device scanning mmc0:1... Found U-Boot script /boot.scr reading /boot.src 115 bytes read in 420 ms (0 Bytes/s) # executing script at 00000000 2708 bytes read in 420 ms (1000 Bytes/s) # executing script at 00000200 4389568 bytes read in 56550 ms (75.2 KiB/s)
No further reaction
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
Thanks for you assistance.
Edgar, DJ3PU, Munich
P.S. I am preparing an article to be included in Magazine of the German Amateur Radio Club (DARC) on implementing Ham Radio Programs into the Rasberry Pi, succeding up to today with Debian-Squeeze, but with OpenSUSE ???
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
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. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
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. 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. 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) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
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: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Le 18/06/2015 13:58, Guillaume Gardet a écrit :
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.
Finally I tested it, and it works just fine (initrd load speed is 5.9 MiB/s !). So, I updated our u-boot packages and we must wait that it reaches Factory. See: https://build.opensuse.org/request/show/312513 Guillaume
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: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (5)
-
David Sterba -
Edgar Dombrowski -
Fabian Vogt -
Freek de Kruijf -
Guillaume Gardet