#1116494 upgrade-reports: The upgrade to linux kernel 6.12.48+deb13-amd64 appears to be missing a patch for the Broadcom wirless. #1116494
- Package:
- upgrade-reports
- Source:
- upgrade-reports
- Submitter:
- Bud Pennington
- Date:
- 2025-09-29 10:54:02 UTC
- Severity:
- normal
- Tags:
My previous release is: <linux 6.12.43+deb13-amd64>
I am upgrading to: <linux 6.12.48+deb13-amd64>
Archive date: <Timestamp, available as project/trace/ftp-master.debian.org
on your mirror or .disk/info on your CD/DVD set>
Upgrade date: <Date and time of the upgrade>
uname -a before upgrade: Linux racoon 6.12.43+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.43-1 (2025-08-27) x86_64 GNU/Linux
uname -a after upgrade: <The result of running uname -a on a shell prompt>
Method: sudo apt update, sudo apt upgrade
Contents of /etc/apt/sources.list:
# Modernized from /etc/apt/sources.list
Types: deb deb-src
URIs: http://deb.debian.org/debian/
Suites: trixie
Components: main non-free-firmware contrib non-free
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
# Modernized from /etc/apt/sources.list
Types: deb deb-src
URIs: http://security.debian.org/debian-security/
Suites: trixie-security
Components: main non-free-firmware contrib non-free
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
# Modernized from /etc/apt/sources.list
Types: deb deb-src
URIs: http://deb.debian.org/debian/
Suites: trixie-updates
Components: main non-free-firmware contrib non-free
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
- Were there any non-Debian packages installed before the upgrade? No
- Was the system pre-update a 'pure' system only containing packages
from the previous release? If not, which packages were not from that
release?
- Did any packages fail to upgrade?
- Were there any problems with the system after upgrading? Wireless not working.
Further Comments/Problems: Previously when the kernel was updated the update would pause and apply a patch. on this update a message appeared stating a module was missing and it wa skipping that step.
Please attach the output of "COLUMNS=200 dpkg -l" (or "env COLUMNS ...",
depending on your shell) from before and after the upgrade so that we
know what packages were installed on your system.
Hi Your report right now contains too little information that we can really act on. A couple of questions: - Can you please provide the upgrade log for apt and dpkg so we see which packages were involved and in particular if we are talking about a dkms module failing to build. check /var/log/apt/term.log* and /var/log/dpkg.log* for the given upgrade. - Please provide as well the list of installed packages, though the first item here would be helpful. - Please provide full kernel log after the update, ideally for both before the kernel update and reboot and as well for the booted kernel after the update. Regards, Salvatore
Hi I've attached the information. I'm not certain what you mean by including the log from before the update. I've been booting up by selecting 6.12.43. I've included the results from booting up 6.12.43 and 6.12.48. There are two lines in the term.log which I think point to the problem Checking the installed list the headers for 6.12.48 is not installed. I am not certain what other packages are needed and what is needed to correct this. Bud
Hi, So it looks you do not have linux-headers-amd64 package installed, the metapackage puling in the latest version of the headers in sync with the installed (metapackage) linux-image-amd64. Due to this the OOT module was built for 6.12.43 based version (for which you have the headers installed) but not for the 6.12.48 one. Install thus the linux-headers-amd64 package which should resolve your issue to get the OOT module built with dkms as well for 6.12.48. Regards, Salvatore
Hi That solved the problem Bud
Hi Bud, Perfect, glad to hear that. Closing the bug accordingly. Regards, Salvatore
Hi Can I be removed from this mailing list please?