Hi, I have a radeon mobility M64S, and when i switch to the console, i have strange colors and lines. the text is readable, but with splashy, you can easily see the corruption problem. I use the tonight 'git pull' and attached some pictures to illustrate the problems. Tanks. Laurent Marchal.
On Wed, Oct 24, 2007 at 01:07:44AM +0200, Laurent Marchal wrote:
Hi,
I have a radeon mobility M64S, and when i switch to the console, i have strange colors and lines. the text is readable, but with splashy, you can easily see the corruption problem. I use the tonight 'git pull' and attached some pictures to illustrate the problems.
Tanks.
Laurent Marchal.
This is definitely an issue with the dotclock. The graph/mode fifo is unable to work correctly as the dotclock is too unstable. I just sent up some patches, to help debug this, to henry's earlier mails. Luc Verhaegen. SUSE/Novell X Driver Developer. -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
Laurent Marchal schreef:
Hi,
I have a radeon mobility M64S, and when i switch to the console, i have strange colors and lines. the text is readable, but with splashy, you can easily see the corruption problem. I use the tonight 'git pull' and attached some pictures to illustrate the problems.
Is this the same issue I'm facing? After updating to the latest revision dbdcc96f8a1daab5e9bc7b086ed9e2630bb350e2, the console looks corrupted when switching back to it from a running X session: - the text is blue-ish instead of gray - the text at the right-hand side looks "eroded" A (not so clear) picture of it is available at http://home.tiscali.nl/rladan/corrupt_console.jpg The good thing is that the X screen looks slightly better now: if I sit a few inches from my screen I could first see that the pixels at the location of the 'back' button in FireFox were a bit noisy, this is now gone. Radeon Mobility X1450 on an Asus A6JE Regards, Rene -- GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) "It won't fit on the line." -- me, 2001 -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
Yes it's the same problem ! sometimes the whole text is squeezing too in console and a switch to the X session stop the squeeze and the text is just blue-ish instead of gray as you said. Luc Verhaegen : if you have little time to explain more in details "This is definitely an issue with the dotclock. The graph/mode fifo is unable to work correctly as the dotclock is too unstable." and where is the "dotclock" code we can look at ? this would be very nice. Laurent Matchal Le mercredi 24 octobre 2007, vous avez écrit :
Laurent Marchal schreef:
Hi,
I have a radeon mobility M64S, and when i switch to the console, i have strange colors and lines. the text is readable, but with splashy, you can easily see the corruption problem. I use the tonight 'git pull' and attached some pictures to illustrate the problems.
Is this the same issue I'm facing? After updating to the latest revision dbdcc96f8a1daab5e9bc7b086ed9e2630bb350e2, the console looks corrupted when switching back to it from a running X session: - the text is blue-ish instead of gray - the text at the right-hand side looks "eroded"
A (not so clear) picture of it is available at http://home.tiscali.nl/rladan/corrupt_console.jpg
The good thing is that the X screen looks slightly better now: if I sit a few inches from my screen I could first see that the pixels at the location of the 'back' button in FireFox were a bit noisy, this is now gone.
Radeon Mobility X1450 on an Asus A6JE
Regards, Rene
-- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
On Wed, Oct 24, 2007 at 10:13:13PM +0200, Laurent Marchal wrote:
Yes it's the same problem ! sometimes the whole text is squeezing too in console and a switch to the X session stop the squeeze and the text is just blue-ish instead of gray as you said.
Luc Verhaegen : if you have little time to explain more in details "This is definitely an issue with the dotclock. The graph/mode fifo is unable to work correctly as the dotclock is too unstable." and where is the "dotclock" code we can look at ? this would be very nice.
Laurent Matchal
There are several mail threads going on about this issue, please go back to the first one, as there it was debugged fully and fixed. I will push up the changes soon, after i've fixed another old sore. Luc Verhaegen. SUSE/Novell X Driver Developer. -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org
participants (3)
-
Laurent Marchal
-
Luc Verhaegen
-
Rene Ladan