Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: If I use the default install options for fedora 14 alpha (installing from DVD), I seem to run into the common bug 596985. If I follow the recommendation in the release notes to use the basic video driver, anaconda tells me it can't start X and wants to use text mode (or VNC). Version-Release number of selected component (if applicable): Whatever is on the fedora 14 alpha x86_64 DVD. How reproducible: every install attempt so far. Steps to Reproduce: 1.boot dvd 2.pick basic video 3.watch it say it can't start X Actual results: can't start X Expected results: GUI installer Additional info: video card is: 01:00.0 VGA compatible controller: ATI Technologies Inc RV410 [Radeon X700 Pro (PCIE)] This card actually works quite well in fedora 13, unfortunately fedora 14 seems to have gone backward. I also see what appears to be a kernel crash walkback early in the boot from DVD, but it flashes past too fast to see any details.
Created attachment 441335 [details] X.log from install attempt I tried the install one more time and was able to capture the log files from /tmp on a pen drive, so I'm attaching them here. Looks like the vesa driver tried a screen resolution which barfed on it.
Created attachment 441336 [details] anaconda.log
Created attachment 441337 [details] libuser.N8EtI0
Created attachment 441338 [details] program.log
Created attachment 441339 [details] storage.log
Created attachment 441340 [details] syslog
Can you get the Beta TC1 and see how this behaves now? http://serverbeach1.fedoraproject.org/pub/alt/stage/14-Beta.TC1/ -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I just tried booting the Beta TC1, and the ATI driver does indeed seem to work fine, but if I try to use the vesa driver it still fails, even if I add something like resolution=1024x768 to the anaconda boot options. Probably not that important since I don't need to use vesa anymore, but still strange.
Created attachment 446551 [details] X log from xdriver=vesa resolution=1024x768 Here's the X log from the failed attempt to boot with vesa driver in the Beta TC1 x86_64 DVD iso.
-- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
(In reply to comment #1) > Created attachment 441335 [details] > X.log from install attempt > > I tried the install one more time and was able to capture the log files > from /tmp on a pen drive, so I'm attaching them here. Looks like the vesa > driver tried a screen resolution which barfed on it. What did you use as a mount point for the pen drive? I tried mounting mine on /mnt (which was already populated), which didn't work (some commands were unrecognized after the mount). I don't want to actually reinstall on this box so it needs to be nondestructive to the existing installation.
Never mind, I made a subdirectory in the same directory where the log files were located, copied the files, and my existing install seems unaffected.
propose for F14 Beta NTH list (new system for tracking bugs that aren't blockers but for which we'll accept fixes through the freeze)
Just tried the release F14 beta x86_64, same vesa driver failure.
This was discussed at the 2010-10-01 blocker / NTH review meeting, and accepted as a nice-to-have.
Basic video driver works well now on "ATI Radeon X800 SE (R430) (PCIE)" (ChipID = 0x554e) connected to a 21" CRT HP A4576A. Until recently, no valid modes were found.
Removing F14 NTH status as F14 is now out. Remaining open nice-to-have issues do NOT automatically become nice-to-have issues for Fedora 15. If you believe a Fedora 14 issue which was accepted as nice-to-have but not resolved in time for release should also qualify for nice-to-have status for Fedora 15, please re-propose it as nice-to-have for Fedora 15. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
F14 is EOL. If this is still reproducible in F15 or later _and_ the KMS driver still does not work for your chip, please file a new bug with the details.