Nvidia driver question

I'm using the 61.77 Nvidia drivers with my old Geforce256 (32mb) 3D Prophet card. However, I'm going to buy a new Nvidia card in the $80 range, probably an FX5200 256 mb. Don't laugh, I'm just not an avid gamer.
My question is, can I just install the new card and the existing drivers will work, or do I need to reinstall the Nvidia drivers? What would be the proper way to install this card and uninstall the old (from a drivers perspective - I got no problems physically yanking the old and adding the new card, been there done that).
Thanks!

Quote
Originally posted by Rogue_Wulff
When I first built this system, I had a GeForce2 MX32MB, added a FX5200 by simply shutting down, swapping the card and rebooting. XP found the new hardware, and reinstalled the drivers, and asked for a reboot.
Since then, I swapped the FX5200 for a FX5700. Done it the same way, just shutdown, and swapped them out. This time, XP did not even ask for a reboot.
While uninstalling the old card/drivers is more commonly recommended, as Wonkanoby pointed out, the drivers are the same for all GeForce cards, regardless of age. Just need newer versions, for the newer cards.
I think I will try it - I'll just shut down and swap the card, then start up and see if XP can figure it out. If not, I can work from there.
Quote
Deleting the card from device manager *should* uninstall the drivers, but may not get every trace of the older versions that are hiding.
I guess I was just thinking of deleting it from device manager in ADDITION to uninstalling the drivers. So in other words, I would use Add/Remove to remove the nvidia 61.77 drivers, then delete the Device, then shut down swap cards, start up and reinstall the 61.77 drivers. But, I'll try the simple approach first.
Thanks for your help everyone.

Similar Messages

Possibly stupid question re: nvidia driver install

Hi there. I was wondering... Is it possible to install the nvidia driver without compiling the kernel? I don't want to repartition my drive to give Arch the space it would need to do that, and even if I had the space I'd rather not have to waste time compiling.
As a side curiousity, if I do indeed need to rebuild the kernel, can anyone explain why I need to? It seems to me that if whoever compiled it in the first place included the sources they used, and if they made a copy available, it would avoid a lot of hassle. Am I wrong?
Thanks in advance.

Pink Chick wrote:
OK - 1.) get source from kernel.org
OK - 2.) extract it in /usr/src
No - 3.) ln -s linux-2.6.4 linux (this step is debateable whither is necassary or not)
OK - 4.) run the NVidia installer (say yes compile me one when it says it can't find any on nvidia's site)
OK - 5.) update XF86Config-4
OK - 6.) add nvidia to the modules like of rc.conf
Just wanted to debate. If you fetched the kernel source, you should have a look inside its readme. There is a strong warning not to link your source to linux. Instead, give your nvidia installer the option where to find the source.
nvinstaller --kernel-source-path=/usr/src/linux-2.6.4/
Thanks, I wasn't aware of that. Will not do that any more
-wd

Windows 8 64-bit install on 970a-g46 Mainboard AHCI and NVIDIA DRIVER issues

My Box:
MSI 970A-G46
BIOS 1.9 (AUG 2012) (Tried 1.11 but the nightmare started then)
AMD FX-6100 (STOCK SPEED AND SETTINGS) WITH OEM HSF
16GB PATRIOT VIPER 3 (1866) RUNNING @ (1600)
USED an EVGA 9800GT 1ST AND UPGRADED TO NVIDIA REFERENCE CARD GTX 550 Ti (1GB) WITH SAME ISSUES
90gb MonsterDigital Daytona SATA III SSD DRIVE (OS and minimal programs)
Antec HE 550
I am at a point of pulling my hair out. I decided to upgrade my system to enhance Diablo III game play. I got a combo deal on the mainboard and cpu, and thought the speed of the game caching on a SSD would also help. The first attempt which took a little struggle was Vista 64-bit. Eventually, I was able to get the OS to work with me, and it was smooth. Since M$ decided to offer the Windows 8 Pro upgrade for only $39.99, I thought, what do I had to lose. Well….lots of time. Now, I am not a newbie, though SSD drives haven’t been more than an interesting thought. So yes, I read many guides on everything from Trim enabled Win 7 and 8, and many other do’s and don’ts. What is driving me to the Netherlands of hell, is the installation and how buggy it has been. It boils down to drivers for the IDE/SATA/AHCI CONTROLLER. First, even thought it “sees” the SSD on installation drive selection, after pulling the USB installation drive, the system forgets it, and there is a “problem with the boot sector”. If you load the driver from the AMD site, it lets the install occur “fine”, but there is an issue with that driver which causes an irq conflict which leads to D3 audio issues and freeze ups. I did finally get things in order (not sure which driver I choose for that), and things were smooth, except I tried to install the GTX 550 ti and that led to a corrupt file error, which the system runs a check disk and cycles the “preparing to repair” and “diagnosing PC” a few times and never allows me to enter SAFE MODE (shift+f8), to disable the NVIDIA driver that is buggy, and doesn’t allow for the NVIDIA Control Panel to install without losing video, and starts the repair cycles again… Leading to ANOTHER RE-INSTALL...
My question, for the Windows 8 Pro installation on the 970a-G46 mainboard and then after install is complete, which driver is the correct choice for the AHCI/SATA Controller? All I find is Win7 64-bit AHCI inf’s, and SB7XX 64-bit inf’s (no SB950 INF). The Driver disk which came with the mainboard is very dated pre Win 8 stuff, ASMEDIA X106 which are not recognized by the OS as written for Win 8. AMD’s latest drivers are the ones causing the IRQ type lags and corruption.
What version, build and type of Windows 8 installations have you used on this mainboard, and what drivers allowed you install it without the above conflicts? Your input may decrease my insanity… So, thank you in advance…

Quote from: m0r9h3u5 on 28-January-13, 12:11:16
I understand what you are telling me, only the generic drivers deliver subpar results. What is the point of running those drivers instead of windows 8 certified drivers written for said devices. My last install is functioning better, but still windows update fails every attempt, the apps i install (ie. weather bug) on the start screen wont load... to me windows 8 is a big fail....but that is just my view...
OK...I also own the 970a G46, and my upgrade experience from Win7 x64 AHCI to Win8 x64 AHCI was flawless the first time. No problems at all. You are running an AMD chipset board with a nVidia gpu, which means that your chipset drivers are not automatically updated with every gpu driver update you do--this would happen automatically if you owned an AMD gpu because AMD includes them in its gpu driver install packages. But--all you have to do to get the proper drivers for your motherboard is go here and download them. You only need the *chipset drivers* from this page--you do not need the RAID drivers, of course. That's it. It's no big deal, and back in the days when nVidia was making motherboard chipsets you had to separately download both the motherboard chipset drivers from nVidia and the AMD gpu drivers from AMD if you did not also own a nVidia gpu.
From your description of your problems it sounds like your installation of Win8 is hosed and you need to format C:\ and clean install from scratch, anyway, so...
A note about AHCI--the *ideal* way to install the AHCI drivers is prior to installing your OS for the first time, you enter the UEFI and set "AHCI" in the appropriate place, instead of IDE, and *then* you reboot from DVD and install your OS which will automatically install the correct AHCI driver from Windows. After the driver installation is complete you should then install the updated 970a drivers from AMD as linked above.
However, it is actually very easy to activate and install AHCI *after* you have installed Windows in normal IDE mode:
To enable AHCI in existing Windows 8 IDE Installation's
Caution: Do NOT enable AHCI in UEFI prior to making the following changes in your Registry! If you had AHCI enabled alreadyin UEFI, disable it first and restart your computer!
Use WinKey + R and type Regedit in the command line and hit the Enter key, this will open the Registration Editor.
Go to:
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/services/iaStorV
right click on Start, select Modify and set Data Value to 0
Close Registration Editor and restart computer.
While booting, open the UEFI Page and set the SATA Mode to AHCI from IDE
Save UEFI settings and restart.
Windows will now install the AHCI drivers automatically and they should work without issues.
In order to avoid installation problems just like you have been experiencing, here is what I would do in your shoes:
1) Set UEFI for normal IDE drive mode
2) Reboot into IDE mode and install your OS
3) After you have finished with the installation, you should be having no troubles in IDE mode. Then go to the instructions above on how to properly enable AHCI *after* you have installed Windows 8 in normal IDE mode.
4) After everything is coming up roses in AHCI mode and you are having no problems, then install the AMD chipset drivers as linked above and you are golden.
Those 4 steps worked perfectly for me the first time (the first time I got them right, that is...).
There's nothing wrong with Win8--this is strictly operator error caused by insufficient research into what AHCI is and how to properly enable it. The Internet has some bad info on Win8 registry settings for AHCI because of the developer preview and the consumer preview versions of Win8 that Microsoft released to the public prior to the final shipping build--many "instructions" for Win8 are therefore not valid for the shipping version of Win8. At first I made some of the same goofs that you did, but now you get to benefit from my hard-won experience... Good luck! Should work like a charm. And, registry AHCI is done differently in Win8 than it is done in Win7 or Vista. Also, the registry settings relative to AHCI in Windows 8 for AMD are different from the registry values that must be changed for an Intel controller.
Parenthetically, My FX-6300 (Vishera) will be here in a couple of days! Yeah!

[SOLVED]Make Pacman think that I have libgl (NVIDIA driver)

Hi,
I've installed my Nvidia driver manualy because my card (NVS 310) do not work with the packages provides by pacman (even in AUR).
Now I have a problem because pacman think I do not have
libgl
and do not allows me to install any graphical tools like libreoffice even if I ignore libgl:
pacman -S libreoffice-fresh --ignore libgl
resolving dependencies...
:: There are 4 providers available for libgl:
:: Repository extra
1) mesa-libgl 2) nvidia-304xx-libgl 3) nvidia-340xx-libgl 4) nvidia-libgl
Enter a number (default=1):
I cannot install one of these package because then conflict with my manual install:
pacman -S libgl
:: There are 4 providers available for libgl:
:: Repository extra
1) mesa-libgl 2) nvidia-304xx-libgl 3) nvidia-340xx-libgl 4) nvidia-libgl
Enter a number (default=1): 4
resolving dependencies...
looking for conflicting packages...
warning: dependency cycle detected:
warning: nvidia-utils will be installed before its nvidia-libgl dependency
Packages (2) nvidia-utils-352.09-1 nvidia-libgl-352.09-1
Total Installed Size: 125.31 MiB
:: Proceed with installation? [Y/n]
(2/2) checking keys in keyring [######################################] 100%
(2/2) checking package integrity [######################################] 100%
(2/2) loading package files [######################################] 100%
(2/2) checking for file conflicts [######################################] 100%
error: failed to commit transaction (conflicting files)
nvidia-utils: /usr/bin/nvidia-bug-report.sh exists in filesystem
nvidia-utils: /usr/bin/nvidia-cuda-mps-control exists in filesystem
Errors occurred, no packages were upgraded.
So my question is: Is there a way to make pacman understand that I have installed libgl manualy so it do not ask me to install it?
Thanks
The possible workaround is to remove my driver manually install any libgl than re-install manualy the driver and ignore libgl in the pacman configuration. But this is REALLY ugly...
Last edited by mickours (2015-06-13 19:09:41)

Thanks for your reply, that was fast!
Make my own package is definitly the right way to do this and I will when I have some time.
For now I tried the workaround I mentioned before:
mickours wrote:The possible workaround is to remove my driver manually install any libgl than re-install manualy the driver and ignore libgl in the pacman configuration. But this is REALLY ugly...
And it works!
Thanks again

W510 problems with Nvidia driver recovery under Windows 7 (64 bit)?

Lenovo W510, Nvidia Qudardo FX 880M video, FHD:
What I'm seeing on occasion is a Windows 7 (64-bit) recovery, screen blanks out, goes 2-3 seconds, then recovers, things go back to normal, but a message displays saying that an error was detected in the video driver, and it has recovered. The new Firefox (4.0.1) seems to be one of the things that may be a contribution, hard to tell. Per System Update at least, I'm current on the Lenovo downloads. SIW shows the driver level as 8.17.12.5738 (2010-06-27). Nvidia web-site shows their current driver level on the wen-site as 270.61 (2011-04-18), which is a considerably newer date at least. So two questions:
Has anyone else seen Driver/Recovery issues on Win 7 (64)
Has anyone directly run the Nvidia video drivers and had them run OK?
Seems like it would be nice for Lenovo to update their drivers, if indeed this is a driver issue, they appear back-level.

I used to have this problem with my W510 running Windows 7 Enterprise 64-bit, especially Firefox 4 crashing the Nvidia display driver almost constantly. I googled and found that this is a known problem between older Nvidia driver and Firefox 4. Later on I downloaded the latest version of Nvidia driver from Lenovo website (it was not posted on the System Update server yet but was available on the regular download site). I clean-installed it (i.e., removing all files and settings created by the old driver) and I haven't experienced the problem since then.
Twitter @thitiv | Work | ThinkPad W520 (4270-CTO) Core i7-2960XM 2.7/3.7 GHz | 16GB Kingston HyperX PnP DDR3-1866
2 x 256GB Crucial M4 & C300 SSDs | Intel Centrino Ultimate-N 6300 | Ericsson F5521gw WWAN | Ultrabay Blu-ray Burner
NVIDIA Quadro 2000M | 15.6" FHD 1920x1080 | ThinkPad Battery 55++ (9-cell) & Battery 27++ (9-cell slice)

NVIDIA driver 6md647ww does not install on W701 with Windows 7 64 Bit

Hello,
I have downloaded the nvidia driver 6md647ww (311.00), 64 bit version, and can't install on a Windows 7 64-bit system. It says "no compatible device found". The strange thing is, although the decompression routine and the window asking to start installation both say that they are the 64 bit version, the text besides the check mark "install the driver now" says it will install the 32 bit version (after decompressing the window says 64 bit in the upper part, but 32 bit in the lower part).
So I guess there is an error in the installation routine which erronously wants to install the 32 bit version although it is DEFINITELY the 64 bit version I have downloaded. Also, I downloaded for testing the 32 bit version of the driver (5md647ww), and if I try to install that, I get exactly the same error as with the 64 bit version.
Could someone please look into the 6md647ww, there is something wrong with it. Also, I can install 6md640ww and 6md643ww without any problems and switch between these two versions without any error - the 6md647ww issue is definitely NOT a problem of my OS configuration.
I have a sporadic heavy crash issue with 6md643ww and need to upgrade badly.
Please help. Best regards, Michael
System: Lenovo W701, 16 GB Ram, Windows 7 64 Bit, NVIDIA Quadro FX 3800M

In the meanwhile Rev 04 of the driver was published. This version is binary different to Rev 03 and - surprise - it now says correctly after unpacking it will install the 64-bit version. But after that same problem as before, "no compatible device found".
I did some searching into the files of 6md647ww. I guess the file Display.Driver\NVLT.inf contains a list of compatible devices - in this file the sections labelled NVIDIA_SetA_Devices.NTamd64.* list a lot of device-ids, for example PCI\VEN_10DE&DEV_0A3C&SUBSYS_214517AA and many more. The device id of the graphics card for a system can be found in the hardware/device manager of windows, I obtained that for my card and this id doesn't show anywhere in NVLT.inf. So if my guess is correct, it is no wonder the installer says "no compatible device" since the device id of my card is not listed in NVLT.inf.
Please note again that all previous versions of lenovo drivers for my NVIDIA Quadro FX 3800M did and do install without absolutely any problem!
This is strange, readme of the current driver version definitely says NVIDIA Quadro FX 3800M is supported by this driver, but the driver doesn't seem to contain the device id for it. Looks almost like the wrong driver was used / bundled into 6md647ww.
And again the question to the board / administrators if lenovo technical support is reading here and is there another contact at lenovo where I could direct my problem to? I am still having the sporadic heavy crash issue which is very dangerous since it can happen any time if displaying whatever graphics in whatever software and which therefore has a high risk of data loss. Also, installing the plain NVIDIA driver directly in the current version still has the problem of flickering and color errors, so this isn't a solution either.
Best regards, Michael

How to get older nvidia driver

I just installed archlinux again and the nvidia driver.
Now when I run 3d games I get a stutter every 13-15 seconds, as if the graphics freeze for 1 second.
I remember having this problem with the nvidia version 169, and then I downgraded the driver which fixed the problem.
But this was in Gentoo.
How do I get an older driver in Archlinux?
I think I need the 100. something driver.

I haven't tried using ABS yet. The question is for me if it will be easier for me to install Gentoo again where I can just choose the driver version freely, or llearn to use ABS.
I was just hoping that I could use Arch since it is faster to install..
Last edited by Kabi (2008-07-14 09:08:14)

Installed Nvidia Driver Problems?

I recently installed Nvidia Ge-Force 5200FX Driver onto my computer and it changes my video bit from 16-Bit to 4-Bit and i cant change back anyone know how i can change it back without uninstalling the driver.

There is one thing you do not seem to have understood so far: This forum is not a general hardware forum but offers help and advice for MSI Retail products only. You were using an MSI MS-6590 KT6 Delta mainboard in your other thread. That is the only reason why we replied to your questions about an unknown video card model in the first place (even though the lack of a video driver for an unknow card has not much to do with your mainboard.
Now you are asking us about some NVIDIA driver issue regarding the "same type of [non-MSI] graphics card" but in a "different computer". You provided no useful information about your system configuration whatsoever (no information about your operating system, no information about the exact driver version, no information about why you installed an NVIDIA driver even though the unknow video card seems to be an old ATI model, etc.) I see nothing that relates to any MSI Retail product in the context of your driver question. I am locking this topic.
If you find one reason why I should re-open your topic and not advise you to look for help in a general hardware forum (there are tons of those out there on the net) write me a PM and tell me what this has to do with MSI Retail products. I will than gladly unlock this thread. Until then:
__ TOPIC LOCKED __

Nvidia Driver and system "hang" issue

Hi all,
This is my first post on these forums but im not new to Mac or windows. Here's my issue. I just installed a copy of Windows 7 Ultimate RTM on my Macbook. Its the first unibody Macbook 2.4ghz w/ 4gigs of ram. Nvidia 9400M graphics.
2 Things happen,one is that a few times a day ill get a "Nvidia Windows Kernel mode driver, version 186.81 failed" error. The symtoms of which are a black screen for a few seconds and then the driver restarts and all is well.
I know 186.81 is the latest 9400M driver. So im not sure why this happens but maybe it relates to my other issue.
My second issue is that the system will, as best as i can describe it, "hang" for a second or two. When i say hang i do not mean freeze to the point of needing to restart, its more that the "hang" happens and a few seconds later its as if nothing happened (this issue is very fequent).
Anyone else ever see or hear anything like this? Please let me know if there is a better place to post this question as well.
Thanks!
P.S. Posted this somewhere else and got 1 reply so far, pasted below:
Okay, how about uninstall or roll back the driver?
use Driver Sweeper 2
just let Windows 7 install its own driver
more like the hang is hard drive has spun down
I would recommend creating your own thread and question instead.
by "the hatter"

Hello guys and thanks for your answers.
I thought that my problem was linked to UEFI, so I reinstalled the os with BIOS and MBR. Unfortunately I had the same problem, with one difference: the auto/default resolution of GRUB and FrameBuffer was 800x600 instead of 1920x1080 for UEFI.
About the nouveau driver, I need 3D acceleration to play games so I need the proprietary driver.
So I decided to test the X server to see if something got wrong.
I uninstalled the nvidia driver and reboot to have my framebuffer back.
Then I edit the ~/.xinitrc file :
xterm & sleep 10
I reinstalled the nvidia driver and reboot : GRUB, then framebuffer for 1 second, then a black screen.
I tried to log in: login + [Enter] + password + [Enter]
I waited 2s then I entered the "startx" command.
And the xterm window appeared. And the best is after the 10s the X server shuts down and the framebuffer was back !!! Unbelievable !!!
So I continued the installation : Gnome + Gdm.
After the reboot : Grub, then framebuffer for 1 second, then a black screen, then Gdm login screen !!!
So it seems to be a problem with nvidia driver and the framebuffer.
After the Gnome + Gdm installation I managed to display the framebuffer in tty2. But I don't know if tty2 was working before (when tty1 only display black screen).
My conclusion and installation tip is to not reboot after the nvidia driver installation and to install a desktop environment + a display manager and to pray to not have problem.

Proprietary nVidia driver pegs fan at 65%

Window-shot:
http://i.imgur.com/feNCk2v.png
$ lspci | grep "VGA"
02:00.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 620] (rev a1)
$ pacman -Qi nvidia
Name : nvidia
Version : 325.15-5
Description : NVIDIA drivers for linux
Architecture : i686
URL : http://www.nvidia.com/
Licenses : custom
Groups : None
Provides : None
Depends On : linux>=3.10 linux<3.11 nvidia-libgl nvidia-utils=325.15
Optional Deps : None
Required By : None
Optional For : None
Conflicts With : nvidia-96xx nvidia-173xx
Replaces : None
Installed Size : 3731.00 KiB
Packager : Evangelos Foutras <[email protected]>
Build Date : Fri 30 Aug 2013 06:11:40 PM NDT
Install Date : Thu 05 Sep 2013 11:00:43 PM NDT
Install Reason : Explicitly installed
Install Script : Yes
Validated By : Signature
$ cat /etc/X11/xorg.conf
Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen" 0 0
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection
Section "Screen"
Identifier "Default Screen"
Device "Device0"
Option "Coolbits" "4"
Option "DPMS" "false"
SubSection "Display"
Modes "nvidia-auto-select"
EndSubSection
EndSection
Everything works well, even native Steam and games. However my GPU fan is constantly pegged at 65%. I'd like this to be lower. The speed is "variable" and I believe that is what I want - automatically adjust to temperature. However, I'd like the fan speed to be lower and automatically adjust to temperature. I'm new to the proprietary nVidia driver so please bear with me and hopefully it is just something simple I've missed.

Awesome that's got it working. Now for another question: How do I get it the module to load automatically like the stock kernel does?
The normal "modprobe nvidia" reports module not found so I'm having to do "insmod /usr/lib/modules/extramodules-4.0-ARCH/nvidia.ko.gz" (at first that gave a bunch of undefined symbol errors but that was resolved by manually doing a "modprobe drm")
So how does modprobe whatever autoloads the modules at boot know where to look? I already symlinked /usr/lib/modules/extramodules-4.0-ARCH to /usr/lib/modules/4.0.0-rc1-ARCH/extramodules like the stock kernel does but I guess that's not enough.

No additional properties & driver question

Hello
Just got done building a new computer and put the MSI NX6800GT TD256 card in and had some driver questions.
I used the drivers that came on the CD for now and everything is working fine, but when I go into the advanced settings and click on the 6800 tab theres no where too adjust direct3d and opengl settings. Supposedly theres and additonal properties tab.......
And are you guys using the drivers from MSI or are you using the Forceware drivers from Nvidia....
Thanks for the help!!

Try using the Catalyst 4.12 final drivers! They really boosted my scores! Get the driver here:
http://www2.ati.com/drivers/wxp-w2k-catalyst-8-082-041130a-019577c.exe
Goodluck

Nvidia driver fails to load with NV GT-220 graphics card

I am using 2.6.33-ARCH of May 13th, I installed a Nvidia GT-220 graphics card over my onboard 6100,
it was using nouveau, i tried to upgrade to using the nvidia driver but find now that i am not able to
modprobe -i nvidia i get Fatal: Error inserting nvidia (/lib/modules/2.6.33-ARCH/kernel/drivers/video/nvideo.ko
modinfo nvidia shows it in the above location.
startx gives me: cannot execute binary file.
even after !nouveau in MODULES /etc/rc.conf it shows up with lsmod |grep nouveau

I installed the nvidia drivers with: sudo pacman -S nvidia nvidia-utils
I seem to of gotten more than one problem with my attemps at resolving this. The issue with nvidia module has been resolved by reinstalling the previous kernel26 2.6.31.3-1 it apparently doesnt have nouveau. and lsmod |grep nouveau gives null reply so its gone...
I used sudo nvidia-xconfig and it completed as expected and wrote a new xorg.conf but i am still getting
cannot execute binary file when i try using startx.
startx gives me: cannot execute binary file. additionally using: sudo X -configure gives the same error.
the versions of nvidia are under question: I have nvidia 195.36.15-2 and nvidia-utils 195.36.15-1
I am not sure if different minors are a problem, just noting the difference.

Nvidia driver having a strange behaviour...

Hi. Yet, I just bought a "new" computer, a dual P3 1400 mhz, 2 gb with, as video card, a nVidia 5200 FX. Now, I've been able to configure everything... but the video card. Yet, what works:
- OpenGL works, according to 'nvidia-settings"
- I get the nVidia logo and I can see something
And what doesn't:
- From the moment I run "startx", I can't switch to the "ctrl + alt + x' consoles
- Although I did configure modes (1024x768, 24 bit), and answered "no" at the question "do you want a virtual screen larger than the physical", the actual resolution is not "1024x768" and I do have a virtual screen larger than the physical.
- According to "nvidia-settings", the card is working at 2x, while it is supposed to work at 4x. At first, I checked in my BIOS and, indeed, it was downgraded at 2x, which I fixed. Then, seeing it wouldn't get to 4x, I reinstalled "nvidia", which didn't solve the problem. Do I need to compile a kernel? Are there configuration files for that?
- Finally, when I close my session of Enlightenment, and thus, get back to the standard consoles, the text that used to be perfectly readable, becomes perfectly unreadable (big pixels).
I did search much on Google for answers but obviously, nothing would really solve my problems. By the way, here is my "xorg.conf" file:
Section "Module"
Load "dbe" # Double buffer extension
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "freetype"
Load "glx"
EndSection
Section "Files"
RgbPath "/usr/lib/X11/rgb"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/75dpi"
FontPath "/usr/share/fonts/100dpi"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/Type1"
EndSection
Section "ServerFlags"
EndSection
Section "InputDevice"
Identifier "Keyboard1"
Driver "kbd"
Option "AutoRepeat" "500 30"
Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
Option "XkbLayout" "ca_enhanced"
EndSection
Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "IMPS/2" # PS/2 Mouse
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
EndSection
Section "Monitor"
Identifier "Monitor0"
HorizSync 31.5, 35.15, 35.5
VertRefresh 50-90
EndSection
Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"
Driver "vga"
EndSection
Section "Device"
Identifier "Card0"
Driver "nvidia"
# VideoRam 131072
# Insert Clocks lines here if appropriate
EndSection
Section "Screen"
Identifier "Screen 1"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
Subsection "Display"
Depth 8
Modes "1280x1024" "1024x768" "800x600" "640x480"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "800x600" "1024x768"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "800x600" "1024x768"
ViewPort 0 0
EndSubsection
EndSection
Section "ServerLayout"
Identifier "Simple Layout"
Screen "Screen 1"
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection

Ok, so in case someone gets stuck in the same problem, here's what I have done (still a detail to fix, looking for it).
About the problem with the extended-3 filesystem, I still have no idea why my computer wouldn't work with it, but, at least, reiserfs works perfectly (phew!).
Now, about the problem with the nvidia driver, what must be done is to, first install xorg (pacman -S xorg), remove only libgl-dri (not mesa)(pacman -Rd libgl-dri) and then install nvidia (pacman -S nvidia)(for newer cards). I'm saying that because many things have been said in different posts, but none really worked well for me.
Finally, and mainly, for the console problem, there is no clean solution: I've been struggling to get that to work for a few hours. Globally, the idea is to compile a kernel with "vesafb-tng", as driver, which fixes the problem. Now, this driver is included in :"archck". However, "grub", on my computer, wouldn't boot with a "initramfs" (still no idea why, but I'm sure I had compiled support for it, written the correct path, etc). So the objective is to apply to a standard kernel the patch applied on "archck" kernel.
Finally, right now, my video card, which is supported to be recognized as "AGP 4X", is recognized as "PCI", which is even worse than the "AGP 2X" I had before. So I'll start searching for that, but if someone could give me some pointers about how to fix that, I would really appreciate.

[SOLVED] nvidia driver causes blank screen soon after boot

Hi,
I have a NVIDIA 560 and was originally using the nouveau driver, but that gave slow performance when doing anything (eg. resizing windows), so I installed the nvidia driver instead by following the wiki section:
https://wiki.archlinux.org/index.php/NV … au_drivers
by essentially just following the scripts given there. After switching to nvidia, the screen goes blank soon after boot. I get back into the system by using nomodeset in menu.cfg.
My question is how do I even begin to find the problem, eg. what log file(s) should I look in and post?
Thanks
Last edited by mark1977 (2012-08-19 17:38:42)

Yes it's the 560 Ti. Thanks I just installed straight from the repos. I've also installed cuda-sdk and cuda-toolkit. I've compiled the libraries inside /opt/cuda-sdk/CUDALibraries fine.
No I go to compile the sdk examples by running make in /opt/cuda-sdk/C and get the following error:
# make
make[1]: Entering directory `/opt/cuda-sdk/C/common'
make[1]: Leaving directory `/opt/cuda-sdk/C/common'
make[1]: Entering directory `/opt/cuda-sdk/C/common'
make[1]: Leaving directory `/opt/cuda-sdk/C/common'
make[1]: Entering directory `/opt/cuda-sdk/C/common'
make[1]: Leaving directory `/opt/cuda-sdk/C/common'
make[1]: Entering directory `/opt/cuda-sdk/shared'
make[1]: Leaving directory `/opt/cuda-sdk/shared'
make[1]: Entering directory `/opt/cuda-sdk/C/src/newdelete'
make[1]: Leaving directory `/opt/cuda-sdk/C/src/newdelete'
make[1]: Entering directory `/opt/cuda-sdk/C/src/simpleTextureDrv'
/usr/bin/ld: cannot find -lcuda
collect2: error: ld returned 1 exit status
make[1]: *** [../../bin/linux/release/simpleTextureDrv] Error 1
make[1]: Leaving directory `/opt/cuda-sdk/C/src/simpleTextureDrv'
make: *** [src/simpleTextureDrv/Makefile.ph_build] Error 2
The Makefile itself essentially seems to just include the file /opt/cuda-sdk/C/common/common.mk, which is:
# Copyright 1993-2011 NVIDIA Corporation. All rights reserved.
# NVIDIA Corporation and its licensors retain all intellectual property and
# proprietary rights in and to this software and related documentation.
# Any use, reproduction, disclosure, or distribution of this software
# and related documentation without an express license agreement from
# NVIDIA Corporation is strictly prohibited.
# Please refer to the applicable NVIDIA end user license agreement (EULA)
# associated with this source code for terms and conditions that govern
# your use of this NVIDIA software.
# Common build script for CUDA source projects for Linux and Mac platforms
.SUFFIXES : .cu .cu_dbg.o .c_dbg.o .cpp_dbg.o .cu_rel.o .c_rel.o .cpp_rel.o .cubin .ptx
# Add new SM Versions here as devices with new Compute Capability are released
SM_VERSIONS := 10 11 12 13 20 21 30
CUDA_INSTALL_PATH ?= /opt/cuda-toolkit
ifdef cuda-install
CUDA_INSTALL_PATH := $(cuda-install)
endif
# detect OS
OSUPPER = $(shell uname -s 2>/dev/null | tr [:lower:] [:upper:])
OSLOWER = $(shell uname -s 2>/dev/null | tr [:upper:] [:lower:])
# 'linux' is output for Linux system, 'darwin' for OS X
DARWIN = $(strip $(findstring DARWIN, $(OSUPPER)))
ifneq ($(DARWIN),)
SNOWLEOPARD = $(strip $(findstring 10.6, $(shell egrep "<string>10\.6" /System/Library/CoreServices/SystemVersion.plist)))
LION = $(strip $(findstring 10.7, $(shell egrep "<string>10\.7" /System/Library/CoreServices/SystemVersion.plist)))
endif
# detect 32-bit or 64-bit platform
HP_64 = $(shell uname -m | grep 64)
OSARCH= $(shell uname -m)
# Basic directory setup for SDK
# (override directories only if they are not already defined)
SRCDIR ?=
ROOTDIR ?= ..
ROOTBINDIR ?= $(ROOTDIR)/../bin
BINDIR ?= $(ROOTBINDIR)/$(OSLOWER)
ROOTOBJDIR ?= obj
LIBDIR := $(ROOTDIR)/../lib
COMMONDIR := $(ROOTDIR)/../common
SHAREDDIR := $(ROOTDIR)/../../shared/
# Compilers
NVCC := $(CUDA_INSTALL_PATH)/bin/nvcc
CXX := g++ -fPIC
CC := gcc -fPIC
LINK := g++ -fPIC
# Includes
INCLUDES += -I. -I$(CUDA_INSTALL_PATH)/include -I$(COMMONDIR)/inc -I$(SHAREDDIR)/inc
# Warning flags
CXXWARN_FLAGS := \
-W -Wall \
-Wimplicit \
-Wswitch \
-Wformat \
-Wchar-subscripts \
-Wparentheses \
-Wmultichar \
-Wtrigraphs \
-Wpointer-arith \
-Wcast-align \
-Wreturn-type \
-Wno-unused-function \
$(SPACE)
CWARN_FLAGS := $(CXXWARN_FLAGS) \
-Wstrict-prototypes \
-Wmissing-prototypes \
-Wmissing-declarations \
-Wnested-externs \
-Wmain \
# architecture flag for nvcc and gcc compilers build
CUBIN_ARCH_FLAG :=
CXX_ARCH_FLAGS :=
NVCCFLAGS :=
LIB_ARCH := $(OSARCH)
# Determining the necessary Cross-Compilation Flags
# 32-bit OS, but we target 64-bit cross compilation
ifeq ($(x86_64),1)
NVCCFLAGS += -m64
LIB_ARCH = x86_64
ifneq ($(DARWIN),)
CXX_ARCH_FLAGS += -arch x86_64
else
CXX_ARCH_FLAGS += -m64
endif
else
# 64-bit OS, and we target 32-bit cross compilation
ifeq ($(i386),1)
NVCCFLAGS += -m32
LIB_ARCH = i386
ifneq ($(DARWIN),)
CXX_ARCH_FLAGS += -arch i386
else
CXX_ARCH_FLAGS += -m32
endif
else
ifeq "$(strip $(HP_64))" ""
LIB_ARCH = i386
NVCCFLAGS += -m32
ifneq ($(DARWIN),)
CXX_ARCH_FLAGS += -arch i386
else
CXX_ARCH_FLAGS += -m32
endif
else
LIB_ARCH = x86_64
NVCCFLAGS += -m64
ifneq ($(DARWIN),)
CXX_ARCH_FLAGS += -arch x86_64
else
CXX_ARCH_FLAGS += -m64
endif
endif
endif
endif
# Compiler-specific flags (by default, we always use sm_10, sm_20, and sm_30), unless we use the SMVERSION template
GENCODE_SM10 := -gencode=arch=compute_10,code=\"sm_10,compute_10\"
GENCODE_SM20 := -gencode=arch=compute_20,code=\"sm_20,compute_20\"
GENCODE_SM30 := -gencode=arch=compute_30,code=\"sm_30,compute_30\"
CXXFLAGS += $(CXXWARN_FLAGS) $(CXX_ARCH_FLAGS)
CFLAGS += $(CWARN_FLAGS) $(CXX_ARCH_FLAGS)
LINKFLAGS += -L/usr/lib
LINK += $(LINKFLAGS) $(CXX_ARCH_FLAGS)
# This option for Mac allows CUDA applications to work without requiring to set DYLD_LIBRARY_PATH
ifneq ($(DARWIN),)
LINK += -Xlinker -rpath $(CUDA_INSTALL_PATH)/lib
endif
# Common flags
COMMONFLAGS += $(INCLUDES) -DUNIX
# If we are enabling GPU based debugging, then we want to use -G, warning that this
# May have a significant impact on GPU device code, since optimizations are turned off
ifeq ($(gpudbg),1)
NVCCFLAGS += -G
dbg = $(gpudbg)
endif
# Debug/release configuration
ifeq ($(dbg),1)
COMMONFLAGS += -g
NVCCFLAGS += -D_DEBUG
CXXFLAGS += -D_DEBUG
CFLAGS += -D_DEBUG
BINSUBDIR := debug
LIBSUFFIX := D
else
COMMONFLAGS += -O2
BINSUBDIR := release
LIBSUFFIX :=
NVCCFLAGS += --compiler-options -fno-strict-aliasing
CXXFLAGS += -fno-strict-aliasing
CFLAGS += -fno-strict-aliasing
endif
# architecture flag for cubin build
CUBIN_ARCH_FLAG :=
# OpenGL is used or not (if it is used, then it is necessary to include GLEW)
ifeq ($(USEGLLIB),1)
ifneq ($(DARWIN),)
OPENGLLIB := -L/System/Library/Frameworks/OpenGL.framework/Libraries
OPENGLLIB += -lGL -lGLU $(COMMONDIR)/lib/$(OSLOWER)/libGLEW.a
else
# this case for linux platforms
OPENGLLIB := -lGL -lGLU -lX11 -lXi -lXmu
# check if x86_64 flag has been set, otherwise, check HP_64 is i386/x86_64
ifeq ($(x86_64),1)
OPENGLLIB += -lGLEW_x86_64 -L/usr/X11R6/lib64
else
ifeq ($(i386),)
ifeq "$(strip $(HP_64))" ""
OPENGLLIB += -lGLEW -L/usr/X11R6/lib
else
OPENGLLIB += -lGLEW_x86_64 -L/usr/X11R6/lib64
endif
endif
endif
# check if i386 flag has been set, otehrwise check HP_64 is i386/x86_64
ifeq ($(i386),1)
OPENGLLIB += -lGLEW -L/usr/X11R6/lib
else
ifeq ($(x86_64),)
ifeq "$(strip $(HP_64))" ""
OPENGLLIB += -lGLEW -L/usr/X11R6/lib
else
OPENGLLIB += -lGLEW_x86_64 -L/usr/X11R6/lib64
endif
endif
endif
endif
endif
ifeq ($(USEGLUT),1)
ifneq ($(DARWIN),)
OPENGLLIB += -framework GLUT
else
ifeq ($(x86_64),1)
OPENGLLIB += -lglut -L/usr/lib64
endif
ifeq ($(i386),1)
OPENGLLIB += -lglut -L/usr/lib
endif
ifeq ($(x86_64),)
ifeq ($(i386),)
OPENGLLIB += -lglut
endif
endif
endif
endif
ifeq ($(USEPARAMGL),1)
PARAMGLLIB := -lparamgl_$(LIB_ARCH)$(LIBSUFFIX)
endif
ifeq ($(USERENDERCHECKGL),1)
RENDERCHECKGLLIB := -lrendercheckgl_$(LIB_ARCH)$(LIBSUFFIX)
endif
ifeq ($(USENVCUVID), 1)
ifneq ($(DARWIN),)
NVCUVIDLIB := -L../../common/lib/darwin -lnvcuvid
endif
endif
# Libs
ifneq ($(DARWIN),)
LIB := -L$(CUDA_INSTALL_PATH)/lib -L$(LIBDIR) -L$(COMMONDIR)/lib/$(OSLOWER) -L$(SHAREDDIR)/lib $(NVCUVIDLIB)
else
ifeq "$(strip $(HP_64))" ""
ifeq ($(x86_64),1)
LIB := -L$(CUDA_INSTALL_PATH)/lib64 -L$(LIBDIR) -L$(COMMONDIR)/lib/$(OSLOWER) -L$(SHAREDDIR)/lib
else
LIB := -L$(CUDA_INSTALL_PATH)/lib -L$(LIBDIR) -L$(COMMONDIR)/lib/$(OSLOWER) -L$(SHAREDDIR)/lib
endif
else
ifeq ($(i386),1)
LIB := -L$(CUDA_INSTALL_PATH)/lib -L$(LIBDIR) -L$(COMMONDIR)/lib/$(OSLOWER) -L$(SHAREDDIR)/lib
else
LIB := -L$(CUDA_INSTALL_PATH)/lib64 -L$(LIBDIR) -L$(COMMONDIR)/lib/$(OSLOWER) -L$(SHAREDDIR)/lib
endif
endif
endif
# If dynamically linking to CUDA and CUDART, we exclude the libraries from the LIB
ifeq ($(USECUDADYNLIB),1)
LIB += ${OPENGLLIB} $(PARAMGLLIB) $(RENDERCHECKGLLIB) ${LIB} -ldl -rdynamic
else
# static linking, we will statically link against CUDA and CUDART
ifeq ($(USEDRVAPI),1)
LIB += -L/usr/lib -lcuda ${OPENGLLIB} $(PARAMGLLIB) $(RENDERCHECKGLLIB) ${LIB}
else
ifeq ($(emu),1)
LIB += -lcudartemu
else
LIB += -lcudart
endif
LIB += ${OPENGLLIB} $(PARAMGLLIB) $(RENDERCHECKGLLIB) ${LIB}
endif
endif
ifeq ($(USECUFFT),1)
ifeq ($(emu),1)
LIB += -lcufftemu
else
LIB += -lcufft
endif
endif
ifeq ($(USECUBLAS),1)
ifeq ($(emu),1)
LIB += -lcublasemu
else
LIB += -lcublas
endif
endif
ifeq ($(USECURAND),1)
LIB += -lcurand
endif
ifeq ($(USECUSPARSE),1)
LIB += -lcusparse
endif
# Lib/exe configuration
# Lib/exe configuration
# Lib/exe configuration
ifneq ($(STATIC_LIB),)
TARGETDIR := $(LIBDIR)
TARGET := $(subst .a,_$(LIB_ARCH)$(LIBSUFFIX).a,$(LIBDIR)/$(STATIC_LIB))
LINKLINE = ar rucv $(TARGET) $(OBJS)
else
ifneq ($(OMIT_CUTIL_LIB),1)
LIB += -lcutil_$(LIB_ARCH)$(LIBSUFFIX)
endif
ifneq ($(OMIT_SHRUTIL_LIB),1)
LIB += -lshrutil_$(LIB_ARCH)$(LIBSUFFIX)
endif
# Device emulation configuration
ifeq ($(emu), 1)
NVCCFLAGS += -deviceemu
CUDACCFLAGS +=
BINSUBDIR := emu$(BINSUBDIR)
# consistency, makes developing easier
CXXFLAGS += -D__DEVICE_EMULATION__
CFLAGS += -D__DEVICE_EMULATION__
endif
TARGETDIR := $(BINDIR)/$(BINSUBDIR)
TARGET := $(TARGETDIR)/$(EXECUTABLE)
LINKLINE = $(LINK) -o $(TARGET) $(OBJS) $(LIB)
endif
# check if verbose
ifeq ($(verbose), 1)
VERBOSE :=
else
VERBOSE := @
endif
# Check for input flags and set compiler flags appropriately
ifeq ($(fastmath), 1)
NVCCFLAGS += -use_fast_math
endif
ifeq ($(keep), 1)
NVCCFLAGS += -keep
NVCC_KEEP_CLEAN := *.i* *.cubin *.cu.c *.cudafe* *.fatbin.c *.ptx
endif
ifdef maxregisters
NVCCFLAGS += -maxrregcount $(maxregisters)
endif
ifeq ($(ptxas), 1)
NVCCFLAGS += --ptxas-options=-v
endif
# Add cudacc flags
NVCCFLAGS += $(CUDACCFLAGS)
# Add common flags
NVCCFLAGS += $(COMMONFLAGS)
CXXFLAGS += $(COMMONFLAGS)
CFLAGS += $(COMMONFLAGS)
ifeq ($(nvcc_warn_verbose),1)
NVCCFLAGS += $(addprefix --compiler-options ,$(CXXWARN_FLAGS))
NVCCFLAGS += --compiler-options -fno-strict-aliasing
endif
# Set up object files
OBJDIR := $(ROOTOBJDIR)/$(LIB_ARCH)/$(BINSUBDIR)
OBJS += $(patsubst %.cpp,$(OBJDIR)/%.cpp.o,$(notdir $(CCFILES)))
OBJS += $(patsubst %.c,$(OBJDIR)/%.c.o,$(notdir $(CFILES)))
OBJS += $(patsubst %.cu,$(OBJDIR)/%.cu.o,$(notdir $(CUFILES)))
# Set up cubin output files
CUBINDIR := $(SRCDIR)data
CUBINS += $(patsubst %.cu,$(CUBINDIR)/%.cubin,$(notdir $(CUBINFILES)))
# Set up PTX output files
PTXDIR := $(SRCDIR)data
PTXBINS += $(patsubst %.cu,$(PTXDIR)/%.ptx,$(notdir $(PTXFILES)))
# Rules
$(OBJDIR)/%.c.o : $(SRCDIR)%.c $(C_DEPS)
$(VERBOSE)$(CC) $(CFLAGS) -o $@ -c $<
$(OBJDIR)/%.cpp.o : $(SRCDIR)%.cpp $(C_DEPS)
$(VERBOSE)$(CXX) $(CXXFLAGS) -o $@ -c $<
# Default arch includes gencode for sm_10, sm_20, sm_30, and other archs from GENCODE_ARCH declared in the makefile
$(OBJDIR)/%.cu.o : $(SRCDIR)%.cu $(CU_DEPS)
$(VERBOSE)$(NVCC) $(GENCODE_SM10) $(GENCODE_ARCH) $(GENCODE_SM20) $(GENCODE_SM30) $(NVCCFLAGS) $(SMVERSIONFLAGS) -o $@ -c $<
# Default arch includes gencode for sm_10, sm_20, sm_30, and other archs from GENCODE_ARCH declared in the makefile
$(CUBINDIR)/%.cubin : $(SRCDIR)%.cu cubindirectory
$(VERBOSE)$(NVCC) $(GENCODE_SM10) $(GENCODE_ARCH) $(GENCODE_SM20) $(GENCODE_SM30) $(CUBIN_ARCH_FLAG) $(NVCCFLAGS) $(SMVERSIONFLAGS) -o $@ -cubin $<
$(PTXDIR)/%.ptx : $(SRCDIR)%.cu ptxdirectory
$(VERBOSE)$(NVCC) $(CUBIN_ARCH_FLAG) $(NVCCFLAGS) $(SMVERSIONFLAGS) -o $@ -ptx $<
# The following definition is a template that gets instantiated for each SM
# version (sm_10, sm_13, etc.) stored in SMVERSIONS. It does 2 things:
# 1. It adds to OBJS a .cu_sm_XX.o for each .cu file it finds in CUFILES_sm_XX.
# 2. It generates a rule for building .cu_sm_XX.o files from the corresponding
# .cu file.
# The intended use for this is to allow Makefiles that use common.mk to compile
# files to different Compute Capability targets (aka SM arch version). To do
# so, in the Makefile, list files for each SM arch separately, like so:
# This will be used over the default rule abov
# CUFILES_sm_10 := mycudakernel_sm10.cu app.cu
# CUFILES_sm_12 := anothercudakernel_sm12.cu
define SMVERSION_template
#OBJS += $(patsubst %.cu,$(OBJDIR)/%.cu_$(1).o,$(notdir $(CUFILES_$(1))))
OBJS += $(patsubst %.cu,$(OBJDIR)/%.cu_$(1).o,$(notdir $(CUFILES_sm_$(1))))
$(OBJDIR)/%.cu_$(1).o : $(SRCDIR)%.cu $(CU_DEPS)
# $(VERBOSE)$(NVCC) -o $$@ -c $$< $(NVCCFLAGS) $(1)
$(VERBOSE)$(NVCC) -gencode=arch=compute_$(1),code=\"sm_$(1),compute_$(1)\" $(GENCODE_SM20) $(GENCODE_SM30) -o $$@ -c $$< $(NVCCFLAGS)
endef
# This line invokes the above template for each arch version stored in
# SM_VERSIONS. The call funtion invokes the template, and the eval
# function interprets it as make commands.
$(foreach smver,$(SM_VERSIONS),$(eval $(call SMVERSION_template,$(smver))))
$(TARGET): makedirectories $(OBJS) $(CUBINS) $(PTXBINS) Makefile
$(VERBOSE)$(LINKLINE)
cubindirectory:
$(VERBOSE)mkdir -p $(CUBINDIR)
ptxdirectory:
$(VERBOSE)mkdir -p $(PTXDIR)
makedirectories:
$(VERBOSE)mkdir -p $(LIBDIR)
$(VERBOSE)mkdir -p $(OBJDIR)
$(VERBOSE)mkdir -p $(TARGETDIR)
tidy :
$(VERBOSE)find . | egrep "#" | xargs rm -f
$(VERBOSE)find . | egrep "\~" | xargs rm -f
clean : tidy
$(VERBOSE)rm -f *.stub.c *.gpu *.cu.cpp *.i *.ii
$(VERBOSE)rm -f *.cubin *.ptx *.fatbin.c *.hash
$(VERBOSE)rm -f *.cudafe1.c *.cudafe2.c *.cudafe1.cpp *.cudafe2.cpp
$(VERBOSE)rm -f $(OBJS)
$(VERBOSE)rm -f $(CUBINS)
$(VERBOSE)rm -f $(PTXBINS)
$(VERBOSE)rm -f $(TARGET)
$(VERBOSE)rm -f $(NVCC_KEEP_CLEAN)
$(VERBOSE)rm -f $(ROOTBINDIR)/$(OSLOWER)/$(BINSUBDIR)/*.ppm
$(VERBOSE)rm -f $(ROOTBINDIR)/$(OSLOWER)/$(BINSUBDIR)/*.pgm
$(VERBOSE)rm -f $(ROOTBINDIR)/$(OSLOWER)/$(BINSUBDIR)/*.bin
$(VERBOSE)rm -f $(ROOTBINDIR)/$(OSLOWER)/$(BINSUBDIR)/*.bmp
$(VERBOSE)rm -f $(ROOTBINDIR)/$(OSLOWER)/$(BINSUBDIR)/*.txt
$(VERBOSE)rm -f $(CUBINDIR)/*.cubin $(PTXDIR)/*.ptx
$(VERBOSE)rm -rf $(ROOTOBJDIR)
$(VERBOSE)rm -rf $(LIBDIR)
$(VERBOSE)rm -rf $(OBJDIR)
$(VERBOSE)rm -rf $(TARGETDIR)
clobber : clean
$(VERBOSE)rm -rf $(COMMONDIR)/lib/*.a
$(VERBOSE)rm -rf $(SHAREDDIR)/lib/*.a
$(VERBOSE)rm -rf $(COMMONDIR)/obj
$(VERBOSE)rm -rf $(SHAREDDIR)/obj
The output of echo $LD_LIBRARY_PATH is blank.
I have checked for libcuda and can find it:
# ls /usr/lib | grep libcuda
libcuda.so.1
libcuda.so.304.32
Is there something obvious I need to do to get these to compile?
Thanks again.

Nvidia Driver Update for MSi Gt 683

Hello Fellows;
I own a MSi GT683-244R notebook.
I received a Beta key for testing the game Battlefield 3 but when I try to start the game they said that the Nvidia Driver is a old version and I need the latest one. I went to Nvidia web page to try to update my driver and I saw that my notebook from MSI is not supported, I need to download from MSI Website. On MSI driver page (http://www.msi.com/product/nb/GT683.html#/?div=Driver&os=Win7%2064) the driver version is 268.12 and on Nvidia driver page (http://www.nvidia.com/Download/Find.aspx?lang=en-us) the lastest certified is 280.26.
So, my question is... when MSI will launch the latest driver for our notebook???
GT is a gaming notebook series, so we need the latest driver, please MSI, update it for us.
Best Regards;
FaHeinen

Quote from: DoDeH1 on 03-October-11, 00:30:43
Product Support
This driver supports the following NVIDIA notebook GPUs (please refer to the Products Supported tab for exceptions):
ION notebook GPUs.
GeForce 8M, 9M, 100M, 200M, 300M, 400M, and 500M-series notebook GPUs.
Quadro 5010M, 5000M, 4000M 3000M, 2000M and 1000M notebook GPUs.
Quadro NVS-series notebook GPUs (only those that support DirectX 10 or higher).
Quadro FX-series notebook GPUs (only those that support DirectX 10 or higher).
NVS-series notebook GPUs (only those that support DirectX 10 or higher).
And by the way I use them on my GT680 without a problem.
You cannot install any video drivers outside of the live update. Nvidia released a beta driver specifically for the Battlefield 3 beta that has been released. because its not available through the live update, you cannot install it on the MSI notebooks.

Nvidia driver question

Similar Messages

Maybe you are looking for