This really is unfortunate, but the way you've tried to fix wouldn't
work in general:
- Not all drivers log in the same way (at least in the upstream kernel)
- Those messages may have been expired from the kernel message buffer
when mkinitramfs runs
- The firmware files requested by a driver
Hi,
I was trying to bisect the kernel, but I found a "strange" behavior:
when I rebuild the linux kernel from vanilla for 5.10.46, I don't see
the "phy#0" interface as output of "iw reg get" and hostapd doesn't work
on 5GHz.
Thus, I'm a bit lost on how to track down the issue… Any help would
Package: src:linux
Version: 5.14.12-1
Severity: normal
Hi,
After upgrading from linux-image-5.10.0-8-amd64, my access point stopped
working on the 5GHz band. It seems that the EEPROM country is ignored,
or misunderstood by the kernel. I have the following at module load:
oct. 15 23:42:21 bel
You won't believe me, but I was facing the same bug : the HW address was
wrong. Ok, that's not unbelievable, but what would you say if I told you
that I solved the problem by halting the machine, physically unplug it
from the power, and wait for 30 seconds, then plug it in again ?
Try it, you
4 matches
Mail list logo
