[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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

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"

Here is the lspci output for this device:

07:00.0 VGA compatible controller: nVidia Corporation Quadro FX 3500 (rev a1) (prog-if 00 [VGA])
        Subsystem: nVidia Corporation Unknown device 032b
        Flags: bus master, fast devsel, latency 0, IRQ 11
        Memory at dd000000 (32-bit, non-prefetchable) [size=16M]
        Memory at c0000000 (64-bit, prefetchable) [size=256M]
        Memory at de000000 (64-bit, non-prefetchable) [size=16M]
        I/O ports at dc80 [size=128]
        Expansion ROM at dfb00000 [disabled] [size=128K]
        Capabilities: [60] Power Management version 2
        Capabilities: [68] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
        Capabilities: [78] Express Endpoint IRQ 0
        Capabilities: [100] Virtual Channel
        Capabilities: [128] Power Budgeting

lspci -n output:

00:07.0 0604: 8086:25e7 (rev 12)

: :' :      We are debian.org. Lower your prices, surrender your code.
`. `'       We will add your hardware and software distinctiveness to
  `-        our own. Resistance is futile.

Reply to: