[SOLVED]xf86-video-intel 2.10 on eeepc 1000 and broken gdm or xorg

liticovjesac · 2010-02-16 08:47:32

Hi everyone
after latest update my gdm is broken. First i downgraded gdm , nothing happened. Then my guess was intel video driver. When I downgraded xf86-video-intel 2.10 to 2.9 everything works fine. Did that happen to anyone else? Any solution except downgrade?

Last edited by liticovjesac (2010-02-22 06:47:40)

hw-tph · 2010-02-17 08:11:39

Can you start X from the console (i.e. by using startx)?

If you have disabled Intel kernel modesetting X will fail, so check that you haven't disabled it on the kernel line in your grub configuration file.

liticovjesac · 2010-02-17 21:06:15

No, stratx , org gdm doesnt work. Message that i got is :

gdm-binary.[1327]: WARNING: GdmDisplay lasted 0.115826 seconds

for 4 times
and at the end

gdmLocalDisplayFactory: maximum number of X display failures reached. check X server log for errors

Xorg log says only at one place

Fatal server error:
no screens found

i am still on kernel 31 and I dont have anything in my grub menu list except path to the kernel

hw-tph · 2010-02-17 21:50:20

What are the errors listed in the X.org log file (/var/log/Xorg.0.log)? Error messages are prefixed with the characters (EE) in order to make them easier to spot, but make sure to pay attention to surrounding lines as well.

liticovjesac · 2010-02-17 22:28:36

this is xorg log

This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.

X.Org X Server 1.7.4.901 (1.7.5 RC 1)
Release Date: 2010-01-23
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.32-ARCH i686 
Current Operating System: Linux vampir 2.6.31-ARCH #1 SMP PREEMPT Tue Nov 10 19:48:17 CET 2009 i686
Kernel command line: root=/dev/disk/by-uuid/43e163d6-4812-45ca-80dc-627c201f315f ro
Build Date: 31 January 2010  11:40:13AM
 
Current version of pixman: 0.16.4
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Wed Feb 17 22:45:50 2010
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "X.org Configured"
(**) |-->Screen "Screen0" (0)
(**) |   |-->Monitor "Monitor0"
(**) |   |-->Device "Card0"
(**) |-->Input Device "Mouse0"
(**) |-->Input Device "Keyboard0"
(**) |-->Input Device "synaptics"
(==) Automatically adding devices
(==) Automatically enabling devices
(**) FontPath set to:
    /usr/share/fonts/misc,
    /usr/share/fonts/100dpi:unscaled,
    /usr/share/fonts/75dpi:unscaled,
    /usr/share/fonts/TTF,
    /usr/share/fonts/Type1,
    /usr/share/fonts/misc,
    /usr/share/fonts/100dpi:unscaled,
    /usr/share/fonts/75dpi:unscaled,
    /usr/share/fonts/TTF,
    /usr/share/fonts/Type1
(**) ModulePath set to "/usr/lib/xorg/modules"
(WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
(WW) Disabling Mouse0
(WW) Disabling Keyboard0
(II) Loader magic: 0x81e5100
(II) Module ABI versions:
    X.Org ANSI C Emulation: 0.4
    X.Org Video Driver: 6.0
    X.Org XInput driver : 7.0
    X.Org Server Extension : 2.0
(--) using VT number 7

(--) PCI:*(0:0:2:0) 8086:27ae:1043:8340 Intel Corporation Mobile 945GME Express Integrated Graphics Controller rev 3, Mem @ 0xf7f00000/524288, 0xd0000000/268435456, 0xf7ec0000/262144, I/O @ 0x0000dc00/8
(--) PCI: (0:0:2:1) 8086:27a6:1043:8340 Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller rev 3, Mem @ 0xf7f80000/524288
(II) Open ACPI successful (/var/run/acpid.socket)
(II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
(II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
(II) "glx" will be loaded. This was enabled by default and also specified in the config file.
(II) "dri" will be loaded. This was enabled by default and also specified in the config file.
(II) "dri2" will be loaded by default.
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
    compiled for 1.7.4.901, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
    compiled for 1.7.4.901, module version = 1.0.0
    Module class: X.Org Server Extension
    ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "xtrap"
(WW) Warning, couldn't open module xtrap
(II) UnloadModule: "xtrap"
(EE) Failed to load module "xtrap" (module does not exist, 0)
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions/libglx.so
(II) Module glx: vendor="X.Org Foundation"
    compiled for 1.7.4.901, module version = 1.0.0
    ABI class: X.Org Server Extension, version 2.0
(==) AIGLX enabled
(II) Loading extension GLX
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions/libdri.so
(II) Module dri: vendor="X.Org Foundation"
    compiled for 1.7.4.901, module version = 1.0.0
    ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "synaptics"
(II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
(II) Module synaptics: vendor="X.Org Foundation"
    compiled for 1.7.3, module version = 1.2.1
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 7.0
(II) LoadModule: "dri2"
(II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
    compiled for 1.7.4.901, module version = 1.1.0
    ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "intel"
(II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
(II) Module intel: vendor="X.Org Foundation"
    compiled for 1.7.4.901, module version = 2.10.0
    Module class: X.Org Video Driver
    ABI class: X.Org Video Driver, version 6.0
(II) LoadModule: "synaptics"
(II) Reloading /usr/lib/xorg/modules/input/synaptics_drv.so
(II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
    i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G,
    E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
    965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
    4 Series, G45/G43, Q45/Q43, G41, B43, Clarkdale, Arrandale
(II) Primary Device is: PCI 00@00:02:0
(WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
(EE) intel(0): No kernel modesetting driver detected.
(II) UnloadModule: "intel"
(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found

Please consult the The X.Org Foundation support 
     at http://wiki.x.org
 for help. 
Please also check the log file at "/var/log/Xorg.1.log" for additional information.

What No kernel modesetting driver detected means?

I added intel driver line to MODULES in mkinitcpio, rebuild kernel (i am still running 31 because of problems with wireless) but no progress with latest intel driver.

combuster · 2010-02-17 22:37:47

You need intel_agp also in mkinitcpio.conf... With the latest video-intel KMS is a must so you need to enable it propperly in 2.6.31...

liticovjesac · 2010-02-18 06:26:06

I had both arguments in modules line in mkinitcpio.conf when I rebuild kernel so it must be something else that i am missing.

kokoko3k · 2010-02-18 09:01:24

Try to post your /boot/grub/menu.lst

liticovjesac · 2010-02-18 09:25:45

This is my menu.lst Very straight forward

# Config file for GRUB - The GNU GRand Unified Bootloader
# /boot/grub/menu.lst

# DEVICE NAME CONVERSIONS 
#
#  Linux           Grub
# -------------------------
#  /dev/fd0        (fd0)
#  /dev/sda        (hd0)
#  /dev/sdb2       (hd1,1)
#  /dev/sda3       (hd0,2)
#

#  FRAMEBUFFER RESOLUTION SETTINGS
#     +-------------------------------------------------+
#          | 640x480    800x600    1024x768   1280x1024
#      ----+--------------------------------------------
#      256 | 0x301=769  0x303=771  0x305=773   0x307=775
#      32K | 0x310=784  0x313=787  0x316=790   0x319=793
#      64K | 0x311=785  0x314=788  0x317=791   0x31A=794
#      16M | 0x312=786  0x315=789  0x318=792   0x31B=795
#     +-------------------------------------------------+
#  for more details and different resolutions see
#  http://wiki.archlinux.org/index.php/GRUB#Framebuffer_Resolution 

# general configuration:
timeout   5
default   0
color light-blue/black light-cyan/blue

# boot sections follow
# each is implicitly numbered from 0 in the order of appearance below
#
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
#
#-*

# (0) Arch Linux
title  Arch Linux
root   (hd0,0)
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/43e163d6-4812-45ca-80dc-627c201f315f ro
initrd /boot/kernel26.img

# (1) Arch Linux
title  Arch Linux Fallback
root   (hd0,0)
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/43e163d6-4812-45ca-80dc-627c201f315f ro
initrd /boot/kernel26-fallback.img

# (2) Windows
#title Windows
#rootnoverify (hd0,0)
#makeactive
#chainloader +1

kokoko3k · 2010-02-18 11:01:54

Nothing special, d'you have native resolution in console (read: is kms enabled in console too?)
If not, that's the root of the problem, which means you probably made some mistake(s):
http://wiki.archlinux.org/index.php/Int … Setting.29
try to do it again.

Last edited by kokoko3k (2010-02-18 11:04:56)

liticovjesac · 2010-02-18 11:59:42

Well i cant tell that I have native resolution in console because everything seems same as before I "enable" KMS. I followed same link that u gave me and I will try it to do again.

As I understand kernel option "i915.modeset=1" is optional just if u want more easy way to enable/disable KMS without rebuilding kernel?

Just to add some info. My computer is eeepc 1000h, with xorg.conf (it did't work without that)

kokoko3k · 2010-02-18 12:07:09

i've a 1005ha and no (well, not yours) problems with Xorg.
Check the size of your console text against the grub one, if they are about the same, then kms is definitely not enabled.

liticovjesac · 2010-02-18 16:20:46

I have done everything again but no luck.
Controled mkinitcpio.conf
add i915.modeset=1 to the menu.lst
removed xorg.conf
rebuild kernel
and same error again. So xf86-video-intel is on the ignore list.

Only thing that is new is that computer now works without xorg.conf

Thanks for the help.

kokoko3k · 2010-02-18 18:03:07

mmh, check in your dmesg output for something like this:

[drm] Initialized drm 1.1.0 20060810                                                                  
i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16                                         
i915 0000:00:02.0: setting latency timer to 64                                                        
[drm] set up 7M of stolen space                                                                       
[drm] LVDS-8: set mode 1024x600 e                                                                     
Console: switching to colour frame buffer device 128x37                                               
fb0: inteldrmfb frame buffer device                                                                   
registered panic notifier                                                                             
[drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0

merleblue · 2010-02-20 01:33:16

I don't know if this will solve all the problems mentioned here, but I have come across messages similar to:

fb0: inteldrmfb frame buffer device                                                                   
registered panic notifier

when I was doing some kernel customization. For me, the symptom was a flash of the screen during boot, and the logos would disappear. I fixed the problem by unsetting the CONFIG_DRM_I915_KMS kernel option. It is located under the menu:
-> Device Drivers
-> Graphic support
-> Direct Rendering Manager (XFree86...)
I also tried leaving that option set, but unsetting the VESA VGA graphics support option under the "Support for frame buffer devices" menu, but doing that unsets the
CONFIG_FB_BOOT_VESA_SUPPORT option and renders the screen useless, even after boot.
Don't forget to run "mkinitcpio" after installing the kernel and modules.
I hope this helps.

liticovjesac · 2010-02-21 14:55:26

Only message connected with drm is one that drm is activated. Thou i got some other error like:

i915: Unknown parameter `modset'

and another one:

ERROR!!! RTMPCancellTimer failed, Timer hasn't been initialize!

Since removing xorg.conf and enebleing KMS I got now flickering of whole screen every now and then. So back to xorg.xonf and maybe I will remove even KMS since i dont need it really (no 3d, no games..)

@merleblue
I really dont understand what have u done and i cant find the path that u provided (menu->device drivers->...)

hw-tph · 2010-02-21 20:15:35

liticovjesac wrote:

@merleblue
I really dont understand what have u done and i cant find the path that u provided (menu->device drivers->...)

merleblue refers to the location in the Linux kernel configuration program(s) where you would find the CONFIG_DRM_I915_KMS option. You said in an earlier post you rebuilt your kernel, so I (and I assume merleblue) got the impression you know your way about make menuconfig.

Is there any particular reason you build your own kernel as opposed to the standard kernel26 from Arch Linux? It works very well in most cases and on most hardware. Using the stock kernel makes it a ton easier to get answers to your problems as well.

liticovjesac wrote:

i915: Unknown parameter `modset'

That would be because you have a typo somewhere, presumable on your kernel line in grub's menu.lst. It's "modeset", not "modset".

Last edited by hw-tph (2010-02-21 20:17:04)

merleblue · 2010-02-21 22:30:02

Why was I compiling my own kernel? ...

I found that framebuffer problem when I was working with another distro (sidux), trying to learn how to build a kernel that could boot without an initrd, just to see how it's done. I did it again with the Archlinux kernel because of the same problem, which happened in the unaltered kernel that was installed when I updated recently. Something seems to have changed in the 2.6.32.8 kernel that everyone uses. I hate to see my console flash like it does without that fix. And I like seeing the little Arch logos during boot. That is the only change I have made in the Arch kernel. You're right, it seems pretty solid, otherwise.

liticovjesac · 2010-02-22 06:47:09

Sorry, rebuilding kernel is a Freudian slip since I have been reading and thinking about doing that. I am still using standard kernel.

It was a typo in the menu.lst. I feel stupid. KMS is enabled and 2.10 intel driver is working. I am really sorry because of this.
On the other hand I can confirm that KMS did not work without adding i915.modeset=1 to the menu.lst
Thanks everyone.

kokoko3k · 2010-02-22 08:26:30

Strange it doesn't, i don't add any additional parameter to grub string.
Glad you solved, by the way.

hw-tph · 2010-02-22 13:58:11

merleblue: My question about the manual kernel compilation was directed at the OP to try to solve the problem at hand. I did not question your motives.

liticovjesac: Great to hear you got it sorted.

merleblue · 2010-02-22 14:31:32

hw-tph: I did not mean to sound upset, and I wasn't bothered by your question. But thanks for taking the time to say something. I've only been using Arch for about a week, and I have been pretty pleased with the tone (and quality) of the online documentation and the forum. There are so many steps involved in waking up Linux, I thought that if the fb clash reported by kokoko3k was the same as my problem, it might at least eliminate one thing for liticovjesac to look at.

Arch Linux

#1 2010-02-16 08:47:32

[SOLVED]xf86-video-intel 2.10 on eeepc 1000 and broken gdm or xorg

#2 2010-02-17 08:11:39

Re: [SOLVED]xf86-video-intel 2.10 on eeepc 1000 and broken gdm or xorg

#3 2010-02-17 21:06:15

Re: [SOLVED]xf86-video-intel 2.10 on eeepc 1000 and broken gdm or xorg

#4 2010-02-17 21:50:20

Re: [SOLVED]xf86-video-intel 2.10 on eeepc 1000 and broken gdm or xorg

#5 2010-02-17 22:28:36

Re: [SOLVED]xf86-video-intel 2.10 on eeepc 1000 and broken gdm or xorg

#6 2010-02-17 22:37:47

Re: [SOLVED]xf86-video-intel 2.10 on eeepc 1000 and broken gdm or xorg

#7 2010-02-18 06:26:06

Re: [SOLVED]xf86-video-intel 2.10 on eeepc 1000 and broken gdm or xorg

#8 2010-02-18 09:01:24

Re: [SOLVED]xf86-video-intel 2.10 on eeepc 1000 and broken gdm or xorg

#9 2010-02-18 09:25:45

Re: [SOLVED]xf86-video-intel 2.10 on eeepc 1000 and broken gdm or xorg

#10 2010-02-18 11:01:54

Re: [SOLVED]xf86-video-intel 2.10 on eeepc 1000 and broken gdm or xorg

#11 2010-02-18 11:59:42

Re: [SOLVED]xf86-video-intel 2.10 on eeepc 1000 and broken gdm or xorg

#12 2010-02-18 12:07:09

Re: [SOLVED]xf86-video-intel 2.10 on eeepc 1000 and broken gdm or xorg

#13 2010-02-18 16:20:46

Re: [SOLVED]xf86-video-intel 2.10 on eeepc 1000 and broken gdm or xorg

#14 2010-02-18 18:03:07

Re: [SOLVED]xf86-video-intel 2.10 on eeepc 1000 and broken gdm or xorg

#15 2010-02-20 01:33:16

Re: [SOLVED]xf86-video-intel 2.10 on eeepc 1000 and broken gdm or xorg

#16 2010-02-21 14:55:26

Re: [SOLVED]xf86-video-intel 2.10 on eeepc 1000 and broken gdm or xorg

#17 2010-02-21 20:15:35

Re: [SOLVED]xf86-video-intel 2.10 on eeepc 1000 and broken gdm or xorg

#18 2010-02-21 22:30:02

Re: [SOLVED]xf86-video-intel 2.10 on eeepc 1000 and broken gdm or xorg

#19 2010-02-22 06:47:09

Re: [SOLVED]xf86-video-intel 2.10 on eeepc 1000 and broken gdm or xorg

#20 2010-02-22 08:26:30

Re: [SOLVED]xf86-video-intel 2.10 on eeepc 1000 and broken gdm or xorg

#21 2010-02-22 13:58:11

Re: [SOLVED]xf86-video-intel 2.10 on eeepc 1000 and broken gdm or xorg

#22 2010-02-22 14:31:32

Re: [SOLVED]xf86-video-intel 2.10 on eeepc 1000 and broken gdm or xorg

Board footer