Rakor
The video works fine with the lower resolution-1024x768- and Nvidia selected but for some reason it wont accept the 1280x1024. Using the wizard its possible to select 1280x1024 and nv and the wizard successfully completes and starts the desktop. Additionally even with the NVidia driver selected on monitor wizard, the NVidia tool will not work.Furthermore kldstat (even with the NVidia driver selected on the Wizard) shows no Nvidia driver loaded. Running kldload nvidia loads the driver. However even with the driver loaded, an attempt to use the NVidia graphics widget yields the "You are not using the Nvidia driver--run nvidia-xconfig as root" message. SU'ing the nvidia-xconfig command from a terminal window yields again, command not found. So thats where I am. The wizard seems to not know which driver is loaded because it claims NVidia but there is no Nvidia module visible in kldstat. I am assuming that kldstat and kldload are similar to the modprobe series of commands in Linux? Anyway I did a kldload nvidia then kldstat and it appeared in the list. I rebooted and ran from boot the wizard. Same results, wizard says that we are using the nvidia driver as it did before , and it still wont accept the higher resolution. So back to the desktop, kldstat and no nvidia module loaded. So apparently when you use kldload to load the module, its only there until the next boot.
Couple of comments here from someone who has run Linux for years -- I currently have 2 multi monitor systems running linux, one with 4 monitors and 2 PCIE cards on an I7 platform, the other is a Core quad with 2 cards and 2 monitors. All of the graphics cards are NVidia. One extremely frustrating problem (and I do not know a way around this) is that whatever configuration tool that is used from the GUI in Linux is apparently NOT aware of what exactly exists in the xorg.conf file in /etc (in Linux). What you end up with as exampled here is the GUI tool in this case, the monitor wizard, reporting wrong information i.e. that you are using the NVidia driver when something else entirely may exist. Additionally in running the monitor wizard as many times as I have and watching the text on the screen as part of this process when X is not running, it seems that X is falling back on a basic X configuration created at install. There is no indication of that on the GUI tool. So what can happen is that you can play with the monitor wizard all day and you dont end up creating a usable Xconf file...or if you do it does not get used and the reason is not readily apparent. I understand the reasons for doing this i.e. someone who cant vi the xconf file, and make good entries by hand and only uses wizards can mess up X where it has no hope of starting. ....but it seems to me from years of messing with linux, that there needs to be , particularly since we seem to be moving more and more into a GUI environment, a way of creating a better graphic interface that actually can "read" what exists in xconf and report it accurately in the GUI rather than simply a widget that can only write to the file. Unfortunately I dont know how to accomplish this.
Enough of my opinions. What has to be done to force the kernel to load the NVidia driver on boot?
Well I ve rattled on quite a bit here LOL thanks again to all of you
Carr
NVidia driver installation on PCBSD 9 rc 3 beta
Hybrid Mode
