Bug 827939 - Fedora 17 boots in text mode, until X is started.
Summary: Fedora 17 boots in text mode, until X is started.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: distribution
Version: 17
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Bill Nottingham
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-03 22:18 UTC by Juan
Modified: 2014-03-17 03:31 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-01 05:42:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Output of dmesg (89.09 KB, text/plain)
2012-06-09 11:30 UTC, Juan
no flags Details
Output of rpm -qa|sort (89.09 KB, text/plain)
2012-06-09 11:31 UTC, Juan
no flags Details
/proc/cmdline (707 bytes, text/plain)
2012-06-09 11:35 UTC, Juan
no flags Details

Description Juan 2012-06-03 22:18:19 UTC
Description of problem:
With Fedora 16 (and earlier) the system entered graphics mode very early when booting (in fact root filesystem is encrypted and its password is requested already in graphics mode.
I did a fresh install of Fedora 17 from DVD, with more or less the same set of packages as before, and preserving the same partitioning structure (Only primary partitions, I don't use LVM and I use software raid 0. Boot partition is in one disk and swap and root partitions are two raid 0 devices).
Now it boots in text mode. It doesn't look even to try to start in graphics mode nor it gives any error message in console.
At first it talked about not finding font file True (there is another bug about this), but I worked it around, there is no such message now, and it still boots in text mode.
My machine is a Core i7 920 with 12 Gb DDR3 1066, dual channel, in 6 2Gb DIMM's.
The motherboard is an Asus P6T SE with last BIOS upgrade (release 0908).
The graphics card is an Asus EAH4550 (radeon 4550, PCI express).
It has 5 SATA2 Seagate disks, a 500Gb one and four 1.5Tb ones. The 500Gb one holds the boot partition and the rest is dedicated to Windows 7. The 1.5Tb ones hold two primary software raid partitions each: a 6Gb one for swap and the rest for root partition. Therefore, raid device md0 is 24Gb big and is composed by the 4 6Gb partitions in raid0. raid device md1 is composed by the other 4 partitions in raid0 too. Encryption is done at software raid partition level, not at raid device level.
I selected to install grub in the boot sector of the boot partition (/dev/sda1). This is a must, as some Windows upgrades require to change the active partition to Windows partition using fdisk in the usual MBR partition table.
As I say, this exact configuration worked before.

Version-Release number of selected component (if applicable):
kernel-3.3.4-5.fc17.x86_64
kernel-3.3.7-1.fc17.x86_64

Happens both with default kernel from distribution and the update kernel 3.3.7-1.

How reproducible:
Well, difficult to say, as it doesn't happen in other machines.
I just installed from DVD. Chose custom partitioning and selected formatting all devices.

Steps to Reproduce:
1. Install Fedora 17 from DVD in that hardware and partition configuration
2. Boot Fedora 17
  
Actual results:
Fedora boots in text mode. Only switches to graphics mode when starting X.

Expected results:
Fedora boots, as before, in graphics mode from the beginning.

Additional info:
Sorry, I'm a bit lost and I don't know what info to provide to help. I didn't even know what component to select for this bug.
Feel free to ask for any info you need.

Comment 1 Bill Nottingham 2012-06-03 22:44:52 UTC
Can you attach the output of "rpm -qa | sort", and attach /proc/cmdline?

Comment 2 Juan 2012-06-03 22:52:26 UTC
Thanks for the fast response.
I will as soon as I'm in front of that computer.

Comment 3 Juan 2012-06-09 11:30:46 UTC
Created attachment 590584 [details]
Output of dmesg

Comment 4 Juan 2012-06-09 11:31:40 UTC
Created attachment 590585 [details]
Output of rpm -qa|sort

Comment 5 Juan 2012-06-09 11:35:23 UTC
Created attachment 590586 [details]
/proc/cmdline

Comment 6 Fedora End Of Life 2013-07-04 01:21:31 UTC
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 7 Fedora End Of Life 2013-08-01 05:42:23 UTC
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.