Hi,
After a recent update (12.3.10, I think), I can’t choose encryption method for my wireless connection and therefore can’t connect. The only option in the combo box is ‘none’. What can I do to fix this?
Please let us see
/sbin/lspci -nnk
Assume it’s a PCI device?
Thank you for your reply. Here it is:
00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM Controller [8086:0154] (rev 09)
Subsystem: Dell Device [1028:05ba]
00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port [8086:0151] (rev 09)
Kernel driver in use: pcieport
00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09)
Subsystem: Dell Device [1028:05ba]
Kernel driver in use: i915
00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04)
Subsystem: Dell Device [1028:05ba]
Kernel driver in use: xhci_hcd
00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
Subsystem: Dell Device [1028:05ba]
Kernel driver in use: mei
00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04)
Subsystem: Dell Device [1028:05ba]
Kernel driver in use: ehci_hcd
00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller [8086:1e20] (rev 04)
Subsystem: Dell Device [1028:05ba]
Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 [8086:1e10] (rev c4)
Kernel driver in use: pcieport
00:1c.1 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 [8086:1e12] (rev c4)
Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04)
Subsystem: Dell Device [1028:05ba]
Kernel driver in use: ehci_hcd
00:1f.0 ISA bridge [0601]: Intel Corporation HM76 Express Chipset LPC Controller [8086:1e59] (rev 04)
Subsystem: Dell Device [1028:05ba]
Kernel driver in use: lpc_ich
00:1f.2 SATA controller [0106]: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] [8086:1e03] (rev 04)
Subsystem: Dell Device [1028:05ba]
Kernel driver in use: ahci
00:1f.3 SMBus [0c05]: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller [8086:1e22] (rev 04)
Subsystem: Dell Device [1028:05ba]
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI Mars [Radeon HD 8500/8700M Series] [1002:6601]
Subsystem: Dell Device [1028:05ba]
07:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller [10ec:8136] (rev 05)
Subsystem: Dell Device [1028:05ba]
Kernel driver in use: r8169
08:00.0 Network controller [0280]: Broadcom Corporation BCM43142 802.11b/g/n [14e4:4365] (rev 01)
Subsystem: Dell Wireless 1704 802.11n + BT 4.0 [1028:0016]
I completely forgot I had to install this driver manually, sorry 
I just have to remember how I did it and do it again 
It would’ve been really neat if openSuse told me that I have no working wireless card
On this page: b43 - Linux Wireless
Your device (14e4:4365) BCM43142
Suggests ‘wl’
That driver is in Packman, but presumably you do have Packman.
Let me see
rpm -qi | grep broadcom
and
zypper lr -d
and
rpm -qa | grep kernel
On 06/24/2013 07:36 AM, zaregis wrote:
>
> I completely forgot I had to install this driver manually, sorry I
> just have to remember how I did it and do it again
>
> It would’ve been really neat if openSuse told me that I have no working
> wireless card
How could the distro handle a case where there is no Linux driver in the kernel?
The only driver for your device is the Broadcom wl driver. The Packman repo
should have one for your current kernel. As that driver is closed source, the
“open” in openSUSE prohibits that driver from being distributed with normal updates.
Be aware that your wireless will break every time the kernel is updated. That is
one of the downsides of using an out-of-kernel driver.
kernel-xen-devel-3.7.10-1.16.1.x86_64
kernel-syms-3.7.10-1.11.1.x86_64
kernel-desktop-devel-3.7.10-1.11.1.x86_64
kernel-devel-3.7.10-1.11.1.noarch
kernel-source-3.7.10-1.11.1.noarch
kernel-devel-3.7.10-1.16.1.noarch
kernel-desktop-3.7.10-1.16.1.x86_64
kernel-xen-devel-3.7.10-1.11.1.x86_64
kernel-firmware-20130114git-1.2.1.noarch
kernel-default-devel-3.7.10-1.16.1.x86_64
kernel-syms-3.7.10-1.16.1.x86_64
kernel-default-devel-3.7.10-1.11.1.x86_64
kernel-default-3.7.10-1.16.1.x86_64
kernel-desktop-3.7.10-1.11.1.x86_64
kernel-desktop-devel-3.7.10-1.16.1.x86_64
I don’t know exactly what this last list shows, but my kernel is 3.7.10-1.16-desktop.
As you can see above, I added Packman. I installed the driver from there, following instructions you gave in another thread, but the driver does not work. Maybe I didn’t remove the old one properly (just deleted /lib/modules/3.7.10-1.16-desktop/extra/wl.ko)?
kernel-desktop-3.7.10-1.16.1.x86_64
kernel-default-3.7.10-1.16.1.x86_64
kernel-desktop-3.7.10-1.11.1.x86_64
Do you have a boot option for the older desktop kernel? Does the wireless work there?
Let us see the result now of
rpm -qa | grep broadcom
broadcom-wl-kmp-desktop-5.100.82.112_k3.7.10_1.16-11.4.x86_64
broadcom-wl-5.100.82.112-11.4.x86_64
I don’t think I have a boot option for the older kernel, but I’d rather keep using the latest anyway. If the driver in Packman won’t work, I’ll just keep using the manually installed one. Hopefully, I wont forget to reinstall it the next time I update the kernel 
In the grub2 menu, select “Advanced options”. That should give you a choice of kernels.
That way, if you forgot to update the wireless driver, you can still boot to the older kernel and update the driver so that future boots with the newer kernel will work. It avoids having to switch to ethernet to do that driver update.
OK
So now lets see
/sbin/lspci -nnk
08:00.0 Network controller [0280]: Broadcom Corporation BCM43142 802.11b/g/n [14e4:4365] (rev 01)
Subsystem: Dell Wireless 1704 802.11n + BT 4.0 [1028:0016]
That means no driver is loaded for the card, right?
Correct, no driver.
But it should be there.
But I’m wondering what exactly you did previously, because you didn’t have Packman repo added at the time did you?
No, I didn’t. I added Packman, installed broadcom-wl and broadcom-wl-kmp-desktop, deleted the old wl.ko and rebooted, that’s all. I also tried removing the wl.ko first, rebooting, installing from Packman etc.
EDIT: Now I’m thinking maybe you asked me how I installed the original driver. I ran make, copied the file to /lib/modules/mykernel/extras/wl and ran modprobe wl. Still works if the Packman driver isn’t installed…
So can you remember what you did previously? Because if you didn’t use the driver built from Packman, did you build it yourself? You do seem to have the necessary build packages in place, at least from what I can see.
Perhaps you remember something like this
802.11 Linux STA driver | Broadcom
But first just try
sudo /sbin/modprobe -rv wl
sudo /sbin/modprobe -v wl
wait for a minute, does the wireless come to life?
First, thank you for your patience.
See the edit in my previous post, please.
The modprobe commands seem to work and load the driver, but it looks like it’s not in use.
When I ran the first command, I got this output: rmmod /lib/modules/3.7.10-1.16-desktop/updates/wl.ko
And after the second, I got this: insmod /lib/modules/3.7.10-1.16-desktop/updates/wl.ko
No complaints, errors…
Then I ran:
lsmod | grep wl
and got this:
wl 2573568 0
Which, I guess, means the wl module is loaded, but it isn’t used by anything.
Keep diggin’ I have to crash…later
Ok, there’s a difference in outputs of modprobe -v wl when loading the two drivers, but I have no idea what it means
With manually built driver, output of modprobe -v wl is:
insmod /lib/modules/3.7.10-1.16-desktop/kernel/net/wireless/cfg80211.ko
insmod /lib/modules/3.7.10-1.16-desktop/extra/wl/wl.ko
And with Packman driver, the output is only the second line:
insmod /lib/modules/3.7.10-1.16-desktop/updates/wl.ko