I have just finished installing openSUSE 11.0 (x86_64) on my new desktop. I have a Netgear WG111v2 USB Wireless card (rtl8187). I have always had a bit of trouble with this on openSUSE. It would never connect if I chose to configure the network with the traditional “ifup”, but even when I use the Network Manager, it’s pretty hit and miss. Sometimes it connects, sometimes it won’t, and when it does, it doesn’t usually last very long. On every other Linux flavor, the following series of commands get’s me connected to my home network with this card:
This has always worked on every modern distro except openSUSE (Gentoo, Ubuntu, Debian, LFS LiveCD, Fedora, etc). Everything goes fine (iwconfig lists wlan0 as associated with the access point, the correct keys are listed), but the dhcpd command times out, and bingo, no internet. I have also tried various other wifi utilities, such as WFIF-Radar and Wicd. I read something on another thread that suggested installing compat-wireless-kmp from schmolle1980’s repo (I threw in rt*-cvs-kmp from there for good measure), but it made no difference. What is wrong here?
I’d hate to resort to ndiswrapper unless I absolutely have to (though I have the original driver CD if I need it), especially since this card is supported by the kernel and works fine on other distros.
zak89 wrote:
> I know, bad joke.
>
> I have just finished installing openSUSE 11.0 (x86_64) on my new
> desktop. I have a Netgear WG111v2 USB Wireless card (rtl8187). I have
> always had a bit of trouble with this on openSUSE. It would never
> connect if I chose to configure the network with the traditional “ifup”,
> but even when I use the Network Manager, it’s pretty hit and miss.
> Sometimes it connects, sometimes it won’t, and when it does, it doesn’t
> usually last very long.
I have not used the RTL8187, but I have an RTL8187B. It connects just fine with
KNM and stays connected as well as any other flavor of wireless. I use WPA
encryption, not WEP.
I can’t get it to connect at all right now. I get the following from dmesg after trying to connect via KNetworkManager:
wlan0: Initial auth_alg=1
wlan0: authenticate with AP 00:My:He:x:Ke:yx
wlan0: RX authentication from 00:My:He:x:Ke:yx (alg=1 transaction=2 status=13)
wlan0: AP denied authentication (auth_alg=1 code=13)
wlan0: authenticate with AP 00:My:He:x:Ke:yx
wlan0: RX authentication from 00:My:He:x:Ke:yx (alg=1 transaction=2 status=13)
wlan0: AP denied authentication (auth_alg=1 code=13)
wlan0: authenticate with AP 00:My:He:x:Ke:yx
wlan0: RX authentication from 00:My:He:x:Ke:yx (alg=1 transaction=2 status=13)
wlan0: AP denied authentication (auth_alg=1 code=13)
wlan0: authentication with AP 00:My:He:x:Ke:yx timed out
Interestingly, I do not get any dmesg output while trying to manually connect with iwconfig.
Okay, I just got it to connect with KNetworkManager. Here is from dmesg:
wlan0: Initial auth_alg=1
wlan0: authenticate with AP 00:My:He:x:Ke:yx
wlan0: Initial auth_alg=1
wlan0: authenticate with AP 00:My:He:x:Ke:yx
wlan0: RX authentication from 00:My:He:x:Ke:yx
(alg=1 transaction=2 status=13)
wlan0: AP denied authentication (auth_alg=1 code=13)
wlan0: authenticate with AP 00:18:01:81:a1:1a
wlan0: RX authentication from 00:My:He:x:Ke:yx
(alg=1 transaction=2 status=13)
wlan0: AP denied authentication (auth_alg=1 code=13)
wlan0: authenticate with AP 00:18:01:81:a1:1a
wlan0: RX authentication from 00:My:He:x:Ke:yx
(alg=1 transaction=2 status=13)
wlan0: AP denied authentication (auth_alg=1 code=13)
wlan0: authentication with AP 00:My:He:x:Ke:yx
timed out
wlan0: Initial auth_alg=1
wlan0: authenticate with AP 00:My:He:x:Ke:yx
wlan0: RX authentication from 00:18:01:81:a1:1a (alg=1 transaction=2 status=13)
wlan0: AP denied authentication (auth_alg=1 code=13)
wlan0: authenticate with AP 00:My:He:x:Ke:yx
wlan0: RX authentication from 00:My:He:x:Ke:yx
(alg=1 transaction=2 status=13)
wlan0: AP denied authentication (auth_alg=1 code=13)
wlan0: authenticate with AP 00:My:He:x:Ke:yx
wlan0: RX authentication from 00:My:He:x:Ke:yx
(alg=1 transaction=2 status=13)
wlan0: AP denied authentication (auth_alg=1 code=13)
wlan0: authentication with AP 00:My:He:x:Ke:yx
timed out
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:My:He:x:Ke:yx
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:My:He:x:Ke:yx
wlan0: RX authentication from 00:My:He:x:Ke:yx
(alg=0 transaction=2 status=0)
wlan0: authenticated
wlan0: associate with AP 00:My:He:x:Ke:yx
wlan0: authentication frame received from 00:My:He:x:Ke:yx
, but not in authenticate state - ignored
wlan0: RX AssocResp from 00:My:He:x:Ke:yx
(capab=0x471 status=0 aid=1)
wlan0: associated
wlan0: CTS protection enabled (BSSID=00:My:He:x:Ke:yx
)
wlan0: switched to short barker preamble (BSSID=00:My:He:x:Ke:yx
)
ip6_tables: (C) 2000-2006 Netfilter Core Team
It appears to be trying several times befor it connects. What is going on?
zak89 wrote:
> I can’t get it to connect at all right now. I get the following from
> dmesg after trying to connect via KNetworkManager:
>
>
> Code:
> --------------------
> wlan0: Initial auth_alg=1
> wlan0: authenticate with AP 00:My:He:x:Ke:yx
> wlan0: RX authentication from 00:My:He:x:Ke:yx (alg=1 transaction=2 status=13)
> wlan0: AP denied authentication (auth_alg=1 code=13)
> wlan0: authenticate with AP 00:My:He:x:Ke:yx
> wlan0: RX authentication from 00:My:He:x:Ke:yx (alg=1 transaction=2 status=13)
> wlan0: AP denied authentication (auth_alg=1 code=13)
> wlan0: authenticate with AP 00:My:He:x:Ke:yx
> wlan0: RX authentication from 00:My:He:x:Ke:yx (alg=1 transaction=2 status=13)
> wlan0: AP denied authentication (auth_alg=1 code=13)
> wlan0: authentication with AP 00:My:He:x:Ke:yx timed out
That is very clear. Your key is wrong. BTW, there is absolutely no need to
obscure the MAC address of your router. Knowing it would only benefit someone
within the listening range of your AP, and any wireless sniffer would get that
info within a fraction of a second. It is good to worry about security, but some
things are not worth worrying about.
zak89 wrote:
> Okay, I just got it to connect with KNetworkManager. Here is from dmesg:
>
>
> Code:
> --------------------
>
> wlan0: Initial auth_alg=1
> wlan0: authenticate with AP 00:My:He:x:Ke:yx
>
> wlan0: Initial auth_alg=1
> wlan0: authenticate with AP 00:My:He:x:Ke:yx
>
> wlan0: RX authentication from 00:My:He:x:Ke:yx
> (alg=1 transaction=2 status=13)
> wlan0: AP denied authentication (auth_alg=1 code=13)
> wlan0: authenticate with AP 00:18:01:81:a1:1a
> wlan0: RX authentication from 00:My:He:x:Ke:yx
> (alg=1 transaction=2 status=13)
> wlan0: AP denied authentication (auth_alg=1 code=13)
> wlan0: authenticate with AP 00:18:01:81:a1:1a
> wlan0: RX authentication from 00:My:He:x:Ke:yx
> (alg=1 transaction=2 status=13)
> wlan0: AP denied authentication (auth_alg=1 code=13)
> wlan0: authentication with AP 00:My:He:x:Ke:yx
> timed out
> wlan0: Initial auth_alg=1
> wlan0: authenticate with AP 00:My:He:x:Ke:yx
>
> wlan0: RX authentication from 00:18:01:81:a1:1a (alg=1 transaction=2 status=13)
> wlan0: AP denied authentication (auth_alg=1 code=13)
> wlan0: authenticate with AP 00:My:He:x:Ke:yx
>
> wlan0: RX authentication from 00:My:He:x:Ke:yx
> (alg=1 transaction=2 status=13)
> wlan0: AP denied authentication (auth_alg=1 code=13)
> wlan0: authenticate with AP 00:My:He:x:Ke:yx
>
> wlan0: RX authentication from 00:My:He:x:Ke:yx
> (alg=1 transaction=2 status=13)
> wlan0: AP denied authentication (auth_alg=1 code=13)
> wlan0: authentication with AP 00:My:He:x:Ke:yx
> timed out
> wlan0: Initial auth_alg=0
> wlan0: authenticate with AP 00:My:He:x:Ke:yx
>
> wlan0: Initial auth_alg=0
> wlan0: authenticate with AP 00:My:He:x:Ke:yx
>
> wlan0: RX authentication from 00:My:He:x:Ke:yx
> (alg=0 transaction=2 status=0)
> wlan0: authenticated
> wlan0: associate with AP 00:My:He:x:Ke:yx
>
> wlan0: authentication frame received from 00:My:He:x:Ke:yx
> , but not in authenticate state - ignored
> wlan0: RX AssocResp from 00:My:He:x:Ke:yx
> (capab=0x471 status=0 aid=1)
> wlan0: associated
> wlan0: CTS protection enabled (BSSID=00:My:He:x:Ke:yx
> )
> wlan0: switched to short barker preamble (BSSID=00:My:He:x:Ke:yx
> )
> ip6_tables: (C) 2000-2006 Netfilter Core Team
>
> --------------------
>
>
> It appears to be trying several times befor it connects. What is going
> on?
Pardon me, but I am using KDE. Is that still the correct address?
By the way, if it makes any difference, I just lost my wifi connection, with the following from dmesg:
usb 3-3: USB disconnect, address 2
usb 3-3.2: USB disconnect, address 5
usb 3-3.2.1: USB disconnect, address 7
usb 3-3.2.3: USB disconnect, address 8
usb 3-3.4: USB disconnect, address 6
usb 3-3: new high speed USB device using ehci_hcd and address 9
usb 3-3: configuration #1 chosen from 1 choice
hub 3-3:1.0: USB hub found
hub 3-3:1.0: 4 ports detected
usb 3-3: New USB device found, idVendor=0424, idProduct=2504
usb 3-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
usb 3-3.2: new full speed USB device using ehci_hcd and address 10
usb 3-3.2: configuration #1 chosen from 1 choice
hub 3-3.2:1.0: USB hub found
hub 3-3.2:1.0: 4 ports detected
...
usb 3-3.4: Product: NETGEAR WG111v2
usb 3-3.4: Manufacturer: NETGEAR WG111v2
...
usb-storage: device scan complete
And now the KNetworkManager applet says the “NetworkManager is not running.” It appears that the kernel decided to rescan all my hardware and lost the connection. This is driving me insane! Why is this only a problem with openSUSE?
Oh, and no, I was not trying to keep you from my access point! http://forums.opensuse.org/images/smiliesnew/smile.png I just have some search and replace strings I run on my posts for any “sensitive” info (in the past I have posted things that should not have been posted).
Okay, I am starting to think that this may be a driver issue? I am no expert, but it appears that the Ubuntu folks are having their share of trouble too.
Ndiswrapper does not work. I am starting to wish I used 32bit openSUSE. Maybe I should try a different kernel version?
I am finding so many conflicting solutions, I am not sure where to start.
zak89 wrote:
> Okay, I am starting to think that this may be a driver issue? I am no
> expert, but it appears that the Ubuntu folks are having ‘their share of
> trouble too.’
> (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/182473)
I think that is a different problem.
> Ndiswrapper does not work. I am starting to wish I used 32bit openSUSE.
> Maybe I should try a different kernel version?
What do you think my problem is? I can’t just be NetworkManager, since the cli approach fails too. Also, it seems that I am getting a connection to the access point, but dhcp is failing. Why is that? Do you think my key is wrong? It works on every other computer/os.
I am tempted to just install Fedora 10 and use that until openSUSE 11.1 comes out. It uses a newer kernel, and Fedora has in the past alway worked with this card. Does that make any sense?
I think I’ll just do that. I tried unloading rtl8187 and reloading it, but now I get the following output after the modprobe command:
FATAL: Error inserting rtl8187 (/lib/modules/2.6.25.18-0.2-default/kernel/drivers/net/wireless/rtl8187.ko): Unknown symbol in module, or unknown parameter (see dmesg)
I think I could figure if out if I put more time into it, but I have work to do and I can’t keep spending more time on my wireless. I don’t like Fedora much at all, but openSUSE 11.1 will be out soon.
Changed my mind. Upon my first look at Fedora 10 I thought “What was I thinking?!” Maybe there’s first class engineering under the hood, but it sure seems well buried in a half hearted attempt at looking “professional”. Sigh. Well, the installer crashed at 99% copying the liveCD image, and I didn’t need much convincing.
I am reinstalling openSUSE 11.0 (32bit this time) right now. What’s so ironic is that, after giving the installer the same essid and wep key I was giving before (on the previous install), the installer connected to my home network without a hitch over the same card the installed OS refused to use reliably. Right now it is downloading the installation packages over the same card that, if past attempts are any clue, it will fail to operate properly (without help, at least). Oh well.
I hope I haven’t tired you out, lwfinger! I really appreciate the help. I wish I could just find a simple reason for why my dhcpd wlan0 command times out on openSUSE, when it works fine on every other distro. Or why the installer connects without a problem, but the installed os is such a headache.
Well, just in time. This time the card worked right out of the box, no configuration at all. It held up about 1.6Gb of downloaded package updates and other post-install stuff, and lasted through the night. I got four bars of signal right now. Thanks alot, lwfinger.
To any who are interested, all I did differently was reinstall openSUSE 11.0 x86, and it worked perfectly (well, I also chose KDE 3.5, but I doubt that was a factor).
zak89 wrote:
> Well, just in time. This time the card worked right out of the box, no
> configuration at all. It held up about 1.6Gb of downloaded package
> updates and other post-install stuff, and lasted through the night. I
> got four bars of signal right now. Thanks alot, lwfinger.
>
> To any who are interested, all I did differently was reinstall openSUSE
> 11.0 x86, and it worked perfectly (well, I also chose KDE 3.5, but I
> doubt that was a factor).
I do not think switching from x86_64 to i386 made a difference as I’ve been
running a 64-bit system since I got my first 64-bit CPU; however I have not been
able to get my wireless to work using KDE4. I think that was the real reason it
works now.
Well, you certainly are more qualified to say so than I am, but I can’t see how the desktop environment would make a real difference. KDE 4 even uses KDE 3’s KNetworkManager.
Well, all’s well that ends well, I suppose. Except that now that you said that, I am starting to want to reinstall the 64bit version with KDE 3.5…
Just had a bit of a scare. I rebooted just now and my card wouldn’t connect. I hadn’t made any changes to the system, but it just wouldn’t get an ip address, even though it had excellent signal. I was panicked a bit, but I finally seem to have hit a working formula; just “ifconfig wlan0” (wait a little), then “ifconfig wlan0 up”, and connect via KNetworkManager. Seems to be okay now. Whew.
