'wiconfig <if> -D' failing with ioctl: Operation now in progress

[David Young]

Since updating to NetBSD 4.0_BETA2 (from NetBSD 3) I've
been unable to get wiconfig -D to work. I've tried with
ath0, rtw0, and iwi0 on two different machines.
In all cases the ioctl() SIOCGWAVELAN loop times out without
getting any result.
Increasing retries from 10 to 60 (sec) did not affect the result.
Is there anything I should be looking at to try to track this
down?

David,

Did it work with ath, rtw, and iwi on NetBSD 3? I did not think it did.
I only expect for it to work with wi. Everything other driver is
a toss-up.

I have been saying so for some time, but here we go again: NetBSD *really*
needs to borrow the 'list scan' functions from ifconfig in FreeBSD.
All of the kernel support should be in NetBSD already. Borrowing those
functions does not require any 802.11 expertise. Don't wait for me to
do it, I haven't the time or the interest.

Dave

[Pavel Cahyna]

Post by David Young

Since updating to NetBSD 4.0_BETA2 (from NetBSD 3) I've
been unable to get wiconfig -D to work. I've tried with
ath0, rtw0, and iwi0 on two different machines.
In all cases the ioctl() SIOCGWAVELAN loop times out without
getting any result.
Increasing retries from 10 to 60 (sec) did not affect the result.
Is there anything I should be looking at to try to track this
down?

David,
Did it work with ath, rtw, and iwi on NetBSD 3? I did not think it did.
I only expect for it to work with wi. Everything other driver is
a toss-up.

It works for me with ath and 3.99.20.

Pavel

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Liam J. Foy]

Post by David Young

Since updating to NetBSD 4.0_BETA2 (from NetBSD 3) I've
been unable to get wiconfig -D to work. I've tried with
ath0, rtw0, and iwi0 on two different machines.
In all cases the ioctl() SIOCGWAVELAN loop times out without
getting any result.
Increasing retries from 10 to 60 (sec) did not affect the result.
Is there anything I should be looking at to try to track this
down?

David,
Did it work with ath, rtw, and iwi on NetBSD 3? I did not think it did.
I only expect for it to work with wi. Everything other driver is
a toss-up.
I have been saying so for some time, but here we go again: NetBSD *really*
needs to borrow the 'list scan' functions from ifconfig in FreeBSD.
All of the kernel support should be in NetBSD already. Borrowing those
functions does not require any 802.11 expertise. Don't wait for me to
do it, I haven't the time or the interest.

I spoke to Sam regarding this and produced a patch set (based on
FreeBSD, of course). However, I am unable to do anything with the code
since I don't have a supported card according to Sam, so I just left it.

Not too sure where the code is now, but it didn't take long to fix up.

---
Liam J. Foy
<***@netbsd.org>



--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Liam J. Foy]

Post by Liam J. Foy

Post by David Young

Since updating to NetBSD 4.0_BETA2 (from NetBSD 3) I've
been unable to get wiconfig -D to work. I've tried with
ath0, rtw0, and iwi0 on two different machines.
In all cases the ioctl() SIOCGWAVELAN loop times out without
getting any result.
Increasing retries from 10 to 60 (sec) did not affect the result.
Is there anything I should be looking at to try to track this
down?

David,
Did it work with ath, rtw, and iwi on NetBSD 3? I did not think it did.
I only expect for it to work with wi. Everything other driver is
a toss-up.

It worked fine with ath on NetBSD 3. It would fail maybe one
time in a hundred or less.

Post by Liam J. Foy

Post by David Young
I have been saying so for some time, but here we go again: NetBSD *really*
needs to borrow the 'list scan' functions from ifconfig in FreeBSD.
All of the kernel support should be in NetBSD already. Borrowing those
functions does not require any 802.11 expertise. Don't wait for me to
do it, I haven't the time or the interest.

I spoke to Sam regarding this and produced a patch set (based on
FreeBSD, of course). However, I am unable to do anything with the code
since I don't have a supported card according to Sam, so I just left it.
Not too sure where the code is now, but it didn't take long to fix up.

If you might have the time and interest to look at this again,
what would it take to get a supported card to you - I'd be
happy to (within reason) order one online and ship to you.
--
David/absolute -- www.NetBSD.org: No hype required --

That's just it - it wouldn't take long at all really. Maybe a day?
Would be
better if someone just borrowed me, or someone else, a card sometime
soon.

---
Liam J. Foy
<***@netbsd.org>



--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Liam J. Foy]

Post by David Young

Since updating to NetBSD 4.0_BETA2 (from NetBSD 3) I've
been unable to get wiconfig -D to work. I've tried with
ath0, rtw0, and iwi0 on two different machines.
In all cases the ioctl() SIOCGWAVELAN loop times out without
getting any result.
Increasing retries from 10 to 60 (sec) did not affect the result.
Is there anything I should be looking at to try to track this
down?

David,
Did it work with ath, rtw, and iwi on NetBSD 3? I did not think it did.
I only expect for it to work with wi. Everything other driver is
a toss-up.
I have been saying so for some time, but here we go again: NetBSD *really*
needs to borrow the 'list scan' functions from ifconfig in FreeBSD.
All of the kernel support should be in NetBSD already. Borrowing those
functions does not require any 802.11 expertise. Don't wait for me to
do it, I haven't the time or the interest.

Quoting what Sam Leffler said:

"wi probably does not integrate properly with net80211. That's true on
freebsd at least. If you try something like ath, ral, atw, rtw, etc.
then it should work. Unfortunately many legacy drivers are not properly
integrated with net80211 and noone cares to fix them."


---
Liam J. Foy
<***@netbsd.org>



--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Liam J. Foy]

A fellow developer is going to borrow me a card. I'll look into
it ASAP.
---
Liam J. Foy
<***@netbsd.org>



--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Rui Paulo]

Post by Liam J. Foy
A fellow developer is going to borrow me a card. I'll look into
it ASAP.

Bringing in the ifconfig changes from FreeBSD isn't difficult, but if
you need any help, give me a call. I've imported other ifconfig/
net80211 params in the past.

--
Rui Paulo



--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Liam J. Foy]

Post by Rui Paulo

Post by Liam J. Foy
A fellow developer is going to borrow me a card. I'll look into
it ASAP.

Bringing in the ifconfig changes from FreeBSD isn't difficult, but
if you need any help, give me a call. I've imported other ifconfig/
net80211 params in the past.

Indeed. Thanks Rui!

---
Liam J. Foy
<***@netbsd.org>



--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Pierrick Brossin]

Since updating to NetBSD 4.0_BETA2 (from NetBSD 3) I've
been unable to get wiconfig -D to work. I've tried with
ath0, rtw0, and iwi0 on two different machines.

Works here on 4.99.5 using ath0 (but it breaks wpa_supplicant).

ath0 at pci5 dev 2 function 0
ath0: interrupting at ioapic0 pin 23, event channel 8
ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps
24Mbps 36Mbps 48Mbps 54Mbps
ath0: turboA rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps
54Mbps
ath0: mac 5.9 phy 4.3 radio 3.6
ath0: Use hw queue 1 for WME_AC_BE traffic
ath0: Use hw queue 0 for WME_AC_BK traffic
ath0: Use hw queue 2 for WME_AC_VI traffic
ath0: Use hw queue 3 for WME_AC_VO traffic
ath0: Use hw queue 8 for CAB traffic
ath0: Use hw queue 9 for beacons


-Pierrick Brossin


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de