Bug#168178: nvidia geforce2 mx 400 shows the same behaviour

2002-11-12 Thread Branden Robinson
On Sun, Nov 10, 2002 at 10:31:03AM +0100, [EMAIL PROTECTED] wrote: > ack. here they come. > > The system is an AMD XP 2000+ w/ 512M RAM. The attached configuration worked > just fine until packages were upgraded. Thank you very much for following up! -- G. Branden Robinson|

Bug#168178: nvidia geforce2 mx 400 shows the same behaviour

2002-11-12 Thread Branden Robinson
On Sun, Nov 10, 2002 at 10:31:03AM +0100, [EMAIL PROTECTED] wrote: > ack. here they come. > > The system is an AMD XP 2000+ w/ 512M RAM. The attached configuration worked > just fine until packages were upgraded. Thank you very much for following up! -- G. Branden Robinson|

Bug#168178: nvidia geforce2 mx 400 shows the same behaviour

2002-11-10 Thread ziegler
ack. here they come. The system is an AMD XP 2000+ w/ 512M RAM. The attached configuration worked just fine until packages were upgraded. regards, hz > On Sat, Nov 09, 2002 at 03:41:56PM +0100, H. Ziegler wrote: > > finally the server doesn't start because: > > "caught signal 11. server aborti

Bug#168178: nvidia geforce2 mx 400 shows the same behaviour

2002-11-10 Thread ziegler
ack. here they come. The system is an AMD XP 2000+ w/ 512M RAM. The attached configuration worked just fine until packages were upgraded. regards, hz > On Sat, Nov 09, 2002 at 03:41:56PM +0100, H. Ziegler wrote: > > finally the server doesn't start because: > > "caught signal 11. server aborti

Bug#168178: nvidia geforce2 mx 400 shows the same behaviour

2002-11-09 Thread Branden Robinson
On Sat, Nov 09, 2002 at 03:41:56PM +0100, H. Ziegler wrote: > finally the server doesn't start because: > "caught signal 11. server aborting" > > let me know if you need more info. I always need the info described in the XF86Config(7) manual page. $ man 7 XF86Config -- G. Branden Robinson

Bug#168178: nvidia geforce2 mx 400 shows the same behaviour

2002-11-09 Thread Branden Robinson
On Sat, Nov 09, 2002 at 03:41:56PM +0100, H. Ziegler wrote: > finally the server doesn't start because: > "caught signal 11. server aborting" > > let me know if you need more info. I always need the info described in the XF86Config(7) manual page. $ man 7 XF86Config -- G. Branden Robinson

Bug#168178: nvidia geforce2 mx 400 shows the same behaviour

2002-11-09 Thread Eduard Bloch
#include * H. Ziegler [Sat, Nov 09 2002, 03:41:56PM]: > package: xserver-xfree86 > version: 4.2.1-3 > > packages from testing, latest driver from nvidia(1.0-3123) compiled > against 2.4.19 and/or 2.4.20-rc1. > > kernel reports "no more MTRRs available", the messages in XFree86.0.log > are the

Bug#168178: nvidia geforce2 mx 400 shows the same behaviour

2002-11-09 Thread Eduard Bloch
#include * H. Ziegler [Sat, Nov 09 2002, 03:41:56PM]: > package: xserver-xfree86 > version: 4.2.1-3 > > packages from testing, latest driver from nvidia(1.0-3123) compiled > against 2.4.19 and/or 2.4.20-rc1. > > kernel reports "no more MTRRs available", the messages in XFree86.0.log > are the

Bug#168178: nvidia geforce2 mx 400 shows the same behaviour

2002-11-09 Thread H. Ziegler
package: xserver-xfree86 version: 4.2.1-3 packages from testing, latest driver from nvidia(1.0-3123) compiled against 2.4.19 and/or 2.4.20-rc1. kernel reports "no more MTRRs available", the messages in XFree86.0.log are the same, except the driver reporting the warning is NV(0). the message

Bug#168178: nvidia geforce2 mx 400 shows the same behaviour

2002-11-09 Thread H. Ziegler
package: xserver-xfree86 version: 4.2.1-3 packages from testing, latest driver from nvidia(1.0-3123) compiled against 2.4.19 and/or 2.4.20-rc1. kernel reports "no more MTRRs available", the messages in XFree86.0.log are the same, except the driver reporting the warning is NV(0). the message co