Am 06.03.2015 um 18:13 schrieb Dirk Müller:
Am 06.03.2015 17:54 schrieb "Jimmy PIERRE" <jimmypierre.rouen.france@gmail.com mailto:jimmypierre.rouen.france@gmail.com>:
On 1 March 2015 at 00:39, Andreas Färber <afaerber@suse.de
mailto:afaerber@suse.de> wrote:
Am 24.02.2015 um 22:57 schrieb Dirk Müller:
Hi,
There's a v3 patchset on the u-boot mailing list, but that's
surely not
yet in our Base:System u-boot package. You'd need a u-boot-rpi2
Contrib
package with those patches applied to create an image.
The u-boot patches are actually in git already
Indeed they were applied Feb 22, but on Feb 21 weren't yet. :)
Cheers, Andreas
and will be in the next stable release then, so that part i
Greetings, Hallo,
Tell me, is it the place to find the .img please:
http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Rasp...
Yes, it will be the right place (or rather a newly created images subdir) once it built.
No, Kiwi images would not go into standard but into images. And that folder does not exist today.
Regards, Andreas
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-rp... 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@suse.de:
Am 06.03.2015 um 18:13 schrieb Dirk Müller:
Am 06.03.2015 17:54 schrieb "Jimmy PIERRE" <jimmypierre.rouen.france@gmail.com mailto:jimmypierre.rouen.france@gmail.com>:
On 1 March 2015 at 00:39, Andreas Färber <afaerber@suse.de
mailto:afaerber@suse.de> wrote:
Am 24.02.2015 um 22:57 schrieb Dirk Müller:
Hi,
There's a v3 patchset on the u-boot mailing list, but that's
surely not
yet in our Base:System u-boot package. You'd need a u-boot-rpi2
Contrib
package with those patches applied to create an image.
The u-boot patches are actually in git already
Indeed they were applied Feb 22, but on Feb 21 weren't yet. :)
Cheers, Andreas
and will be in the next stable release then, so that part i
Greetings, Hallo,
Tell me, is it the place to find the .img please:
http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Rasp...
Yes, it will be the right place (or rather a newly created images subdir) once it built.
No, Kiwi images would not go into standard but into images. And that folder does not exist today.
Regards, Andreas
-- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton; HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
-----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-rp... 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@suse.de:
Am 06.03.2015 um 18:13 schrieb Dirk Müller:
Am 06.03.2015 17:54 schrieb "Jimmy PIERRE" <jimmypierre.rouen.france@gmail.com mailto:jimmypierre.rouen.france@gmail.com>:
On 1 March 2015 at 00:39, Andreas Färber <afaerber@suse.de
mailto:afaerber@suse.de> wrote:
Am 24.02.2015 um 22:57 schrieb Dirk Müller:
Hi,
There's a v3 patchset on the u-boot mailing list, but that's
surely not
yet in our Base:System u-boot package. You'd need a u-boot-rpi2
Contrib
package with those patches applied to create an image.
The u-boot patches are actually in git already
Indeed they were applied Feb 22, but on Feb 21 weren't yet. :)
Cheers, Andreas
and will be in the next stable release then, so that part i
Greetings, Hallo,
Tell me, is it the place to find the .img please:
http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contri b:/RaspberryPi2/standard/armv7hl/
Yes, it will be the right place (or rather a newly created images subdir) once it built.
No, Kiwi images would not go into standard but into images. And that folder does not exist today.
Regards, Andreas
-- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton; HRB 21284 (AG Nürnberg) --
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
Hi Jimmy,
Kindly let us have a quick "to do" to get all (or part) running on a Pi 2 :)
There should be a working image fairly soon here:
http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Rasp...
Greetings, Dirk
Dirk Müller wrote:
Kindly let us have a quick "to do" to get all (or part) running on a Pi 2 :)
There should be a working image fairly soon here:
http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Rasp...
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.
Hi Michael,
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.
Can you point me to the issue that you're hitting? Perhaps I can help (although I don't own a RPi 1).
Greetings, Dirk
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.
Can you point me to the issue that you're hitting? Perhaps I can help (although I don't own a RPi 1).
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.
Op zondag 29 maart 2015 19:45:29 schreef Dirk Müller:
Hi Jimmy,
Kindly let us have a quick "to do" to get all (or part) running on a Pi 2 :)
There should be a working image fairly soon here:
http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Rasp berryPi2/images/
I tried that image headless on my Raspberry Pi 2B, but it I do not get a working Ethernet connection. After the first boot and waiting about 15 minutes, there is nothing in /var/log/journal. Do I need to have a display and keyboard connected?
Hi Freek,
http://download.opensuse.org/repositories/devel:/ARM:/Factory:/Contrib:/Rasp berryPi2/images/
I tried that image headless on my Raspberry Pi 2B
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
Op maandag 30 maart 2015 23:27:19 schreef Dirk Müller:
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 used the one without a build number, which did not work. However the 285 did work and I could ssh into that system and configure things. Will continue tomorrow. Thanks!!!
Op dinsdag 31 maart 2015 01:09:48 schreef Freek de Kruijf:
Op maandag 30 maart 2015 23:27:19 schreef Dirk Müller:
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 used the one without a build number, which did not work. However the 285 did work and I could ssh into that system and configure things. Will continue tomorrow. Thanks!!!
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.
Op dinsdag 31 maart 2015 15:12:53 schreef Freek de Kruijf:
Op dinsdag 31 maart 2015 01:09:48 schreef Freek de Kruijf:
Op maandag 30 maart 2015 23:27:19 schreef Dirk Müller:
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 used the one without a build number, which did not work. However the 285 did work and I could ssh into that system and configure things. Will continue tomorrow. Thanks!!!
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.
Not only the shutdown left an unbootable system, also taking off the power and plugging the power in does not start the system again.
I connected the device with a HDMI display. Starting with a freshly written SD card shows some messages on the screen and finally 4 logos of Raspberry Pi with underneath the message about the system and kernel and a login prompt on tty1. Unplugging the power and plugging it in again, does not produce any video output to the HDMI screen again.
Is there anyway I can help?
Hi Freek,
Not only the shutdown left an unbootable system, also taking off the power and plugging the power in does not start the system again.
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..
Is there anyway I can help?
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
Op dinsdag 31 maart 2015 21:12:53 schreef Dirk Müller:
Hi Freek,
Not only the shutdown left an unbootable system, also taking off the power and plugging the power in does not start the system again.
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..
Is there anyway I can help?
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.
I studied on the BOOT disk the file boot.script and found in the value for bootargs the parameter disk=/dev/disk/by-id/mmc-00000_0x1537043d . I have the feeling there should be -part? appended, where ? should be 2 or 3. Both root= and resume= have -part3. respectively -part4 appended.
Hi Freek,
I studied on the BOOT disk the file boot.script and found in the value for bootargs the parameter disk=/dev/disk/by-id/mmc-00000_0x1537043d . I have the feeling there should be -part? appended, where ? should be 2 or 3. Both root= and resume= have -part3. respectively -part4 appended.
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 :-/
Hi Freek,
I studied on the BOOT disk the file boot.script and found in the value for bootargs the parameter disk=/dev/disk/by-id/mmc-00000_0x1537043d . I have the feeling there should be -part? appended, where ? should be 2 or 3. Both root= and resume= have -part3. respectively -part4 appended.
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 :-/
Op vrijdag 3 april 2015 00:34:06 schreef u:
The fix is to restore that on first boot, so when you log in the first time, run this:
echo "rh 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 :-/
Indeed this works. I now have a bootable RPi2 system. Thanks very much!!!
Hi,
Indeed this works. I now have a bootable RPi2 system. Thanks very much!!!
I've added two more fixes for sound and repairing the hybrid MBR, so one of the next images should work just fine (currently waiting for building/publishing, something seems to broken in OBS right now..)
-
Andreas Färber -
Dirk Müller -
Freek de Kruijf -
jimmypierre.rouen.france＠gmail.com -
Josua Mayer -
Michael Ströder