This error still exist in latest Debian Stable kernel
Linux ci547 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2 (2019-08-28) x86_64
GNU/Linux
The error I encountered was only slightly different, instead of deb9u2, I
got it on deb9u3:
Unable to correct missing packages.
E: Failed to fetch
http://security.debian.org/debian-security/pool/updates/main/l/linux/linux-libc-dev_4.9.168-1+deb9u3_amd64.deb
404 Not Found
The solution I found was
Package: firmware-iwlwifi
Version: 20190717-2
Followup-For: Bug #934781
I did some further digging - in my case, at least, the problem seems to
be triggered by some relatively recent kernel change. I combed through
the system journal for the last few months, and the problem first starts
appearing
After doing some research online, I was able to find people experiencing
the same issues across other distros with the very same NIC on 5.x kernels:
https://bugzilla.redhat.com/show_bug.cgi?id=1709671 (Fedora)
https://bbs.archlinux.org/viewtopic.php?pid=1844324#p1844324 (Arch)
Playing with the
Package: firmware-amd-graphics
Version: 20190717-2
Can you include firmware files for the AMD Navi10 card in to the
firmware-amd-graphics package?
https://people.freedesktop.org/~agd5f/radeon_ucode/navi10/
The Linux kernel 5.3 has support for the Navi10 card. The Oibaf ppa
Mesa master bionic
Package: src:linux
Version: 5.2.9-2
Severity: important
Dear Maintainer,
I've updated kernel from 4.19 to 5.2 and kernel stopped accepting modules
signed with MOK key.
I have secure boot enabled on my system and enrolled generated MOK key. I use
some out-of-tree modules that use DKMS. In the
Hi,
Kernel 5.2.0-2 with device_tree from kernel 4.19 works:
armhfCard arm64Card
4.19.0-5:
Rpi2b Success NotPossible32bitCpu
Rpi3b Success Success
Rpi3b+ Success Success
5.2.0-2 with device_tree from kernel 4.19:
Rpi2b Success*1) NotPossible32bitCpu
Rpi3b
7 matches
Mail list logo
