IWN driver (5000 & 5100 series)

[Nicolas]

Hello NetBSD users.

Someone working on the iwn driver for the Intel Pro Wireless 5000 and
5100 series support ?

Thanks in advance,
Niko.


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

[Christos Zoulas]

Post by Nicolas
Hello NetBSD users.
Someone working on the iwn driver for the Intel Pro Wireless 5000 and
5100 series support ?

I started merging changes from FreeBSD and abandoned it.

christos


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

[Manuel Bouyer]

Post by Christos Zoulas

Post by Nicolas
Hello NetBSD users.
Someone working on the iwn driver for the Intel Pro Wireless 5000 and
5100 series support ?

I started merging changes from FreeBSD and abandoned it.

I also started working on it; didn't finish due do limited time
and missing hardware in hands. From memory the driver did start
operation but the firmware was dying quickly.

[Jeremy C. Reed]

I tried your patch. I am on amd64 and had to patch a little due to:

../../../../dev/pci/if_iwn.c: In function 'iwn_set_timing':
../../../../dev/pci/if_iwn.c:3367: warning: format '%llu' expects type
'long long unsigned int', but argument 3 has type '__uint64_t'
../../../../dev/pci/if_iwn.c: In function 'iwn_read_firmware':
../../../../dev/pci/if_iwn.c:5178: warning: format '%d' expects type
'int', but argument 3 has type 'size_t'

I used PRIu64

DPRINTF(("timing bintval=%u, tstamp=%" PRIu64", init=%u\n",
ni->ni_intval, le64toh(cmd.tstamp), (uint32_t)(val - mod)));

and %zd

aprint_error_dev(sc->sc_dev,
"firmware file too short: %zd bytes\n", size);

hopefully that is correct.

I rebooted with new 5.0_RC3 but didn't see any change.

vendor 0x8086 product 0x4232 (miscellaneous network) at pci2 dev 0
function 0 not configured

I rebooted again (with the switch on front of laptop turned to on and that
made a light come on for the wireless) but still no change.

No extra device showed with "ifconfig -l".

Why is the pci_matchid list not used with "#if 0"? Why isn't the
PCI_PRODUCT_INTEL_PRO_WL_5100AGN_1 et cetera in the pcidevices? Is that
not needed?

(I added it to my pcidevs and regenerated pcidevs.h but then realized
maybe it is not used so didn't rebuild, install, and reboot yet.)

Note I didn't install any firmware yet, but didn't see any kernel output
about that.

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

[Manuel Bouyer]

Post by Jeremy C. Reed
../../../../dev/pci/if_iwn.c:3367: warning: format '%llu' expects type
'long long unsigned int', but argument 3 has type '__uint64_t'
../../../../dev/pci/if_iwn.c:5178: warning: format '%d' expects type
'int', but argument 3 has type 'size_t'
I used PRIu64

Yes, I ran into this after sending the patch

Post by Jeremy C. Reed
DPRINTF(("timing bintval=%u, tstamp=%" PRIu64", init=%u\n",
ni->ni_intval, le64toh(cmd.tstamp), (uint32_t)(val - mod)));
and %zd
aprint_error_dev(sc->sc_dev,
"firmware file too short: %zd bytes\n", size);
hopefully that is correct.
I rebooted with new 5.0_RC3 but didn't see any change.
vendor 0x8086 product 0x4232 (miscellaneous network) at pci2 dev 0
function 0 not configured
I rebooted again (with the switch on front of laptop turned to on and that
made a light come on for the wireless) but still no change.
No extra device showed with "ifconfig -l".
Why is the pci_matchid list not used with "#if 0"? Why isn't the
PCI_PRODUCT_INTEL_PRO_WL_5100AGN_1 et cetera in the pcidevices? Is that
not needed?

it's needed of course. I just added the adapter I was trying to get
working as a quick&dirty hack because I didn't have all the PCI IDs in
hands. See iwn_match() ...

[Jeremy C. Reed]

Post by Manuel Bouyer

Post by Jeremy C. Reed
Why is the pci_matchid list not used with "#if 0"? Why isn't the
PCI_PRODUCT_INTEL_PRO_WL_5100AGN_1 et cetera in the pcidevices? Is that
not needed?

it's needed of course. I just added the adapter I was trying to get
working as a quick&dirty hack because I didn't have all the PCI IDs in
hands. See iwn_match() ...

Okay. Did that and put firmware iwn-5100 in place.

So here is my kernel detecting it:

ppb1 at pci0 dev 28 function 1: vendor 0x8086 product 0x2942 (rev. 0x03)
pci2 at ppb1 bus 3
pci2: i/o space, memory space enabled
iwn0 at pci2 dev 0 function 0: vendor 0x8086 product 0x4232 (rev. 0x 0)
iwn0: interrupting at ioapic0 pin 17
radio config=0x3109
adding chan 1 flags=0x6f maxpwr=15
adding chan 2 flags=0x6f maxpwr=15
adding chan 3 flags=0x6f maxpwr=15
adding chan 4 flags=0x6f maxpwr=15
adding chan 5 flags=0x6f maxpwr=15
adding chan 6 flags=0x6f maxpwr=15
adding chan 7 flags=0x6f maxpwr=15
adding chan 8 flags=0x6f maxpwr=15
adding chan 9 flags=0x6f maxpwr=15
adding chan 10 flags=0x6f maxpwr=15
adding chan 11 flags=0x6f maxpwr=15
adding chan 12 flags=0x61 maxpwr=15
adding chan 13 flags=0x61 maxpwr=15
adding chan 36 flags=0xe1 maxpwr=14
adding chan 40 flags=0xe1 maxpwr=15
adding chan 44 flags=0xe1 maxpwr=15
adding chan 48 flags=0xe1 maxpwr=15
adding chan 52 flags=0x31 maxpwr=15
adding chan 56 flags=0x31 maxpwr=15
adding chan 60 flags=0x31 maxpwr=15
adding chan 64 flags=0x31 maxpwr=15
adding chan 100 flags=0x31 maxpwr=15
adding chan 104 flags=0x31 maxpwr=15
adding chan 108 flags=0x31 maxpwr=15
adding chan 112 flags=0x31 maxpwr=15
adding chan 116 flags=0x31 maxpwr=15
adding chan 120 flags=0x31 maxpwr=15
adding chan 124 flags=0x31 maxpwr=15
adding chan 128 flags=0x31 maxpwr=15
adding chan 132 flags=0x31 maxpwr=15
adding chan 136 flags=0x31 maxpwr=15
adding chan 140 flags=0x31 maxpwr=15
adding chan 149 flags=0xa1 maxpwr=15
adding chan 153 flags=0xa1 maxpwr=15
adding chan 157 flags=0xa1 maxpwr=15
adding chan 161 flags=0xa1 maxpwr=15
adding chan 165 flags=0xa1 maxpwr=15
crystal calibration 0x00640064
, MIMO 1T2R, MoW, address 00:21:6b:3a:1e:c2
iwn0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
iwn0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
iwn0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps


Looks like something is missing above before MIMO. But I see same in code.

Here is my ifconfig attempt without firmware in place:

iwn0: cannot assign link-local address
iwn0: could not read firmware file iwn-5000
iwn0: could not read firmware
iwn0: cannot assign link-local address

Now with firmware in place, the following is from setting nwid and nwkey
and up:

notification qid=0 idx=0 flags=0 type=1
microcode alive notification version=5.10 subtype=9 alive=1
Configuring WiMAX coexistence
notification qid=4 idx=0 flags=0 type=90
sending crystal calibration 100, 100
notification qid=4 idx=1 flags=0 type=176
sending calibration query
notification qid=4 idx=2 flags=0 type=101
notification qid=0 idx=1 flags=0 type=102
saving calibration result code=11 len=88
notification qid=0 idx=2 flags=0 type=102
saving calibration result code=17 len=48
notification qid=0 idx=3 flags=0 type=102
saving calibration result code=9 len=508
notification qid=0 idx=4 flags=0 type=103
notification qid=0 idx=0 flags=0 type=1
microcode alive notification version=5.10 subtype=0 alive=1
Configuring WiMAX coexistence
notification qid=4 idx=0 flags=0 type=90
sending crystal calibration 100, 100
notification qid=4 idx=1 flags=0 type=176
send calibration result idx=1 len=508
notification qid=4 idx=2 flags=0 type=176
send calibration result idx=2 len=88
notification qid=4 idx=3 flags=0 type=176
send calibration result idx=3 len=48
notification qid=4 idx=4 flags=0 type=176
setting power mode
notification qid=4 idx=5 flags=0 type=119
configuring bluetooth coexistence
notification qid=4 idx=6 flags=0 type=155
setting configuration
notification qid=4 idx=7 flags=0 type=16
setting TX power
notification qid=4 idx=8 flags=0 type=152
adding broadcast node
notification qid=4 idx=9 flags=0 type=24
notification qid=4 idx=10 flags=0 type=78
setting critical temperature to 110
notification qid=4 idx=11 flags=0 type=164
adding channel 1
adding channel 2
adding channel 3
adding channel 4
adding channel 5
adding channel 6
adding channel 7
adding channel 8
adding channel 9
adding channel 10
adding channel 11
adding channel 12
adding channel 13
sending scan command nchan=13
notification qid=4 idx=12 flags=0 type=72
notification qid=4 idx=13 flags=0 type=128
notification qid=0 idx=1 flags=0 type=130
scanning channel 1 status 1
notification qid=0 idx=6 flags=0 type=192
received PHY stats
notification qid=0 idx=7 flags=0 type=193
notification qid=0 idx=9 flags=0 type=192
received PHY stats
notification qid=0 idx=10 flags=0 type=193
notification qid=0 idx=11 flags=0 type=192
received PHY stats
notification qid=0 idx=12 flags=0 type=193
notification qid=0 idx=13 flags=0 type=192
received PHY stats
notification qid=0 idx=14 flags=0 type=193
notification qid=0 idx=15 flags=0 type=192
received PHY stats
notification qid=0 idx=16 flags=0 type=193
notification qid=0 idx=17 flags=0 type=192
received PHY stats
notification qid=0 idx=18 flags=0 type=193
notification qid=0 idx=19 flags=0 type=192
received PHY stats
notification qid=0 idx=20 flags=0 type=193
notification qid=0 idx=21 flags=0 type=131
notification qid=0 idx=22 flags=0 type=130
scanning channel 2 status 1
notification qid=0 idx=23 flags=0 type=192
received PHY stats
notification qid=0 idx=24 flags=0 type=193
notification qid=0 idx=25 flags=0 type=192
received PHY stats
notification qid=0 idx=26 flags=0 type=193
notification qid=0 idx=27 flags=0 type=131
notification qid=0 idx=28 flags=0 type=130
scanning channel 3 status 1
notification qid=0 idx=29 flags=0 type=131
notification qid=0 idx=30 flags=0 type=130
scanning channel 4 status 1
notification qid=0 idx=31 flags=0 type=131
notification qid=0 idx=32 flags=0 type=130
scanning channel 5 status 1
notification qid=0 idx=33 flags=0 type=131
notification qid=0 idx=34 flags=0 type=130
scanning channel 6 status 1
notification qid=0 idx=35 flags=0 type=192
received PHY stats
notification qid=0 idx=36 flags=0 type=193
notification qid=0 idx=37 flags=0 type=192
received PHY stats
notification qid=0 idx=38 flags=0 type=193
notification qid=0 idx=39 flags=0 type=192
received PHY stats
notification qid=0 idx=40 flags=0 type=193
notification qid=0 idx=41 flags=0 type=131
notification qid=0 idx=42 flags=0 type=130
scanning channel 7 status 1
notification qid=0 idx=43 flags=0 type=131
notification qid=0 idx=44 flags=0 type=130
scanning channel 8 status 1
notification qid=0 idx=45 flags=0 type=131
notification qid=0 idx=46 flags=0 type=130
scanning channel 9 status 1
notification qid=0 idx=47 flags=0 type=131
notification qid=0 idx=48 flags=0 type=130
scanning channel 10 status 1
notification qid=0 idx=49 flags=0 type=192
received PHY stats
notification qid=0 idx=50 flags=0 type=193
notification qid=0 idx=51 flags=0 type=192
received PHY stats
notification qid=0 idx=52 flags=0 type=193
notification qid=0 idx=53 flags=0 type=131
notification qid=0 idx=54 flags=0 type=130
scanning channel 11 status 1
notification qid=0 idx=55 flags=0 type=192
received PHY stats
notification qid=0 idx=56 flags=0 type=193
notification qid=0 idx=57 flags=0 type=192
received PHY stats
notification qid=0 idx=58 flags=0 type=193
notification qid=0 idx=59 flags=0 type=131
notification qid=0 idx=60 flags=0 type=130
scanning channel 12 status 1
notification qid=0 idx=61 flags=0 type=131
notification qid=0 idx=62 flags=0 type=130
scanning channel 13 status 1
notification qid=0 idx=63 flags=0 type=131
notification qid=0 idx=64 flags=0 type=132
scan finished nchan=13 status=1 chan=13
adding channel 36
adding channel 40
adding channel 44
adding channel 48
adding channel 52
adding channel 56
adding channel 60
adding channel 64
adding channel 100
adding channel 104
adding channel 108
adding channel 112
adding channel 116
adding channel 120
adding channel 124
adding channel 128
adding channel 132
adding channel 136
adding channel 140
adding channel 149
adding channel 153
adding channel 157
adding channel 161
adding channel 165
sending scan command nchan=24
notification qid=4 idx=14 flags=0 type=128
notification qid=0 idx=66 flags=0 type=130
scanning channel 36 status 1
notification qid=0 idx=67 flags=0 type=132
scan finished nchan=0 status=5 chan=0
rxon chan 1 flags 40008025 cck 3 ofdm 0
setting TX power
adding broadcast node
adding BSS node from auth
adding BSS node
setting link quality for node 0
setting sensitivity 120/240/90/170/125/170/95
setting initial differential gains
sending request for statistics
setting sensitivity 120/240/90/170/125/170/95
setting initial differential gains
sending request for statistics
sending data: qid=0 idx=0 len=6 nsegs=1
notification qid=0 idx=68 flags=0 type=192
received PHY stats
notification qid=0 idx=69 flags=0 type=193
notification qid=4 idx=15 flags=0 type=16
notification qid=4 idx=16 flags=0 type=152
notification qid=4 idx=17 flags=0 type=24
notification qid=4 idx=18 flags=0 type=78
notification qid=4 idx=19 flags=0 type=24
notification qid=4 idx=20 flags=0 type=78
notification qid=4 idx=21 flags=0 type=168
notification qid=4 idx=22 flags=0 type=176
notification qid=4 idx=23 flags=0 type=156
notification qid=4 idx=24 flags=0 type=168
notification qid=4 idx=25 flags=0 type=176
notification qid=4 idx=26 flags=0 type=156
notification qid=0 idx=0 flags=0 type=28
notification qid=0 idx=71 flags=0 type=192
received PHY stats
notification qid=0 idx=72 flags=0 type=193
sending data: qid=0 idx=1 len=27 nsegs=1
notification qid=0 idx=1 flags=0 type=28
notification qid=0 idx=74 flags=0 type=192
received PHY stats
notification qid=0 idx=75 flags=0 type=193
timing bintval=100, tstamp=370270310832, init=101968
rxon chan 1 flags 40008025
setting TX power
adding BSS node
setting link quality for node 0
setting sensitivity 120/240/90/170/125/170/95
setting initial differential gains
sending request for statistics
notification qid=4 idx=27 flags=0 type=20
notification qid=4 idx=28 flags=0 type=16
notification qid=4 idx=29 flags=0 type=152
iwn0: fatal firmware error
firmware error log:
program counter = 0x00003E30
source line = 0x000003B5
error data = 0x0000000100000000
branch link = 0x00003DDE00003DDE
interrupt link = 0x0000090E00000000
time = 903123728
driver status:
tx ring 0: qid=0 cur=2 queued=0
tx ring 1: qid=1 cur=0 queued=0
tx ring 2: qid=2 cur=0 queued=0
tx ring 3: qid=3 cur=0 queued=0
tx ring 4: qid=4 cur=36 queued=0
tx ring 5: qid=5 cur=0 queued=0
tx ring 6: qid=6 cur=0 queued=0
tx ring 7: qid=7 cur=0 queued=0
tx ring 8: qid=8 cur=0 queued=0
tx ring 9: qid=9 cur=0 queued=0
tx ring 10: qid=10 cur=0 queued=0
tx ring 11: qid=11 cur=0 queued=0
tx ring 12: qid=12 cur=0 queued=0
tx ring 13: qid=13 cur=0 queued=0
tx ring 14: qid=14 cur=0 queued=0
tx ring 15: qid=15 cur=0 queued=0
tx ring 16: qid=16 cur=0 queued=0
tx ring 17: qid=17 cur=0 queued=0
tx ring 18: qid=18 cur=0 queued=0
tx ring 19: qid=19 cur=0 queued=0
rx ring: cur=100
802.11 state 4



I see the fatal firmware error. I don't know if any of this is useful or
not.

$ ifconfig iwn0
iwn0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
ssid 5FYA8 nwkey *****
powersave off
address: 00:21:6b:3a:1e:c2
media: IEEE802.11 autoselect (autoselect mode 11g)
status: no network


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

[Nicolas]

Hi Christos,

FreeBSD has no support for this card (only for 4965), only OpenBSD has it !

Niko.


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

[Christos Zoulas]

Post by Nicolas
Hi Christos,
FreeBSD has no support for this card (only for 4965), only OpenBSD has it !

Then I mis-remembered. I must have been working with the OpenBSD driver.

christos


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

[Jeremy C. Reed]

Post by Manuel Bouyer
I also started working on it; didn't finish due do limited time
and missing hardware in hands. From memory the driver did start
operation but the firmware was dying quickly.

I also have this device.

003:00:0: Intel product 0x4232 (miscellaneous network)

pcidatabase.com says is Carte Intel WiFi Link 5100 AGN.

Did you use the newer firmware from
http://damien.bergamini.free.fr/packages/openbsd/iwn-firmware-5.1.tgz
(unofficial OpenBSD package)?

If anyone can share your diffs, it would be appreciated.

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

[Nicolas]

Manuel: can you post your patch ?

Thanks in advance.
Niko.


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

[Manuel Bouyer]

Post by Nicolas
Manuel: can you post your patch ?

Here it is. It's against netbsd-5.

Remember it's not functionnal. The kernel builds and boot; at
'ifconfig up' the firmware dies.