Hi, thanks for reporting this bug.
Assigned to the package maintainer.

(Please set the status to 'assigned' if you are working on it)

Assignee: bugsquad => thierry.vignaud
Keywords: (none) => Triaged
Source RPM: (none) => drakxtools

Adding radeon.modeset=0 to the kernel options fixes this.  I guess KMS doesn't work on this chipset.

Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D

This can't be fixed for Mageia 1 now.  I have yet to test and verify if it's still an issue with Mageia 2.

Whiteboard: (none) => OK

This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 1's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not 
be able to fix it before Mageia 1 is end of life.  If you would still like to see 
this bug fixed and are able to reproduce it against a later version of Mageia, 
you are encouraged to click on "Version" and change it against that version 
of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no 
longer maintained, which means that it will not receive any further security or 
bug fix updates. As a result we are closing this bug. 

If you can reproduce this bug against a currently maintained version of Mageia 
please feel free to click on "Version" change it against that version of Mageia and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
Mageia Bugsquad

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

Still valid on Mageia 2.

Version: 1 => 2
Resolution: WONTFIX => (none)
Status: RESOLVED => REOPENED

This issue is now more serious as of Mageia 3.  If you don't have radeon.modeset = 0, the console size is still incorrect.  However, if you *do* have it, X is unable to start!  FWIW I do have radeon-firmware installed.

Version: 2 => Cauldron
Whiteboard: OK => MGA3TOO, MGA2TOO

What about Mga5?

Keywords: (none) => NEEDINFO
Version: Cauldron => 3

No reason to think it's changed, I'll check mga5 when it comes out.

Whiteboard: MGA4TOO => MGA3TOO
Version: 3 => 4

well: both kernel & ati drivers have been improved quite a lot.
We definitively want testing _before_ the final release, not after...

We're talking about the console, so am I correct in saying that the only "driver" that is important here is the KMS one in the kernel itself?  If so, if possible, I could try installing the Cauldron kernel on it and see how it looks.  I depend heavily on this laptop throughout the week, so I'm not ready to fully upgrade it to an unfinished release.

Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

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

Sorry for the delay, this is still valid.

Resolution: OLD => (none)
Status: RESOLVED => REOPENED
Version: 4 => Cauldron

(In reply to David Walser from comment #15)
> Sorry for the delay, this is still valid.

If it is still valid in current cauldron, then please remove "NEEDINFO".
Thanks :-)

Whiteboard: MGA3TOO => (none)
CC: (none) => marja11

I doubt current Cauldron is really testable.  Anyway, as long as nothing's done to fix it, it will remain valid.

Keywords: NEEDINFO => (none)

...now 5 more years are gone ...and this fine piece of hardware is now 20 years old! Is it still in use David? 

Any updates on this? Can we close it OLD or is there still (invisible) progress?

It's actually only 17 years old :P

I do still have it, but I am not currently using it.

Resolution: (none) => WONTFIX
Status: REOPENED => RESOLVED