Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 597016 - Upgrade F12->F13 leaves existing nomodeset in grub.conf for Intel video
Summary: Upgrade F12->F13 leaves existing nomodeset in grub.conf for Intel video
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 13
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-27 23:10 UTC by Patrick O'Callaghan
Modified: 2010-05-27 23:14 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-05-27 23:14:03 UTC

Attachments (Terms of Use)

Description Patrick O'Callaghan 2010-05-27 23:10:03 UTC
Description of problem:
F13 apparently requires KMS when used with Intel video. However F12 also worked without KMS. The update process doesn't check for nomodeset in grub.conf, leading to a system that won't boot correctly until modified.

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

How reproducible:
Only tried it once.

Steps to Reproduce:
1.Upgrade F12->F13 on a machine with nomodeset in the kernel grub.conf line
2.Upgrade leaves nomodeset
3.If the system requires KMS, it will not boot correctly
Actual results:
System fails to boot correctly

Expected results:
Correct boot

Additional info:
I have an Intel video chip on the mobo. This apparently requires KMS (F12 didn't require it and I didn't use KMS), so Anaconda should check for this. I had to hand-edit the grub.conf file to get a correct boot.

Comment 1 Chris Lumens 2010-05-27 23:14:03 UTC
anaconda preserves boot options from one install to the next, which usually works pretty well.  Unfortunately we cannot determine which machines do and do not require this parameter to be removed automatically, so we need to stick with our current policy.  Upgrades often have lots of little problems like this and do require some work by the user after completion.  We simply cannot take all possibilities into account.

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