Bug 1475 - radeon HD 6310 does not work with ati but does with fglrx
Summary: radeon HD 6310 does not work with ati but does with fglrx
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2011-05-29 23:59 CEST by JeanBaptiste Lamy
Modified: 2012-01-18 08:09 CET (History)
3 users (show)

See Also:
Source RPM: x11-driver-video-ati
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description JeanBaptiste Lamy 2011-05-29 23:59:07 CEST 
My radeon HD 6310 card (integrated in the AMD E350 processor) is automatically configured by Mageia with the "ati" free driver, however this driver does not work and produce random pixels on the screen.

However, the radeon HD 6310 works well with the ATI proprietary driver (installed manually in RPMDrake) or the "vesa" driver.
Comment 1 Thierry Vignaud 2011-10-04 17:47:28 CEST 
What's the output of "lspcidrake -v|grep Card" ?

Keywords: (none) => NEEDINFO
CC: (none) => thierry.vignaud
Component: Installer => RPM Packages
Source RPM: (none) => ldetect-lst

Comment 2 JeanBaptiste Lamy 2011-10-04 20:08:29 CEST 
jiba dans ~ :  lspcidrake -v|grep Card

Card:ATI Radeon HD 2000 and later (radeon/fglrx): ATI Technologies Inc|Device 9802 [DISPLAY_VGA] (vendor:1002 device:9802 subv:1043 subd:84a5)
Comment 3 Thierry Vignaud 2011-10-06 10:23:01 CEST 
Can you also attach your /var/log/Xorg.0.log when using ati?
Or your  /var/log/Xorg.9.log if you just made the test in XFdrake
Comment 4 Thierry Vignaud 2011-11-27 23:35:56 CET 
ping?
Thierry Vignaud 2011-12-10 04:26:10 CET

CC: (none) => anssi.hannula
Summary: radeon HD 6310 not working => radeon HD 6310 does not work with ati but does with fglrx
Source RPM: ldetect-lst => x11-driver-video-ati

Comment 5 Marja Van Waes 2012-01-18 08:09:06 CET 
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Status: NEW => RESOLVED
CC: (none) => marja11
Resolution: (none) => OLD
Note You need to log in before you can comment on or make changes to this bug.