[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#917272: marked as done (Kernel module failed to load on 4.19 kernel.)

Your message dated Fri, 18 Jan 2019 19:27:40 +0000
with message-id <e886ce5439fa17670a0b18ff28c07c608fbe00dd.camel@decadent.org.uk>
and subject line Re: Bug#916816: firmware-amd-graphics: AMDGPU lacks recent firmwares fro 4.19 based kernel, not usable.
has caused the Debian Bug report #916816,
regarding Kernel module failed to load on 4.19 kernel.
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 owner@bugs.debian.org
immediately.)


-- 
916816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916816
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Package: firmware-amd-graphics
Version: 20180825+dfsg-1

For some reason, from 4.19.0 onward, the kernel refuses to load the AMD modules. The screen defaults to 80*25 text mode and "startx" does not work.
Here is what I have tried:
linux-image-4.19.0-trunk-amd64-unsigned/now 4.19.5-1~exp1 amd64: WORKS
linux-image-4.19.0-1-amd64-unsigned/unstable 4.19.12-1 amd64: DOES NOT WORK
linux-image-4.20.0-trunk-amd64-unsigned/experimental 4.20-1~exp1 amd64: DOES NOT WORK ("dmesg" log attached)
It does not look like the kernel itself is the problem (as 4.19-trunk works but 4.19 does not), so the problem is the firmware.
--
"And in the naked light, I saw ten thousand people, maybe more. People \
talking without speaking, people hearing without listening. People writ\
ing songs that voices never shared, no one dared disturb the sound of s\
ilence." --MA Bo'yong
-----BEGIN PGP SIGNATURE-----
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAGBQJcIg5HAAoJENi1YDlFXXQfqRAH/3NGXqLXLCWWOEAkRkHn
RXCYbILbBYqY9G1PTadc4ycce828Z9uwRytKkQ3C7rvulIjcYA6SD5Zv7Yl6
g9yhb0+ZW6gedIV86bGvQpwgY2NWyvDtm1FL+GUrEcrNMT9qJD1W4uQ2s+P9
YZCdEWcvBaj/mYuqLzHG9yA/2Kfv7BFjULbhq3+PDfBKiOGZdG3ufHd6NEP5
m7QN/PXV2F6K6BPQ/uGragb0/QHFUE6pyeCynh4rbDixMwe5Fb2mfRcDNTDg
J8GUH8J0CkLaqADVZK6zzrDiAy+MqlVK3zTSx3EBK6bDc8S9CNOgvXt34XRh
KwceEhcEsZpqKguUw3qlsQg=
=cy56
-----END PGP SIGNATURE-----

Attachment: dmesg.0
Description: Binary data

Attachment: dmesg.0.sig
Description: PGP signature

Attachment: publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys

Attachment: publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature


--- End Message ---
--- Begin Message --- 
Version: 20190114-1

On Fri, 2019-01-18 at 19:02 +0100, Axel Regnat wrote:
> This bug should be fixed with firmware-nonfree 20190114-1.
[...]

Right, but I forgot to close this.

Ben.

-- 
Ben Hutchings
Always try to do things in chronological order;
it's less confusing that way.

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: