I have just installed openSuse 11.4 KDE 64-bit on a Dell M1330. When I click on my networking panel, it says WLAN interface is unavailable. I’ve followed the steps in the stickied post and found the WLAN hardware info, a screenshot of which is below:
Next it says to do this - you need to look at the logs, in particular the info in /var/log/boot.msg. To see this, you need YaST => Miscellaneous => System Logs and select boot.msg.
In YaST there is no such option for system logs under miscellaneous, so I can’t do that. The results of the sudo /usr/sbin/iwlist scan command produce the following:
*root’s password:
lo Interface doesn’t support scanning.
eth0 Interface doesn’t support scanning.
wlan0 Interface doesn’t support scanning : Network is down*
The wireless box in my network panel is ticked (for enabled). Anyone able to point me in the right direction?
When I first installed on my Dell laptop, the wireless card wasn’t recognized at all until I installed broadcom drivers. You at least seem to be ahead of that problem.
After I got it working, I used FnF2 in Windows to turn off wireless. Then I booted into linux to see the effect. I saw pretty much what you are describing. I booted to Windows, did FnF2 to turn on Wireless. Then, if I recall, I had to shutdown, reboot, and do the FnF2 a second time before it would stick.
I later discovered that I could have just used FnF2 within opensuse to achieve similar results. However, that still left the wireless soft-blocked. Fortunately, I had installed “rfkill” (using a wired connection), and that could clear the soft-block and put be back in business with Wireless.
I don’t know if any of that will work for you. If you can install “rfkill” using a wired connection, you will at least have a better idea of seeing what is happening. Use “rfkill list” to see what is blocked.
@nrickert it seems that i have the same problem…but i can’t unblock the soft block…do you know how to solve it?
you can see here: my wireless is not working…
Yes, that was my reaction too. Setting up an ethernet connection is rather simple. You could do it manually, without help from either the “ifup” scripts or NetworkManager. If this user is only able to do it with NetworkManager, then something else is going on that he is not telling us about.
Back, now, to TheLoverZ: The only reasons why “ifup” would fail for the wired connection are:
(1) the ethernet device is not recognized by the system, in which case NetworkManager would not help at all;
(2) there is no DHCP for the network, in which case NetworkManager would not work at all, though perhaps manual assignment of an IP would work;
(3) the DHCP for the network is broken, and works only with “dhclient” (used by NetworkManager), but not with “dhcpcd” (the default dhcp client with “ifup”.
I wanted to know what happens with “ifup” on WiFi, because in my experience it is more reliable than NetworkManager. The reason to use NetworkManager is to give more user control and to allow easier switching between networks with a laptop.
There is one possible problem with WiFi that you might not have eliminated. That is when you have setup MAC filtering on the WiFi network, but then forgotten that you set it up. If the wlan card MAC is not in the MAC filter list, you will be able to scan the network but you will never be able to associate. That at least seems to fit the evidence that you have provided here. It might be a possibility that you could investigate.
On 07/15/2011 12:06 AM, TheLover Z wrote:
>
> I got this now…what is it…
>
> /usr/sbin/iwlist scan
> lo Interface doesn’t support scanning.
>
> eth0 Interface doesn’t support scanning.
>
> wlan0 Interface doesn’t support scanning : Device or resource busy
That usually means that NetworkManager is scanning. Wait a few seconds and retry.
The problem may also be in your registry settings, which causes problems with your wireless Internet connection. So, check the keys to see if any other third-party local area network (LAN) manager is running. Remove any third-party LAN and reboot your system.
