You are not logged in.

Pages: 1

#1 2014-08-04 09:06:02

nbd
Member
Registered: 2014-08-04
Posts: 389

[SOLVED]Screen resolution began to be incorrectly detected

After installing some packages not having obvious relations to video issues (mysql and zfs related packages), the screen resolution on my 1280x1024 screen began to be set as 1024x768 without 1280x1024 in the list of possible modes. I tried to X -configure but to no avail. Reinstalling xorg-server also didn't help. I tried to manually detect and add 1280x1024 mode with xrandr, this mode began to appear in the modes list, but the resolution remains 1024x768 when it's selected.

I have an ancient SiS videocard, but  it worked OK with the standard vesa driver.

What can be the cause of this issue and how it could be corrected?

Some fragments of Xorg log:

[   769.623] (II) VESA(0): Total Memory: 512 64KB banks (32768kB)
[   769.623] (II) VESA(0): Monitor0: Using default hsync range of 31.50-48.00 kHz
[   769.623] (II) VESA(0): Monitor0: Using default vrefresh range of 50.00-70.00 Hz
[   769.623] (II) VESA(0): Monitor0: Using default maximum pixel clock of 65.00 MHz
[   769.623] (WW) VESA(0): Unable to estimate virtual size
[   769.623] (II) VESA(0): Not using built-in mode "1600x1200" (no mode of this name)
[   769.623] (II) VESA(0): Not using built-in mode "1280x1024" (no mode of this name)
[   769.623] (II) VESA(0): Not using built-in mode "1024x768" (no mode of this name)
[   769.623] (II) VESA(0): Not using built-in mode "800x600" (no mode of this name)
[   769.623] (II) VESA(0): Not using built-in mode "640x480" (no mode of this name)
[   769.623] (WW) VESA(0): No valid modes left. Trying less strict filter...
[   769.623] (II) VESA(0): Monitor0: Using hsync range of 31.50-48.00 kHz
[   769.623] (II) VESA(0): Monitor0: Using vrefresh range of 50.00-70.00 Hz
[   769.623] (II) VESA(0): Monitor0: Using maximum pixel clock of 65.00 MHz
[   769.623] (WW) VESA(0): Unable to estimate virtual size
[   769.623] (II) VESA(0): Not using built-in mode "1600x1200" (hsync out of range)
[   769.623] (II) VESA(0): Not using built-in mode "1280x1024" (hsync out of range)
[   769.623] (--) VESA(0): Virtual size is 1024x768 (pitch 1024)
[   769.623] (**) VESA(0): *Built-in mode "1024x768"
[   769.623] (**) VESA(0): *Built-in mode "800x600"
[   769.623] (**) VESA(0): *Built-in mode "640x480"
[   769.623] (==) VESA(0): DPI set to (96, 96)
[   769.623] (II) VESA(0): Attempting to use 60Hz refresh for mode "1024x768" (118)
[   769.624] (II) VESA(0): Attempting to use 60Hz refresh for mode "800x600" (115)
[   769.624] (II) VESA(0): Attempting to use 60Hz refresh for mode "640x480" (112)

// Another fragment:



[   769.384] (II) LoadModule: "glx"
[   769.384] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[   769.392] (II) Module glx: vendor="X.Org Foundation"
[   769.392] 	compiled for 1.16.0, module version = 1.0.0
[   769.392] 	ABI class: X.Org Server Extension, version 8.0
[   769.392] (==) AIGLX enabled
[   769.392] (II) LoadModule: "vesa"
[   769.393] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[   769.395] (II) Module vesa: vendor="X.Org Foundation"
[   769.395] 	compiled for 1.16.0, module version = 2.3.2
[   769.395] 	Module class: X.Org Video Driver
[   769.395] 	ABI class: X.Org Video Driver, version 18.0
[   769.395] (II) VESA: driver for VESA chipsets: vesa
[   769.395] (++) using VT number 1

[   769.395] (--) controlling tty is VT number 1, auto-enabling KeepTty
[   769.395] (II) Loading sub module "vbe"
[   769.395] (II) LoadModule: "vbe"
[   769.396] (II) Loading /usr/lib/xorg/modules/libvbe.so
[   769.396] (II) Module vbe: vendor="X.Org Foundation"
[   769.396] 	compiled for 1.16.0, module version = 1.1.0
[   769.396] 	ABI class: X.Org Video Driver, version 18.0
[   769.396] (II) Loading sub module "int10"
[   769.396] (II) LoadModule: "int10"
[   769.398] (II) Loading /usr/lib/xorg/modules/libint10.so
[   769.399] (II) Module int10: vendor="X.Org Foundation"
[   769.399] 	compiled for 1.16.0, module version = 1.0.0
[   769.399] 	ABI class: X.Org Video Driver, version 18.0
[   769.399] (II) VESA(0): initializing int10
[   769.421] (II) VESA(0): Primary V_BIOS segment is: 0xc000
[   769.424] (II) VESA(0): VESA BIOS detected
[   769.424] (II) VESA(0): VESA VBE Version 3.0
[   769.424] (II) VESA(0): VESA VBE Total Mem: 32768 kB
[   769.424] (II) VESA(0): VESA VBE OEM: SiS
[   769.424] (II) VESA(0): VESA VBE OEM Software Rev: 1.0
[   769.424] (II) VESA(0): VESA VBE OEM Vendor: Silicon Integrated Systems Corp.
[   769.424] (II) VESA(0): VESA VBE OEM Product: 6330
[   769.424] (II) VESA(0): VESA VBE OEM Product Rev: 3.72.10
[   769.448] (==) VESA(0): Depth 24, (--) framebuffer bpp 32
[   769.448] (==) VESA(0): RGB weight 888
[   769.448] (==) VESA(0): Default visual is TrueColor
[   769.448] (==) VESA(0): Using gamma correction (1.0, 1.0, 1.0)
[   769.448] (II) Loading sub module "ddc"
[   769.448] (II) LoadModule: "ddc"
[   769.448] (II) Module "ddc" already built-in
[   769.533] (II) VESA(0): VESA VBE DDC supported
[   769.533] (II) VESA(0): VESA VBE DDC Level none
[   769.533] (II) VESA(0): VESA VBE DDC transfer in appr. 0 sec.
[   769.576] (II) VESA(0): VESA VBE DDC read failed
[   769.576] (II) VESA(0): Searching for matching VESA mode(s):

Last edited by nbd (2014-08-05 09:17:50)

bing different

Offline

#2 2014-08-04 09:18:01

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,424
Website

Re: [SOLVED]Screen resolution began to be incorrectly detected

Please use code tags when pasting to the boards: https://wiki.archlinux.org/index.php/Fo … s_and_Code

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#3 2014-08-04 10:12:25

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: [SOLVED]Screen resolution began to be incorrectly detected

Remove the configs created with 'X -configure'. Have a look at https://wiki.archlinux.org/index.php/Xr … esolutions
Post what graphics hardware exactly are you running and what packages did you update. Have you tried  using some sis drivers? Have a look at https://wiki.archlinux.org/index.php/SiS
How are you starting X? Does starting X as root (the old way) help?

Offline

#4 2014-08-04 11:08:03

nbd
Member
Registered: 2014-08-04
Posts: 389

Re: [SOLVED]Screen resolution began to be incorrectly detected

I tried the 'xf86-video-sis' from the official repositories, but it didn't work: 'X -configure' outputs that no devices are found.

The command

# lspci | grep SiS

gives the output:

00:00.0 Host bridge: Silicon Integrated Systems [SiS] 662 Host (rev 01)
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] AGP Port (virtual PCI-to-PCI bridge)
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS964 [MuTIOL Media IO] LPC Controller (rev 36)
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 IDE Controller (rev 01)
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] SiS7012 AC'97 Sound Controller (rev a0)
00:03.0 USB controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f)
00:03.1 USB controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f)
00:03.2 USB controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f)
00:03.3 USB controller: Silicon Integrated Systems [SiS] USB 2.0 Controller
00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 91)
00:05.0 IDE interface: Silicon Integrated Systems [SiS] SATA (rev 01)
00:1f.0 PCI bridge: Silicon Integrated Systems [SiS] PCI-to-PCI bridge
01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter (rev 04)

The command 'X -configure' with the 'xf86-video-vesa' driver produces the following xorg.conf file:

Section "ServerLayout"
	Identifier     "X.org Configured"
	Screen      0  "Screen0" 0 0
	InputDevice    "Mouse0" "CorePointer"
	InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
	ModulePath   "/usr/lib/xorg/modules"
	FontPath     "/usr/share/fonts/misc/"
	FontPath     "/usr/share/fonts/TTF/"
	FontPath     "/usr/share/fonts/OTF/"
	FontPath     "/usr/share/fonts/Type1/"
	FontPath     "/usr/share/fonts/100dpi/"
	FontPath     "/usr/share/fonts/75dpi/"
EndSection

Section "Module"
	Load  "glx"
EndSection

Section "InputDevice"
	Identifier  "Keyboard0"
	Driver      "kbd"
EndSection

Section "InputDevice"
	Identifier  "Mouse0"
	Driver      "mouse"
	Option	    "Protocol" "auto"
	Option	    "Device" "/dev/input/mice"
	Option	    "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
	Identifier   "Monitor0"
	VendorName   "Monitor Vendor"
	ModelName    "Monitor Model"
EndSection

Section "Device"
        ### Available Driver options are:-
        ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
        ### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
        ### <percent>: "<f>%"
        ### [arg]: arg optional
        #Option     "ShadowFB"           	# [<bool>]
        #Option     "DefaultRefresh"     	# [<bool>]
        #Option     "ModeSetClearScreen" 	# [<bool>]
	Identifier  "Card0"
	Driver      "vesa"
	BusID       "PCI:1:0:0"
EndSection

Section "Screen"
	Identifier "Screen0"
	Device     "Card0"
	Monitor    "Monitor0"
	SubSection "Display"
		Viewport   0 0
		Depth     1
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     4
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     8
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     15
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     16
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     24
	EndSubSection
EndSection

The X server is started via startxfce4 in the ~/.xinitrc file:

#!/bin/sh
#
# ~/.xinitrc
#

if [ -d /etc/X11/xinit/xinitrc.d ]; then
  for f in /etc/X11/xinit/xinitrc.d/*; do
    [ -x "$f" ] && . "$f"
  done
  unset f
fi

exec startxfce4

I tried to use the recommendations about using xrandr. The command

# cvt 1280 1024

produces the following:

# 1280x1024 59.89 Hz (CVT 1.31M4) hsync: 63.67 kHz; pclk: 109.00 MHz
Modeline "1280x1024_60.00"  109.00  1280 1368 1496 1712  1024 1027 1034 1063 -hsync +vsync


Then I perfrom the following two commands:

# xrandr --newmode "1280x1024_60.00"  109.00  1280 1368 1496 1712  1024 1027 1034 1063 -hsync +vsync

# xrandr --addmode default "1280x1024_60.00"

This adds the 1280x1024 mode to the list of available modes in the display control panel, but when
this mode is selected - nothing happens and the resolution remains the same: 1024x768.

EDIT:

I tried all three SiS drivers from the repository: sis, sisusb and sisimedia. In all three cases 'X -configure' failed with an error message: "No devices to configure". The strange thing is that the vesa driver worked OK out of the box. What could cause such a strange problem with the screen resolution?

EDIT 2:

The cause of the problem was the cable from the monitor to the computer: it was twisted and apparently was causing some aberrations to the signal. I found out it when added to the xorg.conf file the line HorizSync = 58-61. After adding that line the problem disappeared. I began to think why the things previously have been working OK without that line. And supposed that the matter is in hardware. I straighted out the cable and the problem isn't occuring anymore even without the xorg.conf editings.

Last edited by nbd (2014-08-04 17:58:13)

bing different

Offline

#5 2014-08-04 23:50:31

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Re: [SOLVED]Screen resolution began to be incorrectly detected

Is everything working again?
If so, please remember to mark the thread as solved https://bbs.archlinux.org/viewtopic.php?id=130309

Offline

Pages: 1

Board footer

Powered by FluxBB