Xfce display resolution and position lost

bga

New Member

Reaction score: 6
Messages: 9

Lenovo T420 with FreeBSD 11 release, xfce and slim system showing problem that may be same as in thread 57449. New to FreeBSD so I can't be sure but the problem didn't appear until upgraded from 10.3. Sporadically, on power up the screen is offset up with the lower quarter of screen black and at a 1024x768 resolution (checked in Settings Display). Editing the settings in Setting manager has no effect, but on shutting down or rebooting a few times the correct display position and resolution (1366X768) returns. Following suggestion in cited thread: Output from xrandr with no args when display is bad:
Code:
$ /usr/local/bin/xrandr
/usr/local/bin/xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
default connected 1024x768+0+0 0mm x 0mm
   1024x768      61.00*
Output from xrandr with no args when display is good:
Code:
$ /usr/local/bin/xrandr
Screen 0: minimum 320 x 200, current 1366 x 768, maximum 8192 x 8192
LVDS1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 309mm x 173mm
   1366x768      60.10*+
   1024x768      60.00  
   800x600       60.32    56.25  
   640x480       59.94  
VGA1 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
DP1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)
Thanks for any suggestions.
 

SirDice

Administrator
Staff member
Administrator
Moderator

Reaction score: 13,894
Messages: 40,608

Have a look at /var/log/Xorg.0.log when things work and when they don't. It looks like something fails to load or get detected properly every now and then. Hopefully there's some clues in the logs.
 
OP
B

bga

New Member

Reaction score: 6
Messages: 9

Have a look at /var/log/Xorg.0.log when things work and when they don't. It looks like something fails to load or get detected properly every now and then. Hopefully there's some clues in the logs.
The first 100 lines of the /var/log/Xorg.0.log files were the same, but both had this which maybe has diagnostic value:
Code:
[    21.865] (==) No monitor specified for screen "Builtin Default fbdev Screen 0".
   Using a default monitor configuration.
[    21.865] (**) |-->Screen "Builtin Default vesa Screen 0" (2)
[    21.865] (**) |   |-->Monitor "<default monitor>"
[    21.865] (**) |   |-->Device "Builtin Default vesa Device 0"
[    21.865] (==) No monitor specified for screen "Builtin Default vesa Screen 0".
   Using a default monitor configuration.
/var/log/Xorg.0.log when the problem had self-corrected had at line 121:
Code:
[    23.817] (WW) Falling back to old probe method for vesa
[    23.817] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[    23.817] (II) intel(0): Creating default Display subsection in Screen section
   "Builtin Default intel Screen 0" for depth/fbbpp 24/32
[    23.817] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[    23.817] (==) intel(0): RGB weight 888
[    23.817] (==) intel(0): Default visual is TrueColor
[    23.817] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 3000
[    23.817] (**) intel(0): Relaxed fencing enabled
[    23.817] (**) intel(0): Wait on SwapBuffers? enabled
[    23.817] (**) intel(0): Triple buffering? enabled
[    23.817] (**) intel(0): Framebuffer tiled
[    23.817] (**) intel(0): Pixmaps tiled
[    23.817] (**) intel(0): 3D buffers tiled
[    23.817] (**) intel(0): SwapBuffers wait enabled
[    23.817] (==) intel(0): video overlay key set to 0x101fe
[    23.818] (II) intel(0): Output LVDS1 has no monitor section
and at the same position when the problem was present:
Code:
[    25.392] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[    25.392] (II) Loading sub module "vbe"
[    25.392] (II) LoadModule: "vbe"
[    25.392] (II) Loading /usr/local/lib/xorg/modules/libvbe.so
[    25.412] (II) Module vbe: vendor="X.Org Foundation"
[    25.412]    compiled for 1.17.4, module version = 1.1.0
[    25.412]    ABI class: X.Org Video Driver, version 19.0
[    25.412] (II) Loading sub module "int10"
[    25.412] (II) LoadModule: "int10"
[    25.413] (II) Loading /usr/local/lib/xorg/modules/libint10.so
[    25.433] (II) Module int10: vendor="X.Org Foundation"
[    25.433]    compiled for 1.17.4, module version = 1.0.0
[    25.433]    ABI class: X.Org Video Driver, version 19.0
[    25.433] (II) VESA(0): initializing int10
[    25.434] (II) VESA(0): Bad V_BIOS checksum
And the files were entirely different from then on with the file when the error was present 300 lines longer than the file when the display was okay.
Poking around I found section 5.4.5 in the Manual which led me to use pciconf -lv | grep -B3 display which showed:
Code:
$ pciconf -lv | grep -B3 display
vgapci0@pci0:0:2:0:   class=0x030000 card=0x21ce17aa chip=0x01268086 rev=0x09 hdr=0x00
    vendor     = 'Intel Corporation'
    device     = '2nd Generation Core Processor Family Integrated Graphics Controller'
    class      = display
Following the Manual further I created /usr/local/etc/X11/xorg.conf.d/driver-intel.conf as
Code:
Section "Device"
        Identifier "Card0"
        Driver     "intel"
        # BusID    "pci0:0:2:0"
EndSection
And on rebooting from an affected display got a normal display. The file /var/log/Xorg.0.log was now very different. As the problem occurred and self-corrected randomly usually with some number (5-8?) bootups, I don't know if it is fixed or not. And, not having much understanding I suspect my fix (if it is a fix) is not the best fix, but in any case thanks for pointing me to a place to look. I would like to know if, as I feel sure must be the case, something different would be better. Thanks.
 

SirDice

Administrator
Staff member
Administrator
Moderator

Reaction score: 13,894
Messages: 40,608

Looks like you had been using the vesa(4) driver, although it works pretty much all the time it's rather slow. The intel(4) driver should be much better so it wasn't all for nothing ;)
 
  • Thanks
Reactions: bga
OP
B

bga

New Member

Reaction score: 6
Messages: 9

Looks like you had been using the vesa(4) driver, although it works pretty much all the time it's rather slow. The intel(4) driver should be much better so it wasn't all for nothing ;)
Maybe it's good for me to confirm that it does seem quicker. I'll consider the issue fixed. (And I see now how to use the manual page formatting.)
 
OP
B

bga

New Member

Reaction score: 6
Messages: 9

Maybe it's good for me to confirm that it does seem quicker. I'll consider the issue fixed. (And I see now how to use the manual page formatting.)
 
Top