Arm-dev

arm-dev@lists.centos.org

684 discussions

armv7hl - centos 7.1 rebuild status
by Fabian Arrotin 20 Jun '15

20 Jun '15

-----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-----

6 33

Completing the package set
by Karanbir Singh 19 Jun '15

19 Jun '15

hi guys, We need to get the rest of the distro packages processed in so we have a good baseline for CentOS-7. If needed, we can skip things that might be considered un-needed, but lets get a good list of those together and make sure its visible. Once that is done, we'll need to get the updates going. Who can help with this ? I believe plague is all setup and able to facilitate builds. -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

2 1

Nightly Image builds
by Karanbir Singh 19 Jun '15

19 Jun '15

Hi, It would be good to get a single location ( ideally on the arm repos host ) with all the various images built. - KB -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc

3 2

Re: [Arm-dev] Howto / bananapi
by Nicolas 18 Jun '15

18 Jun '15

Thanks a lot for your quick response. I will try it asap and let you know :-) Nicolas Le 18 juin 2015 08:45, Mandar Joshi a écrit: Where can I find infos to create the image? You can try generating the image using RootFS Build Factory https://github.com/mndar/rbf If it works please let me know so that I can add Bananapi to the list of tested boards. I have added support for bananapi but I don't have one. The support if based on information available here http://fedoraproject.org/wiki/Architectures/ARM/F21/Installation Refer README.md It has everything to get you started. You need Linux running on armv7 hardware or Qemu to use RootFS Build Factory. You can generate image for Qemu using the build factory. For Bananapi 1. Clone the repo 2. run the command ./rbf.py build templates/bananapi.xml 3. Write image bananapi-centos-image.img to sd card Regards Mandar Joshi _______________________________________________ Arm-dev mailing list Arm-dev(a)centos.org http://lists.centos.org/mailman/listinfo/arm-dev

2 2

enough packages for a @core install ?
by Fabian Arrotin 12 Jun '15

12 Jun '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, It seems we have now reach the point where enough packages are built to start looking at producing a working minimal setup. (with the c7-buildroot and c7-pass-1 repos) Who does take that in charge, and document it ? Cheers, - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlVshykACgkQnVkHo1a+xU5YtACfYOFWMIuJgBnrKSAOx2mjKCo/ /z4AnjRshY3xIHGQIhJcruiXsbs+1Dcj =TBOb -----END PGP SIGNATURE-----

5 28

zfs-fuse and dracut
by Gordan Bobic 09 Jun '15

09 Jun '15

Dear listers, I have modified the ZoL dracut module so it works with zfs-fuse. So if you wanted to be able to use zfs-fuse with a normal initrd with standard interoperability (e.g. have the initrd rebuilt automatically on kernel upgrades), now you can! There is no longer any need to slum it with lesser file systems, even if you are using a 32-bit system (i686, armv5tel, armv7hl, etc.) that doesn't play with with ZoL. :) I am using this on my ARM Chromebook running RedSleeve 7. You can find the code here: zfs-fuse-dracut: https://github.com/gordan-bobic/zfs-fuse-dracut zfs-fuse: https://github.com/gordan-bobic/zfs-fuse This is a fork of Emmanuel's branch that includes support for pool versions up to and including v26. It includes: 1) Latest modifications I made to improve systemd interoperability. 2) Some out of tree patches that that have been shipping with Fedora and Debian It does not yet include any backported patches from Seth's zfs-fuse github tree as I have not yet had time to review the patches since the repository divergence. RPMs are here: http://ftp.redsleeve.org/pub/el7-extra/SRPMS/zfs-fuse-0.7.1-2.el7.src.rpm http://ftp.redsleeve.org/pub/el7-extra/RPMS/armv5tel/zfs-fuse-0.7.1-2.el7.a… Please try it and report any bugs you encounter. Many thanks. Gordan

1 0

CentOS-7 beta candidate for AArch64 platforms
by Jim Perrin 27 May '15

27 May '15

We are pleased to announce the public beta release of CentOS Linux 7 for AArch64 compatible hardware. We've addressed a number of issues discovered from the previous 2 weeks of alpha testing, and feel that the release is stable enough to transition to beta. Improvements from Alpha ======================= Improved package selection: A number of additional packages have been added, including libreoffice, evolution, abrt, and more. Updated kernel: Some non-fatal kernel errors have been address by moving to a 4.1rc based kernel version. This also adds ACPI functionality to the platform. Improved Group selection: The installer now offers a larger group selection from the previous minimal-only install. Installation ============ Installation guides and documentation will be provided via the CentOS wiki, at http://wiki.centos.org/SpecialInterestGroup/AltArch/AArch64 Download ======== The full (unsigned) install tree is available at http://buildlogs.centos.org/centos/7/os/aarch64/ ============ Contributing The AArch64 effort is meant to be a community effort as part of the AltArch SIG (http://wiki.centos.org/SpecialInterestGroup/AltArch), and we welcome enthusiasts and vendors to contribute patches, fixes, documentation, etc. In the AArch64 Extras repository, we have provided the mock package and dependencies so that community members can more easily contribute, as well as testing their own builds locally. Please submit patches, fixes, etc to the Arm-Dev list (http://lists.centos.org/mailman/listinfo/arm-dev) for discussion and acceptance. We encourage vendors to come and join this effort, we have a loose organization focused on the alternative architectures build process and welcome interaction at the group level. Please get in touch with me (jperrin(a)centos.org) or K Singh ( kbsingh(a)centos.org ) to find out more details. The wider CentOS Ecosystem is also welcome to engage with us, both at the project and code level. If you are working with a project that interfaces, manages or develops on top of CentOS, specially in the virtualization, cloud, container and infrastructure management areas - we would love to have you guys get involved. While we don't have a lot of resources, we are working with a few vendors to build up a community resource pool that we would encourage other projects to share their development, testing and delivery around CentOS Linux for aarch64. -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77

1 0

CentOS 7 ARMv7 build status
by Fabian Arrotin 25 May '15

25 May '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've been busy on various things (including personal and family related issues) but I had some time to work on the plague build farm. After a discussion with Johnny, KB and Jim, we thought that it would be a good idea to try to focus first on a "self-contained" buildroot, and only then trying to rebuild the 7.1503 SRPMS against that buildroot, and not against F19/F20 (there will be some issues that will need to be solved though) I got a "self-contained" buildroot, rebuilt from 7.1503 packages, and I started with gcc, then glibc, then kernel (4.0.0-1, for compat reason with aarch64), and each time repodata was regenerated , so glibc has been rebuilt with gcc from 7.1.1503, etc .. The current c7-buildroot is here : http://armv7.dev.centos.org/repodir/c7-buildroot/ Then I put all the 7.1503 in the queue, and target name being c7-pass-1 , and the built packages are located here : http://armv7.dev.centos.org/repodir/c7-pass-1/ As plague-server required mod_python (deprecated now) we don't have any Web UI people can have a look at. But I created a "quick-and-dirty" script that gathers information from the mysql DB, and outputs that here : - - Packages in the current queue : http://armv7.dev.centos.org/queue.html - - Packages in a "failed" status : http://armv7.dev.centos.org/report.html (with link to the log files) Those pages are generated every 5 minutes, through a cron job. Now that we have something that can be used, I'll work on the access for contributors (two names are on my list). Actually, I'm also using the list of packages in failed status, to requeue those at the end, automatically. A best option would be to do that in a "clever" way, so trying to build a map of BuildRequires: and so which package would need to be built before another one, but my time is limited at the moment ( <hint> welcome ! </hint> ) I'm not expecting that to work for a complete and final tree though. So we'll have to have a look at the build logs, and sometimes we'll probably have to use a specific mock config file for one or two packages (or even a "patch" will be needed too) so the best/easiest/fastest will probably be to do that "locally" and not use plague (even if using the same build nodes) I had to exclude some packages from the queue, as armv7hl was excluded, but we can probably investigate if that can be built or not ... I guess people don't want me to spam the list every day with a long list of packages still in the queue :-) , so everybody can have a look at the website. If you have brilliant ideas, opinions, etc .. feel free to comment and participate. Sorry if that took more time that what I was expecting ... Kind Regards - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlVdySwACgkQnVkHo1a+xU6x6ACdGbZrnpCpJAxaNkezmSnQreiz iIAAnAlK1zMJ3BRq+3TsA1wbe0HlAnBt =elV4 -----END PGP SIGNATURE-----

4 4

opening up the armv7hl plague builders (was plague farm)
by Fabian Arrotin 19 May '15

19 May '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there ! We've all been busy on various things in parallel, but I wanted to give a status update to the list, about those armv7hl nodes that we can use to bootstrap/build CentOS 7. I just tested that the plague setup was running fine (so basically plague-server accepting jobs, and distributing those jobs amongs the builders nodes). We'd like now to open access to that plague build farm. I've just started a wiki page dedicated to this (http://wiki.centos.org/SpecialInterestGroup/AltArch/Arm32) containing some basic info on how to install and configure plague-client. We still have to discuss a good target/mock config files naming convention, including which repo are already available for dev/users. As a reminder, those nodes are currently running Fedora 21, and as plague WebUI needed mod_python, but not available anymore, we currently have no http/web ui that people can have a look at. OTOH, plague-server now sends the build logs/reports fine, and everybody can access the repodata/files/build logs at the following location (just using mod index for now) : http://armv7.dev.centos.org/repodir (for the built packages, including repodata) http://armv7.dev.centos.org/rpmbuild (for the log files) As an example, I submitted blindly all CentOS 7.0.1406 SRPMS to plague, using a f19 as buildroot. If we consider gcc : - - build log is available at http://armv7.dev.centos.org/rpmbuild/centos-f19-7-0-arm/515-gcc-4.8.2-16.el… - - artifact/rpm[s] are available at http://armv7.dev.centos.org/repodir/centos-f19-7-0-arm/gcc/4.8.2-16.el7/arm… If you need/want access, feel free to discuss that on this list, but also to create a bug report on https://bugs.centos.org, in the Buildsys project, category "community buildsys - arm32" Let's discuss what would be the best option for the target names/mock config files, and I can then let $cfgmgmt distribute that to server/builders. Happy Monday ! :-) - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlVQmxsACgkQnVkHo1a+xU4NmACeObf3iINOAUo7sC8k99H+DmlE B6cAmwQsSsTy6+dLqI4OijOUAEpSXUqm =DXgQ -----END PGP SIGNATURE-----

5 6

best kernel for armv7hl ?
by cc35359 gma 13 May '15

13 May '15

Fabian, I dont normally travel to these CentOS mailing lists, however, I wanted to mention about how I shoved Fedora Rawhide on a number of raspberry pis, because i think it would be a highly advantageous idea to push out at least a minimal image for the raspberry pi with the armv7 release for CentOS 7. If not that, at least have a clear path for those wanting it. In my adventures with rawhide on the raspis, i've found that the best way to handle the hardware is by using the kernel actually distributed by the raspi foundation, versus compiling my own. unfortunately there are a few broadcom pieces that make it difficult. In order to get rawhide running, it was a very simple process. 1. mount the fedora image 2. make an sd card paritioned how you want it (i dont use swap on sd card, so just 500 mb for /boot, and the rest for /. 3. rsync the data to the sd card, except the boot. 4. copy the boot directory from the raspi's git with the necessary firmware. 5. copy the kernel libraries. 6. i created a dracut initrd because i needed to have dm-crypt available because i normally encrypt the / partition myself. 7. modify fstab, boot.txt, cmdline.txt as necessary 8. boot, and its magic. I dont mind repeating the process for a centos image if help is needed, perhaps creating a scripted method to generate the images for the future would be something to look into. So that was a lot of rambling, but long story short, i can assist you with a raspberry pi image based on my fedora creations if we feel that centos can provide such an image. otherwise once the armv7 packages are ready, i can create documentation and a potential "offsite" image if there are legal reasons for not supplying it. thanks for listening, -David

2 3

← Newer
1
...
62
63
64
65
66
67
68
69
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Arm-dev