VT fails after drm load

q-pa commented 1 month ago

Version

24.07.3

What desktop?

Official MATE

Explain the issue and what happens

The following error occurs in dmesg:

[drm] Initialized i915 1.6.0 20201103 for drmn0 on minor 0 VT: Driver priority 0 too low. Current 101 fbd0: not attached to vt(4) console; another device has precedence (err=17)

and the display goes black until a display manager is started.

Explain how to reproduce the bug?

.

What is the Expected behavior (if applicable)

starting VT, seeing boot messages, being able to switch TTYs

Additional context (if applicable)

Known bug: https://www.mail-archive.com/stable@freebsd.org/msg02342.html

q-pa commented 1 month ago

My hardware: Intel(R) UHD Graphics 620 (KBL GT2)

cat /var/log/Xorg.0.log | grep Intel
[    12.068] (II) modeset(0): glamor X acceleration enabled on Mesa Intel(R) UHD Graphics 620 (KBL GT2)

My current workaround is to not to use VTs plus I temporary have set kern.vt.suspendswitch=0 in /etc/sysctl.conf to get suspend/resume working properly.

Also my system is using the iris driver instead of crocus

cat /var/log/Xorg.0.log | grep iris  
[    12.236] (II) modeset(0): [DRI2]   DRI driver: iris
[    12.260] (II) AIGLX: Loaded and initialized iris

these posts contain lots of information regarding this bug: https://forums.freebsd.org/threads/intermittant-bug-in-14-0-release-dri-crocus-driver.91824/

q-pa commented 1 week ago

After updating to 24.10.1 the boot messages are displayed again and I can use VTs again. But there still seems to be an issue with drm load.

Before switching VTs:

xdriinfo

Screen 0: crocus

After switching VTs:

xdriinfo

failed to authenticate magic 1
failed to load driver: crocus
failed to authenticate magic 1
failed to load driver: crocus
Screen 0: swrast

ghostbsd / issues