| View previous topic :: View next topic |
| Author |
Message |
boemba
n00b
Joined: 09 Apr 2003
Posts: 54
Location: Dendermonde
|
 Posted: Tue Apr 22, 2003 8:23 pm Post subject: Nvidia probleempje |
 |
|
Hoi hier ben ik weer.
ik heb zonet NVidia drivers glx en kernel ge-emerged en ik heb dan de nodige aanpassingen gemaakt zoals beschreven in de readme. maar wanneer ik driver naar nvidia zet werkt X niet meer. De oplossing ligt allicht me allicht voor de neus maar ik kijk er weer es over. Wanneer ik de driver verander krijg ik volgende foutmelding:
(II) LoadModule: "nvidia"
(II) Loading /usr/X11R6/lib/modules/drivers/nvidia_drv.o
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.4349
Module class: XFree86 Video Driver
(II) NVIDIA XFree86 Driver 1.0-4349 Thu Mar 27 19:02:58 PST 2003
(II) NVIDIA Unified Driver for all NVIDIA GPUs
(II) Primary Device is: PCI 01:00:0
(WW) NVIDIA: Chipset "GeForce2 MX/MX 400" in Device section "nvidia" isn't valid for this driver
(EE) No devices detected.
Fatal server error:
no screens found
Iemand een idee wat het zou kunnen zijn?
Met vriendelijke groeten |
|
| Back to top |
|
 |
rbonthond
Apprentice
Joined: 24 Jun 2002
Posts: 190
|
| Posted: Tue Apr 22, 2003 9:08 pm Post subject: |
|
|
dit is mijn configuratie:
| Code: |
Section "Device"
# got me a spliffy card !
Identifier "NVidia GeForce4 Ti 4600"
VendorName "NVidia"
BoardName "ASUS"
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
Driver "nvidia"
# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.
#ChipSet "GeForce4 Ti 4600"
# Various other lines can be specified to override the driver's automatic
# detection code. In most cases they are not needed.
#VideoRam 256
#Clocks 25.2 28.3
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.
#BusID "PCI:0:10:0"
# Various option lines can be added here as required. Some options
# are more appropriate in Screen sections, Display subsections or even
# Monitor sections.
# Uncomment following option if you see a
# big white block instead of the cursor!
#Option "sw_cursor"
# general options
Option "NvAgp" "1"
#Option "DPMS" "on"
Option "NoLogo" "on"
# nice cursor shadow
# not needed anymore with xfree-4.3.0
#Option "CursorShadow" "true"
#Option "CursorShadowAlpha" "64"
#Option "CursorShadowXOffset" "2"
#Option "CursorShadowYOffset" "2"
# new nvidia driver requires to turn
# on 2d accelaration
#nvidia 3123 and lower syntax
#Option "NoRenderAccel"
#nvidia 4191 and higher syntac
#Option "RenderAccel" "true"
#disabled it: gives random lock-ups for me
# setup twinview with tv-out
# only enable 1024x768 for tv, ti4600 can handle that
# for movies: switch to fullscreen and display is
# on both monitor and tv !
# for desktop: switch to 1024x768 and desktop is same
# on both screens
# todo: i have a 100hz tv...
# if only i would know the hsync...
Option "TwinView"
Option "SecondMonitorHorizSync" "33-50"
Option "SecondMonitorVertRefresh" "60"
Option "TwinViewOrientation" "Clone"
Option "MetaModes" "1600x1200,NULL;1280x1024,NULL;1024x768,1024x768"
Option "TVStandard" "PAL-G"
Option "TVOutFormat" "SVIDEO"
EndSection
|
mijn eerste gok bij jou probleem:
haal die ChipSet setting eruit, de driver zal ut wel zelf uitvogelen. |
|
| Back to top |
|
|
boemba
n00b
Joined: 09 Apr 2003
Posts: 54
Location: Dendermonde
|
| Posted: Wed Apr 23, 2003 2:43 am Post subject: |
|
|
| Bedankt dat was inderdaad het probleem, het was dus echt iets simpels. Ik had er nooit bij stilgestaan dat dat tot de mogelijkheden zou behoren om die chipset eruit te smijten |
|
| Back to top |
|
|
JefP@@
Apprentice
Joined: 09 May 2002
Posts: 179
Location: Belgium
|
| Posted: Thu Apr 24, 2003 7:42 am Post subject: |
|
|
Dat heb je nu eenmaal met closed source drivers ...  |
|
| Back to top |
|
|
rbonthond
Apprentice
Joined: 24 Jun 2002
Posts: 190
|
| Posted: Thu Apr 24, 2003 8:30 pm Post subject: |
|
|
| JefP@@ wrote: | | Dat heb je nu eenmaal met closed source drivers ... |
wees blij dat er drivers zijn |
|
| Back to top |
|
|
Stuartje
Apprentice
Joined: 12 Dec 2002
Posts: 165
|
| Posted: Thu Apr 24, 2003 8:43 pm Post subject: |
|
|
En goeie! Ik heb nog nooit klagen gehad over die nvidia drivers, das iets anders dan met SiS  |
|
| Back to top |
|
|
JefP@@
Apprentice
Joined: 09 May 2002
Posts: 179
Location: Belgium
|
| Posted: Wed Apr 30, 2003 9:05 am Post subject: |
|
|
| rbonthond wrote: | | JefP@@ wrote: | | Dat heb je nu eenmaal met closed source drivers ... |
wees blij dat er drivers zijn |
was voor hun eigen goed niet? anders waren ze nu helemaal niet bij de groteren ...
Ik moet toegeven dat ik ook nog nooit probs gehad heb met de drivers. Dat neemt niet weg dat drivers beter zouden kunnen zijn, indien je goeie intel hebt over het OS en over de hardware zelf ... een samenwerking zou dus ideaal zijn.
Toch nog ff meegeven dat 3dfx in der tijd is overgenomen door nvidia. Het is nl het linux team van 3dfx dat nu linux drivers maakt voor nvidia. Ik was vroeger trouwens héél blij met mijn voodoo2 kaartje onder linux. En dat waren open source drivers
grtz |
|
| Back to top |
|
|
|
Dutch
