[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#934724: marked as done (bugs.debian.org: Kernel Upgrade to 5.2.0-2 Appears to Break WiFi Using Broadcom BCM4352 Adapter)

Your message dated Sat, 17 Aug 2019 15:50:03 +0900
with message-id <CAEQ9gEkzSTQ5ebo3y=UFwufHMd9LwLQp5zP3D=dN0OmQKBpC9w@mail.gmail.com>
and subject line Re: Bug#934724: Kernel Upgrade to 5.2.0-2 Appears to Break WiFi Using Broadcom BCM4352 Adapter
has caused the Debian Bug report #934724,
regarding bugs.debian.org: Kernel Upgrade to 5.2.0-2 Appears to Break WiFi Using Broadcom BCM4352 Adapter
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
934724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934724
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-headers-5.2.0-2-common:amd64 (5.2.7-1, automatic), linux-image-5.2.0-2-amd64:amd64 (5.2.7-1, automatic), linux-headers-5.2.0-2-amd64:amd64 (5.2.7-1, automatic), linux-kbuild-5.2:amd64 (5.2.7-1, automatic)
Severity: important

Dear Maintainer,

Kernel was upgraded to 5.2.0-2 on 08/09/2019.  I booted into my Debian Unstable partition today and WiFi was not working.  I received no notification that wireless networks were available and left mouse clicking on the network manager applet showed no options for wireless.  Booting into kernels 4.19.0-5 or 4.19.0-4 results in working WiFi.

I've checked kernel.log and I'm not seeing anything that stands out.  I've checked syslog and I found the following, although I don't know if it's an issue:

Aug 13 17:58:39 debian-unstable NetworkManager[691]: <info>  [1565733519.5033] NetworkManager (version 1.20.0) is starting... (for the first time)
Aug 13 17:58:39 debian-unstable NetworkManager[691]: <info>  [1565733519.5034] Read config: /etc/NetworkManager/NetworkManager.conf (lib: no-mac-addr-change.conf)
Aug 13 17:58:39 debian-unstable NetworkManager[691]: <warn>  [1565733519.5034] config: unknown key 'wifi.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'
Aug 13 17:58:39 debian-unstable NetworkManager[691]: <warn>  [1565733519.5034] config: unknown key 'ethernet.cloned-mac-address' in section [device-mac-addr-change-wifi] of file '/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled



--- End Message ---
--- Begin Message --- 
On Sat, Aug 17, 2019 at 10:49 AM Kurt Meyer <yahweh19114@hailmail.net> wrote:
>
> You can close this.  There is no bug.  Evidently, the post install script either didn't, or failed to, update the kernel to include the wireless module.  Steps I took to resolve the issue:

Yes, the problem is gone, but it's resolved by new version
6.30.223.271-11 of broadcom-sta.
You can track it by:
- https://bugs.debian.org/928754

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

--- End Message ---
Reply to: