Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #64435

Bug#928631:

From Diederik de Haas <didi.debian@cknow.org>
Newsgroups linux.debian.bugs.dist, linux.debian.kernel
Subject Bug#928631:
Date 2019-07-14 23:30 +0200
Message-ID <yjUed-2xk-3@gated-at.bofh.it> (permalink)
References <xVhH3-1oo-1@gated-at.bofh.it> <yjSFr-1tx-1@gated-at.bofh.it> <xVhH3-1oo-1@gated-at.bofh.it> <yjSFr-1tx-1@gated-at.bofh.it>
Organization Connecting Knowledge

Cross-posted to 2 groups.

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

Hi,

On zondag 14 juli 2019 21:38:14 CEST Hillel Lubman wrote:
> 20190502-1 is already outdated, since amdgpu firmware had some updates
> upstream:
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
> /log/amdgpu
> 
> Does this problem still occur if you use latest upstream firmware?

I first updated my local git repo to 3d1e5537dbd8ac36c01fc33e7bf525e5c8e4b708.

I then upgraded back to the latest package versions and rebooted and 
encountered the same issue as reported.

Started SystemRescueCD and chrooted into my system (just like before), but I 
now copied the vega10* files from the amdgpu dir to /lib/firmware/amdgpu/ and 
rebooted again.
And now it succeeded :D
Thanks a lot for the hint!

> By the way, it works well for me (Ryzen 7 2700X / Vega 56), but I'm running
> kernel 5.2.1 in Debian testing.

I didn't upgrade my kernel, so I'm still on 4.19.0-5-amd64 (4.19.37-5) in 
Debian Sid.
So the only thing that was needed for me was updating the firmware files to the 
latest version.

Cheers,
  Diederik

Back to linux.debian.kernel | Previous | Next | Find similar | Unroll thread


Thread

Bug#928631:  Diederik de Haas <didi.debian@cknow.org> - 2019-07-14 23:30 +0200

csiph-web