Bug 722212

Summary: On install Fedora ...
Product: [Fedora] Fedora Reporter: marian <bispartacus>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 15CC: anaconda-maint-list, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-01 18:24:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
first
none
second
none
third
none
fourth none

Description marian 2011-07-14 16:12:35 UTC
Description of problem:
Run install from usbstick,select second option for launch install.After finish install boot from system fail. 

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:
On /etc/X11/xorg.conf vesa mode is selected, instead of nouveau driver in my case

Expected results:
Exist on xorg.conf right video module-nouveau driver on my case.

Additional info:

Comment 1 Brian Lane 2011-07-15 00:58:29 UTC
Please provide more details about what you are doing and what failed.

What and how did you write to the usb stick? What 'second option' did you select? eg. actual text

Attach the logs from /tmp/*log during the install, or /var/log/anaconda/* after the install to this bug as individual attachments.

Comment 2 marian 2011-07-15 04:10:34 UTC
Second options is Boot(Basic  Video).After finish install on xorg.conf remain
vesa driver on configuration which on my system do not  boot because nouveau
module is active.
Fixing this issue;Edit /etc/X11/xorg.conf and replace vesa word with nouveau.
On my system vesa driver don't boot after install.

Comment 3 Chris Lumens 2011-07-15 14:06:43 UTC
Please attach the log files asked for in comment #1.  Thanks.

Comment 4 marian 2011-07-15 21:16:23 UTC
Created attachment 513444 [details]
first

Comment 5 marian 2011-07-15 21:17:00 UTC
Created attachment 513445 [details]
second

Comment 6 marian 2011-07-15 21:17:32 UTC
Created attachment 513446 [details]
third

Comment 7 marian 2011-07-15 21:18:36 UTC
Created attachment 513447 [details]
fourth

Comment 8 Chris Lumens 2011-08-01 18:24:57 UTC
This is just how it works, though.  If you select the basic video option or otherwise add the --xdriver= flag to your anaconda command line, you will end up with the vesa driver while anaconda is running.  Then, we propagate that to the installed system on the theory that if you needed it while you were running the installation X server, you'll likely need it on the installed system too.

It sounds to me like you have a separate X-related bug that needs to be looked at, though that's not installer stuff.