вт, 13 мая 2025 г., 12:30 RVP <r...@sdf.org>:

> On Fri, 2 May 2025, Andrew Randrianasulu wrote:
>
> > In NetBSD 10.1/amd64 it does not show up in glxinfo output, and manually
> doing
> >
> > modload amdgpu leaves no traces in dmesg
> >
>
> No, that doesn't work. You have to either,
>
> a) load all the reqd. kernel modules in /boot.cfg, or,
> b) compile the driver into the kernel
>
> for the driver to "take".
>
> For a) see the "load" commands in:
>
> https://gnats.netbsd.org/57207



Ah, thanks!

I copy/pasted this line

menu=Boot with amdgpu and voluminous debugging spew:rndseed
/var/db/entropy-file;load amdgpu;load drmkms;load drmkms_linux;load
drmkms_pci;load drmkms_sched;load drmkms_ttm;load sysmon;load
sysmon_power;boot -v -x

into my boot.cfg from Slackware and we will see if it works on next reboot
(not sure when exactly)


>
> > 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Baffin
> HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X]
> > [...]
> > 01:00.0 0300: 1002:699f (rev c7) (prog-if 00 [VGA controller])
> >
>
> Looks like a supported card. See list here:
>
>
> https://github.com/NetBSD/src/blob/netbsd-10/sys/external/bsd/drm2/dist/drm/amd/amdgpu/amdgpu_drv.c#L957



Yea, I was just surprized module loading not worked. I think Linux can
"kick away" firmware/vga display buffer on load, but I guess NetBSD still
can't? Or may be something else prevent runtime take-over by gpu driver
module after system boot?


>
> -RVP
>

Reply via email to