Date: Sun, 12 Oct 2014 22:32:36 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 193770] CURRENT/UEFI: x11/nvidia-driver: loading module via loader.conf freezes system Message-ID: <bug-193770-13-k1Ws4EeEye@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-193770-13@https.bugs.freebsd.org/bugzilla/> References: <bug-193770-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193770 Dave <dcbdbis@comcast.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcbdbis@comcast.net --- Comment #3 from Dave <dcbdbis@comcast.net> --- I also have the issue, but it goes much deeper than just NVIdia. It affects any 3rd party module you may try to load from /boot/loader.conf. It appears that the loader is ignoring the configured module_path in the /boot/defaults/loader.conf file which includes /boot/modules as a legit search path for other modules.....Loader is ignoring this directive and is only looking at /boot/kernel for it's modules. Thus the loader dies and pukes out a CPU register dump on your screen. The temporary fix is to either load it in the scripts (as mentioned), or copy the module from /boot/modules to /boot/kernel It the module exists in /boot/kernel.....you can continue to load your modules in the loader.conf file normally. FYI, Sincerely and respectfully, Dave -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-193770-13-k1Ws4EeEye>