My Matrox G200 died with 2.5.51

Hi all.
I compiled the new 2.5.51 kernel and enabled the new framebuffer with 
the VESA generic driver.
My system is a Slackware 8.0. My graphic card was a Matrox G200 and the 
resolution of fb console was 1024 X 768, 16M of colors (0x318).
When I rebooted with my new kernel, i noted that fb didn't work well 
(when i switched from a tty to another, some parts of the first tty were 
"pasted" to the second).
When I rebooted, my Matrox G200 died definetly.  I've made something 
wrong or it's an fb's bug?
If it is a bug, I hope to have been helpful.
see you,

    Moreno




-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/

I compiled the new 2.5.51 kernel and enabled the new framebuffer with 
the VESA generic driver.
My system is a Slackware 8.0. My graphic card was a Matrox G200 and the 
resolution of fb console was 1024 X 768, 16M of colors (0x318).
When I rebooted with my new kernel, i noted that fb didn't work well 
(when i switched from a tty to another, some parts of the first tty were 
"pasted" to the second).
When I rebooted, my Matrox G200 died definetly.  I've made something 
wrong or it's an fb's bug?
If it is a bug, I hope to have been helpful.
see you,

Your card died :-( Sounds like your hardware bit the dust. The VESA code 
isn't able to kill any cards as it depends on the BIOS to do the right 
thing.




-------------------------------------------------------
This SF.NET email is sponsored by:  The Best Geek Holiday Gifts!
Time is running out!  Thinkgeek.com has the coolest gifts for
your favorite geek.   Let your fingers do the typing.   Visit Now.
T H I N K G E E K . C O M        http://www.thinkgeek.com/sf/