Binary nVidia-driver with GeForce2 Integrated GPU
Frank Steinborn
steinex at nognu.de
Sat Jul 18 16:34:11 UTC 2009
Hi list,
I have a box with a GeForce2 MX/MX400 onboard on an nForce-chipset and
want to use the binary nVidia-driver with it. I have to use the legacy
driver (96.43.13). It installs without problems, and the GPU gets
detected properly:
nvidia0: <GeForce2 Integrated GPU> on vgapci0
vgapci0: child nvidia0 requested pci_enable_busmaster
vgapci0: child nvidia0 requested pci_enable_io
nvidia0: [GIANT-LOCKED]
nvidia0: [ITHREAD]
However, if I start X, strange things happen. The video is shown, but
there are many artifacts and all looks kind of strange - it is
unusable. I can see the following from the nVidia-driver in dmesg
after X started:
NVRM: Xid (0002:00): 13, 0000 01014a00 0000004a 00000104 00000003
00000802
NVRM: Xid (0002:00): 13, 0000 01014a00 0000004a 00000104 00000003
00000802
NVRM: Xid (0002:00): 13, 0000 01014a00 0000004a 00000104 00000003
00000802
NVRM: Xid (0002:00): 13, 0000 01014a00 0000004a 00000104 00000003
00000802
NVRM: Xid (0002:00): 13, 0000 01016100 0000008a 00000104 00000003
00000002
NVRM: Xid (0002:00): 13, 0000 01014200 00000062 00000300 fffffff7
00000002
NVRM: Xid (0002:00): 13, 0000 01014200 00000062 00000300 fffffff1
00000002
NVRM: Xid (0002:00): 13, 0000 01016100 0000008a 00000104 97004200
00000002
NVRM: Xid (0002:00): 13, 0000 01016100 0000008a 00000104 97004200
00000002
NVRM: Xid (0002:00): 13, 0000 01016100 0000008a 00000104 97004200
00000002
NVRM: Xid (0002:00): 13, 0000 01014a00 0000004a 00000104 00000003
00000802
NVRM: Xid (0002:00): 13, 0000 01011900 00000019 00000104 00000003
00000802
NVRM: Xid (0002:00): 13, 0000 01011900 00000019 00000104 00000000
00000800
NVRM: Xid (0002:00): 13, 0000 01019700 00001196 00000c28 02410273
00000800
NVRM: Xid (0002:00): 13, 0000 01014a00 0000004a 00000104 00000003
00000802
NVRM: Xid (0002:00): 13, 0000 01016100 0000008a 00000104 97004200
00000002
The README of the driver says that Xid-errors occor when the card gets
wrong instructions from the driver and/or vice-versa, but that doesn't
help me much getting to the root of the problem.
What I've done so far to track this down:
- Tried the driver from ports (atm in version 96.43.11) and the one
from the website (96.43.13).
- installed compat5x (The nVidia page claims this is necessary).
- I tried with agp-support from the nVidia-driver and with agp-support
from the FreeBSD kernel.
All that did not changed the observed beharviour. I would be more than
happy if someone could provide me with a hint...
The Xorg.0.log doesn't provide meaningful informations, except the
Xid-errors shown above. xorg.conf attached.
Thanks,
Frank
-------------- next part --------------
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "Files"
FontPath "/usr/X11R6/lib/X11/fonts/terminus-font"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/sysmouse"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
HorizSync 30-60
VertRefresh 50-76
Option "DPMS"
EndSection
Section "Device"
Identifier "Card0"
Driver "nvidia"
VendorName "nVidia Corporation"
BoardName "NVCrush11 [GeForce2 MX Integrated Graphics]"
BusID "PCI:2:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 32
EndSubSection
EndSection
More information about the freebsd-questions
mailing list