Bug 691609 - display freeze on boot if nomodeset is not set
Summary: display freeze on boot if nomodeset is not set
Keywords:
Status: CLOSED DUPLICATE of bug 493754
Alias: None
Product: Fedora
Classification: Fedora
Component: LiveCD
Version: 15
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-29 00:28 UTC by Chris Murphy
Modified: 2013-01-10 06:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-28 03:18:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
dmesg output nouveau "hang" (109.38 KB, text/plain)
2011-03-29 00:28 UTC, Chris Murphy
no flags Details

Description Chris Murphy 2011-03-29 00:28:40 UTC
Created attachment 488309 [details]
dmesg output nouveau "hang"

Description of problem: During LiveCD boot, display hangs at 
[    1.608692] fb: conflicting fb hw usage nouveaufb vs EFI VGA - removing generic driver

Although it has successfully finished booting, it is possible to blindly login as root and reboot (or save dmesg output!). Problem does not occur if kernel line includes "nomodeset" so this may be a nouveau + EFI bug.

Version-Release number of selected component (if applicable):
Fedora-15-Alpha-x86_64-Live-Desktop.iso
2.6.38-0.rc5.git1.1.fc15.x86_64
Also tried with 2.6.35.6, 2.6.35.11 same results with f14.

How reproducible:
100% when (U)EFI booting.
0% when BIOS emulation booting.
0% when (U)EFI booting with kernel line "nomodeset"

Steps to Reproduce:
1. Boot from Live CD on USB stick (using livecd-iso-to-disk with --efi) in native EFI mode.
2. Allow GRUB to autoboot (timeout)

  
Actual results:
Fedora splashscreen appears, then vanishes leaving a single line of text on-screen:
[    1.608692] fb: conflicting fb hw usage nouveaufb vs EFI VGA - removing generic driver


Expected results:
Expect the liveCD to boot all the way to the desktop.


Additional info (regression):

1. Using kernel line nomodeset allows boot to proceed (have other issues later).

2. More from dmesg
[    1.601497] nouveau 0000:01:00.0: enabling device (0002 -> 0003)
[    1.601505] nouveau 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[    1.601511] nouveau 0000:01:00.0: setting latency timer to 64
[    1.608687] [drm] nouveau 0000:01:00.0: Detected an NV50 generation card (0x084700a2)
[    1.608690] checking generic (c0060000 708000) vs hw (c0000000 10000000)
[    1.608692] fb: conflicting fb hw usage nouveaufb vs EFI VGA - removing generic driver
[    1.634737] Console: switching to colour dummy device 80x25
[    1.655185] [drm] nouveau 0000:01:00.0: Attempting to load BIOS image from PRAMIN
[    1.655193] [drm] nouveau 0000:01:00.0: ... BIOS signature not found
[    1.655195] [drm] nouveau 0000:01:00.0: Attempting to load BIOS image from PROM
[    1.655199] [drm] nouveau 0000:01:00.0: ... BIOS signature not found
[    1.655201] [drm] nouveau 0000:01:00.0: Attempting to load BIOS image from PCIROM
[    1.655290] nouveau 0000:01:00.0: Invalid ROM contents
[    1.655334] [drm] nouveau 0000:01:00.0: ... BIOS signature not found
[    1.655336] [drm] nouveau 0000:01:00.0: Attempting to load BIOS image from ACPI
[    1.655338] [drm] nouveau 0000:01:00.0: ... BIOS signature not found
[    1.655340] [drm] nouveau 0000:01:00.0: No valid BIOS image found
[    1.666705] nouveau 0000:01:00.0: PCI INT A disabled

3.
Full dmesg log attached.

4.
fn + control + option + f2 brings up a console with login (but you can't see it). Type in root, then return. Type in your choice of commands in the blind...

Comment 1 Chris Murphy 2011-03-29 03:59:31 UTC
Related to:
https://bugs.freedesktop.org/show_bug.cgi?id=35267

However, for LiveCD this is a show stopper bug for supporting EFI booting with LiveCD. EFI boot for installation is necessary because:

"You cannot install the operating system on a system that uses BIOS and then boot this installation on a system that uses UEFI. "
http://docs.fedoraproject.org/en-US/Fedora/14/html/Installation_Guide/ch-Boot-x86.html

Comment 2 Chris Murphy 2011-03-31 00:15:02 UTC
Additional info here:
http://bugzilla.redhat.com/show_bug.cgi?id=493754#c12

Summary: Without a means to retrieve VBIOS on the affected models (at least Macbook Pro 4,1), EFI native booting may not be possible. Even if it is possible, it will probably require either text only mode or BIOS emulation based installation of the system, and then fixing it after the fact for EFI booting.

Unclear how the author of this page was able to get a Macbook Pro 4,1 to EFI boot.
http://grub.enbug.org/TestingOnMacbook

Suggestion that this either be closed, or marked as duplicate of 493754.

Comment 3 Matthias Clasen 2011-04-28 03:18:19 UTC

*** This bug has been marked as a duplicate of bug 493754 ***


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