Solved Problem with new Nvidia driver 367.35

  • Thread starter Deleted member 45312
  • Start date
D

Deleted member 45312

Guest
Hi,

I just upgraded x11/nvidia-driver to 367.35 and my screen is black !
I have to comment out the following line in my /etc/X11/xorg.conf to retrieve my display... but with screen tearing now.
Code:
Section "Screen"
  Identifier  "Screen0"
  Device  "Device0"
  Monitor  "Monitor0"
  DefaultDepth  24
  Option  "Stereo" "0"
# Option  "metamodes" "nvidia-auto-select +0+0 { ForceCompositionPipeline = On }"
  SubSection  "Display"
  Depth  24
  EndSubSection
EndSection

In addition, although I built this package without linux support, kernel modules linux.ko and linux_common.ko are automatically loaded at startup.

My system is FreeBSD 10.3-RELEASE-p7 amd64 .
 
Nice, it works now with my GT610.
 
Apparently not on my Zotac with a GT520. I get a black screen, (block) cursor top left hand of the screen and a non-moving mouse pointer. Blindly exiting X causes a freaky looking colored block screen. Haven't spent too much time on it yet though. I might try again tonight.

For posterity sake: FreeBSD 10.3-RELEASE-p7 NVidia driver 367.44.
 
It would be nice to push a port of the last working nvidia-driver 346.96. I also own an Asus GT520 but I am not using it currently with FreeBSD.
 
Apparently not on my Zotac with a GT520. I get a black screen, (block) cursor top left hand of the screen and a non-moving mouse pointer. Blindly exiting X causes a freaky looking colored block screen.
That's exactly what I get when there is no "Modes" line in my xorg.conf.
 
Apparently not on my Zotac with a GT520. I get a black screen, (block) cursor top left hand of the screen and a non-moving mouse pointer. Blindly exiting X causes a freaky looking colored block screen. Haven't spent too much time on it yet though. I might try again tonight.
Working now. I just had to replace nvidia_load with nvidia-modeset_load in /boot/loader.conf. My old xorg.conf needed some work too. I figured I'd do that properly too and removed any and all traces of xorg.conf.
Then created the following files:
/usr/local/etc/X11/xorg.conf.d/driver-nvidia.conf
Code:
Section "Device"
        Identifier  "Card0"
        Driver      "nvidia"
EndSection
I also use a couple of extra fonts:
/usr/local/etc/X11/xorg.conf.d/files-fonts.conf
Code:
Section "Files"
        FontPath     "/usr/local/share/fonts/bitstream-vera/"
        FontPath     "/usr/local/share/fonts/webfonts/"
        FontPath     "/usr/local/share/fonts/dejavu/"
        FontPath     "/usr/local/share/fonts/terminus-font/"
EndSection

It's working perfectly fine now. Switching back and forth between X and console works as usual. Ran startx several times in a row and it's still working as expected.
 
I'll see if it works for me though, just now had to rollback to the state before update. On my nVidia GeForce GT430 X log shows monitors aren't detected at all and that's the problem. I do have the driver conf file and I do have metamodes string in a conf file, but all to no avail.

EDIT: evidently, I've missed out what it says in the postinstall message:
Starting with version 358.09, some important functionality of the driver
has been broken out into a separate kernel module, nvidia-modeset.ko.
Users that experience hangs when starting X11 server, or observe

(II) NVIDIA(0): Validated MetaModes:
(II) NVIDIA(0): "NULL"

in /var/log/Xorg.0.log should replace ``nvidia'' with ``nvidia-modeset''
in their /boot/loader.conf or /etc/rc.conf configuration files, depending
on how they prefer to load NVidia driver kernel module.

That fixed it indeed.
 
Back
Top