Bug 710718 - Preupgrade leaves me at a blank screen
Summary: Preupgrade leaves me at a blank screen
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: preupgrade
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-04 09:11 UTC by James Begley
Modified: 2011-06-06 08:57 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-06-06 08:57:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
lspci output (15.52 KB, text/plain)
2011-06-04 09:11 UTC, James Begley
no flags Details
lspic run as root (40.37 KB, text/plain)
2011-06-04 09:13 UTC, James Begley
no flags Details

Description James Begley 2011-06-04 09:11:26 UTC
Created attachment 502964 [details]
lspci output

Description of problem:
My attempt to use preupgrade to move from F14 to F15 fails. Preupgrade has downloaded all the packages and then asks to reboot. When the laptop is rebooted I get left with a black screen with a blinking white cursor in the top left hand corner. The fans on the laptop are then in full flow, indicating that something is driving the CPU hard, but nothing happens. After ~30 minutes I've had to kill the power and reboot to F14.

Version-Release number of selected component (if applicable):
preupgrade-1.1.9-1.fc14.noarch

How reproducible:
Every time

Steps to Reproduce:
1. Run preupgrade
2. Reboot
3.
  
Actual results:
Blank screen

Expected results:
Preupgrade launches me into the F15 installer

Additional info:
This is a modern sony vaio laptop with an ATI Radeon HD5600 graphics card. Could this be causing problems?

Comment 1 James Begley 2011-06-04 09:13:09 UTC
Created attachment 502965 [details]
lspic run as root

Comment 2 James Begley 2011-06-06 08:57:04 UTC
Hmmm ... running preupgrade again appears to have picked up a newer kernel which boots OK. everything is working for me on this laptop now.


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