OpenSUSE Wireless :: Wireless Connection Stuck On Activating
May 6, 2011
I've been having problems with connecting to my router with my wireless card. Sometimes knetworkmanager attempts to the connect to my wireless via it's saved profile but it just stays on "Activating" for about 45 seconds then just stops. This only started happening a few days ago, so maybe the new kernel update has something to do with it?
I've tried to debugging the problem myself and have found if I reboot my router knetworkmanager can connect immediately to the wireless router, but also something interesting I found was is I assigned a IP Address and DNS manually on the saved profile it would connect with no problem (No reboot of router required), so it is indicating there is a problem with getting network settings. I've confirmed that the wireless card is not hard or soft blocked through rfkill.
I was using the box standard ath5k driver when this problem started happening and even went as far as a complete reinstall but ironically enough on first boot from a fresh install my wireless could not connect with the problem described above. I've since moved to the compat-wireless drivers but the problem remains.
I checked a couple of logs, one log file of significance was the wpa_suppliment log which was full of these messages: From all my debugging I can only assume that the kernel update is a possible cause for all of this as the problem occurring on first boot of a fresh install sounds like a general bug. I've got all of the requested information about my wireless card below, hope I've got everything:
I think I need wireless App. Its really frustrated to get wireless to work. I always a window user since window 3.1 came out. I am trying to learn new OS, but only to get stuck on getting my wireless to connect. Maybe I am not cutting out to be linux user?
I am getting trouble with knetwork manager. I created a new connection by scanning and connecting using knetwork manager. But every time connection gets disconnected and ask for password and again it connects.
I have searched and have not found anything specific to my issue. I am currently using NDISWrapper to load the bcmwl15 driver and when it's active it works beautifully.Problem is sometimes at boot, the card doesn't "turn on" and I don't know how else to describe it. The OS does not even detect that the hardware is present. I have disabled wireless hotkey in BIOS. The only way to make the wireless card "active" is to reboot with the wiredconnection to the router. After doing that the wireless card "wakes up" and works awesome.Is there anything I can do to make sure the driver load at boot?mes I get the error that NDISWrapper is not modprobbed when I go to network configuration and if I wish to do i now? I don't know if that has anything to do with the boot sequence. Using the <modprobe ndiswrapper> command as root does nothing permanant
I own an ASUS N61JV-X2 notebook PC. It has an Atheros Communication, Inc. AR9285 Wireless Network Adapter. 03:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01) 03:00.0 0280: 168c:002b (rev 01) I cannot see any SSIDs including my home Verizon FiOS 802.11 G WPA2-AES-TKIP encrypted network. I went to Starbucks to try to connect to their free Wi-Fi and I could not make a connection. How do I solve this problem so that I can connect to a SSID of my choice and make a wireless connection while using GNOME 3?
I recently bought a D-Link DIR-655 router capable of 802.11n operation, upgrading from a DIR-624 router only capable of 802.11g operation. While my overall setup uses wired connections, other people in the house prefer wireless, and the upgrade was undertaken more for a hoped for increase in wireless range, rather than the possibility of increased speed, since the router is located to accommodate the wired connections. However, to test the 802.11n operation I bought a D-Link DWA-130 USB dongle for my now 5-year old laptop, which comes with an otherwise satisfactory 100Mbs ethernet port(eth1) and an 802.11g wireless card(eth0). By checking the dmesg | grep firmware output after I plugged in the dongle I determined that the necessary firmware was rtl8192sfw.bin, which I found on the web, and downloaded into the directory /lib/RTL8192SU.
A subsequent reboot and then YaST > Network Devices > Network Settings showed the device as wlan0, but not configured. I changed the Network Setup Method to ifup (since I can see no way to do a device configuration in Network Manager), and configured the device, and at the same time deleted the configuration for the existing 802.11g wireless card(eth0). I then rebooted, went back into YaST to confirm the wlan0 device was configured and the 802.11g device (eth0) was not, changed the Network Setup Method back to Network Manager, rebooted again. Making sure that the router was set to only transmit/receive using 802.11n I then typed iwlist scan. To my surprise, the output showed first that the supposedly unconfigured eth0 device seemed to be still active, for it found my home network, and claimed that the protocol used was 802.11g. On the other hand, the newly configured wlan0 device produced the message: "Interface doesn't support scanning: Network is down".
First, should I expect iwlist scan to work for a device that shows as unconfigured? And even if it should work, shouldn't it show 802.11n as the protocol, assuming that the router is in fact telling the truth? Is there any independent means to determine if the router is only using 802.11n as it claims? Second, the overall goal is to make the wireless network in the house 802,11n only, and since the dongle is backward compatible with 802.11g, I would expect to permanently unconfigure the eth0 device and use the dongle, both here and on the road. I do not need two wireless connections on my laptopThe laptop is running SuSE 11.2 as of about a month ago. Some relevant(I hope) command line output:siracusa:~ # uname -aLinux siracusa 188.8.131.52-0.2-desktop #1 SMP PREEMPT 2010-03-16 21:25:39 +0100 i686 i686 i386 GNU/LinuxUSB Information
siracusa:~ # lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 2001:3301 D-Link Corp. [hex]
I just started using OpenSUSE on an old laptop. It seems that I have my graphical problems at least temporarily solved, but I continued to lose my wireless connection after an hour of use. This is an old and well supported chipset (RT2500) and I had never had any issues with it before. I use WPA security, and one kind poster suggested I had a line for using the old "wext" driver in the /etc/sysconfig/ifcfg-wlan0 file, and that seems to have sorted it since I have not had any further issues since doing that edit. I eventually found the information on my own:
# Note: This option requires a wpa driver supporting it, like # the 'nl80211' driver used by default since openSUSE 11.3. # When you notice problems with your hardware, please file a
There seem to be a number of people that believe the junk that NetworkManager is buggy.As I believe the opposite, I want to offer more detailed instructions on how to create the initial connection, and how to troubleshoot the process. Once readers of this group have commented on this draft, I plan to ask the moderators to make it a sticky.
This description will be specific to the KDE desktop. The steps will be similar for Gnome, but the details may be different.
Step 1: Do you have a Network Manager applet in the system tray? If not, use YaST => Network Devices => Network Settings. Under the "Global Options" tab, click on the "User Controlled with Network Manager" button. If it is already set, you will get a warning box when "Network Settings" starts.
Step 2: Now you should see the NM applet. Click on it and check the popup. If the "Enable Wireless" checkbox is inactive (gray), there are several possibilities: (1) Your wireless device driver is not loaded, (2) the necessary firmware is not available, or (3) an rfkill switch/button is wrong. For (1), check "hwinfo --network" and check the "Driver" line. If it is blank, then you need to run the command "/sbin/lspci -nn" if the device is connected to a PCI bus, or "lsusb" if a USB device. Post the results on the Wireless forum. For (2), look at the output of "dmesg | grep firmware", which will list the name of the file(s) to be loaded.
For Broadcom devices that use either b43 or b43legacy, the firmware is obtained by using the command "/usr/sbin/install_b43xx_firmware". You will need a wired connection to complete this step. For (3), you will also need a wired connection and install the "rfkill" package using the command "sudo zypper in rfkill". The interrogate the current settings with "/usr/sbin/rfkill list". If any device is "Hard blocked", then wireless will be disabled.
Step 3: Once the "Enable Wireless" checkbox is active, check it and click on "Manage Connections". Choose the Wireless tab and click on Add. Enter the name for this connection. You will probably want to check the "Connect Automatically" box. Next click on the Scan button. If you do not see your Access Point (AP) in the map, you will not be able to get a connection. Click on the AP you want, and click OK. The (E)SSID should be in the SSID box. The other boxes on this screen should be OK as is. If you have several APs with the same SSID, but you wish to restrict the connection to only one of them, then you should enter its MAC address in the BSSID box.
This usage is rare. Next click on the "Wireless Security" tab and enter any encryption secrets. The correct type should have been selected. For WEP encryption, you will need to use the hex key, not a passphrase. Once this is complete, click OK to close this screen, and the configure screen. During this process, a popup should appear offering to use a wallet to store the connection secret. If you use a password on this wallet, you will need to enter that password each time you log in. If you set no password on the wallet, the security level is lowered, but entering a password is avoided.
Step 4: At this point, you will need to disconnect the wire. Whenever the computer can make a hard-wired connection, it will supersede any wireless option. The wireless connection should then occur automatically.
I set up 11.4 in my laptopnd, after updating and downloading the proper firmwareeverytihing runs great. I already configured the wireless network via the standard NetworkManager but the connection never starts automatically. When I boot up it reports all the wireless connections available and also let me connect to hidden networks (mine is not broadcasting so I have to use this option). I had to reconfigure my network options the first time I selected Hidden Networks but it connects fine. Please note I had already selected the "Automatic connection" optionSo the only question is how I configure my equipment so it connects automatically to the already configured network
A friend who switched ISP's gave me his old Linksys WRT54-G wireless router. I went through the installation procedure and had a wireless connection up and running - smiley face. I had security set up for WPA, and decided to upgrade it to WPA2. Another smiley face. When I went to connect (had already done so successfully), I noticed it referred to my wireless as Linksys - I was expecting to see the SSID. So I started playing around in Network Manager and now I have things all effed up.
Don't know exactly what I did, but now I have no wireless. So I ran a few commands (lshw -C network, iwconfig, ifconfig, and iwlist scan), and looking at the results I see what appear to be inconsistencies in the output. I've posted them below, and make the following observations:
1. Under the lshw it refers to my wireless connection logical name as wmaster0, and has the correct MAC address, etc.
2. Under the iwconfig it says, 'wmaster0 no wireless extensions', but then refers to wlan0 as the wireless connection (although it does not seem to be running).
3. Under ifconfig I see both a wlan0 and a wlan0:avahi. The wlan0 has no IP, the wlan0:avahi does, but it is incorrect.
I am trying to get a netgear wireless usb card to work correctly. I have installed ndiswrapper and gotten the correct drivers installed. The device does show up with lsusb. I can't seem to figure out how to get the wireless card to show up in gnome to start using it.
Update: the ndiswrapper module does load but when i run ndiswrapper -l it just shows the driver installed but, it is not showing my wireless usb card (0846:9020).
I just installed openSUSE dual-boot with windows. Wireless works fine on windows. Only ethernet works on openSUSE. At first, it couldn't even find my wireless network. With my friend's help we experimented and tried everything to find the driver for my broadcam4312 driver.
Later, my friend some update from the official openSUSE peeps... Then, the wireless could my network. I entered in my password and then hoped for the best but then it got stuck on the Obtaining IP Adress part. I know I got the rite password.
Is there an easy way (or even a hard way) to activate wireless network capability from the command prompt? I want to do this because I like to use the fvwm window manager, but I also like wireless! (In fvwm wireless networking doesn't start up automatically.)
I tried just starting the wireless by...
Despite the promising messages, wireless didn't work.
I'm fairly new to Ubuntu. I'm struggling to enable wireless on my Acer Travelmate 2480. Wireless was turned on and off in Windows with a button which does nothing in Ubuntu.I think I must be missing drivers or something, but how do I get them if I can't connect to the internet?
I am running FC13 on a Compaq Presario 2100 using a Broadcom BCM4306. I was able to get it running thanks to Fedora Unity Project. But It's a very unstable connection. I don't know what settings to adjust or enable or disable. It's not my router, this is the only wireless connection in the house that I have trouble with.
I'm trying to set up a wireless connection to my personal wireless net. I have a Linksys N router and I am using a WMN 300n adapter. I found out how to get the connection manager but I'm not sure if i ams upposed to enter the MAC of the router and I know what the SSID is but the B**ssid(not quite sure what that was and I'm on a Win7 system right now)so any info to get my wireless connection now
I was with SuSe linux time before it became part of Novell. Of course many of my hardware did not work at that time. But the large repository on installation disc attracted me to SuSE. I have been with other version of linux for last few years. With the release of SuSE 11.2, i thought i would just give it a try. I like what i see and would very much like to make a comeback. Except, my wireless usb stick is not working.I got Asus USB-N13 wireless stick. I tried all the article i found how to install wireless card using ndiswrapper or without, but sadly its still not working.
I have a problem getting a wireless connection to appear on OpenSUSE 11.3. I think it's because I don't have the drivers. I used to use Ubuntu, where the drivers just had their own menu, but I'm lost with OpenSUSE. I was told to post the output of dmesg | egrep "ssb|b43" and here it is:
I've got an old Compaq Armada E500 laptop (850mhz PIII, 512mb RAM, 30GB HD) that I've been running OpenSUSE 11.1 w/Gnome desktop. My wireless adapter (Linksys Wireless-G, model WPC54G ver. 2 w/acx-111 chipset) worked well with this setup, but no that I've upgraded to OpenSUSE 11.2 w/KDE, I've got to start all over. I tried doing what I did before, which was to copy the firmware file into /lib/firmware.
I m trying to get internet connection via wireless on Suse 11.4. Although ifstatus eth1 reports an IP address (and router reports a wireless connection) no Internet access is possible, which seems very strange (including the admin page of the router).
When I attempt to connect to a wireless network, the network manager asks me for the network's password, then says 'setting network address' for 20 or so seconds, then asks me for some random Hex or ASCII key in the same type of window I put the password in (Secrets for Noel -- KDE Daemon). Since a key is already typed into the window, I press OK, which then causes the network manager to go back to 'setting network address', then the window pops up again and keeps repeating itself.
I'm running Opensuse 11.4 with KDE, and my driver is ath9k. I don't know much about linux so please don't tell me to 'recompile this' or 'change this setting' without explaining how to do it. Please help, I've been unable to connect to wireless in OpenSUSE for 2 weeks now.
im having a problem setting ad hoc wireless network between two opensuse boxes, using network manager, every time im about to smash the box, maybe im doing something wrong in the steps or something idk
I have installed opensuse 11.3. I am unable to connect to my wireless connection. KNetworkManager finds the connection (when I scan for connections), I can enter the WEP Hex key, it says it is configured. Goes through its "check list" when you click "ok", and all seems good. But it won't connect. When I run "nm-tool" I get: State: unknown WARNING **: error: could not connect to NetworkManager Just ridiculous, brand new, up to date OS, and its this difficult to connect to a wireless router!
I'm using OpenSuse 11.1 (but it applies also to 11.0) on a Dell XPS, NetworkManager and scpm to manage profiles. I configured wireless network without problems and all runs perfectly. The annoying problem is that the wireless connection doesn't start at boot. Also by clicking on the NetworkManager applet networks are not displayed
But, as soon as I launch network configuration from Yast without do anything other, magically the wireless network is recognized and the PC connects to it.
It seems that the network configuration from Yast activates NetworkManager to connect or it activates the interface or the hardware.