WPI Driver Support (WAS: Re: mode 11g, but 6Mbps)
On 7/24/07, Tom Evans <[EMAIL PROTECTED]> wrote: On Tue, 2007-07-24 at 11:42 +0200, Pietro Cerutti wrote: > Federico Lorenzi wrote: > > On 7/24/07, Pietro Cerutti <[EMAIL PROTECTED]> wrote: > >> Hi List, > >> I have an Intel PRO/Wireless 3945ABG adapter using the wpi0 driver > >> connecting to an access point using the 802.11g mode. > >> # ifconfig wpi0 mode 11g > >> # ifconfig wpi0 > >> ... > >> media: IEEE 802.11 Wireless Ethernet autoselect mode 11g (OFDM/6Mbps) > >> ... > >> > >> Can anyone explain why I see OFDM/6Mbps instead of OFDM/54Mbps (or at > >> least 19Mbps if you mean the actual throughput?) > > It could depend on a few things, first off remember that it's a highly > > experimental driver at > > this stage, and don't mean to be stating the obvious, but are you > > actually close enough to > > the AP to get 54mbps? Windows says 54 / 11 no matter what speed it is > > running at. > > Hi Federico, > > Actually I'm 4 meters away from the AP. > I know that wpi is still in pre-alpha state ;-) > > Tnx > Heh, at least you have some connectivity - mine is still using none! [EMAIL PROTECTED]:0:0: class=0x028000 card=0x135c103c chip=0x42228086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '3945ABG Intel 3945ABG Wireless LAN controller' class = network Driver either fails to initialise, or panic's my -CURRENT laptop :) I'd think its highly likely that performance issues are due to pre-release quality of the driver. I have the same problem too, which forces me to use a 2 year old atheros pcmcia card. I take it you are trying the perforce version right? I don't suppose you could give me what error message you get so we could 'compare'. Mine is something about not being able to allocate memory. Cheers ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: WPI Driver Support (WAS: Re: mode 11g, but 6Mbps)
Federico Lorenzi wrote: > On 7/24/07, Tom Evans <[EMAIL PROTECTED]> wrote: >> On Tue, 2007-07-24 at 11:42 +0200, Pietro Cerutti wrote: >> > Federico Lorenzi wrote: >> > > On 7/24/07, Pietro Cerutti <[EMAIL PROTECTED]> wrote: >> > >> Hi List, >> > >> I have an Intel PRO/Wireless 3945ABG adapter using the wpi0 driver >> > >> connecting to an access point using the 802.11g mode. >> > >> # ifconfig wpi0 mode 11g >> > >> # ifconfig wpi0 >> > >> ... >> > >> media: IEEE 802.11 Wireless Ethernet autoselect mode 11g >> (OFDM/6Mbps) >> > >> ... >> > >> >> > >> Can anyone explain why I see OFDM/6Mbps instead of OFDM/54Mbps >> (or at >> > >> least 19Mbps if you mean the actual throughput?) >> > > It could depend on a few things, first off remember that it's a >> highly >> > > experimental driver at >> > > this stage, and don't mean to be stating the obvious, but are you >> > > actually close enough to >> > > the AP to get 54mbps? Windows says 54 / 11 no matter what speed it is >> > > running at. >> > >> > Hi Federico, >> > >> > Actually I'm 4 meters away from the AP. >> > I know that wpi is still in pre-alpha state ;-) >> > >> > Tnx >> > >> >> Heh, at least you have some connectivity - mine is still using none! >> >> [EMAIL PROTECTED]:0:0: class=0x028000 card=0x135c103c chip=0x42228086 >> rev=0x02 >> hdr=0x00 >> vendor = 'Intel Corporation' >> device = '3945ABG Intel 3945ABG Wireless LAN controller' >> class = network >> >> Driver either fails to initialise, or panic's my -CURRENT laptop :) >> >> I'd think its highly likely that performance issues are due to >> pre-release quality of the driver. > I have the same problem too, which forces me to use a 2 year old atheros > pcmcia card. I take it you are trying the perforce version right? I don't > suppose you could give me what error message you get so we could > 'compare'. Mine is something about not being able to allocate memory. > Heh for me I can now load the driver, and even associate with a non encrypted access point, but i cant pass traffic and it soom panics the machine (keep meaning to give Benjamin Close some debug output to see if he can help but I havent time at the moment.) I'm using the version from the latest tarball (http://people.freebsd.org/~benjsc/downloads/wpi/20070615-wpi-freebsd-7.0-current.tgz) It seems to actually be the latest version (I think the date he put on its wrong ;) Vince > Cheers > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: WPI Driver Support (WAS: Re: mode 11g, but 6Mbps)
On Tue, 2007-07-24 at 16:58 +0200, Federico Lorenzi wrote: > On 7/24/07, Tom Evans <[EMAIL PROTECTED]> wrote: > > On Tue, 2007-07-24 at 11:42 +0200, Pietro Cerutti wrote: > > > Federico Lorenzi wrote: > > > > On 7/24/07, Pietro Cerutti <[EMAIL PROTECTED]> wrote: > > > >> Hi List, > > > >> I have an Intel PRO/Wireless 3945ABG adapter using the wpi0 driver > > > >> connecting to an access point using the 802.11g mode. > > > >> # ifconfig wpi0 mode 11g > > > >> # ifconfig wpi0 > > > >> ... > > > >> media: IEEE 802.11 Wireless Ethernet autoselect mode 11g (OFDM/6Mbps) > > > >> ... > > > >> > > > >> Can anyone explain why I see OFDM/6Mbps instead of OFDM/54Mbps (or at > > > >> least 19Mbps if you mean the actual throughput?) > > > > It could depend on a few things, first off remember that it's a highly > > > > experimental driver at > > > > this stage, and don't mean to be stating the obvious, but are you > > > > actually close enough to > > > > the AP to get 54mbps? Windows says 54 / 11 no matter what speed it is > > > > running at. > > > > > > Hi Federico, > > > > > > Actually I'm 4 meters away from the AP. > > > I know that wpi is still in pre-alpha state ;-) > > > > > > Tnx > > > > > > > Heh, at least you have some connectivity - mine is still using none! > > > > [EMAIL PROTECTED]:0:0: class=0x028000 card=0x135c103c chip=0x42228086 > > rev=0x02 > > hdr=0x00 > > vendor = 'Intel Corporation' > > device = '3945ABG Intel 3945ABG Wireless LAN controller' > > class = network > > > > Driver either fails to initialise, or panic's my -CURRENT laptop :) > > > > I'd think its highly likely that performance issues are due to > > pre-release quality of the driver. > I have the same problem too, which forces me to use a 2 year old atheros > pcmcia card. I take it you are trying the perforce version right? I don't > suppose you could give me what error message you get so we could > 'compare'. Mine is something about not being able to allocate memory. > > Cheers Yes, I knocked up a quick ruby script to scarily rip the files out of perforce web interface. Mine also fails with a similar message; I forget the exact details, and 5 time out of 10 it also panic's my laptop, so I won't try it again till after work ;) Tom signature.asc Description: This is a digitally signed message part
Re: WPI Driver Support (WAS: Re: mode 11g, but 6Mbps)
Here is the current output of loading the very latest wpi code from p4 (loaded with sysctl debug.bootverbose=1) : pci8: driver added found-> vendor=0x8086, dev=0x4222, revid=0x02 bus=8, slot=0, func=0 class=02-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=16 powerspec 2 supports D0 D3 current D0 MSI supports 1 message, 64 bit pci8:0:0: reprobing on driver added wpi0: mem 0xe800-0xe8000fff irq 16 at device 0.0 on pci8 wpi0: Driver Revision 20070715-nwifi wpi0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xe800 Resetting the card - clearing any uploaded firmware wpi0: Hardware Revision (0x1) Size: 44 - alignement 4096 Memory, allocated & Aligned! Size: 245760 - alignement 4096 Memory, allocated & Aligned! Size: 16384 - alignement 16384 bus_dmamem_alloc failed to align memory properly. Memory Unaligned, trying again: 0 bus_dmamem_alloc failed to align memory properly. Memory Unaligned, trying again: 1 bus_dmamem_alloc failed to align memory properly. Memory Unaligned, trying again: 2 Memory, allocated & Aligned! Size: 93184 - alignement 16384 bus_dmamem_alloc failed to align memory properly. Memory Unaligned, trying again: 0 bus_dmamem_alloc failed to align memory properly. Memory Unaligned, trying again: 1 bus_dmamem_alloc failed to align memory properly. Memory Unaligned, trying again: 2 bus_dmamem_alloc failed to align memory properly. Memory Unaligned, trying again: 3 bus_dmamem_alloc failed to align memory properly. Memory Unaligned, trying again: 4 Memory, allocated & Aligned! Size: 16384 - alignement 16384 Memory, allocated & Aligned! Size: 93184 - alignement 16384 Memory, allocated & Aligned! Size: 16384 - alignement 16384 bus_dmamem_alloc failed to align memory properly. Memory Unaligned, trying again: 0 bus_dmamem_alloc failed to align memory properly. Memory Unaligned, trying again: 1 Memory, allocated & Aligned! Size: 93184 - alignement 16384 bus_dmamem_alloc failed to align memory properly. Memory Unaligned, trying again: 0 bus_dmamem_alloc failed to align memory properly. Memory Unaligned, trying again: 1 bus_dmamem_alloc failed to align memory properly. Memory Unaligned, trying again: 2 bus_dmamem_alloc failed to align memory properly. Memory Unaligned, trying again: 3 wpi0: could not allocate shared page DMA memory wpi0: could not allocate tx command DMA memory wpi0: could not allocate Tx ring 2 device_attach: wpi0 attach returned 6 pci24: driver added pci32: driver added On the plus side, it didn't panic.. If anyone wants my script for fetching from perforce, I've attached it. It requires rubygems, and hpricot from rubygems, but apart from that its all in base ruby iirc. signature.asc Description: This is a digitally signed message part
