Hello Stan,
On Sun, Oct 21, 2018 at 09:37:19AM -0700, stan wrote:
You could compare the journal messages from the older firmware when
it succeeded with those from the failing firmware to see if there is any
difference. For that matter, compare the successful old load with the
failing old load. But I don't think it is failing to find the firmware
files that exist.
The AMD firmware is loaded in drivers/gpu/drm/amd/amdgpu/ampgpu_device.c
In that source, there are two other firmware blobs treated the same as
the raven: vega10 and vega12. Do you find those in the same place as
the raven firmware blob? Do they have the same permissions?
[...chomp...chomp...chomp...]
Because there is a specific path for raven, I'm surprised that
the
older firmware actually worked. The kernel looks for firmware with
raven in the name, and I didn't see a fallback, though I could have
missed it because everything is done via pointers to structs, and I
didn't get into that level of detail.
Thank you for taking the time to look at the source. But I think there was a
miscommunication. I have been using the raven ridge firmware successfully before. It
failed after I tried the ROCm packages.
Finally, could there be leftovers from the Rocm code causing
problems?
That was it, see Allan's post. It was stale dracut conf files that pointed to a
different kernel firmware directory that's the culprit.
Thanks again for taking the time to investigate :)
Cheers,
--
Suvayu
Open source is the future. It sets us free.