amdgpu as described in the Handbook... If there are errors from THAT, please post here, and we'll try to help you work through the errors.Well, hardware drivers don't play well with freebsd-update(8). These days, you gotta find the appropriate repo for the GPU firmwares. I think others did point out the correct URLs in this thread.Well, the most recent error, as described in my thread in "Updating & Installing" came after rebooting into 13.5-RELEASE-p6, from -p5. I then updated pkgs, and did 'kldload amdgpu' which, per the logs, apparently loaded successfully, but then immediately dropped me into a reboot countdown, in tiny font that I wasn't prepared to read. Rebooted itself... apparently without properly dismounting the file system, and then I was able to load amdgpu, but promptly crashed the system when I tried to start X -- which had apparently been corrupted from the previous reboot. Fixed that with 'pkg upgrade -f' and here we are. Still a few issues per that thread, so looking at a reinstall anyway....
So like I said, maybe I'm too old for FreeBSD desktop at this point. I don't have these issues other than with the graphics -- so not on my server (vcolo, or whatever the right term is now). This is not my first problem. All can probably be traced to user error, but nonetheless.
# cd /usr/ports/graphics/drm-kmod
# make && make install
I don't do buildworld, I just install a fresh version, and grab a snapshot of ports, and go from there. With a good processor, it takes me about a couple days to compile my way into a graphical desktop. Yeah, it does take babysitting the compilation up front, but then it's less work doing research on repos afterwards.astyle: I used to take more your approach, and did make buildworld every time, etc. I guess I'm just wanting something less labor intensive at this point. I kind of boggle at all the things I used to do.... So it goes.
I didn't know that.Would be incorrect for UEFI boot.
This is because UEFI doesn't have legacy (including VGA and VESA) framebuffers by default and having their own ones instead (accessed via GOP service) and it grabs actual video hardwares, thus, VESA cannot grab it.I didn't know that.
I've been using old hardware for too long.![]()
You don't need to build kernel locally, either.astyle: I used to take more your approach, and did make buildworld every time, etc. I guess I'm just wanting something less labor intensive at this point. I kind of boggle at all the things I used to do.... So it goes.
I quite agree, however, for 13.5-RELEASE there are no 'kmods' repositories: https://pkg.freebsd.org/FreeBSD:13:amd64/. The 'kmods' were introduced in 14.2-RELEASE (stable/14). Why should it be needed to build a graphics/drm-kmod when using 13.5-RELEASE*, except perhaps when a remote build is lagging behind a newly issued version upgrade in the source of the ports tree?What's needed is kernel source that matches the running (or updated via freebsd-update or something and to be run on next restart) kernel.