-----Original Message----- From: Josua Mayer [mailto:josua.mayer97@gmail.com] Sent: 19 March 2015 10:42 To: openSUSE ARM ML Subject: Re: [opensuse-arm] openSUSE ARM img compatible with Raspberry Pi 2 Hi everybody, since apparently the showstopper right now is a kernel package, I decided to quickly make one, based on my original cubox-i kernel package (this way it has been quick and easy). Please have a look at https://build.opensuse.org/package/show/home:mayerjosua:Chromebook/kernel-r… and use it if it works. I tried to document the spec-file well to ease future maintenance. The only missing feature is a proper kernel-source package to build modules against. I dont have an rpi2 to test with so this is as far as I can go. 2015-03-07 1:14 GMT+08:00 Andreas Färber <afaerber(a)suse.de>de>: Greetings, Kindly let us have a quick "to do" to get all (or part) running on a Pi 2 :) I have had not much luck with openSUSE but others work immediately (download, write to SD) except some tweaking for wi-fi etc. Have a great Sunday! Keep it up ;-) Jimmy nui.fr -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

Dirk Müller wrote: And how about the rasperry pi #1? Will the image also be fixed? I can't help with kernel problems. But I can test stuff. Ciao, Michael.

Dirk Müller wrote: Mail thread started here: http://lists.opensuse.org/opensuse-arm/2015-03/msg00005.html Currently I've blocked the kernel update on my four rasperry pis 1 running openSUSE Factory_ARM. Thanks in advance for looking into it. Ciao, Michael.

Hi Freek, Please try again (Build 285 or newer). I've not been able to test ethernet yet as I don't have ethernet while having time for hacking the device, but it boots up properly for me on serial console and I can login. I can see the 1GB RAM, 4 CPUs and eth0 which is in dhcp wait, so it doesn't look too bad. I don't have display or keyboard connected. one thing that is broken right now is soft reboot :/ Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

Op dinsdag 31 maart 2015 01:09:48 schreef Freek de Kruijf: I did a "shutdown -P now" and also "shutdown -r now", which left an unbootable system behind. So I had to start all over again. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

Hi Freek, yes, the kiwi firstboot somehow wrecks the firmware, so a 2nd boot fails. I currently think it is the resizing during initial boot, but it could be also something else.. Figure out what the bug is and how to fix it :-) I'm looking as astonished as you are. if you have any hint on what might go wrong, let me know. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

Hi Freek, The disk parameter should be the disk, thats the root= parameter that needs the partition added. Anyway, the issue is way simpler. the Kiwi initrd destroys the hybrid GPT on resize, which causes the raspberry pi firmware failing to find the u-boot bootloader. The fix is to restore that on first boot, so when you log in the first time, run this: echo "r h 1 2 3 n c y 82 n 83 n w y" | \ /usr/sbin/gdisk /dev/mmcblk0 I'm trying to add that as a workaround to the image. Ideally there would be some feature in kiwi to do that :-/ -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org

Op vrijdag 3 april 2015 00:34:06 schreef u: Indeed this works. I now have a bootable RPi2 system. Thanks very much!!! -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org