wpi3945 driver bug?

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

wpi3945 driver bug?

Lontronics Mailinglist account
I am using the wpi3945 driver with the latest wpi-firmware (2.4.14). When I am not using my wireless connection for some time, because the laptop is staying switched on and unused for some time, I do get a wireless time-out.
The OpenBSD is Obsd-current snap 20-07-07, but the issue was already there as long as I am using Obsd (about three months now).

Is this a driver bug or can it be solved another way?

Jan

Reply | Threaded
Open this post in threaded view
|

Re: wpi3945 driver bug?

damien.bergamini
| I am using the wpi3945 driver with the latest wpi-firmware
| (2.4.14). When I am not using my wireless connection for some
| time, because the laptop is staying switched on and unused for
| some time, I do get a wireless time-out.

What is a "wireless time-out"?
It is normal that the access point deassociates idle stations.
But the wpi(4) driver should reassociate immediately.

Damien

| The OpenBSD is Obsd-current snap 20-07-07, but the issue was
| already there as long as I am using Obsd (about three months now).
|
| Is this a driver bug or can it be solved another way?
|
| Jan

Reply | Threaded
Open this post in threaded view
|

Re: wpi3945 driver bug?

Peter Nicolai Mathias Hansteen
"Damien Bergamini" <[hidden email]> writes:

> But the wpi(4) driver should reassociate immediately.

And it does, most of the time.  For one reason or another, at
semi-random intervals I get

Jul 23 08:06:49 thingy /bsd: wpi0: fatal firmware error
Jul 23 08:06:50 thingy /bsd: wpi0: timeout waiting for adapter to initialize
Jul 23 08:06:50 thingy /bsd: wpi0: could not load firmware

Less often now (I tend to run latest snapshots, too lazy to do real
-current most times), but it still happens, and sometimes AFAICS this
leads to loss of link if not complete deassociation.  Usually fixable
with a new ifconfig wpi0 up (mumble) && dhclient wpi0, though.  I've
seen this on all revs since I got the machine (Thinkpad R60) in
October last.

If I can help debug this I'd be more than happy to.

- P
--
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://www.blug.linux.no/rfc1149/ http://www.datadok.no/ http://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.

Reply | Threaded
Open this post in threaded view
|

Re: wpi3945 driver bug?

Reyk Floeter-2
In reply to this post by damien.bergamini
On Mon, Jul 23, 2007 at 08:29:04AM +0200, Damien Bergamini wrote:
> | I am using the wpi3945 driver with the latest wpi-firmware
> | (2.4.14). When I am not using my wireless connection for some
> | time, because the laptop is staying switched on and unused for
> | some time, I do get a wireless time-out.
>
> What is a "wireless time-out"?

i get another type of timeout in my ThinkPad T61, the wireless doesn't
work:

wpi0 at pci2 dev 0 function 0 "Intel PRO/Wireless 3945ABG" rev 0x02: irq 11, MoW2, address 00:19:d2:97:24:61

ifconfig wpi0 up

wpi0: timeout waiting for thermal sensors calibration

(i'm using the f/w package 2.14.4 as proposed by the manpage in -current)

reyk

Reply | Threaded
Open this post in threaded view
|

Re: wpi3945 driver bug?

damien.bergamini
That is a different problem.
It happens when the wireless button that enables/disables the radio
has not been pushed, or if it is an ACPI-only button or if it's a
software switch that needs some vendor-specific driver to actually
enable the radio.

Damien


> i get another type of timeout in my ThinkPad T61, the wireless doesn't
> work:
>
> wpi0 at pci2 dev 0 function 0 "Intel PRO/Wireless 3945ABG" rev 0x02: irq 11,
> MoW2, address 00:19:d2:97:24:61
>
> ifconfig wpi0 up
>
> wpi0: timeout waiting for thermal sensors calibration
>
> (i'm using the f/w package 2.14.4 as proposed by the manpage in -current)
>
> reyk

Reply | Threaded
Open this post in threaded view
|

Re: wpi3945 driver bug?

Reyk Floeter-2
On Mon, Jul 23, 2007 at 12:08:07PM +0200, [hidden email] wrote:
> That is a different problem.
> It happens when the wireless button that enables/disables the radio
> has not been pushed, or if it is an ACPI-only button or if it's a
> software switch that needs some vendor-specific driver to actually
> enable the radio.
>

ah, i found the little button on the front, thanks! (i didn't have
that on my old thinkpad). now it works...

sorry for this,
reyk