Hi,
Martin Husemann wrote:
> The message is bogus, it has nothing to do with autoconfiguration.
Misleading.. I was wondering what autoconfiguration had to be done after
everything was connected.
>
> "Fatal error" is a bit in the interrupt cause register of the intel
> chipset. The driver can
El mar, 7 may 2024 a las 11:13, Martin Husemann () escribió:
>
> On Tue, May 07, 2024 at 08:16:18AM +, Riccardo Mottola wrote:
> > [ 3574.054462] iwi0: autoconfiguration error: fatal error
>
> The message is bogus, it has nothing to do with autoconfiguration.
>
> "Fatal error" is a bit in the
On Tue, May 07, 2024 at 08:16:18AM +, Riccardo Mottola wrote:
> [ 3574.054462] iwi0: autoconfiguration error: fatal error
The message is bogus, it has nothing to do with autoconfiguration.
"Fatal error" is a bit in the interrupt cause register of the intel
chipset. The driver can not do
Hi,
Riccardo Mottola wrote:
> dmesg | grep iwi0
> [ 1.005536] iwi0 at pci2 dev 2 function 0: Intel PRO/Wireless LAN
> 2200BG Mini-PCI Adapter (rev. 0x05)
> [ 1.005536] iwi0: interrupting at irq 11
> [ 1.005536] iwi0: 802.11 address 00:16:6f:0c:0f:59
> [ 3574.054462] iwi0:
Hi,
I upgraded my trusty Thinkpad to T30 to 10.0 and now most rough edges
have been sorted out.
Yesterday I connected it via WiFi, connected remotely to it, then went
to bed. Today I see the connection dropped and a green message on the
console.
Ifconfig says network down.
dmesg | grep iwi0
[
