If you did not migrate your account yet, visit https://idp-portal-info.suse.com/
|ラップトップ - デスクトップ - サーバー - 仮想マシン|
|ビデオカード - サウンドカード - ネットワークアダプタ(有線) - ネットワークアダプタ(無線) - Bluetoothアダプタ - プリンター - スキャナー - TVカード - デジタルカメラ - ウェブカメラ - UPS - フロッピードライブ|
Please note that if a piece of hardware was working on a previous release than the current one, there is a pretty good chance that it will work on the most recent release. However, there is no guarantee that the current release did not somehow break the driver or configuration for that piece of hardware (for example refer to Bug 168618). Please check that the hardware continues to work as expected for the most recent release before updating the for the most recent release in the following tables.
|Chipset||Type||Bus||Driver||SL 9.3||SL 10.0||SL 10.1||SL 10.2||SL 10.3||SLES/NLD 9||Comments|
|Atheros AR2413A||802.11bg||PCI||madwifi||Works well with madwifi on 10.3 x86_64.|
|Atheros 5005G||802.11bg||PCI/Cardbus||madwifi||Needs nongpl kernel package. SL 10.1: Here is a workaround using ndiswrapper or madwifi.|
|Atheros 5005G||802.11a||PCI/Cardbus||madwifi||Needs nongpl kernel package. SL 10.1: Here is a workaround using ndiswrapper or madwifi.|
|Atheros 5005GS||802.11abg||MiniPCI||madwifi||Install it using the ndiswrapper (not recommended) or the madwifi driver. On some machines, when supended to disk, it won't connect anymore until next reboot. See also bug 22259.|
|Atheros 5006EG||802.11bg||PCI/Cardbus||madwifi||Needs nongpl kernel package. SL 10.2-10.3: Here is a workaround using ndiswrapper or madwifi.|
|Atheros 5210||802.11a||PCI/Cardbus||madwifi||(SLES/NLD 9 - i386 only) needs nongpl kernel package. SL 10.1: Here is a workaround using ndiswrapper or madwifi.|
|Atheros 5211||802.11ab||PCI/Cardbus||madwifi||(SLES/NLD 9 - i386 only) needs nongpl kernel package. SL 10.1: Here is a workaround using ndiswrapper or madwifi.|
|Atheros 5212||802.11abg||PCI/Cardbus||madwifi||(SLES/NLD 9 - i386 only) needs nongpl kernel package. For SL 10.1 and 10.2: Here is a workaround using ndiswrapper or madwifi.|
|Broadcom||bcm43xx|| 10.3 See note for 10.2.
10.1 Works with ndiswrapper(64bit drivers also work with ndiswrapper).
|INPROCOMM IPN 2220||802.11abg||mini-PCI||neti2220x64/ndiswrapper||
Works without problems on openSuSE 10.2 x64 and 10.3 x64 using the win2k_x64 driver and ndiswrapper. WEP works. WPA not tested.
|Intel PRO/Wireless 2100||802.11b||PCI||ipw2100||
For suse 10.2 to work, the ipw-firmware package from the Non-OSS add-on CD (or non-oss repo) is required.
|Intel PRO/Wireless 2200BG||802.11bg||PCI||ipw2200||
|Intel PRO/Wireless 2915ABG||802.11abg||PCI||ipw2200||On SuSE 10.1 need to use the Extras CD disk 6. May need traditional ifup since sometimes card misses available networks. Other than that standard network manager seems normal.|
|Intel PRO/Wireless 3945ABG||802.11abg||PCI-e||ipw3945||
|Intel Wireless WiFi Link 4965AGN||802.11a/b/g/n||PCI-e||iwlwifi (iwl4965)|| Supported using the |
|Marvell 8335||802.11b/g||PCI||-||Could not get this to work with ndiswrapper.|
|Prism2/2.5/3||802.11b||PCI/PCMCIA||hostap||chipset is supported by three drivers hostap, linux-wlan-ng, and orinoco (SLES/NLD 9 uses linux-wlan-ng driver by default)|
|PrismGT/ Duette||802.11bg||PCI||prism54||In 10.1 you need to download firmware, see PCI devices below. In 9.3, 10.0 you could obtain it via YAST.|
|Ralink RT2400||802.11b||PCI/Cardbus||rt2400||works fine out of the box no problems yet encountered.|
|Ralink RT2500||802.11g||PCI/Cardbus||rt2500||current stable driver does not work with SMP kernel, new driver with SMP support currently being developed. Try this HowTo!|
|Ralink RT2570||802.11g||USB||rt2570||(Random user: I couldn't make this one work by the default suse installation, v10.0 or 10.1; but this project (1) (2) is a possible solution.)|
|Realtek 8187||802.11a/b/g||USB||not sure|| Requires ndiswrapper (adhoc and managed) or the official drivers found here (adhoc or Infrastructure). Official drivers work with versions shown to the left, ndiswrapper needs to be tested in other versions. Drivers come with a "readme" on how to install. Must be done in root.
|Texas Instruments ACX100||802.11b+||PCI/Cardbus||acx||proprietary protocol (22 Mbps)|
|Texas Instruments ACX111||802.11g||PCI/Cardbus||acx|| very buggy driver (currently alpha), packet loss, connection loss, Linux-unfriendly vendor,
requires acx_111 firmware
|ZyDAS ZD1211||802.11g||USB||zd1211|| An opensource driver (V2.0.0) for kernel 2.4/2.6 can be found at the Zydas-Homepage. In addition, there's an OpenSource fork actively maintained, available at .
The zd1211rw driver is included in the kernel. It's only needed to copy the firmware to its place, you can find it here: http://zd1211.ath.cx/wiki/DriverRewrite
Chipsets missing or listed here as not supported may work using ndiswrapper.
Atheros chipsets can be used via the Atheros madwifi driver.
help with ndiswrapper here 
You can find an extensive list of wireless LAN cards including the chipset information here .
|Supports Network Install||Supported in installed system||9.3||10.0||10.1||10.2||10.3||Comments|
|ARtem||Onair ComCard 11||orinoco_cs|
|Belkin||F5D7010||RT2500||only non-SMP kernel (see information above about RT2500 chipset)|
|Conceptronics||54 Mbit/s WLAN PCMCIA||RT2500||only non-SMP kernel (see information above about RT2500 chipset)|
|E-Tech||WGPC03||RT2500||only non-SMP kernel (see information above about RT2500 chipset)|
|Netgear||MA401||Prism II / hostap_cs with orinoco_cs||10.2 - yast recognizes and configures.. I needed to add "exclude irq 3" in /etc/pcmcia/config.opts to avoid the card from using IRQ 3 on reboot which conflicted... this could be unique to my HW..|
|Netgear||WG511 v2.0|| Prism Duett
| after online-update,
ndiswrapper + Win2000 driver
| Prism: Doesn't work on SuSe 10 rc1 works with workaround: add "PREFER_WPA_SUPPLICANT='no' to the ifcfg-wlan, |
Marvell: Works sometimes not on SuSE 9.3 (Reason not known, reconnect helps mostly)
|Netgear||WG511 v3.0||only by ndiswrapper|
|Netgear||WG511T||AR5212|| on 10.1,
|10.1, 10.2 & 10.3: Enable the Madwifi repository (http://madwifi.org/suse/) and install through Yast -> Software -> Software Management Install notes|
|Sitecom||WL-011 v1||atmel||download the firmware from the SuSe 10.0 Evaluation repository or use yast with extra repository|
|Sitecom||WL-120 v1||TI ACX111||Requires acx_111 & acx_111c16 firmware, rename files to lower case but need upper case .BIN|
|SMC||SMCWCBT-G||Atheros 5212 /
|Tested on 32 and 64 bits, supports WEP and WPA 1,2|
|3Com||3CRWE154A72||AR5212 (AR5002X??)|| downloaded drivers from http://snapshots.madwifi.org and followed instructions from http://linux.wordpress.com/2006/05/21/suse-101-and-atheros-based-wifi-cards/
important note: the LED's are not supported
|Supports Network Install||Supported in installed system||9.3||10.0||10.1||10.2||10.3||Comments|
|Addon||GWU190||Realtek 8187||Same adaptor as the netger wg111V2 Will work with x86_64 SUSE, Need to download the source code from Realtek web site. with 10.2 you will get a lot of symbol warnings, but works,and can be managed from Yast or network manager.|
|A-Link||WL54USB||Auto-detected during x86_32 openSUSE 10.3 install. No need to do anything. I provided PSK for my WPA encrypted network during install and it just simply works!|
|Asus||M2N VM-DH (usb on mainboard)||Realtek 8187||
1) Download the source code from http://rtl-wifi.sourceforge.net/wiki/Mac80211 and follow readme (make, make install), 2) modprobe rtl8187 as root for loading the module, 3) call knetworkmanager, works with WPA on x86_64 OpenSuse 10.3
|AVM||Fritz!WLAN Stick USB||How-To: SDB:AVM Fritz!WLAN Stick USB|
| Tested on 32 bits, on 64 bits machine (AX2 6000) driver gives a compilation error: (...) rtmp_main.c:1: error: -mpreferred-stack-boundary=2 is not between 4 and 12|
make: *** [rtmp_main.o] Error 1
Supports WEP, WPA 1,2
|D-Link||DWL-G122 ver B1||RT 2500||(does not work on SMP kernels!) hardware version B1 (not C1)|
|D-Link||DWL-G122 ver C1||RT 73|
|D-Link||DWL-122||?/prism2_usb||Seems to depend on revision: ID 2001:3700 D-Link Corp. [hex] DWL-122 802.11b (works). Instr.: Install wlan-kmp-default ; modprobe prism2_usb .. openSUSE 10.2 autodetects the WLAN Stick now .. Use YaST2 Lan to configure. (Merge with above?)|
|D-Link||DWL-G132||Atheros||H/W v:A3 F/W v:1.21 ID=2001:3a03 802.11g Ndiswrapper is straightforward: rpm for 10.1&2, source for 10.0. Install notes|
|Edimax||7317U||Zydas zd1211||supports USB2.0 and works immediately after compile with make|
|LinkSyS||WUSB54G||In 9.3 only with the Serial Monkey Driver. Had to edit the config-file of the wireless-card; The USB-Adapter has to be configured in YAST as ethernet-device. In addition to this file You need a file named ifcfg-rausb0 (text-file)in the directory /etc/sysconfig/network.|
|Longshine||8131G2||Zydas zd1211||supports USB2.0 and works immediately after compile with make|
|Microsoft||MN-510||in 10.1 final it is seen when you run tail -f /var/log/messages but yast will not see it|
|MSI||US54SE||Zydas zd1211||Tested on 32 and 64 bits|
|Netgear||WG121||Prism GT||Will NOT work with x86_64 SUSE, 32 bit drivers do not work with 64 bit OS, no plans by Netgear to ever provide 64 bit drivers, Windows or Linux.|
|Netgear||MA111 v1!||You need to use the Windows XP driver with Ndiswrapper. Tested with 32-bit.|
|Netgear||WG111V2||Realtek 8187|| Will work with x86_64 SUSE, Need to download the source code from Realtek web site. with 10.2 you will get a lot of symbol warnings, but works,and can be managed from Yast or network manager.|
>> Device also works under openSUSE 10.3 beta 2; just with ndiswrapper and without the source from Realtek.<<
|Ovislink||W108USB||ndiswrapper||Only available for 32 bits systems (no windows driver for 64 bits), supports WEP, WPA 1,2|
|Sweex||LW058||ndiswrapper / Marvell 88W8335 - Libertas 802.11b/g Wireless? (must check)|| lsusb -v command partial output:
idVendor 0x1286 idProduct 0x1fab bcdDevice 0.01 iManufacturer 1 MARVELL iProduct 2 MARVELL Wireless Device V18.104.22.168
I.e. adapter usbid: 1286:1fab. Additionally check with this usbid on http://ndiswrapper.sourceforge.net. Then Wiki->List. Tested on 32 bits, supports WEP, WPA 1,2 not tested. Windoze drivers downloaded from  may be corrupted. Please use supplied CD. As a graphical ndiswrapper interface you may use ndisgtk
|X-Micro||XWL-11GUZX||zd1211|| 10.2 => have a look at the help for zd1211-Chipset
10.3 works out of the box
|Supports Network Install||Supported in installed system||SUSE Linux
|Airlink||AWLH3025||ACX111/acx_pci||10.0 OSS||x86||First you need to install firmware using YOU and selecting installacx111firmware.sh, then you can configure directly with YaST|
|Allied Telesyn||AT-WCP200G||ACX111/acx_pci||See Comments||10.1||x86||Requires NDISWRAPPER. No native Linux support.|
|Allnet||AL0271||Atheros/ath_pci||Only in 10.0||10.0, 10.1||x86, x86_64||WEP supported. For 10.1 the madwifi drivers are needed. If the installation of the madwifi-kmp-*.rpm package fails, get the src-package and rebuild it: rpmbuild --rebuild --target=[yourTarget] madwifi-*.src.rpm. The new packages are located at the adequate directory in /usr/src/packages/RPMS/|
|Conceptronics||54 Mbit/s WLAN PCI||RT2500||9.3 + 10.0||x86, x86_64, non-SMP only|| only non-SMP kernel (see information above about RT2500 chipset)|
Some C54RI cards may have problems with rt2500pci module used by default in openSUSE 10.3. Installing serialmonkey drivers (module rt2500) can solve this issue. See chipset details above.
|D-Link||DWL-520+||ACX100/YAST2||10.0 RC1||Card is recognised, yet unable to start WiFi, still on the lookout (See discussion article)|
|D-Link||DWL-510||r8180||10.0 32/64-bit, 10.1 32-bit||x86_64||kernel driver included as standard, does not show in Yast but is picked up on a fresh install. Drivers provided by vendor are for 32-bit only. ndiswrapper can not load 32-bit drivers on 64-bit OS.|
|D-Link||DWL-G520 version b||Atheros/ath_pci||10.0 OSS, 10.2, 10.3||x86, x86_64||Version b cards that use the Atheros chips work out of the box in 10.0. Card recognized, just needed to configure the network interface with Yast and it worked instantly. For 10.2 you will need to install the madwifi drivers (http://madwifi.org/suse/10.2/).|
|D-Link||DWL-G520 version C||Atheros/ath_pci||10.1 OSS||x86||Version C cards are not recognised. Nidswrapper locks up.|
|Intersil||ISL3890||PrismGT/Duette||10.1 OSS||x86|| You need to download the firmware, version 22.214.171.124, for the ISL3890 from the following URL http://prism54.org/fullmac.html
and saved the firmware file as isl3890 (no Capitals) in the /lib/firmware/ directory. I used in KDE KMenu/System/FileManager/ FileManager-SuperUserMode to download/save the firmware.
|Netgear||WG311 T/G/R||AR52xx/madwifi||10.0 OSS, 10.2||i386|| After installing the NON-GPL kernel, card works out of the box.
Yast2 uses module ath_pci. Works with SuSe 10.2 after installing madwifi (tested with madwifi-0.9.2.1-0.1 and WG311-T card).
|Linksys Wireless-N PCI||WMP300N||Broadcom 4329 1bcmwl5||10.2||x86, x86_64||1Use ndiswrapper and the drivers from the CD.|
|SMC||SMCWPCIT-G|| AR5212 /
|10.2||x86, x86_64||Card support WEP and WPA 1,2|
|Sweex||LW052||Atheros AR2413A/ madwifi ath_pci||10.3||x86_64||Works well with madwifi. Repository can be added to YaSt |
|TP-Link||TL-WN650G||Atheros/ath_pci||Only in 10.0||10.0, 10.1, 10.2, 10.3||x86, x86_64||WEP and WPA supported. For 10.1, 10.2 and 10.3 the madwifi drivers are needed. If the installation of the madwifi-kmp-*.rpm package fails, get the src-package and rebuild it: rpmbuild --rebuild --target=[yourTarget] madwifi-*.src.rpm. The new packages are located at the adequate directory in /usr/src/packages/RPMS/|
How do I know which chipset I have?
The chipset is what determines which driver you need, not the manufacturer of the card. Here are a number of ways to find out. All the commands should be run as root.
Otherwise use this command if you have a pcmcia card or an onboard card:
Or this if you have a usb card:
This won't output very detailed information, but it'll give you a unique hardware ID, for example 046d:c01b. Search for it with Google or another internet search engine to find out which chipset is on the device.
If there's no native Linux driver for your card, maybe you can use a Windows driver with Ndiswrapper