I have encountered a defect that I think was caused by an update to drivers made on or after 2024-08-04.
So I'm looking for the easiest way to downgrade my drivers to previously installed versions, for testing purposes.
Specifically, I would like to revert changes to the firmware-brcm80211_20230625-2+rpt3_all.deb package, which was created on 2024-08-04 (so must have been very recently updated). I applied an auto-update to raspberry pi firmware a couple of days ago, and I have reason to believe that update caused my WiFi Direct code to stop working.
I'm thinking there's a master package that includes the new drivers as a sub-package -- a package with the name somewhere along the lines of "Rasperry Pi firmware", or "Raspberry pi boot image". Or perhaps there's a way to get the bootloader to run an older inittramfs image.
The intiramfs image definitely contains the driver in question. Downgrading the driver didn't have any effect until I also updated initramfs images.
Unfortunately, I overzealously rebuilt ALL the initramfs images ('sudo build-initframfs -u', seemed very reasonable until it rebuilt ALL of my initframfs images, including those belonging to previous firmware updates). So if there's a bootloader option, I'm still going to need a way to downgrade and install correct initramfs images on either this damaged system, or on a clean install.
Details of the problem, in the improbable case that anyone has specific insight into this issue:
I've tracked the issue down to a call that wpa_supplicant makes, as one of the very last steps in bringing up a Wiif P2p Interface. wpa_supplicant asks the nl80211 driver to operate a register a new interface in WIFI P2P MODE. The driver returns an error message:
Sep 05 14:39:47 raspberrypi wpa_supplicant[667]: nl80211: kernel reports: Registration to specific type not supported
Probing the driver from the commandline indicates that the driver very much does support P2P operations. So this isn't a case of Broadcom just abandaning support for P2P altogether.
Excuses in advance if I'm not using terminology correctly here. Despite having spent months rooting through wpa_supplicant/Network Manager source code to get this solution to work on bookworm in the first place, I am still deeply uncomfortable in this level of Linux detail and operation. (It took me months to get it to work in the first place on "buster", and then "bookworm" and the Network Manager stack required more months of work and a complete rewrite of the original implementation. To get taken down again by a driver update that's going to require debugging through kernel driver sources is..... terrifyingly outside of my comfort zone.
So I'm looking for the easiest way to downgrade my drivers to previously installed versions, for testing purposes.
Specifically, I would like to revert changes to the firmware-brcm80211_20230625-2+rpt3_all.deb package, which was created on 2024-08-04 (so must have been very recently updated). I applied an auto-update to raspberry pi firmware a couple of days ago, and I have reason to believe that update caused my WiFi Direct code to stop working.
I'm thinking there's a master package that includes the new drivers as a sub-package -- a package with the name somewhere along the lines of "Rasperry Pi firmware", or "Raspberry pi boot image". Or perhaps there's a way to get the bootloader to run an older inittramfs image.
The intiramfs image definitely contains the driver in question. Downgrading the driver didn't have any effect until I also updated initramfs images.
Unfortunately, I overzealously rebuilt ALL the initramfs images ('sudo build-initframfs -u', seemed very reasonable until it rebuilt ALL of my initframfs images, including those belonging to previous firmware updates). So if there's a bootloader option, I'm still going to need a way to downgrade and install correct initramfs images on either this damaged system, or on a clean install.
Details of the problem, in the improbable case that anyone has specific insight into this issue:
I've tracked the issue down to a call that wpa_supplicant makes, as one of the very last steps in bringing up a Wiif P2p Interface. wpa_supplicant asks the nl80211 driver to operate a register a new interface in WIFI P2P MODE. The driver returns an error message:
Sep 05 14:39:47 raspberrypi wpa_supplicant[667]: nl80211: kernel reports: Registration to specific type not supported
Probing the driver from the commandline indicates that the driver very much does support P2P operations. So this isn't a case of Broadcom just abandaning support for P2P altogether.
Excuses in advance if I'm not using terminology correctly here. Despite having spent months rooting through wpa_supplicant/Network Manager source code to get this solution to work on bookworm in the first place, I am still deeply uncomfortable in this level of Linux detail and operation. (It took me months to get it to work in the first place on "buster", and then "bookworm" and the Network Manager stack required more months of work and a complete rewrite of the original implementation. To get taken down again by a driver update that's going to require debugging through kernel driver sources is..... terrifyingly outside of my comfort zone.
Statistics: Posted by rerdavies — Thu Sep 05, 2024 10:20 pm — Replies 0 — Views 18