|Summary:||x11/nvidia-driver-340: panic with GeForce 320M|
|Product:||Ports & Packages||Reporter:||Tim Preston <freebsdbugs>|
|Component:||Individual Port(s)||Assignee:||Alexey Dokuchaev <danfe>|
|Severity:||Affects Only Me||CC:||iwtcex, rigoletto, w.schwarzenfeld|
Description Tim Preston 2018-11-08 11:18:09 UTC
Created attachment 199077 [details] Core dump summary I'm running 12.0-BETA3 but have experienced this issue with other versions of 11.2, stable/11, and 12-CURRENT. Loading the nvidia-driver-340 and running startx will crash the machine every time. This is a 2010 Mac Mini and uniquely the graphics card shares system memory. I believe the Device ID is 0x08a4, and is listed as supported here: https://www.nvidia.com/object/IO_32667.html I have tried loading the kernel extension via kldload, /etc/rc.conf, and /boot/loader.conf, and building with ports. Configuration details are: pciconf -lv | grep display -B 3 -A 1 vgapci0@pci0:5:0:0: class=0x030000 card=0x00c0106b chip=0x08a410de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'MCP89 [GeForce 320M]' class = display subclass = VGA /usr/local/etc/X11/xorg.conf.d/driver-nvidia.conf Section "Device" Identifier "Card0" Driver "nvidia" BusId "PCI:5:0:0" EndSection A core dump summary is attached. Thank you, Tim
Comment 1 Walter Schwarzenfeld 2019-08-11 14:00:34 UTC
Maintainer feedback, please!
Comment 2 Alexandre C. Guimarães 2019-10-30 21:41:06 UTC
IDK if this is the exactly same problem but upgrading to 410.104: >ln: /usr/local/lib/xorg/modules/extensions/.nvidia/libglx.so.1: > No such file or directory >pkg: POST-INSTALL script failed Then, as expected, the driver don't work. >12.1-STABLE f97711e483f(stable/12) Thank you.
Comment 3 Alex S 2019-10-30 22:49:43 UTC
(In reply to Alexandre C. Guimarães from comment #2) libglx.so was renamed to libglxserver_nvidia.so in 410.x, so your problem is related to bug 232645.
Comment 4 Alexey Dokuchaev 2019-10-31 08:53:58 UTC
(In reply to Alexandre C. Guimarães from comment #2) Yes, SUB_FILES were not adjusted in the update to 410.104. Please try with the latest update to 430.50 in ports r516138.