Cannot see my WLAN cards in YAST2
Dear list; I've installed 10.1 RC1 of OpenSuSE and just wanted to configure my WLAN network cards, one manufactured by D-Link, one by Netgear. But both of them don't appear in the network card configuration applet of YAST2. I'm running also SuSE 9.3 on a different partition, here I see both of the cards and also can communicate over them. The exact name of the D-Link card appearing in SuSE 9.3 is: D-Link AR5212 802.11 abg NIC Netgear is named in 9.3 as follow: Netgear WG311T Wireless PCI Adapter For D-Link, Ive already tried to copy the configuration file named ifcfg-wlan-id-00:0d:88:e5:fc:4e from the folder /etc/sysconfig/network of my 9.3 installation to the 10.1 RC1 installation. The success is, that the card appeares now and can be configured as known, but it is not working anyhow as I could see in the network interfaces of the information center. Under the following link you'll find a screenshot I've made, if you don't believe me! ;) http://files.streife.com/nw.jpg Please, do you have any suggestions what's running wrong on 10.1? Has anyone discovered similar problems and possibly know how to handle this? Thanks a lot! Thomas
On Sunday 23 April 2006 20:13, Thomas Astleitner wrote:
I've installed 10.1 RC1 of OpenSuSE and just wanted to configure my WLAN network cards, one manufactured by D-Link, one by Netgear. But both of them don't appear in the network card configuration applet of YAST2.
Not sure if it's the YaST2 module that you refer to as applet or not - or do you refer to the NetworkManager applet running in systray (which is not yast-related directly)? However the important thing is not the manufacturer of the cards, but the chipset on them (check that with # lspci or # lsusb). But I have the problem too. My Linksys card (Broadcom chipset) using ndiswrapper for driver does not appear in the YaST nic module. This is a problem as NetworkManager doesn't work very well for me either. I've been hesitant to reporting this as a bug because I'm using ndiswrapper - though my wlan nic works fine with yast2 on 10.0. But since other people seems to be having the same problem maybe.. I haven't tested this with rc2 though - since I chose to install that on my desktop this time around. cb400f
Am Sonntag, 23. April 2006 20:35 schrieb Martin Schlander:
Not sure if it's the YaST2 module that you refer to as applet or not - or do you refer to the NetworkManager applet running in systray (which is not yast-related directly)?
As you can see on the screenshot, i refer to the network card manager in the YaST system (I cannot give you the exact english name because I'm running a german system). But please see by yourself: http://files.streife.com/nw.jpg So do you agree with me that this may be a YaST problem? Thomas
On Sunday 23 April 2006 22:35, Thomas Astleitner wrote:
So do you agree with me that this may be a YaST problem?
Could be. Sorry about not reading your first mail thouroghly enough ;) Your problem is not the same as mine then, but you've given me an idea. My bcm4306 pcmcia wireless using ndiswrapper, appears in ifconfig and is detected by networkmanager. But is nowhere to be found in YaST2 NIC-module. I would like to use ifup, as NetworkManager will not connect using wpa-encryption. http://suse.linuxin.dk/nw.png Should I report this as a bug? Or is this a well deserved penalty for owning a crappy Broadcom card that only "works" with ndiswrapper? In 10.0 using the same card + ndiswrapper/windowsdriver it works well with the YaST NIC-module (except for the occassional freeze - but that is definitely a ndiswrapper issue) cb400f
Martin Schlander wrote:
would like to use ifup, as NetworkManager will not connect using wpa-encryption.
I have one Linksys WPC54G, but my network is WEP, so I can't say anything about WPA, but I can tell you that if you want to use your card with ifup, you can manually add it on YaST, and associate with ndiswrapper module, because YaST can't see it automatically. -- % Mauricio Teixeira (netmask) % mteixeira{a}webset{d}net <> Maceio/AL/BR % http://mteixeira.webset.net <> http://pmping.sf.net
On Monday 24 April 2006 14:28, Mauricio Teixeira (netmask) wrote:
I have one Linksys WPC54G, but my network is WEP, so I can't say anything about WPA, but I can tell you that if you want to use your card with ifup, you can manually add it on YaST, and associate with ndiswrapper module, because YaST can't see it automatically.
Very nice. That wasn't hard at all. After adding my pcmcia wlan manually to YaST I can connect with wpa using ifup-method without any problems. Once you get around those rough edges 10.1 is starting to look pretty good ;) Thanks for the help, one less thing to worry about. I still wonder if this is somehow a bug though - as I don't have to add my wlan nic to YaST manually in 10.0. cb400f
Martin Schlander wrote:
Thanks for the help, one less thing to worry about. I still wonder if this is somehow a bug though - as I don't have to add my wlan nic to YaST manually in
I'm not the right person to say that, but it does look like a regression. If you could do it in 10.1, you could be doing in 10.1, *unless* the developers decided to drop automatic detection of ndiswrapper devices in favor of using NetworkManager. -- % Mauricio Teixeira (netmask) % mteixeira{a}webset{d}net <> Maceio/AL/BR % http://mteixeira.webset.net <> http://pmping.sf.net
Am Sonntag, 23. April 2006 23:31 schrieb Martin Schlander:
Should I report this as a bug? Or is this a well deserved penalty for owning a crappy Broadcom card that only "works" with ndiswrapper?
From my opinion, this seems to be a (not quite small) bug, when network cards disappear in a higher version of an operating system than in previous. So would you be so kind to post a bug report? I'd appreciate if you would keep me up to date what the programmers say about that or if at less you can send me a link to the bug thread once you have posted. To chipsets: I don't think that those network cards are very exclusive. Exactly for this reason I bought me cards from known manufactures as Netgear and D-Link. But for your bug report you can use the informations I gave you in my first eMail. If you have further questions for your report, please feel free to involve. Thanks a very lot! Thomas
To chipsets: I don't think that those network cards are very exclusive. Exactly for this reason I bought me cards from known manufactures as Netgear and D-Link. But for your bug report you can use the informations I gave you in my first eMail. Yes, but without chipset information nobody knows which driver is able to get the card working.. manufacturers change chipsets during product
Thomas Astleitner wrote: lifetime without changing the product name (sometimes just the revision) :) Philipp
On Monday 24 April 2006 19:03, Thomas Astleitner wrote:
So would you be so kind to post a bug report?
I'd appreciate if you would keep me up to date what the programmers say about that or if at less you can send me a link to the bug thread once you have posted.
To chipsets: I don't think that those network cards are very exclusive. Exactly for this reason I bought me cards from known manufactures as Netgear and D-Link. But for your bug report you can use the informations I gave you in my first eMail.
If you have further questions for your report, please feel free to involve.
I've reported my problem. If you believe that our problems are related you can add your information as a comment - I'm not sure this is the case however. https://bugzilla.novell.com/show_bug.cgi?id=168967 cb400f
Martin Schlander wrote:
But I have the problem too. My Linksys card (Broadcom chipset) using ndiswrapper for driver does not appear in the YaST nic module. This is a
I also have a Linksys (WPC54G) and it doesn't show up in YaST, but if you insert the card, then "modprobe ndiswrapper" (given you've already installed the Windows drivers in it), KNetworkManager sees the card just fine, and then I can connect (on infra-structure mode only, no Ad-Hoc yet). BTW, I had to add "modprobe ndiswrapper" into /etc/init.d/after.local, so that the module gets automatically loaded on every boot. -- % Mauricio Teixeira (netmask) % mteixeira{a}webset{d}net <> Maceio/AL/BR % http://mteixeira.webset.net <> http://pmping.sf.net
On Mon, Apr 24, 2006 at 09:24:51AM -0300, Mauricio Teixeira (netmask) wrote:
Martin Schlander wrote:
But I have the problem too. My Linksys card (Broadcom chipset) using ndiswrapper for driver does not appear in the YaST nic module. This is a
I also have a Linksys (WPC54G) and it doesn't show up in YaST, but if you insert the card, then "modprobe ndiswrapper" (given you've already installed the Windows drivers in it), KNetworkManager sees the card just fine, and then I can connect (on infra-structure mode only, no Ad-Hoc yet).
BTW, I had to add "modprobe ndiswrapper" into /etc/init.d/after.local, so that the module gets automatically loaded on every boot.
Configure it with YAST , see /usr/share/doc/packages/ndiswrapper/README.SUSE Ciao, Marcus
On Mon, 2006-04-24 at 09:24 -0300, Mauricio Teixeira (netmask) wrote:
Martin Schlander wrote:
But I have the problem too. My Linksys card (Broadcom chipset) using ndiswrapper for driver does not appear in the YaST nic module. This is a
I also have a Linksys (WPC54G) and it doesn't show up in YaST, but if you insert the card, then "modprobe ndiswrapper" (given you've already installed the Windows drivers in it), KNetworkManager sees the card just fine, and then I can connect (on infra-structure mode only, no Ad-Hoc yet).
BTW, I had to add "modprobe ndiswrapper" into /etc/init.d/after.local, so that the module gets automatically loaded on every boot.
That is what "ndiswrapper -m" does for you. Usage: ndiswrapper OPTION Manage ndis drivers for ndiswrapper. -i inffile Install driver described by 'inffile' -d devid driver Use installed 'driver' for 'devid' -e driver Remove 'driver' -l List installed drivers -m Write configuration for modprobe -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
Kenneth Schneider wrote:
That is what "ndiswrapper -m" does for you.
It could be what it's *intended* to do, but it doesn't. It simply adds a line that associates wlan0 to ndiswrapper, making it easier to "ifup wlan0", but that doesn't make the module automatically loads, unless the interface is setup to come up "onboot" (which is not the case, since I'm using NetworkManager, not ifup). -- % Mauricio Teixeira (netmask) % mteixeira{a}webset{d}net <> Maceio/AL/BR % http://mteixeira.webset.net <> http://pmping.sf.net
participants (6)
-
Kenneth Schneider -
Marcus Meissner -
Martin Schlander -
Mauricio Teixeira (netmask) -
Philipp Wollermann -
Thomas Astleitner