Re: fbd0 / vt(4) console, no longer coming up after 14.2-RELEASE upgrade?

From: Arnold Greyling <greylina_at_menusis.com>
Date: Wed, 04 Dec 2024 06:17:31 UTC
> On 04 Dec 2024, at 02:18, Felipe Grazziotin <felipe@starbyte.net> wrote:
> 
> Hi folks,
> 
> I'm not sure how to report this - please let me know and I'll follow
> up accordingly.
> 
> I've been running 14.x on my Intel NUC (NUC6i3SYH Intel Core i3-6100U)
> as a home server for about a year now, flawless.
> Last night I did an upgrade from 14.1-p6 to 14.2-p0. It didn't go 100%
> clean, on the first call to
> # freebsd-update fetch install ;  freebsd-update upgrade -r 14.2
> <
<snip details>
> [7] <6>[drm] Initialized i915 1.6.0 20201103 for drmn0 on minor 0
> 
> Reading the readmining dmesg buffer after connecting to SSH, I see the
> following:
> 
> [7] VT: Driver priority 0 too low. Current 101
> [7]  fbd0: not attached to vt(4) console; another device has precedence (err=17)
> [7] pchtherm0: <Skylake PCH Thermal Subsystem> mem
> 0xdf050000-0xdf050fff at device 20.2 on pci0
> [7] ichsmb0: <Intel Sunrise Point-LP SMBus controller> port
> 0xf040-0xf05f mem 0xdf04a000-0xdf04a0ff at device 31.4 on pci0
> [7] smbus0: <System Management Bus> on ichsmb0
> 

It may be related to the open issue from the errata:

drm-kmod packages compiled on FreeBSD 14.1 result in the text console being inoperative when the kernel module is loaded. Recompiling the package from the ports tree will restore the lost functionality. This issue will also resolve itself after the FreeBSD 14.1 EoL, when packages for 14-STABLE will start being built on FreeBSD 14.2-RELEASE.

https://www.freebsd.org/releases/14.2R/errata/

Regards
Arnold

--
Arnold Greyling
greylina@menusis.com
https://arnoldgreyling.solutions <https://arnoldgreyling.solutions/>