-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi folks !
Just to let you know that the armv7hl plague builders have been busy during the week. Apart from the c7-buildroot, the SRPM packages built through plague are listed here : http://armv7.dev.centos.org/built.html As more and more BuildRequires: deps are now solved, new packages are built every day (all that in loop)
Slowly wondering how we can have a look at a minimal list of packages (basically using http://armv7.dev.centos.org/repodir/c7-pass-1/ and http://armv7.dev.centos.org/repodir/c7-buildroot/ ) for a working RootFS that can be tested on various armv7 boards (raspi2, odroid c1, etc ..)
As I'm myself a beginner (wrt to ARM platform), searching for opinions/howtos/help from you and see how we can generate that, and also document all that on wiki.centos.org
As an example, it seems odroid c1 needs uboot, and I see most people still using the hardkernel.org/odroid kernel, instead of the one from the distro. Is that needed, if so, why, and all such kind of questions that we can put/answer on the wiki.
Volunteers ? :-)
- --
Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
For the package list needed, it may be cheating, but if you use the same packages that fedora uses for their arm7 minimal, that should be enough and they would have worked out the dependencies needed. Obviously there will be some differences. As far as raspi2 goes, I can build one off of a generic rootfs without uboot without issue. I could even take an older fedora build, change the repos over to centos, replace my version packages and do a yum distro-sync to replace everything fedora with centos. Its a very dirty method, but it should work and would not need a rootfs, only a repo for yum to see.
On May 29, 2015 8:22:25 AM CDT, Fabian Arrotin arrfab@centos.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi folks !
Just to let you know that the armv7hl plague builders have been busy during the week. Apart from the c7-buildroot, the SRPM packages built through plague are listed here : http://armv7.dev.centos.org/built.html As more and more BuildRequires: deps are now solved, new packages are built every day (all that in loop)
Slowly wondering how we can have a look at a minimal list of packages (basically using http://armv7.dev.centos.org/repodir/c7-pass-1/ and http://armv7.dev.centos.org/repodir/c7-buildroot/ ) for a working RootFS that can be tested on various armv7 boards (raspi2, odroid c1, etc ..)
As I'm myself a beginner (wrt to ARM platform), searching for opinions/howtos/help from you and see how we can generate that, and also document all that on wiki.centos.org
As an example, it seems odroid c1 needs uboot, and I see most people still using the hardkernel.org/odroid kernel, instead of the one from the distro. Is that needed, if so, why, and all such kind of questions that we can put/answer on the wiki.
Volunteers ? :-)
Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlVoaBEACgkQnVkHo1a+xU6FRACgkSCATUH+XLztEXxfuXjuXmi5 GCsAniJN/S/AudeL4ffuCqWbfbBi5PJJ =Z4Av -----END PGP SIGNATURE----- _______________________________________________ Arm-dev mailing list Arm-dev@centos.org http://lists.centos.org/mailman/listinfo/arm-dev
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 29/05/15 15:27, cc35359@gmail.com wrote:
For the package list needed, it may be cheating, but if you use the same packages that fedora uses for their arm7 minimal, that should be enough and they would have worked out the dependencies needed. Obviously there will be some differences. As far as raspi2 goes, I can build one off of a generic rootfs without uboot without issue. I could even take an older fedora build, change the repos over to centos, replace my version packages and do a yum distro-sync to replace everything fedora with centos. Its a very dirty method, but it should work and would not need a rootfs, only a repo for yum to see.
Basically I wanted to follow the minimal group defined in the comps.xml file (except some firmware not needed for arm). Working against a fedora image can probably work, but only something older than centos 7, so normallly Fedora 19 (so that packages are updated by centos 7 trees). If you can start working on that , that would probably help, and at least produces some "momentum" for the final image :-)
OTOH, it would be good to document how to do that "from scratch" when we'll want to produce such image, and each specific thing that needs to be solved for some boards.
Thanks for your help !
- --
Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
Do you have rsync or another easier way to grab the rpms? Doesn't look like ftp is setup to do that recursively. It'll just take a long time to manually download them all :)
On May 29, 2015 8:35:34 AM CDT, Fabian Arrotin arrfab@centos.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 29/05/15 15:27, cc35359@gmail.com wrote:
For the package list needed, it may be cheating, but if you use the same packages that fedora uses for their arm7 minimal, that should be enough and they would have worked out the dependencies needed. Obviously there will be some differences. As far as raspi2 goes, I can build one off of a generic rootfs without uboot without issue. I could even take an older fedora build, change the repos over to centos, replace my version packages and do a yum distro-sync to replace everything fedora with centos. Its a very dirty method, but it should work and would not need a rootfs, only a repo for yum to see.
Basically I wanted to follow the minimal group defined in the comps.xml file (except some firmware not needed for arm). Working against a fedora image can probably work, but only something older than centos 7, so normallly Fedora 19 (so that packages are updated by centos 7 trees). If you can start working on that , that would probably help, and at least produces some "momentum" for the final image :-)
OTOH, it would be good to document how to do that "from scratch" when we'll want to produce such image, and each specific thing that needs to be solved for some boards.
Thanks for your help !
Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlVoayYACgkQnVkHo1a+xU6w9ACfaEXJ/dJW3j0zHDJ+jGmMSdMp MM4An30tzl4wWhXmTu75VPeScZz8eMQO =1iR/ -----END PGP SIGNATURE----- _______________________________________________ Arm-dev mailing list Arm-dev@centos.org http://lists.centos.org/mailman/listinfo/arm-dev
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 29/05/15 17:13, cc35359@gmail.com wrote:
Do you have rsync or another easier way to grab the rpms? Doesn't look like ftp is setup to do that recursively. It'll just take a long time to manually download them all :)
No rsync but you can either always point to that node (as it's a rolling tree !) or simply configure a (disabled by default) yum repo pointing to c7-buildroot and c7-pass-1 and use reposync to automatically download the packages ;-)
- --
Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
Well I got a base fedora booted now, we'll give it a shot. I'm sure I'll have to go through some dependency h3ll for awhile :)
On May 29, 2015 10:18:39 AM CDT, Fabian Arrotin arrfab@centos.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 29/05/15 17:13, cc35359@gmail.com wrote:
Do you have rsync or another easier way to grab the rpms? Doesn't look like ftp is setup to do that recursively. It'll just take a long time to manually download them all :)
No rsync but you can either always point to that node (as it's a rolling tree !) or simply configure a (disabled by default) yum repo pointing to c7-buildroot and c7-pass-1 and use reposync to automatically download the packages ;-)
Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlVog08ACgkQnVkHo1a+xU5/3wCfSYJ07QycVY8Rgx3Ko8vMB1Xs gb0Ani7N2x3yowjB+DHt37DlhmzneGWO =1fCD -----END PGP SIGNATURE----- _______________________________________________ Arm-dev mailing list Arm-dev@centos.org http://lists.centos.org/mailman/listinfo/arm-dev
OK, I have a centos raspi2 all working. Not a single fedora package left. Do you have any pi2s?
On May 29, 2015 10:18:39 AM CDT, Fabian Arrotin arrfab@centos.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 29/05/15 17:13, cc35359@gmail.com wrote:
Do you have rsync or another easier way to grab the rpms? Doesn't look like ftp is setup to do that recursively. It'll just take a long time to manually download them all :)
No rsync but you can either always point to that node (as it's a rolling tree !) or simply configure a (disabled by default) yum repo pointing to c7-buildroot and c7-pass-1 and use reposync to automatically download the packages ;-)
Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlVog08ACgkQnVkHo1a+xU5/3wCfSYJ07QycVY8Rgx3Ko8vMB1Xs gb0Ani7N2x3yowjB+DHt37DlhmzneGWO =1fCD -----END PGP SIGNATURE----- _______________________________________________ Arm-dev mailing list Arm-dev@centos.org http://lists.centos.org/mailman/listinfo/arm-dev
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 29/05/15 20:03, cc35359@gmail.com wrote:
OK, I have a centos raspi2 all working. Not a single fedora package left. Do you have any pi2s?
Oh cool ... I have myself only two raspi1 and one odroid c1 .. but I'm sure some other folks on this list have raspi2 available .. Have you got the full list of needed packages for a working c7 install ?
- --
Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
Its just a mostly bare install, less than a GB of space used to run. There are still a few packages I can likely clean off, but there is nothing there beyond what you have compiled already at least. I can put the image file on Google drive (I could host the image on the centos pi itself to allow a download, but I only have 1mbit upload speed), that way you can at least mount it and see what is there, or i can just dump the installed package list for you. I will look into slimming it up even further, but is there a specific goal in mind for the minimal rootfs: is it a size goal, or simply "all thats needed to boot, take a keyboard as input, and access yum repos on a network"? Getting it working was step 1, at least its proof that your hard work is paying off :) Do we want anyone else to be able to download the image as well in order to look for major faults yet, or wait until the next phase when you have a rootfs built?
On May 30, 2015 6:12:12 AM CDT, Fabian Arrotin arrfab@centos.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 29/05/15 20:03, cc35359@gmail.com wrote:
OK, I have a centos raspi2 all working. Not a single fedora package left. Do you have any pi2s?
Oh cool ... I have myself only two raspi1 and one odroid c1 .. but I'm sure some other folks on this list have raspi2 available .. Have you got the full list of needed packages for a working c7 install ?
Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlVpmwwACgkQnVkHo1a+xU74WACeNam/49Of46CPWP7KK2BocbOs NuEAnRuWp4p8e0aPhcKA+5+reSNs4R7n =ez8r -----END PGP SIGNATURE----- _______________________________________________ Arm-dev mailing list Arm-dev@centos.org http://lists.centos.org/mailman/listinfo/arm-dev
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 30/05/15 13:26, cc35359@gmail.com wrote:
Its just a mostly bare install, less than a GB of space used to run. There are still a few packages I can likely clean off, but there is nothing there beyond what you have compiled already at least. I can put the image file on Google drive (I could host the image on the centos pi itself to allow a download, but I only have 1mbit upload speed), that way you can at least mount it and see what is there, or i can just dump the installed package list for you. I will look into slimming it up even further, but is there a specific goal in mind for the minimal rootfs: is it a size goal, or simply "all thats needed to boot, take a keyboard as input, and access yum repos on a network"? Getting it working was step 1, at least its proof that your hard work is paying off :) Do we want anyone else to be able to download the image as well in order to look for major faults yet, or wait until the next phase when you have a rootfs built?
Well, you can upload it where you can, and then I can grab it and put it somewhere else (like buildlogs.centos.org ? ) so that people can have a look and test it. What I'd like to see though is also documenting that on wiki.centos.org. For example, have you used the kernel-4.0.0 rpm package built and available in the c7-buildroot (http://armv7.dev.centos.org/repodir/c7-buildroot/kernel/), or have you used the one from another distro ? etc .. So if someone has expertise with specific boards, we can all write/centralize that on the wiki, so that we can then eventually automate the various .img files creation, for all kind of specific boards, etc ..
Do you have already have a wiki account ? We can use a generic "entry" page for arm32 (like the existing http://wiki.centos.org/SpecialInterestGroup/AltArch/Arm32 page) , but moving content like plague builder access somewhere else (a sub-page) and do something like /Raspberry1 , or /Odroid , etc ..)
What do you (all) think ?
- --
Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 30/05/15 14:20, Fabian Arrotin wrote:
On 30/05/15 13:26, cc35359@gmail.com wrote:
Its just a mostly bare install, less than a GB of space used to run. There are still a few packages I can likely clean off, but there is nothing there beyond what you have compiled already at least. I can put the image file on Google drive (I could host the image on the centos pi itself to allow a download, but I only have 1mbit upload speed), that way you can at least mount it and see what is there, or i can just dump the installed package list for you. I will look into slimming it up even further, but is there a specific goal in mind for the minimal rootfs: is it a size goal, or simply "all thats needed to boot, take a keyboard as input, and access yum repos on a network"? Getting it working was step 1, at least its proof that your hard work is paying off :) Do we want anyone else to be able to download the image as well in order to look for major faults yet, or wait until the next phase when you have a rootfs built?
Well, you can upload it where you can, and then I can grab it and put it somewhere else (like buildlogs.centos.org ? ) so that people can have a look and test it. What I'd like to see though is also documenting that on wiki.centos.org. For example, have you used the kernel-4.0.0 rpm package built and available in the c7-buildroot (http://armv7.dev.centos.org/repodir/c7-buildroot/kernel/), or have you used the one from another distro ? etc .. So if someone has expertise with specific boards, we can all write/centralize that on the wiki, so that we can then eventually automate the various .img files creation, for all kind of specific boards, etc ..
Do you have already have a wiki account ? We can use a generic "entry" page for arm32 (like the existing http://wiki.centos.org/SpecialInterestGroup/AltArch/Arm32 page) , but moving content like plague builder access somewhere else (a sub-page) and do something like /Raspberry1 , or /Odroid , etc ..)
What do you (all) think ?
Just to add that we'll probably have to write (or integrate ?) some scripts to init the node, like for the resize2fs, etc .. so basically what other distro have also for that kind of boards ...
- --
Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
If you decide where to plant the wiki page, I'll be happy to document all the steps necessary to go from rootfs to a running raspi. I can toss on the extra steps I took for this "proof of concept" I built as well for now, though those steps will be irrelevant when there is a CentOS rootfs. It does use the kernel compiled specifically for the board from the raspi foundation, as well as the necessary binary firmware. One thing to consider is that when it comes to the arm boards, in my opinion, where people will be turning to CentOS is for their home servers. They want the security, stability and support cycle that centos provides for the Pi that's their file server, or owncloud server, or dovecot/postfix, that is running non stop and problem free in the closet. Its unlikely that the media lovers will be turning to CentOS except for minidlna or media tomb. Starting developers may also be attracted to using an enterprise grade system instead of the bleeding edge distros, so some basic gpio pin usage may be done. So at the very least, a collection of how to's in regard to common home server applications may be beneficial, as a lot of these devices aren't targeted to those of us using Linux the last 20 years, but for those who are starting out learning. I'll be happy to write any up that we feel would be good to have. Maybe we even want to think of including some things like samba, owncloud, dlna server, etc in an image for that reason as well (things that centos already provides for the x86-64). Just some thoughts. I'll paste the link to the image below. I did build it on a 16gb SD card as I had nothing smaller laying around, but I can always find a $4 4gb card to help generate future images depending on how its decided to generate them in the future- if we provide a full image for different boards, or just instruct on how to use the generic image. Maybe we'll want a minimal image and a GUI image even. I shrunk it up a bit more to what I felt was a good balance of what a minimal install should have, and I exported the list from yum to the /root/ directory, so you can mount the image and grab the list without having to extract it from the yum or rpm databases. The / partition has 672mb of data on it. Also, I didn't notice a dhcp service built, so to use the image you will need to set a static one the old fashioned way (ifconfig and 'route add default x') . The pass1 and buildroot repos added are disabled by default. Root password is blank, and obviously would need to be set before allowing the internet (and all its lovely bots) to touch it. -David
https://drive.google.com/open?id=0B6w0L-XWgP4sVGpkS1l5dnE2bkk&authuser=0
On May 30, 2015 7:22:27 AM CDT, Fabian Arrotin arrfab@centos.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 30/05/15 14:20, Fabian Arrotin wrote:
On 30/05/15 13:26, cc35359@gmail.com wrote:
Its just a mostly bare install, less than a GB of space used to run. There are still a few packages I can likely clean off, but there is nothing there beyond what you have compiled already at least. I can put the image file on Google drive (I could host the image on the centos pi itself to allow a download, but I only have 1mbit upload speed), that way you can at least mount it and see what is there, or i can just dump the installed package list for you. I will look into slimming it up even further, but is there a specific goal in mind for the minimal rootfs: is it a size goal, or simply "all thats needed to boot, take a keyboard as input, and access yum repos on a network"? Getting it working was step 1, at least its proof that your hard work is paying off :) Do we want anyone else to be able to download the image as well in order to look for major faults yet, or wait until the next phase when you have a rootfs built?
Well, you can upload it where you can, and then I can grab it and put it somewhere else (like buildlogs.centos.org ? ) so that people can have a look and test it. What I'd like to see though is also documenting that on wiki.centos.org. For example, have you used the kernel-4.0.0 rpm package built and available in the c7-buildroot (http://armv7.dev.centos.org/repodir/c7-buildroot/kernel/), or have you used the one from another distro ? etc .. So if someone has expertise with specific boards, we can all write/centralize that on the wiki, so that we can then eventually automate the various .img files creation, for all kind of specific boards, etc ..
Do you have already have a wiki account ? We can use a generic "entry" page for arm32 (like the existing http://wiki.centos.org/SpecialInterestGroup/AltArch/Arm32 page) , but moving content like plague builder access somewhere else (a sub-page) and do something like /Raspberry1 , or /Odroid , etc ..)
What do you (all) think ?
Just to add that we'll probably have to write (or integrate ?) some scripts to init the node, like for the resize2fs, etc .. so basically what other distro have also for that kind of boards ...
Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlVpq4MACgkQnVkHo1a+xU7YIACfT10b7tKb2blRsT51PgXgCs89 87kAn2sugXx2BE6PobfM1ROxOMCfNQ8k =1c02 -----END PGP SIGNATURE----- _______________________________________________ Arm-dev mailing list Arm-dev@centos.org http://lists.centos.org/mailman/listinfo/arm-dev
On 05/30/2015 06:26 AM, cc35359@gmail.com wrote:
Its just a mostly bare install, less than a GB of space used to run. There are still a few packages I can likely clean off, but there is nothing there beyond what you have compiled already at least. I can put the image file on Google drive (I could host the image on the centos pi itself to allow a download, but I only have 1mbit upload speed), that way you can at least mount it and see what is there, or i can just dump the installed package list for you. I will look into slimming it up even further, but is there a specific goal in mind for the minimal rootfs: is it a size goal, or simply "all thats needed to boot, take a keyboard as input, and access yum repos on a network"? Getting it working was step 1, at least its proof that your hard work is paying off :) Do we want anyone else to be able to download the image as well in order to look for major faults yet, or wait until the next phase when you have a rootfs built?
OK, I have a pi2 image built from RBF:
However, the dbus service is not working.
The way RBF is currently set up, it uses the raspi2 3.18.14-v7+ kernel on a vfat filesystem.
Are you using the raspi2 kernel and does your dbus service work?
Thanks, Johnny Hughes
On May 30, 2015 6:12:12 AM CDT, Fabian Arrotin arrfab@centos.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 29/05/15 20:03, cc35359@gmail.com wrote: OK, I have a centos raspi2 all working. Not a single fedora package left. Do you have any pi2s? Oh cool ... I have myself only two raspi1 and one odroid c1 .. but I'm sure some other folks on this list have raspi2 available .. Have you got the full list of needed packages for a working c7 install ? - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlVpmwwACgkQnVkHo1a+xU74WACeNam/49Of46CPWP7KK2BocbOs NuEAnRuWp4p8e0aPhcKA+5+reSNs4R7n =ez8r -----END PGP SIGNATURE----- ------------------------------------------------------------------------ Arm-dev mailing list Arm-dev@centos.org http://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org http://lists.centos.org/mailman/listinfo/arm-dev
I had no dbus issues with the couple images I made. One image I made by simply yum distro syncing from fedora 19. The other image I did used yum to install to a USB stick, then copied that to an sdcard. The / worked on both ext4 and xfs for me as well, vfat is needed for boot though. I used the same kernel, and even copied the RPI script over and have ran it a few times on the last image I made. I had some issues with a WiFi module, but resolved that. No other problems.
On June 17, 2015 6:13:21 AM CDT, Johnny Hughes johnny@centos.org wrote:
On 05/30/2015 06:26 AM, cc35359@gmail.com wrote:
Its just a mostly bare install, less than a GB of space used to run. There are still a few packages I can likely clean off, but there is nothing there beyond what you have compiled already at least. I can put the image file on Google drive (I could host the image on
the
centos pi itself to allow a download, but I only have 1mbit upload speed), that way you can at least mount it and see what is there, or
i
can just dump the installed package list for you. I will look into slimming it up even further, but is there a specific goal in mind for the minimal rootfs: is it a size goal, or simply
"all
thats needed to boot, take a keyboard as input, and access yum repos
on
a network"? Getting it working was step 1, at least its proof that your hard work
is
paying off :) Do we want anyone else to be able to download the image as well in
order
to look for major faults yet, or wait until the next phase when you
have
a rootfs built?
OK, I have a pi2 image built from RBF:
However, the dbus service is not working.
The way RBF is currently set up, it uses the raspi2 3.18.14-v7+ kernel on a vfat filesystem.
Are you using the raspi2 kernel and does your dbus service work?
Thanks, Johnny Hughes
On May 30, 2015 6:12:12 AM CDT, Fabian Arrotin arrfab@centos.org
wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 29/05/15 20:03, cc35359@gmail.com wrote: OK, I have a centos raspi2 all working. Not a single fedora package left. Do you have any pi2s? Oh cool ... I have myself only two raspi1 and one odroid c1 .. but I'm suresome
other folks on this list have raspi2 available .. Have you got the full list of needed packages for a working c7install ?
- -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlVpmwwACgkQnVkHo1a+xU74WACeNam/49Of46CPWP7KK2BocbOs NuEAnRuWp4p8e0aPhcKA+5+reSNs4R7n =ez8r -----END PGP SIGNATURE-----
Arm-dev mailing list Arm-dev@centos.org http://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org http://lists.centos.org/mailman/listinfo/arm-dev
Arm-dev mailing list Arm-dev@centos.org http://lists.centos.org/mailman/listinfo/arm-dev
I had no dbus issues with the couple images I made. One image I made by simply yum distro syncing from fedora 19. The other image I did used yum to install to a USB stick, then copied that to an sdcard. The / worked on both ext4 and xfs for me as well, vfat is needed for boot though. I used the same kernel, and even copied the RPI script over and have ran it a few times on the last image I made. I had some issues with a WiFi module, but resolved that. No other problems.
Can you share the list of installed packages on any of the images where DBus and NetworkManager worked. Did you install anything apart from @core ?
I did have to install NetworkManager-wifi and its dependencies, but I do not recall anything else I needed to do. Dbus just worked out of the box. I would have to export a package list, but that pi I can't access over the internet and I'm not at home with it.
On June 17, 2015 10:58:50 AM CDT, Mandar Joshi emailmandar@gmail.com wrote:
I had no dbus issues with the couple images I made. One image I made
by simply yum distro syncing from fedora 19. The other image I did used yum to install to a USB stick, then copied that to an sdcard. The / worked on both ext4 and xfs for me as well, vfat is needed for boot though. I used the same kernel, and even copied the RPI script over and have ran it a few times on the last image I made. I had some issues with a WiFi module, but resolved that. No other problems.
Can you share the list of installed packages on any of the images where DBus and NetworkManager worked. Did you install anything apart from @core ? _______________________________________________ Arm-dev mailing list Arm-dev@centos.org http://lists.centos.org/mailman/listinfo/arm-dev
OK, I have a pi2 image built from RBF:
However, the dbus service is not working.
The way RBF is currently set up, it uses the raspi2 3.18.14-v7+ kernel on a vfat filesystem.
Are you using the raspi2 kernel and does your dbus service work?
I found a solution. Had to copy dbus.service and dbus.socket from /lib/systemd/system/ to /usr/lib/systemd/system and create a symlink for dbus.socket in dbus.target.wants
The commands I executed were
cd /usr/lib/systemd/system cp /lib/systemd/system/dbus.s* . cd dbus.target.wants/ ln -s ../dbus.socket . reboot
I tested this fix on Rpi2 and Odroid C1 Can you check if this works for you? Not sure why this problem should have occurred in the first place. But the above steps do fix the problem for me.
Did something go wrong in the image build that it didn't dump it in /usr for some reason? I'm not sure why else that would happen, something when it installed the dbus rpm
On June 17, 2015 3:47:21 PM CDT, Mandar Joshi emailmandar@gmail.com wrote:
OK, I have a pi2 image built from RBF:
However, the dbus service is not working.
The way RBF is currently set up, it uses the raspi2 3.18.14-v7+
kernel
on a vfat filesystem.
Are you using the raspi2 kernel and does your dbus service work?
I found a solution. Had to copy dbus.service and dbus.socket from /lib/systemd/system/ to /usr/lib/systemd/system and create a symlink for dbus.socket in dbus.target.wants
The commands I executed were
cd /usr/lib/systemd/system cp /lib/systemd/system/dbus.s* . cd dbus.target.wants/ ln -s ../dbus.socket . reboot
I tested this fix on Rpi2 and Odroid C1 Can you check if this works for you? Not sure why this problem should have occurred in the first place. But the above steps do fix the problem for me. _______________________________________________ Arm-dev mailing list Arm-dev@centos.org http://lists.centos.org/mailman/listinfo/arm-dev
Did something go wrong in the image build that it didn't dump it in /usr for some reason? I'm not sure why else that would happen, something when it installed the dbus rpm
rpm -ql dbus says files are in lib and not /usr/lib http://pastebin.com/g3Wsmjgz
Weird thing is that this problem doesn't present itself on the image generated for Cubietruck.
On 06/17/2015 04:04 PM, Mandar Joshi wrote:
Did something go wrong in the image build that it didn't dump it in /usr for some reason? I'm not sure why else that would happen, something when it installed the dbus rpm
rpm -ql dbus says files are in lib and not /usr/lib http://pastebin.com/g3Wsmjgz
Weird thing is that this problem doesn't present itself on the image generated for Cubietruck.
Mandar,
The filesystem rpm also has issues on the raspi2 .. it fails to install either while creating the image OR afterwards .. and a weird symlink happens in / that looks like this:
lib;0001e142 -> usr/lib
Here is the error:
Error unpacking rpm package filesystem-3.2-18.el7.armv7hl error: unpacking of archive failed on file /lib: cpio: rename Verifying : filesystem-3.2-18.el7.armv7hl
But that also works on cubietruck.
These issues could be related as filesystem is just a bunch of directories so something is happening with symlinking or renaming of directories.
It seems that issue night be caused by cpio .. will investigate further. cpio might also be being used by the dbus rpm for moving those files that are not moved.
Thanks, Johnny Hughes
The filesystem rpm also has issues on the raspi2 .. it fails to install either while creating the image OR afterwards .. and a weird symlink happens in / that looks like this:
lib;0001e142 -> usr/lib
Here is the error:
Error unpacking rpm package filesystem-3.2-18.el7.armv7hl error: unpacking of archive failed on file /lib: cpio: rename Verifying : filesystem-3.2-18.el7.armv7hl
But that also works on cubietruck.
I had noticed that sometimes filesystem-3.2-18.el7.armv7hl and glibc-common-2.17-78.el7.armv7hl fail to install and added it to the known issues in the README but did not realize the issue was specific to raspberry pi 2
The dbus problem presents itself with the Odroid C1 as well. I'll check if the same rpms are failing there too.
The filesystem rpm also has issues on the raspi2 .. it fails to install either while creating the image OR afterwards .. and a weird symlink happens in / that looks like this:
lib;0001e142 -> usr/lib
Here is the error:
Error unpacking rpm package filesystem-3.2-18.el7.armv7hl error: unpacking of archive failed on file /lib: cpio: rename Verifying : filesystem-3.2-18.el7.armv7hl
But that also works on cubietruck.
These issues could be related as filesystem is just a bunch of directories so something is happening with symlinking or renaming of directories.
Found the problem. In case of a custom kernel (Rpi2 and Odroid C1) the kernel modules were being copied before installing packages. The kernel modules go in /lib. I guess that is what was causing the problem. /lib being present before installing the filesystem rpm I moved the installation of kernel after network config and tested generation of images for Rpi2 and OdroidC1. No more errors! I uploaded changes to the github repo. However, I haven't tested the change thoroughly. Just generated the images once.
That would likely explain why my manual method worked, I did the kernel at the very end.
On June 18, 2015 3:33:11 PM CDT, Mandar Joshi emailmandar@gmail.com wrote:
The filesystem rpm also has issues on the raspi2 .. it fails to
install
either while creating the image OR afterwards .. and a weird symlink happens in / that looks like this:
lib;0001e142 -> usr/lib
Here is the error:
Error unpacking rpm package filesystem-3.2-18.el7.armv7hl error: unpacking of archive failed on file /lib: cpio: rename Verifying : filesystem-3.2-18.el7.armv7hl
But that also works on cubietruck.
These issues could be related as filesystem is just a bunch of directories so something is happening with symlinking or renaming of directories.
Found the problem. In case of a custom kernel (Rpi2 and Odroid C1) the kernel modules were being copied before installing packages. The kernel modules go in /lib. I guess that is what was causing the problem. /lib being present before installing the filesystem rpm I moved the installation of kernel after network config and tested generation of images for Rpi2 and OdroidC1. No more errors! I uploaded changes to the github repo. However, I haven't tested the change thoroughly. Just generated the images once. _______________________________________________ Arm-dev mailing list Arm-dev@centos.org http://lists.centos.org/mailman/listinfo/arm-dev
On 06/18/2015 03:33 PM, Mandar Joshi wrote:
The filesystem rpm also has issues on the raspi2 .. it fails to install either while creating the image OR afterwards .. and a weird symlink happens in / that looks like this:
lib;0001e142 -> usr/lib
Here is the error:
Error unpacking rpm package filesystem-3.2-18.el7.armv7hl error: unpacking of archive failed on file /lib: cpio: rename Verifying : filesystem-3.2-18.el7.armv7hl
But that also works on cubietruck.
These issues could be related as filesystem is just a bunch of directories so something is happening with symlinking or renaming of directories.
Found the problem. In case of a custom kernel (Rpi2 and Odroid C1) the kernel modules were being copied before installing packages. The kernel modules go in /lib. I guess that is what was causing the problem. /lib being present before installing the filesystem rpm I moved the installation of kernel after network config and tested generation of images for Rpi2 and OdroidC1. No more errors! I uploaded changes to the github repo. However, I haven't tested the change thoroughly. Just generated the images once.
I can confirm that the rpi2 image did not have the errors WRT glibc and filesystem. I have copied said image to an SD Card and I am looking at it now.
I did notice an error in gnutls install that said:
Error in GnuTLS initialization: Failed to acquire random data.
I am not sure this is a major issue in the chroot install .. I will reinstall gnutls on the image once on the machine and see if we get the same error.
I will also try to verify that this had no impact on other packages in the image install that might have required something from gnutls.
On 06/19/2015 06:22 PM, Johnny Hughes wrote:
On 06/18/2015 03:33 PM, Mandar Joshi wrote:
The filesystem rpm also has issues on the raspi2 .. it fails to install either while creating the image OR afterwards .. and a weird symlink happens in / that looks like this:
lib;0001e142 -> usr/lib
Here is the error:
Error unpacking rpm package filesystem-3.2-18.el7.armv7hl error: unpacking of archive failed on file /lib: cpio: rename Verifying : filesystem-3.2-18.el7.armv7hl
But that also works on cubietruck.
These issues could be related as filesystem is just a bunch of directories so something is happening with symlinking or renaming of directories.
Found the problem. In case of a custom kernel (Rpi2 and Odroid C1) the kernel modules were being copied before installing packages. The kernel modules go in /lib. I guess that is what was causing the problem. /lib being present before installing the filesystem rpm I moved the installation of kernel after network config and tested generation of images for Rpi2 and OdroidC1. No more errors! I uploaded changes to the github repo. However, I haven't tested the change thoroughly. Just generated the images once.
I can confirm that the rpi2 image did not have the errors WRT glibc and filesystem. I have copied said image to an SD Card and I am looking at it now.
I did notice an error in gnutls install that said:
Error in GnuTLS initialization: Failed to acquire random data.
I am not sure this is a major issue in the chroot install .. I will reinstall gnutls on the image once on the machine and see if we get the same error.
I will also try to verify that this had no impact on other packages in the image install that might have required something from gnutls.
Reinstalling gnutls did not result in the same error, also I did not have any indication that it caused any issues the way it installed in the chroot initially. So I think this can be ignored unless someone determines it causes an issue.
I did notice that port 22 on firewalld was NOT open on the rpi2 install, but it was open on the cubietruck install. Any idea why?
Thanks, Johnny Hughes
I did notice an error in gnutls install that said:
Error in GnuTLS initialization: Failed to acquire random data.
Adding mount --rbind /dev/ to the installroot solves this problem. I've uploaded the change to github
I did notice that port 22 on firewalld was NOT open on the rpi2 install, but it was open on the cubietruck install. Any idea why?
This is caused by IPv6_rpfilter=yes in /etc/firewalld/firewalld.conf Firewalld gives this error http://pastebin.com/FwHgvyXw in /var/log/firewalld while starting
Setting IPv6_rpfilter=no in /etc/firewalld/firewalld.conf solves the problem for me. This issue is specific to the Raspberry Pi 2. Firewalld starts correctly with IPv6_rpfilter=yes on the Odroid C1 too. So I'm guessing it has to do with IPv6_rpfilter support in the Raspberry Pi 2 kernel but I could be wrong.
Regards Mandar Joshi
Oh, and might want to consider compiling network manager :)
On May 29, 2015 10:18:39 AM CDT, Fabian Arrotin arrfab@centos.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 29/05/15 17:13, cc35359@gmail.com wrote:
Do you have rsync or another easier way to grab the rpms? Doesn't look like ftp is setup to do that recursively. It'll just take a long time to manually download them all :)
No rsync but you can either always point to that node (as it's a rolling tree !) or simply configure a (disabled by default) yum repo pointing to c7-buildroot and c7-pass-1 and use reposync to automatically download the packages ;-)
Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlVog08ACgkQnVkHo1a+xU5/3wCfSYJ07QycVY8Rgx3Ko8vMB1Xs gb0Ani7N2x3yowjB+DHt37DlhmzneGWO =1fCD -----END PGP SIGNATURE----- _______________________________________________ Arm-dev mailing list Arm-dev@centos.org http://lists.centos.org/mailman/listinfo/arm-dev
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 29/05/15 20:09, cc35359@gmail.com wrote:
Oh, and might want to consider compiling network manager :)
Yeah, it's one of the few remaining packages declared in the @minimal group not (yet) built .. and mandatory :-) There are new packages built every day, but I'll have a look at NetworkManager to see if there isn't a "circular dep" involved for that one (like I had for soooooo much packages up to $now)
Cheers,
- --
Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
On 05/29/2015 04:22 PM, Fabian Arrotin wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi folks !
Just to let you know that the armv7hl plague builders have been busy during the week. Apart from the c7-buildroot, the SRPM packages built through plague are listed here : http://armv7.dev.centos.org/built.html As more and more BuildRequires: deps are now solved, new packages are built every day (all that in loop)
Slowly wondering how we can have a look at a minimal list of packages (basically using http://armv7.dev.centos.org/repodir/c7-pass-1/ and http://armv7.dev.centos.org/repodir/c7-buildroot/ ) for a working RootFS that can be tested on various armv7 boards (raspi2, odroid c1, etc ..)
As I'm myself a beginner (wrt to ARM platform), searching for opinions/howtos/help from you and see how we can generate that, and also document all that on wiki.centos.org
As an example, it seems odroid c1 needs uboot, and I see most people still using the hardkernel.org/odroid kernel, instead of the one from the distro. Is that needed, if so, why, and all such kind of questions that we can put/answer on the wiki.
Volunteers ? :-)
I volunteer to do any testing you please on the U3 I have handy.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 29/05/15 15:35, Manuel Wolfshant wrote:
On 05/29/2015 04:22 PM, Fabian Arrotin wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi folks !
Just to let you know that the armv7hl plague builders have been busy during the week. Apart from the c7-buildroot, the SRPM packages built through plague are listed here : http://armv7.dev.centos.org/built.html As more and more BuildRequires: deps are now solved, new packages are built every day (all that in loop)
Slowly wondering how we can have a look at a minimal list of packages (basically using http://armv7.dev.centos.org/repodir/c7-pass-1/ and http://armv7.dev.centos.org/repodir/c7-buildroot/ ) for a working RootFS that can be tested on various armv7 boards (raspi2, odroid c1, etc ..)
As I'm myself a beginner (wrt to ARM platform), searching for opinions/howtos/help from you and see how we can generate that, and also document all that on wiki.centos.org
As an example, it seems odroid c1 needs uboot, and I see most people still using the hardkernel.org/odroid kernel, instead of the one from the distro. Is that needed, if so, why, and all such kind of questions that we can put/answer on the wiki.
Volunteers ? :-)
I volunteer to do any testing you please on the U3 I have handy.
Cool, so let's try first to list a way to "build" those images first :-) I don't know people prefer to use (as a "standard tool") to install the packages in a / partition. yum --installroot ? lorax ? something else ?
- --
Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
On 05/29/2015 04:40 PM, Fabian Arrotin wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 29/05/15 15:35, Manuel Wolfshant wrote:
On 05/29/2015 04:22 PM, Fabian Arrotin wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi folks !
Just to let you know that the armv7hl plague builders have been busy during the week. Apart from the c7-buildroot, the SRPM packages built through plague are listed here : http://armv7.dev.centos.org/built.html As more and more BuildRequires: deps are now solved, new packages are built every day (all that in loop)
Slowly wondering how we can have a look at a minimal list of packages (basically using http://armv7.dev.centos.org/repodir/c7-pass-1/ and http://armv7.dev.centos.org/repodir/c7-buildroot/ ) for a working RootFS that can be tested on various armv7 boards (raspi2, odroid c1, etc ..)
As I'm myself a beginner (wrt to ARM platform), searching for opinions/howtos/help from you and see how we can generate that, and also document all that on wiki.centos.org
As an example, it seems odroid c1 needs uboot, and I see most people still using the hardkernel.org/odroid kernel, instead of the one from the distro. Is that needed, if so, why, and all such kind of questions that we can put/answer on the wiki.
Volunteers ? :-)
I volunteer to do any testing you please on the U3 I have handy.
Cool, so let's try first to list a way to "build" those images first :-) I don't know people prefer to use (as a "standard tool") to install the packages in a / partition. yum --installroot ? lorax ? something else ?
dd if=functional.img of=/dev/sdb bs=8M && relocate sdcard to ARM system :))
FWIW: #ls /mnt/arhive/1/linux/distributions/odroid/ -l -rw-rw-r--. 1 wolfy wolfy 2544983052 Jan 12 2014 Lubuntu-13.10_Whisper-U2-HDMI.20140101.img.xz
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 29/05/15 16:58, Manuel Wolfshant wrote:
On 05/29/2015 04:40 PM, Fabian Arrotin wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 29/05/15 15:35, Manuel Wolfshant wrote:
On 05/29/2015 04:22 PM, Fabian Arrotin wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi folks !
Just to let you know that the armv7hl plague builders have been busy during the week. Apart from the c7-buildroot, the SRPM packages built through plague are listed here : http://armv7.dev.centos.org/built.html As more and more BuildRequires: deps are now solved, new packages are built every day (all that in loop)
Slowly wondering how we can have a look at a minimal list of packages (basically using http://armv7.dev.centos.org/repodir/c7-pass-1/ and http://armv7.dev.centos.org/repodir/c7-buildroot/ ) for a working RootFS that can be tested on various armv7 boards (raspi2, odroid c1, etc ..)
As I'm myself a beginner (wrt to ARM platform), searching for opinions/howtos/help from you and see how we can generate that, and also document all that on wiki.centos.org
As an example, it seems odroid c1 needs uboot, and I see most people still using the hardkernel.org/odroid kernel, instead of the one from the distro. Is that needed, if so, why, and all such kind of questions that we can put/answer on the wiki.
Volunteers ? :-)
I volunteer to do any testing you please on the U3 I have handy.
Cool, so let's try first to list a way to "build" those images first :-) I don't know people prefer to use (as a "standard tool") to install the packages in a / partition. yum --installroot ? lorax ? something else ?
dd if=functional.img of=/dev/sdb bs=8M && relocate sdcard to ARM system :))
FWIW: #ls /mnt/arhive/1/linux/distributions/odroid/ -l -rw-rw-r--. 1 wolfy wolfy 2544983052 Jan 12 2014 Lubuntu-13.10_Whisper-U2-HDMI.20140101.img.xz
Well, I guess we all know how to use dd to install a functional.img to disk, but my question for the arm-dev list was more : how do we build that functional.img first ? :-)
- --
Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
At some point, I will want to build a replacement for my mailserver. The list of software on that is rather extensive starting with postfix and going through roundcubemail. My current server is running on Redsleeve 6 and I had a challenge getting some of the dependencies met, pulling in from EPEL6 noarch rpms.
Then there is my samba server that is currently on ClearOS that I want to build Samba from scratch. Preferably Samba 4, but dnsmasq and all else that is needed.
But for starters I will just want apache for my web server.
On 05/29/2015 09:22 AM, Fabian Arrotin wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi folks !
Just to let you know that the armv7hl plague builders have been busy during the week. Apart from the c7-buildroot, the SRPM packages built through plague are listed here : http://armv7.dev.centos.org/built.html As more and more BuildRequires: deps are now solved, new packages are built every day (all that in loop)
Slowly wondering how we can have a look at a minimal list of packages (basically using http://armv7.dev.centos.org/repodir/c7-pass-1/ and http://armv7.dev.centos.org/repodir/c7-buildroot/ ) for a working RootFS that can be tested on various armv7 boards (raspi2, odroid c1, etc ..)
As I'm myself a beginner (wrt to ARM platform), searching for opinions/howtos/help from you and see how we can generate that, and also document all that on wiki.centos.org
As an example, it seems odroid c1 needs uboot, and I see most people still using the hardkernel.org/odroid kernel, instead of the one from the distro. Is that needed, if so, why, and all such kind of questions that we can put/answer on the wiki.
Volunteers ? :-)
Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlVoaBEACgkQnVkHo1a+xU6FRACgkSCATUH+XLztEXxfuXjuXmi5 GCsAniJN/S/AudeL4ffuCqWbfbBi5PJJ =Z4Av -----END PGP SIGNATURE----- _______________________________________________ Arm-dev mailing list Arm-dev@centos.org http://lists.centos.org/mailman/listinfo/arm-dev
-
cc35359＠gmail.com -
Fabian Arrotin -
Johnny Hughes -
Mandar Joshi -
Manuel Wolfshant -
Robert Moskowitz