Bug#970011: linux: missing build dependency on kernel-wedge in stage1 build
Source: linux Version: 5.8.7-1 Severity: important User: helm...@debian.org Usertags: rebootstrap Hi, I'm run into a bootstrap failure caused by linux: https://jenkins.debian.net/job/rebootstrap_hppa_gcc10/9/ | dh_prep | dh_prep: warning: All requested packages have been excluded (e.g. via a Build-Profile or due to architecture restrictions). | kernel-wedge install-files 5.8.0-1 | bash: kernel-wedge: command not found | make[2]: Leaving directory '/tmp/buildd/linux/linux-5.8.7' | make[2]: *** [debian/rules.real:573: install-udeb_hppa] Error 127 | make[1]: Leaving directory '/tmp/buildd/linux/linux-5.8.7' | make[1]: *** [debian/rules.gen:89: binary-arch_hppa] Error 2 | make: *** [debian/rules:43: binary-arch] Error 2 | dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 What we see here is that kernel-wedge is not found while cross building linux with the stage1 profile for hppa. This seems to be a recent thing. It used to work earlier. I'm not sure yet, how many other architectures are affected. A kernel-wedge dependency is there, but it is tagged . That used to be true. Do note that the failing target is install-udeb_hppa and that in a stage1 build, we don't produce any udebs. So in reality it seems more likely that the whole target should be skipped, but isn't. The target seems to be pulled in by debian/rules.gen, but that's about where I stopped understanding the logic. Can I ask you to look into this? In the mean time, I guess installing kernel-wedge is a viable workaround. While looking into linux' build profiles I was wondering whether we still need stage1. linux gained a number of functional profiles including pkg.linux.nokernel, pkg.linux.notools and pkg.linux.nosource. Their combination does not exactly reproduce stage1, but it is close. I'm wondering whether we can simply switch any stage1 user to using the combination of these three and be done. I haven't tried whether this actually works yet, but I believe it is feasible and you get the idea. Helmut
Bug#968567: linux-image-4.19.0-10-amd64: kernel failure when writing on a GFS2 partition
Hi, I can confirm the existence of this CPU soft-lock bug with gfs2. I won't worry about reproducing the kernel bug message, but I have done a bit of digging and if I revert the following commit, added in the 4.19.130 release then this fixes issue for me. https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.19.y=c91cffd0fd010c06d67f3a9a528b858ce28c60fb Note that the problem is still present in the latest upstream release in the 4.19 series (4.19.144) I've reported this bug in the kernel bugzilla, referenced here: https://bugzilla.kernel.org/show_bug.cgi?id=209217 Cheers, Daniel Craig
Processed: closing 941597
Processing commands for cont...@bugs.debian.org: > close 941597 5.7.17-1 Bug #941597 [src:linux] linux: [dtb] Raspberry Pi 3B+: does not shut down (regression against buster) Marked as fixed in versions linux/5.7.17-1. Bug #941597 [src:linux] linux: [dtb] Raspberry Pi 3B+: does not shut down (regression against buster) Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 941597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941597 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: linux-image-4.5.0-trunk-armmp-lpae: raspberry pi 2: smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped
Processing commands for cont...@bugs.debian.org: > fixed 820622 4.19.132-1 Bug #820622 [src:linux] linux-image-4.5.0-trunk-armmp-lpae: raspberry pi 2: smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped Marked as fixed in versions linux/4.19.132-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 820622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820622 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#820622: linux-image-4.5.0-trunk-armmp-lpae: raspberry pi 2: smsc95xx 1-1.1:1.0 eth0: kevent 2 may have been dropped
fixed 820622 4.19.132-1 thanks Hello, I have not seen this message appear in my RPi2, using stock Debian kernels starting at 4.19 (even a bit before that, I think). I do not use the LPAE kernel, as I understand it does not make much sense in the RPi2 (sold only with 1GB RAM, and not expandable), so probably this specific kernel should be tested, but I believe the bug can be now safely closed. signature.asc Description: PGP signature
Processed: closing 878332
Processing commands for cont...@bugs.debian.org: > close 878332 Bug #878332 [src:linux] linux > 4.11: Raspberry pi 2 hangs at boot with lpae kernel Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 878332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878332 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#941597: linux: [dtb] Raspberry Pi 3B+: does not shut down (regression against buster)
fixed 941597 5.7.17-1 thanks I have some RPi3B+ using the arm64 Linuxkernel at version 5.7 (currently in testing), and they both shutdown and reboot reliably. I believe this bug can now be closed. signature.asc Description: PGP signature
Processed: Re: linux > 4.11: Raspberry pi 2 hangs at boot with lpae kernel
Processing commands for cont...@bugs.debian.org: > fixed 878332 4.19.132-1 Bug #878332 [src:linux] linux > 4.11: Raspberry pi 2 hangs at boot with lpae kernel Marked as fixed in versions linux/4.19.132-1. > fixed 878332 5.7.17-1 Bug #878332 [src:linux] linux > 4.11: Raspberry pi 2 hangs at boot with lpae kernel Marked as fixed in versions linux/5.7.17-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 878332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878332 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#878332: linux > 4.11: Raspberry pi 2 hangs at boot with lpae kernel
fixed 878332 4.19.132-1 fixed 878332 5.7.17-1 thanks Hello, This bug is no longer present in kernels shipped in Debian stable / testing / unstable. Do note, though, that the Raspberry Pi 2 is sold with 1GB RAM only and cannot be upgraded, and thus has no use for LPAE, we have used only regular linux-image-armmp kernels (and have no reason to suppose -lpae is needed). signature.asc Description: PGP signature
Bug#969979: linux-image-4.19.0-6-amd64: checkarray on degraded RAID array crashes the system
On Wed, 2020-09-09 at 20:34 +0200, Seb wrote: > Hi, > > > > > Package: src:linux > > > Version: 4.19.67-2+deb10u2 > > [...] > > This version is 10 months old; please upgrade and try again as the > > bug may have been fixed already. > > OK, I will, but I do not know how to properly upgrade the kernel on a > Debain-stable system (which is up-to-date with respect to "apt upgrade"). > Could you enlighten me and say which kernel version I should try? You should install "linux-image-amd64", if it's not already installed. Also, your APT sources should include both stable and security suites, like this: deb http://deb.debian.org/debian/ buster main deb http://security.debian.org/ buster/updates main If you only enable the security suite you will be missing important updates. Ben. -- Ben Hutchings Life would be so much easier if we could look at the source code. signature.asc Description: This is a digitally signed message part
Bug#969961: firmware-amd-graphics: amdgpu requires firmware installed even it already has been installed
>* What led up to the situation? > None, just boot up. >* What exactly did you do (or not do) that was effective (or > ineffective)? > 1. Go to tty2, login. Enter "sudo modprobe -r amdgpu" > 2. Then, Enter "sudo modprobe -i amdgpu" >* What was the outcome of this action? > None graphics shows up..Startx failed too. >* What outcome did you expect instead? > No error shows and graphics shows up. Have you tried newer amd microcode (as far as I remember Debian has an 2019 outdated one)? also linux 5.8 in unstable would be worth a try. thanks. -- maks
Processed: Re: Bug#966218: marked as done (firmware: failed to load iwl-debug-yoyo.bin (-2))
Processing control commands:
> reopen -1
Bug #966218 {Done: Salvatore Bonaccorso } [src:linux]
firmware: failed to load iwl-debug-yoyo.bin (-2)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions linux/5.8.7-1.
> found -1 5.8.7-1
Bug #966218 [src:linux] firmware: failed to load iwl-debug-yoyo.bin (-2)
Marked as found in versions linux/5.8.7-1.
--
966218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#966218: marked as done (firmware: failed to load iwl-debug-yoyo.bin (-2))
control: reopen -1 control: found -1 5.8.7-1 $ uname -a Linux foo 5.8.0-1-amd64 #1 SMP Debian 5.8.7-1 (2020-09-05) x86_64 GNU/Linux $ journalctl -k -g iwl-debug-yoyo -- Logs begin at Mon 2020-08-03 07:03:27 EDT, end at Wed 2020-09-09 16:08:47 EDT. -- Sep 09 15:53:32 foo kernel: iwlwifi :03:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
Bug#969979: linux-image-4.19.0-6-amd64: checkarray on degraded RAID array crashes the system
On Wed, Sep 09, 2020 at 08:34:16PM +0200, Seb wrote: > > > > Package: src:linux > > > Version: 4.19.67-2+deb10u2 > > [...] > > This version is 10 months old; please upgrade and try again as the bug > > may have been fixed already. > > OK, I will, but I do not know how to properly upgrade the kernel on a > Debain-stable system (which is up-to-date with respect to "apt upgrade"). > Could you enlighten me and say which kernel version I should try? How about: apt-get dist-upgrade What is its output? of course reboot after upgrade. best, -- maks
Bug#969979: linux-image-4.19.0-6-amd64: checkarray on degraded RAID array crashes the system
Hi, Package: src:linux Version: 4.19.67-2+deb10u2 [...] This version is 10 months old; please upgrade and try again as the bug may have been fixed already. OK, I will, but I do not know how to properly upgrade the kernel on a Debain-stable system (which is up-to-date with respect to "apt upgrade"). Could you enlighten me and say which kernel version I should try? Regards, Sébastien.
firmware-nonfree_20200817-1~bpo10+1_source.changes ACCEPTED into buster-backports
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 10 Sep 2020 02:47:14 +0900 Source: firmware-nonfree Architecture: source Version: 20200817-1~bpo10+1 Distribution: buster-backports Urgency: medium Maintainer: Debian Kernel Team Changed-By: Roger Shimizu Closes: 969000 Changes: firmware-nonfree (20200817-1~bpo10+1) buster-backports; urgency=medium . * Team upload. * Rebuild for buster-backports. . firmware-nonfree (20200817-1) unstable; urgency=medium . [maximilian attems] * New upstream version: - linux-firmware: update NXP SDSD-8997 firmware image - amdgpu: update navi10 firmware for 20.30 - amdgpu: update navi14 firmware for 20.30 - amdgpu: update picasso firmware for 20.30 - amdgpu: update raven firmware for 20.30 - amdgpu: update raven2 firmware for 20.30 - amdgpu: update renoir firmware for 20.30 - amdgpu: update vega10 firmware for 20.30 - amdgpu: update vega12 firmware for 20.30 - amdgpu: update vega20 firmware for 20.30 - i915: Add HuC firwmare v7.5.0 for TGL - i915: Add DMC firmware 2.08 for TGL - i915: Add DMC firmware 2.02 for RKL - rtl_bt: Update RTL8822C BT UART firmware to 0x0599_8A4F - brcm: Add brcmfmac43455-sdio.raspberrypi,3-model-a-plus.txt symlink * add rtw88 RTL8821C firmware (closes: #969000) * Update to linux-support 5.7.0-3. . [ Aníbal Limón ] * qcom-soc: Add venus 5.2/5.4 firmware Checksums-Sha1: 3e78794990fabc8bc931aae57595c0ad98882453 4003 firmware-nonfree_20200817-1~bpo10+1.dsc f3e267ce26f704a80366ccd4c9c74df94367fb77 784188 firmware-nonfree_20200817-1~bpo10+1.debian.tar.xz 4d8f751be9a7d1665af97bc4584d41105c2a9427 13581 firmware-nonfree_20200817-1~bpo10+1_amd64.buildinfo Checksums-Sha256: fd2e550a968680217a3b63e4bbe1ed08a5c828fc8f3c540bbf6d6e529a2dabfa 4003 firmware-nonfree_20200817-1~bpo10+1.dsc aa3f2d871eee020358dc2be846396f61d9f7dab7cb25e10df7c00bc20f131ff5 784188 firmware-nonfree_20200817-1~bpo10+1.debian.tar.xz ef56ade49924364a900f8a3e033b9a3b9361b105938ee4284b69c35fedc526ee 13581 firmware-nonfree_20200817-1~bpo10+1_amd64.buildinfo Files: e1af73d7798bede3338f76a24627c2d7 4003 non-free/kernel optional firmware-nonfree_20200817-1~bpo10+1.dsc cd9b49e04b2f221d6d46feda4a52bf45 784188 non-free/kernel optional firmware-nonfree_20200817-1~bpo10+1.debian.tar.xz 2c00cdd33dc7f210a7130c02d74048c7 13581 non-free/kernel optional firmware-nonfree_20200817-1~bpo10+1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEECjKtvoA5m+cWOFnspHhrDacDNKgFAl9ZGEgQHHJvc2hAZGVi aWFuLm9yZwAKCRCkeGsNpwM0qPElD/42pGf0MBqSrpfNoDE2PNwxXqxzOHHOpXSM yYrSclY2WS3GB8zme0VWL/UiTcSR+TZT0WSkPGWOKP7Qlv4KwMS9vxZV6/SItxJI ukKdgjz5vBew9eJ2cb08F623IbuCObvwQ+oMTTkGWkhrnKa849CipsDTAYaRM67q A2t0EE8bNwhicncjzg9noty0BbiEBjRXUAndiuto9YVVEsrDbIb7cSqGYuCssOz8 X2E3b9mH2IH3d0n52jySXE42LnBKT4+vkNSOvsJdMz80hESHr0HEbcomPiIEGzss kAcWoUAAInh8sc1dffEquuG9Fral+F1NwQXv4jCHwj9TSXn1BQe5eMegG0gkWKxz Rjpb2mAxNRdgdW8d/bJHslRZyiFld2WjnC4/opqoH9B4SzEjrHjN5enFJpTzE+Uh X/u8Vu/XrV759uCYtdH+oduxTzAqWl5LpkHTJPudjNRqI+2CkHD4+hfbMXUe1TMW A3ijpXT72olnwu6rKCknWVNhpKYuQtq72boWO3rk1zXJV4nIVlkf5W45kSpo/WDd NeapzAEeTjNDovNC6u6AeIUdFSoyhiqIjfL8HT9crfG0febx62klNoXEF+U/dKRR R6ISJ3waRMDRA/mjkNCQ9Wmps776TTgxU0WZRlR8G6yzLfzHv5mbGW6aam978HXo w6ziVwBDNA== =cre+ -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of firmware-nonfree_20200817-1~bpo10+1_source.changes
firmware-nonfree_20200817-1~bpo10+1_source.changes uploaded successfully to localhost along with the files: firmware-nonfree_20200817-1~bpo10+1.dsc firmware-nonfree_20200817-1~bpo10+1.debian.tar.xz firmware-nonfree_20200817-1~bpo10+1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
Processed: Re: Bug#969979: linux-image-4.19.0-6-amd64: checkarray on degraded RAID array crashes the system
Processing control commands: > tag -1 moreinfo Bug #969979 [src:linux] linux-image-4.19.0-6-amd64: checkarray on degraded RAID array crashes the system Added tag(s) moreinfo. -- 969979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969979 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969979: linux-image-4.19.0-6-amd64: checkarray on degraded RAID array crashes the system
Control: tag -1 moreinfo On Wed, 2020-09-09 at 18:03 +0200, Seb wrote: > Package: src:linux > Version: 4.19.67-2+deb10u2 [...] This version is 10 months old; please upgrade and try again as the bug may have been fixed already. Ben. -- Ben Hutchings Time is nature's way of making sure that everything doesn't happen at once. signature.asc Description: This is a digitally signed message part
Processed: severity of 969979 is important
Processing commands for cont...@bugs.debian.org: > severity 969979 important Bug #969979 [src:linux] linux-image-4.19.0-6-amd64: checkarray on degraded RAID array crashes the system Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 969979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969979 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: support for RTL8723DE in kernel 5.8
Hi, On Wed, Sep 09, 2020 at 02:14:38PM +0200, Toon Pepermans wrote: > I've seen that the current Debian Sid kernel, package > linux-image-5.8.0-1-amd64 (5.8.7-1), does not have the files > /lib/modules/5.8.0-1-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723d.ko > and rtw88_8723de.ko > Is this a mistake or intentional? It is probably just that nobody asked about it (btw, ideally with a bugreport). We can enable it on the next upload, and just pushed the config change to the packaging repository. Regards, Salvatore
Bug#969979: linux-image-4.19.0-6-amd64: checkarray on degraded RAID array crashes the system
Package: src:linux Version: 4.19.67-2+deb10u2 Severity: critical Justification: breaks the whole system Dear Maintainer, This machine runs a six-disks RAID10 array with mdadm. This morning, cat /sys/block/md2/md/mismatch_cnt reported 128, indicating errors on the array. This may be linked to a hard drive that failed a few weeks ago and has been replaced since. I do not know when the count started exceeding zero. To correct the problem, I ran /usr/share/mdadm/checkarray /dev/md2 as explained in /usr/share/doc/mdadm/README.checkarray . Before the check was complete, the system crashed. Here is the kernel oops message from /var/log/syslog: Sep 9 16:13:13 ns3358511 freshclam[786]: Wed Sep 9 16:13:13 2020 -> Testing database: '/var/lib/clamav/tmp.009ee/clamav-1c0b168938d0b213620d993d9646fef3.tmp-daily.cld' ... Sep 9 16:13:13 ns3358511 kernel: [151276.866290] BUG: unable to handle kernel NULL pointer dereference at 0008 Sep 9 16:13:13 ns3358511 kernel: [151276.866297] PGD 0 P4D 0 Sep 9 16:13:13 ns3358511 kernel: [151276.866301] Oops: [#1] SMP PTI Sep 9 16:13:13 ns3358511 kernel: [151276.866305] CPU: 0 PID: 5665 Comm: md2_resync Not tainted 4.19.0-6-amd64 #1 Debian 4.19.67-2+deb10u2 Sep 9 16:13:13 ns3358511 kernel: [151276.866307] Hardware name: System manufacturer System Product Name/P8H77-I, BIOS 1001 02/01/2013 Sep 9 16:13:13 ns3358511 kernel: [151276.866314] RIP: 0010:r10buf_pool_alloc+0x338/0x430 [raid10] Sep 9 16:13:13 ns3358511 kernel: [151276.866316] Code: 20 48 98 48 89 c2 48 c1 e2 04 48 01 d0 4c 8d 2c c6 49 8d 5d 08 49 81 c5 88 00 00 00 eb 09 48 83 c3 08 49 39 dd 74 c5 48 8b 3b <48> 8b 47 08 48 8d 50 ff a8 01 48 0f 45 fa 0f 1f 44 00 00 f0 ff 4f Sep 9 16:13:13 ns3358511 kernel: [151276.866320] RSP: 0018:a4bdc2173b08 EFLAGS: 00010202 Sep 9 16:13:13 ns3358511 kernel: [151276.866323] RAX: dac9003b RBX: 904c27de5528 RCX: 0010 Sep 9 16:13:13 ns3358511 kernel: [151276.866325] RDX: dac9003b8887 RSI: 904c27de5400 RDI: Sep 9 16:13:13 ns3358511 kernel: [151276.866327] RBP: 0001 R08: dac9003b8848 R09: 904d1fdee000 Sep 9 16:13:13 ns3358511 kernel: [151276.866329] R10: 904d1fdee6d8 R11: dac900c6e188 R12: 904a20c469c0 Sep 9 16:13:13 ns3358511 kernel: [151276.866332] R13: 904c27de5598 R14: R15: 0002 Sep 9 16:13:13 ns3358511 kernel: [151276.866335] FS: () GS:904d0f80() knlGS: Sep 9 16:13:13 ns3358511 kernel: [151276.866338] CS: 0010 DS: ES: CR0: 80050033 Sep 9 16:13:13 ns3358511 kernel: [151276.866340] CR2: 0008 CR3: 0002c6a0a001 CR4: 001606f0 Sep 9 16:13:13 ns3358511 kernel: [151276.866343] Call Trace: Sep 9 16:13:13 ns3358511 kernel: [151276.866351] ? blk_attempt_plug_merge+0xee/0xf0 Sep 9 16:13:13 ns3358511 kernel: [151276.866355] ? finish_wait+0x80/0x80 Sep 9 16:13:13 ns3358511 kernel: [151276.866359] mempool_alloc+0x67/0x190 Sep 9 16:13:13 ns3358511 kernel: [151276.866364] raid10_alloc_init_r10buf+0x23/0xa0 [raid10] Sep 9 16:13:13 ns3358511 kernel: [151276.866368] raid10_sync_request+0x1e4/0x1e60 [raid10] Sep 9 16:13:13 ns3358511 kernel: [151276.866372] ? try_to_del_timer_sync+0x4d/0x80 Sep 9 16:13:13 ns3358511 kernel: [151276.866376] ? cpumask_next+0x16/0x20 Sep 9 16:13:13 ns3358511 kernel: [151276.866383] ? is_mddev_idle+0xcc/0x12a [md_mod] Sep 9 16:13:13 ns3358511 kernel: [151276.866389] md_do_sync.cold.86+0x3f4/0x911 [md_mod] Sep 9 16:13:13 ns3358511 kernel: [151276.866392] ? finish_wait+0x80/0x80 Sep 9 16:13:13 ns3358511 kernel: [151276.866397] ? __switch_to_asm+0x35/0x70 Sep 9 16:13:13 ns3358511 kernel: [151276.866402] ? md_rdev_init+0xb0/0xb0 [md_mod] Sep 9 16:13:13 ns3358511 kernel: [151276.866407] md_thread+0x94/0x150 [md_mod] Sep 9 16:13:13 ns3358511 kernel: [151276.866412] kthread+0x112/0x130 Sep 9 16:13:13 ns3358511 kernel: [151276.866415] ? kthread_bind+0x30/0x30 Sep 9 16:13:13 ns3358511 kernel: [151276.866418] ret_from_fork+0x35/0x40 Sep 9 16:13:13 ns3358511 kernel: [151276.866421] Modules linked in: ipt_REJECT nf_reject_ipv4 xt_multiport nft_compat nft_counter nf_tables nfnetlink jfs i915 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel drm_kms_helper kvm drm mei_me eeepc_wmi asus_wmi mei i2c_algo_bit sparse_keymap irqbypass rfkill pcc_cpufreq iTCO_wdt iTCO_vendor_support ie31200_edac sg wmi_bmof evdev crct10dif_pclmul crc32_pclmul video pcspkr ghash_clmulni_intel wmi button intel_cstate intel_uncore intel_rapl_perf loop ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 fscrypto ecb raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c crc32c_generic raid0 multipath linear raid10 raid1 md_mod sd_mod crc32c_intel ahci libahci libata aesni_intel xhci_pci i2c_i801 xhci_hcd aes_x86_64 crypto_simd cryptd glue_helper
support for RTL8723DE in kernel 5.8
I've seen that the current Debian Sid kernel, package linux-image-5.8.0-1-amd64 (5.8.7-1), does not have the files /lib/modules/5.8.0-1-amd64/kernel/drivers/net/wireless/realtek/rtw88/rtw88_8723d.ko and rtw88_8723de.ko Is this a mistake or intentional? Thanks, Toon Pepermans
Processed: limit source to linux, tagging 943337
Processing commands for cont...@bugs.debian.org: > limit source linux Limiting to bugs with field 'source' containing at least one of 'linux' Limit currently set to 'source':'linux' > tags 943337 + pending Bug #943337 [src:linux] linux-image-5.3.0-1-amd64: Keyboard driver for SPI connected MacBooks not included Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 943337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943337 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969961: firmware-amd-graphics: amdgpu requires firmware installed even it already has been installed
Package: firmware-amd-graphics Version: 20200817-1 Severity: important Dear Maintainer, * What led up to the situation? None, just boot up. * What exactly did you do (or not do) that was effective (or ineffective)? 1. Go to tty2, login. Enter "sudo modprobe -r amdgpu" 2. Then, Enter "sudo modprobe -i amdgpu" * What was the outcome of this action? None graphics shows up..Startx failed too. * What outcome did you expect instead? No error shows and graphics shows up. My inxi -xx -GSC shows: System:Host: XQQY-debian Kernel: 5.7.0-3-amd64 x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: KDE Plasma 5.17.5 tk: Qt 5.14.2 wm: kwin_x11 dm: SDDM Distro: Debian GNU/Linux bullseye/sid CPU: Info: 6-Core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP arch: Zen 2 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 94790 Speed: 3950 MHz min/max: 2200/3950 MHz Core speeds (MHz): 1: 3949 2: 3938 3: 3949 4: 3949 5: 3950 6: 3949 7: 3950 8: 3949 9: 3940 10: 3933 11: 3951 12: 3949 Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] vendor: XFX Pine driver: amdgpu v: kernel bus ID: 08:00.0 chip ID: 1002:731f Display: x11 server: X.Org 1.20.8 compositor: kwin_x11 driver: amdgpu FAILED: ati unloaded: fbdev,modesetting,radeon,vesa resolution: 1920x1080 s-dpi: 96 OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.37.0 5.7.0-3-amd64 LLVM 10.0.1) v: 4.6 Mesa 20.1.7 direct render: Yes I have upload my log of this problem to https://pastebin.com/1h1cT4wB Also, I have marked what happen when I type "sudo modprobe -r amdgpu" On line 1592 and "sudo modprobe -i amdgpu" on line 1638 -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-3-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE=zh_CN:zh_TW Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled firmware-amd-graphics depends on no packages. firmware-amd-graphics recommends no packages. Versions of packages firmware-amd-graphics suggests: ii initramfs-tools 0.137 -- no debconf information
