Bug 851110 - blank screen on first reboot after Fedora17 installation from DVD ISO
blank screen on first reboot after Fedora17 installation from DVD ISO
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel (Show other bugs)
x86_64 Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: Adam Jackson
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-08-23 05:29 EDT by Andrew Henry
Modified: 2013-07-31 13:51 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-07-31 13:51:02 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Andrew Henry 2012-08-23 05:29:37 EDT
Description of problem:

I Installed F17 from DVD iso on a USB stick on a Thinkpad Edge 13 with Intel GMA450 graphics.  It is a clean install, where I chose to overwrite existing linux partitions.  Install went fine.  I chose Encrypted LVM auto-setup for partitions.  I used F15 and F16 on same laptop without issue, and just went from f16 to f17 yesterday.

On reboot, I get Grub display with no background wallpaper (Win7 still boots fine).  I choose to boot top line: Fedora, and it gives two text lines, the second of which is "loading initial ramdisk".  Then screen goes black, and I get no text or graphics, even if I wait several minutes.  The screen is still active, i.e. it is not truly blanked.

I guessed that it's waiting for an encryption passphrase, so I reboot and wait for black screen then enter the passphrase, hit enter and after 30-35 s I get GDM, but it's the wrong resolution.  It should be 1376x768, but I get 1024x768.  I can login ok, but system settings doesn't show the correct resolutions for my laptop.  Yum upgrade doesn't find any updates.

Im not sure if this is an encryption passphrase dialog display issue, or a general Intel GMA display issue (as I have the wrong resolution).

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

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 Andrew Henry 2012-08-23 10:31:41 EDT
I saw on another website that someone has an identical problem to mine but on a Macbook:

Comment 2 Andrew Henry 2012-08-23 10:32:32 EDT
... sorry for double post...

i.e. it seems to be a monitor issue where the monitor is not getting properly identified.  this would explain both the blank screen and the wrong resolution in gdm.
Comment 3 Fedora End Of Life 2013-07-03 15:25:19 EDT
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 4 Fedora End Of Life 2013-07-31 13:51:12 EDT
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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