Bug 683222 - [Sandy_Bridge] X doesn't start in installer, Intel HD 3000 (Core i5-2500K)
Summary: [Sandy_Bridge] X doesn't start in installer, Intel HD 3000 (Core i5-2500K)
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 15
Hardware: x86_64
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-08 21:11 UTC by Andrew Gormanly
Modified: 2018-04-11 09:15 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-25 10:08:57 UTC
Type: ---


Attachments (Terms of Use)
X.log (28.83 KB, text/plain)
2011-03-08 21:11 UTC, Andrew Gormanly
no flags Details
anaconda.log (2.91 KB, text/plain)
2011-03-10 09:01 UTC, Andrew Gormanly
no flags Details

Description Andrew Gormanly 2011-03-08 21:11:01 UTC
Created attachment 483017 [details]
X.log

Description of problem:
Need to install in basic graphics mode, normal mode goes to black screen on starting X

Version-Release number of selected component (if applicable):
1.9.99.1

How reproducible:
Every time

Steps to Reproduce:
1. Boot F15 Alpha installation DVD
2.
3.
  
Actual results:
Switch to X shows nothing

Expected results:
X and installer

Additional info:
X.log attached

Comment 1 Matěj Cepl 2011-03-10 01:03:51 UTC
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information especially concerning your hardware we require that will be helpful in our diagnosis of this issue.

If the anaconda crashes during the switching to the graphic mode, most likely the problem lies in Xorg support for your graphics chip. There are couple of options how we can obtain information necessary for resolving the issue.

If the computer is not completely frozen when installation fails, switch to the console (Ctrl+Alt+F2) and copy /tmp/X* and /var/log/anaconda.xlog to some other place -- USB stick, some other computer via network, somewhere on the Internet, and please attach it to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

If the computer is completely useless after installation fails, you can also install Fedora with a VESA mode driver (see http://docs.fedoraproject.org/en-US/Fedora/13/html/Installation_Guide/ for more information on that). Then after successful installation you can collect /var/log/anaconda.xlog, /var/log/Xorg.0.log, and the output of the program dmesg instead.

Or you can install Fedora in a text mode completely, and then start X after that. If it fails, still /var/log/Xorg.0.log and the output of dmesg program from the failed attempt to start X would be useful.

We will review this issue again once you've had a chance to attach this information.

Thank you very much in advance.

Comment 2 Andrew Gormanly 2011-03-10 09:01:09 UTC
Created attachment 483390 [details]
anaconda.log

Comment 3 Andrew Gormanly 2011-03-10 09:02:40 UTC
X.log was already attached, anaconda.log just has been.

The system is up with the VESA driver.

Comment 4 Matěj Cepl 2011-03-17 14:31:40 UTC
(In reply to comment #1)
> Then after successful installation you can collect [...] and the output of
> the program dmesg instead.

Please. Thank you

Comment 5 Andrew Gormanly 2011-03-24 23:23:46 UTC
Intel driver working now with current updates, can close this.

Comment 6 Matěj Cepl 2011-03-25 10:08:57 UTC
Thank you for letting us know.


Note You need to log in before you can comment on or make changes to this bug.