WirelessChipsets

Differences between revisions 8 and 9
Revision 8 as of 2006-03-29 10:32:46
Size: 2512
Editor: p548F65DC
Comment: RaLink RT2500
Revision 9 as of 2006-03-29 10:42:37
Size: 2645
Editor: p548F65DC
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
|| '''Chipset Vendor''' || '''Chipset name''' (as from lspci, maybe shortened) |||| '''Status on Ubuntu 5.10 "breezy badger"''' |||||||| '''Status on Ubuntu 6.06 "dapper drake"''' || date || || '''Chipset Vendor''' || '''Chipset name''' (as from lspci, maybe shortened) |||| '''Status on Ubuntu 5.10 "breezy badger"''' |||||||| '''Status on Ubuntu 6.06 "dapper drake"''' || '''date''' ||
Line 7: Line 7:
|| Broadcom || BCM4306 || ndiswrapper; no monitoring, no link quality information || wlan* || || || || || 2006-03-29 ||
Line 13: Line 14:
|| '''Chipset Vendor''' || '''Chipset name''' (as from lsusb<sup>[#remark4 4]</sup>) |||| '''Status on Ubuntu 5.10 "breezy badger"''' |||||||| '''Status on Ubuntu 6.06 "dapper drake"''' || date || || '''Chipset Vendor''' || '''Chipset name''' (as from lsusb<sup>[#remark4 4]</sup>) |||| '''Status on Ubuntu 5.10 "breezy badger"''' |||||||| '''Status on Ubuntu 6.06 "dapper drake"''' || '''date''' ||

On this page, we want to collect information about the status of specific WLAN chipsets, NOT the devices. Linux drivers are nearly always generic drivers, so different devices with the same hardware are driven by the same driver; normally the system doesn't even know about the vendor of the device. In addition WLAN devices tend to change the real hardware in them very often any without any information to the users.

PCI, PC-Card/32 Bit PCMCIA

Chipset Vendor

Chipset name (as from lspci, maybe shortened)

Status on Ubuntu 5.10 "breezy badger"

Status on Ubuntu 6.06 "dapper drake"

date

problems on basic WLAN functionality<sup>[#remark1 1]</sup>

interface name

problems on basic WLAN functionality<sup>[#remark1 1]</sup>

WPA<sup>[#remark2 2]</sup>

ways to get network-manager to fail<sup>[#remark3 3]</sup>

interface name

Broadcom

BCM4306

ndiswrapper; no monitoring, no link quality information

wlan*

2006-03-29

intel

ipw2100

none

eth*

none

Ad-Hoc + WEP

eth*

2006-03-29

intel

ipw2200

none

eth*

none

eth*

2006-03-29

RaLink

RT2500

very unstable, no mode=Master

ra*

no mode=Master

ra*

2006-03-29

TI

ACX 100

none

wlan*

none

wlan*

2006-03-29

USB

Chipset Vendor

Chipset name (as from lsusb<sup>[#remark4 4]</sup>)

Status on Ubuntu 5.10 "breezy badger"

Status on Ubuntu 6.06 "dapper drake"

date

problems on basic WLAN functionality<sup>[#remark1 1]</sup>

interface name

problems on basic WLAN functionality<sup>[#remark1 1]</sup>

WPA<sup>[#remark2 2]</sup>

ways to get network-manager to fail<sup>[#remark3 3]</sup>

interface name

1Anchor(remark1)) just write "none", if you do not need to install any driver or change configuration files (maybe except /etc/network/interfaces manually.

2Anchor(remark2)) needs wpasupplicant. This is NOT supported on breezy (but might work, as an unconfigured version of wpasupplicant exists in universe).

3Anchor(remark3)) just write "none", as long, as you can't get network-manager to fail on it.

4Anchor(remark4)) it is VERY important to add the IDs here. So a valid entry looks like "ID 046d:c308 Logitech, Inc. Internet Navigator Keyboard" (that example is not a WLAN device Wink ;) or only "ID 058f:6362" if lsusb doesn't have strings.

WirelessChipsets (last edited 2008-08-06 16:34:56 by localhost)