Red Hat Bugzilla – Bug 471365
Installer still does not switch to graphical install
Last modified: 2009-10-22 08:47:05 EDT
Description of problem:
I upgraded from Fedora 9 to Fedora 10 preview (x86_64) using a downloaded DVD-Image. I use an Asus M2N68-VM Mainboard with nVidia Corporation GeForce 7050 PV / nForce 630a (rev a2) (output from lspci).
=> please note that this is a relatively new motherboard
The graphical installer is not used during install.
I already filed this for an earlier (beta?) release of FC 9.
After the upgrade is finished, I get a running x system by just starting startx without any modification of config files. Is the config just copied from FC9 in this case or is the installed one working with my chipset?
Version-Release number of selected component (if applicable):
Fedora 10 preview x86_64 DVD image
Steps to Reproduce:
1. instsall FC9 x86_64
2. upgrade to FC 10 preview x86_64
Installer does not go in graphical install
Installer should go to graphical install
Please note, that the FC 9 install starts in graphical install and also leaves a working x configuration (vesa driver) behind.
Because text install does not provide all of the functionality an most users will not be able to configure x by hand, I strongly recommend to include at least the functionality of fc9 in the fc10 DVD.
Does it try to start X and then fall back and ask if you want to use the text installer instead? If so, please attach /tmp/X.log to this bug report. Also, please attach /tmp/anaconda.log in any case. Thanks.
I already did that for the beta of FC10, but nothing seemed to happen with my input. Now I start the installation again do the copying and stuff and hope this time it was not in vain.
Anaconda tried to start x and fell back to console.
Created attachment 323576 [details]
Created attachment 323577 [details]
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
Crosslinking to similar bugs:
*** This bug has been marked as a duplicate of bug 480541 ***