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