Hello,
I am running Tumbleweed 64 bit, kernel 4.14.9-1-default. Wireless card is Rosewill RNX-AC1900PCI, a clone of TP-Link TC-9E wireless adapter.
lspci -nnk
gives:
02:00.0 Network controller [0280]: Broadcom Limited BCM4360 802.11ac Wireless Network Adapter [14e4:43a0] (rev 03)
Subsystem: Broadcom Limited Device [14e4:0619]
Kernel driver in use: wl
Kernel modules: bcma, wl
This evening I ran “zypper dup” and the kernel was updated to 4.14.11-1.5-default, and kernel-firmware was updated automatically to version 20180104-1.1. After reboot, there’s no wireless connection at all! I cannot install software packages or updates.
At the previous kernel level, YAST Software Management shows that kernel-devel 4.14.11-1.5-default is available for installation. Its description says to help with building kernel modules. If I were to install this kernel-devel then boot into the new kernel 4.14.11-1.5, will the system shows available wireless connections?
I would very much appreciate your suggestions and comments.
Please post:
uname -a
zypper se -si broad kernel
zypper lr -d
Hello Sauerland,
Thank you for your reply. I am booting into kernel 4.14.9-1-default, thus there’s Internet connection to write a reply. Here goes:
uname -r
4.14.9-1-default
zypper se -si broad kernel
S | Name | Type | Version | Arch | Repository
---+--------------------------------+---------+-----------------------------+--------+----------------------
i+ | broadcom-wl | package | 6.30.223.271-9.24 | x86_64 | (System Packages)
i | broadcom-wl-kmp-default | package | 6.30.223.271_k4.14.9_1-9.24 | x86_64 | (System Packages)
i+ | kernel-default | package | 4.14.9-1.5 | x86_64 | (System Packages)
i+ | kernel-default | package | 4.14.11-1.5 | x86_64 | Main Repository (OSS)
i+ | kernel-firmware | package | 20180104-1.1 | noarch | Main Repository (OSS)
i+ | mobile-broadband-provider-info | package | 20170310-1.2 | noarch | Main Repository (OSS)
zypper lr -d
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service
--+----------------------------------+----------------------------+---------+-----------+---------+----------+--------+---------------------------------------------------------------------+--------
1 | download.opensuse.org-non-oss | Main Repository (NON-OSS) | Yes | (r ) Yes | Yes | 99 | yast2 | http://download.opensuse.org/tumbleweed/repo/non-oss/ |
2 | download.opensuse.org-oss | Main Repository (OSS) | Yes | (r ) Yes | Yes | 99 | yast2 | http://download.opensuse.org/tumbleweed/repo/oss/ |
3 | download.opensuse.org-tumbleweed | Main Update Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/tumbleweed/ |
4 | openSUSE-20150519-0 | openSUSE-20150519-0 | Yes | ( p) Yes | No | 99 | yast2 | cd:///?devices=/dev/disk/by-id/ata-HL-DT-STDVD-RAM_GH22NS30 |
5 | openSUSE_Tumbleweed | openSUSE_Tumbleweed | Yes | (r ) Yes | Yes | 99 | rpm-md | http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/ |
6 | repo-debug | openSUSE-Tumbleweed-Debug | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/tumbleweed/repo/oss/ |
7 | repo-source | openSUSE-Tumbleweed-Source | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/source/tumbleweed/repo/oss/
The kmp for wl is still for the previous kernel. Reboot, select the previous kernel through Advanced Options and you’re back online. Then wait for an update from the broadcom-wl packages by the Packman packagers.
Some background: the recent intel cpu flaws have forced the devs to urgently patch the kernel and some other packages. The Packman guys haven’t had the time yet to rebuild their packages.
Try:
zypper dup
broadcom-wl is there since today night, you have only forgotten to update…
http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/Essentials/x86_64/
Hello Sauerland and Knurpht,
Thank you both for your help. I am back on line using the new kernel after “zypper dup” which upgrades the 2 packages “broadcom-wl” and “broadcom-wl-kmp-default”:
uname -r
4.14.11-1-default
rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
How do I mark this thread as SOLVED?
Have a very nice day! Cheers!
