xf86-video-intel

Bug #406460
Comment #24

Comment 24 for bug 406460

Revision history for this message

jerrylamos (jerrylamos) wrote on 2010-01-02:

#24

Geir, good point. A lot of water goes under the dam when running Ubuntu development levels.

Karmic during development from late June into (I think) August had problems on i845. Bryce had some suggestions and tried his suggestions. Late in Karmic development a linux-image update fixed the problem for me.

Karmic release level and updates to 2.6.31-16 I haven't had a problem. The pc has running currently multi boot Lucid, Karmic, Jaunty, DebianLXDE, and Slax. Only one that hangs up is Lucid.

Lucid started out O.K. for me, no surprise, early in development not much had changed yet.

Lucid around 2.6.32-5 got black screen on boot. I do try combinations of default, "vesa", and nomodeset in attempts to get going.

Based on your suggestions, downloaded the freeze .deb's with Karmic, copied to Lucid, then did recovery command line dpkg -i. No luck with them.

Decided to do a re-install in case some of the fix attempts were clouding the issue. Even the Lucid live CD at level 2.6.32-7 boots to black screen unless I key in an xorg.conf. The installed 2.6.32-7 booted to black screen. Recovery mode command line sudo apt-get update, sudo apt-get dist-upgrade to 2.6.32-9 boots to black screen.

Based on your subsequent suggerstions, downloaded 2.6.32rc1 with Karmic, copied to Lucid, then did Lucid recovery command line dpkg -i. Hooray, it booted! Tried rc3, rc4, rc5, rc6, rc7. Each booted. 2.6.32-7 and 2.6.32-9 still boot to black screen.

Trying 2.6.33rc2 booted O.K. several times. Ran for over an hour and then the screen froze. Command line still worked so I got ubuntu-bug xorg apport report, Xorg.0.log, .xsession-errors. Not sure if anyone has any use for these.

At this point I could try for a buffer trace or whatever it is called, there is a complex Wiki procedure which I may/may not have any luck with. ssh in from another pc, the whole bit. It's a bit complex for my level of linux command line experience because the Wiki directions don't match what happens on the screen. Not sure if anyone has any time to analyze the trace anyway.

I could try some of the rc's to see if they would hang up. This is time consuming because 2.6.33rc2 ran for over an hour before freezing screen. At that point I'm shooting in the dark because I don't know which ones may have had a change of interest. That could take days of my "spare" time between shoveling snow, preparing a computer class demo of Ubuntu, OpenSUSE, Fedora, Debian, Slax, Knoppix, usb boot, etc.

Hmmm. Thanks for your interest. Jerry

Geir, good point.  A lot of water goes under the dam when running Ubuntu development levels.

Karmic during development from late June into (I think) August had problems on i845.  Bryce had some suggestions and tried his suggestions.  Late in Karmic development a linux-image update fixed the problem for me.

Karmic release level and updates to 2.6.31-16 I haven't had a problem.  The pc has running currently multi boot Lucid, Karmic, Jaunty, DebianLXDE, and Slax.  Only one that hangs up is Lucid.

Lucid started out O.K. for me, no surprise, early in development not much had changed yet.

Lucid around 2.6.32-5 got black screen on boot.  I do try combinations of default, "vesa", and nomodeset in attempts to get going.

Based on your suggestions, downloaded the freeze .deb's with Karmic, copied to Lucid, then did recovery command line dpkg -i.  No luck with them.

Decided to do a re-install in case some of the fix attempts were clouding the issue.  Even the Lucid live CD at level 2.6.32-7 boots to black screen unless I key in an xorg.conf.  The installed 2.6.32-7 booted to black screen.  Recovery mode command line sudo apt-get update, sudo apt-get dist-upgrade to 2.6.32-9 boots to black screen.

Based on your subsequent suggerstions, downloaded 2.6.32rc1 with Karmic, copied to Lucid, then did Lucid recovery command line dpkg -i.  Hooray, it booted!  Tried rc3, rc4, rc5, rc6, rc7.  Each booted.  2.6.32-7 and 2.6.32-9 still boot to black screen.

Trying 2.6.33rc2 booted O.K. several times.  Ran for over an hour and then the screen froze.  Command line still worked so I got ubuntu-bug xorg apport report, Xorg.0.log, .xsession-errors.  Not sure if anyone has any use for these.

At this point I could try for a buffer trace or whatever it is called, there is a complex Wiki procedure which I may/may not have any luck with.  ssh in from another pc, the whole bit.  It's a bit complex for my level of linux command line experience because the Wiki directions don't match what happens on the screen.  Not sure if anyone has any time to analyze the trace anyway.

I could try some of the rc's to see if they would hang up.  This is time consuming because 2.6.33rc2 ran for over an hour before freezing screen.  At that point I'm shooting in the dark because I don't know which ones may have had a change of interest.  That could take days of my "spare" time between shoveling snow, preparing a computer class demo of Ubuntu, OpenSUSE, Fedora, Debian, Slax, Knoppix, usb boot, etc.

Hmmm.  Thanks for your interest.  Jerry