freebsd-update install
afterwards? Twice, first one time, then reboot, then another time.When the kernel starts booting or when a drm driver is loaded?the screen went blank at the point the video mode changes.
Is it necessary for a custom kernel or always? The handbook is very subtle at this point. Just for acquiring knowledge.Did you runfreebsd-update install
afterwards? Twice, first one time, then reboot, then another time.
See "24.2.3. Performing Major and Minor Version Upgrades" here: https://docs.freebsd.org/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html
It is always necessary. If you use a custom kernel you additionally need to issueIs it necessary for a custom kernel or always?
nextboot -k GENERIC
after the first freebsd-update install
.Looks like I was a bit too quick to diagnose failure..... After a reboot, I happened to leave the system for over ten minutes and the display of the booting process resumed, but something must be wrong for it to take so long..... It was very quick before the upgrade.I have just runfreebsd-update -r 12.2 upgrade
and all appeared to go well, but on reboot the system started OK but the screen went blank at the point the video mode changes.
[2020-11-11] Due to slight changes to the ABI and KBI between FreeBSD 12.1 and FreeBSD 12.2, it is important to note that certain third-party kernel modules may need to be rebuilt locally, until FreeBSD 12.1 reaches end of life.
Of note, this includes, but is not limited to, graphics/*-kmod, net/*-kmod, and possibly others that are too extensive to list.
I was able to boot up quickly, so it looks like /boot/kernel/i915kms.ko was causing the problem. After running:-kld_list='i915kms'
pkg install drm-kmod
things are working normally again.kld_list='/boot/modules/i915kms.ko'
This was because the packages were built for 12.1 and these caused problems on 12.2. But 12.1 has since gone EoL and packages are now being built for 12.2, so this warning can be ignored.Did you read the release notes and errata? Maybe it'll help.