Re: [opensuse-arm] Image repos needs cleanup
Le 28/05/2015 15:55, Guillaume Gardet a écrit : Le 28/05/2015 15:52, Ludwig Nussel a écrit : Guillaume Gardet wrote: in http://download.opensuse.org/ports/armv7hl/factory/images/ we need to remove all *Factory* images since they have been renamed *Tumbleweed*. armv7 is not Tumbleweed. It really is Factory, ie the untested base of Tumbleweed. Some times ago, I have been told that for armv7 what is published _is_ Tumbleweed. ^^ Nevertheless, images have been renamed. So, there are old images named Factory and newer images named Tumblewwed in the same images repo. Repo still needs cleanup. :( Guillaume Guillaume cu Ludwig -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Image repos needs cleanup
Hi Guillaume, > Repo still needs cleanup. :( I know. I've mailed the OBS admins and still have not gotten a reply :-( Pinging again.. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Problem using YaST because rebuild of ruby packet is blocked by boost library
Op zaterdag 6 juni 2015 22:59:28 schreef Dirk Müller: > Hi Freek, > > > I tried to find the project on build.opensuse.org that builds > > libstorage-ruby, but could not find it. > > its a subpackage of libstorage: > > https://build.opensuse.org/package/show/openSUSE:Factory:ARM/libstorage > > Greetings, > Dirk Using this information and copying the .spec and tar file and using rpmbuild on both my RPi2B and RPi1B I succeeded in building the newest versions of the libstorage rpms. I tested these with "yast network" and now this works OK. -- 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] Factory: boot.scr not updated
Le 07/06/2015 22:31, Frank Kunz a écrit : Hi, also with new builds from today the situation is still the same. it seems that all sunxi based board images are broken. I tried to find out what is wrong but up to now without success. 'Old' images with kernel 3.19 (Factory) still work. Could you give us the kiwi version from working image, please? Guillaume Br, Frank -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Factory: boot.scr not updated
Le 28/05/2015 16:32, Guillaume Gardet a écrit : Hi, after testing some factory images, it appears that boot.scr/boot.script are not updated, so board is unbootable after first boot. Anything changed in config or kiwi? Marcus, it seems that kiwi does not run our u-boot hook (setupUBoot.sh) which is in /kiwi-hooks/ because test if file exists fails whereas it is there. :( boot.kiwi log: ** ++ local 'IFS= ' ++ '[' '!' -z '' ']' ++ export eval KIWI_ALLOW_HOOK_CMD_setupUBoot=0 ++ KIWI_ALLOW_HOOK_CMD_setupUBoot=0 ++ HOOK=/kiwi-hooks/setupUBoot.sh ++ '[' '!' -e /kiwi-hooks/setupUBoot.sh ']' ++ HOOK=/lib/kiwi/hooks/setupUBoot.sh ++ '[' -e /lib/kiwi/hooks/setupUBoot.sh ']' ++ '[' '!' -z '' ']' ++ eval local 'call_cmd=$KIWI_ALLOW_HOOK_CMD_setupUBoot' +++ local call_cmd=0 ** How could we debug this? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Factory: boot.scr not updated
Le 08/06/2015 11:43, Guillaume Gardet a écrit : Le 28/05/2015 16:32, Guillaume Gardet a écrit : Hi, after testing some factory images, it appears that boot.scr/boot.script are not updated, so board is unbootable after first boot. Anything changed in config or kiwi? Marcus, it seems that kiwi does not run our u-boot hook (setupUBoot.sh) which is in /kiwi-hooks/ because test if file exists fails whereas it is there. :( boot.kiwi log: ** ++ local 'IFS= ' ++ '[' '!' -z '' ']' ++ export eval KIWI_ALLOW_HOOK_CMD_setupUBoot=0 ++ KIWI_ALLOW_HOOK_CMD_setupUBoot=0 ++ HOOK=/kiwi-hooks/setupUBoot.sh Marcus, should not we look for /mnt/kiwi-hooks/setupUBoot.sh since at this moment, partition is mounted on /mnt ? Guillaume ++ '[' '!' -e /kiwi-hooks/setupUBoot.sh ']' ++ HOOK=/lib/kiwi/hooks/setupUBoot.sh ++ '[' -e /lib/kiwi/hooks/setupUBoot.sh ']' ++ '[' '!' -z '' ']' ++ eval local 'call_cmd=$KIWI_ALLOW_HOOK_CMD_setupUBoot' +++ local call_cmd=0 ** How could we debug this? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Factory: boot.scr not updated
Le 08/06/2015 11:54, Guillaume Gardet a écrit : Le 08/06/2015 11:43, Guillaume Gardet a écrit : Le 28/05/2015 16:32, Guillaume Gardet a écrit : Hi, after testing some factory images, it appears that boot.scr/boot.script are not updated, so board is unbootable after first boot. Anything changed in config or kiwi? Marcus, it seems that kiwi does not run our u-boot hook (setupUBoot.sh) which is in /kiwi-hooks/ because test if file exists fails whereas it is there. :( boot.kiwi log: ** ++ local 'IFS= ' ++ '[' '!' -z '' ']' ++ export eval KIWI_ALLOW_HOOK_CMD_setupUBoot=0 ++ KIWI_ALLOW_HOOK_CMD_setupUBoot=0 ++ HOOK=/kiwi-hooks/setupUBoot.sh Marcus, should not we look for /mnt/kiwi-hooks/setupUBoot.sh since at this moment, partition is mounted on /mnt ? I will send a patch to fix this later today. Guillaume Guillaume ++ '[' '!' -e /kiwi-hooks/setupUBoot.sh ']' ++ HOOK=/lib/kiwi/hooks/setupUBoot.sh ++ '[' -e /lib/kiwi/hooks/setupUBoot.sh ']' ++ '[' '!' -z '' ']' ++ eval local 'call_cmd=$KIWI_ALLOW_HOOK_CMD_setupUBoot' +++ local call_cmd=0 ** How could we debug this? Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Factory: boot.scr not updated
Le 08/06/2015 12:10, Marcus Schäfer a écrit : Hi, Marcus, should not we look for /mnt/kiwi-hooks/setupUBoot.sh since at this moment, partition is mounted on /mnt ? no hook scripts are embedded into the initrd, and if not actively removed (e.g via config.sh) they are also available in the later system for reference. Most people use an init/systemd script to remove them on first boot though because they are not really needed at that stage anymore Ok, so, I will check if it is in the initrd. Guillaume Regards, Marcus -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Factory: boot.scr not updated
Le 08/06/2015 12:06, Marcus Schäfer a écrit : Hi, Le 28/05/2015 16:32, Guillaume Gardet a écrit : Hi, after testing some factory images, it appears that boot.scr/boot.script are not updated, so board is unbootable after first boot. Anything changed in config or kiwi? Marcus, it seems that kiwi does not run our u-boot hook (setupUBoot.sh) which is in /kiwi-hooks/ because test if file exists fails whereas it is there. :( boot.kiwi log: ** ++ local 'IFS= ' ++ '[' '!' -z '' ']' ++ export eval KIWI_ALLOW_HOOK_CMD_setupUBoot=0 ++ KIWI_ALLOW_HOOK_CMD_setupUBoot=0 ++ HOOK=/kiwi-hooks/setupUBoot.sh ++ '[' '!' -e /kiwi-hooks/setupUBoot.sh ']' ++ HOOK=/lib/kiwi/hooks/setupUBoot.sh ++ '[' -e /lib/kiwi/hooks/setupUBoot.sh ']' ++ '[' '!' -z '' ']' ++ eval local 'call_cmd=$KIWI_ALLOW_HOOK_CMD_setupUBoot' +++ local call_cmd=0 ** How could we debug this? Check the initrd if the script is really included gzip -cd | cpio -it | grep setupUBoot.sh It is in uImage format, so we need to remove headers before extract it with: sudo tail -c+65 < initrd.uboot | gunzip > /tmp/out gzip -cd /tmp/out | cpio -it | grep setupUBoot.sh which returns: kiwi-hooks/setupUBoot.sh 265320 blocs So, it is here... Guillaume If it does not exist at all check if the tarball providing the script(s) is bootincluded Next check if the archive bundled the scripts correctly, should look like this: tar -tf foo.tgz kiwi-hooks/ kiwi-hooks/setupUBoot.sh If all that matches check the kiwi build log if you can see the "Installing archives" log information Regards, Marcus -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Factory: boot.scr not updated
Le 08/06/2015 12:24, Guillaume Gardet a écrit : Le 08/06/2015 12:06, Marcus Schäfer a écrit : Hi, Le 28/05/2015 16:32, Guillaume Gardet a écrit : Hi, after testing some factory images, it appears that boot.scr/boot.script are not updated, so board is unbootable after first boot. Anything changed in config or kiwi? Marcus, it seems that kiwi does not run our u-boot hook (setupUBoot.sh) which is in /kiwi-hooks/ because test if file exists fails whereas it is there. :( boot.kiwi log: ** ++ local 'IFS= ' ++ '[' '!' -z '' ']' ++ export eval KIWI_ALLOW_HOOK_CMD_setupUBoot=0 ++ KIWI_ALLOW_HOOK_CMD_setupUBoot=0 ++ HOOK=/kiwi-hooks/setupUBoot.sh ++ '[' '!' -e /kiwi-hooks/setupUBoot.sh ']' ++ HOOK=/lib/kiwi/hooks/setupUBoot.sh ++ '[' -e /lib/kiwi/hooks/setupUBoot.sh ']' ++ '[' '!' -z '' ']' ++ eval local 'call_cmd=$KIWI_ALLOW_HOOK_CMD_setupUBoot' +++ local call_cmd=0 ** How could we debug this? Check the initrd if the script is really included gzip -cd | cpio -it | grep setupUBoot.sh It is in uImage format, so we need to remove headers before extract it with: sudo tail -c+65 < initrd.uboot | gunzip > /tmp/out gzip -cd /tmp/out | cpio -it | grep setupUBoot.sh which returns: kiwi-hooks/setupUBoot.sh 265320 blocs So, it is here... Moreover, second script installUBoot.sh is executed (but it is a bit later). Full boot.kiwi log is there: http://paste.opensuse.org/90335031 Guillaume Guillaume If it does not exist at all check if the tarball providing the script(s) is bootincluded Next check if the archive bundled the scripts correctly, should look like this: tar -tf foo.tgz kiwi-hooks/ kiwi-hooks/setupUBoot.sh If all that matches check the kiwi build log if you can see the "Installing archives" log information Regards, Marcus -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Factory: boot.scr not updated
Hi, > Le 28/05/2015 16:32, Guillaume Gardet a écrit : > >Hi, > > > >after testing some factory images, it appears that boot.scr/boot.script are > >not updated, so board is unbootable after first boot. > > > >Anything changed in config or kiwi? > > Marcus, it seems that kiwi does not run our u-boot hook (setupUBoot.sh) which > is in /kiwi-hooks/ because test if file exists fails whereas it is there. :( > > boot.kiwi log: > ** > ++ local 'IFS= > ' > ++ '[' '!' -z '' ']' > ++ export eval KIWI_ALLOW_HOOK_CMD_setupUBoot=0 > ++ KIWI_ALLOW_HOOK_CMD_setupUBoot=0 > ++ HOOK=/kiwi-hooks/setupUBoot.sh > ++ '[' '!' -e /kiwi-hooks/setupUBoot.sh ']' > ++ HOOK=/lib/kiwi/hooks/setupUBoot.sh > ++ '[' -e /lib/kiwi/hooks/setupUBoot.sh ']' > ++ '[' '!' -z '' ']' > ++ eval local 'call_cmd=$KIWI_ALLOW_HOOK_CMD_setupUBoot' > +++ local call_cmd=0 > ** > > How could we debug this? Check the initrd if the script is really included gzip -cd | cpio -it | grep setupUBoot.sh If it does not exist at all check if the tarball providing the script(s) is bootincluded Next check if the archive bundled the scripts correctly, should look like this: tar -tf foo.tgz kiwi-hooks/ kiwi-hooks/setupUBoot.sh If all that matches check the kiwi build log if you can see the "Installing archives" log information Regards, Marcus -- Public Key available via: https://keybase.io keybase search marcus_schaefer --- Marcus Schäfer (Res. & Dev.) SUSE Linux GmbH Tel: 0911-740 53 0 Maxfeldstrasse 5 FAX: 0911-740 53 479 D-90409 Nürnberg HRB: 21284 (AG Nürnberg) Germany GF: Felix Imendörffer, Jane Smithard GF: Dilip Upmanyu, Graham Norton http://www.suse.de --- -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Factory: boot.scr not updated
Hi, > Marcus, should not we look for /mnt/kiwi-hooks/setupUBoot.sh since at this > moment, partition is mounted on /mnt ? no hook scripts are embedded into the initrd, and if not actively removed (e.g via config.sh) they are also available in the later system for reference. Most people use an init/systemd script to remove them on first boot though because they are not really needed at that stage anymore Regards, Marcus -- Public Key available via: https://keybase.io keybase search marcus_schaefer --- Marcus Schäfer (Res. & Dev.) SUSE Linux GmbH Tel: 0911-740 53 0 Maxfeldstrasse 5 FAX: 0911-740 53 479 D-90409 Nürnberg HRB: 21284 (AG Nürnberg) Germany GF: Felix Imendörffer, Jane Smithard GF: Dilip Upmanyu, Graham Norton http://www.suse.de --- -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Factory: boot.scr not updated
Le 08/06/2015 12:40, Guillaume Gardet a écrit : Le 08/06/2015 12:24, Guillaume Gardet a écrit : Le 08/06/2015 12:06, Marcus Schäfer a écrit : Hi, Le 28/05/2015 16:32, Guillaume Gardet a écrit : Hi, after testing some factory images, it appears that boot.scr/boot.script are not updated, so board is unbootable after first boot. Anything changed in config or kiwi? Marcus, it seems that kiwi does not run our u-boot hook (setupUBoot.sh) which is in /kiwi-hooks/ because test if file exists fails whereas it is there. :( boot.kiwi log: ** ++ local 'IFS= ' ++ '[' '!' -z '' ']' ++ export eval KIWI_ALLOW_HOOK_CMD_setupUBoot=0 ++ KIWI_ALLOW_HOOK_CMD_setupUBoot=0 ++ HOOK=/kiwi-hooks/setupUBoot.sh ++ '[' '!' -e /kiwi-hooks/setupUBoot.sh ']' ++ HOOK=/lib/kiwi/hooks/setupUBoot.sh ++ '[' -e /lib/kiwi/hooks/setupUBoot.sh ']' ++ '[' '!' -z '' ']' ++ eval local 'call_cmd=$KIWI_ALLOW_HOOK_CMD_setupUBoot' +++ local call_cmd=0 ** How could we debug this? Check the initrd if the script is really included gzip -cd | cpio -it | grep setupUBoot.sh It is in uImage format, so we need to remove headers before extract it with: sudo tail -c+65 < initrd.uboot | gunzip > /tmp/out gzip -cd /tmp/out | cpio -it | grep setupUBoot.sh which returns: kiwi-hooks/setupUBoot.sh 265320 blocs So, it is here... Moreover, second script installUBoot.sh is executed (but it is a bit later). Full boot.kiwi log is there: http://paste.opensuse.org/90335031 I just rechecked and it seems that there is no /kiwi-hooks/ at all in initrd (seems I had a look at a previous initrd extraction, sorry) BUT installUBoot.sh is called. So, I guess this is from /kiwi-hooks/ from SD card. Guillaume Guillaume If it does not exist at all check if the tarball providing the script(s) is bootincluded Yes : Next check if the archive bundled the scripts correctly, should look like this: tar -tf foo.tgz kiwi-hooks/ kiwi-hooks/setupUBoot.sh tar -tf uboot-setup-beaglebone.tgz kiwi-hooks/ kiwi-hooks/installUBoot.sh kiwi-hooks/setupUBoot.sh If all that matches check the kiwi build log if you can see the "Installing archives" log information Build log is here: https://build.opensuse.org/build/openSUSE:Factory:ARM/factory/armv7l/JeOS-beaglebone/_log I can see: [ 253s] Jun-07 19:57:50 <1> : Installing raw archives in: /usr/src/packages/KIWIROOT-oem... [ 253s] Jun-07 19:57:50 <1> : EXEC [chmod 755 /usr/src/packages/KIWIROOT-oem/screenrc.smart] [ 254s] + export PBL_SKIP_BOOT_TEST=1 [ 254s] + PBL_SKIP_BOOT_TEST=1 [ 254s] + trap clean INT TERM [ 254s] + for i in uboot-setup-beaglebone.tgz [ 254s] + grep -v '/$' [ 254s] + tar -tf /usr/src/packages/SOURCES/uboot-setup-beaglebone.tgz [ 254s] + for i in uboot-setup-beaglebone.tgz [ 254s] + tar -C /usr/src/packages/KIWIROOT-oem -xvf /usr/src/packages/SOURCES/uboot-setup-beaglebone.tgz [ 254s] kiwi-hooks/ [ 254s] kiwi-hooks/installUBoot.sh [ 254s] kiwi-hooks/setupUBoot.sh [ 254s] + echo 0 [ 254s] + exit 0 And: [ 285s] Jun-07 19:58:22 <1> : Reading contents of bootincluded packages/archives [ 285s] Jun-07 19:58:22 <1> : EXEC [rpm --root /usr/src/packages/KIWIROOT-oem -ql "dtb-am335x" 2>&1] [ 285s] Jun-07 19:58:22 <1> : --> got list from dtb-am335x [ 285s] Jun-07 19:58:22 <1> : EXEC [rpm --root /usr/src/packages/KIWIROOT-oem -ql "kernel-default" 2>&1] [ 286s] Jun-07 19:58:22 <1> : --> got list from kernel-default [ 286s] Jun-07 19:58:22 <1> : EXEC [rpm --root /usr/src/packages/KIWIROOT-oem -ql "u-boot-am335xevm" 2>&1] [ 286s] Jun-07 19:58:23 <1> : --> got list from u-boot-am335xevm [ 286s] Jun-07 19:58:23 <1> : --> got list from bootincluded_archives.filelist [ 286s] Jun-07 19:58:23 <1> : Checking for tools in bootincluded contents to keep [ 286s] Jun-07 19:58:23 <1> : --> no tools to keep Does it help you to find the problem? Guillaume Regards, Marcus -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] Difference between Release supported platforms and Community supported platforms
Hi, On this page: https://en.opensuse.org/openSUSE:Supported_ARM_boards What is the difference between "Release supported platforms" and "Community supported platforms"? I though it was based on upstream/downstream kernel, but it seems I am wrong, or the list needs a big update. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Factory: boot.scr not updated
Le 08/06/2015 16:26, Marcus Schäfer a écrit : Hi, Full boot.kiwi log is there: http://paste.opensuse.org/90335031 There should be the message "Boot including archive(s) [bootstrap]: ..." But it's not there. However I can see the .kiwi file to have this archive boot included. Very strange. I'll test a local build Ok. Thanks for having a look at it. Looking forward to get (good) news from you. ;) Guillaume Regards, Marcus -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Difference between Release supported platforms and Community supported platforms
> Am 08.06.2015 um 16:28 schrieb Guillaume Gardet : > > Hi, > > On this page: https://en.opensuse.org/openSUSE:Supported_ARM_boards > > What is the difference between "Release supported platforms" and "Community > supported platforms"? It was "main repo" vs "Contrib" > > I though it was based on upstream/downstream kernel, but it seems I am wrong, > or the list needs a big update. There is a really good chance it does ;) Alex > > > > Guillaume > > -- > To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org > To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org > -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Difference between Release supported platforms and Community supported platforms
Le 08/06/2015 16:38, Alexander Graf a écrit : Am 08.06.2015 um 16:28 schrieb Guillaume Gardet : Hi, On this page: https://en.opensuse.org/openSUSE:Supported_ARM_boards What is the difference between "Release supported platforms" and "Community supported platforms"? It was "main repo" vs "Contrib" I though it was based on upstream/downstream kernel, but it seems I am wrong, or the list needs a big update. There is a really good chance it does ;) Ok, so I will clean it up. :) Guillaume Alex Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Factory: boot.scr not updated
Le 08/06/2015 17:03, Marcus Schäfer a écrit : Hi, Le 08/06/2015 16:26, Marcus Schäfer a écrit : Hi, Full boot.kiwi log is there: http://paste.opensuse.org/90335031 There should be the message "Boot including archive(s) [bootstrap]: ..." But it's not there. However I can see the .kiwi file to have this archive boot included. Very strange. I'll test a local build Ok. Thanks for having a look at it. Looking forward to get (good) news from you. ;) I found the bug in kiwi, not so good news, but I will fix it :-) It is still a good news. ;) new package submission will follow today... evening because I have another bug in the list which needs to be fixed Thanks and sorry for this one, it's a clear regression due to the changes in the handling Ok. Thanks for your fix. Guillaume Regards, Marcus -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
[opensuse-arm] Raspberry Pi 1 and GPT partition really booting?
Hi, I tested (hybrid) GPT partitionned images for Raspberry Pi and it does not boot at all (even the GPU firmware which is the 1st stage). Is there someone here who booted such an image? If so, which Pi version and which openSUSE image version? Otherwise, I would like to revert to FAT16 boot partition. Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Difference between Release supported platforms and Community supported platforms
Le 08/06/2015 16:44, Guillaume Gardet a écrit : Le 08/06/2015 16:38, Alexander Graf a écrit : Am 08.06.2015 um 16:28 schrieb Guillaume Gardet : Hi, On this page: https://en.opensuse.org/openSUSE:Supported_ARM_boards What is the difference between "Release supported platforms" and "Community supported platforms"? It was "main repo" vs "Contrib" I though it was based on upstream/downstream kernel, but it seems I am wrong, or the list needs a big update. There is a really good chance it does ;) Ok, so I will clean it up. :) I merged https://en.opensuse.org/Portal:ARM/GetARMed and https://en.opensuse.org/openSUSE:Supported_ARM_boards (1st part). Could you please review/edit this page: https://en.opensuse.org/Portal:ARM/GetARMed Guillaume -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Raspberry Pi 1 and GPT partition really booting?
> Am 08.06.2015 um 17:56 schrieb Guillaume Gardet : > > Hi, > > I tested (hybrid) GPT partitionned images for Raspberry Pi and it does not > boot at all (even the GPU firmware which is the 1st stage). > > Is there someone here who booted such an image? If so, which Pi version and > which openSUSE image version? > > Otherwise, I would like to revert to FAT16 boot partition. It has a FAT boot (gpu, uboot) partition. And it did work for me on RPi1 and RPi2. I have already put both of them in persistent home automation use though, so I can't verify today's image ;) Alex > > > Guillaume > > -- > To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org > To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org > -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Factory: boot.scr not updated
Am 08.06.2015 um 11:36 schrieb Guillaume Gardet: > Could you give us the kiwi version from working image, please? That's what I found out of the image: kiwi_iversion='1.12.1' kiwi_revision='a1b5148889afb4530f8f202f4175f58e5c5bf171' Br, Frank -- To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org
Re: [opensuse-arm] Raspberry Pi 1 and GPT partition really booting?
Op maandag 8 juni 2015 20:29:02 schreef Alexander Graf: > > Am 08.06.2015 um 17:56 schrieb Guillaume Gardet > > : > > > > Hi, > > > > I tested (hybrid) GPT partitionned images for Raspberry Pi and it does not > > boot at all (even the GPU firmware which is the 1st stage). > > > > Is there someone here who booted such an image? If so, which Pi version > > and which openSUSE image version? > > > > Otherwise, I would like to revert to FAT16 boot partition. > > It has a FAT boot (gpu, uboot) partition. And it did work for me on RPi1 and > RPi2. I have already put both of them in persistent home automation use > though, so I can't verify today's image ;) > > Alex > > > Guillaume I have both Tumbleweed for RPi1B and RPi2B working on both of my RPi's. But I used older images to start and have, in the meantime, updated these systems using "zypper up". However yast is not usable because libstorage-ruby is for Ruby 2.1 where yast needs 2.2. I succeeded in generating this library for both systems. -- 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
