Talk:HCL/Network Adapters (Wireless)

From openSUSE

Just want to state that D-Link DWL G122 USB WLAN adapter is working perfectly with the shipped driver. There is no need to use ndiswrapper any longer. Cheers Bernd. Yes, all features can be administrated with Yast. Regards Jochen

Apple AirPort Cards

I'm wondering what is up with the Apple Airport cards? --Keichwa 00:58, 13 Dec 2005 (MST)

The airport cards do have a device driver in the kernel, but I'm not sure how they work on SuSE since I don't use a mac. AFAIK, the airport extreme does not have a driver.

I guess more info will come out when someone tries it, but thats about all the info I have, sorry --CuCullin 07:36, 13 Dec 2005 (MST)

Natively supported WLAN-cards

Since SuSE 10.1 will not have any non-gpl-modules I think there is urgent need to set up a site or section on this page that lines out which chipsets are usable with 10.1 out of the box. Having to compile, or having to search on the internet before being able to use WLAN is certainly not soemthing that would speak for SuSE and should thus be avoided.

I think that the only way to do so, apart from either accepting non-gpl drivers, is having a tool that gets and installs them from whereever they are or, at minimum, and I guess that is the only feasable option, provide a site that the user can get detailed information from, which chipsets provide GPLed drivers.

That site should not only rely on user's input but be set up by SuSE-employees in order to provide reliable and complete information. No matter what the arguments are concerning non-gpl-drivers, the user expects to have WLAN working by installing a driver from a CD and no more steps. No matter if it is SuSE's fault or not, the user will blame SuSE and as there are more and more notebooks, there will be more and more users with this issue.

WG111T

I just installed a WG111T under Suse 10.1 with ndiswrapper. Needed to install two drivers/.inf files, but after that all worked fine, including WPA.

Planet WL-8314 wireless PCI

For some time I tried to install a Planet WL-8314 card. Difficult because of the "unknown vendor" report from lspci. ndiswrapper did not work because of the lack of .inf file on the manufacturer site and CD (only an installable utility).

Last week installation succeeded under suse 10.1 with ndiswrapper. I used the mrv8335 driver from Marvell (the name being there in the verbose description). There are some error messages and warnings during installation, but I use WPA without problems.

IPW2100 KNetworkManager failure in openSUSE 10.2

I have not yet managed to get a network connection under openSUSE 10.2 (kernel-2.6.18.8-0.3-default) with the IPW2100 WLAN adapter in my Toshiba Portege R100 laptop using KNetworkManager. On the other hand, ifup works fine. The ipw-firmware-7-31 RPM is installed, but KNetworkManager hangs at "Activating Wireless Network Connection -- 28% -- Activation stage: Configuring device.", followed by "Connection failure" after about 30 seconds. KNetworkManager occasionally shows a list of access points, but very unreliably; often the list is empty when there should be several nodes with excellent signal. The dmesg log shows

 ieee80211_crypt: registered algorithm 'TKIP'
 ieee80211_crypt: registered algorithm 'CCMP'
 ipw2100: Fatal interrupt. Scheduling firmware restart.
 ipw2100: Fatal interrupt. Scheduling firmware restart.
 ipw2100: exit - failed to send CARD_DISABLE command
 NET: Registered protocol family 17
 ipw2100: Fatal interrupt. Scheduling firmware restart.
 ipw2100: Fatal interrupt. Scheduling firmware restart.
 ipw2100: eth0: firmware fatal error
 ipw2100: exit - failed to send CARD_DISABLE command
 ipw2100: eth0: Failed to start the card.
 ieee80211_crypt: registered algorithm 'WEP'

Markus Kuhn 20:33, 27 May 2007 (UTC)

D-Link DWL520+ PCI adapter installation 10.3

Installed on openSUSE 10.3 (from CD) using the following procedure: Install openSUSE. Download Firmware from Sourceforge ACX100 driver project. Installed acx-kmp-default-20070101_2.6.22.5_31-6.i586.rpm from my ISP's mirror (Internode) using YaST. Set network settings to connect to my Access Point - DWL520+ was working and I could see it attached to my AP, but couldn't ping. After lots of reading, found that my on-board NIC had auto-installed and had the same subnet mask as the DWL520+ wireless setup, causing conflict. Article on MadWifi describes this here Set onboard NIC to startup on cable plug-in, problem solved.

Took ages, but was all very simple in the end. Hope this helps someone.