Your message dated Tue, 22 Sep 2026 16:30:31 +0200 (CEST)
with message-id <[email protected]>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #1028987,
regarding linux-image-amd64: Does not build with rtlwifi
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 [email protected]
immediately.)
--
1028987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028987
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: linux-image-amd64
Version: 6.1.0-1
Severity: normal
X-Debbugs-Cc: [email protected]
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Upgrading linux-image/linux-headers on Debian Sid with rtlwifi.
* What exactly did you do (or not do) that was effective (or
ineffective)?
sudo apt upgrade. Then after it failed, I've been running sudo apt install -f
to get it to retry after trying to fix.
* What was the outcome of this action?
The build fails (sudo apt install linux-image-amd64 fails). First, I got:
Deprecated feature: REMAKE_INITRD
(/var/lib/dkms/rtlwifi-new/0.6/source/dkms.conf)
So I tried just removing that line from the dkms.conf file. Here is the log in
/var/lib/dkms/rtlwifi-new/0.6/build/make.log after that:
DKMS make.log for rtlwifi-new-0.6 for kernel 6.1.0-1-amd64 (x86_64)
Sun Jan 15 02:14:08 PM CST 2023
make: Entering directory '/usr/src/linux-headers-6.1.0-1-amd64'
ERROR: Kernel configuration is invalid.
include/generated/autoconf.h or include/config/auto.conf are missing.
Run 'make oldconfig && make prepare' on kernel src to fix it.
make: *** [/usr/src/linux-headers-6.1.0-1-common/Makefile:817:
include/config/auto.conf] Error 1
make: Leaving directory '/usr/src/linux-headers-6.1.0-1-amd64'
I tried just following the instructions in the error. But "make oldconfig"
from that directory gives me:
GEN Makefile
/usr/src/linux-headers-6.1.0-1-common/scripts/Makefile.build:44:
/usr/src/linux-headers-6.1.0-1-common/scripts/basic/Makefile: No such file or
directory
make[1]: *** No rule to make target
'/usr/src/linux-headers-6.1.0-1-common/scripts/basic/Makefile'. Stop.
make: *** [/usr/src/linux-headers-6.1.0-1-common/Makefile:644: scripts_basic]
Error 2
* What outcome did you expect instead?
The package to install.
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (990, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.0.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages linux-image-amd64 depends on:
ih linux-image-6.1.0-1-amd64 6.1.4-1
linux-image-amd64 recommends no packages.
linux-image-amd64 suggests no packages.
--- End Message ---
--- Begin Message ---
Hi
This bug was filed for a (very) old kernel or the bug is old itself
without resolution. Maybe it was for a feature enablement which nobody
acted on. We are sorry we were not able to timely deal with this issue.
There are many open bugs for the src:linux package and thus we are
closing older bugs where it's unclear if they still occur in newer
versions and are still relevant to the reporter. For an overview see:
https://bugs.debian.org/src:linux .
If you can reproduce your issue with
- the current version in unstable/testing
- the latest kernel from backports
or, if it was a feature addition/wishlist and still consider it
relevant, then:
Please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.
Please try to provide as much fresh details including kernel logs where
relevant. In particular were an issue is coupled with specific hardware we
might ask you to do additional debugging on your side as the owner of the
hardware.
Regards,
Salvatore
--- End Message ---
