After upgrading to x11-base/xorg-server-1.3.0.0 and x11-drivers/xf86-video-i810-2.0.0, the X server crashes when it is started with signal 11. After little experimentation, I found out it does only when I use both outputs of the card as separate screens (eq. :1.0 and :1.1). X log and its console output will be posted in a follow-up, since bugzilla does not allow attaching files to the initial post. Should I provide any other information? How do I get it? Thank you
Created attachment 118090 [details] The X log
Created attachment 118092 [details] The console output
Please also attach your xorg.conf and emerge --info.
Created attachment 118508 [details] emerge --info output
(In reply to comment #4) > Created an attachment (id=118508) [edit] > emerge --info output > Although your CFLAGS and LDFLAGS make me suspicious that it's a build problem, it might be worth poking around https://bugs.freedesktop.org to see if anyone else has reported this issue.
Created attachment 118509 [details] The config This is not the exact config as the one which was used to generate the log, but this one crashes in the same way. Is it OK, or I should regenerate the output and log with this slightly modified config? For the sake completeness, this is from lspci, if exact card version is needed: 00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03) (prog-if 00 [VGA]) Subsystem: Dell Unknown device 01af Flags: bus master, fast devsel, latency 0, IRQ 19 Memory at dff00000 (32-bit, non-prefetchable) [size=512K] I/O ports at ec38 [size=8] Memory at c0000000 (32-bit, prefetchable) [size=256M] Memory at dfec0000 (32-bit, non-prefetchable) [size=256K] Capabilities: [d0] Power Management version 2 Any other way I could be of help? Thank you
(In reply to comment #0) > signal 11. After little experimentation, I found out it does only when I use > both outputs of the card as separate screens (eq. :1.0 and :1.1). From what I remember, this configuration isn't really supported anymore. Instead of specifying the outputs of this card this way, you're supposed to use xrandr to set up the displays. Monitor sections can be set up in the xorg.conf by adding: Option "monitor-VGA" "MonitorAcerLCD" Option "monitor-LVDS" "MonitorLCD" These go into your Device section. The format is monitor-OUTPUT, where OUTPUT is the RandR name of the output.
(In reply to comment #7) > (In reply to comment #0) > > signal 11. After little experimentation, I found out it does only when I use > > both outputs of the card as separate screens (eq. :1.0 and :1.1). > > From what I remember, this configuration isn't really supported anymore. > Instead of specifying the outputs of this card this way, you're supposed to use > xrandr to set up the displays. Monitor sections can be set up in the xorg.conf > by adding: > > Option "monitor-VGA" "MonitorAcerLCD" > Option "monitor-LVDS" "MonitorLCD" > > These go into your Device section. The format is monitor-OUTPUT, where OUTPUT > is the RandR name of the output. Thanks for the suggestion, I will try that ASAP (probably tommorow), and if it does not help, I will try to compile it with less aggressive flags as sugested before (though, I never had a problem with those for longer than a year).
(In reply to comment #7) > (In reply to comment #0) > > signal 11. After little experimentation, I found out it does only when I use > > both outputs of the card as separate screens (eq. :1.0 and :1.1). > > From what I remember, this configuration isn't really supported anymore. > Instead of specifying the outputs of this card this way, you're supposed to use > xrandr to set up the displays. Monitor sections can be set up in the xorg.conf > by adding: > > Option "monitor-VGA" "MonitorAcerLCD" > Option "monitor-LVDS" "MonitorLCD" > > These go into your Device section. The format is monitor-OUTPUT, where OUTPUT > is the RandR name of the output. This works, however it has one display -> I have binded desktops in sawfish. But it has the advantage of adding and removing the montor on-the-fly, so I will probably do some serious hacking of sawfish :-|. Thanks for the suggestion By the way, is the old way really unsupported, or it is a bug?
(In reply to comment #9) > By the way, is the old way really unsupported, or it is a bug? It's really unsupported, at least for the Intel driver. I'm glad to hear things are relatively working for you. I'll mark this upstream for the crash - feel free to pursue that angle if you wish.
