Bug 24833 - xserver-xorg-video-intel causing Ubuntu 9.04 and 9.10 to crash at startup
Summary: xserver-xorg-video-intel causing Ubuntu 9.04 and 9.10 to crash at startup
Status: RESOLVED WONTFIX
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium critical
Assignee: Carl Worth
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2009-10-31 14:18 UTC by jasmines
Modified: 2010-03-23 13:17 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description jasmines 2009-10-31 14:18:55 UTC
Since I upgraded to Ubuntu Jaunty (9.04) I had to revert to 2.4 version of the driver, 'cause neither the official packet nor the one provided from intellinuxgraphics.com works.

When I upgraded to Ubuntu Karmic 9.10, last week, I tried to re-install the newest version, but I'm still experiencing crashes at startup.

With Jaunty I saw the "Kubuntu" logo loading, then the screen went in "Low Graphics Mode", showing the window for troubleshooting (but nothing could be solved).

Now, with Karmic, I see the "Kubuntu" logo loading, then the screen freezes. And that's all.
Comment 1 Carl Worth 2009-11-06 12:16:46 UTC
I'm sorry, I'm not familiar with the versions of our driver included in
various Ubuntu releases. Could you please indicate which versions of the
driver are causing you problems?

Thanks,

-Carl

PS. See here for general information on information that can be useful
in bug reports against the Intel driver:

http://intellinuxgraphics.org/how_to_report_bug.html
Comment 2 jasmines 2009-11-06 12:50:06 UTC
I've been experiencing trouble with every version > 2.5 which is included in Jaunty and Karmic. I suppose it's something related to the new kernel builds.
Comment 3 Gordon Jin 2009-11-29 19:31:44 UTC
jasmines, could you provide the detailed info according to the link given by Carl? So far I even don't know which chipset you are talking about.
Comment 4 jasmines 2009-11-29 22:01:49 UTC
I'd love to provide useful details, but all I can do is to execute what you tell me to do.
My chipset is: Intel Corporation Mobile Series 4 Chipset Integrated Graphics Controller (4500MHD with i915 Kernel module).
Comment 5 Carl Worth 2009-12-02 08:48:22 UTC
(In reply to comment #4)
> I'd love to provide useful details, but all I can do is to execute what you
> tell me to do.
> My chipset is: Intel Corporation Mobile Series 4 Chipset Integrated Graphics
> Controller (4500MHD with i915 Kernel module).

Hi jasmines,

So the first thing I look for in a bug report are what versions of the
kernel and driver are reported to have the bug. Because that will tell
me what code to go look for to find the bug, (and to be able to look
to see if subsequent commits are likely to have fixed the bug or not).

But as I've said earlier in this bug report, I don't know what
versions you are using that have the bug. The driver version is
reported in the Xorg.0.log file, so if you attach that, we can see
what kernel and driver ou are using.

The "how_to_report_bug" page I linked to above talks about providing
the Xorg.0.log file (and other information).

It will be most useful if you can get back to us with more of these
details.

Thanks,

-Carl


Comment 6 ykzhao 2010-03-15 19:12:55 UTC
(In reply to comment #4)
> I'd love to provide useful details, but all I can do is to execute what you
> tell me to do.
> My chipset is: Intel Corporation Mobile Series 4 Chipset Integrated Graphics
> Controller (4500MHD with i915 Kernel module).
> 

Will you please try the 2.6.33 kernel and attach the following outputs when the issue happens? (Please add the boot option of "drm.debug=0x04")
   a. Xorg.0.log
   b. dmesg

thanks.

Comment 7 jasmines 2010-03-23 13:17:35 UTC
Formatted and reinstalled Ubuntu 9.10.
Problem solved, and I can't be useful for further activities related to the initial bug. Sorry.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.