Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller
HI all, Rene Ladan wrote: [EMAIL PROTECTED] schreef: Michel Talon wrote: For me the driver 0070121-wpi-freebsd.tar.gz as mentioned in the postof Gilbert Cao is the only one that works, and works very well. I am just using it now. My computer is a Sony Vaio VGN C1 in 32 bits mode. I would like to second this. I have tried the 20070125-wpi-freebsd.tar.gz and the 20070131-wpi-freebsd.tar.gz drivers from http://www.clearchain.com/~benjsc/download/, and I get screens full of debug messages [scanning many channels], but the interface always reports 'no carrier'. Same here. The 01/31 driver associated once (I think), but mostly just hangs or crashes my laptop. The 01/21 driver seems to work fine (I get 1 LOR). Laptop: Asus A6JE, card-0x10018086 chip=0x42228086 rev=0x02 hdr=0x00 OS : 7.0-CURRENT i386 2007/02/06 LOR : pci4:1:3: reprobing on driver added wpi0: fatal firmware error wpi0: configure command failed wpi0: could not configure device wpi0: link state changed to UP lock order reversal: 1st 0xc724fb50 wpi0 (network driver) @ if_wpi.c:1555 2nd 0xc075560c udp (udp) @ /usr/src/sys/netinet/udp_usrreq.c:294 KDB: stack backtrace: db_trace_self_wrapper(c0696cf6,e7984a28,c052d735,c0698dc6,c075560c,...) at db_trace_self_wrapper+0x27 kdb_backtrace(c0698dc6,c075560c,c06987e1,c06987e1,c06a3184,...) at kdb_backtrace+0x2f witness_checkorder(c075560c,9,c06a3184,126,0,...) at witness_checkorder+0x6e4 _mtx_lock_flags(c075560c,0,c06a3184,126,c04fa08a,...) at _mtx_lock_flags+0xb9 udp_input(c6cfce00,14,c4e51000,1,0,...) at udp_input+0x221 ip_input(c6cfce00,c06930ee,c6d1882e,c4e51000,c6d1882e,...) at ip_input+0x67f netisr_dispatch(2,c6cfce00,6,3,0,...) at netisr_dispatch+0x68 ether_demux(c4e51000,c6cfce00,3,0,3,9) at ether_demux+0x2e6 ether_input(c4e51000,c6cfce00,c724fa24,c6cfce00,18,...) at ether_input+0x26f ieee80211_deliver_data(c6cfce00,e7984c2c,6,18,c052cf03,...) at ieee80211_deliver_data+0x80 ieee80211_input(c724f008,c6cfce00,c50f9c00,28,0,...) at ieee80211_input+0xb71 wpi_intr(c724f000,0,c06911b0,2aa,1,...) at wpi_intr+0x6df ithread_execute_handlers(c55da480,c4d75800,c06911b0,30e,c53f21b0,...) at ithread_execute_handlers+0x14c ithread_loop(c6383650,e7984d38,c0690f94,328,c55da480,...) at ithread_loop+0x78 fork_exit(c04e14fc,c6383650,e7984d38) at fork_exit+0xcc fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe7984d6c, ebp = 0 --- Regards, Rene I have Compaq nw8440 with this wireless card. After: ifconfig wpi0 up: setting h/w config 1200 firmware status=0xbfbf need val=0x4040 firmware status=0xbfbf need val=0x4040 firmware status=0xbfbf need val=0x4040 firmware status=0x need val=0x4040 firmware status=0xbfbf need val=0x4040 firmware status=0xbfbf need val=0x4040 firmware status=0x need val=0x4040 rx notification qid=80 idx=0 flags=0 type=1 len=36 microcode alive notification version 10d00 alive 1 temperature -212 rx notification qid=4 idx=0 flags=0 type=176 len=4 rx notification qid=4 idx=1 flags=0 type=119 len=4 rx notification qid=4 idx=2 flags=0 type=155 len=4 wpi0: fatal firmware error ((Software Error)) wpi0: configure command failed wpi0: could not configure device After second attempt : setting h/w config 1200 firmware status=0xbfbf need val=0x4040 firmware status=0xbfbf need val=0x4040 firmware status=0xbfbf need val=0x4040 firmware status=0x need val=0x4040 firmware status=0xbfbf need val=0x4040 firmware status=0xbfbf need val=0x4040 firmware status=0x need val=0x4040 wpi0: timeout waiting for adapter to initialize [EMAIL PROTECTED]:0:0: class=0x028000 card=0x135c103c chip=0x42228086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' class= network vmstat -i interrupt total rate irq1: atkbd01023 1 irq9: acpi0 172 0 irq14: ata0 46 0 irq16: pcm0 bge0 12470 15 irq17: wpi0+ 22503 27 irq18: cbb0 uhci2 12362 15 irq19: fwohci0+1 0 irq20: uhci0 ehci0 1 0 irq21: uhci1 1 0 cpu0: timer 1614326 1997 cpu1: timer 1610328 1992 Total3273233 4051 FreeBSD 6.2-STABLE #1: Tue Feb 6 18:47:56 EET 2007 amd64 kldstat Id Refs AddressSize Name 18 0x8010 62e358 kernel 21 0x8072f000 ea50 if_wpi.ko 31 0xa897e000 adde msdosfs.ko 41 0xa8a1f000 c38d snd_hda.ko 51 0xa8a2c000 297desound.ko I'm using 20070131-wpi-freebsd.tar.gz wpi-firmware-kmod-1.0_1 And it is weird because I'm sure few times the wireless goes up and start scanning :) Do you
Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller
Michel Talon wrote: For me the driver 0070121-wpi-freebsd.tar.gz as mentioned in the postof Gilbert Cao is the only one that works, and works very well. I am just using it now. My computer is a Sony Vaio VGN C1 in 32 bits mode. I would like to second this. I have tried the 20070125-wpi-freebsd.tar.gz and the 20070131-wpi-freebsd.tar.gz drivers from http://www.clearchain.com/~benjsc/download/, and I get screens full of debug messages [scanning many channels], but the interface always reports 'no carrier'. I am sending this using the 0070121-wpi-freebsd.tar.gz driver. The machine here is a Toshiba Tecra m6-EZ6611, and I am running FreeBSD 6.2-stable [base system updated 17 Jan 2007]. I'm not much of a hacker, but I can test and send results. I appreciate all the work that has been done, and now I can use this work laptop [they said I could load any OS I wanted on it] without an external wireless card. -- jim smith ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller
[EMAIL PROTECTED] schreef: Michel Talon wrote: For me the driver 0070121-wpi-freebsd.tar.gz as mentioned in the postof Gilbert Cao is the only one that works, and works very well. I am just using it now. My computer is a Sony Vaio VGN C1 in 32 bits mode. I would like to second this. I have tried the 20070125-wpi-freebsd.tar.gz and the 20070131-wpi-freebsd.tar.gz drivers from http://www.clearchain.com/~benjsc/download/, and I get screens full of debug messages [scanning many channels], but the interface always reports 'no carrier'. Same here. The 01/31 driver associated once (I think), but mostly just hangs or crashes my laptop. The 01/21 driver seems to work fine (I get 1 LOR). Laptop: Asus A6JE, card-0x10018086 chip=0x42228086 rev=0x02 hdr=0x00 OS : 7.0-CURRENT i386 2007/02/06 LOR : pci4:1:3: reprobing on driver added wpi0: fatal firmware error wpi0: configure command failed wpi0: could not configure device wpi0: link state changed to UP lock order reversal: 1st 0xc724fb50 wpi0 (network driver) @ if_wpi.c:1555 2nd 0xc075560c udp (udp) @ /usr/src/sys/netinet/udp_usrreq.c:294 KDB: stack backtrace: db_trace_self_wrapper(c0696cf6,e7984a28,c052d735,c0698dc6,c075560c,...) at db_trace_self_wrapper+0x27 kdb_backtrace(c0698dc6,c075560c,c06987e1,c06987e1,c06a3184,...) at kdb_backtrace+0x2f witness_checkorder(c075560c,9,c06a3184,126,0,...) at witness_checkorder+0x6e4 _mtx_lock_flags(c075560c,0,c06a3184,126,c04fa08a,...) at _mtx_lock_flags+0xb9 udp_input(c6cfce00,14,c4e51000,1,0,...) at udp_input+0x221 ip_input(c6cfce00,c06930ee,c6d1882e,c4e51000,c6d1882e,...) at ip_input+0x67f netisr_dispatch(2,c6cfce00,6,3,0,...) at netisr_dispatch+0x68 ether_demux(c4e51000,c6cfce00,3,0,3,9) at ether_demux+0x2e6 ether_input(c4e51000,c6cfce00,c724fa24,c6cfce00,18,...) at ether_input+0x26f ieee80211_deliver_data(c6cfce00,e7984c2c,6,18,c052cf03,...) at ieee80211_deliver_data+0x80 ieee80211_input(c724f008,c6cfce00,c50f9c00,28,0,...) at ieee80211_input+0xb71 wpi_intr(c724f000,0,c06911b0,2aa,1,...) at wpi_intr+0x6df ithread_execute_handlers(c55da480,c4d75800,c06911b0,30e,c53f21b0,...) at ithread_execute_handlers+0x14c ithread_loop(c6383650,e7984d38,c0690f94,328,c55da480,...) at ithread_loop+0x78 fork_exit(c04e14fc,c6383650,e7984d38) at fork_exit+0xcc fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe7984d6c, ebp = 0 --- Regards, Rene -- GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) It won't fit on the line. -- me, 2001 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller
(Sorry hackers, I have forgotten you, and here is my previous post below to freebsd-drivers) On Thu, Feb 01, 2007 at 03:48:49AM -0600, Sam Fourman Jr. wrote: I installed 20070131-wpi-freebsd.tar.gz (file date was 2-1-2007 on the website) I am using a fresh install of 6.2 REALESE when I try ifconfig wpi0 up I get a infinite loop and looks like it is scanning channels scanning channel 6 status 1 a bunch of rx notifications the trouble is the loop never ends Sam Fourman Jr. I tried the wpi 20070131 driver. It seems that I have the same problem as the previous version (20070125). According to the /var/log/messages below, no AP associated, and still scanning. Moreover, those 4 lines seems suspicious. Feb 3 11:45:41 vaio kernel: wpi0: Ethernet address: 00:18:de:5c:cb:9a Feb 3 11:45:41 vaio kernel: wpi0: [GIANT-LOCKED] Feb 3 11:45:41 vaio kernel: wpi0: 11a rates: Feb 3 11:45:41 vaio kernel: wpi0: 11b rates: In the current custom version I have, I have the following lines : Feb 3 12:02:59 vaio kernel: wpi0: Ethernet address: 00:18:de:5c:cb:9a Feb 3 12:02:59 vaio kernel: wpi0: [GIANT-LOCKED] Feb 3 12:02:59 vaio kernel: wpi0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps Feb 3 12:02:59 vaio kernel: wpi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps Feb 3 12:02:59 vaio kernel: wpi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps Here is the /var/log/messages sample. Feb 3 11:45:41 vaio kernel: wpi0: Intel(R) PRO/Wireless 3945ABG mem 0xcc00-0xcc000fff irq 18 at device 0.0 on pci6 Feb 3 11:45:41 vaio kernel: CONTIG ALLOC: size: 44, alignment: 4096 Feb 3 11:45:41 vaio kernel: CONTIG ALLOC: size: 245760, alignment: 4096 Feb 3 11:45:41 vaio kernel: CONTIG ALLOC: size: 16384, alignment: 16384 Feb 3 11:45:41 vaio kernel: bus_dmamem_alloc failed to align memory properly. Feb 3 11:45:41 vaio kernel: CONTIG ALLOC: size: 32768, alignment: 4 Feb 3 11:45:41 vaio kernel: CONTIG ALLOC: size: 16384, alignment: 16384 Feb 3 11:45:41 vaio kernel: bus_dmamem_alloc failed to align memory properly. Feb 3 11:45:41 vaio kernel: CONTIG ALLOC: size: 32768, alignment: 4 Feb 3 11:45:41 vaio kernel: CONTIG ALLOC: size: 16384, alignment: 16384 Feb 3 11:45:41 vaio kernel: bus_dmamem_alloc failed to align memory properly. Feb 3 11:45:41 vaio kernel: CONTIG ALLOC: size: 32768, alignment: 4 Feb 3 11:45:41 vaio kernel: CONTIG ALLOC: size: 16384, alignment: 16384 Feb 3 11:45:41 vaio kernel: bus_dmamem_alloc failed to align memory properly. Feb 3 11:45:41 vaio kernel: CONTIG ALLOC: size: 32768, alignment: 4 Feb 3 11:45:41 vaio kernel: CONTIG ALLOC: size: 16384, alignment: 16384 Feb 3 11:45:41 vaio kernel: bus_dmamem_alloc failed to align memory properly. Feb 3 11:45:41 vaio kernel: CONTIG ALLOC: size: 32768, alignment: 4 Feb 3 11:45:41 vaio kernel: CONTIG ALLOC: size: 16384, alignment: 16384 Feb 3 11:45:41 vaio kernel: bus_dmamem_alloc failed to align memory properly. Feb 3 11:45:41 vaio kernel: CONTIG ALLOC: size: 32768, alignment: 4 Feb 3 11:45:41 vaio kernel: CONTIG ALLOC: size: 512, alignment: 16384 Feb 3 11:45:41 vaio kernel: bus_dmamem_alloc failed to align memory properly. Feb 3 11:45:41 vaio kernel: channel 1 pwr1 0x007c pwr2 0x007a Feb 3 11:45:41 vaio kernel: channel 2 pwr1 0x0077 pwr2 0x007c Feb 3 11:45:41 vaio kernel: channel 3 pwr1 0x008b pwr2 0x008d Feb 3 11:45:41 vaio kernel: channel 4 pwr1 0x008f pwr2 0x008a Feb 3 11:45:41 vaio kernel: channel 5 pwr1 0x pwr2 0x Feb 3 11:45:41 vaio kernel: channel 6 pwr1 0x0080 pwr2 0x007f Feb 3 11:45:41 vaio kernel: channel 7 pwr1 0x007f pwr2 0x0080 Feb 3 11:45:41 vaio kernel: channel 8 pwr1 0x0085 pwr2 0x0085 Feb 3 11:45:41 vaio kernel: channel 9 pwr1 0x0086 pwr2 0x0085 Feb 3 11:45:41 vaio kernel: channel 10 pwr1 0x pwr2 0x Feb 3 11:45:41 vaio kernel: channel 11 pwr1 0xfffe pwr2 0xfffe Feb 3 11:45:41 vaio kernel: channel 12 pwr1 0x pwr2 0xfffe Feb 3 11:45:41 vaio kernel: channel 13 pwr1 0xfffe pwr2 0xfffe Feb 3 11:45:41 vaio kernel: channel 14 pwr1 0x pwr2 0xfffe Feb 3 11:45:41 vaio kernel: wpi0: Ethernet address: 00:18:de:5c:cb:9a Feb 3 11:45:41 vaio kernel: wpi0: [GIANT-LOCKED] Feb 3 11:45:41 vaio kernel: wpi0: 11a rates: Feb 3 11:45:41 vaio kernel: wpi0: 11b rates: Feb 3 11:45:41 vaio kernel: setting h/w config 1200 Feb 3 11:45:41 vaio kernel: firmware status=0xbfbf need val=0x4040 Feb 3 11:45:41 vaio last message repeated 2 times Feb 3 11:45:41 vaio kernel: firmware status=0x need val=0x4040 Feb 3 11:45:41 vaio kernel: firmware status=0xbfbf need val=0x4040 Feb 3 11:45:41 vaio kernel: firmware status=0xbfbf need val=0x4040 Feb 3 11:45:41 vaio kernel: firmware status=0x need val=0x4040 Feb 3 11:45:41 vaio kernel: rx notification qid=80 idx=0 flags=0 type=1 len=36 Feb 3 11:45:41 vaio kernel: microcode alive notification version 10d00 alive 1 Feb 3 11:45:41 vaio kernel:
Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller
A new version of the driver is up which fixes the firmware issues. Seems the wpi-firmware-kmod port was creating corrupt modules. Things should work much better now. Download at the same place, file: 20070131-wpi-freebsd.tar.gz Unfortunately, i must report that this last version still does not work for me. Even worse the computer is flooded with error messages to the point it is hard to reboot. These are like so: Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=92 flags=0 type=131 len=20 Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=93 flags=0 type=157 len=244 Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=94 flags=0 type=130 len=24 Feb 3 00:11:31 rose kernel: scanning channel 14 status 1 Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=95 flags=0 type=131 len=20 Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=96 flags=0 type=132 len=16 Feb 3 00:11:31 rose kernel: scan finished nchan=14 status=1 chan=14 Feb 3 00:11:31 rose kernel: rx notification qid=4 idx=136 flags=0 type=128 len=8 Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=97 flags=0 type=157 len=244 Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=98 flags=0 type=130 len=24 Feb 3 00:11:31 rose kernel: scanning channel 36 status 1 continually repeating and the WLAN light never lights up. For me the driver 0070121-wpi-freebsd.tar.gz as mentioned in the postof Gilbert Cao is the only one that works, and works very well. I am just using it now. My computer is a Sony Vaio VGN C1 in 32 bits mode. -- Michel Talon ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller
Michel, I was told a few days ago that those messages are nothing more than debug messages, and that is how it is supposed to work. Sam Fourman Jr. On 2/2/07, Michel Talon [EMAIL PROTECTED] wrote: A new version of the driver is up which fixes the firmware issues. Seems the wpi-firmware-kmod port was creating corrupt modules. Things should work much better now. Download at the same place, file: 20070131-wpi-freebsd.tar.gz Unfortunately, i must report that this last version still does not work for me. Even worse the computer is flooded with error messages to the point it is hard to reboot. These are like so: Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=92 flags=0 type=131 len=20 Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=93 flags=0 type=157 len=244 Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=94 flags=0 type=130 len=24 Feb 3 00:11:31 rose kernel: scanning channel 14 status 1 Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=95 flags=0 type=131 len=20 Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=96 flags=0 type=132 len=16 Feb 3 00:11:31 rose kernel: scan finished nchan=14 status=1 chan=14 Feb 3 00:11:31 rose kernel: rx notification qid=4 idx=136 flags=0 type=128 len=8 Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=97 flags=0 type=157 len=244 Feb 3 00:11:31 rose kernel: rx notification qid=96 idx=98 flags=0 type=130 len=24 Feb 3 00:11:31 rose kernel: scanning channel 36 status 1 continually repeating and the WLAN light never lights up. For me the driver 0070121-wpi-freebsd.tar.gz as mentioned in the postof Gilbert Cao is the only one that works, and works very well. I am just using it now. My computer is a Sony Vaio VGN C1 in 32 bits mode. -- Michel Talon ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller
Hi Folks, A new version of the driver is up which fixes the firmware issues. Seems the wpi-firmware-kmod port was creating corrupt modules. Things should work much better now. Download at the same place, file: 20070131-wpi-freebsd.tar.gz Cheers, Benjamin Sam Fourman Jr. wrote: I can also confirm that i get the firmware_get: failed to load firmware image wpi_fw on the 20070125 version. I should note that I tried it on a fresh 6.2 RELEASE install. Sam Fourman Jr. On 1/27/07, Gilbert Cao [EMAIL PROTECTED] wrote: On Fri, Jan 26, 2007 at 11:09:51PM +1030, Benjamin Close wrote: Hi Gilbert, Thanks for the custom version. I've integrated the changes into the driver I'm working on. For those wanting to test out the driver which is now fully up to date with all change from NetBSD OpenBSD - and has a few minor improvements over them, grab it from: http://www.clearchain.com/~benjsc/download/ File is: 20070125-wpi-freebsd.tar.gz Full instructions on how to build / install the driver are in the README in the tar file. This should work both under -current and 6.2-Stable now. Info about the driver and what's working/broken can be found at: http://www.clearchain.com/wiki/wpi Cheers, Benjamin I have tried the new 20070125 version. However, I did not manage to make work. At least, it compiles. I have installed, both wpi_fw.ko and the if_wpi.ko, as the README said. wpi_fw.ko lies in /boot/modules and if_wpi.ko in /boot/kernel. When, I kldload if_wpi, here is a small sample of /var/log/messages Jan 27 10:30:39 vaio kernel: wpi0: Intel(R) PRO/Wireless 3945ABG mem 0xcc00-0xcc000fff irq 18 at device 0.0 on pci6 Jan 27 10:30:39 vaio kernel: bus_dmamem_alloc failed to align memory properly. Jan 27 10:30:39 vaio last message repeated 6 times Jan 27 10:30:39 vaio kernel: wpi0: Ethernet address: 00:18:de:5c:cb:9a Jan 27 10:30:39 vaio kernel: wpi0: [GIANT-LOCKED] Jan 27 10:30:39 vaio kernel: wpi0: 11a rates: Jan 27 10:30:39 vaio kernel: wpi0: 11b rates: Jan 27 10:30:40 vaio kernel: firmware_get: failed to load firmware image wpi_fw Jan 27 10:30:40 vaio kernel: wpi0: could not load firmware image 'wpi_fw' Jan 27 10:30:40 vaio kernel: firmware_get: failed to load firmware image wpi_fw Jan 27 10:30:40 vaio kernel: wpi0: could not load firmware image 'wpi_fw' Jan 27 10:32:19 vaio kernel: firmware_get: failed to load firmware image wpi_fw Jan 27 10:32:19 vaio kernel: wpi0: could not load firmware image 'wpi_fw' In kldstat, both modules are loaded. Then, I have kldunload if_wpi (and if_wpi seems to be reload, automatically, I don't know why). Same problem, it seems that wpi_fw could not be load (found ?). As a result, no AP is associated. After a fresh reboot, I have reinstall the custom 20070121 version of mine, and all returns OK. Another strange thing: when kldload if_wpi with 20070121 version, and then kldstat, I don't see wpi_ucode. It seems that wpi_ucode.ko does not need to be loaded, in my case. My wpi_ucode.ko lies in /boot/modules After another fresh reboot, I first moved wpi_ucode.ko to another place. When I kldload if_wpi, I got the following message: Jan 27 09:47:16 vaio kernel: wpi0: Intel(R) PRO/Wireless 3945ABG mem 0xcc00-0xcc000fff irq 18 at device 0.0 on pci6 Jan 27 09:47:16 vaio kernel: bus_dmamem_alloc failed to align memory properly. Jan 27 09:47:16 vaio last message repeated 6 times Jan 27 09:47:16 vaio kernel: wpi0: Ethernet address: 00:18:de:5c:cb:9a Jan 27 09:47:16 vaio kernel: wpi0: [GIANT-LOCKED] Jan 27 09:47:16 vaio kernel: wpi0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps Jan 27 09:47:16 vaio kernel: wpi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps Jan 27 09:47:16 vaio kernel: wpi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps Jan 27 09:47:16 vaio kernel: firmware_get: failed to load firmware image wpi_ucode Jan 27 09:47:16 vaio kernel: wpi0: could not load firmware image 'wpi_ucode' So, it seems that wpi_ucode.ko have to lied in my /boot/modules (the place where I have also put if_wpi 20070121 version), even if it is not loaded. -- (hika) Gilbert Cao http://www.miaouirc.com - MiaouIRC Project 2002-2003 http://www.bsdmon.com - The BSD DMON Power to serve IRC : #miaule at IRCNET Network ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-drivers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller
Benjamin Close wrote: Hi Folks, A new version of the driver is up which fixes the firmware issues. Seems the wpi-firmware-kmod port was creating corrupt modules. Things should work much better now. Download at the same place, file: 20070131-wpi-freebsd.tar.gz So, when is it going to HEAD? :-) -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer signature.asc Description: OpenPGP digital signature
Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller
On Fri, Jan 26, 2007 at 11:09:51PM +1030, Benjamin Close wrote: Hi Gilbert, Thanks for the custom version. I've integrated the changes into the driver I'm working on. For those wanting to test out the driver which is now fully up to date with all change from NetBSD OpenBSD - and has a few minor improvements over them, grab it from: http://www.clearchain.com/~benjsc/download/ File is: 20070125-wpi-freebsd.tar.gz Full instructions on how to build / install the driver are in the README in the tar file. This should work both under -current and 6.2-Stable now. Info about the driver and what's working/broken can be found at: http://www.clearchain.com/wiki/wpi Cheers, Benjamin I have tried the new 20070125 version. However, I did not manage to make work. At least, it compiles. I have installed, both wpi_fw.ko and the if_wpi.ko, as the README said. wpi_fw.ko lies in /boot/modules and if_wpi.ko in /boot/kernel. When, I kldload if_wpi, here is a small sample of /var/log/messages Jan 27 10:30:39 vaio kernel: wpi0: Intel(R) PRO/Wireless 3945ABG mem 0xcc00-0xcc000fff irq 18 at device 0.0 on pci6 Jan 27 10:30:39 vaio kernel: bus_dmamem_alloc failed to align memory properly. Jan 27 10:30:39 vaio last message repeated 6 times Jan 27 10:30:39 vaio kernel: wpi0: Ethernet address: 00:18:de:5c:cb:9a Jan 27 10:30:39 vaio kernel: wpi0: [GIANT-LOCKED] Jan 27 10:30:39 vaio kernel: wpi0: 11a rates: Jan 27 10:30:39 vaio kernel: wpi0: 11b rates: Jan 27 10:30:40 vaio kernel: firmware_get: failed to load firmware image wpi_fw Jan 27 10:30:40 vaio kernel: wpi0: could not load firmware image 'wpi_fw' Jan 27 10:30:40 vaio kernel: firmware_get: failed to load firmware image wpi_fw Jan 27 10:30:40 vaio kernel: wpi0: could not load firmware image 'wpi_fw' Jan 27 10:32:19 vaio kernel: firmware_get: failed to load firmware image wpi_fw Jan 27 10:32:19 vaio kernel: wpi0: could not load firmware image 'wpi_fw' In kldstat, both modules are loaded. Then, I have kldunload if_wpi (and if_wpi seems to be reload, automatically, I don't know why). Same problem, it seems that wpi_fw could not be load (found ?). As a result, no AP is associated. After a fresh reboot, I have reinstall the custom 20070121 version of mine, and all returns OK. Another strange thing: when kldload if_wpi with 20070121 version, and then kldstat, I don't see wpi_ucode. It seems that wpi_ucode.ko does not need to be loaded, in my case. My wpi_ucode.ko lies in /boot/modules After another fresh reboot, I first moved wpi_ucode.ko to another place. When I kldload if_wpi, I got the following message: Jan 27 09:47:16 vaio kernel: wpi0: Intel(R) PRO/Wireless 3945ABG mem 0xcc00-0xcc000fff irq 18 at device 0.0 on pci6 Jan 27 09:47:16 vaio kernel: bus_dmamem_alloc failed to align memory properly. Jan 27 09:47:16 vaio last message repeated 6 times Jan 27 09:47:16 vaio kernel: wpi0: Ethernet address: 00:18:de:5c:cb:9a Jan 27 09:47:16 vaio kernel: wpi0: [GIANT-LOCKED] Jan 27 09:47:16 vaio kernel: wpi0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps Jan 27 09:47:16 vaio kernel: wpi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps Jan 27 09:47:16 vaio kernel: wpi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps Jan 27 09:47:16 vaio kernel: firmware_get: failed to load firmware image wpi_ucode Jan 27 09:47:16 vaio kernel: wpi0: could not load firmware image 'wpi_ucode' So, it seems that wpi_ucode.ko have to lied in my /boot/modules (the place where I have also put if_wpi 20070121 version), even if it is not loaded. -- (hika) Gilbert Cao http://www.miaouirc.com - MiaouIRC Project 2002-2003 http://www.bsdmon.com - The BSD DMON Power to serve IRC : #miaule at IRCNET Network pgp7rkDuJbL9V.pgp Description: PGP signature
Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller
I can also confirm that i get the firmware_get: failed to load firmware image wpi_fw on the 20070125 version. I should note that I tried it on a fresh 6.2 RELEASE install. Sam Fourman Jr. On 1/27/07, Gilbert Cao [EMAIL PROTECTED] wrote: On Fri, Jan 26, 2007 at 11:09:51PM +1030, Benjamin Close wrote: Hi Gilbert, Thanks for the custom version. I've integrated the changes into the driver I'm working on. For those wanting to test out the driver which is now fully up to date with all change from NetBSD OpenBSD - and has a few minor improvements over them, grab it from: http://www.clearchain.com/~benjsc/download/ File is: 20070125-wpi-freebsd.tar.gz Full instructions on how to build / install the driver are in the README in the tar file. This should work both under -current and 6.2-Stable now. Info about the driver and what's working/broken can be found at: http://www.clearchain.com/wiki/wpi Cheers, Benjamin I have tried the new 20070125 version. However, I did not manage to make work. At least, it compiles. I have installed, both wpi_fw.ko and the if_wpi.ko, as the README said. wpi_fw.ko lies in /boot/modules and if_wpi.ko in /boot/kernel. When, I kldload if_wpi, here is a small sample of /var/log/messages Jan 27 10:30:39 vaio kernel: wpi0: Intel(R) PRO/Wireless 3945ABG mem 0xcc00-0xcc000fff irq 18 at device 0.0 on pci6 Jan 27 10:30:39 vaio kernel: bus_dmamem_alloc failed to align memory properly. Jan 27 10:30:39 vaio last message repeated 6 times Jan 27 10:30:39 vaio kernel: wpi0: Ethernet address: 00:18:de:5c:cb:9a Jan 27 10:30:39 vaio kernel: wpi0: [GIANT-LOCKED] Jan 27 10:30:39 vaio kernel: wpi0: 11a rates: Jan 27 10:30:39 vaio kernel: wpi0: 11b rates: Jan 27 10:30:40 vaio kernel: firmware_get: failed to load firmware image wpi_fw Jan 27 10:30:40 vaio kernel: wpi0: could not load firmware image 'wpi_fw' Jan 27 10:30:40 vaio kernel: firmware_get: failed to load firmware image wpi_fw Jan 27 10:30:40 vaio kernel: wpi0: could not load firmware image 'wpi_fw' Jan 27 10:32:19 vaio kernel: firmware_get: failed to load firmware image wpi_fw Jan 27 10:32:19 vaio kernel: wpi0: could not load firmware image 'wpi_fw' In kldstat, both modules are loaded. Then, I have kldunload if_wpi (and if_wpi seems to be reload, automatically, I don't know why). Same problem, it seems that wpi_fw could not be load (found ?). As a result, no AP is associated. After a fresh reboot, I have reinstall the custom 20070121 version of mine, and all returns OK. Another strange thing: when kldload if_wpi with 20070121 version, and then kldstat, I don't see wpi_ucode. It seems that wpi_ucode.ko does not need to be loaded, in my case. My wpi_ucode.ko lies in /boot/modules After another fresh reboot, I first moved wpi_ucode.ko to another place. When I kldload if_wpi, I got the following message: Jan 27 09:47:16 vaio kernel: wpi0: Intel(R) PRO/Wireless 3945ABG mem 0xcc00-0xcc000fff irq 18 at device 0.0 on pci6 Jan 27 09:47:16 vaio kernel: bus_dmamem_alloc failed to align memory properly. Jan 27 09:47:16 vaio last message repeated 6 times Jan 27 09:47:16 vaio kernel: wpi0: Ethernet address: 00:18:de:5c:cb:9a Jan 27 09:47:16 vaio kernel: wpi0: [GIANT-LOCKED] Jan 27 09:47:16 vaio kernel: wpi0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps Jan 27 09:47:16 vaio kernel: wpi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps Jan 27 09:47:16 vaio kernel: wpi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps Jan 27 09:47:16 vaio kernel: firmware_get: failed to load firmware image wpi_ucode Jan 27 09:47:16 vaio kernel: wpi0: could not load firmware image 'wpi_ucode' So, it seems that wpi_ucode.ko have to lied in my /boot/modules (the place where I have also put if_wpi 20070121 version), even if it is not loaded. -- (hika) Gilbert Cao http://www.miaouirc.com - MiaouIRC Project 2002-2003 http://www.bsdmon.com - The BSD DMON Power to serve IRC : #miaule at IRCNET Network ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller
Gilbert Cao wrote: Snip As I have posted a message here: http://lists.freebsd.org/pipermail/freebsd-questions/2007-January/140475.html I have put a custom version of mine from your last package here: http://www.bsdmon.com/download/20070121-wpi-freebsd.tar.gz What I have mainly done is to make the package compile and work (for me a least) on 6.2-RELEASE (and possibly other 6.x ?). Don't know if you will ignore it or not, but I feel like I should have post it here, anyway. As it works well, now for my daily uses (reading mail, surfing on the HTTP, playing Q3 ;), I may post some debug output, if needed, but I keep using 6.2, no -current. The post may be off topic, sorry .. Hi Gilbert, Thanks for the custom version. I've integrated the changes into the driver I'm working on. For those wanting to test out the driver which is now fully up to date with all change from NetBSD OpenBSD - and has a few minor improvements over them, grab it from: http://www.clearchain.com/~benjsc/download/ File is: 20070125-wpi-freebsd.tar.gz Full instructions on how to build / install the driver are in the README in the tar file. This should work both under -current and 6.2-Stable now. Info about the driver and what's working/broken can be found at: http://www.clearchain.com/wiki/wpi Cheers, Benjamin ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller
On 1/26/07, Benjamin Close [EMAIL PROTECTED] wrote: Gilbert Cao wrote: Snip As I have posted a message here: http://lists.freebsd.org/pipermail/freebsd-questions/2007-January/140475.html I have put a custom version of mine from your last package here: http://www.bsdmon.com/download/20070121-wpi-freebsd.tar.gz What I have mainly done is to make the package compile and work (for me a least) on 6.2-RELEASE (and possibly other 6.x ?). Don't know if you will ignore it or not, but I feel like I should have post it here, anyway. As it works well, now for my daily uses (reading mail, surfing on the HTTP, playing Q3 ;), I may post some debug output, if needed, but I keep using 6.2, no -current. The post may be off topic, sorry .. Hi Gilbert, Thanks for the custom version. I've integrated the changes into the driver I'm working on. For those wanting to test out the driver which is now fully up to date with all change from NetBSD OpenBSD - and has a few minor improvements over them, grab it from: http://www.clearchain.com/~benjsc/download/ File is: 20070125-wpi-freebsd.tar.gz Full instructions on how to build / install the driver are in the README in the tar file. This should work both under -current and 6.2-Stable now. Info about the driver and what's working/broken can be found at: http://www.clearchain.com/wiki/wpi Cheers, Benjamin Great stuff, now the wlan speed is much much faster, thank you for the hard a nice work ;) -- Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller
On Sat, Jan 20, 2007 at 06:38:46PM +, Abdullah Al-Marrie wrote: [..] Well, sorry to post in *this* thread. It may not be appropriate, but I just subscribe to freebsd-drivers :p. On 1/7/07, Benjamin Close [EMAIL PROTECTED] wrote: 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. [..] 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 As I have posted a message here: http://lists.freebsd.org/pipermail/freebsd-questions/2007-January/140475.html I have put a custom version of mine from your last package here: http://www.bsdmon.com/download/20070121-wpi-freebsd.tar.gz What I have mainly done is to make the package compile and work (for me a least) on 6.2-RELEASE (and possibly other 6.x ?). Don't know if you will ignore it or not, but I feel like I should have post it here, anyway. As it works well, now for my daily uses (reading mail, surfing on the HTTP, playing Q3 ;), I may post some debug output, if needed, but I keep using 6.2, no -current. The post may be off topic, sorry ... -- (hika) Gilbert Cao http://www.miaouirc.com - MiaouIRC Project 2002-2003 http://www.bsdmon.com - The BSD DMON Power to serve IRC : #miaule at IRCNET Network pgpvUOCtJmQWl.pgp Description: PGP signature
Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller
On 1/7/07, Benjamin Close [EMAIL PROTECTED] wrote: Massimo Lusetti wrote: On 1/5/07, Max Laier [EMAIL PROTECTED] wrote: Thoughts? Volunteers? 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@freebsd.org/msg20710.html) 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 0x812d9e20 wpi0 (network driver) @ if_wpi.c:1554 2nd 0xff003cee32f0 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 = 0xa0698d40, 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 0xff (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
Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller
Hello everyone, I have a Lenovo N 100 0768 DKU notebook with a 3945 wireless card installed I just installed the FreeBSD 6.2 Realese on it, What instructions do I have to follow to compile and install the Driver so I may test it for everyone? Thank you for any help at all Sam Fourman Jr, On 1/7/07, Joel Dahl [EMAIL PROTECTED] wrote: Mån 2007-01-08 klockan 00:05 +1030 skrev Benjamin Close: 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@freebsd.org/msg20710.html) 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. Gavin Atkinson (CC'ed) is AFAIK also working on wpi(4) for FreeBSD, according to his announcement on net@: http://lists.freebsd.org/pipermail/freebsd-net/2006-December/012808.html -- Joel ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller
Massimo Lusetti wrote: On 1/5/07, Max Laier [EMAIL PROTECTED] wrote: Thoughts? Volunteers? 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@freebsd.org/msg20710.html) 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 0x812d9e20 wpi0 (network driver) @ if_wpi.c:1554 2nd 0xff003cee32f0 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 = 0xa0698d40, 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 0xff (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
Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller
On Sunday 07 January 2007 14:35, Benjamin Close wrote: Massimo Lusetti wrote: On 1/5/07, Max Laier [EMAIL PROTECTED] wrote: Thoughts? Volunteers? 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.htm l) 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@freebsd.org/msg20710.html) 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. Excellent! 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.htm l) 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 I have patches for iwi(4) somewhere and should finally get to doing something with them ... * A lock order reversal in wpi_intr lock order reversal: 1st 0x812d9e20 wpi0 (network driver) @ if_wpi.c:1554 2nd 0xff003cee32f0 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 = 0xa0698d40, rbp = 0 --- This one looks like the same issue as if_iwi.c, 1.43: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/iwi/if_iwi.c#rev1.43 i.e. just drop the driver lock when calling back into the (net80211) stack. There is some discussion about how the ic is protected, but for now dropping the lock is the right thing to do. 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 Your box seems to have a reasonable uptime. Is that right, or should I continue to mirror your tarballs? To help debug: kldload wpi_ucode kldload if_wpi
Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller
Mån 2007-01-08 klockan 00:05 +1030 skrev Benjamin Close: 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@freebsd.org/msg20710.html) 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. Gavin Atkinson (CC'ed) is AFAIK also working on wpi(4) for FreeBSD, according to his announcement on net@: http://lists.freebsd.org/pipermail/freebsd-net/2006-December/012808.html -- Joel ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller
Hi All, After getting a new laptop I discovered being tied to a wire when your used to wireless is extremely annoying. Hence I've done a port of the NetBSD driver wpi (20070106 rev) for the Intel3945ABG wireless card to FreeBSD Many thanks to Damien for writing the NetBSD driver in the first place and the initial FreeBSD port which I referenced extensively. The driver is available at: http://www.clearchain.com/~benjsc/download/20070106-wpi-freebsd.tar.gz (dynamic dns host, so just retry later if it's down): Please let me know if you have any issues and I'll try to address them. I'm not sure how well it will work on -stable, I'm running FreeBSD wolf.clearchain.com 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Wed Dec 13 16:09:21 CST 2006 [EMAIL PROTECTED]:/usr/src/sys/amd64/compile/GENERIC amd64 and don't have a -stable machine for testing. Those not using -current, be sure to remove #define WPI_CURRENT in if_wpi.c before compiling. This email was sent through the driver :) Cheers, Benjamin ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller
On Friday 05 January 2007 15:45, Benjamin Close wrote: Hi All, After getting a new laptop I discovered being tied to a wire when your used to wireless is extremely annoying. Hence I've done a port of the NetBSD driver wpi (20070106 rev) for the Intel3945ABG wireless card to FreeBSD Many thanks to Damien for writing the NetBSD driver in the first place and the initial FreeBSD port which I referenced extensively. The driver is available at: http://www.clearchain.com/~benjsc/download/20070106-wpi-freebsd.tar.gz (dynamic dns host, so just retry later if it's down): Mirror'ed at: http://people.freebsd.org/~mlaier/wpi_port/ Please let me know if you have any issues and I'll try to address them. I'm not sure how well it will work on -stable, I'm running FreeBSD wolf.clearchain.com 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Wed Dec 13 16:09:21 CST 2006 [EMAIL PROTECTED]:/usr/src/sys/amd64/compile/GENERIC amd64 and don't have a -stable machine for testing. Those not using -current, be sure to remove #define WPI_CURRENT in if_wpi.c before compiling. This email was sent through the driver :) -- /\ Best regards, | [EMAIL PROTECTED] \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | [EMAIL PROTECTED] / \ ASCII Ribbon Campaign | Against HTML Mail and News pgpJwRS6CI5lR.pgp Description: PGP signature
Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller
Max Laier wrote: On Friday 05 January 2007 15:45, Benjamin Close wrote: Hi All, After getting a new laptop I discovered being tied to a wire when your used to wireless is extremely annoying. Hence I've done a port of the NetBSD driver wpi (20070106 rev) for the Intel3945ABG wireless card to FreeBSD Many thanks to Damien for writing the NetBSD driver in the first place and the initial FreeBSD port which I referenced extensively. The driver is available at: http://www.clearchain.com/~benjsc/download/20070106-wpi-freebsd.tar.gz (dynamic dns host, so just retry later if it's down): Mirror'ed at: http://people.freebsd.org/~mlaier/wpi_port/ Please let me know if you have any issues and I'll try to address them. I'm not sure how well it will work on -stable, I'm running FreeBSD wolf.clearchain.com 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Wed Dec 13 16:09:21 CST 2006 [EMAIL PROTECTED]:/usr/src/sys/amd64/compile/GENERIC amd64 and don't have a -stable machine for testing. Those not using -current, be sure to remove #define WPI_CURRENT in if_wpi.c before compiling. This email was sent through the driver :) While I'm really happy to see people working on this, isn't this a duplicated effort? This is at least the third attempt to get a wpi(4) driver on FreeBSD (and I'm sure two of them are based on Damien's driver). I might be missing something though. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer signature.asc Description: OpenPGP digital signature
Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller
On Friday 05 January 2007 16:58, Florent Thoumie wrote: Max Laier wrote: On Friday 05 January 2007 15:45, Benjamin Close wrote: Hi All, After getting a new laptop I discovered being tied to a wire when your used to wireless is extremely annoying. Hence I've done a port of the NetBSD driver wpi (20070106 rev) for the Intel3945ABG wireless card to FreeBSD Many thanks to Damien for writing the NetBSD driver in the first place and the initial FreeBSD port which I referenced extensively. The driver is available at: http://www.clearchain.com/~benjsc/download/20070106-wpi-freebsd.tar. gz (dynamic dns host, so just retry later if it's down): Mirror'ed at: http://people.freebsd.org/~mlaier/wpi_port/ Please let me know if you have any issues and I'll try to address them. I'm not sure how well it will work on -stable, I'm running FreeBSD wolf.clearchain.com 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Wed Dec 13 16:09:21 CST 2006 [EMAIL PROTECTED]:/usr/src/sys/amd64/compile/GENERIC amd64 and don't have a -stable machine for testing. Those not using -current, be sure to remove #define WPI_CURRENT in if_wpi.c before compiling. This email was sent through the driver :) While I'm really happy to see people working on this, isn't this a duplicated effort? This is at least the third attempt to get a wpi(4) driver on FreeBSD (and I'm sure two of them are based on Damien's driver). I might be missing something though. Hence the extensive CC-list ... I'm trying to get all people involved to talk to each other and coordinate. From what I hear the other drivers showed some problems regarding resource allocation - maybe this one does better ... I'm more than willing to shepherd one of these drivers into the tree, but I'd need people with the actual hardware to say: Yes it works (for a large enough fraction of cases) and possibly somebody to serve as a maintainer willing to deal with PRs and stuff in the future. Given that part one of this is fullfilled by either of the available drivers - let's get something in and work from there. Thoughts? Volunteers? -- /\ Best regards, | [EMAIL PROTECTED] \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | [EMAIL PROTECTED] / \ ASCII Ribbon Campaign | Against HTML Mail and News pgppQgFMSDRRG.pgp Description: PGP signature
Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller
On 1/5/07, Max Laier [EMAIL PROTECTED] wrote: Thoughts? Volunteers? 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. Best regards -- Massimo http://meridio.blogspot.com ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller
Max Laier schreef: On Friday 05 January 2007 16:58, Florent Thoumie wrote: Max Laier wrote: On Friday 05 January 2007 15:45, Benjamin Close wrote: Hi All, After getting a new laptop I discovered being tied to a wire when your used to wireless is extremely annoying. Hence I've done a port of the NetBSD driver wpi (20070106 rev) for the Intel3945ABG wireless card to FreeBSD Many thanks to Damien for writing the NetBSD driver in the first place and the initial FreeBSD port which I referenced extensively. The driver is available at: http://www.clearchain.com/~benjsc/download/20070106-wpi-freebsd.tar. gz (dynamic dns host, so just retry later if it's down): Mirror'ed at: http://people.freebsd.org/~mlaier/wpi_port/ Please let me know if you have any issues and I'll try to address them. I'm not sure how well it will work on -stable, I'm running FreeBSD wolf.clearchain.com 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Wed Dec 13 16:09:21 CST 2006 [EMAIL PROTECTED]:/usr/src/sys/amd64/compile/GENERIC amd64 and don't have a -stable machine for testing. Those not using -current, be sure to remove #define WPI_CURRENT in if_wpi.c before compiling. This email was sent through the driver :) While I'm really happy to see people working on this, isn't this a duplicated effort? This is at least the third attempt to get a wpi(4) driver on FreeBSD (and I'm sure two of them are based on Damien's driver). I might be missing something though. Hence the extensive CC-list ... I'm trying to get all people involved to talk to each other and coordinate. From what I hear the other drivers showed some problems regarding resource allocation - maybe this one does better ... [...] Added Gavin Atkinson to the CC list, he is working on a wpi(4) clone which I'm using at the moment. It has some memory corruption error, but is otherwise behaving quite good. Regards, Rene -- GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) It won't fit on the line. -- me, 2001 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller
Hi Benajmin, On Sat, Jan 06, 2007 at 01:15:11AM +1030, Benjamin Close wrote: Hi All, After getting a new laptop I discovered being tied to a wire when your used to wireless is extremely annoying. Hence I've done a port of the NetBSD driver wpi (20070106 rev) for the Intel3945ABG wireless card to FreeBSD Many thanks to Damien for writing the NetBSD driver in the first place and the initial FreeBSD port which I referenced extensively. The driver is available at: http://www.clearchain.com/~benjsc/download/20070106-wpi-freebsd.tar.gz (dynamic dns host, so just retry later if it's down): Please let me know if you have any issues and I'll try to address them. I'm not sure how well it will work on -stable, I'm running FreeBSD wolf.clearchain.com 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Wed Dec 13 16:09:21 CST 2006 [EMAIL PROTECTED]:/usr/src/sys/amd64/compile/GENERIC amd64 and don't have a -stable machine for testing. Those not using -current, be sure to remove #define WPI_CURRENT in if_wpi.c before compiling. This email was sent through the driver :) This is FreeBSD 6-STABLE of 19 Dec; laptop is a Dell Latitude D820. The driver loads OK. Mind you, I had to manually copy the wlan_amrr code from CURRENT to get it to compile on this STABLE box (along with some minor .h file merging). However, it does not work correctly. dmesg(8) output can be found on http://rink.nu/tmp/dmesg-wpi Any advice would be very appreciated! Thanks for working on this! -- Rink P.W. Springer- http://rink.nu It is such a quiet thing, to fall. But yet a far more terrible thing, to admit it.- Darth Traya smime.p7s Description: S/MIME cryptographic signature
Re: Updated Driver for 3945ABG Intel 3945ABG Wireless LAN controller
Rene Ladan schrieb: [...] Added Gavin Atkinson to the CC list, he is working on a wpi(4) clone which I'm using at the moment. It has some memory corruption error, but is otherwise behaving quite good. Regards, Rene I did a quick try with this driver and unfortunately it suffers from the same allocation issue as the old one. I talked to Gavin about this issue and I promised I'll provide him the pieces of information he asked when I have a bit more time, but I have a very busy period now due to the uni exams. The problem seems to be the same for both version. Regards, Gabor ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
