Bug 507162 - vesa_drv cannot find CS5520.
Summary: vesa_drv cannot find CS5520.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-vesa
Version: 11
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-21 11:39 UTC by TAKADA Yoshihito
Modified: 2009-06-25 18:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-06-25 18:12:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
dmesg (12.79 KB, text/plain)
2009-06-21 11:40 UTC, TAKADA Yoshihito
no flags Details
lspci -v (1.57 KB, text/plain)
2009-06-21 11:41 UTC, TAKADA Yoshihito
no flags Details
Xorg.0.log (11.17 KB, text/plain)
2009-06-21 11:44 UTC, TAKADA Yoshihito
no flags Details

Description TAKADA Yoshihito 2009-06-21 11:39:54 UTC
Description of problem:
vesa_drv missing my graphics controller MediaGX internal, CS5520.

Version-Release number of selected component (if applicable):
Fedora 11
xorg-x11-drv-vesa-2.2.0-3.fc11.i586

How reproducible:
yes


Steps to Reproduce:
1. Install F11 to box of MediaGX(GeodeGX1) with CS5520. not a CS5530.
2. run X
3. vesa_drv cannot find graphics controller.
  
Actual results:
see attached files.
dmesg(special kernel. Fedora's kernel cannot boot.)
lspci -v
Xorg.0.log(it is result of X -configure).

Additional info:
In F8 and F9 vesa_drv works right.
vesa_drv of F11 pre-release shows X11 desktop.
This system was lost, because it was overwritten in F11.

Comment 1 TAKADA Yoshihito 2009-06-21 11:40:49 UTC
Created attachment 348785 [details]
dmesg

Output of dmesg.

Comment 2 TAKADA Yoshihito 2009-06-21 11:41:55 UTC
Created attachment 348786 [details]
lspci -v

Output of lspci -v

Comment 3 TAKADA Yoshihito 2009-06-21 11:44:36 UTC
Created attachment 348787 [details]
Xorg.0.log

Xorg.0.log when run X -configure.

Comment 4 Adam Jackson 2009-06-25 18:12:25 UTC
Yep.  The X server now only supports PCI devices and kernel framebuffer devices.  Yours appears to be neither.


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