[opensuse-arm] Contribute wih OpenSUSE for Raspberry Pi
Hello list, My name is Sergio Fernandez , I am personally interested in helping with the development of the image and OpenSuSE repositories for Raspberry Pi , since I have a project for a specialized desktop computer based on these two components. I have seen that there is only unofficial images for Raspberry Pi, by SuSE decisions. I've also seen that everything is a bit chaotic and therefore funny :) And I'd like to participate. I have several years administering Linux systems , I´m familiar with SuSE enterprise systems, and packaged for RPM distributions such as Mandriva and Mageia (and of course RHEL). Don't know how SUSE buildsystem works, but come with the intention to learn. I downloaded an image from Bernhard repository and I launched my Rpi. I've done some modifications and configurations and, works well . But I need more integration and stability and I want collaborate to do it for everyone. So where I can start? What to read , where to search ... Regards P.S.: Sorry for my English. Not so proper. -- ------------------------- Sergio Fernandez Cordero -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 12.12.2013, at 12:32, Sergio Fernández Cordero
Hello list,
My name is Sergio Fernandez , I am personally interested in helping with the development of the image and OpenSuSE repositories for Raspberry Pi , since I have a project for a specialized desktop computer based on these two components.
I have seen that there is only unofficial images for Raspberry Pi, by SuSE decisions. I've also seen that everything is a bit chaotic and therefore funny :) And I'd like to participate.
I have several years administering Linux systems , I´m familiar with SuSE enterprise systems, and packaged for RPM distributions such as Mandriva and Mageia (and of course RHEL). Don't know how SUSE buildsystem works, but come with the intention to learn.
I downloaded an image from Bernhard repository and I launched my Rpi. I've done some modifications and configurations and, works well . But I need more integration and stability and I want collaborate to do it for everyone.
So where I can start? What to read , where to search ...
The main reason we don't have an official Raspberry PI image today is that the build fails: https://build.opensuse.org/project/show/devel:ARM:13.1:Contrib:RaspberryPi The build fails because the kernel we're using inside the build VM doesn't have proper FAT support. There are 2 things to do here: 1) Try to build an image locally. Use "osc build" to build it on your existing RPi installation. Check whether the result actually works. 2) Enable proper vfat support for the guest kernel in our RPi build project. Adrian just introduced a feature this week that should make this possible. But it's not for the faint of heart yet :). Once we have those 2 pieces solved you should even be able to build your own customized image in OBS for the RPi. Oh, there is more to fix. When you look at the XFCE or E17 image, you will see that there are unresolvable packages. That's most likely because they simply haven't compiled. It would be good to find out why they don't compile, fix them and then somehow make them available to everyone (probably an overlay in the Ports repo plus a maintenance update).
Regards
P.S.: Sorry for my English. Not so proper.
Welcome on board :) Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am Donnerstag, 12. Dezember 2013, 14:03:14 schrieb Alexander Graf:
On 12.12.2013, at 12:32, Sergio Fernández Cordero
wrote: Hello list,
My name is Sergio Fernandez , I am personally interested in helping with the development of the image and OpenSuSE repositories for Raspberry Pi , since I have a project for a specialized desktop computer based on these two components.
I have seen that there is only unofficial images for Raspberry Pi, by SuSE decisions. I've also seen that everything is a bit chaotic and therefore funny :) And I'd like to participate.
I have several years administering Linux systems , I´m familiar with SuSE enterprise systems, and packaged for RPM distributions such as Mandriva and Mageia (and of course RHEL). Don't know how SUSE buildsystem works, but come with the intention to learn.
I downloaded an image from Bernhard repository and I launched my Rpi. I've done some modifications and configurations and, works well . But I need more integration and stability and I want collaborate to do it for everyone.
So where I can start? What to read , where to search ...
The main reason we don't have an official Raspberry PI image today is that the build fails:
https://build.opensuse.org/project/show/devel:ARM:13.1:Contrib:RaspberryPi
The build fails because the kernel we're using inside the build VM doesn't have proper FAT support. There are 2 things to do here:
btw, I added lately support to run distro kernel and initrd's. So such things can be added now in projects. You may just try to aggregate the (x86_64) kernel package from home:adrianSuSE kernel-obs-build package and add the following line prjconf to use that kernel: VMInstall: kernel-obs-build Make sure to ExportFilter this also to your arm architecture repos. shall I try to adapte this project to validate if it works? -- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
On 12.12.2013, at 14:41, Adrian Schröter
Am Donnerstag, 12. Dezember 2013, 14:03:14 schrieb Alexander Graf:
On 12.12.2013, at 12:32, Sergio Fernández Cordero
wrote: Hello list,
My name is Sergio Fernandez , I am personally interested in helping with the development of the image and OpenSuSE repositories for Raspberry Pi , since I have a project for a specialized desktop computer based on these two components.
I have seen that there is only unofficial images for Raspberry Pi, by SuSE decisions. I've also seen that everything is a bit chaotic and therefore funny :) And I'd like to participate.
I have several years administering Linux systems , I´m familiar with SuSE enterprise systems, and packaged for RPM distributions such as Mandriva and Mageia (and of course RHEL). Don't know how SUSE buildsystem works, but come with the intention to learn.
I downloaded an image from Bernhard repository and I launched my Rpi. I've done some modifications and configurations and, works well . But I need more integration and stability and I want collaborate to do it for everyone.
So where I can start? What to read , where to search ...
The main reason we don't have an official Raspberry PI image today is that the build fails:
https://build.opensuse.org/project/show/devel:ARM:13.1:Contrib:RaspberryPi
The build fails because the kernel we're using inside the build VM doesn't have proper FAT support. There are 2 things to do here:
btw, I added lately support to run distro kernel and initrd's. So such things can be added now in projects.
You may just try to aggregate the (x86_64) kernel package from
home:adrianSuSE kernel-obs-build
package and add the following line prjconf to use that kernel:
VMInstall: kernel-obs-build
Make sure to ExportFilter this also to your arm architecture repos.
shall I try to adapte this project to validate if it works?
We also need to force the codepage modules into the initrd so that it automatically loads them on boot (via -m). But yes, please :). Alex -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am Donnerstag, 12. Dezember 2013, 14:47:57 schrieb Alexander Graf:
On 12.12.2013, at 14:41, Adrian Schröter
wrote: Am Donnerstag, 12. Dezember 2013, 14:03:14 schrieb Alexander Graf:
On 12.12.2013, at 12:32, Sergio Fernández Cordero
wrote:
...
The main reason we don't have an official Raspberry PI image today is that the build fails:
https://build.opensuse.org/project/show/devel:ARM:13.1:Contrib:RaspberryPi
The build fails because the kernel we're using inside the build VM doesn't have proper FAT support. There are 2 things to do here:
btw, I added lately support to run distro kernel and initrd's. So such things can be added now in projects.
You may just try to aggregate the (x86_64) kernel package from
home:adrianSuSE kernel-obs-build
package and add the following line prjconf to use that kernel:
VMInstall: kernel-obs-build
Make sure to ExportFilter this also to your arm architecture repos.
shall I try to adapte this project to validate if it works?
We also need to force the codepage modules into the initrd so that it automatically loads them on boot (via -m). But yes, please :).
yes, it is already added there. It is setup in the project now, but no build starts, because of dependency issues in openSUSE:Factory:ARM atm. tryed to solve some by manually triggering rebuilds, but we may should do a clean build in any case ... -- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Le 12/12/2013 14:58, Adrian Schröter a écrit :
Am Donnerstag, 12. Dezember 2013, 14:47:57 schrieb Alexander Graf:
On 12.12.2013, at 14:41, Adrian Schröter
wrote: Am Donnerstag, 12. Dezember 2013, 14:03:14 schrieb Alexander Graf:
On 12.12.2013, at 12:32, Sergio Fernández Cordero
wrote: ...
The main reason we don't have an official Raspberry PI image today is that the build fails:
https://build.opensuse.org/project/show/devel:ARM:13.1:Contrib:RaspberryPi
The build fails because the kernel we're using inside the build VM doesn't have proper FAT support. There are 2 things to do here: btw, I added lately support to run distro kernel and initrd's. So such things can be added now in projects.
You may just try to aggregate the (x86_64) kernel package from
home:adrianSuSE kernel-obs-build
package and add the following line prjconf to use that kernel:
VMInstall: kernel-obs-build
Make sure to ExportFilter this also to your arm architecture repos.
shall I try to adapte this project to validate if it works? We also need to force the codepage modules into the initrd so that it automatically loads them on boot (via -m). But yes, please :). yes, it is already added there.
It is setup in the project now, but no build starts, because of dependency issues in openSUSE:Factory:ARM atm.
You could try to setup 13.1 repo instead: devel:ARM:13.1:Contrib:RaspberryPi Guillaume
tryed to solve some by manually triggering rebuilds, but we may should do a clean build in any case ...
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am Donnerstag, 12. Dezember 2013, 15:11:57 schrieb Guillaume Gardet:
Le 12/12/2013 14:58, Adrian Schröter a écrit :
Am Donnerstag, 12. Dezember 2013, 14:47:57 schrieb Alexander Graf:
On 12.12.2013, at 14:41, Adrian Schröter
wrote: Am Donnerstag, 12. Dezember 2013, 14:03:14 schrieb Alexander Graf:
On 12.12.2013, at 12:32, Sergio Fernández Cordero
wrote: ...
The main reason we don't have an official Raspberry PI image today is that the build fails:
https://build.opensuse.org/project/show/devel:ARM:13.1:Contrib:RaspberryPi
The build fails because the kernel we're using inside the build VM doesn't have proper FAT support. There are 2 things to do here: btw, I added lately support to run distro kernel and initrd's. So such things can be added now in projects.
You may just try to aggregate the (x86_64) kernel package from
home:adrianSuSE kernel-obs-build
package and add the following line prjconf to use that kernel:
VMInstall: kernel-obs-build
Make sure to ExportFilter this also to your arm architecture repos.
shall I try to adapte this project to validate if it works? We also need to force the codepage modules into the initrd so that it automatically loads them on boot (via -m). But yes, please :). yes, it is already added there.
It is setup in the project now, but no build starts, because of dependency issues in openSUSE:Factory:ARM atm.
You could try to setup 13.1 repo instead: devel:ARM:13.1:Contrib:RaspberryPi
okay, same applied there. (Check prjconf, the kernel-obs-build aggregate and the additional x86_64 arch in project setup, in case you want to see my changes). It is not a good idea to aggregate from my personal home project on the long run, but you may want to wait for a kernel-obs-build package in factory before you change that. In case you want to run local builds, you need a latest version "build" package, eg. from openSUSE:Tools project and you need to build with kvm or xen, eg: osc build --vm-type=kvm images armv6l otherwise the kernel and initrd will not be used. bye adrian -- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Strike! :) https://build.opensuse.org/package/show/devel:ARM:13.1:Contrib:RaspberryPi/J... happy testing! adrian PS: I noticed that the image name contains armv7l string, even though it is build with armv6 rpms. Am Donnerstag, 12. Dezember 2013, 15:38:18 schrieb Adrian Schröter:
Am Donnerstag, 12. Dezember 2013, 15:11:57 schrieb Guillaume Gardet:
Le 12/12/2013 14:58, Adrian Schröter a écrit :
Am Donnerstag, 12. Dezember 2013, 14:47:57 schrieb Alexander Graf:
On 12.12.2013, at 14:41, Adrian Schröter
wrote: Am Donnerstag, 12. Dezember 2013, 14:03:14 schrieb Alexander Graf:
On 12.12.2013, at 12:32, Sergio Fernández Cordero
wrote: ...
The main reason we don't have an official Raspberry PI image today is that the build fails:
https://build.opensuse.org/project/show/devel:ARM:13.1:Contrib:RaspberryPi
The build fails because the kernel we're using inside the build VM doesn't have proper FAT support. There are 2 things to do here: btw, I added lately support to run distro kernel and initrd's. So such things can be added now in projects.
You may just try to aggregate the (x86_64) kernel package from
home:adrianSuSE kernel-obs-build
package and add the following line prjconf to use that kernel:
VMInstall: kernel-obs-build
Make sure to ExportFilter this also to your arm architecture repos.
shall I try to adapte this project to validate if it works? We also need to force the codepage modules into the initrd so that it automatically loads them on boot (via -m). But yes, please :). yes, it is already added there.
It is setup in the project now, but no build starts, because of dependency issues in openSUSE:Factory:ARM atm.
You could try to setup 13.1 repo instead: devel:ARM:13.1:Contrib:RaspberryPi
okay, same applied there. (Check prjconf, the kernel-obs-build aggregate and the additional x86_64 arch in project setup, in case you want to see my changes).
It is not a good idea to aggregate from my personal home project on the long run, but you may want to wait for a kernel-obs-build package in factory before you change that.
In case you want to run local builds, you need a latest version "build" package, eg. from openSUSE:Tools project and you need to build with kvm or xen, eg:
osc build --vm-type=kvm images armv6l
otherwise the kernel and initrd will not be used.
bye adrian
-- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Thanks Adrian. It does build but it does not boot due to a known problem which should have been fixed by Marcus in kiwi. But, I will create another thread for that. Guillaume Le 12/12/2013 17:21, Adrian Schröter a écrit :
Strike! :)
https://build.opensuse.org/package/show/devel:ARM:13.1:Contrib:RaspberryPi/J...
happy testing! adrian
PS: I noticed that the image name contains armv7l string, even though it is build with armv6 rpms.
Am Donnerstag, 12. Dezember 2013, 15:38:18 schrieb Adrian Schröter:
Am Donnerstag, 12. Dezember 2013, 15:11:57 schrieb Guillaume Gardet:
Le 12/12/2013 14:58, Adrian Schröter a écrit :
Am Donnerstag, 12. Dezember 2013, 14:47:57 schrieb Alexander Graf:
On 12.12.2013, at 14:41, Adrian Schröter
wrote: Am Donnerstag, 12. Dezember 2013, 14:03:14 schrieb Alexander Graf: > On 12.12.2013, at 12:32, Sergio Fernández Cordero
wrote: > ... > The main reason we don't have an official Raspberry PI image today is that the build fails: > > https://build.opensuse.org/project/show/devel:ARM:13.1:Contrib:RaspberryPi > > The build fails because the kernel we're using inside the build VM doesn't have proper FAT support. There are 2 things to do here: btw, I added lately support to run distro kernel and initrd's. So such things can be added now in projects. You may just try to aggregate the (x86_64) kernel package from
home:adrianSuSE kernel-obs-build
package and add the following line prjconf to use that kernel:
VMInstall: kernel-obs-build
Make sure to ExportFilter this also to your arm architecture repos.
shall I try to adapte this project to validate if it works? We also need to force the codepage modules into the initrd so that it automatically loads them on boot (via -m). But yes, please :). yes, it is already added there.
It is setup in the project now, but no build starts, because of dependency issues in openSUSE:Factory:ARM atm. You could try to setup 13.1 repo instead: devel:ARM:13.1:Contrib:RaspberryPi okay, same applied there. (Check prjconf, the kernel-obs-build aggregate and the additional x86_64 arch in project setup, in case you want to see my changes).
It is not a good idea to aggregate from my personal home project on the long run, but you may want to wait for a kernel-obs-build package in factory before you change that.
In case you want to run local builds, you need a latest version "build" package, eg. from openSUSE:Tools project and you need to build with kvm or xen, eg:
osc build --vm-type=kvm images armv6l
otherwise the kernel and initrd will not be used.
bye adrian
-- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Thanks Alexander, I'll take a look at it. :) El 2013-12-12 14:03, Alexander Graf escribió:
On 12.12.2013, at 12:32, Sergio Fernández Cordero
wrote: Hello list,
My name is Sergio Fernandez , I am personally interested in helping with the development of the image and OpenSuSE repositories for Raspberry Pi , since I have a project for a specialized desktop computer based on these two components.
I have seen that there is only unofficial images for Raspberry Pi, by SuSE decisions. I've also seen that everything is a bit chaotic and therefore funny :) And I'd like to participate.
I have several years administering Linux systems , I´m familiar with SuSE enterprise systems, and packaged for RPM distributions such as Mandriva and Mageia (and of course RHEL). Don't know how SUSE buildsystem works, but come with the intention to learn.
I downloaded an image from Bernhard repository and I launched my Rpi. I've done some modifications and configurations and, works well . But I need more integration and stability and I want collaborate to do it for everyone.
So where I can start? What to read , where to search ...
The main reason we don't have an official Raspberry PI image today is that the build fails:
https://build.opensuse.org/project/show/devel:ARM:13.1:Contrib:RaspberryPi
The build fails because the kernel we're using inside the build VM doesn't have proper FAT support. There are 2 things to do here:
1) Try to build an image locally. Use "osc build" to build it on your existing RPi installation. Check whether the result actually works. 2) Enable proper vfat support for the guest kernel in our RPi build project. Adrian just introduced a feature this week that should make this possible. But it's not for the faint of heart yet :).
Once we have those 2 pieces solved you should even be able to build your own customized image in OBS for the RPi.
Oh, there is more to fix. When you look at the XFCE or E17 image, you will see that there are unresolvable packages. That's most likely because they simply haven't compiled. It would be good to find out why they don't compile, fix them and then somehow make them available to everyone (probably an overlay in the Ports repo plus a maintenance update).
Regards
P.S.: Sorry for my English. Not so proper.
Welcome on board :)
Alex
-- ------------------------- Sergio Fernandez Cordero -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (4)
-
Adrian Schröter
-
Alexander Graf
-
Guillaume Gardet
-
Sergio Fernández Cordero