You are not logged in.
I try to update xorg-server this weekend but pacman shows that it is incompatible with my current xf86 video module.
My HP DV1040 notebook doesn´t work with xf86-video-intel neither xf86-video-vesa, it only works with xf86-video-intel-legacy.
Is there a way so I can install xorg-server 1.7 ?
Regards
Last edited by htierno (2009-11-02 13:10:05)
Offline
The xf86-video-intel-legacy driver is deprecated and hasn't been updated since May, so it won't work with the new xorg. Whats the problem with the vesa driver?
Offline
Did you actually try the 2.9.1 driver, with or without KMS?
Offline
Offline
xf86-video-intel never worked for me, I only get a black screen, the same with the vesa drivers.
I´ve never look much in log files because the legacy module worked like a charmed (until yesterday with xorg-server 1.7)
Where do I have to start looking ?
Thanks
Offline
Did you actually try the 2.9.1 driver, with or without KMS?
I don´t know about KMS. But actually the intel driver never worked for me since I installed arch in last may.
Offline
By the way, lspci |grep -i vga throws this:
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
Offline
Actually the behavior with vesa driver is different than intel driver. With intel driver I get a black screen and a complete system lock down. With vesa driver I get a black screen too but I can switch to another terminal and login.
Offline
I've exactly the same problem. Same 82852/855GM Integrated Graphics Device...
Offline
xf86-video-intel never worked for me, I only get a black screen, the same with the vesa drivers.
I´ve never look much in log files because the legacy module worked like a charmed (until yesterday with xorg-server 1.7)
The legacy module is so far behind, it will probably not work for long (if it still does, that is) and simply go away.
Where do I have to start looking ?
1.) If you don't know about KMS or anything else related to X, look here: http://wiki.archlinux.org/index.php/Intel_Graphics (unfortunately, it is a bit outdated) and here: http://wiki.archlinux.org/index.php/Xorg
2.) Do you use an xorg.conf? If yes, post it. Also, try without an xorg.conf.
3.) Try with and without KMS.
4.) Try the vesa driver.
5.) Try disabling compositing if you use it.
6.) You should try to find out whether it is the driver or the X server which causes the crash (i.e. try upgrading only one of them, then the other way around).
7.) Check not only Xorg.0.log, but also dmesg
8.) check bugs.freedesktop.org
Edit: added stuff
Last edited by mutlu_inek (2009-11-02 04:23:10)
Offline
I'm in a similar case. I used xf86-video-intel-legacy.
I tried xf86-video-vesa but can't use compositing with it. I tried xf86-video-intel it's better in the way that my WM looks like before but I get long time response (nearly 3 or 4 seconds between each image) whereas glxgears tels me something about 950 FPS.
If I try with a xorg.conf I get an error message during bootup which says:
"x responding too fast. disabling for 5 minutes"
I don't know what to do.
Offline
vesa is not a long term solution, but it should at least work. What is you startup proceure - login manager, inittab or console?
Good ideas do not need lots of lies told about them in order to gain public acceptance.
Offline
htierno wrote:xf86-video-intel never worked for me, I only get a black screen, the same with the vesa drivers.
I´ve never look much in log files because the legacy module worked like a charmed (until yesterday with xorg-server 1.7)The legacy module is so far behind, it will probably not work for long (if it still does, that is) and simply go away.
htierno wrote:Where do I have to start looking ?
1.) If you don't know about KMS or anything else related to X, look here: http://wiki.archlinux.org/index.php/Intel_Graphics (unfortunately, it is a bit outdated) and here: http://wiki.archlinux.org/index.php/Xorg
2.) Do you use an xorg.conf? If yes, post it. Also, try without an xorg.conf.
3.) Try with and without KMS.
4.) Try the vesa driver.
5.) Try disabling compositing if you use it.
6.) You should try to find out whether it is the driver or the X server which causes the crash (i.e. try upgrading only one of them, then the other way around).
7.) Check not only Xorg.0.log, but also dmesg
If I delete the file Xorg.0.log and restart with the intel driver the file doesn´t regenerate and since my system is unresponsive I can´t look at dmesg. Then I restart in runlevel 3 but everything normal in dmesg.8.) check bugs.freedesktop.org
I will.Edit: added stuff
2.) Do you use an xorg.conf? If yes, post it. Also, try without an xorg.conf.
I don´t
3.) Try with and without KMS.
I´ll try this but the intel driver never worked for me, even when KMS wasn´t available.
4.) Try the vesa driver.
I already did. It doesn´t work either but in a different way. I will try to get the intel driver working first, if I can´t I will try this driver.
5.) Try disabling compositing if you use it.
Don´t know about this.
6.) You should try to find out whether it is the driver or the X server which causes the crash (i.e. try upgrading only one of them, then the other way around).
If I keep the xorg-server 1.6 and update from the legacy driver to the intel driver I get the same results. The driver is the issue maybe it doesn´t work with my graphics chipset. (Actually the driver says i810/i830/i915/945G/G965+ but no 855GM so is the legacy but the later worked fine) and maybe my only hope is the vesa driver.
Thanks for replying.
Offline
my only hope is the vesa driver
I'd use vesa only as a debugging aid to see if you can get the regular intel driver to work. If you cannot you're much better off downgrading than running xorg 1.7 with a vesa driver.
Good ideas do not need lots of lies told about them in order to gain public acceptance.
Offline
I can boot with a ubuntu 9.04 live CD and it´s using intel driver, so it has to be a configuration problem in arch. I´ll try to boot up with ubuntu againt in runlevel 3 and generate a xorg.conf file (the one I generate in arch doesn´t work either)
Offline
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").
3 - xrandr shows you the names of different outputs available on your system (LVDS, VGA-0, etc.) and resolutions available on each:
$ xrandr
4 - create the modeline for your resolution using "gtf" (in my case a resolution of 1440x900 pixel with refresh rate of 75Hz):
$ gtf 1440 900 75
This returns an output similar to this one:
$ # 1440x900 @ 75.00 Hz (GTF) hsync: 70.50 kHz; pclk: 136.49 MHz
Modeline "1440x900_75.00" 136.49 1440 1536 1688 1936 900 901 904 940 -HSync +Vsync
5 - create a new mode, copying the information after the word "Modeline" into the xrandr command:
$ xrandr --newmode "1440x900_75.00" 136.49 1440 1536 1688 1936 900 901 904 940 -HSync +Vsync
6 - add and activate the new mode (you have to replace VGA1 with the correct output name given by xrandr in - 1 -):
$ xrandr --addmode VGA1 1440x900_75.00
$ xrandr --output VGA1 --mode 1440x900_75.00
7 - to make xrandr settings persistent (without using xorg.conf), just add the 3 xrandr commands given in - 5 - and - 6 - to the file "/etc/gdm/PreSession/Default"
Hope this helps
Last edited by marcoscan (2009-11-02 19:46:05)
Offline
In a sense that's good news - if your graphics look good on ubuntu 9.04, you may not need the legacy driver.
But it doesn't mean that your configuration in arch is at fault. It's much more likely that it is the combination of xorg-server / intel driver.
Did you follow JGC's suggestion and try the new driver with and without KMS?
Last edited by grey (2009-11-02 13:06:12)
Good ideas do not need lots of lies told about them in order to gain public acceptance.
Offline
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").
3 - xrandr shows you the names of different outputs available on your system (LVDS, VGA-0, etc.) and resolutions available on each:
$ xrandr
4 - create the modeline for your resolution using "gtf" (in my case a resolution of 1440x900 pixel with refresh rate of 75Hz):
gtf 1440 900 75
This returns an output similar to this one:
# 1440x900 @ 75.00 Hz (GTF) hsync: 70.50 kHz; pclk: 136.49 MHz Modeline "1440x900_75.00" 136.49 1440 1536 1688 1936 900 901 904 940 -HSync +Vsync
5 - create a new mode, copying the information after the word "Modeline" into the xrandr command:
xrandr --newmode "1440x900_75.00" 136.49 1440 1536 1688 1936 900 901 904 940 -HSync +Vsync
6 - add and activate the new mode (you have to replace VGA1 with the correct output name given by xrandr in - 1 -):
xrandr --addmode VGA1 1440x900_75.00 xrandr --output VGA1 --mode 1440x900_75.00
7 - to make xrandr settings persistent (without using xorg.conf), just add the 3 xrandr commands given in - 3 - and - 4 - to the file "/etc/gdm/PreSession/Default"
Hope this helps
I tried only points 1 and 2 and it worked !
Thanks a lot to all of you
Offline
You're welcome!
Offline
I'm in a similar case. I used xf86-video-intel-legacy.
I tried xf86-video-vesa but can't use compositing with it. I tried xf86-video-intel it's better in the way that my WM looks like before but I get long time response (nearly 3 or 4 seconds between each image) whereas glxgears tels me something about 950 FPS.
If I try with a xorg.conf I get an error message during bootup which says:
"x responding too fast. disabling for 5 minutes"I don't know what to do.
I solved these issues activating kms:
I tried only points 1 and 2 and it worked !
Thanks a lot to all of you
Activating KMS is also working for me (with xf86-video-intel).
Thanks.
Offline
Hi! First of all thank you so much for you explanations in this thread. I had the very same issue about the switching from xf86-video-intel-legacy to xf86-video-intel. Thanks to your instructions I solved the main issue and I got a starting Xorg 1.7.1 with the 2.9.1 intel drivers. ;-)
In order to achieve this "feat" I had to:
- enable KMS
- include the modules in mkinitcpio configuration
- recreate the kernel image
- append "i915.modeset=1" to the kernel line in grub's menu.lst (though dmesg says "unknown boot option... ignoring")...
I also needed not to set any xorg.conf file. If so (also with the result file from X -configure) the server doesn't start at all).
Anyway thaks to all this things it eventually worked. kdm (shipped by KdeMod4) starts correctly and the console switching is fast as promised with KMS enables...
BUT... after few seconds once logged into a DE (I tried KDE and a freshly installed Fluxbox) the whole system hangs abruptly
That's what I get after reboot from the last Xorg log file /var/log/Xorg.0.log after the correct start messages:
[mi] EQ overflowing. The server is probably stuck in an infinite loop.
Backtrace:
0: /usr/bin/X (xorg_backtrace+0x3b) [0x80e37ab]
1: /usr/bin/X (mieqEnqueue+0x1ab) [0x80e2aeb]
2: /usr/bin/X (xf86PostMotionEventP+0xcc) [0x80b30fc]
3: /usr/bin/X (xf86PostMotionEvent+0x68) [0x80b3288]
4: /usr/lib/xorg/modules/input/synaptics_drv.so (0xb6ee9000+0x321b) [0xb6eec21b]
5: /usr/lib/xorg/modules/input/synaptics_drv.so (0xb6ee9000+0x57ad) [0xb6eee7ad]
6: /usr/bin/X (0x8048000+0x7aaff) [0x80c2aff]
7: /usr/bin/X (0x8048000+0x1057e4) [0x814d7e4]
8: (vdso) (__kernel_sigreturn+0x0) [0xb7771400]
9: /usr/lib/libdrm.so.2 (drmCommandNone+0x32) [0xb7239ba2]
10: /usr/lib/xorg/modules/drivers/intel_drv.so (0xb71ae000+0x2055e) [0xb71ce55e]
11: /usr/bin/X (0x8048000+0x130a7b) [0x8178a7b]
12: /usr/bin/X (0x8048000+0x1241ba) [0x816c1ba]
13: /usr/bin/X (BlockHandler+0x58) [0x806e868]
14: /usr/bin/X (WaitForSomething+0x114) [0x80aa8c4]
15: /usr/bin/X (0x8048000+0x33cc0) [0x807bcc0]
16: /usr/bin/X (0x8048000+0x1ab15) [0x8062b15]
17: /lib/libc.so.6 (__libc_start_main+0xe6) [0xb7394a36]
18: /usr/bin/X (0x8048000+0x1a701) [0x8062701]
Anyway I found on the web that KMS conflicts with vesafb and genrally with the other fb drivers for both X and the kernel. The only fb-related entry I can still find in Xorg log is libfb that's a software module for framebuffer management... but I have no idea how to stop it from loading from Xorg.
My next step will be to try to disable synaptics drivers since, along with Intel, they are the only drivers named in the backtrace above.
Any suggestion is greatly appreciated
Thanks in advance!
bYe,
Andy
Last edited by wandrian (2009-11-03 14:06:15)
Offline
Hello..
I have the same issue about the switching from xf86-video-intel-legacy to xf86-video-intel but I'm not able to solve this problem.
I tried to follow your instructions, KMS (early or late start) with and without xorg.conf, but I obtain always the same black screen.
My video card is: Intel 82852/82855 GM/GME..
any suggestion is very appreciated. If necessary I can post all my config files.
Maurizio.
Offline
sorry, is it possible to modify the tag [solved] with [semi-solved] or remove, since all of us solve the problem? thanx
Last edited by *blasco* (2009-11-04 16:37:16)
Offline
Hello,
I have the same problem. I could partly solve it, if I put acpi=off to my kernel line. But then my ipw2200 doesn't work anymore. And my console looks ugly, so I´m pretty sure it has something to do with the framebuffer device.
How can I disable it?
291078
Last edited by 291078 (2009-11-04 18:49:21)
Offline