Re: Changes in drm ports
- In reply to: Emmanuel Vadot : "Re: Changes in drm ports"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 03 May 2022 15:26:51 UTC
>>> I'm using radeonkms on DELL studio 15 (very old machine). >>> Although it works well on drm-current-kmod/drm-devel-kmod with >>> gpu-firmware-kmod, it can't work on drm-54-kmod/drm-510-kmod with >>> gpu-firmware-radeon-kmod. It froze after showing 'Mounting filesystems'. >> [snip] >> >> gpu-firmware-radeon-kmod-aruba-20211014 >> ^^^^^ >> "Aruba" is the default firmware and probably that's not what you want. >> You need to find your own chipset and build correct flavor(s) for you. >> >> Do "grep 'could not load firmware image' /var/log/messages". For >> example, you will see something like this: >> >> May 2 21:48:35 xxxxxx kernel: drmn0: could not load firmware image >> 'radeon/TAHITI_uvd.bin' >> May 2 21:48:35 xxxxxx kernel: drmn0: could not load firmware image >> 'radeon/TAHITI_vce.bin' >> >> This means you need need "tahiti" firmware and you will have to build >> and install it. Note you may need multiple flavors. For example, I had >> to build two flavors for the above GPU, i.e., aruba and tahiti. >> >> May 3 08:46:38 xxxxxx kernel: drmn0: successfully loaded firmware image >> 'radeon/ARUBA_pfp.bin' >> May 3 08:46:38 xxxxxx kernel: drmn0: successfully loaded firmware image >> 'radeon/ARUBA_me.bin' >> May 3 08:46:38 xxxxxx kernel: drmn0: successfully loaded firmware image >> 'radeon/ARUBA_rlc.bin' >> May 3 08:46:38 xxxxxx kernel: drmn0: successfully loaded firmware image >> 'radeon/TAHITI_uvd.bin' >> May 3 08:46:38 xxxxxx kernel: drmn0: successfully loaded firmware image >> 'radeon/TAHITI_vce.bin' Thank you very much. After installing graphics/gpu-firmware-kmod meta ports, drm-(54|510)-kmod works fine on DELL studio 15. As I don't have time right now, I'll find firmware I need later. I think I probably need cedar and cypress. -- Masachika ISHIZUKA