right, i just tried to install the NVidia drivers (again) with envy, i then made sure the universe & multiverse reops wher enabled (i was paranoid the upgrading from Feisty to Gutsy would disable them, but, it didn't) all this started when i clicked "Restricted Drivers" in System Settings however, i received this massage then this message and i finally got this screen can someone please shed any this situation, because i'm just getting more & more confused
The drivers from the Ubuntu repos are compiled against the old kernel, not your custom one, so they will not work. You'll have to build your drivers the Nvidia way. See here: http://www.hardwareforums.com/howto-install-nvidia-drivers-linux-debian-ubuntu-15319/ But first, you might want to throw the following lines into your /etc/environment file: Code: CHOST="i686-pc-linux-gnu" CFLAGS="-march=native -O2 -pipe -fomit-frame-pointer" CXXFLAGS="-march=native -O2 -pipe -fomit-frame-pointer"
thankies BTW: what does it actually do, adding those lines BTW: thanks for pulling the original post from oblivion, i couldn' fix the pic, so,i thought :swear: it, i'll post it later and a final thank you to make use both sick[ot]don't you get fed with people with you knowing more than a hell of a lot of people[/ot]
Those lines, when placed in your /etc/environment, will make it so anything you compile on your system will be optimized to run in the best possible way on your hardware, instead of being generically compatible with many system types. I suggested this so that when you build your drivers, they too will be optimized for your CPU. No problem.
i'll just think for a while, as i think i can retrieve the driver install the grx driver command from outside X, cos Here, as i think i nearly remember it, bit more thinking time required[ot]i think i place the *.run in a DIR and ls'd it, i think[/ot]
A non-graphical way you can download the current stable Nvidia drivers (as of today) like so: Code: wget http://us.download.nvidia.com/XFree86/Linux-x86/169.09/NVIDIA-Linux-x86-169.09-pkg1.run In the future, you can always find the latest stable Nvidia drivers for Linux/Unix here: Unix Drivers Portal Page
no, it didn't work, ive attached the install log for you, & even i can read what happened, so, you have no problems, see ya soon Edit: well that another way to get drivers Edit: guessing but[ot]don't believe that[/ot] they must have recently started releasing them in that way
It said that it couldn't find your kernel source path. That means that either the kernel headers package wasn't installed alongside the kernel, or else it doesn't know where to find them. If you did install the kernel header .deb file, try appending this to the end of the command line when you try to install the drivers: Code: --kernel-source-path=/usr/src/linux-headers-`uname -r` ...note that ` is used (shares the same key as ~), not ' (which shares the same key as "). So, the resulting command would look something like the following: Code: sh NVIDIA-Linux-x86-169.09-pkg1.run --x-module-path=/usr/lib/xorg/modules/ -aqNX --kernel-source-path=/usr/src/linux-headers-`uname -r`
definitely will do maybe on a US keyboard layout, but, UK shares ~ with # & an apostrophe (') is shared with @, another keyboard layout difference is: @ symbol key is swapped with speech marks (") :good:, i'll try it
Yes, you're right about the keyboard layout differences, thanks for the correction. The point I was trying to make is that you need to use a left-facing apostrophe (`), not the normal one which is typically represented strictly vertically, like a single quote ('). The left-facing apostrophe is used when you want to use a command as part of another string. In this case, we are figuring out the name of your running kernel with the `uname -r` command, and automatically putting the results right into the path.
just realised exactly how big a plank i am, i haven't being adding the last apostrophe :doh: will try again Edit not apostrophe (`)[ot]plank[/ot]
ok, now i don't know what happened, i issued the command in recovery mode & i got the familiar lines of full stops (periods) then the screen goes black with a root prompt at the bottom left runlevel 1 displaying / as %2f was more than a bit confusing at first[ot]tw4ting thing[/ot] Edit: im nearly ready to give up now getting the grx drivers working, not giving up with *nix
Why are you in runlevel one? It's less complicated than you're making it, I promise. Maybe it'd be best to just SSH into your computer from another system, then copy & paste the following command rather than trying to type it: Code: wget http://us.download.nvidia.com/XFree86/Linux-x86/169.09/NVIDIA-Linux-x86-169.09-pkg1.run && sudo sh NVIDIA-Linux-x86-169.09-pkg1.run --x-module-path=/usr/lib/xorg/modules/ -aqNX --kernel-source-path=/usr/src/linux-headers-`uname -r` Best regards, -AT
well i can only use one hand to type, so, rather than pressing keystrokes, i just fin it easier to reboot into recovery mode so, you say no, it's ok, i've survived this long with *nix without 3D, i'm sure i can survive without 3D knowing me i'll probably wait till i can access use a standalone system from a internet enable system because most off best stuff in *nix is i presume is accessed from outside X
thank you for your kind offer but that command wouldn't have worked anyway, because the *.run file is not executable to begin with, you need && chmod a+x myfile && in the middle Edit: so th command would have being Code: wget http://us.download.nvidia.com/XFree86/Linux-x86/169.09/NVIDIA-Linux-x86-169.09-pkg1.run && chmod a+x myfile && sudo sh NVIDIA-Linux-x86-169.09-pkg1.run --x-module-path=/usr/lib/xorg/modules/ -aqNX --kernel-source-path=/usr/src/linux-headers-`uname -r`
Good catch, very observative. But just so you know, "sh" will execute it whether or not it's got the execute bit set.
bo11ocks, i though i'd caught you out, if it was being executed by ./ it would need to be executable[ot]bo11ocks[/ot]but at least i thought i knew what i was talking about serves me right for trying to be a smart ass, thankies anyway
No problem, you'd be right if the run file wasn't essentially a bash script. For a binary executable, you'd be exactly correct.
well (i know it's an excuse) i am still leaning (stating the obvious) BTW: i guess that's what makes you the nonconformist geek master general
