Changes in drm ports <https://lists.freebsd.org/archives/freebsd-x11/2022-May/001421.html> Farewell, drm-current-kmod and drm-devel-kmod – welcome, graphics/drm-54-kmod and graphics/drm-510-kmod; multiple ports and flavours for GPU firmware | The FreeBSD Forums <https://forums.freebsd.org/threads/85011> I assume that some of what's possible, given the changes, will be out of scope for desktop-installer. Maybe of most interest: * graphics/drm-510-kmod recommended for users of FreeBSD 13.1-RELEASE (and greater) where graphics/drm-fbsd13-kmod (tracking Linux 5.4) does not support the hardware – and please note that ports such as graphics/drm-510-kmod do not depend upon graphics/gpu-firmware-kmod Thank you.
(In reply to Graham Perrin from comment #0) > – and please note that ports such as graphics/drm-510-kmod > do not depend upon graphics/gpu-firmware-kmod For example, <https://github.com/freebsd/freebsd-ports/commit/df783714c97a24716bef17cf9f95039beee5af6f> for graphics/drm-fbsd13-kmod no longer depending upon graphics/gpu-firmware-kmod > … The dependency is still on the drm-kmod metaport so > pkg install drm-kmod will still bring the firmwares.
Thanks for the heads-up. I'm not sure what to do with this beyond adding a suggestion to auto-gpu-setup to manually try one of the other drm-kmod ports if the default drm-kmod-fbsd* don't support the hardware. Unfortunately, the fact that the port names contain hard-coded versions makes automating installation problematic. E.g. if I script something to install drm-510-kmod, it will get broken as soon as the version changes. This much may be worth doing, though. If automating isn't practical, I like to at least point the user in the direction of possible solutions.
For now I've added an informational message to auto-gpu-setup. At some point (hopefully in the next few months) I'll be investigating the possibility of a more automated GPU setup, using some contributed scripts. We'll see where the DRM ports are at that point and whether alternatives can be incorporated.