Bug#407138: autodetection leads to vesa used instead of nv

2007-01-19 Thread Josselin Mouette
Le jeudi 18 janvier 2007 à 22:40 +0100, Petter Reinholdtsen a écrit : [Josselin Mouette] lspci -n output: 00:07.0 0604: 8086:25e7 (rev 12) This is the wrong device. It is a bridge. Please send info on PCI device 07:00.0. I suspect it is PCI id 10de:029d, but need you to confirm it.

Bug#407138: autodetection leads to vesa used instead of nv

2007-01-18 Thread Petter Reinholdtsen
[Josselin Mouette] lspci -n output: 00:07.0 0604: 8086:25e7 (rev 12) This is the wrong device. It is a bridge. Please send info on PCI device 07:00.0. I suspect it is PCI id 10de:029d, but need you to confirm it. Friendly, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL

Bug#407138: autodetection leads to vesa used instead of nv

2007-01-16 Thread Josselin Mouette
Package: discover1-data Version: 2.2006.12.28 I've just installed etch on a brand new Xeon system with a nVidia Quadro FX 3500 graphics card, and the X server configured itself to use the vesa driver, while this card is perfectly supported by the nv driver. Here is the lspci output for this