Bug 627073

Summary: VESA driver does not work with X700 Pro (1002:5e4b)
Product: [Fedora] Fedora Reporter: Tom Horsley <horsley1953>
Component: xorg-x11-drv-vesaAssignee: Adam Jackson <ajax>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 14CC: awilliam, jfrieben, robatino, xgl-maint
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-03 19:30:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
X.log from install attempt
none
anaconda.log
none
libuser.N8EtI0
none
program.log
none
storage.log
none
syslog
none
X log from xdriver=vesa resolution=1024x768 none

Description Tom Horsley 2010-08-25 01:34:15 UTC
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.

Comment 1 Tom Horsley 2010-08-26 21:43:10 UTC
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.

Comment 2 Tom Horsley 2010-08-26 21:43:41 UTC
Created attachment 441336 [details]
anaconda.log

Comment 3 Tom Horsley 2010-08-26 21:44:37 UTC
Created attachment 441337 [details]
libuser.N8EtI0

Comment 4 Tom Horsley 2010-08-26 21:45:03 UTC
Created attachment 441338 [details]
program.log

Comment 5 Tom Horsley 2010-08-26 21:45:30 UTC
Created attachment 441339 [details]
storage.log

Comment 6 Tom Horsley 2010-08-26 21:45:57 UTC
Created attachment 441340 [details]
syslog

Comment 7 Adam Williamson (Red Hat non-Fedora) 2010-09-10 08:12:18 UTC
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

Comment 8 Tom Horsley 2010-09-10 16:34:43 UTC
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.

Comment 9 Tom Horsley 2010-09-10 16:37:20 UTC
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.

Comment 10 Adam Williamson (Red Hat non-Fedora) 2010-09-10 17:02:57 UTC

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 11 Andre Robatino 2010-09-12 23:32:28 UTC
(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.

Comment 12 Andre Robatino 2010-09-12 23:59:39 UTC
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.

Comment 13 Adam Williamson (Red Hat non-Fedora) 2010-09-15 16:35:23 UTC
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)

Comment 14 Adam Williamson (Red Hat non-Fedora) 2010-09-28 01:42:44 UTC

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 15 Tom Horsley 2010-09-29 22:18:52 UTC
Just tried the release F14 beta x86_64, same vesa driver failure.

Comment 16 Adam Williamson (Red Hat non-Fedora) 2010-10-01 21:29:37 UTC
This was discussed at the 2010-10-01 blocker / NTH review meeting, and accepted as a nice-to-have.

Comment 17 Joachim Frieben 2010-10-21 19:41:43 UTC
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.

Comment 18 Adam Williamson (Red Hat non-Fedora) 2010-11-01 23:00:32 UTC
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

Comment 19 Adam Williamson (Red Hat non-Fedora) 2010-11-01 23:00:45 UTC

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 20 Adam Jackson 2012-01-03 19:30:06 UTC
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.