[opensuse-arm] Newest images for RPi1 and RPi2 are not usable headless
I tried Tumbleweed Build325.1 for RPi1 and Build314.1 for RPi2 in a headless situation, but both do do not end with an active Ethernet connection. Is this to be expected? u-boot problem? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] RPi 2 XFCE image
Am Donnerstag, 18. Juni 2015, 13:20:42 schrieb David Byte: > In trying to chase down the issue on my RPi 2 and the graphics I > performed a zypper up (93 packages). After giving a serious wait (20 > minutes or so), I issued a reboot command. > > Now, the system will not boot. Thoughts? I had the same issue yesterday (it may be a different issue now, though): the new 3.18.14-1-rpi2 kernel does somehow lack support for the sdhci driver, so the SD card is not recognized anymore. Just change the symlinks in the second partition back to the old 3.18.9-3-rpi2 kernel and initrd and it should work again. -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] RPi 2 XFCE image
In trying to chase down the issue on my RPi 2 and the graphics I performed a zypper up (93 packages). After giving a serious wait (20 minutes or so), I issued a reboot command. Now, the system will not boot. Thoughts? -- David Byte Sr. Technology Strategist Alliances and Integrated Systems SUSE db...@suse.com (P)918.528.4422 www.suse.com -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] kernel 3.11.4 fails to build with gcc 5
Am Donnerstag, 18. Juni 2015, 19:24:07 schrieb Guillaume Gardet: > Hi, > > I updated kernel-raspberrypi config to get initrd support but it fails to > build with gcc 5. :( > > It is a kernel 3.11.4 where I added include/linux/compiler-gcc5.h > > Any idea how to fix it? > > https://build.opensuse.org/package/show/devel:ARM:Factory:Contrib:RaspberryPi/kernel-raspberrypi arch/arm/include/asm/glue-cache.h uses "extern inline", which won't work: https://gcc.gnu.org/gcc-5/porting_to.html It was changed to "static inline" in 76ae03828756bac2c1fa2c7eff7485e5f815dbdb Cheers, Fabian > Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] kernel 3.11.4 fails to build with gcc 5
Hi, I updated kernel-raspberrypi config to get initrd support but it fails to build with gcc 5. :( It is a kernel 3.11.4 where I added include/linux/compiler-gcc5.h Any idea how to fix it? https://build.opensuse.org/package/show/devel:ARM:Factory:Contrib:RaspberryPi/kernel-raspberrypi Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] R:R:I am Lost: No Boot
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+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] R:R:I am Lost: No Boot
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+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] R:R:I am Lost: No Boot
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+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
