WLAN Unavailable in NM - openSUSE 13.1

English Network/Internet
#1

I am sorry to bother the forum with this error, but I have tried to read wifi threads and google about this error with no result

The wifi adaptor is a D-link USB dongle, model DWL-G122 connected to my HP Compaq 6910p laptop running KDE 13.1. The internal wifi is disabled in BIOS because it is not working any more.

As fare I can see in the dmesg /messages-file the usb dongle is found and the rt73usb driver is loaded.

lsusb says:
Bus 002 Device 005: ID 07d1:3c03 D-Link System AirPlus G DWL-G122 Wireless Adapter(rev.C1) [Ralink RT2571W]

And rt73usb is found in the kernel with: lsmod |grep rt73usb
rt73usb 30986 0
rt2x00usb 20041 1 rt73usb
rt2x00lib 53042 2 rt73usb,rt2x00usb
crc_itu_t 12627 2 rt73usb,firewire_core
usbcore 206447 6 rt73usb,rt2x00usb,usbhid,uhci_hcd,ehci_pci,ehci_hcd

But only my wired network adaptor shows up in Networkmanager, and no wifi or enable wifi is possible :frowning:

I have a paste of my messages file here:
SUSE Paste

Say if the forum needs more information, and I hope you can help me

Jan

#2

Hi, could you please post the output, between CODE tags, the # in the editor, of the commands below,

lsusb -t

and

ip addr
#3

BTW: I’d also give the internal wificard another shot. You wouldn’t be the first one to find out the card works, was just missing some firmware and the appropriate driver. 13,1 has a newer kernel which could also make a difference.

#4

Maybe I forgot to write that I am working on a new installation (not upgrade)

I think some progress has happened :slight_smile:

I checked in Yast that NM was running the network and not ifup. I didn’t change to ifup. Just canceled again. I have also done one or two rebooting. And now WLAN Interface is showed in NM applet. But it greyed out together with Enable wireless.

In Manages Connection I have tried to Add a new connection with the same contents as another laptop, which is runing the same 13.1 but internal wifi adaptor. So SSID and security /WPA2 personal are all the same. I have tried dhcp or manual IPV4, but nothing helps. What more is tried, is to use "Restrict to Inerface: wlp0s29f7u1.

I found this in end of the NM log:
(wlp0s29f7u1): device state change: unmanaged -> unavailable (reason ‘managed’) [10 20 2]
but not sure what it means and if thats the error.

I paste the NM log, but don’t look at the buttom, because I tried different things.
SUSE Paste

Jan

#5

Sorry our replies passed each other.

I will come back in a moment with the information you want.

#6

Looks like the driver is there, and OK, but the radio switch is switched of by the hardware.

Install

zypper in rfkill

, then run

rfkill list

If one of the options says “yes”, unblock the index no, see example from my laptop


laptop:~ # rfkill list
0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: yes
1: asus-wlan: Wireless LAN
        Soft blocked: yes
        Hard blocked: no
laptop:~ # rfkill unblock 1
laptop:~ # rfkill list
0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
1: asus-wlan: Wireless LAN
        Soft blocked: no
        Hard blocked: no

After the first command my wifi stops working immediately, after the second it comes back up :).

#7

I tried this:

rfkill list
0: hp-wifi: Wireless LAN
        Soft blocked: no
        Hard blocked: yes
1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
2: hp-bluetooth: Bluetooth
        Soft blocked: yes
        Hard blocked: yes
3: hp-gps: GPS
        Soft blocked: yes
        Hard blocked: yes
linux-rsxz:/home/kjersti # rfkill unblock 0
linux-rsxz:/home/kjersti # rfkill list
0: hp-wifi: Wireless LAN
        Soft blocked: no
        Hard blocked: yes
1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
2: hp-bluetooth: Bluetooth
        Soft blocked: yes
        Hard blocked: yes
3: hp-gps: GPS
        Soft blocked: yes
        Hard blocked: yes

But it didn’t come up :frowning:

#8

Here are info to your ealier questions:

lsusb -t
/:  Bus 07.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
    |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
/:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
    |__ Port 2: Dev 2, If 0, Class=Vendor Specific Class, Driver=, 12M
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
    |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=rt73usb, 480M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/4p, 480M

ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:1e:ec:a2:9b:06 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.48/24 brd 192.168.1.255 scope global enp0s25
       valid_lft forever preferred_lft forever
    inet6 fe80::21e:ecff:fea2:9b06/64 scope link 
       valid_lft forever preferred_lft forever
3: wlp0s29f7u1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 00:15:e9:33:f7:d8 brd ff:ff:ff:ff:ff:ff

It not possibly to get the internal wifi adaptor running because some nasty liquid ran down into the internal part of the touch bottum that enable wifi :frowning:
Unless there some trick to do a sw activate of the internal wifi passing the buttom?
I have tried earlier to search this possibility without luck :frowning:

#9

What does

nm-tool

say

#10

nm-tools says:

nm-tool

NetworkManager Tool

State: disconnected

- Device: wlp0s29f7u1 ----------------------------------------------------------
  Type:              802.11 WiFi
  Driver:            rt73usb
  State:             unavailable
  Default:           no
  HW Address:        00:15:E9:33:F7:D8

  Capabilities:

  Wireless Properties
    WEP Encryption:  yes
    WPA Encryption:  yes
    WPA2 Encryption: yes

  Wireless Access Points 


- Device: enp0s25 --------------------------------------------------------------
  Type:              Wired
  Driver:            e1000e
  State:             unavailable
  Default:           no
  HW Address:        00:1E:EC:A2:9B:06

  Capabilities:
    Carrier Detect:  yes
    Speed:           100 Mb/s

  Wired Properties
    Carrier:         off

I am replaying this thread from the laptop with the bad wifi we are working on. I am replaying by running on the wired interface. Can it somehow damage the state of the bad usb wifi ?
This replay I tried to unplug the wired cable when I typed the nm-tool command and then reconnect. But I don’t see any difference.

#11

On 12/12/2013 09:16 AM, janoleholm wrote:
> It not possibly to get the internal wifi adaptor running because some
> nasty liquid ran down into the internal part of the touch bottum that
> enable wifi :frowning:
> Unless there some trick to do a sw activate of the internal wifi passing
> the buttom?
> I have tried earlier to search this possibility without luck :frowning:

If this information had been in your first posting, we could have gotten it
resolved more quickly. It seems that the defective switch is locked in the “Off”
position. The way the radio-kill process works, if any radio is blocked, then
all radios are blocked.

From the rfkill listing, you need to identify what driver is loaded for the
built-in wireless card and blacklist it. You can find the driver with
“/sbin/lspci -nnv”. Once you know that info, create a new file in
/etc/modprobe.d/ with the name “50-wireless.conf” containing a line “blacklist
name_of_driver”. Just to be clear, substitute the actual name of the driver in
that line.

After rebooting, again run the rfkill listing. If the Bluetooth and GPS entries
are still blocked, then we will need to find the drivers used there. If that is
the case, please post the output of lsmod.

#12

I don’t think I have mentioned that USB D-link dongle has 2 LED’s

Act: No light
Link: flashes once in a while

#13

Please look at the previous page, Larry (lwfinger) is the wireless guru you should listen to :).

#14

I am so sorry that I didn’t see Larry’s post in previous page :slight_smile:

I know Larry is the expert, and he has helped earlier too - thanks Larry.

I understand Larry’s advice, but I don’t think it will help, because I have disabled the internal wifi in the bios, and I don’t think that the internal wifi driver was loaded.
But to be sure I have taken out the D-link USB dongle and instead enabled the internal wifi in bios, installed the driver. As it is BCM4311 device I install the driver - also from Larry’s help page. And lspci command has this out (only part with wifi is cut/pasted):

10:00.0 Network controller [0280]: Broadcom Corporation BCM4311 802.11b/g WLAN [14e4:4311] (rev 02)
        Subsystem: Hewlett-Packard Company BCM4311 802.11b/g Wireless LAN Controller [103c:1375]
        Flags: bus master, fast devsel, latency 0, IRQ 17
        Memory at e4000000 (64-bit, non-prefetchable) [size=16]
        Capabilities: [40] Power Management version 3
        Capabilities: [58] Vendor Specific Information: Len=78 <?>
        Capabilities: [e8] MSI: Enable- Count=1/1 Maskable- 64bit+
        Capabilities: [d0] Express Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [13c] Virtual Channel
        Capabilities: [160] Device Serial Number d6-09-00-ff-ff-4f-00-21
        Capabilities: [16c] Power Budgeting <?>
        Kernel driver in use: b43-pci-bridge
        Kernel modules: ssb

I am unsure what the right name for the blacklist file contens shall be: b43-pci-bridge, b43 or b43xx?

I found different names looking in messages and with lsmod command.[/size]

#15

On 12/12/2013 11:06 AM, janoleholm wrote:
>
> I am so sorry that I didn’t see Larry’s post in previous page :slight_smile:
>
> I know Larry is the expert, and he has helped earlier too - thanks
> Larry.
>
> I understand Larry’s advice, but I don’t think it will help, because I
> have disabled the internal wifi in the bios, and I don’t think that the
> internal wifi driver was loaded.
> But to be sure I have taken out the D-link USB dongle and instead
> enabled the internal wifi in bios, installed the driver. As it is
> BCM4311 device I install the driver - also from Larry’s help page. And
> lspci command has this out (only part with wifi is cut/pasted):
>
> Code:
> --------------------
> 10:00.0 Network controller [0280]: Broadcom Corporation BCM4311 802.11b/g WLAN [14e4:4311] (rev 02)
> Subsystem: Hewlett-Packard Company BCM4311 802.11b/g Wireless LAN Controller [103c:1375]
> Flags: bus master, fast devsel, latency 0, IRQ 17
> Memory at e4000000 (64-bit, non-prefetchable) [size=16]
> Capabilities: [40] Power Management version 3
> Capabilities: [58] Vendor Specific Information: Len=78 <?>
> Capabilities: [e8] MSI: Enable- Count=1/1 Maskable- 64bit+
> Capabilities: [d0] Express Endpoint, MSI 00
> Capabilities: [100] Advanced Error Reporting
> Capabilities: [13c] Virtual Channel
> Capabilities: [160] Device Serial Number d6-09-00-ff-ff-4f-00-21
> Capabilities: [16c] Power Budgeting <?>
> Kernel driver in use: b43-pci-bridge
> Kernel modules: ssb
>
>
> --------------------
>
>
> I am unsure what the right name for the blacklist file contens shall be:
> b43-pci-bridge, b43 or b43xx?
>
> I found different names looking in messages and with lsmod command.

Blacklist ssb and b43, and leave the wireless enabled in the BIOS.

[/size]

#16

Now I have blacklist’ed b43 and ssb and left bcm4311 enabled in BIOS. Here are contents of blacklist files:

linux-rsxz:/etc/modprobe.d # cat 50-wireless.conf
blacklist b43
blacklist ssb

And this is list of rfkill:

rfkill list
0: hp-wifi: Wireless LAN
        Soft blocked: no
        Hard blocked: yes
1: hp-bluetooth: Bluetooth
        Soft blocked: yes
        Hard blocked: yes
2: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
3: hp-gps: GPS
        Soft blocked: yes
        Hard blocked: yes

I think there are 2 wifi’s and phy0 is unblocked. Can you see which is usb and which is internal? No change in NM applet WLAN still unavailable.

#17

On 12/12/2013 11:46 AM, janoleholm wrote:
>
> Now I have blacklist’ed b43 and ssb and left bcm4311 enabled in BIOS.
> Here are contents of blacklist files:
>
> Code:
> --------------------
> linux-rsxz:/etc/modprobe.d # cat 50-wireless.conf
> blacklist b43
> blacklist ssb
>
>
> --------------------
>
>
> And this is list of rfkill:
>
> Code:
> --------------------
> rfkill list
> 0: hp-wifi: Wireless LAN
> Soft blocked: no
> Hard blocked: yes
> 1: hp-bluetooth: Bluetooth
> Soft blocked: yes
> Hard blocked: yes
> 2: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: no
> 3: hp-gps: GPS
> Soft blocked: yes
> Hard blocked: yes
>
>
> --------------------
>
>
> I think there are 2 wifi’s and phy0 is unblocked. Can you see which is
> usb and which is internal? No change in NM applet WLAN still
> unavailable.

The USB device is phy0. It is OK.

Where is the lsmod output?

#18

Here is a paste of lsmod:

SUSE Paste

I don’t think I could find b43 or ssb with: lsmod |grep b43 or ssb

#19

Sorry, that I have to leave soon :frowning:
I will be back tomorrow. It is evening here in Denmark now and friends coming by.

Thanks for all your help so fare

Jan

#20

On 12/12/2013 12:16 PM, janoleholm wrote:
>
> Sorry, that I have to leave soon :frowning:
> I will be back tomorrow. It is evening here in Denmark now and friends
> coming by.
>
> Thanks for all your help so fare

We all work at our own schedule. Of course, I am not waiting breathlessly for
your response. :slight_smile: After all, it is your problem - my systems are working fine
except for a kernel oops in a new driver that I am readying.

I think the rfkill blockage is coming from the module hp-wmi. Please blacklist
it as well. This one will probably affect your fn keys, but at least we can test
if it is the problem.

If you still have the radio blocked, please blacklist bnep and bluetooth. I do
not know what BT devices you might have, but you have radio block originating there.