Arch Linux

nybegynner

Member

From: Norway

Registered: 2010-02-07

Posts: 36

[SOLVED] Angry resolutions

I'm experiencing some strange issues with the resolution on my arch.
1. Randomly, during boot, the screen resolution is changed to somewhat a little window in the upper left part of my screen and stays that way if I'm only using the tty. This is bearable, but annoing.
2. The real problem is sometimes when i start the X server, it randomly changes the resolution to a smaller screen. I've come around this by "resetting" the X server resolution by killing it manually, but this is not good for my computer.
Some info:

lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)

Intel drivers

pacman -Q | grep intel
intel-dri 7.9.0.git20101207-2
xf86-video-intel 2.13.0-4

Xorg.0.log:

tail -50 /var/log/Xorg.0.log
[    44.720] (**) Option "xkb_model" "evdev"
[    44.720] (**) Option "xkb_layout" "no"
[    44.720] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event8)
[    44.720] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
[    44.720] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[    44.720] (II) LoadModule: "synaptics"
[    44.721] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[    44.722] (II) Module synaptics: vendor="X.Org Foundation"
[    44.722]     compiled for 1.9.2, module version = 1.3.0
[    44.722]     Module class: X.Org XInput Driver
[    44.722]     ABI class: X.Org XInput driver, version 11.0
[    44.722] (II) Synaptics touchpad driver version 1.3.0
[    44.722] (**) Option "Device" "/dev/input/event8"
[    44.843] (--) SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5580
[    44.843] (--) SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4796
[    44.843] (--) SynPS/2 Synaptics TouchPad: pressure range 0 - 255
[    44.843] (--) SynPS/2 Synaptics TouchPad: finger width range 0 - 15
[    44.843] (--) SynPS/2 Synaptics TouchPad: buttons: left right
[    44.843] (**) Option "TapButton1" "1"
[    44.843] (**) Option "TapButton2" "2"
[    44.843] (**) Option "TapButton3" "3"
[    44.950] (--) SynPS/2 Synaptics TouchPad: touchpad found
[    44.950] (**) SynPS/2 Synaptics TouchPad: always reports core events
[    45.003] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD)
[    45.003] (**) SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
[    45.003] (**) SynPS/2 Synaptics TouchPad: MaxSpeed is now 1.75
[    45.003] (**) SynPS/2 Synaptics TouchPad: AccelFactor is now 0.038
[    45.003] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[    45.003] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
[    45.003] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[    45.003] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[    45.083] (--) SynPS/2 Synaptics TouchPad: touchpad found
[    45.083] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
[    45.083] (II) No input driver/identifier specified (ignoring)
[    45.084] (II) config/udev: Adding input device ST LIS3LV02DL Accelerometer (/dev/input/event6)
[    45.084] (II) No input driver/identifier specified (ignoring)
[    45.084] (II) config/udev: Adding input device ST LIS3LV02DL Accelerometer (/dev/input/js0)
[    45.084] (II) No input driver/identifier specified (ignoring)
[    45.084] (II) config/udev: Adding input device PC Speaker (/dev/input/event4)
[    45.084] (II) No input driver/identifier specified (ignoring)
[    45.085] (II) config/udev: Adding input device HP WMI hotkeys (/dev/input/event5)
[    45.085] (**) HP WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[    45.086] (**) HP WMI hotkeys: always reports core events
[    45.086] (**) HP WMI hotkeys: Device: "/dev/input/event5"
[    45.110] (--) HP WMI hotkeys: Found keys
[    45.110] (II) HP WMI hotkeys: Configuring as keyboard
[    45.110] (II) XINPUT: Adding extended input device "HP WMI hotkeys" (type: KEYBOARD)
[    45.110] (**) Option "xkb_rules" "evdev"
[    45.110] (**) Option "xkb_model" "evdev"
[    45.110] (**) Option "xkb_layout" "no"

Any help is appreciated!

Last edited by nybegynner (2010-12-22 22:48:59)

Gusar

Member

Registered: 2009-08-25

Posts: 3,605

Re: [SOLVED] Angry resolutions

Your first problem, and maybe the second one too, is usually a symptom of false detection of TV-out. Try explicitly disabling TV-out on the kernel commandline:

video=SVIDEO-1:d

Check in /sys/class/drm, maybe it's something other than SVIDEO-1, but it's usually that.

nybegynner

Member

From: Norway

Registered: 2010-02-07

Posts: 36

Re: [SOLVED] Angry resolutions

Ok, mine was located at /sys/class/drm/card0-SVIDEO-1. I ran the command and disabled it, but after reboot the issue still there and the the TV-out is enabled. Any ideas?

Gusar

Member

Registered: 2009-08-25

Posts: 3,605

Re: [SOLVED] Angry resolutions

What command exactly did you use? Only the SVIDEO-1 part matters, as I wrote it, not the card0 part. The command should work, it has for others before.

nybegynner

Member

From: Norway

Registered: 2010-02-07

Posts: 36

Re: [SOLVED] Angry resolutions

I issued the command:

 video=SVIDEO-1:d 

and I checked the status witch then was "disconnected", but after reboot the status was "connected" again. How can I do this step before or during boot to prevent the issue?

skunktrader

Member

From: Brisbane, Australia

Registered: 2010-02-14

Posts: 1,543

Re: [SOLVED] Angry resolutions

I think he meant for you to reboot and then pass that as a command line argument when you start the kernel

nybegynner

Member

From: Norway

Registered: 2010-02-07

Posts: 36

Re: [SOLVED] Angry resolutions

I think he meant for you to reboot and then pass that as a command line argument when you start the kernel

Ok, how do I pass an argument to the kernel?

Gusar

Member

Registered: 2009-08-25

Posts: 3,605

Re: [SOLVED] Angry resolutions

Ok, how do I pass an argument to the kernel?

In /boot/grub/menu.lst (assuming you're using grub), add the command to the line that starts with 'kernel'

nybegynner

Member

From: Norway

Registered: 2010-02-07

Posts: 36

Re: [SOLVED] Angry resolutions

Thank you! That did the trick.