Still struggling to deal with the ongoing broadcom issues that I, as well as others, have. Most likely I prematurely closed issue, as it seems that a larger Silverblue/Aurora mis-configuration issue is the culprit.
Can someone explain what the ujust action “configure-broadcom-wl” is doing in script “/usr/share/ublue-os/just/50-akmods.just” ?
When you run this action, the “Disable” section creates two files:
/etc/modules-load.d/broadcom-wl-blacklist.conf
/etc/modules-load.d/default-disable-broadcom-wl.conf
…this seems intended to blacklist the broadcom wifi module.
However, running the “Enable” action attempts to delete two different files, and leaves the above two files behind; these files remain after a reboot.
sudo rm -f /etc/modprobe.d/broadcom-wl-blacklist.conf
sudo rm -f /etc/modprobe.d/default-disable-broadcom-wl.conf
I can’t understand how this is expected to work. Can anyone explain? It seems like a typo, but perhaps not.
Also, I can see that the broadcom module “brcmfmac” is blacklisted by the system, and I cannot find any way to force it to load during boot.
]$ sudo modprobe --show-config | grep brcmfmac | grep -v alias
blacklist brcmfmac
]$ systemd-analyze cat-config modprobe.d | grep brcmfmac
blacklist brcmfmac
This module ( which I need to load ) is getting blacklisted here:
]$ cat /usr/lib/modprobe.d/broadcom-wl-blacklist.conf
# modules blacklisted for broadcom-wl
<snipped>
blacklist brcmfmac
It seems there is no way to prevent this blacklist, as this file is on part of the read-only file system. I have created a file in “/etc/modprobe.d/broadcom-wl-blacklist.conf” to install this module at boot time, but nothing happens.
Why is this module blacklisted here, and is there anyway to override this?
