Date: Tue, 3 May 2022 15:45:27 +0200 From: Emmanuel Vadot <manu@bidouilliste.com> To: Jung-uk Kim <jkim@FreeBSD.org> Cc: Masachika ISHIZUKA <ish@amail.plala.or.jp>, x11@freebsd.org Subject: Re: Changes in drm ports Message-ID: <20220503154527.ae90d1d70a151f8bb24b8d69@bidouilliste.com> In-Reply-To: <816e5347-52a9-cd9b-8e66-5549b85fb29c@FreeBSD.org> References: <20220501200413.5e6b9e105b22b6e54888be1f@bidouilliste.com> <20220503.142847.811013461191473249.ish@amail.plala.or.jp> <816e5347-52a9-cd9b-8e66-5549b85fb29c@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 3 May 2022 09:22:14 -0400 Jung-uk Kim <jkim@FreeBSD.org> wrote: > On 22. 5. 3., Masachika ISHIZUKA wrote: > >> I've reworked the drm ports and the gpu-firmware ports, here is what > >> changed : > >> > > [snip] > >> > >> For the gpu firmwares it's now in multiple packages. > > > > 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'. > > I'm using aio boot(cameleon UEFI boot loader) because this machine > > is too old and uefi boot is not supported by bios, crash dump was > > destroyed on next boot by cameleon and so I cannot save crash dump. > > > > [OK] > > drm-current-kmod-5.4.144.g20220223 or drm-devel-kmod-5.7.19.g20220223 > > gpu-firmware-kmod-g20210330 > > > > [NG] > > drm-54-kmod-5.4.144 or drm-510-kmod-5.10.0 > > gpu-firmware-radeon-kmod-aruba-20211014 > > > > P.S. drm-(54|510)-kmod work well on XPS12/Vostro 3267 with i915kms. > > 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' > > Jung-uk Kim > Not much to say beyond what jkim@ said. It's a known fact that some AMD SoC uses multiple generation firmware (might be the case for PCI-E card not sure). Again if you don't know what you need just use the metaport that install everything :) -- Emmanuel Vadot <manu@bidouilliste.com> <manu@freebsd.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20220503154527.ae90d1d70a151f8bb24b8d69>