NetBSD-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: External monitor not detected
>> Using a Tiger lake laptop with NetBSD 10 I can not get the HDMI port working.
>> xrandr -q only prints an 1 entry named "default" for the builtin display.
>> Is there anything to check or try?
>>
>If you have a Tiger Lake GPU, then you're very likely not running with DRMKMS,
>and only the genfb driver has attached. With genfb, only the primary display
>gets output. See wsdisplay(4).
>And, if you want to rotate the picture, you can only do it in X. See wsfb(4).
>Try,
>fgrep genfb /var/run/dmesg.boot
>see if it says `drm at genfb0 not configured'.
This does print:
genfb0 at pci0 dev 2 function 0: Intel UHD Graphics (GT2, 96/80 EU) (rev. 0x03)
genfb0: framebuffer at 0x4000000000, size 800x1280, depth 32, stride 3200
genfb0: shadow framebuffer enabled, size 4000 KB
wsdisplay0 at genfb0 kbdmux 1: console (default, vt100 emulation), using wskbd0
drm at genfb0 not configured
startx seems to use wsfb, it tries modesetting though:
[ 2605.090] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 2605.090] (II) VESA: driver for VESA chipsets: vesa
[ 2605.090] (II) wsfb: driver for wsdisplay framebuffer: wsfb
[ 2605.090] (--) Using wscons driver on /dev/ttyE4 in pcvt compatibility mode (version 3.32)
[ 2605.090] (--) using VT number 5
[ 2605.100] (EE) open /dev/dri/card0: No such file or directory
[ 2605.100] (WW) Falling back to old probe method for modesetting
[ 2605.100] (EE) open /dev/dri/card0: No such file or directory
[ 2605.100] vesa: Ignoring device with a bound kernel driver
[ 2605.100] (WW) Falling back to old probe method for wsfb
[ 2605.100] (II) wsfb(2): using default device
[ 2605.100] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 2605.100] (EE) Screen 0 deleted because of no matching config section.
[ 2605.100] (II) UnloadModule: "modesetting"
[ 2605.100] (EE) Screen 0 deleted because of no matching config section.
[ 2605.100] (II) UnloadModule: "vesa"
[ 2605.100] (II) fboffset 0
[ 2605.100] (II) wsfb(0): Creating default Display subsection in Screen section
"Builtin Default wsfb Screen 0" for depth/fbbpp 24/32
My attempts at forcing the right driver with a custom config failed:
First tried X -configure, it generated a config file but also printed this:
Number of created screens does not match number of detected devices.
Configuration failed.
(EE) Server terminated with error (2). Closing log file.
Starting the the autogenerated config with X -config ~/xorg.conf.new exited with:
[ 1525.543] (EE) No devices detected.
[ 1525.543] (EE)
Fatal server error:
[ 1525.543] (EE) no screens found(EE)
[ 1525.543] (EE)
Tried changing intel to modesetting
Identifier "Card0"
Driver "intel" -> "modesetting"
BusID "PCI:0:2:0"
Driver "intel"
But got:
[ 934.601] (II) LoadModule: "modesetting"
[ 934.601] (II) Loading /usr/X11R7/lib/modules/drivers/modesetting_drv.so
[ 934.601] (II) Module modesetting: vendor="X.Org Foundation"
[ 934.601] compiled for 1.21.1.9, module version = 1.21.1
[ 934.601] Module class: X.Org Video Driver
[ 934.601] ABI class: X.Org Video Driver, version 25.2
[ 934.601] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 934.601] (--) Using wscons driver on /dev/ttyE4 in pcvt compatibility mode (version 3.32)
[ 934.601] (--) using VT number 5
[ 934.610] (EE) open /dev/dri/card0: No such file or directory
[ 934.610] (WW) Falling back to old probe method for modesetting
[ 934.610] (EE) open /dev/dri/card0: No such file or directory
[ 934.610] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 934.610] (EE) Screen 0 deleted because of no matching config section.
[ 934.610] (II) UnloadModule: "modesetting"
[ 934.610] (EE) Device(s) detected, but none match those in the config file.
[ 934.610] (EE)
Fatal server error:
[ 934.610] (EE) no screens found(EE)
Home |
Main Index |
Thread Index |
Old Index