openSUSE 13.2: Wireless adapter not recognized, even after release notes followed

Hello,

Just upgraded to openSUSE 13.2 KDE 64-bit. Also installed Packman repo and broadcom-wl. It turned out b43 is already available and installed via YAST > Software Management.

I followed the openSUSE 13.2 Release Notes to disable Wicked service and enable Network Manager service. However, after reboot I notice the light on my wireless adapter is not lit. It’s Linksys WPC-300n V1 PCMCIA card. Somehow the adapter is not recognized.

#lspci -nnk does not show the kernel module, i.e. wl, for this card.

#rfkill list shows:

0 phy0: wireless LAN
softblock: no
hardblock: yes

Any suggestions? Thank you

:frowning:

If you are using a laptop then you should look for the wireless button/switch.

Hi,

Thanks for your reply. I forgot to switch it back on. In any case, even if the wireless switch is in the ON position, the two pilot lights are not on for Linux distros, but lit up when I boot into Windows. I believe the adapter is near the end of its life.

:wink:

Have you tried installing the kernel-firmware package?

Hi, taytong888

what’s the output of

lsmod | grep mii

and

sudo lspci

I’ve reported a related problem as a bug here:
https://bugzilla.opensuse.org/show_bug.cgi?id=903525

Take a look and follow the discussion. Maybe also add info if you have any.

In my opinion after a clean install everything should just work or there should be a message shown about how to fix the problem if there is a legal issue. After all there are packman repos and other solutions, and someone that installs an OS for the first time isn’t supposed to automatically know every workaround to every problem with Linux. Things should just work, or instructions should be easily accessible about how to fix a problem.

OpenSUSE LiveDVD with KDE 13.1 and 13.2 works fine for my Broadcom 43xxx, maybe you should test installing from that iso-file instead?

It’s already installed, automatically. Without it, there would be no b43-firmware or broadcom-wl, etc.


lsmod | grep mii

gives:

mii 13654 2 8139cp,8139too

The following yields more info:


#lspci -nnk

00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD/ATI] RC410 Host Bridge [1002:5a31] (rev 01)
Subsystem: Toshiba America Info Systems Device [1179:ff00]
00:01.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RC4xx/RS4xx PCI Bridge [int gfx] [1002:5a3f]
Kernel modules: shpchp
00:06.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] RC4xx/RS4xx PCI Express Port 3 [1002:5a38]
Kernel driver in use: pcieport
Kernel modules: shpchp
00:12.0 IDE interface [0101]: Advanced Micro Devices, Inc. [AMD/ATI] IXP SB4x0 Serial ATA Controller [1002:4379] (rev 80)
Subsystem: Toshiba America Info Systems Device [1179:ff00]
Kernel driver in use: sata_sil
Kernel modules: sata_sil, pata_acpi, ata_generic
00:13.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] IXP SB4x0 USB Host Controller [1002:4374] (rev 80)
Subsystem: Toshiba America Info Systems Device [1179:ff00]
Kernel driver in use: ohci-pci
Kernel modules: ohci_pci
00:13.1 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] IXP SB4x0 USB Host Controller [1002:4375] (rev 80)
Subsystem: Toshiba America Info Systems Device [1179:ff00]
Kernel driver in use: ohci-pci
Kernel modules: ohci_pci
00:13.2 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] IXP SB4x0 USB2 Host Controller [1002:4373] (rev 80)
Subsystem: Toshiba America Info Systems Device [1179:ff00]
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD/ATI] IXP SB4x0 SMBus Controller [1002:4372] (rev 82)
Subsystem: Toshiba America Info Systems Device [1179:ff00]
Kernel driver in use: piix4_smbus
Kernel modules: i2c_piix4
00:14.1 IDE interface [0101]: Advanced Micro Devices, Inc. [AMD/ATI] IXP SB4x0 IDE Controller [1002:4376] (rev 80)
Subsystem: Toshiba America Info Systems Device [1179:ff00]
Kernel driver in use: pata_atiixp
Kernel modules: pata_atiixp, pata_acpi, ata_generic
00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] IXP SB4x0 High Definition Audio Controller [1002:437b] (rev 01)
Subsystem: Toshiba America Info Systems Device [1179:ff00]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD/ATI] IXP SB4x0 PCI-ISA Bridge [1002:4377] (rev 80)
Subsystem: Toshiba America Info Systems Device [1179:ff00]
00:14.4 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] IXP SB4x0 PCI-PCI Bridge [1002:4371] (rev 80)
01:05.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] RC410M [Mobility Radeon Xpress 200M] [1002:5a62]
Subsystem: Toshiba America Info Systems Device [1179:ff03]
Kernel modules: radeon
02:00.0 Ethernet controller [0200]: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter (PCI-Express) [168c:001c] (rev 01)
Subsystem: Askey Computer Corp. WLL3140 (Toshiba PA3501U-1MPC) 802.11bg Wireless Mini PCIe Card [144f:7106]
Kernel driver in use: ath5k
Kernel modules: ath5k

09:00.0 FireWire (IEEE 1394) [0c00]: VIA Technologies, Inc. VT6306/7/8 [Fire II(M)] IEEE 1394 OHCI Controller [1106:3044] (rev c0)
Subsystem: Toshiba America Info Systems Device [1179:ff00]
Kernel driver in use: firewire_ohci
Kernel modules: firewire_ohci
09:04.0 CardBus bridge [0607]: ENE Technology Inc CB1410 Cardbus Controller [1524:1410] (rev 01)
Subsystem: Toshiba America Info Systems Device [1179:ff00]
Kernel driver in use: yenta_cardbus
Kernel modules: yenta_socket
09:06.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter [10ec:8139] (rev 10)
Subsystem: Toshiba America Info Systems Device [1179:ff00]
Kernel driver in use: 8139too
**Kernel modules: 8139cp, 8139too
**

Note that ath5k is the wireless driver for the built-in Atheros wireless G mini-PCIe adapter. Since I already installed b43, I want to backlist ath5k in order to have wireless N, but this results in no wireless connection. I cannot configure or set up wireless connection in Network Manager unless I undo this blacklisting. This means somehow b43 or broadcom-wl is not loaded at boot time.

PS: Previously I said this Linksys card is near the end of its life. This is wrong, because the 2 LEDs light up with other Linux distros using broadcom wl (i.e. STA).

I am having wireless connection, BUT this is due to ath5k of wireless G built-in Atheros adapter.


#rfkill list
0: phy0: Wireless LAN
        Soft blocked: **no**
        Hard blocked: **no**

Note that the Linksys PCMCIA wireless N adapter is still not lit up.

Did you actually run

sudo /usr/sbin/install_bcm43xx_firmware

Hi, taytong888

quick response,

try deleting kernel module 8139cp and see if it makes a difference

sudo rmmod 8139cp

this change will not survive a re-boot

To prevent it from being loaded at all, create a file /etc/modprobe.d/8139cp-blacklist.conf (the filename doesn’t matter, so you could use something else if you want to) with the following content:

blacklist 8139cp

Hi, taytong888

lengthier response

more information can be seen from the outputs of,

for wireless i/f

journalctl | grep ‘02:00.0’

for wired i/f

journalctl | grep ‘09:06.0’

for NetworkManager (if that’s being used)

journalctl | grep ‘NetworkManager’

(NB. depending on setup, the outputs can be very long and can take some time,
if so send the outputs to a file)
post the outputs from the last boot if necessary

my preferred method of kernel module selection for networking is via the network, wicked
gui from within yast, although wicked has not sucessfully worked, then after a cold re-boot
change back to NetworkManager if its preferred
(on this laptop, Toshiba SM60, both ipv4 and ipv6 connections are being established to the modem/router)

hth

@caf4926,

Your suggested command “sudo /usr/sbin/install_bcm43xx_firmware” installs both b43 and b43legacy firmwares, but has no effect. Same thing when I installed b43legacy-firmware and b43-fwcutter via YAST > Software Management.

@keellambert,

“sudo rmmod 8139cp” has no effects.

In both of the above, lspci -nnk returns the same screen as before.

By the way, I just notice that right after logging in and just before 13.2 loads, the screen shows the following as the last line:

[6.300168] pcmcia_socket pcmcia_socket0: cardbus cards are not supported

I am wondering if this has anything to do with the Linksys adapter not being recognized.

I may have to try a clean install.

Hi, taytong888

according to the output in post #8,
the wireless card is being recognised,
‘Kernel driver in use: ath5k’
and
the correct driver for ethernet is also correctly installed,
‘Kernel driver in use: 8139too’

has the procedure given in the following link been tried?
https://forums.opensuse.org/showthread.php/502149-Doesn-t-connect-to-Internet?p=2673245#post2673245

cheers

Hello keellambert,

I just did follow the procedure you suggested in Post#10 of your link above. After all the systemctl commands were carried out and reboot, I still have both wired and wireless connections as before. My problem is, although wireless connection is made available by ath5k of the built-in wireless G adapter, it’s NOT what I want. I want wireless N made available by b43legacy-firmware for the Linksys adapter WPC300N v1, which in a few previous openSUSE distributions were enabled by either b43 or broadcom wl firmware.

Hi, taytong888

in yast, network settings,
global options, Network Setup Method,
if Wicked Service is selected,
then in Overview, when the wlan device is selected, and then Edit,
in the Hardware tab, what can be seen in the Module Name pull-down list?

cheers

I did follow all that. Still “ath5k”!. The Linksys adapter does not show up!

:frowning:

Hi,

I discovered that /lib/firmware/brcm has bcm43xx-0.fw but lib/firmware/b43, lib/firmware/b43legacy and lib/firmware/broadcom-wl-firmwares DO NOT.

Just wondering if this is why the Linksys WPC300N v1 adapter still is not recognized in my old laptop.

Any ideas, comments or suggestions?

No. Forget about b43.
This only supports some Broadcom BCM43xxx chips.
You do not have a Broadcom device.

No idea, why you think b43legacy, b43 or wl would help you.
And this seems to have caused confusion for the ones trying to help you as well. :wink:

Just to clarify, you are talking about this, right?

02:00.0 Ethernet controller [0200]: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter (PCI-Express) [168c:001c] (rev 01)
        Subsystem: Askey Computer Corp. WLL3140 (Toshiba PA3501U-1MPC) **802.11bg Wireless Mini PCIe Card [144f:7106]
        Kernel driver in use: ath5k
        Kernel modules: ath5k**

ath5k is the (only) correct driver for this:
http://wireless.kernel.org/en/users/Drivers/ath5k

Do you have “broadcom-wl” installed? Remove it! This might prevent other things from loading correctly.

If your only problem is that you can’t get 802.11N, then it might just not be supported.

No idea “why the Linksys WPC300N v1 adapter still is not recognized in my old laptop”, but better open a new thread for this with the lspci information.
This one is already too confusing as-is I’d say…
The Linksys WPC300N does have a broadcom chip apparently, namely a “BCM4321”. You need the broadcom-wl driver for that, but not all versions are supported by wl either as it seems.

PS, just noted that you do have another thread open about that already (3 years old): BCM4321 on Linksys WPC300N V1 - Network/Internet - openSUSE Forums
You still haven’t solved it?