Bug 696644 - UMS:REDWOOD: Missing support for ATI FirePro V3800
Summary: UMS:REDWOOD: Missing support for ATI FirePro V3800
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 14
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Jérôme Glisse
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-14 14:08 UTC by Erik P. Olsen
Modified: 2018-04-11 12:11 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-15 20:43:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
/var/log/dmesg (55.91 KB, text/plain)
2011-04-14 19:06 UTC, Erik P. Olsen
no flags Details

Description Erik P. Olsen 2011-04-14 14:08:39 UTC
Description of problem: Missing or broken support for ATI FirePro V3800


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


How reproducible:Always


Steps to Reproduce:
1.Install ATI FirePro V3800
2.Boot
3.
  
Actual results:Black screen before display of logon screen


Expected results:Logon screen


Additional info:

Comment 1 Matěj Cepl 2011-04-14 14:54:52 UTC
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information especially concerning your hardware we require that will be helpful in our diagnosis of this issue.

If the anaconda crashes during the switching to the graphic mode, most likely the problem lies in Xorg support for your graphics chip. There are couple of options how we can obtain information necessary for resolving the issue.

If the computer is not completely frozen when installation fails, switch to the console (Ctrl+Alt+F2) and copy /tmp/X* and /var/log/anaconda.xlog to some other place -- USB stick, some other computer via network, somewhere on the Internet, and please attach it to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

If the computer is completely useless after installation fails, you can also install Fedora with a VESA mode driver (see http://docs.fedoraproject.org/en-US/Fedora/13/html/Installation_Guide/
for more information on that). Then after successful installation you can collect /var/log/anaconda.xlog, /var/log/Xorg.0.log, and the output of the program dmesg instead.

Or you can install Fedora in a text mode completely, and then start X after that. If it fails, still /var/log/Xorg.0.log and the output of dmesg program from the failed attempt to start X would be useful.

We will review this issue again once you've had a chance to attach this information.

Thank you very much in advance.

Comment 2 Erik P. Olsen 2011-04-14 19:06:15 UTC
Created attachment 492202 [details]
/var/log/dmesg

Attached as requested.

Comment 3 Erik P. Olsen 2011-04-14 19:11:01 UTC
Forgot to say that dmesg was after startx and that Xorg.0.log was empty.

Comment 4 Jérôme Glisse 2011-04-15 13:33:25 UTC
Remove nomodeset radeon.modeset=0 from your kernel boot line

We don't support UMS. Also you would need a more recent kernel (updating your fedora should bring a recent enough kernel with support for your gpu)

Comment 5 Erik P. Olsen 2011-04-15 14:47:20 UTC
Thanks a lot. It's a little slow but at least it's supported.

Comment 6 Matěj Cepl 2011-04-15 16:01:06 UTC
(In reply to comment #5)
> Thanks a lot. It's a little slow but at least it's supported.

So, does it mean that this bug can be closed?

Comment 7 Erik P. Olsen 2011-04-15 16:40:35 UTC
Yes.


Note You need to log in before you can comment on or make changes to this bug.