|Benjamin Close||Jan 5, 2007 7:00 am|
|Max Laier||Jan 5, 2007 7:47 am|
|Florent Thoumie||Jan 5, 2007 8:20 am|
|Max Laier||Jan 5, 2007 8:32 am|
|Attilio Rao||Jan 5, 2007 8:50 am|
|Massimo Lusetti||Jan 5, 2007 8:57 am|
|Rene Ladan||Jan 5, 2007 9:07 am|
|Rink Springer||Jan 5, 2007 12:23 pm|
|Gabor Kovesdan||Jan 5, 2007 2:13 pm|
|Benjamin Close||Jan 7, 2007 5:36 am|
|Max Laier||Jan 7, 2007 7:52 am|
|Joel Dahl||Jan 7, 2007 1:31 pm|
|Sam Fourman Jr.||Jan 15, 2007 12:38 am|
|Abdullah Al-Marrie||Jan 21, 2007 3:14 pm|
|Gilbert Cao||Jan 25, 2007 12:11 am|
|Benjamin Close||Jan 26, 2007 3:08 pm|
|Abdullah Ibn Hamad Al-Marri||Jan 26, 2007 4:33 pm|
|Gilbert Cao||Jan 27, 2007 12:44 pm|
|Sam Fourman Jr.||Jan 27, 2007 10:46 pm|
|Benjamin Close||Jan 31, 2007 5:00 pm|
|Florent Thoumie||Jan 31, 2007 5:00 pm|
|Sam Fourman Jr.||Feb 1, 2007 9:48 am|
|Abdullah Ibn Hamad Al-Marri||Feb 1, 2007 9:53 am|
|Sam Fourman Jr.||Feb 1, 2007 9:58 am|
|Benjamin Close||Feb 1, 2007 11:22 am|
|Sam Leffler||Feb 1, 2007 5:21 pm|
|Gilbert Cao||Feb 3, 2007 8:37 pm|
|Abdullah Ibn Hamad Al-Marri||Mar 7, 2007 6:04 am|
|Subject:||Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller|
|From:||Abdullah Al-Marrie (alma...@gmail.com)|
|Date:||Jan 21, 2007 3:14:36 pm|
On 1/7/07, Benjamin Close <Benj...@clearchain.com> wrote:
Massimo Lusetti wrote:
On 1/5/07, Max Laier <ma...@love2party.net> wrote:
I can say that the first attempt still running fine here on my laptop on a -STABLE as of yesterday. I use it on a daily basis without any glitch. I must say i don't do or tried to do nothing special or network intensive job, but for reading emails, doing a lot of ssh and http/https the drivers is working smoothly.
I will try to compile this new one on my stable during the week end and will see on Monday how it will perform on my office wi-lan.
For the records: my wpi doesn't still work on OpenBSD-current cause it's integrated and the switch used to turn it on seems an acpi one which OpenBSD doesn't attach very well yet.
Hi Folks, I did the port as my searching led me to believe that progress on a driver had stagnated. Port 1: was done by Damien himself (http://lists.freebsd.org/pipermail/freebsd-mobile/2006-July/008768.html) Port 2: was an updated version by Daminen: http://osdir.com/ml/freebsd-hackers...@freebsd.org/msg58154.html which seems to be duplicated here: http://people.freebsd.org/~flz/local/wpi/ (http://www.mail-archive.com/freebsd-net@fr...@) With version 2 being minor bug fixes to version 1 to try and get it working. Since then the driver has come a long way in netbsd with the FreeBSD version just getting older.
To others working on a wpi driver, please post something indicating what you've done and even a sample of what your up to so we can one build one driver that just works. I also did the driver port as everything I found failed to work on a 64bit kernel, most the time wouldn't even compile.
I'm happy to try and maintain this driver. I have the hardware.
The main bugs I know about in this driver port are:
* The use of the iee80211_amrr code The files exist in -current in /usr/src/sys/net80211 but the required symbols are not in a GENERIC kernel build. There is a wlan_amrr module which uses this code, though I'm not sure how to make use of this, it appears a simple dependency on the module is not enough. The use of the 80211_amrr code also means that use under -stable requires quite a bit more work as Rink pointed out.
* Bus resource allocation issues Mainly related to: "bus_dmamem_alloc failed to align memory properly." I'm hoping Mike (http://lists.freebsd.org/pipermail/freebsd-stable/2006-June/026262.html) might be able to help resolve these.
These allocation issues are caused while allocating of the rx & tx ring buffers - which if they are broken explain why things don't work. I'm still coming to grips to how the whole bus_dma_tag_create works. The Netbsd bus_dma_map_alloc seems much more intuitive. I've found if the module failed the first time, unloading it, then reloading it would often make the allocation issues disappear and the driver just work. Though I've also found sometimes that even though the allocation issues are reported, things still work, I'm guessing the alignment is pulled into line by higher levels of bus_dma.
* ifconfig down causes timeouts reseting the tx ring I'm still chasing the cause of this. It seems non critical as the driver still works with an ifconfig up
* Watch dog timer uses an obsolete interface I'm looking into the correct way to do watchdog timing
* A lock order reversal in wpi_intr lock order reversal: 1st 0xffffffff812d9e20 wpi0 (network driver) @ if_wpi.c:1554 2nd 0xffffff003cee32f0 radix node head (radix node head) @ net/route.c:147 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x3a witness_checkorder() at witness_checkorder+0x4f9 _mtx_lock_flags() at _mtx_lock_flags+0x75 rtalloc1() at rtalloc1+0x7a arplookup() at arplookup+0x5c arpintr() at arpintr+0x255 ether_demux() at ether_demux+0x2d3 ether_input() at ether_input+0x1e9 ieee80211_input() at ieee80211_input+0xd05 wpi_intr() at wpi_intr+0x9d7 ithread_loop() at ithread_loop+0xfe fork_exit() at fork_exit+0xaa fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffffffa0698d40, rbp = 0 ---
For those wishing to help debug the driver and get it working, I've posted a new version http://www.clearchain.com/~benjsc/download/20070107-wpi-freebsd.tar.gz
To help debug:
kldload wpi_ucode kldload if_wpi wlandebug -i wpi0 0xffffff (I've included a copy of the -current tool to save having to checkout the tree) sysctl debug.wpi=10 (Debug levels are explained in if_wpi.c) ifconfig wpi0 up ... wait 30 seconds then... ifconfig wpi0 down
Then put /var/log/messages somewhere on the web & let me know
This will dump lots of debug info to syslog but should help me work out whats happening. If the driver works for you, stick to debug level 5 max, else you'll be bombarded with logs. I'll try to install FBSD 32 -current & -stable (32/64) on the laptop in the next week to see what might be different. ANY feedback is helpful.
Finally, for those who see "rx tail flags error xxx" this is caused by a 802.11 frame with an invalid CRC. Hence seeing the occasional one (with debug level 4 or higher) is quiet normal. If you see floods of them then chances are the rx ring is really out of alignment and things will just be busted.
FreeBSD DELL 6.2-STABLE FreeBSD 6.2-STABLE #1: Fri Jan 19 20:32:20 UTC 2007 Bdo@DELL:/usr/obj/usr/src/sys/BDO i386
DELL# tail /var/log/messages Jan 20 18:34:48 DELL kernel: rx intr: idx=63 len=128 stat len=89 rssi=61 rate=a chan=11 tstamp=134327399314interrupt reg 80000008 Jan 20 18:34:48 DELL kernel: rx notification qid=d5 idx=124 flags=0 type=157 len =244 Jan 20 18:34:48 DELL kernel: interrupt reg 80000008 Jan 20 18:34:48 DELL kernel: rx notification qid=d5 idx=125 flags=2 type=27 len= 128 Jan 20 18:34:48 DELL kernel: rx intr: idx=1 len=128 stat len=89 rssi=63 rate=a c han=11 tstamp=134327501715interrupt reg 80000008 Jan 20 18:34:48 DELL kernel: rx notification qid=d5 idx=126 flags=0 type=157 len =244 Jan 20 18:34:48 DELL kernel: sending data: qid=0 idx=118 len=2 nsegs=1 Jan 20 18:34:48 DELL kernel: wpi0: link state changed to DOWN Jan 20 18:34:48 DELL dhclient: connection closed Jan 20 18:34:48 DELL dhclient: exiting.
Also in dmesg
rx intr: idx=39 len=1232 stat len=1193 rssi=4 rate=5 chan=11 tstamp=134441615293rx tail flags error 702 interrupt reg 80000008 rx notification qid=84 idx=238 flags=2 type=27 len=128 rx intr: idx=40 len=128 stat len=89 rssi=63 rate=a chan=11 tstamp=134441677716interrupt reg 80000008 rx notification qid=84 idx=239 flags=0 type=157 len=244 interrupt reg 80000008
rx notification qid=85 idx=12 flags=0 type=157 len=244 interrupt reg 80000008 rx notification qid=85 idx=13 flags=2 type=27 len=128 rx intr: idx=7 len=128 stat len=89 rssi=63 rate=a chan=11 tstamp=134443213720interrupt reg 80000000 rx notification qid=85 idx=14 flags=0 type=157 len=244 interrupt reg 80000008 rx notification qid=85 idx=15 flags=2 type=27 len=128 rx intr: idx=9 len=128 stat len=89 rssi=62 rate=a chan=11 tstamp=134443316118interrupt reg 80000008 rx notification qid=85 idx=16 flags=0 type=157 len=244 interrupt reg 80000008 rx notification qid=85 idx=17 flags=2 type=27 len=128 rx intr: idx=11 len=128 stat len=89 rssi=63 rate=a chan=11 tstamp=134443418515interrupt reg 80000008 rx notification qid=85 idx=18 flags=0 type=157 len=244 interrupt reg 80000008 rx notification qid=85 idx=19 flags=2 type=27 len=128 rx intr: idx=13 len=128 stat len=89 rssi=62 rate=a chan=11 tstamp=134443520918interrupt reg 80000000 rx notification qid=85 idx=20 flags=0 type=157 len=244
-Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/