amdgpu on Ryzen 4700 w. Vega10 Renoir Graphics

[Niclas Zeising]

On 2020-07-16 19:49, Michael Schuster wrote:
> 
> 
> On Thu, Jul 16, 2020 at 4:58 PM Niclas Zeising 
> <zeising+freebsd at daemonic.se <mailto:zeising%2Bfreebsd at daemonic.se>> wrote:
> 
>     On 2020-07-16 16:48, Michael Schuster wrote:
>      > Hi all,
>      >
>      > I know I'm top-posting (this note) AND cross-posting - please
>     bear(sp?)
>      > with me, I think I'm somewhat justified:
>      >
>      >
>      > On Wed, Jul 15, 2020 at 9:46 PM Niclas Zeising
>      > <zeising+freebsd at daemonic.se
>     <mailto:zeising%2Bfreebsd at daemonic.se>
>     <mailto:zeising%2Bfreebsd at daemonic.se
>     <mailto:zeising%252Bfreebsd at daemonic.se>>> wrote:
>      >
>      >
>      >      >         On 2020-07-15 14:25, Michael Schuster wrote:
>      >      >          > Hi all,
>      >      >          >
>      >      >          > I got a new HP laptop (455 G7) and put latest
>     GhostBSD
>      >      >         (20.04, based on
>      >      >          > 12.1 release) on it. During installation, the only
>      >     graphics
>      >      >         selection that
>      >      >          > didn't fail was 'scfb', which I'm still using.
>      >      >          >
>      >      >          > AFAICT from my research, Renoir is supported by
>     latest drm
>      >      >         driver/module,
>      >      >          > so I installed that (
>      >      >          >
>      >      >
>     https://github.com/FreeBSDDesktop/kms-drm/tree/drm-v5.0-fbsd12.1).
>      >      >
>      >      >         That branch isn't used, and may be broken.
>      >      >         If you want to get anything more recent than
>      >     drm-fbds12.0-kmod,
>      >      >         which
>      >      >         tracks Linux 4.16, you have to upgrade to current
>     and use
>      >      >         drm-devel-kmod
>      >      >         (which currently is at 5.3).
>      >      >
>      >      >
>      >      >     just to be clear: by "current", you mean FreeBSD
>      >     13.0-current, right?
>      >      >     thx
>      >      >
>      >      >
>      >      > so I went ahead and installed FreeBSD-current on this machine,
>      >     and then
>      >      > drm-devel-kmodas you recommended. Alas, I'm getting an error:
>      >      >
>      >      > KLD amdgpu.ko: depends on kernel - not available or
>     version mismatch
>      >      >
>      >      > some googling showed that - since I did a fresh install of
>      >     -current just
>      >      > now - amdgpu must be out of sync. the version I have
>     installed is:
>      >      >
>      >      > xf86_video-amdgpu-19.1.0_1.
>      >
>      >     This means that your kernel and the drm-devel-kmod package
>     are out of
>      >     sync.  drm-devel-kmod installs the kernel graphics drivers,
>     such as
>      >     amdgpu.ko, and it has to be in sync with your kernel. 
>     Depending a bit
>      >     on which svn revision of current you have, you should be able
>     to build
>      >     drm-devel-kmod (and preferably gpu-firmware-kmod) from ports.
>      >
>      >
>      > @Niclas,
> 
>     your FreeBSD system.  Updating FreeBSD Current is generally
>     accomplished
>     by rebuilding and installing it from source.  Instructions on that can
>     be found here:
>     https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
> 
> 
> again, thx.
> Building world and the kernel worked, I'm now running that kernel I built.
> I managed to successfully build graphics/drm-devel-kmod and 
> gpu-firmware-kmod. "make install" for some reason didn't - I could only 
> find modified amdgpu.ko in 
> graphics/drm-devel-kmod/work/stage/boot/modules/ (and no documentation 
> on how to achieve this) - so I copied all the .ko files from that 
> directory into /boot/modules, though a reboot didn't help, here's the 
> latest Xorg.0.log output (selected)
> 
> [    22.733] (==) Matched ati as autoconfigured driver 0
> [    22.733] (==) Matched modesetting as autoconfigured driver 1
> [    22.733] (==) Matched scfb as autoconfigured driver 2
> [    22.733] (==) Matched vesa as autoconfigured driver 3
> [    22.733] (==) Assigned the driver to the xf86ConfigLayout
> [    22.733] (II) LoadModule: "ati"
> [    22.734] (WW) Warning, couldn't open module ati
> [    22.734] (EE) Failed to load module "ati" (module does not exist, 0)
> [    22.734] (II) LoadModule: "modesetting"
> [...]
> [    22.735] (II) LoadModule: "scfb"
> [...]
> [    22.736] (II) LoadModule: "vesa"
> [...]
> [    22.736] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
> [    22.736] (II) scfb: driver for wsdisplay framebuffer: scfb
> [    22.737] (II) VESA: driver for VESA chipsets: vesa
> [    22.737] (--) Using syscons driver with X support (version 2.0)
> [    22.737] (++) using VT number 9
> 
> [    22.747] (EE) open /dev/dri/card0: No such file or directory
> [    22.747] (WW) Falling back to old probe method for modesetting
> [    22.747] (EE) open /dev/dri/card0: No such file or directory
> [    22.747] (WW) Falling back to old probe method for scfb
> [    22.747] scfb trace: probe start
> [    22.747] (II) scfb(1): using default device
> [    22.747] scfb trace: probe done
> [    22.747] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card 
> support
> [    22.747] (EE) Screen 0 deleted because of no matching config section.
> 
> and indeed, /dev/dri is nonexistent (though /dev/drm/ contains a ton 
> (... ok, 0x100) of driver entries). Also note: amdgpu appears nowhere in 
> the excerpt above (or even the complete Xorg.0.log file).
> 
> One thing I remember from the previous ghostbsd installation: 
> /etc/rc.conf's kld_list contained a few more entries that just 
> "/boot/modules/amdgpu.ko" that I have now ... should I put something 
> else in?
> 
> so - once more - I'm hoping for your guidance :-)

It would be interesting to see why make install in drm-devel-kmod failed 
and you had to copy the modules yourself.
 From the output you've pasted, it looks like amdgpu.ko didn't load and 
attach properly to the hardware.  What does dmesg say when you load the 
module?  Have you done any xorg configuration?  That should in general 
not be needed, so it might be worth trying without any configuration.
Regards
-- 
Niclas