Closed freedge closed 4 months ago
one workaround is to layer the qed-firmware package with sudo rpm-ostree install qed-firmware
then write a systemd service in this fashion
# https://unix.stackexchange.com/questions/229048/how-to-start-a-systemd-service-before-networking-starts
# https://github.com/coreos/fedora-coreos-tracker/issues/1746
[Unit]
Description=Reload qed firmware
DefaultDependencies=no
Before=network-pre.target
Wants=network-pre.target
Wants=systemd-modules-load.service local-fs.target
After=systemd-modules-load.service local-fs.target
Conflicts=shutdown.target
Before=shutdown.target
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStartPre=-/usr/sbin/modprobe -r qede
ExecStart=/usr/sbin/modprobe qede
[Install]
WantedBy=multi-user.target
@freedge Sorry for missing this! We will add back the firmware for the time being.
One question: you mention the NIC no longer works without the firmware blob. Is there any e.g. "reduced capacity" mode which allows it to work, or is it entirely non-functional without the file?
haha you were working on another ticket I opened :D
without the qed-firmware the NIC is entirely non functional, "ip link" does not show the interface. In practice you need to access the system from the console and reboot on the previous ostree entry.
The fix for this went into testing stream release 40.20240701.1.0
. Please try out the new release and report issues.
Describe the bug
after zincati upgrade from 40.20240504.3.0 to 40.20240519.3.0 , my server does not have network anymore
logs
Reproduction steps
Expected behavior
network up
Actual behavior
no network, Failed to find fw file - /lib/firmware/qed/qed_init_values_zipped-8.59.1.0.bin
System details
● fedora:fedora/x86_64/coreos/stable Version: 40.20240504.3.0 (2024-05-20T18:00:04Z) Commit: 72cf2f80ba1496d478e110d03e1199d9d21382840e96ffeddf4303eb040fbb55 GPGSignature: Valid signature by 115DF9AEF857853EE8445D0A0727707EA15B79CC