Can't configure display resolution

Terraman · Sep 6, 2020

Hi,

I've done a lot of reading and searching but I can't configure my laptop's display resolution...

This is my /var/log/Xorg.0.log post: https://pastebin.com/DsHWs2Ku

xrandr output:

Code:

xrandr: Failed to get size of gamma for output default
Screen 0: minimum 800 x 600, current 800 x 600, maximum 800 x 600
default connected 800x600+0+0 0mm x 0mm
800x600 0.00*

I also followed the handbook instructions about Xorg.

Thanks

Minbari · Sep 6, 2020

Did you install a video driver? From that log look like VESA is loading OK.

Mjölnir · Sep 6, 2020

We need more infos about your system & setup:

FTR: OS is FreeBSD 12.1-RELEASE-p8
dmesg -a | grep '\[drm\]' (type & model of graphics card/GPU)
pkg info -Ig 'drm-*'
sysrc -v kld_list
VESA is outdated/obsolete for modern displays. Many modern high resolution displays only support a very reduced number of VESA video modes, because their native resolution does not fit VESA resolutions (by means of having a greatest common divisor), i.e. instead of blurring the display they simply do not support certain VESA resolutions. Thus you need to install the appropiate X11 video driver, i.e. pkg install xf86-video-*

T-Daemon · Sep 6, 2020

mjollnir said:
We need more infos about your system & setup:

FTR: OS is FreeBSD 12.1-RELEASE-p8

dmesg -a | grep '\[drm\]' (type & model of graphics card/GPU)

pkg info -Ig 'drm-*'

sysrc -v kld_list

VESA is outdated/obsolete for modern displays. Many modern high resolution displays only support a very reduced number of VESA video modes, because their native resolution does not fit VESA resolutions (by means of having a greatest common divisor), i.e. instead of blurring the display they simply do not support certain VESA resolutions. Thus you need to install the appropiate X11 video driver, i.e. pkg install xf86-video-*

In my experience it is better to start asking which graphics card the user has before requesting configuration and driver package details, and don't trust on any vendor and model description from the user, trust only pciconf -vl | grep -B3 display.

T-Daemon · Sep 6, 2020

Terraman, please execute pciconf -vl | grep -B3 display and post the output.

Terraman · Sep 6, 2020

T-Daemon said:
Terraman, please execute pciconf -vl | grep -B3 display and post the output.

Hi T-Daemon,

This is the output:

Code:

$  pciconf -vl | grep -B3 display
vgapci0@pci0:0:2:0:    class=0x030000 card=0x99881019 chip=0x0be18086 rev=0x0b hdr=0x00
    vendor     = 'Intel Corporation'
    device     = 'Atom Processor D2xxx/N2xxx Integrated Graphics Controller'
    class      = display

Thanks

Terraman · Sep 6, 2020

mjollnir said:
We need more infos about your system & setup:

FTR: OS is FreeBSD 12.1-RELEASE-p8

dmesg -a | grep '\[drm\]' (type & model of graphics card/GPU)

pkg info -Ig 'drm-*'

sysrc -v kld_list

VESA is outdated/obsolete for modern displays. Many modern high resolution displays only support a very reduced number of VESA video modes, because their native resolution does not fit VESA resolutions (by means of having a greatest common divisor), i.e. instead of blurring the display they simply do not support certain VESA resolutions. Thus you need to install the appropiate X11 video driver, i.e. pkg install xf86-video-*

Hi mjollnir,

These are the outputs:

Code:

$ dmesg -a | grep '\[drm\]'
info: [drm] Initialized drm 1.1.0 20060810
$ pkg info -Ig 'drm-*'
drm-legacy-kmod-g20200825      Legacy DRM modules for the linuxkpi-based KMS components
$ sysrc -v kld_list
/etc/rc.conf: kld_list: /boot/modules/i915kms.ko

Thanks

Alexander88207 · Sep 6, 2020

graphics/drm-legacy-kmod is obsolete doesn't it work with graphics/drm-kmod? I have an laptop with an intel atom aswell and it works fine.

Terraman · Sep 6, 2020

Alexander88207 said:
graphics/drm-legacy-kmod is obsolete doesn't it work with graphics/drm-kmod? I have an laptop with an intel atom aswell and it works fine.

Yes, I know, but I've tried several things out...

I've installed the newer version, this is the output:

Code:

$ pkg info -Ig 'drm-*'                                                             
drm-fbsd12.0-kmod-4.16.g20200221 DRM modules for the linuxkpi-based KMS components
drm-kmod-g20190710             Metaport of DRM modules for the linuxkpi-based KMS components
$ sysrc -v kld_list                                                                  
/etc/rc.conf: kld_list: /boot/modules/i915kms.ko

Minbari · Sep 7, 2020

Why so many people ignore Xorg intel driver, I have no idea! Your processor (Atom Integrated Graphics Controller) is supported by x11-drivers/xf86-video-intel driver.

Alexander88207 · Sep 7, 2020

xf86-video-intel is very old, the default modesetting driver is better.

Minbari · Sep 7, 2020

Alexander88207 said:
xf86-video-intel is very old, the default modesetting driver is better.

His Atom processor is also old. On an old Thinkpad T430 which has an i7-3612QM (Ivy-Bridge) processor I have x11-drivers/xf86-video-intel and graphics/drm-kmod installed side by side and everything works as it was expected.

Mjölnir · Sep 7, 2020

Alexander88207 said:
xf86-video-intel is very old, the default modesetting driver is better.

Why? Please explain.
Which one in /usr/ports/X11-drivers/xf86-video-* is that? Do you mean X11-drivers/xf86-video-scfb?

Mjölnir · Sep 7, 2020

Terraman:

Make shure you can get higher resolutions via the graphics/drm-kmod on the console:
pkg install drm-kmod & sysrc kld_list+=" /boot/modules/i915kms.ko" and
kldload /boot/modules/i915kms.ko or shutdown -r +2min "Change DRM/KMS video kernel module" should change the console's resolution, which you can control via kern.vt.fb.default_mode="<X>x<Y>" or kern.vt.fb.modes.<connector>="<X>x<Y>" in loader.conf(5). You can grep '\[drm]' /var/run/dmesg.boot the connector name after verbose bootup. When you load the DRM/KMS kernel module manually, make shure X11 is not running, i.e. no display manager e.g. sddm(1).
Once that works, you can install either the intel(4) or scfb(4) X11 video driver. AFAIK the specialized drivers offer 3D & video acceleration, while the framebuffer driver does not; I may be wrong, though.

Alexander88207 · Sep 7, 2020

mjollnir said:
Why? Please explain.

Which one in /usr/ports/X11-drivers/xf86-video-* is that? Do you mean X11-drivers/xf86-video-scfb?

1. More Stable, less bugs, better perfomance (If you want a better answer duck "xf86-video-intel vs modesetting")

2. It comes out of the box with x11-servers/xorg-server and sits in lib/xorg/modules/drivers/modesetting_drv.so you can see it also the in the xorg log file that modesetting_drv.so is being used if xf86-video-intel is not installed.

Mjölnir · Sep 7, 2020

Alexander88207 said:
1. More Stable, less bugs, better perfomance (If you want a better answer duck "xf86-video-intel vs modesetting")
2. It comes out of the box with x11-servers/xorg-server and sits in lib/xorg/modules/drivers/modesetting_drv.so you can see it also the in the xorg log file that modesetting_drv.so is being used if xf86-video-intel is not installed.

That's all Linux stuff, no search results for FreeBSD. According to the Phoronix benchmark -- which is mostly synthetic anyway -- 3D performance is about the same, and 2D performance is much better for the intel(4) driver (that's what usually counts on the desktop). I will now try again if the SNA acceleration works for intel(4) (default is still UXA) vs. the modesetting driver + glamoregl module. I have to reboot anyway after freebsd-update(8) to 12.1-RELEASE-p9. Thx for the hint.

Deleted member 63539 · Sep 7, 2020

Could you try to compile from port graphics/drm-kmod instead of installing the packacge drm-kmod?

Terraman · Sep 7, 2020

Minbari said:
Why so many people ignore Xorg intel driver, I have no idea! Your processor (Atom Integrated Graphics Controller) is supported by x11-drivers/xf86-video-intel driver.

Yes! Indeed! It is still installed:

Code:

$ sudo pkg install -y xf86-video-intel
Password:
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Checking integrity... done (0 conflicting)
The most recent versions of packages are already installed

Terraman · Sep 7, 2020

sysctl said:
Could you try to compile from port graphics/drm-kmod instead of installing the packacge drm-kmod?

Done!

Code:

$ sudo pkg delete drm-kmod
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 1 packages (of 0 packages in the universe):

Installed packages to be REMOVED:
    drm-kmod: g20190710

Number of packages to be removed: 1

Proceed with deinstalling packages? [y/N]: y
[1/1] Deinstalling drm-kmod-g20190710...

$ cd /usr/ports/graphics/drm-kmod
$ sudo make install clean
===>  Installing for drm-kmod-g20190710
===>  Checking if drm-kmod is already installed
===>   Registering installation for drm-kmod-g20190710
Installing drm-kmod-g20190710...
===>  Cleaning for drm-kmod-g20190710

It isn't fixed yet.

Alexander88207 · Sep 7, 2020

Terraman said:

Done!

Code:

$ sudo pkg delete drm-kmod
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 1 packages (of 0 packages in the universe):

Installed packages to be REMOVED:
    drm-kmod: g20190710

Number of packages to be removed: 1

Proceed with deinstalling packages? [y/N]: y
[1/1] Deinstalling drm-kmod-g20190710...

$ cd /usr/ports/graphics/drm-kmod
$ sudo make install clean
===>  Installing for drm-kmod-g20190710
===>  Checking if drm-kmod is already installed
===>   Registering installation for drm-kmod-g20190710
Installing drm-kmod-g20190710...
===>  Cleaning for drm-kmod-g20190710

It isn't fixed yet.

You also have to delete graphics/drm-fbsd12.0-kmod before building, because graphics/drm-kmod is only a metapackage or a metaport to be exactly

Terraman · Sep 7, 2020

Alexander88207 said:
You also have to delete graphics/drm-fbsd12.0-kmod before building, because graphics/drm-kmod is only a metapackage or a metaport to be exactly

Ok, but...

Code:

$ sudo pkg delete drm-fbsd12.0-kmod
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 2 packages (of 0 packages in the universe):

Installed packages to be REMOVED:
    drm-fbsd12.0-kmod: 4.16.g20200221
    drm-kmod: g20190710

Number of packages to be removed: 2

The operation will free 10 MiB.

Proceed with deinstalling packages? [y/N]: y
[1/2] Deinstalling drm-kmod-g20190710...
[2/2] Deinstalling drm-fbsd12.0-kmod-4.16.g20200221...
[2/2] Deleting files for drm-fbsd12.0-kmod-4.16.g20200221: 100%
$ cd /usr/ports/graphics/drm-kmod/
/usr/ports/graphics/drm-kmod/$ sudo make install clean
===>   drm-kmod-g20190710 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by drm-kmod-g20190710 for building
===>  Extracting for drm-kmod-g20190710
===>  Patching for drm-kmod-g20190710
===>  Configuring for drm-kmod-g20190710
===>  Staging for drm-kmod-g20190710
===>   drm-kmod-g20190710 depends on file: /boot/modules/drm.ko - not found
===>  drm-fbsd12.0-kmod-4.16.g20190814 requires kernel source files in
/usr/src.
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/graphics/drm-fbsd12.0-kmod
*** Error code 1

Stop.
make: stopped in /usr/ports/graphics/drm-kmod
cd /usr/ports/graphics/drm-fbsd12.0-kmod/
/usr/ports/graphics/drm-fbsd12.0-kmod$ sudo make install clean
===>  drm-fbsd12.0-kmod-4.16.g20190814 requires kernel source files in
/usr/src.
*** Error code 1

Stop.
make: stopped in /usr/ports/graphics/drm-fbsd12.0-kmod

Alexander88207 · Sep 7, 2020

I assume that you are using 12-Release? If yes do # svnlite checkout https://svn.freebsd.org/base/releng/12.1 /usr/src.

If you are using 12.1-STABLE for example "12.1-STABLE r364849" do # svnlite checkout https://svn.freebsd.org/base/stable/12 -r364849 /usr/src.

If you dont know what version are you using use uname -a.

Terraman · Sep 7, 2020

Alexander88207 said:
I assume that you are using 12-Release? If yes do # svnlite checkout https://svn.freebsd.org/base/releng/12.1 /usr/src.

If you are using 12.1-STABLE for example "12.1-STABLE r364849" do # svnlite checkout https://svn.freebsd.org/base/stable/12 -r364849 /usr/src.

If you dont know what version are you using use uname -a.

Yes, I'm using 12-Release. I've got the next message:

Code:

Checked out revision 365430.

Mjölnir · Sep 7, 2020

freebsd-update(8) 1st. drm-kmod is a meta-port, you may want to build drm-fbsd12.0-kmod. Try again now that you've got the FreeBSD sources: cd, \nohup nice make -C /usr/ports/graphics/drm-fbsd12.0-kmod install clean &, then less nohup.out.

Terraman · Sep 8, 2020

mjollnir said:
freebsd-update(8) 1st. drm-kmod is a meta-port, you may want to build drm-fbsd12.0-kmod. Try again now that you've got the FreeBSD sources: cd, \nohup nice make -C /usr/ports/graphics/drm-fbsd12.0-kmod install clean &, then less nohup.out.

I've done the instructions:

Code:

#\nohup nice make -C /usr/ports/graphics/drm-fbsd12.0-kmod install clean &
[1] 1689
root@freebsd:~ # appending output to nohup.out
less nohup.out
===> Building/installing dialog4ports as it is required for the config dialog
===>  Cleaning for dialog4ports-0.1.6
===>  License BSD2CLAUSE accepted by the user
===>   dialog4ports-0.1.6 depends on file: /usr/local/sbin/pkg - found
=> dialog4ports-0.1.6.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
=> Attempting to fetch https://files.etoilebsd.net/dialog4ports/dialog4ports-0.1.6.tar.gz
dialog4ports-0.1.6.tar.gz                               10 kB   46 MBps    00s
===> Fetching all distfiles required by dialog4ports-0.1.6 for building
===>  Extracting for dialog4ports-0.1.6
=> SHA256 Checksum OK for dialog4ports-0.1.6.tar.gz.
===>  Patching for dialog4ports-0.1.6
===>  Configuring for dialog4ports-0.1.6
===>  Building for dialog4ports-0.1.6
--- dialog4ports.o ---
--- mixedlist.o ---
--- dialog4ports.1.gz ---
--- dialog4ports.o ---
cc  -O2 -pipe  -fstack-protector-strong -fno-strict-aliasing  -Wall -pedantic -c dialog4ports.c -o dialog4ports.o
--- mixedlist.o ---
cc  -O2 -pipe  -fstack-protector-strong -fno-strict-aliasing  -Wall -pedantic -c mixedlist.c -o mixedlist.o
--- dialog4ports.1.gz ---
gzip -cn dialog4ports.1 > dialog4ports.1.gz
--- dialog4ports ---
cc -O2 -pipe  -fstack-protector-strong -fno-strict-aliasing  -Wall -pedantic dialog4ports.o mixedlist.o -o dialog4ports -lncursesw -lm -ldialog
===>  Staging for dialog4ports-0.1.6
===>   Generating temporary packing list
install  -s -m 555 dialog4ports /usr/ports/ports-mgmt/dialog4ports/work/stage/usr/local/bin
install  -m 0644 dialog4ports.1.gz /usr/ports/ports-mgmt/dialog4ports/work/stage/usr/local/man/man1
====> Compressing man pages (compress-man)
===>  Installing for dialog4ports-0.1.6
===>  Checking if dialog4ports is already installed
===>   Registering installation for dialog4ports-0.1.6
Installing dialog4ports-0.1.6...
===>  Cleaning for dialog4ports-0.1.6

And compiled from port graphics/drm-kmod.

Can't configure display resolution

Terraman

Minbari

Mjölnir

T-Daemon

T-Daemon

Terraman

Terraman

Alexander88207

Enthusiast

Terraman

Minbari

Alexander88207

Enthusiast

Minbari

Mjölnir

Mjölnir

Alexander88207

Enthusiast

Mjölnir

Deleted member 63539

Guest

Terraman

Terraman

Alexander88207

Enthusiast

Terraman

Alexander88207

Enthusiast

Terraman

Mjölnir

Terraman