X freezes after cold boot with Intel 845 chipset

[julianlubenov]

Binary package hint: xserver-xorg-video-intel

I have installed Gutsy on 26 computers in my university. The computers are with onboard intel 82845g/gl video and Ubuntu is with xserver-xorg-video-intel driver. The problem is that when I power on the computers and boot in Ubuntu at random the half of the computers freeze when X starts. They freeze in two ways, only with black screen or with cursor and garbage screen. When I turn on the computers if I boot in windows and then restart in Linux the computers always start normally and no matter haw many times I restart the the problem doesn't occur. But when I power off the computers and then power on them again the half of the computers are freezing when X starts. May be the thing is that somehow windows initializes the video card and the Ubuntu's video drivers doesn't, or do that wrong.
Please help.

[julianlubenov (julianlubenov)]

Here is my Xorg.0.log.old file after the system have freezed in the previous boot.

[Bryce Harrington (bryce)]

Hmm, that sounds quite odd. However, there are no error messages jumping out at me in the Xorg.0.log.old file.

Would you be willing and able to run this through gdb to determine roughly where in the code the fault lies? Info about using the debugger with X for troubleshooting crashes is at https://wiki.ubuntu.com/DebuggingXorg. Further debugging tips and processes are documented at https://wiki.ubuntu.com/X/Debugging

[Peter Clifton (pcjc2)]

There are some unreleased fixes which help people with intel 855 HW, perhaps you might like to test them with the 845 HW and see if that helps?

http://www2.eng.cam.ac.uk/~pcjc2/ubuntu/xserver-xorg-video-intel_2.1.1-0ubuntu10~pcjc2.2_i386.deb

This encorporates all other unreleased fixes I've been working on.

[jhansonxi (jhansonxi)]

I've encountered similar problems with an Intel D845GBV system. The system is not mine and I didn't have a lot of time to test. Initially the system seemed fine but I was having problems with Compiz and RDC (couldn't switch back from full screen) so I disabled AIGLX in xorg.conf (probably not the best method) and then the problems started. I tried monitoring via ssh and a serial console but when X dies the system locks hard and neither responds. I did try using gdb but it developed an error and reported the data was not reliable. Logs and info attached but the X log only reports "Fatal server error: lockup".

[blazerw (randy-1702)]

I have the same problem on an Intel Inspiron 1100 that has an 845G. However, if I remove "splash" from the grub line that boots the computer, it can successfully start X nearly 100% of the time. So, a work around might be to edit /boot/grub/menu.lst and remove "splash" from the boot line.

Also, Fedora 8 can boot the computer with Fedora's graphical startup and always gets X to start.

[Bryce Harrington (bryce)]

Perhaps this is related to the intelfb issue. If removing vesa from the grub boot line resolves it, that's a strong indication that it's the issue.

http://bugs.freedesktop.org/show_bug.cgi?id=12772

[Axel Pospischil (apos)]

I had some severe problems getting the driver to work (see https://launchpad.net/bugs/114331). I thought, it works, but after rebooting the machine the next day, X freezes the system. Only with the following procedure I can get X up and running - once it runs, it is stable:

"Warm" boot (just "reboot") the machine from a previously working X/DRI session, e.g. from a SuSE 10.3 on the same machine. I have to start a video inside of this xsession.

EVERY "Cold" boot (e.g. after the machine was completely shut down for a while) results in a system freeze upon X start (screen keeps black). This is for hardy AND gutsy (after system upgrade). I am opening a new bug to this.

There is no logs in Xorg.log.old! I will try gdb soon.

[Axel Pospischil (apos)]

Logs from Xorg.0.log* attached.

[Axel Pospischil (apos)]

Logs from Xorg.0.log* attached.

[Axel Pospischil (apos)]

The Xorg0.log.old ist the one (I asume) when the system crashes (cold boot)
The Xorg.0.log is the one after the next warm boot.

hardy alpha 4 (fresh harddisk installation) && apt-get upgrade
xserver-xorg-video-intel Version: 2:2.2.0.90-2ubuntu2
linux-image-generic Version: 2.6.24.7.7

[Axel Pospischil (apos)]

Using gdb for debugging seams to be impossible in this case because I cannot get a PID for X: it crashes upon startup.

I started X via an ssh-session (export DISPLAY=localhost:0.0;strace -o strace-X.log.crash X) on the machine. The logs for both - ltrace and strace - are attached. The logs for a "warm" start with a previously SuSE 10.3 X session running DRI and a video have the endings ".success". For "cold" start they have the endings ".crash".
I killed the xserver via "Ctrl+Alt+Backspace".

I hope these informations are useful.

[Axel Pospischil (apos)]

According to http://wiki.debian.org/XStrikeForce/XserverDebugging:
 apt-get install xserver-xorg-video-intel-dbg libgl1-mesa-dri-dbg libgl1-mesa-glx-dbg

I tried using gdb in batch mode with:

 gdb /usr/bin/Xorg -batch -ex 'run' -ex 'set logging overwrite on' -ex 'set logging on' -ex 'bt full' -ex set 'logging off' -> results in empty gdb.txt: "no stack"

 gdb /usr/bin/Xorg -batch -ex 'run' -ex 'handle all nostop' -ex 'handle all pass' -ex 'handle 11 stop' -ex 'cont' -ex 'bt full' -ex 'cont' -> results in empty gdb.txt: "no stack"

The (ssh) shell output of the starting Xorg is

[...]
(==) Using config file: "/etc/X11/xorg.conf"
[New Thread 0xb7c686b0 (LWP 5418)]
(no debugging symbols found)
[tcsetpgrp failed in terminal_inferior: Operation not permitted]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(II) Module "ddc" already built-in
(II) Module "i2c" already built-in
(II) Module "ramdac" already built-in
--->>> CRASH

The acccording Xorg.0.log is attached again in "logs.tgz".
"messages" and "kern.log" are from the next boot, but don't contain any useful informations.

Can somebody give me a hint how to enable the debugging symbols when testing xorg?

[Axel Pospischil (apos)]

This really didn't let me sleep - so I decided to try another (comparable) distribution. Madriva or Fedora doesn't seam to be comparible, because they use older kernel/xorg. So SuSE 11 alpha2 came along yesterday, and I gave it a fresh autoconfigured (Xorg) install. I had to enable "3D" support. It uses the "i810" driver by default. I also tested "xorg.conf" with the "intel" driver: no difference.

It comes with:
# rpm -q xorg-x11-server
xorg-x11-server-7.3-57

# X -version
X.Org X Server 1.4.0.90
Release Date: 5 September 2007
X Protocol Version 11, Revision 0
Build Operating System: openSUSE SUSE LINUX
Current Operating System: Linux ibmr31 2.6.24-6-default #1 SMP 2008/01/31 14:27:52 UTC i686
Build Date: 03 February 2008 06:46:59AM

I "cold" booted the machine ... and X comes up without any problems. DRI is running much faster, than on ubuntu hardy - 170.000 fps to 50.000 fps / with XAA, tested with glxgears (I know this is not the best test for this).

SUMMARY: This should definitely work!

1. It seams to be an initialization problem with DRI, because once it runs - "warm" boot supported and "pre initialized" by another X - it runs fine. 'julianlubenov' (initial posting) got this effect by booting into windows.
2. It affects both 8.04/hardy/alpha4 and 7.10/gutsy (with the actual updates).
3. Results on OpenSuSE 11 could be a hint. Probably upstream could manage to contact these people.
4. If "intel" does not work yet for i830M chipsets, it should NOT be used. DRI definitely IS useful for a fast desktop experience (even without compiz).

[Axel Pospischil (apos)]

Was too fast: After a while of letting the battery out of the machine openSUSE shows exactly the same behaviour upon cold boot / warm boot :(

[unggnu (unggnu)]

I had a similar problem with a Gericom Laptop with i845.
"VGA compatible controller [0300]: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device [8086:2562] (rev 03) (prog-if 00 [VGA])"
But since the Intel driver didn't work because of Bug #135093 I have used the i810 driver which has the same problem that it freezes often after cold boot. An easy workaround was to boot Ubuntu recovery mode and then restart. Atm I couldn't test the Laptop since it isn't my own.
Maybe someone can check if it works with the recovery mode and can post both Xorg.0.logs of the session but more important this issue should be reported upstream with all needed information.

[Axel Pospischil (apos)]

Hi unggnu, unfortunatly rebooting in recovery mode does not work on my machine.
Opened a new bug for the HARDY/8.04 and the i830M chipset: Bug #192088.

[unggnu (unggnu)]

Have you started gdm in recovery mode? I guess it only starts automatically if a root password is set otherwise you have to start it with the command "/etc/init.d/gdm start".
Maybe it was random or a different problem since it happens with the i810 driver.

[Axel Pospischil (apos)]

Hi unggnu, Just did an apt-get upgrade on hardy alpha4 (kernel 2.6.24-8).

Tried also starting X out of recovery mode (we are talking about a cold boot!). Both plain "X" and gdm results in system freeze.

Runs fine after a (suse 10.3) warm boot (reboot).

Reported this to https://bugs.freedesktop.org/show_bug.cgi?id=10472

[unggnu (unggnu)]

The original Freedesktop report was for i845 and happens with the i810 driver too like in my case. Since i810 seems to always work for you it could be different problem.

[Axel Pospischil (apos)]

+++ This bug was initially created as a clone of Bug #10472 +++

X freezes upon startup when doing a COLD BOOT (using DRI).

System: ubuntu hardy/8.04
- hardy alpha 4 (fresh harddisk installation) && apt-get upgrade
- Chipset: Onboard Intel Corporation 82830 CGC (i830M)
- xserver-xorg-video-intel Version: 2:2.2.0.90-2ubuntu2
- linux-image-generic Version: 2.6.24.7.7
- standard xorg.conf with: Driver "intel" or "i810"

Only starting into an older linux on the same machine (with dri enabled,
playing with glxgears), then WARM BOOT (reboot) into ubuntu works.

Same behaviour on SuSE 11 alpha1 and on Ubuntu gutsy/7.10 (since updates of
Jan/2008).

Logs and whole story (short - i830M):

https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/192088

(long - i845 / i830M):

https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/151044

[Axel Pospischil (apos)]

*** Bug 10472 has been marked as a duplicate of this bug. ***

[Axel Pospischil (apos)]

Please refer to the previously mentioned link (http://launchpadlibrarian.net/12000527/logs.tgz) for LOG FILES and TRACES, because the attachment is too big for this bugzilla.

[Axel Pospischil (apos)]

This happens with both - new "i810" AND "intel" driver. Thanks unggnu for searching the bug database, I reported this upstreams: https://bugs.freedesktop.org/show_bug.cgi?id=14528.

[Hong-liu (hong-liu)]

(In reply to comment #0)
> Logs and whole story (short - i830M):
>
> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/192088

From this link, It seems you can kill the Xserver via "Ctrl+Alt+Backspace", So X server is not crashed/frozen, it is just blank screen. Can you ssh to this machine? If can, would you please turn on ModeDebug in your xorg.conf and provide two xorg log (warm boot and cold boot)?

Did you use the intelfb module in kernel (grep intelfb in your dmesg log will give you the answer)? If so, please remove it before starting X.

Thanks,
Hong

[Michael Fu (michael-fu-intel)]

(In reply to comment #2)
> Please refer to the previously mentioned link
> (http://launchpadlibrarian.net/12000527/logs.tgz) for LOG FILES and TRACES,
> because the attachment is too big for this bugzilla.
>

Alex, would you please attach them as seperate files here? Also please refer to http://www.intellinuxgraphics.org/how_to_report_bug.html for what we needed.

[Axel Pospischil (apos)]

Thanks Hong and Micheal for your replies and tips.
I am new to X debugging, so it took me a little while ...

Hong, unfortunatly X freezes the whole system, it is NOT possible to kill the server with Crtl-Alt-Backspace. I did this when testing X on the warm booted machine with ltrace/strace.

- linux-image-generic Version: 2.6.24.8.8
- xserver-xorg-core Version: 2:1.4.1~git20080131-1ubuntu2
- xserver-xorg-video-intel Version: 2:2.2.0.90-2ubuntu2
- NO framebuffer is loaded, no vga=... boot options
- system boots without (!) bootsplash
- Option "ModeDebug" "yes" in the Device section of xorg.conf

-------------------------------------
Here's what I did on the hardware and software mentioned above:

1. Removed power plug and battery out of the machine for a few seconds (or leaving the machine for half an hour powered off). The notebook has a relatively new mainboard battery.
Booted into runlevel 5 (gdm disabled).
Ssh'd into the machine as root.

2. Via remote: # strace Xorg > strace_cold.log

RESULT:
X freezes. The resulting trace file is EMPTY. So I attached what I could catch from the remote shell in strace_cold-remoteshell.log.
Rebooted (!) the machine. Saved /var/log/... files as attachments.

------------------------------------
Now I tried something else according to https://wiki.ubuntu.com/DebuggingXorg.

# apt-get install xserver-xorg-core-dbg xserver-xorg-video-intel-dbg

Added the following to xorg.conf
Section "ServerFlags"
        Option "NoTrapSignals" "true"
EndSection

# sudo modprobe drm
# sudo echo 1 | sudo tee /sys/module/drm/parameters/debug
# ulimit -c unlimited
# sudo gdb /usr/bin/Xorg
# (gdb) run -keeptty -dumbSched

kern.log only shows one new line before freeze:
  Feb 19 14:11:18 ibmr31 kernel: [ 61.457528] [drm] Initialized drm 1.1.0 20060810

RESULT:
X tries to start but freezes the machine.
No core dump in /etc/X11. I attach the catched gdb remote session.
Rebooted the machine and attached /var/log/Xorg.0.log,messages,kern.log

------------------------------------
For today my time exeeded - sorry.

Could you tell me how to enable coredumps in Xorg in this case? Or probably how to define a breakpoint?

Greets
Axel

[Axel Pospischil (apos)]

Created an attachment (id=14410)
Logs and configuration files for first attempt on X debugging

[Axel Pospischil (apos)]

Created an attachment (id=14411)
Logs and configuration files for SECOND attempt on X debugging

[Axel Pospischil (apos)]

Started new attempts using the above configuration and coming nearer ...
Followed advices in https://wiki.ubuntu.com/Strace

a. Preparation
# sudo su
# ulimit -c unlimited
# modprobe drm
# echo 1 | tee /sys/module/drm/parameters/debug

b. Run
# strace -Ff -tt /usr/bin/Xorg 2>&1 | tee strace-Xorg.log

RESULT:
With this command, the system does NOT freeze anymore, but X is NOT starting through - it stops, when the error occurs. I didn't go deep into strace, but I hope this is correct - please tell me if I am wrong. I attach the logs.

Thanks for your patience with my efforts in learning debugging ;)
Axel

[Axel Pospischil (apos)]

Created an attachment (id=14423)
THIRD successful attempt debugging with strace after COLD BOOT

[Axel Pospischil (apos)]

Directly (!) after the last post I booted into SuSE 10.3 (3D/DRI enabled) on the same machine and ran glxgears. If I don't do this the "trick" would not work!
I "WARM" (re)booted imediately into ubuntu 8.04.

I used the same commands as for the COLD boot (the last post) to start Xorg.

RESULT:
X did not came up like expected using strace with "-Ff -tt". It stopped at right the same loacation in strace. So I left them away and just did a plain "strac /usr/bin/Xorg" which leaded into a running X.

[Axel Pospischil (apos)]

Sorry, but my attachments are too big for this bugzilla and I don NOT upload them seperatly (this tests are scripted and it really took to much time and is error prone).

So the logs are here: System always starts into runlevel 5, but without X.
X is started via ssh - see above.

1. First boot (COLD):
http://launchpadlibrarian.net/12091276/Xorg-crash_on_COLD_boot-logs.tar.bz2
RESULT: X does not start and system freeezs completely.
Logs are from the NEXT boot.

2. Second boot (COLD):
http://launchpadlibrarian.net/12091373/Xorg-SECOND%20BOOT%20-%20crash_on_COLD_boot-logs.tar.bz2
RESULT: X does not start, but system keeps usable (only black screen).
Logs are from the same boot.

3. Third boot (WARM and pre initialized via SuSE 10.3):
http://launchpadlibrarian.net/12091181/Xorg-on_warm_boot-logs.tar.bz2
RESULT: X comes up without problem.

[Axel Pospischil (apos)]

Created an attachment (id=14427)
my scripts used for testing

[Hong-liu (hong-liu)]

What is the driver version used in your SUSE system? So booting to Suse is always OK wether cold / warm boot?

Would you please try several things:
1. for 1st cold boot, 2nd cold boot and warm boot before starting X, could you try to lspci -xxx and dump the register using intel_reg_dump (in xf86-video-intel/src/reg_dump), and compare the logs to see if there is any difference?

2. for the 1st code boot, from the log
(II) intel(0): I2C bus "DVOI2C_E" removed.
(II) intel(0): I2C bus "DVOI2C_B" initialized.
1st cold boot stops here, while 2nd cold boot continues...
(II) intel(0): I2C device "DVOI2C_B:i82807aa "ivch" LVDS/CMOS panel controller" registered at address 0

The code is in i830_dvo_init (xf86-video-intel/src/i830_dvo.c),

448 if (gpio_inited != gpio) {
449 if (pI2CBus != NULL)
450 xf86DestroyI2CBusRec(pI2CBus, TRUE, TRUE);
451 if (!I830I2CInit(pScrn, &pI2CBus, gpio,
452 gpio == GPIOB ? "DVOI2C_B" : "DVOI2C_E")) {
          ***this create DVOI2C_B bus and both boot reached here***
453 continue;
454 }
455 }
456
457 if (drv->vid_rec != NULL)
458 ret_ptr = drv->vid_rec->init(pI2CBus, drv->address);
             ***this will call ivch_init(), it seems the 1st boot froze the sytem in this function.

Would you please try to start Xserver within GDB and set a break point in ivch_init, and then single-step in this function to see which line causes the system freeze.

Thanks,
Hong

[unggnu (unggnu)]

Upstream has closed the original bug report because it was started for i810 driver. We could create a new one but I guess that Axel Pospischil experiences the same bug with i830 and I don't own the laptop with 845 so I can't get the information for a separate bug report.
If someone has a laptop with i845 chipset and experiences this problem feel free to open a new upstream report and link it here again.

[Michael Fu (michael-fu-intel)]

ping update from bug reporter...

[unggnu (unggnu)]

Could everybody please support upstream bug report under https://bugs.freedesktop.org/show_bug.cgi?id=14528 so that it gets fixed? Maybe a new bug report has to be created for the 845g chipset (http://intellinuxgraphics.org/how_to_report_bug.html) but I guess the 830 has the same problem.
It would be great if the fix could make it into Hardy but the time is running.

[Axel Pospischil (apos)]

Hello again, hello Hong,
first thank you very much for your answer and regard me being so late. I was very busy ... so back to work on open source now ;)

SUSE 10.3:
==========
Your question about the version of xorg in suse 10.3 (rpm -qa --info xorg-x11-server):
Name : xorg-x11-server
Version : 7.2
Release : 143.6 - Build Date: Mi 24 Okt 2007 16:24:12

New is: after doing the tests the driver behaves erratic. Sometimes it takes me three times after a cold boot to get the server running. First time system freezes right upon X startup showing crizzeling cube (the cursor) in the middle of the screen. Second time system freezes with vertical colored lines spread above the whole screen. Third time the boot process run's through and everything is O.K. Then (and only then !!!) it is possible to boot another Linux (e.g. ubuntu) without hazzle using DRI.

Ubuntu Hardy 8.04 LTS:
======================
By the way: another guy had detzected the same problems on a X3100 intel chipset (see: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/192088/comments/8) .

On my ubuntu things changed and a I recognized a new version of the "xserver-video-intel" driver arrived on alpha6 these days. I updated the system again today.
 -> xserver-xorg-video-intel 2:2.2.1-1ubuntu4

And suprise, surprise: The X server system boots now into the graphical desktop after a COLD boot. Using the system in a normal way is no probelem.

BUT - starting an applications that uses DRI (e.g. glxgears or compiz) makes the system freeze again.

DEBUGGING
=========
I booted Ubuntu 8.04, logged remotly via ssh into the machine and started the debugger via ssh:

 # pgrep Xorg
 5413
 # gdb /usr/bin/Xorg
 # (gdb) attach 5413
 [...]
 Loaded symbols for /usr/lib/xorg/modules//libexa.so
 Reading symbols from /usr/lib/dri/i915_dri.so...done.
 Loaded symbols for /usr/lib/dri/i915_dri.so
 Reading symbols from /usr/lib/libexpat.so.1...done.
 Loaded symbols for /usr/lib/libexpat.so.1
 0xb7fe1410 in __kernel_vsyscall ()
As you can see, the i915 drive is loaded, xorg.conf is showing the "intel" Driver. Could that be the problem?

I added the breakpoint
 # (gdb) break i830_dvo.c:438
 Breakpoint 1 at 0xb7b94016: file ../../src/i830_dvo.c, line 438.
 # (gdb) cont

Now I start glxgears, but the system does freeze when starting it. So I cannot get a backtrace again ;( You see I am completely new to X debugging.

Do I have to run glxgears also with the debugger?

Probably it will take a little time for my reply. Thanks for your patience.
Axel

[Axel Pospischil (apos)]

Created an attachment (id=15383)
GLXgears freezes the system

[Axel Pospischil (apos)]

Because the original problem is gone - the system boots into the graphical system - should I close this thread? Consider, that DRI is not usable anyhow, problem seems so be deallocated into the running X process.

[Axel Pospischil (apos)]

Hi there, since the easter egg search is not possible due to snow in germany/wiesbaden (my car was white this morning) I had some time reading some logs ;)

So the fact, that the graphical system is usable now make testing a lot more comfortable and less time consuming. I first disabled DRI with:
 - Option "DRI" "false"
and started testing.

PARTIAL SOLUTION
================
Carefully watching the Xorg.0.log's now, I remembered having some trouble back in time with an option in xorg.conf and the 830M chipset:
 - DefaultDepth 16 (in 'Screen' Section)

After adding the line to the xorg.conf and restarting gdm, the colors of the desktop are much more smooth (concerns depth 16bit).

TEST
====
1. Shutting the notebook down, get the power cord out, get the battery back out. Wait 5 Minutes ... starting into ubuntu 8.04/gnome.
RESULT: Graphical desktop appears like expected.

2. But when I start glxgears, the system freezes completely. Disabling DRI with
 - Option "DRI" "false"
makes the system usable again - naturally.
I don't no exactly how, but playing arround with playing videos, the following xorg.conf settings
 - VideoRam 65536 # depreciated!
 - Option "BackingStore" "true"
 - Option "AccelMethod" "XAA"
together with restarting X several times, got me a running glxgears once, but never again. Unfortunately I could not reproduce this behaviour.

CONCLUSION (for now)
==========
1. This chipset is NOT good for use with 24bit color depth at all - or, in other words: this causes a lot of trouble. Probably the intel driver should respect/take care of this circumstance.

2. Problem with DRI is still the case, but the X boots up for now.

---------------------
I will try a little more. But for now it's enough and I am happy, that I have at least a usable system - despite without DRI ;(
Adding logs now ...

[Axel Pospischil (apos)]

Created an attachment (id=15391)
Xorg.conf and system logs after a freeze with glxgears.

[Hong-liu (hong-liu)]

For your DRI issue, I'd like to suggest you to update your mesa i915 dri driver and kernel drm module, and have a try.

If the problem still exists, please open a new bug about your DRI issue.

I will close this one since the 2D issue seems gone now.

Thanks,
Hong

[unggnu (unggnu)]

This cold boot issue should be fixed in latest Hardy Intel driver at least for i830. Could please someone confirm this with current Hardy and i845 chipset?

[Axel Pospischil (apos)]

Thanks too for your guidance.
Axel

[Axel Pospischil (apos)]

After upate of today on the - not yet official - ubuntu hardy / 8.04 with
 - linux-image-generic Version: 2.6.24.14.16
 - xserver-xorg-core Version: 2:1.4.1~git20080131-1ubuntu6
 - xserver-xorg-video-intel Version: 2:2.2.1-1ubuntu6

my problems are completely gone ;) ;) ;)
So there is 3D from COLD boot straight after starting X and I could remove my "Option "DRI" false" line out of xorg.conf.

Real happy now - good work.

I am adding my xorg.conf for the Thinkpad R31.

[Axel Pospischil (apos)]

Created an attachment (id=15728)
Xorg.conf Ubuntu Hardy 8.04 for 1024x768 LCD on TP R31

[Hong-liu (hong-liu)]

glad to hear it's working now :)

[brianglass (brian-glassbrian)]

I have an Inspiron 1100 with an i845 chipset. I have the latest Hardy as of 4/8/08. I still have the cold boot problem.

[unggnu (unggnu)]

Could you please then report it upstream http://intellinuxgraphics.org/how_to_report_bug.html and post the link here?

[unggnu (unggnu)]

Is the problem fixed with Final Hardy? If not please attach the files /etc/X11/xorg.conf, /var/log/Xorg.0.log and /var/log/Xorg.0.log.old (this file only if the cold boot problem appears the boot before) and the output of dmesg so we can record it upstream.

[Bryce Harrington (bryce)]

According to upstream 14528, Axel's issue is fix. We don't have enough info on brianglasses' issue to know if he's seeing the same bug or something different. Since there's been no reply from him in 2 months, assuming he found a resolution to his issue. Closing this bug as fixed.

[Axel Pospischil (apos)]

Hello guys,

sorry to mention, that problems are back again (for a while). I did not have the time to report - sorry.

System:
-------
- Ubuntu hardy heron - 8.04 LTS

Problem description:
--------------------
1.When DRI is enabled and an opengl application starts (e.g. glxgears, stellarium, compiz, ...) system freezes completely.
2. DRI __is_not__ working any more after rebooting from another linux, where DRI was working (e.g. suse 10.1).

Partial fix:
------------
I had to add "Option "DRI" false" line in xorg.conf.
So the computer is usable for now with 2D.

I am filing a new bug to i830M and DRI problems within the next days with the according logs.

[Axel Pospischil (apos)]

Hi there after a while,

System:
-------------------
Thinkpad R31 (specs see above)
Ubuntu 8.10 with
- xserver-xorg 1:7.4~5ubuntu3 the X.Org X server
- xserver-xorg-video-intel 2:2.4.1-1ubuntu10 X.Org X server -- Intel i8xx, - i9xx display driver
- linux-image-generic 2.6.27.7.11 Generic Linux kernel image

Updated Informations
--------------------

I am very pleased to announce, that with upgrade to ubuntu 8.10, several problems are gone under __ONE_ circumstance:
I deleted the xorg.conf completely and let the system decide to configure a new one! Using the old xorg.conf is possible but leads into the described problems above.

FIRST: DRI now works. It is incredibly slow, but no freezes any more ;) No more hangs during boot or starting GL applications (including e.g. metacity compositing manager).

SECOND: The first time ever for the last years, I am able to use the dual screen option to use a second monitor expanding my display - not only the "clone" function.

One glitch: I had to manually add the parts from the keyboard and mouse device section from my old to the new xorg.conf.

A big "thank you" to all intel developers working on these threads!

Greets Axel

[Axel Pospischil (apos)]

Created an attachment (id=20040)
Xorg.conf with auto configuration (except mouse and keyboard) and randr

This make the former solution for xorg.conf obsolete (but only tested for Ubuntu 8.10).

[Axel Pospischil (apos)]

ADDENDUM
--------

Due to some artifacts on the screen I had to add

Section "Screen"
...
   DefaultDepth 16
...

to the xorg.conf. I suppose this is the same problem with this chipset as mentioned in another post above.

[Axel Pospischil (apos)]

Fixed for me in Intrepid Ibex (8.10): See https://bugs.freedesktop.org/show_bug.cgi?id=14528