On Sat, Jun 25, 2022 at 10:34:59PM +0100, piorunz wrote: > On 25/06/2022 22:13, Bijan Soleymani wrote: > > On 6/25/2022 5:05 PM, piorunz wrote: > > > On 25/06/2022 22:01, Bijan Soleymani wrote: > > > > > > > Unfortunately in this case that might not work. > > > > > > > > The file that is needed is wl.ko > > > > > > That's what dmesg says? Can you copy entire line here? > > > > I think the dmesg output is of the form > > > > [time] wl: ... > > > > I guess between that wl kernel module and the output of lspci you could > > find the package through apt-file and apt-cache. > > > > Bijan > > > Usually it says something like this: > > 9.826410] rtl8821ae 0000:05:00.0: Direct firmware load for > rtlwifi/rtl8821aefw_29.bin failed with error -2 > [ 9.826420] rtl8821ae 0000:05:00.0: firmware: failed to load > rtlwifi/rtl8821aefw.bin (-2) Ah, but that's when you already have the driver (rtl8821ae), and this driver looks for the firmware to push to the network card (that would be xxxx.bin). The driver is complaining in dmesg that it can't find the firmware. If I understand the original case, wl, the whole kernel driver is missing and can only be compiled at the user's site for license reasons. That's where DKMS comes in. There's no driver which can complain in dmesg. Cheers -- t
Attachment:
signature.asc
Description: PGP signature