x220 X Screen Cut Off

stantheman286 · 2011-08-16 03:02:59

Hi,

I installed Arch on my x220 and when I boot Gnome with the stock (2.6) kernel, the desktop fills the screen, although the resolution is off.

However, when I switched to using a custom compile of the 3.0.1 kernel, when I log into Gnome, my screen is shifted up, so the top 1/4 of my screen is cut off and the bottom 1/4 is just blank. I have installed vesa, fbdev and i915 and have the modules loaded, so I'm thinking it might be an X issue.

Any ideas?

Thanks guys!

Matt

BurntSushi · 2011-08-16 04:15:40

Have you tried using the "auto" feature on your monitor? It might fix things for you.

Otherwise, do you have an xorg.conf? If so, could you post it?

Could you also post the output of `xrandr`?

stantheman286 · 2011-08-16 04:51:56

How do I use the "auto" feature? I am using modules inside /etc/X11/xorg.conf.d/, I didn't try create a classic xorg.conf file like I did in Gentoo, but when I did, I just got a blank screen.

I'm rebuilding the kernel using the old config from my 2.6.34 kernel, so once I can, I will post the output of xrandr.

Thanks!

Matt

stantheman286 · 2011-08-16 06:26:30

Ok, here's a few more bits of my config, let me know if you need anything else:

xrandr:

Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
default connected 1024x768+0+0 0mm x 0mm
   1024x768        0.0*

10-evdev.conf:

# Catchall classes for input devices
# We don't simply match on any device since that also adds accelerometers
# and other devices that we don't really want to use. The list below
# matches everything but joysticks.

Section "InputClass"
        Identifier "evdev pointer catchall"
        MatchIsPointer "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
EndSection

Section "InputClass"
        Identifier "evdev keyboard catchall"
        MatchIsKeyboard "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
EndSection

Section "InputClass"
        Identifier "evdev tablet catchall"
        MatchIsTablet "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
EndSection

Section "InputClass"
        Identifier "evdev touchscreen catchall"
        MatchIsTouchscreen "on"
        MatchDevicePath "/dev/input/event*"
        Driver "evdev"
EndSection

10-monitor.conf:

Section "Monitor"
        Identifier "Monitor0"
#        Option "DPI" "125 x 125"
        DisplaySize 277 156
EndSection

Section "Device"
    Identifier    "Device0"
    Driver        "vesa" #Choose the driver used for this monitor
EndSection

Section "Screen"
    Identifier    "Screen0"  #Collapse Monitor and Device section to Screen section
    Device        "Device0"
    Monitor       "Monitor0"
    DefaultDepth  16 #Choose the depth (16||24)
    SubSection "Display"
        Depth     16
        Modes     "1200x800_75.00" #Choose the resolution
    EndSubSection
EndSection

Thanks!

Matt

bernarcher · 2011-08-16 06:49:23

stantheman286 wrote:

How do I use the "auto" feature?

I think BurntSushi refers to the OSD (On Screen Display) settings of the monitor itself. Most have a feature called "auto" or "auto align" which aligns and sometimes resizes the screen to the video signals the monitor receives.

This feature is not software related. Consult your monitor handbook.

stantheman286 · 2011-08-16 15:23:16

I looked for an "auto" feature for the x220 but couldn't find one. I tried the various Fn combinations, including trying to switch to an external monifor, but nothing automatically resized the screen. I posted my .conf files above, they don't look quite right to me. I'm a n00b when it comes to using xorg.conf.d/ instead of xorg.conf.

Matt

BurntSushi · 2011-08-16 19:58:24

Ah, I didn't know you were on a laptop, my bad. I don't think they exist on a laptop screen. But this is a strange issue.

A few ideas...

Get rid of 10-monitor.conf completely, and don't replace it with anything. (Make a backup somewhere if you like.) xrandr is saying that the max resolution of your laptop is 1024x768, but your 10-monitor.conf has 1200x800. Are you supposed to be able to run at something higher than 1024x768? If you are, then xrandr isn't seeing it and something is very off and you should consult the people that develop your video driver. (They will probably like to see the `xrandr` output and your Xorg log.)

Otherwise, you could also try this in X as a longshot:

xrandr --output default --auto

(The fact that your monitor is named "default" is strange to me.)

Last edited by BurntSushi (2011-08-16 19:59:19)

stantheman286 · 2011-08-16 20:21:29

Get rid of 10-monitor.conf completely, and don't replace it with anything. (Make a backup somewhere if you like.) xrandr is saying that the max resolution of your laptop is 1024x768, but your 10-monitor.conf has 1200x800

Tried it and it shifted my screen a little bit, but still off. The 1200x800 was my bad, I was messing with the resolution to see if I could fix the screen.

Are you supposed to be able to run at something higher than 1024x768?

Yea, 1366 x 768 is the max resolution. It's an Intel i915 based controller, so I have to believe that I either forgot to load a module or didn't add it to my new kernel entirely. I used this site to help set up my kernel, so I must be missing something: http://www.thinkwiki.org/wiki/Installin … 0_hardware. I loaded the old 2.6 kernel also and did an lsmod to see what was loaded, but I didn't see anything graphics related that was different between that and my 3.0.1 kernel.

Thanks!
Matt

MoonSwan · 2011-08-16 20:25:41

installed vesa, fbdev and i915 and have the modules loaded,

From the first post in this thread...If you look at the wiki, this particular driver should NOT be used in conjuction with framebuffer settings or uvesa. Perhaps this is being overlooked?

{Edit} found it! Perhaps this is part of your issue:

KMS is supported by Intel chipsets that use the i915 DRM driver and is now enabled by default as of kernel v2.6.32. Since xf86-video-intel 2.10, using KMS is mandatory. KMS is typically initialized after the kernel is bootstrapped. It is possible however to enable KMS during bootstrap itself, allowing the entire boot process to run at native resolution.
Note: When using KMS, you must remove any references to "vga" or "video" from the kernel line in /boot/grub/menu.lst

Taken from here:

https://wiki.archlinux.org/index.php/Intel

Follow that guide and see if it helps?

Last edited by MoonSwan (2011-08-16 20:30:59)

stantheman286 · 2011-08-16 20:35:28

Hey MoonSwan,

Yea, I just found that section last night, so I updated to make sure I was using KMS properly. I unloaded all those modules and tried to boot X again and it's still cut off. It's funny, b/c my framebuffer looks good, the text fills the whole screen while booting, it's just X that's the issue...

Thanks!

Matt

Arch Linux

#1 2011-08-16 03:02:59

x220 X Screen Cut Off

#2 2011-08-16 04:15:40

Re: x220 X Screen Cut Off

#3 2011-08-16 04:51:56

Re: x220 X Screen Cut Off

#4 2011-08-16 06:26:30

Re: x220 X Screen Cut Off

#5 2011-08-16 06:49:23

Re: x220 X Screen Cut Off

#6 2011-08-16 15:23:16

Re: x220 X Screen Cut Off

#7 2011-08-16 19:58:24

Re: x220 X Screen Cut Off

#8 2011-08-16 20:21:29

Re: x220 X Screen Cut Off

#9 2011-08-16 20:25:41

Re: x220 X Screen Cut Off

#10 2011-08-16 20:35:28

Re: x220 X Screen Cut Off

Board footer