Red Hat Bugzilla – Bug 577312
install: X startup failed, falling back to text mode
Last modified: 2018-04-11 10:42:06 EDT
Created attachment 402889 [details]
Description of problem: During fresh install from Fedora 13-beta-RC1 x86_64 DVD, selecting "Install with basic video driver" results in "X startup failed, falling back to text mode". The install proceeds with only VGA character-cell "graphics" instead of X11 graphics.
Version-Release number of selected component (if applicable):
How reproducible: every time
Steps to Reproduce:
1. Boot Fedora 13-beta-RC1 x86_64 DVD
2. Select Install with basic video driver
Actual results: X startup failed, falling back to text mode
Expected results: uses X11 graphics during install
Created attachment 402890 [details]
lspci; lspci -n; lspci -v
05:00.0 VGA compatible controller: nVidia Corporation G72 [GeForce 7300 SE] (rev a1)
Created attachment 402892 [details]
16:26:58,390 INFO kernel:[drm] Initialized drm 1.1.0 20060810
16:26:58,622 INFO kernel:[drm] nouveau 0000:05:00.0: Detected an NV40 generation card (0x246300b1)
16:26:58,623 INFO kernel:[drm] Initialized nouveau 0.0.16 20090420 for 0000:05:00.0 on minor 0
16:28:31,165 ERR kernel:[drm] nouveau 0000:05:00.0: called without init
Created attachment 403010 [details]
Same problem on a recent card:
07:27:29,124 INFO kernel:[drm] Initialized drm 1.1.0 20060810
07:27:29,534 INFO kernel:[drm] nouveau 0000:01:00.0: Detected an NV50 generation card (0x0a5000a2)
07:27:29,535 INFO kernel:[drm] Initialized nouveau 0.0.16 20090420 for 0000:01:00.0 on minor 0
07:28:00,362 ERR kernel:[drm] nouveau 0000:01:00.0: called without init
01:00.0 VGA compatible controller: nVidia Corporation Device 0a20 (rev a2)
01:00.0 0300: 10de:0a20 (rev a2)
01:00.0 VGA compatible controller: nVidia Corporation Device 0a20 (rev a2) (prog-if 00 [VGA controller])
Subsystem: XFX Pine Group Inc. Device 294a
Flags: bus master, fast devsel, latency 0, IRQ 18
Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
Memory at d0000000 (64-bit, prefetchable) [size=256M]
Memory at ce000000 (64-bit, prefetchable) [size=32M]
I/O ports at dc00 [size=128]
Expansion ROM at fea80000 [disabled] [size=512K]
Capabilities:  Power Management version 3
Capabilities:  MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities:  Express Endpoint, MSI 00
Capabilities: [b4] Vendor Specific Information: Len=14 <?>
Capabilities:  Virtual Channel
Capabilities:  Power Budgeting <?>
Capabilities:  Vendor Specific Information: ID=0001 Rev=1 Len=024 <?>
This is weird ... you ask for vesa and you get nouveau. Assigning to xserver, there is something weird there.
Seems like whoever-is-responsible for writing xorg.conf in cases user asks for xdriver=vesa didn't do its job. It could be possibly confused by /etc/xorg.conf.d which is a new thing in Fedora 13.
Reassigning to anaconda without prejudice for getting it back if it is shown to be Xorg bug after all.
Auch, sorry, taking it back.
It looks like the change might have been introduced by anaconda patch e146251c0bd1b9325401eb15b9b157d886a8ff4a from Mon Dec 21 10:20:47 2009 -0500.
We used to write /etc/X11/xorg.conf during the initialization of anaconda and then another one to /mnt/sysimage/etc/X11/xorg.conf during the configuration of the installed system.
This patch changed it and the file is being written to /mnt/sysimage/etc/X11/xorg.conf on both calls.
So I think it is our fault and also F13Blocker.
What is the proper place to put Device section with driver selection now? Should we use /etc/X11/xorg.conf or /etc/X11/xorg.conf.d/anaconda for example?
Commited to anaconda as 2b9955806d2a2f735898456963676d941d07b7c9.
*** Bug 582274 has been marked as a duplicate of this bug. ***
Hi, is this fix going to RHEL 6? It seems to be a problem there too when using kickstart.
No, because commit e146251c0bd1b9325401eb15b9b157d886a8ff4a caused this, and that was never committed to rhel6-branch. If you are seeing something, it's likely caused by something else. Please file a new bug with new information.
Tested TC1, this is fixed: selecting Basic Graphics mode gives you a graphical install with vesa (confirmed by checking the /etc/X11/xorg.conf file and /tmp/X.log).
Fedora Bugzappers volunteer triage team
I've reported bug 632805 which looks similar to this, for 14 Beta TC1.
Nope, it's not. It's just a known bug between vesa driver and qemu.
Fedora Bugzappers volunteer triage team