You are not logged in.

#1 2022-01-21 21:15:42

levi
Moderator
From: Yorkshire, UK
Registered: 2018-06-16
Posts: 1,179

Maintenance work required to keep your machines booting?

https://archlinux.org/news/linux-firmwa … splitting/

Sounds like we'll need to install some archlinux32 specific kernel packages for our systems.  Are those ready yet?  Perhaps the systems will still boot but with broken audio or wifi or something.


Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.

Offline

#2 2022-01-22 09:00:59

abaumann
Administrator
From: Zurich
Registered: 2019-11-14
Posts: 810
Website

Re: Maintenance work required to keep your machines booting?

Good observation, I checked first all kernels (so we don't end up in a non-booting system):

core/linux:
config.i486:CONFIG_FW_LOADER_COMPRESS=y
config.i686:CONFIG_FW_LOADER_COMPRESS=y
config.pentium4:CONFIG_FW_LOADER_COMPRESS=y

extra/linux-pae:
CONFIG_FW_LOADER_COMPRESS=y

extra/linux-olpc-xo1 (affected only OLPC-XO-1 and the Wifi usb8xxx driver, I suppose - which should be in a linux-firmware-olpc-xo-1 package maybe anyway):
fixed in 775559e12d6f033da05dca6d34a1f375fa05c475

extra/linux-zen:
CONFIG_FW_LOADER_COMPRESS=y

For the firmware packages themselves:

https://bugs.archlinux.org/task/72559

https://archlinux.org/packages/?sort=&q … =&flagged=

any    Core    linux-firmware    20220119.0c6a7b3-2    Firmware files for Linux    2022-01-21   
any    Core    linux-firmware-bnx2x    20220119.0c6a7b3-2    Firmware files for Linux - bnx2x / Firmware for Broadcom NetXtreme II 10Gb ethernet adapters    2022-01-21   
any    Core    linux-firmware-liquidio    20220119.0c6a7b3-2    Firmware files for Linux - liquidio / Firmware for Cavium LiquidIO server adapters    2022-01-21   
any    Core    linux-firmware-marvell    20220119.0c6a7b3-2    Firmware files for Linux - marvell / Firmware for Marvell devices    2022-01-21   
any    Core    linux-firmware-mellanox    20220119.0c6a7b3-2    Firmware files for Linux - mellanox / Firmware for Mellanox Spectrum switches    2022-01-21   
any    Core    linux-firmware-nfp    20220119.0c6a7b3-2    Firmware files for Linux - nfp / Firmware for Netronome Flow Processors    2022-01-21   
any    Core    linux-firmware-qcom    20220119.0c6a7b3-2    Firmware files for Linux - qcom / Firmware for Qualcomm SoCs    2022-01-21   
any    Core    linux-firmware-qlogic    20220119.0c6a7b3-2    Firmware files for Linux - qlogic / Firmware for QLogic devices    2022-01-21   
any    Core    linux-firmware-whence

So I'll force the build of those additional firmware packages.

I think, unless you have one of the hardware listed above, everything is still in linux-firmware as before.

Then we should be fine (TM = aka final last words). :-)

Offline

#3 2022-01-22 09:15:07

abaumann
Administrator
From: Zurich
Registered: 2019-11-14
Posts: 810
Website

Re: Maintenance work required to keep your machines booting?

Yep, the buildmaster just picks up linux-firmware:

linux-firmware 6e98bea0d686d489c2a66fd1d907ddf5c99dbac7 3da8128a6649d579877d5192ab96175eb23cb18d core

Currently the whole "update-from-upstream" process seems broken..

Offline

#4 2022-01-22 17:39:28

levi
Moderator
From: Yorkshire, UK
Registered: 2018-06-16
Posts: 1,179

Re: Maintenance work required to keep your machines booting?

abaumann wrote:

I think, unless you have one of the hardware listed above, everything is still in linux-firmware as before.

The way I read it is all of those devices are capable of running Arch64, so we don't absolutely need to support them.

If this is limited to only those devices because they do something weird, I'd have thought the 32-bit parts are less lilkely to be weird in the same way. Unless the're weird in that they're still connecting some device or other over a PCI old school bus or something, because they're early 64-bit devices, I suppose.


Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.

Offline

#5 2022-01-22 20:23:05

abaumann
Administrator
From: Zurich
Registered: 2019-11-14
Posts: 810
Website

Re: Maintenance work required to keep your machines booting?

Ah, that's good news, thanks for checking. :-)

Offline

#6 2022-01-22 22:07:53

levi
Moderator
From: Yorkshire, UK
Registered: 2018-06-16
Posts: 1,179

Re: Maintenance work required to keep your machines booting?

Well there is apparently an upstream package called amd-ucode, but it seems that's preexisting, so if you've got that already you still need it and if not you don't.

Yes, it seems reading it with an improve git diff head on it seems that's mainly included in the context lines.  The only new packages are for weird things like if you're running archlinux on a switch or something.


Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.

Offline

#7 2022-01-23 08:48:40

abaumann
Administrator
From: Zurich
Registered: 2019-11-14
Posts: 810
Website

Re: Maintenance work required to keep your machines booting?

amd-ucode and intel-ucode are microcode patches for AMD and Intel CPUs, usually only for newer models.
I just noticed that the naming conventions changed from intel_ucode.img to intel-ucode.img, so, as I'm updating
the ISO, this is something to be taken into account.

Also here: I doubt that any 32-bit CPUs got microcode updates from the respective vendor..

Offline

#8 2022-01-23 17:02:26

levi
Moderator
From: Yorkshire, UK
Registered: 2018-06-16
Posts: 1,179

Re: Maintenance work required to keep your machines booting?

Yes, but the linux-firmware packages don't contain microcode do they?  They contain x86 binary driver blobs for peripherals in the main.  The point of confusion for me where I conflated these two types of packages was that they're both apparently built by the same PKGBUILD.


Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.

Offline

#9 2022-01-24 06:37:48

abaumann
Administrator
From: Zurich
Registered: 2019-11-14
Posts: 810
Website

Re: Maintenance work required to keep your machines booting?

This is indeed rather confusing:

https://archlinux.org/packages/core/any/linux-firmware/
https://archlinux.org/packages/extra/any/intel-ucode/

amd-ucode, linux-firmware-bnx2x, linux-firmware-liquidio, linux-firmware-marvell, linux-firmware-mellanox, linux-firmware-nfp, linux-firmware-qcom, linux-firmware-qlogic, linux-firmware-whence

The AMD microcode is in the firmware package, the Intel microcode in its own package in extra.

We have to ask upstream, why this is the case.

On the binary level this is not relevant, as the split packages are their own independent entities.

Offline

Board footer

Powered by FluxBB