Ubuntu
xorg package

NVIDIA driver for Asus F3S?

Asked by george_rutkay

When I try to adjust Visual effects under System/Preferences/Appearance, I am unable to set anything up greater than "None".

A small screen pops up saying "Searching for available drivers..." and it just goes on and on forever, remaining at 0%

If I go to System/Administration/Hardware drivers and let that control panel run, it identifies two NVIDIA acceletrated graphics drivers - version 173 and version 177, which it recommends.

When I select 177, click on Activate, the computer pops up the same small screen saying "Searching for available drivers..." and it just goes on and on forever, remaining at 0%.

If I restart the computer and repeat this exercise, then if I click on 173 instead, the computer pops up the same small screen saying "Searching for available drivers..." and it just goes on and on forever, remaining at 0%.

Is there anything I can do to resolve this? My wife's nephew will be using this computer for graphics work. I dual-boots next to Windows Vista and it has the graphics capacity to do well.

Thanks.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu xorg Edit question
Assignee:
No assignee Edit question
Solved by:
george_rutkay
Solved:
Last query:
Last reply:
Revision history for this message
george_rutkay (yaktur) said : 		#1

I went through Synpatic and searched for anything related to NVIDIA 177, then I enabled these. The computer needed the Ubuntu 8.10 CD so I fed it to the computer and restarted it.

Now when I go to System/Administration/Hardware drivers and let that control panel run, it identifies two NVIDIA accelerated graphics drivers - version 173 and version 177, which it recommends.

When I select 177, click on Activate, the computer pops up the small screen saying "Searching for available drivers..." and this time it succeeded. Now I restart the computer, as it says....and the driver does appear to load. I also get an icon at the top-right of the screen in the shape of a circuit board, explaining that this is a proprietary driver.

I can't say which thing really solved it, but it's better than it was before.