Hi Stan, Sorry for the late response, I wasn't monitoring the list. I actually thought of what you mentioned in the other post, the firmware making a persistent change in some register. I really don't know how I could investigate that :-| On Wed, Oct 17, 2018 at 09:18:18AM -0700, stan wrote: > On Wed, 17 Oct 2018 09:26:01 +0530 > Suvayu Ali <fatkasuvayu+linux@xxxxxxxxx> wrote: > > > I have already tried both rebuilding the initrd, and reinstall the > > kernel to no avail :( > > I don't know if firmware loading is done similarly to a kernel module. > If it is, you could try modprobe. I have tried modprobe, lsmod, etc, and I see the amdgpu module is loaded. I don't know how to check something for firmware. I guess the issue is, the module loads, but it fails to find and load the binary blob (firmware) that it needs (as seen in the journal). So the picture is consistent, I just can't figure out why it fails to find the firmware files. Does Fedora use a firmware loader? Maybe I can hack around and invoke it in "verbose mode". If it is something internal to the kernel, I doubt something like that would be possible. > The other thing is to do an > rpm -q --filesbypkg [package name] > for each of the packages in question, to see if there is a difference > in what they installed. A difference should point you to the file(s) > that are causing the issue. I have tried rpm --verify, no luck. I will try your suggestion and see if that points to something. My plan of last resort is to do a fresh install when F29 is released, but understanding and solving this issue would be far more satisfying :). Thanks again, -- Suvayu Open source is the future. It sets us free. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
