Intel WiFi 5100/5300

[Lutz Bichler]

Hi,

does anybody know what happened to the attempts to support Intel WiFi 5100/5300 interfaces in the iwn-driver? Are any patches available which could be used to start working on support for these interfaces?

Lutz
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
_______________________________________________
freebsd-net@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@..."

[Bernhard Schmidt-4]

On Friday 09 October 2009 19:08:39 Lutz Bichler wrote:
> Hi,
>
> does anybody know what happened to the attempts to support Intel WiFi
>  5100/5300 interfaces in the iwn-driver? Are any patches available which
>  could be used to start working on support for these interfaces?

I'm curious too, as I'm playing with idea to start porting the latest changes
to if_iwn from OpenBSD. Already started with adding the 5000 series firmware to
iwnfw...

--
Bernhard
_______________________________________________
freebsd-net@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@..."

[Glen Barber-2]

Hi

On Fri, Oct 9, 2009 at 6:03 PM, Bernhard Schmidt <bschmidt@...> wrote:

> On Friday 09 October 2009 19:08:39 Lutz Bichler wrote:
>> Hi,
>>
>> does anybody know what happened to the attempts to support Intel WiFi
>>  5100/5300 interfaces in the iwn-driver? Are any patches available which
>>  could be used to start working on support for these interfaces?
>
> I'm curious too, as I'm playing with idea to start porting the latest changes
> to if_iwn from OpenBSD. Already started with adding the 5000 series firmware to
> iwnfw...
>

If you need patches tested for 8-STABLE for the 5100 AGN, I am more
than happy to test.


--
Glen Barber
_______________________________________________
freebsd-net@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@..."

[Lawrence Stewart-3]

Bernhard Schmidt wrote:

> On Friday 09 October 2009 19:08:39 Lutz Bichler wrote:
>> Hi,
>>
>> does anybody know what happened to the attempts to support Intel WiFi
>>  5100/5300 interfaces in the iwn-driver? Are any patches available which
>>  could be used to start working on support for these interfaces?
>
> I'm curious too, as I'm playing with idea to start porting the latest changes
> to if_iwn from OpenBSD. Already started with adding the 5000 series firmware to
> iwnfw...
>

Most recent effort to port Intel 5100 support that I'm aware of was done
by Daniel Roethlisberger (cc'd). He has the work kicking around in a
private svn repo. No idea what state it's in though.

Cheers,
Lawrence
_______________________________________________
freebsd-net@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@..."

[Daniel Roethlisberger]

Lawrence Stewart <lstewart@...> 2009-10-14:

> Bernhard Schmidt wrote:
> > On Friday 09 October 2009 19:08:39 Lutz Bichler wrote:
> > > does anybody know what happened to the attempts to support
> > > Intel WiFi 5100/5300 interfaces in the iwn-driver? Are any
> > > patches available which could be used to start working on
> > > support for these interfaces?
> >
> > I'm curious too, as I'm playing with idea to start porting
> > the latest changes to if_iwn from OpenBSD. Already started
> > with adding the 5000 series firmware to iwnfw...
>
> Most recent effort to port Intel 5100 support that I'm aware of
> was done by Daniel Roethlisberger (cc'd). He has the work
> kicking around in a private svn repo. No idea what state it's
> in though.

I haven't had a chance to work on this for some time.  A bunch of
other folks are interested and/or working on it.  I've added two
of the most recently active ones to the Cc: list.

The code in my svn repo [1] is not up to date with all the 802.11
changes in -current.  Status is still that scanning works, but
associating (tx actually) fails with a firmware exception.
Brandon has made some progress on why this is happening, but no
real fix yet I think.

[1] https://svn.roe.ch/iwn/trunk

--
Daniel Roethlisberger
http://daniel.roe.ch/
_______________________________________________
freebsd-net@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@..."

[Brandon Gooch]

On Wed, Oct 14, 2009 at 11:33 PM, Daniel Roethlisberger <daniel@...> wrote:

> Lawrence Stewart <lstewart@...> 2009-10-14:
>> Bernhard Schmidt wrote:
>> > On Friday 09 October 2009 19:08:39 Lutz Bichler wrote:
>> > > does anybody know what happened to the attempts to support
>> > > Intel WiFi 5100/5300 interfaces in the iwn-driver? Are any
>> > > patches available which could be used to start working on
>> > > support for these interfaces?
>> >
>> > I'm curious too, as I'm playing with idea to start porting
>> > the latest changes to if_iwn from OpenBSD. Already started
>> > with adding the 5000 series firmware to iwnfw...
>>
>> Most recent effort to port Intel 5100 support that I'm aware of
>> was done by Daniel Roethlisberger (cc'd). He has the work
>> kicking around in a private svn repo. No idea what state it's
>> in though.
>
> I haven't had a chance to work on this for some time.  A bunch of
> other folks are interested and/or working on it.  I've added two
> of the most recently active ones to the Cc: list.
>
> The code in my svn repo [1] is not up to date with all the 802.11
> changes in -current.  Status is still that scanning works, but
> associating (tx actually) fails with a firmware exception.
> Brandon has made some progress on why this is happening, but no
> real fix yet I think.
>
> [1] https://svn.roe.ch/iwn/trunk
>
> --
> Daniel Roethlisberger
> http://daniel.roe.ch/
>

Hi everyone. Yes, it's true that I've found SOMETHING, although I'm
still investigating why that something is happening in the first
place. I'm having to work on it in between "real life", so that means
I need the working, current driver in tree most of the time. I have a
5300 in another computer I'm planning on hacking around on in the near
future so I can have both a 4965 and 5000 series test environment.

Right now, I'm reading through these:

man -k ieee80211

...and friends.

I don't know much about the technology, so I decided to start over
from the beginning, making this whole "iwn driver update" more of a
"learn FreeBSD's IEEE802.11 layer" thing (a long-term project).

So, yeah, I'll share more as I get it :)

-Brandon
_______________________________________________
freebsd-net@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@..."

[Bernhard Schmidt-4]

Hi,

Just to let you know, I started working on that myself and was finally able to
get a connection and make traffic yesterday :) I'm still having issues scanning
5Ghz channels though.. anyways, I'll post updates on  sunday.

--
Bernhard
_______________________________________________
freebsd-net@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@..."

[Brandon Gooch]

On Thu, Oct 15, 2009 at 6:15 AM, Bernhard Schmidt
<bschmidt@...> wrote:
> Hi,
>
> Just to let you know, I started working on that myself and was finally able to
> get a connection and make traffic yesterday :) I'm still having issues scanning
> 5Ghz channels though.. anyways, I'll post updates on  sunday.
>
> --
> Bernhard
>

That's great!

BTW, which chip are you working with? Are you planning on pushing back
your updates to Daniel's SVN repo?

-Brandon
_______________________________________________
freebsd-net@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@..."

[Bernhard Schmidt-4]

On Friday 16 October 2009 02:52:26 Brandon Gooch wrote:

> On Thu, Oct 15, 2009 at 6:15 AM, Bernhard Schmidt
>
> <bschmidt@...> wrote:
> > Hi,
> >
> > Just to let you know, I started working on that myself and was finally
> > able to get a connection and make traffic yesterday :) I'm still having
> > issues scanning 5Ghz channels though.. anyways, I'll post updates on
> >  sunday.
> >
> > --
> > Bernhard
>
> That's great!
>
> BTW, which chip are you working with? Are you planning on pushing back
> your updates to Daniel's SVN repo?

I'm working with a 5100 currently, I do also have a 5300 and 4965 to test. As
I did start from scratch (didn't know about the repo at that point) the diff
against that it is probably quite large, have to check that though.

--
Bernhard
_______________________________________________
freebsd-net@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@..."

[Bernhard Schmidt-4]

On Thursday 15 October 2009 08:15:57 Bernhard Schmidt wrote:
> .. anyways, I'll post updates on  sunday.

Here we go.

http://techwires.net/~bschmidt/patches/freebsd/iwn/

Testers/feedback welcome!

Code is pretty stable although there are still a few open issues. Nothing
major I should be able to figure them out.

* I did only tests with a 5100 card, other might not yet work.. I will do
tests wie 5300 and 4965 cards later this week.
* 11N has not been tested at all.
* Deauth/disconnect frames are not handled correctly, those yield firmware
errors. The remote side might therefore not be able to clean up correctly,
whichs lead to no answers to probe requests on new scans.
* Encryption of any kind does not yet work.
* Monitor mode/radiotap does not yet work.
* IBSS mode has not been tested.
* iwnfw module is locked somehow on kldunload.
* RF kill switch might not work correctly.
* Manpage needs an update. :)
* Suspend/resume is broken.

--
Bernhard
_______________________________________________
freebsd-net@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@..."

[Pawel Worach]

On Oct 18, 2009, at 16:27, Bernhard Schmidt wrote:

>
> On Thursday 15 October 2009 08:15:57 Bernhard Schmidt wrote:
>> .. anyways, I'll post updates on  sunday.
>
> Here we go.
>
> http://techwires.net/~bschmidt/patches/freebsd/iwn/
>
> Testers/feedback welcome!
>
> Code is pretty stable although there are still a few open issues.  
> Nothing
> major I should be able to figure them out.
>
> * I did only tests with a 5100 card, other might not yet work.. I  
> will do
> tests wie 5300 and 4965 cards later this week.
> * 11N has not been tested at all.
> * Deauth/disconnect frames are not handled correctly, those yield  
> firmware
> errors. The remote side might therefore not be able to clean up  
> correctly,
> whichs lead to no answers to probe requests on new scans.
> * Encryption of any kind does not yet work.
> * Monitor mode/radiotap does not yet work.
> * IBSS mode has not been tested.
> * iwnfw module is locked somehow on kldunload.
> * RF kill switch might not work correctly.
> * Manpage needs an update. :)
> * Suspend/resume is broken.
>

Works here for an open network (FreeBSD 8.0-RC1), thanks for working  
on this!

iwn0: <Intel(R) PRO/Wireless 5300> mem 0xf4300000-0xf4301fff irq 17 at  
device 0.0 on pci3
iwn0: MIMO 3T3R, MoW, address 00:16:ea:e3:e2:82
iwn0: [ITHREAD]
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
iwn0: 11na MCS: 15Mbps 30Mbps 45Mbps 60Mbps 90Mbps 120Mbps 135Mbps  
150Mbps 30Mbps 60Mbps 90Mbps 120Mbps 180Mbps 240Mbps 270Mbps 300Mbps
iwn0: 11ng MCS: 15Mbps 30Mbps 45Mbps 60Mbps 90Mbps 120Mbps 135Mbps  
150Mbps 30Mbps 60Mbps 90Mbps 120Mbps 180Mbps 240Mbps 270Mbps 300Mbps
wlan0: Ethernet address: 00:16:ea:e3:e2:82
wlan0: link state changed to UP
iwn0: need multicast update callback
iwn0: need multicast update callback
iwn0: need multicast update callback

wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu  
1500
        ether 00:16:ea:e3:e2:82
        inet 10.0.1.17 netmask 0xffffff00 broadcast 10.0.1.255
        media: IEEE 802.11 Wireless Ethernet OFDM/36Mbps mode 11g
        status: associated
        ssid "xxx" channel 11 (2462 Mhz 11g) bssid 00:xx:xx:xx:xx:xx
        country US authmode OPEN privacy OFF txpower 15 bmiss 10 scanvalid 60
        protmode CTS wme roaming MANUAL

--
Pawel

> --
> Bernhard
> _______________________________________________
> freebsd-net@... mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe@..."
>
_______________________________________________
freebsd-net@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@..."

[Lucius Windschuh]

Hi Bernhard,
I tried your module on my T400 with a PRO/Wireless 5300 and WITNESS,
INVARIANTS enabled.
If the RF kill switch is set to "WLAN disabled", this command sequence
produces a panic:
$ kldload iwnfw
$ kldload if_iwn
$ ifconfig wlan create wlandev iwn0
wlan0
$ ifconfig wlan0 up

iwn0: iwn_init_locked: radio is disabled by hardware switch
panic: _mtx_lock_sleep: recursed on non-recursive mutex iwn0 @
/usr/src/sys/modules/iwn/../../dev/iwn/if_iwn.c:5497

Locks:
exclusive sleep mutex iwn0 (network driver) r = 0 (0xc8242008) locked
@ /usr/src/sys/modules/iwn/../../dev/iwn/if_iwn.c:3091
exclusive sleep mutex iwn0 (network driver) r = 0 (0xc8242008) locked
@ /usr/src/sys/modules/iwn/../../dev/iwn/if_iwn.c:3091
exclusive sx so_rcv_sx (so_rcv_sx) r = 0 (0xc7f836fc) locked @
/usr/src/sys/kern/uipc_sockbuf.c:148
exclusive sx so_rcv_sx (so_rcv_sx) r = 0 (0xc7f833c4) locked @
/usr/src/sys/kern/uipc_sockbuf.c:148
exclusive sx so_rcv_sx (so_rcv_sx) r = 0 (0xc7f83560) locked @
/usr/src/sys/kern/uipc_sockbuf.c:148
exclusive sx so_rcv_sx (so_rcv_sx) r = 0 (0xc7f37d6c) locked @
/usr/src/sys/kern/uipc_sockbuf.c:148
exclusive sx so_rcv_sx (so_rcv_sx) r = 0 (0xc7f66898) locked @
/usr/src/sys/kern/uipc_sockbuf.c:148
exclusive lockmgr bufwait (bufwait) r = 0 (0xdae5ce20) locked @
/usr/src/sys/kern/vfs_bio.c:1835
exclusive lockmgr snaplk (snaplk) r = 0 (0xc7df01dc) locked @
/usr/src/sys/kern/vfs_vnops.c:536

db:0:kdb.enter.default>  bt
Tracing pid 2552 tid 100211 td 0xc7d2b230
kdb_enter(c09e4c81,c09e4c81,c09e365d,eb2b8ab0,1,...) at kdb_enter+0x3a
panic(c09e365d,c7e97960,c823f4b4,1579,c8242008,...) at panic+0x136
_mtx_lock_sleep(c8242008,c7d2b230,0,c823f4b4,1579,...) at _mtx_lock_sleep+0x4a
_mtx_lock_flags(c8242008,0,c823f4b4,1579,c6958800,...) at _mtx_lock_flags+0xf7
iwn_stop(c8242000,0,c823f4b4,c13,c828f000,...) at iwn_stop+0x32
iwn_ioctl(c6958800,80206910,c8291420,c7d2b230,eb2b8bac,...) at iwn_ioctl+0x102
ifioctl(c80a380c,80206910,c8291420,c7d2b230,c807e500,...) at ifioctl+0xa05
soo_ioctl(c8070dc8,80206910,c8291420,c6b71e00,c7d2b230,...) at soo_ioctl+0x415
kern_ioctl(c7d2b230,3,80206910,c8291420,6f5d10,...) at kern_ioctl+0x1dd
ioctl(c7d2b230,eb2b8cf8,c,c09fbc00,c0a53bc8,...) at ioctl+0x134
syscall(eb2b8d38) at syscall+0x283
Xint0x80_syscall() at Xint0x80_syscall+0x20
--- syscall (54, FreeBSD ELF32, ioctl), eip = 0x281c8a13, esp =
0xbfbfe46c, ebp = 0xbfbfe4c8 ---

BTW: With the RF kill switch set to "WLAN enabled", it works for open
networks. But ifconfig wlan1 list ap did not return my 802.11a access
point. Is this expected?

Regards and thanks for the work.

Lucius
_______________________________________________
freebsd-net@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@..."

[Bernhard Schmidt-4]

On Sunday 18 October 2009 21:41:36 Lucius Windschuh wrote:
> Hi Bernhard,
> I tried your module on my T400 with a PRO/Wireless 5300 and WITNESS,
> INVARIANTS enabled.
> If the RF kill switch is set to "WLAN disabled", this command sequence

[..]

Thanks for reporting this, there seems to be an issue in iwn_cleanup().

> BTW: With the RF kill switch set to "WLAN enabled", it works for open
> networks. But ifconfig wlan1 list ap did not return my 802.11a access
> point. Is this expected?

No it's not. I'll noticed that also during the last tests, scanning on 5Ghz
channels does not work reliably, setting a fixed channel works though.


--
Bernhard
_______________________________________________
freebsd-net@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@..."

[Vassilis Laganakos]

Hello,

> On Thursday 15 October 2009 08:15:57 Bernhard Schmidt wrote:
> > .. anyways, I'll post updates on  sunday.
>
> Here we go.
>
> http://techwires.net/~bschmidt/patches/freebsd/iwn/
>
> Testers/feedback welcome!
>
> Code is pretty stable although there are still a few open issues. Nothing
> major I should be able to figure them out.
>
> * I did only tests with a 5100 card, other might not yet work.. I will do
> tests wie 5300 and 4965 cards later this week.
> * 11N has not been tested at all.
> * Deauth/disconnect frames are not handled correctly, those yield firmware
> errors. The remote side might therefore not be able to clean up correctly,
> whichs lead to no answers to probe requests on new scans.
> * Encryption of any kind does not yet work.
> * Monitor mode/radiotap does not yet work.
> * IBSS mode has not been tested.
> * iwnfw module is locked somehow on kldunload.
> * RF kill switch might not work correctly.
> * Manpage needs an update. :)
> * Suspend/resume is broken.
>

Awesome! I was checking things out for iwn 5100, but I was getting firmware problems.
I'll try your stuff on 8-STABLE and get back with info.

Thank you very much for working on this!

Best regards,
Vassilis L.



     
_______________________________________________
freebsd-net@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@..."

[Brandon Gooch]

On Sun, Oct 18, 2009 at 2:27 PM, Bernhard Schmidt
<bschmidt@...> wrote:

> On Thursday 15 October 2009 08:15:57 Bernhard Schmidt wrote:
>> .. anyways, I'll post updates on  sunday.
>
> Here we go.
>
> http://techwires.net/~bschmidt/patches/freebsd/iwn/
>
> Testers/feedback welcome!
>
> Code is pretty stable although there are still a few open issues. Nothing
> major I should be able to figure them out.
>
> * I did only tests with a 5100 card, other might not yet work.. I will do
> tests wie 5300 and 4965 cards later this week.
> * 11N has not been tested at all.
> * Deauth/disconnect frames are not handled correctly, those yield firmware
> errors. The remote side might therefore not be able to clean up correctly,
> whichs lead to no answers to probe requests on new scans.
> * Encryption of any kind does not yet work.
> * Monitor mode/radiotap does not yet work.
> * IBSS mode has not been tested.
> * iwnfw module is locked somehow on kldunload.
> * RF kill switch might not work correctly.
> * Manpage needs an update. :)
> * Suspend/resume is broken.
>
> --
> Bernhard
>

Great job!

However, with my 4965, I get a page fault somewhere in
iwn4965_set_txpower when I load if_iwn.ko (I'm loading iwnfw.ko
manually before loading if_iwn.ko)

I'll see if I can gather a bit more info tomorrow.

-Brandon
_______________________________________________
freebsd-net@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@..."

[Glen Barber-2]

Howdy!

On Sun, Oct 18, 2009 at 10:27 AM, Bernhard Schmidt
<bschmidt@...> wrote:

> On Thursday 15 October 2009 08:15:57 Bernhard Schmidt wrote:
>> .. anyways, I'll post updates on  sunday.
>
> Here we go.
>
> http://techwires.net/~bschmidt/patches/freebsd/iwn/
>
> Testers/feedback welcome!
>
> Code is pretty stable although there are still a few open issues. Nothing
> major I should be able to figure them out.
>
> * I did only tests with a 5100 card, other might not yet work.. I will do
> tests wie 5300 and 4965 cards later this week.
> * 11N has not been tested at all.
> * Deauth/disconnect frames are not handled correctly, those yield firmware
> errors. The remote side might therefore not be able to clean up correctly,
> whichs lead to no answers to probe requests on new scans.
> * Encryption of any kind does not yet work.
> * Monitor mode/radiotap does not yet work.
> * IBSS mode has not been tested.
> * iwnfw module is locked somehow on kldunload.
> * RF kill switch might not work correctly.
> * Manpage needs an update. :)
> * Suspend/resume is broken.
>

Any thoughts on the errors I get with buildkernel (attached)?  The
kernel config has no other changes compared to GENERIC than enabling
KDB and DDB.

Thanks and regards,

--
Glen Barber

===> iwn (all)
cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc   -DH
AVE_KERNEL_OPTION_HEADERS -include /usr/obj/usr/src/sys/PEGASUS/opt_global.h -I.
 -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param
 large-function-growth=1000 -fno-common -g -I/usr/obj/usr/src/sys/PEGASUS -mno-a
lign-long-strings -mpreferred-stack-boundary=2  -mno-mmx -mno-3dnow -mno-sse -mn
o-sse2 -mno-sse3 -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-prot
ector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  -Wmissing-pr
ototypes -Wpointer-arith -Winline -Wcast-qual  -Wundef -Wno-pointer-sign -fforma
t-extensions -c /usr/src/sys/modules/iwn/../../dev/iwn/if_iwn.c
cc1: warnings being treated as errors
/usr/src/sys/modules/iwn/../../dev/iwn/if_iwn.c: In function 'iwn_read_firmware'
:
/usr/src/sys/modules/iwn/../../dev/iwn/if_iwn.c:4986: warning: format '%ld' expe
cts type 'long int', but argument 4 has type 'size_t'
/usr/src/sys/modules/iwn/../../dev/iwn/if_iwn.c:5016: warning: format '%ld' expe
cts type 'long int', but argument 4 has type 'size_t'
*** Error code 1

Stop in /usr/src/sys/modules/iwn.
*** Error code 1

Stop in /usr/src/sys/modules.
*** Error code 1

Stop in /usr/obj/usr/src/sys/PEGASUS.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.

_______________________________________________
freebsd-net@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@..."

[Glen Barber-2]

On Sun, Oct 18, 2009 at 9:14 PM, Glen Barber <glen.j.barber@...> wrote:
> Howdy!
>
>
> Any thoughts on the errors I get with buildkernel (attached)?  The
> kernel config has no other changes compared to GENERIC than enabling
> KDB and DDB.
>
> Thanks and regards,
>

This is 8-STABLE, r198209 by the way. Sorry for not including that initially.

--
Glen Barber
_______________________________________________
freebsd-net@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@..."

[Alireza Torabi]

Many thanks for your work on this.
When do you think you'll have the ecryption support for iwn? (so
cheeky of me I know!)

Alireza

On 10/18/09, Bernhard Schmidt <bschmidt@...> wrote:

> On Thursday 15 October 2009 08:15:57 Bernhard Schmidt wrote:
>> .. anyways, I'll post updates on  sunday.
>
> Here we go.
>
> http://techwires.net/~bschmidt/patches/freebsd/iwn/
>
> Testers/feedback welcome!
>
> Code is pretty stable although there are still a few open issues. Nothing
> major I should be able to figure them out.
>
> * I did only tests with a 5100 card, other might not yet work.. I will do
> tests wie 5300 and 4965 cards later this week.
> * 11N has not been tested at all.
> * Deauth/disconnect frames are not handled correctly, those yield firmware
> errors. The remote side might therefore not be able to clean up correctly,
> whichs lead to no answers to probe requests on new scans.
> * Encryption of any kind does not yet work.
> * Monitor mode/radiotap does not yet work.
> * IBSS mode has not been tested.
> * iwnfw module is locked somehow on kldunload.
> * RF kill switch might not work correctly.
> * Manpage needs an update. :)
> * Suspend/resume is broken.
>
> --
> Bernhard
> _______________________________________________
> freebsd-net@... mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe@..."
>

_______________________________________________
freebsd-net@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@..."

[Bernhard Schmidt-4]

On Sunday 18 October 2009 16:27:37 Bernhard Schmidt wrote:
> On Thursday 15 October 2009 08:15:57 Bernhard Schmidt wrote:
> > .. anyways, I'll post updates on  sunday.
>
> Here we go.

Update:
* All reported issues should now be fixed, please verify.
* WPA does work.

Still open:
* Test reports welcome, especially with 4965, 5150, 5300 and 5350.

At this point, if no issue come up, the driver has the same functionality as
the in tree one.

http://techwires.net/~bschmidt/patches/freebsd/iwn/sys/
or
http://techwires.net/~bschmidt/patches/freebsd/iwn/iwn-20091020.tar.gz

--
Bernhard
_______________________________________________
freebsd-net@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@..."

[David Horn]

On Tue, Oct 20, 2009 at 4:47 PM, Bernhard Schmidt
<bschmidt@...> wrote:
> On Sunday 18 October 2009 16:27:37 Bernhard Schmidt wrote:
>> On Thursday 15 October 2009 08:15:57 Bernhard Schmidt wrote:
>> > .. anyways, I'll post updates on  sunday.
>>
>> Here we go.
>
> Update:
> * All reported issues should now be fixed, please verify.
> * WPA does work.

4965 with mode 11g WPA2/AES works well on 2.4Ghz (Have not tried
5Ghz/11a or 5Ghz/11n)

>
> Still open:
> * Test reports welcome, especially with 4965, 5150, 5300 and 5350.
>
> At this point, if no issue come up, the driver has the same functionality as
> the in tree one.

Any thoughts on IBSS or 11n mode support ?  (I could not get 4965 11ng
mode to work, and IBSS support is disabled in the drivercaps)  Of
course, this is on-par with the in-tree iwn driver as well.

The only new issue I have found so far is that I must manually load
iwnfw.ko before loading if_iwn.ko (the module depend used to work on
the in-tree driver)

Thanks for your work on this driver!

---Dave H
_______________________________________________
freebsd-net@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@..."