- automotive-sig - lists.centos.org

Weekly update on the automotive-sig
by Pierre-Yves Chibon 25 Feb '22

25 Feb '22

Good Morning Everyone, So here are some of the changes that we have worked on over the last few weeks: * We have worked on some documentation on how to integrate container images while building images. This documentation can be found at: https://sigs.centos.org/automotive/building/containers/ * We have worked with the CentOS infrastructure to allow using the flat dist-git layout in CBS. Announce: https://lists.centos.org/pipermail/centos-devel/2022-February/120223.html * We have started a discussion around the structure of the lookaside used in CentOS: https://lists.centos.org/pipermail/centos-devel/2022-February/120226.html * We have fixed our sample images to use the `kernel-automotive` package instead of the old `kernel-auto` package (oups!). This simple fix, fixes booting a graphical user interface on the raspberry pi 4 * We have refreshed our sample images available at: https://pingou.fedorapeople.org/images/ * We have expanded the documentation available at: https://sigs.centos.org/automotive/ with information about: * The use of content resolver to define the content * How to download the RPMs of interest to the automotive SIG Just a few notes about building images currently: - It looks like CentOS-Stream 9 may have a bug which prevents building image. This is known and being investigated, we'll just have to wait a little. - The rpi4 sample images mentioned above can boot a desktop environment using Wayland if the raspberry pi is configured to use ACPI. If the raspberry pi is configured to use device-tree, Wayland isn't starting correctly. Editing `/etc/gdm/custom.conf` to disable Wayland will make the session start with Xorg, which works fine. - Neptune itself segfaults on launch currently, this is also known and we're looking into it (likely simply needs a rebuild). Happy hacking! Pierre

1 0

Weekly update on the automotive-sig
by Pierre-Yves Chibon 17 Feb '22

17 Feb '22

Good Morning Everyone, First of all, apologies for the silence, it has been two weeks since we sent the last update, we need to get back into this habit :) So here are some of the changes that we have worked on over the last few weeks: * We have done quite a few changes on osbuild to allow building system images with container image pre-installed. This way you can build, say a qcow2 image, boot it in qemu and have `podman images` show you images directly. We can now integrate this with quadlet [1] and as a result have not only a container pre-installed but even automatically started at boot time! If you want to build an image with a container included, ensure you have the latest osbuild package from copr. * We have been working with the CentOS infrastructure to allow using the "flat" dist-git layout when building on CBS (CentOS BuildSystem: https://cbs.centos.org) This should be landing early next week, all tests * having passed in staging! * A few changes have been made to the automotive docs, including the addition on a doc on how to contribute to the automotive-sig repository. * We dropped weak package dependencies from the images built via the automotive-sig repository. This should speed up building the images as well as reduce their size * We have been working on a small project named "remote_builder" which aims is to make it easy for developers to (re)build their source RPM onto multiple hosts (of different architecture). It uses containers as the buildroot/build environment for the source rpm. Its documentation can be found at: https://remote-builder.readthedocs.io/ This is still somewhat work in progress but early developers are more than welcome to give it a try! Happy hacking, Pierre [1] https://github.com/containers/quadlet

1 0

Weekly update on the automotive-sig
by Alexander Larsson 21 Jan '22

21 Jan '22

Actually this is an update for the last two weeks, as there was no update last week. Things that happened last two weeks: * The build pipelines in the manifests dropped a bunch of packages that are not used by the images, such as filesystem support for xfs/squashfs and cdrom support. This makes the build smaller and faster and requires less packages to be supported. * There is a new makefile target extension "*.ext4" which creates an image similar to the normal one but without a multi-partition setup. This is useful on some boards where the boot happens in a non traditional way and all that is needed is the root filesystem. * There is a new makefile target "*.tar" which makes it easy to generate a tarballs containing the contents of what would otherwise be in image. * The makefiles now support passing strings with spaces in them in the DEFINES variable by escaping them with a backslash. * The two images "kernel_dev" and "osbuilder" were combined into a single "developer" image that has the content of the previous as well as some container tooling. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Alexander Larsson Red Hat, Inc alexl(a)redhat.com alexander.larsson(a)gmail.com

1 0

Alternative aarch64/arm64 development environments
by Eric Curtin 14 Jan '22

14 Jan '22

Hi Guys, I wrote a blog post describing and comparing Fedora on M1 macOS, Fedora on Android, Fedora on Raspberry Pi and Fedora on x86_64. CentOS runs on these platforms just as well. If curious see below: https://ericcurtin.wordpress.com/2022/01/14/more-than-a-pi-alternative-aarc… Is mise le meas/Regards, Eric Curtin

1 0

Weekly update on the automotive-sig
by Pierre-Yves Chibon 07 Jan '22

07 Jan '22

Good Morning Everyone, First of all, we would like to wish you all a very happy new year! May it give us the opportunity to meet with you all and see our group grow and succeed :) Here is a quick update of some of the things we have been working on this week: * Packaging Some of the libraries we have been using had been quickly packaged and made available in a copr repo. We figured it was time to have another look at them, polish their packaging and submit them to be included in Fedora and EPEL. * A container to (re)building the kernel's RPM We've been looking at ways to build a container with all the dependencies pre-installed to make it really easy to (re)build the kernel's RPM. We ended up with two methods: - One using OSBuild and the Makefile [1] This allows to build qcow2 or container images thus giving the possibility to use VM or container both with the same content - One using a more traditional approach based on a Dockerfile [2] For both approaches, once you are running the container, you can simply: - get a kernel source rpm (for example: https://cbs.centos.org/kojifiles/packages/kernel-auto/5.14.0/30.1.el9s/src/… ) - rpmbuild --rebuild kernel-auto-*.src.rpm Happy hacking, Pierre [1] https://gitlab.com/redhat/automotive/automotive-sig/-/merge_requests/97 [2] Location for that file is still being discussed but we can already make it available on this list if someone is interested/wants it earlier. Just say so :)

1 0

Status update on the automotive SIG
by Alexander Larsson 17 Dec '21

17 Dec '21

Things are slowing down now in the project with the holidays coming up, so this might be the last status report in a while, but here are some updates of what happened this week. * Building images in a VM The makefile that builds images now has support (enabled via make VM=1) to run the build in a virtual machine. This has some advantages, First it allows you to run the entire build as a non-privileged user, so no sudo is required, and it doesn't affect the host system. Secondly, it allows you to run the build in a software-emulated non-native architecture VM. For example, you can build an aarch64 image on an x86_64 machine. This is much slower than a native build, but not extremely so. For example, a raspberry pi4 build on my intel desktop takes about 30 minutes. This can be a nice way to e.g. kickstart a raspberry pi image. As part of this change, the makefile rules and the image filenames changed so that they now have the architecture name in them. * Non-UEFI booting raspberry pi images The "direct" version of the images is normally a direct-uefi boot, skipping over grub to be faster. On the raspberry pi however even direct-uefi isn't direct as the firmware is not natively uefi. Instead it was first loading a uefi binary, which then booted the kernel. This is now changed, so that by default (but you can disable it) it boots the kernel directly from the raspberry pi firmware. This makes cold boot times much faster, with boot-to-login going from 2 minutes to 30 seconds. * Neptune image updates There were various updates to the neptune images, which now support both wayland and x11, with new neptune full-screen session options in gdm. * Working on weekly builds We are working on producing weekly builds of the images.. Hopefully we will finish this soon and have the builds publically available, until then there are some manual builds here: https://pingou.fedorapeople.org/images/ * Issues with the raspberry pi images There are some known issues with the kernel graphics drivers in the current images for raspberry pis. The images in the above link should work, but if you build your own from the latest manifests you might run into issues with this graphics not working. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Alexander Larsson Red Hat, Inc alexl(a)redhat.com alexander.larsson(a)gmail.com

1 0

Updates to the automotive-sig
by Liora Milbaum 16 Dec '21

16 Dec '21

Good Morning/Afternoon/Evening Everyone, Here is a quick update on the work that has been done over this week in the automotive-sig repository by the Toolchain team, The product build pipeline was created. It is now triggered automatically when changes are pushed to the main branch, after merge requests are merged. It generates a yum repository which is based on the packages manifest file <https://gitlab.com/redhat/automotive/automotive-sig/-/blob/main/package_lis…> (aka lockfile). The yum repository is stored in an AWS S3 bucket - `auto-product-build` One can download the yum repository into the development environment by invoking the following command: (AWS credentials need to be configured locally to authenticate against AWS, but do not need special permissions, this bucket is configured with a public-read ACL, open to any authenticated AWS user) aws s3 cp s3://auto-product-build/latest/cs9 <your-local-directory> --recursive Note: Once changes land in the main branch, the bucket will become temporarily unavailable as the `latest` directory is recreated with the changed packages (this will be improved in future iterations) We welcome your feedback, Liora -- Liora Milbaum She - Her - Hers Product Owner, In-Vehicle Operating System, Software Supply Chain Senior Principal Software Engineer, Always Ready RHEL Red Hat Beyond Lead Red Hat <https://www.redhat.com/> Israel lmilbaum(a)redhat.com M: 054-656-0051 <0546560051> <https://red.ht/sig>

1 0

Status update on the automotive SIG
by Pierre-Yves Chibon 03 Dec '21

03 Dec '21

Good Morning Everyone, Here is a quick update on the work that have happened this week in the automotive-sig repository. * New image In addition to the two existing image (minimal and neptune) we have introduced a new image type: osbuilder which is meant to give anyone who wants, an easy way to run osbuild and thus build their own images. You will therefore find osbuild and its dependencies pre-installed on this image, but not the automotive-sig repository. * Sample images We have created a few images based on the manifests present in the automotive-sig repository. You can find them at: https://pingou.fedorapeople.org/images/ Installing them will be a matter of de-compressing them using `unxz <filename.xz>`, then flashing them onto a SD card (beware to change `/dev/sda` to your set-up): ``` dd if=<filenamed.img> of=/dev/sda status=progress bs=4M ``` These images and this location are temporary, in the coming weeks we will be looking at automating the building of these images and make them accessible via the documentation at: https://sigs.centos.org/automotive Happy hacking, Pierre

1 0

FYI: incoherence between sig.centos and wiki.centos
by Fulup Ar Foll 01 Dec '21

01 Dec '21

1 0

Status update on the automotive work
by Pierre-Yves Chibon 26 Nov '21

26 Nov '21

Good Morning Everyone, Here is a quick update on the work that have happened this week in the automotive-sig repository. * Makefile simplifying image builds There is a new Makefile in the git repository that does all the steps involved when building images. This is much easier to use and means the docs are simpler. For example, to build an ostree based neptune image targeting the Raspberry Pi 4, all you have to do is run `make cs9-rpi4-neptune-ostree.img`. Or, if you want to build a rpm-based qemu image, instead run `make cs9-qemu-neptune-regular.qcow2`. There are all sort of other features too, check out the website and/or `make help` for more information. The documentation on how to build images has been adjusted to rely on this Makefile: https://sigs.centos.org/automotive/building/ * More stream-lined templates With the help of the OSBuild team, a number of changes have landed to the osbuild-mpp pre-processing tool that our build workflow rely upon. Thanks to this, we have been able to stream-line and merge our templates. The template for the CS9 minimal image is now just 62 lines long, while the one for the neptune is 108 lines. Using either of these template you can still generate images for x86_64, aarch64, ostree-based, non-ostree-based, direct boot or grub-based boot. The new templates are in yaml format, not json. Not only is this more readable, but it also allows us to have comments in the files. Note: Make sure you update to the very latest osbuild rpm (from copr [2]) for this to work. * New kernel A new kernel-auto package has landed in the automotive testing repository [1]. That update brings along with it improved support for the raspberry pi 4 as well as for the Nvidia Jetson boards. Note: with this kernel we are now able to build images on CS9 itself * More RT packages In order to make most of the RT features of the kernel-auto as few extra packages have been added to the automotive testing repository, namely: realtime-setup, realtime-tests and tuned with its tuned-profiles-realtime sub-package. Happy hacking, Alex & Pierre [1] The "release" repositories are currently frozen for CS9, so the SIG can only push up to the testing repository which can be found at: https://buildlogs.centos.org/9-stream/automotive/ [2] https://copr.fedorainfracloud.org/coprs/g/osbuild/osbuild/

1 0

2025

2024

2023

2022

2021

automotive-sig