You are not logged in.
I have an Intel Corporation 82845G/GL video card and with the last pacman update I replaced xf86-video-intel-legacy driver (which I used without xorg.conf) with xf86-video-intel, experiencing some issues (Xorg crashes, wrong resolution and refresh rate, strange dpi settings).
I solved these issues activating kms:
1 - adding "i915.modeset=1" to the kernel commandline and removing all "vga=" and "video=" options in /boot/grub/menu.lst
and
2 - adding "intel_agp i915" to MODULES section in /etc/mkinitcpio.conf: MODULES="... intel_agp i915"...and then setting the correct monitor resolution for my Samsung monitor with xrandr (following this how to "https://wiki.ubuntu.com/X/Config/Resolution").
This helped me to get X working, but glxgears gives Segmentation fault.
dmesg shows
glxgears[14526]: segfault at 1300 ip b735b084 sp bf83de20 error 4 in libdricore.so[b726a000+206000]
So probably things aren't still quite as they should be.
PS. remove the solved tag.
Offline
This helped me to get X working, but glxgears gives Segmentation fault.
dmesg showsglxgears[14526]: segfault at 1300 ip b735b084 sp bf83de20 error 4 in libdricore.so[b726a000+206000]
So probably things aren't still quite as they should be.
remove the solved tag.
I must be lucky then, glxgears works well too
Offline
Did a complete reinstall, everything works fine now!
Offline
Yeah I had no problems with the latest xorg & intel revisions - just read the wiki before upgrading, quite pleased!
The last major update caused some headaches (dreadful performance) so I went back to the legacy intel drivers for a number of months.
All is well now though
-//------------------/------>
Offline
Thank you, macroscan, for your working cure for 82845G/GL.
Unfortunately, The problem IS NOT SOLVED for those with a 82852/82855 GM/GME chip.
There are no error markers in xorg.0.log, when using a correct xorg.conf.
Disabling xorg.conf leads to error markers for missing /dev/fb0 predeceed by warnig markers for vesa nad fbdev ('falling back to old probe method...'). There must be some wrong method of invoking fb driver (first loaded fbdev, after WWs loaded fbdevhw. The versions are 2.9.1 for intel driver, 2.2.1 for vesa driver, 0.4.1 for fbdev driver (according the log). Hal says to xorg, that there are three devices and screens (intel, vesa, fbdev). For all three screens a default monitor is used. Modules succesfully loaded are extmod, dbe, glx with aiglx, recorg, dri, dri2, intel and vesa. Module fbdev with fbdevhw seems failing in creation od fb0.
Note: After EE marker for missing /dev/fb0 a vga and ramdac submodules were loaded. The last two rows od xorg.0.log tell about drmOpenDevice (/dev/dri/card0) and open result 8.
That's all I can tell about the environment of the xorg failure. Any idea, JGC?
Last edited by pjezek (2009-11-25 15:03:31)
Our tomcat for your mice! Archlinux for your comps! Alfa Romeo for your roads! Faster running guaranted!
Offline