Discussion:
NetBSD -CURRENT / iwn firmware error
(too old to reply)
Victor Dorneanu
2010-01-13 11:49:41 UTC
Permalink
Hi everybody!

I just installed NetBSD -CURRENT (5.99.23) and realized that iwn isn't
working properly.

# ifconfig iwn0 up

returns:

Jan 13 12:04:42 BlackTiny /netbsd: iwn0: fatal firmware error
Jan 13 12:04:42 BlackTiny /netbsd: firmware error log:
Jan 13 12:04:42 BlackTiny /netbsd: program counter = 0x000161C0
Jan 13 12:04:42 BlackTiny /netbsd: source line = 0x00000445
Jan 13 12:04:42 BlackTiny /netbsd: error data = 0x0000044500000000
Jan 13 12:04:42 BlackTiny /netbsd: branch link = 0x00016162000161D4
Jan 13 12:04:42 BlackTiny /netbsd: interrupt link = 0x000006BA00000000
Jan 13 12:04:42 BlackTiny /netbsd: time = 11257
Jan 13 12:04:42 BlackTiny /netbsd: driver status:
Jan 13 12:04:42 BlackTiny /netbsd: tx ring 0: qid=0 cur=0 queued=0
Jan 13 12:04:42 BlackTiny /netbsd: tx ring 1: qid=1 cur=0 queued=0
Jan 13 12:04:42 BlackTiny /netbsd: tx ring 2: qid=2 cur=0 queued=0
Jan 13 12:04:42 BlackTiny /netbsd: tx ring 3: qid=3 cur=0 queued=0
Jan 13 12:04:42 BlackTiny /netbsd: tx ring 4: qid=4 cur=9 queued=0
Jan 13 12:04:42 BlackTiny /netbsd: tx ring 5: qid=5 cur=0 queued=0
Jan 13 12:04:42 BlackTiny /netbsd: tx ring 6: qid=6 cur=0 queued=0
Jan 13 12:04:42 BlackTiny /netbsd: tx ring 7: qid=7 cur=0 queued=0
Jan 13 12:04:42 BlackTiny /netbsd: tx ring 8: qid=8 cur=0 queued=0
Jan 13 12:04:42 BlackTiny /netbsd: tx ring 9: qid=9 cur=0 queued=0
Jan 13 12:04:42 BlackTiny /netbsd: tx ring 10: qid=10 cur=0 queued=0
Jan 13 12:04:42 BlackTiny /netbsd: tx ring 11: qid=11 cur=0 queued=0
Jan 13 12:04:42 BlackTiny /netbsd: tx ring 12: qid=12 cur=0 queued=0
Jan 13 12:04:42 BlackTiny /netbsd: tx ring 13: qid=13 cur=0 queued=0
Jan 13 12:04:42 BlackTiny /netbsd: tx ring 14: qid=14 cur=0 queued=0
Jan 13 12:04:42 BlackTiny /netbsd: tx ring 15: qid=15 cur=0 queued=0
Jan 13 12:04:42 BlackTiny /netbsd: rx ring: cur=10
Jan 13 12:04:42 BlackTiny /netbsd: 802.11 state 1


Does anybody experience the same issue and has a solution for this?! I
also downloaded the latest iwn firmware
(http://damien.bergamini.free.fr/packages/openbsd/) and replaced the old
one in /usr/pkg/libdata/if_iwn/. But no difference...

Thank you in advance.
--
Victor Dorneanu

Contact
- Web/Blog: http://dornea.nu

GnuPG information
- KeyID = 0xD20870F4 (pgp.mit.edu)
- Key fingerprint = DD6B 5E09 242F 7410 3F90 492A 4CBA FD13 D208 70F4


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Victor Dorneanu
2010-01-13 16:49:56 UTC
Permalink
I can only report that it worked (and still does) in 5.99.7, even if the
performance is poor (but that's a known issue of the Bergamini(-derived)
iwn(4), apparently). I might have time to upgrade that laptop in a week
or two though, so I can test then.
Cheers,
Oh.. BTW: Which iwn are you using? Intel 4965/5000/... ?!

# lspci
03:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)


It would be great if somebody could report sth related to Intel 4965 AGN.
--
Victor Dorneanu

Contact
- Web/Blog: http://dornea.nu

GnuPG information
- KeyID = 0xD20870F4 (pgp.mit.edu)
- Key fingerprint = DD6B 5E09 242F 7410 3F90 492A 4CBA FD13 D208 70F4


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Thomas E. Spanjaard
2010-01-13 16:35:44 UTC
Permalink
Post by Victor Dorneanu
I just installed NetBSD -CURRENT (5.99.23) and realized that iwn isn't
working properly.
Does anybody experience the same issue and has a solution for this?! I
also downloaded the latest iwn firmware
(http://damien.bergamini.free.fr/packages/openbsd/) and replaced the old
one in /usr/pkg/libdata/if_iwn/. But no difference...
I can only report that it worked (and still does) in 5.99.7, even if the
performance is poor (but that's a known issue of the Bergamini(-derived)
iwn(4), apparently). I might have time to upgrade that laptop in a week
or two though, so I can test then.

Cheers,
--
Thomas E. Spanjaard
***@netphreax.net
***@deepbone.net
Thomas E. Spanjaard
2010-01-13 23:24:14 UTC
Permalink
Post by Victor Dorneanu
Oh.. BTW: Which iwn are you using? Intel 4965/5000/... ?!
# lspci
03:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN [Kedron] Network Connection (rev 61)
It would be great if somebody could report sth related to Intel 4965 AGN.
4965AGN in a Lenovo ThinkPad X61.

Cheers,
--
Thomas E. Spanjaard
***@netphreax.net
***@deepbone.net
Victor Dorneanu
2010-01-14 11:03:30 UTC
Permalink
Post by Thomas E. Spanjaard
4965AGN in a Lenovo ThinkPad X61.
Cheers,
Thats strange. I have the same machine here: Thinkpad x61. BTW: Which
firmware version do you use?
--
Victor Dorneanu

Contact
- Web/Blog: http://dornea.nu

GnuPG information
- KeyID = 0xD20870F4 (pgp.mit.edu)
- Key fingerprint = DD6B 5E09 242F 7410 3F90 492A 4CBA FD13 D208 70F4


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Thomas E. Spanjaard
2010-01-16 14:12:07 UTC
Permalink
Post by Victor Dorneanu
Post by Thomas E. Spanjaard
4965AGN in a Lenovo ThinkPad X61.
Thats strange. I have the same machine here: Thinkpad x61. BTW: Which
firmware version do you use?
iwn-firmware-4.44.1.20

Cheers,
--
Thomas E. Spanjaard
***@netphreax.net
***@deepbone.net
Victor Dorneanu
2010-01-18 09:30:40 UTC
Permalink
Post by Thomas E. Spanjaard
iwn-firmware-4.44.1.20
Cheers,
This is really strange. Which arch do you use? I'm currently using AMD64.
--
Victor Dorneanu

Contact
- Web/Blog: http://dornea.nu

GnuPG information
- KeyID = 0xD20870F4 (pgp.mit.edu)
- Key fingerprint = DD6B 5E09 242F 7410 3F90 492A 4CBA FD13 D208 70F4


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Thomas E. Spanjaard
2010-01-19 01:25:07 UTC
Permalink
Post by Victor Dorneanu
Post by Thomas E. Spanjaard
iwn-firmware-4.44.1.20
This is really strange. Which arch do you use? I'm currently using AMD64.
Also amd64 :).

Cheers,
--
Thomas E. Spanjaard
***@netphreax.net
***@deepbone.net
Loading...