Bug#1042818: firmware-amd-graphics: Random display freezes on certain AMD GPUs
Package: firmware-amd-graphics Version: 20230515-3 Tags: fixed-upstream, upstream Followup-For: Bug #1042818 X-Debbugs-Cc: onit...@gmail.com linux-firmware 20230804 has been released and contains the mentioned reverts for amdgpu firmware. This is not a permanent fix of the underlying problem, but it will at least allow systems to function normally again. Please update as soon as possible. This should also fix #1040185, but for that issue, a backport to bookworm may be required. Thanks. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (300, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.4.0-1-amd64 (SMP w/24 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB 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.142 -- no debconf information
Bug#1043024: amdgpu: When updating I get a "Possible missing firmware /lib/firmware/amdgpu/modules" (Sapphire Nitro R9 390)
Package: firmware-amd-graphics Version: 20230515-3 Followup-For: Bug #1043024 X-Debbugs-Cc: onit...@gmail.com Can you post which firmware files are missing exactly? dmesg should give you all the needed information. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (300, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.4.0-1-amd64 (SMP w/24 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB 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.142 -- no debconf information
Bug#1042818: firmware-amd-graphics: Random display freezes on certain AMD GPUs due to "Error waiting for DMUB idle: status=3"
Package: firmware-amd-graphics Version: 20230515-3 Severity: important Tags: upstream Forwarded: https://gitlab.freedesktop.org/drm/amd/-/issues/1887 X-Debbugs-Cc: onit...@gmail.com Dear Maintainer, The current AMDGPU firmware in Debian has compatibility issues with 6.3+ kernels. These errors manifest themselves with kernel messages like these: [ +0.226777] [drm:dc_dmub_srv_wait_idle [amdgpu]] *ERROR* Error waiting for DMUB idle: status=3 [ +4.020959] [drm:dc_dmub_setup_subvp_dmub_command [amdgpu]] *ERROR* Error waiting for DMUB idle: status=3 Furthermore, they cause sudden display freezes and even GPU lock-ups that require power-cycling the system. It's not clear why these problems occur, but they might have to do with certain optimizations that AMD had to do to reduce power consumption at idle on RX 7000 series GPUs. See https://gitlab.freedesktop.org/drm/amd/-/issues/2315 for more information about this issue. As a temporary workaround, it's possible to avoid the power management optimizations by reducing the overall pixel clock rate or creating modelines with a longer blanking delay, as long as the display supports this. For example, reducing the refresh rate from 120Hz to 60Hz has helped in one case for me. Another workaround is to disable optimizations in the affected firmware with the kernel option drm.vblankoffdelay=0 . As stated in https://gitlab.freedesktop.org/drm/amd/-/issues/1887#note_1993615 , the problematic firmware changes were reverted in https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=d3f66064cf43bd7338a79174bd0ff60c4ecbdf6d , and there have been several amdgpu firmware commits since. Please update linux-firmware as soon a release containing the revert or a permanent fix is available. Thanks. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (300, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.4.0-1-amd64 (SMP w/24 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB 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.142 -- no debconf information
Bug#925424: linux-image-amd64: Build the Silead touchscreen controller kernel driver
Hi Debian kernel team, It's been 4 years, and the Debian kernel is still lacking out-of-the-box support for Silead touchscreen controllers and corresponding DMI quirks. Can you please enable these options? CONFIG_TOUCHSCREEN_SILEAD=m CONFIG_TOUCHSCREEN_DMI=y Thank you very much.
Bug#1031534: firmware-linux-nonfree: Package removed from sid and bookworm
Package: firmware-linux-nonfree Version: 20221214-3 Severity: grave Justification: renders package unusable X-Debbugs-Cc: onit...@gmail.com Dear Maintainer, With the recent upgrade to version 20230210 (or 20230117 on testing), the package has vanished from the apt cache of two of my bookworm/sid installations. apt policy reports that firmware-linux-nonfree is stuck at version 20221214-3 on my systems, with the only available version being the one that is locally installed. According to https://tracker.debian.org/pkg/firmware-nonfree everything seems to be fine, but I simply don't see any available upgrades. Opening https://packages.debian.org/source/unstable/firmware-nonfree reports: "Package not available in this suite." Were these packages renamed, or what exactly is going on here? -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (900, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (300, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-3-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages firmware-linux-nonfree depends on: ii firmware-amd-graphics 20221214-3 ii firmware-misc-nonfree 20221214-3 Versions of packages firmware-linux-nonfree recommends: ii amd64-microcode 3.20220411.1 ii intel-microcode 3.20221108.1 firmware-linux-nonfree suggests no packages. -- no debconf information
Re: Bug#1012547: linux: disable user namespaces per default
Seems I'm not the only one who's quite concerned about the ongoing security impact of user namspaces, as the recent/current discussion about some LSM patches for 6.1 shows: 99% of all code does NOT WANT the user namespace thing, and it's been a big new attack surface for the kernel getting things subtly wrong. It's still a shame to see that Debian intentionally sacrifices the security of *all* users just for the needs of very few. I'd very much like to see where Linus gets his "99%" from. Sounds a like like a "I'm not using it, so 99% of all users aren't using it". Podman certainly supports and uses them, when run as non-root. [1] [2] The whole point of user namespaces is to *reduce* the attack surface, not increase it. If you don't have a comparable feature, you need to give your applications more power, increasing the risk of system compromise overall. For example: Running containers or container runtimes as root. That the implementation has serious issues like this one is sad, but it is more of an indication that the feature wasn't quite ready for general consumption yet, not that it's a bad feature per se. And how would you build a user base and discover issues without making the feature available to the general public? [1] https://medium.com/techbull/what-is-user-namespace-and-podmans-rootless-containers-fc4c292c6bad [2] https://opensource.com/article/18/12/podman-and-user-namespaces
Bug#1009618: Firmware "beige-goby*", for Radeon RX6500XT, missing from package
Package: firmware-amd-graphics Version: 20210818-1 Severity: important Followup-For: Bug #1009618 X-Debbugs-Cc: onit...@gmail.com A couple of other firmware files have been missing for a while too: W: Possible missing firmware /lib/firmware/amdgpu/yellow_carp_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/vangogh_gpu_info.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/ip_discovery.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/beige_goby_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/beige_goby_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/yellow_carp_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/yellow_carp_toc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/yellow_carp_asd.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_sos.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish2_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish2_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish2_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish2_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish2_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish2_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/yellow_carp_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/yellow_carp_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/yellow_carp_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/yellow_carp_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/yellow_carp_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/yellow_carp_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/beige_goby_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/beige_goby_mec2.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/beige_goby_mec.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/beige_goby_me.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/beige_goby_pfp.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/beige_goby_ce.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish2_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish2_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/yellow_carp_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/beige_goby_sdma.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/yellow_carp_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/beige_goby_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/beige_goby_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/yellow_carp_dmcub.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/beige_goby_dmcub.bin for module amdgpu Most of them can be found in https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
Bug#931930: Workaround ? [Re: firmware-misc-nonfree: Please, include i915/icl_dmc_ver1_07.bin]
> Does someone has a woraround ? The Debian source package doesn't have > the right version of the files. You can pull the current version from Salsa and build the .deb yourself: https://salsa.debian.org/kernel-team/firmware-nonfree Just be aware that you have to manually replace your locally built package when the package is uploaded to the Debian servers, as it will have the same version. > BTW, do the maintainer(s) have acknowledged the problem ? I'm not sure... Maybe raise the severity of the issue a bit?
Bug#956221: firmware-misc-nonfree: missing firmware i915/{icl_dmc_ver1_09,tgl_dmc_ver2_04,{skl,bxt,kbl,glk,cml,icl,ehl,tgl…
I believe this bug has already been reported here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931930 Duplicate?
Bug#940633: linux-image-5.2.0-2-amd64: UI microfreezes with with i915 driver
Package: src:linux Version: 5.2.9-2 Severity: important Tags: patch upstream Dear Maintainer, Linux 5.2 kernels contain a bug that causes short graphics freezes when using the i915 driver on certain Intel GPUs. The issue was originally reported here: https://bugzilla.kernel.org/show_bug.cgi?id=204183 A patch for 5.2 is available here: https://patchwork.freedesktop.org/series/63774/#rev4 This patch will likely be included in kernel 5.3, but 5.2 and possibly older kernels are also affected. Please consider adding this patch to 5.2 until it arrives in a stable kernel. As a temporary workaround, it's possible to disable PSR (Panel Self Refresh) by adding i915.enable_psr=0 to the kernel command line. There may be higher power consumption or other consequences. Thanks! (Package-specific info truncated because it's not relevant to the problem) -- Package-specific info: ** Version: Linux version 5.2.0-2-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-21)) #1 SMP Debian 5.2.9-2 (2019-08-21) ** Command line: N/A ** Kernel log: N/A ** Model information N/A ** Loaded modules: i915 ** PCI devices: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) ** USB devices: N/A -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (900, 'testing'), (300, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-5.2.0-2-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.135 ii kmod26-2 ii linux-base 4.6 Versions of packages linux-image-5.2.0-2-amd64 recommends: ii apparmor 2.13.3-5 ii firmware-linux-free 3.4 Versions of packages linux-image-5.2.0-2-amd64 suggests: pn debian-kernel-handbook ii grub-efi-amd64 2.04-3 pn linux-doc-5.2 Versions of packages linux-image-5.2.0-2-amd64 is related to: ii firmware-amd-graphics 20190717-2 pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv ii firmware-iwlwifi 20190717-2 pn firmware-libertas ii firmware-linux-nonfree20190717-2 ii firmware-misc-nonfree 20190717-2 pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-realtek pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor
Bug#929424: initramfs-tools: update-initramfs should not store temporary files on /boot
Package: initramfs-tools Version: 0.133 Severity: normal Dear Maintainer, On systems with a small /boot volume, update-initramfs will frequently fail with pigz: abort: write error on (No space left on device) This hasn't been an issue so far, with a 200MB boot volume and a maximum of 2 kernels kept. But now, I have encountered it on several systems that need a separate /boot partition, on 2 different CPU architectures. After the new initramfs is generated, it will fit on the small /boot without problems. This leads me to the conclusion that update-initramfs stores temporary files on the volumes - I don't think it should do that. Please make sure that uncompressed images, temporary files, etc. are stored on a volume that does not have dire size constraints, such as /tmp or similar. Thank you. -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 52M May 2 17:16 /boot/initrd.img-4.19.0-4-amd64 -rw-r--r-- 1 root root 52M May 23 10:38 /boot/initrd.img-4.19.0-5-amd64 -- /proc/cmdline BOOT_IMAGE=/vmlinuz-4.19.0-4-amd64 root=/dev/mapper/vg--packie-lv--debian2 ro quiet -- resume RESUME=/dev/mapper/vg--packie-lv--swap -- /proc/filesystems btrfs ext3 ext2 ext4 fuseblk xfs jfs msdos vfat ntfs minix hfs hfsplus qnx4 ufs -- lsmod Module Size Used by vboxpci28672 0 vboxnetadp 28672 0 vboxnetflt 32768 0 vboxdrv 491520 3 vboxpci,vboxnetadp,vboxnetflt ufs86016 0 qnx4 16384 0 hfsplus 114688 0 hfs69632 0 minix 40960 0 ntfs 110592 0 vfat 24576 0 msdos 20480 0 fat86016 2 msdos,vfat jfs 208896 0 xfs 1458176 0 cpuid 16384 0 ctr16384 0 ccm20480 0 rfcomm 86016 16 fuse 122880 3 ipt_MASQUERADE 16384 1 nf_conntrack_netlink49152 0 xfrm_user 45056 1 xfrm_algo 16384 1 xfrm_user nft_counter16384 15 nft_chain_nat_ipv4 16384 4 nf_nat_ipv416384 2 ipt_MASQUERADE,nft_chain_nat_ipv4 xt_addrtype16384 1 nft_compat 20480 4 nf_tables 143360 45 nft_compat,nft_chain_nat_ipv4,nft_counter nfnetlink 16384 4 nft_compat,nf_conntrack_netlink,nf_tables xt_conntrack 16384 1 nf_nat 36864 1 nf_nat_ipv4 nf_conntrack 163840 5 xt_conntrack,nf_nat,ipt_MASQUERADE,nf_nat_ipv4,nf_conntrack_netlink nf_defrag_ipv6 20480 1 nf_conntrack nf_defrag_ipv4 16384 1 nf_conntrack br_netfilter 24576 0 bridge188416 1 br_netfilter stp16384 1 bridge llc16384 2 bridge,stp pci_stub 16384 1 overlay 126976 0 bnep 24576 2 binfmt_misc20480 1 hid_jabra 16384 0 snd_usb_audio 258048 2 snd_usbmidi_lib36864 1 snd_usb_audio ext4 733184 2 hid_generic16384 0 snd_rawmidi40960 1 snd_usbmidi_lib mbcache16384 1 ext4 snd_seq_device 16384 1 snd_rawmidi jbd2 122880 1 ext4 fscrypto 32768 1 ext4 ecb16384 0 btusb 53248 0 btrtl 16384 1 btusb btbcm 16384 1 btusb btintel24576 1 btusb usbhid 57344 0 bluetooth 643072 41 btrtl,btintel,btbcm,bnep,btusb,rfcomm hid 139264 3 usbhid,hid_generic,hid_jabra drbg 28672 1 uvcvideo 118784 0 ansi_cprng 16384 0 videobuf2_vmalloc 16384 1 uvcvideo videobuf2_memops 16384 1 videobuf2_vmalloc arc4 16384 2 videobuf2_v4l2 28672 1 uvcvideo ecdh_generic 24576 1 bluetooth crc16 16384 2 bluetooth,ext4 videobuf2_common 53248 2 videobuf2_v4l2,uvcvideo intel_rapl 24576 0 x86_pkg_temp_thermal16384 0 videodev 212992 3 videobuf2_v4l2,uvcvideo,videobuf2_common intel_powerclamp 16384 0 mei_wdt16384 0 media 45056 2 videodev,uvcvideo coretemp 16384 0 kvm_intel 241664 0 iwlmvm294912 0 mac80211 823296 1 iwlmvm kvm 729088 1 kvm_intel snd_hda_codec_realtek 118784 1 irqbypass 16384 1 kvm crct10dif_pclmul 16384 0 snd_hda_codec_generic86016 1 snd_hda_codec_realtek crc32_pclmul 16384 0 snd_hda_codec_hdmi 57344 1 iwlwifi 241664 1 iwlmvm ghash_clmulni_intel16384 0
Bug#927252: linux-4.19.0-4-arm64: Enable SPI CAN drivers for ARM/AARCH64
Package: src:linux Version: 4.19.28-2 Severity: wishlist Tags: patch Dear Maintainer, Please consider enabling the SPI-attached CAN bus drivers in the Debian kernel. They are useful on ARM SoCs with an SPI bus, such as the Raspberry Pi. The Raspbian kernel package already includes these drivers, and they do no harm on platforms that don't use them. To load these drivers, a suitable DeviceTree config is required. Thank you! Here's a patch for .config: --- a/.config 2019-03-15 02:16:04.0 + +++ b/.config 2019-04-16 21:46:33.124431597 + @@ -1696,8 +1699,8 @@ # # CAN SPI interfaces # -# CONFIG_CAN_HI311X is not set -# CONFIG_CAN_MCP251X is not set +CONFIG_CAN_HI311X=m +CONFIG_CAN_MCP251X=m # # CAN USB interfaces -- Package-specific info: ** Version: Linux version 4.19.0-4-arm64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-2)) #1 SMP Debian 4.19.28-2 (2019-03-15) ** Command line: bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 dma.dmachans=0x7f35 bcm2709.boardrev=0xa020d3 bcm2709.serial=0xffbcac2c bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=29 bcm2709.disk_led_active_low=0 smsc95xx.macaddr=B8:27:EB:BC:AC:2C vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 console=tty0 root=/dev/mmcblk0p2 rw elevator=deadline fsck.repair=yes net.ifnames=0 cma=256M rootwait ** Tainted: C (1024) * Module from drivers/staging has been loaded. ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information Device Tree model: Raspberry Pi 3 Model B Plus Rev 1.3 ** Loaded modules: at24 i2c_dev ip6t_REJECT nf_reject_ipv6 nft_counter ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_comment nft_compat nf_tables nfnetlink nls_ascii nls_cp437 vfat fat btsdio bluetooth vc4 drbg snd_soc_core ansi_cprng ecdh_generic snd_pcm_dmaengine snd_pcm microchip brcmfmac snd_timer snd soundcore brcmutil lan78xx cec cfg80211 drm_kms_helper of_mdio fixed_phy drm libphy rfkill vchiq(C) pwm_bcm2835 bcm2835_thermal bcm2835_rng rng_core bcm2835_wdt leds_gpio ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb aes_arm64 dwc2 udc_core usbcore sdhci_iproc sdhci_pltfm sdhci usb_common bcm2835 i2c_bcm2835 phy_generic ** PCI devices: not available ** USB devices: not available -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: arm64 (aarch64) Kernel: Linux 4.19.0-4-arm64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_CRAP Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-4.19.0-4-arm64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.133 ii kmod26-1 ii linux-base 4.6 Versions of packages linux-image-4.19.0-4-arm64 recommends: ii apparmor 2.13.2-10 ii firmware-linux-free 3.4 ii irqbalance 1.5.0-3 Versions of packages linux-image-4.19.0-4-arm64 suggests: pn debian-kernel-handbook pn linux-doc-4.19 Versions of packages linux-image-4.19.0-4-arm64 is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x ii firmware-brcm8021120190114-1 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas pn firmware-linux-nonfree pn firmware-misc-nonfree pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-realtek pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor -- no debconf information
Bug#895131: linux-perf: Add libopencsd support to perf
Sorry, I did not see the full scope of this bug. Removing the forwarded tag. John: Feel free to add the upstream bug if you report a new one for the sparc64 issue. Thanks!
Bug#895131: linux-perf: Add libopencsd support to perf
> I guess we could do this. I just find it odd that a profiling library for > ARM is a build dependency on all architectures. > > I'll look into fixing libopencsd. The library seems to also include a decoder for (debug?) traces, which may be useful on other archs as well. Anyway, I reported the issue upstream: https://github.com/Linaro/OpenCSD/issues/16
Bug#895131: linux-perf: Add libopencsd support to perf
> This change made src:linux BD-Uninstallable on sparc64 [1] as > the package libopencsd doesn't build there [2]. > > Since this library is ARM-specific anyway, wouldn't it make > more sense to have this build-dependency on ARM targets only? libopencsd does build fine on other architectures, though. According to this[1], the fix should be simply replacing -fpic with -fPIC. [1] https://lists.debian.org/debian-sparc/2014/07/msg00037.html
Bug#833551: firmware-ipw2x00 in stretch contains the wrong firmware for ipw2200 in kernel 4.6
Package: firmware-ipw2x00 Version: 20160110-1 Severity: important Tags: newcomer Dear Maintainer, The firmware-ipw2x00 package in Debian stretch contains firmware for Intel Wireless Pro 2100/2200 devices, but the firmware does not match what the driver in kernel 4.6 requires. The package has version 3.0 from upstream, but version 3.1 is required. Without the the correct firmware, the driver will report lots of ipw2200: Firmware error detected. Restarting. errors, and the wireless card is barely usable, if at all. Manually installing the firmware from upstream resolves this problem. Please update the package so it has the correct firmware. Thank you. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 4.6.0-1-686-pae (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages firmware-ipw2x00 depends on: ii debconf [debconf-2.0] 1.5.59 firmware-ipw2x00 recommends no packages. Versions of packages firmware-ipw2x00 suggests: ii initramfs-tools 0.125 -- debconf information: firmware-ipw2x00/license/error: * firmware-ipw2x00/license/accepted: true
Bug#689753: Still an issue
I think this bug should be reopened and not closed as WONTFIX. The suggested workaround with /etc/kernel-img.conf doesn't seem to work, and implementing some extra logic to support filesystems without hardlinks shouldn't be too difficult. Why not just create a copy instead if hardlinking fails? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54deaae8.5020...@gmail.com
Bug#597897: Current status of alsa-firmware?
Is there an update on the packaging status of alsa-firmware, or integration into linux-firmware-nonfree? This RFP was reported more than 3 years ago, yet firmware images for certain audio devices are still missing in Debian. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/539b3f19.6040...@gmail.com
