Hi all, I am completely new to linux (don’t mind the console at al though, since I worked with computers before GUI even came around) and just now installed Opensuse 13.1 and all works fine, except the wireless. This sucks since I switched on from LinuxMint cause the wireless didn’t work. Now from my LinuxMint struggle I know way more about my crappy wireless-card than I ever wanted to, but it still doesn’t want to work.
The system is 13.1, KDE. The wireless card is linksys wmp54g 4.0 pci, which uses the Ralink rt2500 chips. The network is completely unsecured, broadcasting it’s name and using dhcp/dynamic ip.
(2) Now /sbin/lspci does indeed give: 01:07:0 Network controller: Ralink corp. RT2500 Wireless 802.11bg (rev 01)
–>Sys recognizes the wireless card.
(3) Went through an unbelievable 926 lines after ‘dmesg less’ but haven’t found a thing. I admit I was scanning at some point though.
–>no idea about firmware
(4) /usr/sbin/iwconfig: gives:
wlpls7 IEEE 802.11bg ESSID:off/any Mode: Managed Access Point: Not-associated Tx-Power=20 dBm Retry long lmit: 7 RTS thr:off Fragment thr:off Power Management: on
–>driver seems to work
(5) sudo usr/sbin/iwlist scan:
wlpls7 No scan results
*this is the first time it actually agrees to scan at all. I got Interface doesn’t support scanning before.
Having wasted hours trying to get my wireless to work on LinuxMint it seems I have the same problem with OpenSuse 13.1. I am at the point of giving up, but though I’d ask if anyone can tell what I can do next to get this working. Thanks in advance!
Are you using NetworkManager? If not you would have to set up the connection in YaST, not KDE (the KDE network management settings need NetworkManager to work).
I would suggest to enable it in that case: YaST->Network Devices->Network Settings->Global Options.
Thanks Wolfi323!
*
“Are you using NetworkManager? If not you would have to set up the connection in YaST, not KDE (the KDE network management settings need NetworkManager to work).
I would suggest to enable it in that case: YaST->Network Devices->Network Settings->Global Options.*”
No, I do not think I was using NetworkManager. YaST->Network Devices ->Network Settings->Global Options shows “Traditional Method with ifup” marked.
I changed it to “User Controlled with Networkmanager” and immediately get a pop-up saying "Applet needed NetworkManager is controlled by desktop applet (KDE plasma widget and nm-applet for GNOME). Be sure it’s running and if not start it manually. I press OK and it starts saving the network configuration, which hangs around 88% cue popup saying "Error no network running", I press OK and find myself back in the YaST control center.
So my guess is that the no network running is a consequence of not having this plasma widget running, it that correct?
No.
YaST doesn’t know anything about that applet. The popup is just a reminder for you that you should enable it and is shown unconditionally.
But the applet should be enabled by default. It should be in your system tray, but you’ll only see it if NetworkManager is running.
Hm, I never have seen that other error though.
What does YaST show if you enter Network Settings again? Is it back at “ifup” or is NetworkManager enabled now?
In the latter case maybe just try to reboot to get the network service started?
If I enter again, I first get a configuring network screen, then get shown a Network Settings screen with two network-cards/connections shown as ‘not configured’ and this immediately grays-over to get a pop-up saying: *"**Warning *Network is currently controlled by NetworkManager and its settings cannot be edited by YaST. To edit the settings use the NetworkManager connection editor or switch the network setup method to Traditional with ifup. "
At the Global Options the User Controlled with NetworkManager is still selected.
NetworkManager.service - Network Manager
loaded: loaded (…etc… /enabled)
Active: active (running) since Sun 2013 etc… 28mins ago
Main PID: 6639 (NetworkManager)
CGroup: /system.slice/NetworkManager.service
|-6639 /usr/sbin/NetworkManager - - no- daemon
–>NetworkManager is running
lspci -nnk: oh man, I am on a different pc typing this (hey no connection) so no way I can type all that. What are you looking for? About the network controller it says:
–>So again it seems the right driver is found and in use.
The /user/sbin/iwconfig I gave in my OP:
wlpls7 IEEE 802.11bg ESSIDff/any Mode: Managed Access Point: Not-associated Tx-Power=20 dBm Retry long lmit: 7 RTS thrff Fragment thrff Power Management: on
I got a W-lan interface in the tray.
I’ll reboot now.// Done, it didn’t do anything as far as I can tell.
The /user/sbin/iwconfig I gave in my OP:
wlpls7 IEEE 802.11bg ESSIDff/any Mode: Managed Access Point: Not-associated Tx-Power=20 dBm Retry long lmit: 7 RTS thrff Fragment thrff Power Management: on
Ah, ok. Sorry.
Forgot about that.
I got a W-lan interface in the tray.
And can you connect there? (Click on it)
Do you see any networks there?
Maybe the Wifi is turned off in the BIOS or via a switch?
Please also run:
rfkill list
You may have to install the package “rfkill” first.
I can’t connect via the wireless network thing in the tray no, since I see no networks. Spoon-feeding it the ESSID, physical adress or other data does not seem to help either.
Wireless is not turned off in the BIOS or via a switch, since I simply removed an winXP installation from it to put LinuxMint and then OpenSUSE on it. The card worked fine with the winXP install so BIOS and switch seem out of the question.
It tries to get a package list from the online repos, since you don’t have a network connection this doesn’t work obviously. Enter YaST->Software Repositories and disable all repos except the Installation DVD.
Ok, I give up and will be installing xp again. I had this weekend to get Linux working and it’s not. So, time to cut my losses. Thanks Wolfi323 for your efforts to try and help me.
Well, I’m not really that experience with wireless, and especially not with your particular adapter.
But it seems to be a general problem, if you couldn’t get it to work in Mint either.
Maybe that particular model is just not supported for whatever reasons? Maybe there’s a bug in the driver?
Anyway, I guess we’ll never know…
