Bug 9961

Summary: default video configuration for Radeon X200/X300 does not work
Product: Mageia Reporter: Mike Rambo <mhrambo3501>
Component: InstallerAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED OLD QA Contact:
Severity: major    
Priority: Normal CC: anssi.hannula, fri
Version: Cauldron   
Target Milestone: ---   
Hardware: i586   
OS: Linux   
URL: https://forums.mageia.org/en/viewtopic.php?f=15&t=4799&p=33926#p33926
Whiteboard:
Source RPM: CVE:
Status comment:
Attachments: dmesg.txt
Xorg.9.log
Xorg.0.log

Description Mike Rambo 2013-05-03 16:11:06 CEST
Description of problem:
Testing mga3 RC on an older stock HP dx5150. The default video configuration does not work. Reboot after installation dumps me back to cli. There is an error there but I did not write it down. Changing to VESA driver enables the graphical interface to then work. XFdrake always want to select "ATI Radeon HD 4870 and earlier". I think this was what the installer had set too. It does not work. It was determined in the above forum thread that the X300 was not supported by that driver. This chipset may need to be blacklisted or in some way forced to use the VESA driver.

Version-Release number of selected component (if applicable):
Mageia 3 Release Candidate

How reproducible:
Simply installing the mga3 RC on this hardware results in this problem. Setting this to MAJOR as it will leave new installations people may try non-functional at least from a GUI perspective. Reset as you see fit.


Reproducible: 

Steps to Reproduce:
Comment 1 Manuel Hiebel 2013-05-05 12:30:15 CEST
Any improvement with the last updates ?

CC: (none) => anssi.hannula

Comment 2 Anssi Hannula 2013-05-05 12:38:23 CEST
"ATI Radeon HD 4870 and earlier" means _all_ Radeon cards until Radeon HD 4870. This includes Radeon X300 which is supported by the driver, including OpenGL 3D support. I agree the naming may be confusing, but it won't be changed for mga3.

Can you get us the contents of "/var/log/Xorg.0.log" and the output of "dmesg" (use "dmesg > dmesg.txt" to save to file) after the failure?
Comment 3 Mike Rambo 2013-05-07 18:32:46 CEST
Created attachment 3898 [details]
dmesg.txt
Comment 4 Mike Rambo 2013-05-07 18:33:30 CEST
Created attachment 3899 [details]
Xorg.9.log
Comment 5 Mike Rambo 2013-05-07 18:42:07 CEST
Attached both of the requested files. The latter was generated by attempting to set the ATI Radeon HD 4870 and earlier driver from XFdrake followed by a click on the test button. It fails with the no screens found error (that I thought I had mentioned in the bug but which I see I did not). I guess after having talked about this so much in the forums I forgot to put it in the bug report. Sorry for the missing information.
Comment 6 Mike Rambo 2013-05-07 19:11:17 CEST
Created attachment 3900 [details]
Xorg.0.log
Comment 7 Mike Rambo 2013-05-07 19:12:10 CEST
Have installed latestest updates and rebooted as suggested. No difference.
Comment 8 Morgan Leijström 2013-05-09 09:55:50 CEST
Works here: mga3 with "ATI Radeon HD 4870 and earlier" works for me on Thinkpad T43 2668-44G, and have done so a couple months since i installed mga3 beta something on it.

MCC hardware section describe it as "RV370/M22 [Mobility Radeon X300]".
Further down it say "Unit Sub-ID: 0x056e."
Maybe we have different chip versions?

Or you miss some firmware?

CC: (none) => fri

Comment 9 Mike Rambo 2013-05-09 13:24:08 CEST
The system has the following firmware installed. This the correct package??

radeon-firmware-20130421-1.mga3.nonfree
Comment 10 Mike Rambo 2013-05-23 16:28:17 CEST
Wanted to note that this is not a problem with Mageia 3 i586 release DVD. The installer picked the same ATI Radeon HD 4870 and earlier that dual arch CD installer used - but it works whereas before it did not. Could x86_64 be the difference? The dual arch CD I tested picked a 64 bit installation - which is appropriate for the hardware - while I chose the 32 bit i586 DVD for the final release since I want to use it on more than one machine.
Comment 11 Samuel Verschelde 2015-05-06 21:10:46 CEST
Closing as OLD (and comment #10 is encouraging about the status of the issue). Please reopen if needed.

Status: NEW => RESOLVED
Resolution: (none) => OLD