Re: xfree86 4.1.0 ati rage 128

2001-08-16 Thread christophe barbé
Check in the debian-user mailing list archive, this is a know issue. You need to override a .o file found in a tgz from XFree. Or check the bug page of xserver-xfree86. http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=xserver%2Dxfree86 Christophe Le jeu, 16 aoû 2001 11:16:40, Tim Connors a écri

Re: xfree86 4.1.0 ati rage 128

2001-08-16 Thread Vivek
On Thu, 16 Aug 2001, Tim Connors wrote: > > I had no problems with xfree86 4.0.x on my dell inspiron 4000, but after > upgrading to 4.1.0, I now have crud all over my text console when I either > quit X or go to the console. I have temporarily solved this problem by Assuming you don't have an fb

Re: xfree86 4.1.0 ati rage 128

2001-08-16 Thread christophe barbé
Check in the debian-user mailing list archive, this is a know issue. You need to override a .o file found in a tgz from XFree. Or check the bug page of xserver-xfree86. http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=xserver%2Dxfree86 Christophe Le jeu, 16 aoû 2001 11:16:40, Tim Connors a écr

xfree86 4.1.0 ati rage 128

2001-08-16 Thread Tim Connors
I had no problems with xfree86 4.0.x on my dell inspiron 4000, but after upgrading to 4.1.0, I now have crud all over my text console when I either quit X or go to the console. I have temporarily solved this problem by using a savetextmode/textmode combination, but this is tedious for everytime I

Re: xfree86 4.1.0 ati rage 128

2001-08-16 Thread Vivek
On Thu, 16 Aug 2001, Tim Connors wrote: > > I had no problems with xfree86 4.0.x on my dell inspiron 4000, but after > upgrading to 4.1.0, I now have crud all over my text console when I either > quit X or go to the console. I have temporarily solved this problem by Assuming you don't have an fb

xfree86 4.1.0 ati rage 128

2001-08-16 Thread Tim Connors
I had no problems with xfree86 4.0.x on my dell inspiron 4000, but after upgrading to 4.1.0, I now have crud all over my text console when I either quit X or go to the console. I have temporarily solved this problem by using a savetextmode/textmode combination, but this is tedious for everytime I