-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, May 25, 2006 at 12:06:32PM -0400, Max H. wrote: > Rodrigo Barbosa wrote: > > > >Can you give us the data on your chipset, for reference ? > > Sure...output is at the bottom. > > lspci -vv outputs: > > 02:02.0 Ethernet controller: Atheros Communications, Inc. AR5211 > 802.11ab NIC (rev 01) > Subsystem: Unknown device 17ab:8310 > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- > ParErr- Stepping- SERR+ FastB2B+ > Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium > >TAbort- <TAbort- <MAbort- >SERR- <PERR- > Latency: 168 (2500ns min, 7000ns max), Cache Line Size 08 > Interrupt: pin A routed to IRQ 11 > Region 0: Memory at d0200000 (32-bit, non-prefetchable) [size=64K] > Capabilities: [44] Power Management version 2 > Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA > PME(D0-,D1-,D2-,D3hot-,D3cold-) > Status: D0 PME-Enable- DSel=0 DScale=2 PME- > > lspci -n outputs: > > 02:02.0 Class 0200: 168c:0012 (rev 01) Okey, that is a 802.11ab (11Mbps) chip. My experiences were only with 802.11g (54Mbps) chips. In any case, it is VERY odd yours identifies itself as a Class 0200 device. I suppose it should a 0280 (Network controller). In any case, tkx for the info. - -- Rodrigo Barbosa <rodrigob at suespammers.org> "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFEdksDpdyWzQ5b5ckRAmGGAJ4hU3VObtoKBUNti6nCWADC24z3KgCdG8C+ 2kZdrgZicNxvjH5sIeAm4D0= =jjyG -----END PGP SIGNATURE-----