Anyone got the binary package for nvidia to work and if so which
version.
This is a deal killer for me. I've hardly used linux since they made
installing the nvida package incomprehensible to me. The nouveau driver
is so bad it reminds me of the state of affairs with video 14 years ago.
The nv driver was better.
Someone really needs to find a way to work with nvidia. Smart phones
have better video for cripes sake.
Am Sat, 03 Nov 2012 09:14:15 -0400
schrieb Ron Gibson <rsgib...@tampabay.rr.com>:
> RE: Slackware 14
> Anyone got the binary package for nvidia to work and if so which
> version.
> This is a deal killer for me. I've hardly used linux since they made
> installing the nvida package incomprehensible to me. The nouveau
> driver is so bad it reminds me of the state of affairs with video 14
> years ago.
> The nv driver was better.
> Someone really needs to find a way to work with nvidia. Smart phones
> have better video for cripes sake.
Working ok here: Slackware 14, GT 9500, NVIDIA-linux-x86-304.60. The
previous version did work as well, out of the box. I'm running 32 bit
slackware and hardly ever had problems with the nvidia binary. It was
always downloading the driver, su, running the installer and ready.
Ron Gibson <rsgib...@tampabay.rr.com> wrote:
> RE: Slackware 14
> Anyone got the binary package for nvidia to work and if so which
> version.
> This is a deal killer for me. I've hardly used linux since they made
> installing the nvida package incomprehensible to me. The nouveau driver
> is so bad it reminds me of the state of affairs with video 14 years ago.
> The nv driver was better.
> Someone really needs to find a way to work with nvidia. Smart phones
> have better video for cripes sake.
What is the problem. You have to have the appropriate ???.run
file from NVidia for your video card. My card is a GEForce 9500
and I use NVIDIA-Linux-x86-304.37.run.
After sh the run file, you have to accept the conditions.
Thereafter the process runs by itself. If your driver
is too old for your current kernel you have to get a
later driver.
The nvidia module will not load if nouveau is already
loaded, therefore you have to blacklist nouveau in
the file /etc/modprobe.d/blacklist.conf.
The single line:
blacklist nouveau
suffices. Then you have to boot to get rid of nouveau
and then you can load the nvidia module.
On Sat, 3 Nov 2012 18:09:56 +0000 (UTC), root <NoEM...@home.org> wrote:
>What is the problem. You have to have the appropriate ???.run
>file from NVidia for your video card. My card is a GEForce 9500
>and I use NVIDIA-Linux-x86-304.37.run.
GTX 460, Slack 14, standard Intel mobo and CPU.
Binary attempted: NVIDIA-Linux-x86-302.17
>After sh the run file, you have to accept the conditions.
>Thereafter the process runs by itself. If your driver
>is too old for your current kernel you have to get a
>later driver.
Tried this.
>The nvidia module will not load if nouveau is already
>loaded, therefore you have to blacklist nouveau in
>the file /etc/modprobe.d/blacklist.conf.
Did that.
>The single line:
>blacklist nouveau
>suffices. Then you have to boot to get rid of nouveau
>and then you can load the nvidia module.
Well I give up on Slackbuilds. It points to a file I can not find. So
the binary will have to work.
I have an older Nvidia binary that might work - 270.something. But the
Slackbuild simply won't go without the necessary files and/or the script
is incorrect. I've looked in the info file and the file it sites for a
source (which BTW differs from what you get from the link on the
website) won't work. I can't any find source.tar.gz any file that will
work in the script.
I'm done several Slackbuilds and this one has errors in it. If someone
did it successfully I'd appreciate a URL for the 32 bit source file that
will not throw off a "not found error".
Right now the status is
1) Slackbuild scripts and docs have errors.
2) The nvidia binary won't go, however I have old binaries that worked
(with previous Slackware and other distros) archived. Also I can do
stuff like use my xorg.conf from previous Slackware versions.
Most effort has gone into the build script. Unless I get more info I'm
stopping that approach.
but I prefer
http://www.nvidia.com/Download/index.aspx?lang=en-us Select the 5 options correctly and click Search.
I have a geforce 8400 gs so for me the correct series is geforce 8 series.
The Product, of course, is geforce 8400 gs.
This installs on a 32-bit Slackware-14.0, so OS is linux 32-bit.
Search takes me to http://www.nvidia.com/object/linux-display-ia32- 304.60-driver.html where I click Download.
I save that to /install, which contains such stuff as IBM's OmniFind Yahoo! Edition, Oracle's Vbox, and my previous version (295.40) of the nVidia driver.
You MUST have installed the correct kernel source tree into /usr/src/linux-VERSION, which for 14.0 is linux-3.2.29. You do not need to compile the kernel, but the source must exist and 'make oldconfig', run from /usr/src/linux-3.2.29, must work.
You SHOULD install package extra/xf86-video-nouveau-blacklist.
Make sure that NVIDIA-Linux-x86-304.60.run is executable (chmod 755) and then, logged in as root to a console (because you're installing system software, after all) run it:
./NVIDIA-Linux-x86-304.60.run
It will ask you to accept the license and then will install. When it finishes, it will offer to create a suitable xorg.conf and backs up the existing one for you Justin Case.
If you put NVIDIA-Linux-x86-304.60.run into the same subdirectory as nvidia-driver.SlackBuild and edit the SlackBuild so the versioning is correct, you can build a Slackware package. I can't imagine why you'd do that unless you wanted to switch between the proprietary and the (broken) Linux GPL driver...
And yes, nVidia's drivers work. Like gangbusters.
-- buck
On 3 Nov 2012 21:18:39 GMT, buck <b...@private.mil> wrote:
>Ron Gibson <rsgib...@tampabay.rr.com> wrote in >news:ep5a98plcr0t8cliq2ojr6ffdun6355pro@4ax.com: >> Anyone got the binary package for nvidia to work and if so which
>> version.
>Your're not the brighest crayon in the box, are you? And when I look >up 'stubbon' in the dictionary, I see Ron Gibson.
What an asshole. I just solved the problem and the answer was nothing
like what you state.
Piece of advice - give up you night job as a "guru" sheet for brains.
I've been using Slackware since kernel 0.9, child.
Now quit embarrassing yourself. People are watching and laughing.
>> Anyone got the binary package for nvidia to work and if so which
>> version.
>> This is a deal killer for me. I've hardly used linux since they made
>> installing the nvida package incomprehensible to me. The nouveau driver
>> is so bad it reminds me of the state of affairs with video 14 years ago.
>> The nv driver was better.
>> Someone really needs to find a way to work with nvidia. Smart phones
>> have better video for cripes sake.
>What is the problem. You have to have the appropriate ???.run
>file from NVidia for your video card. My card is a GEForce 9500
>and I use NVIDIA-Linux-x86-304.37.run.
>After sh the run file, you have to accept the conditions.
>Thereafter the process runs by itself. If your driver
>is too old for your current kernel you have to get a
>later driver.
>The nvidia module will not load if nouveau is already
>loaded, therefore you have to blacklist nouveau in
>the file /etc/modprobe.d/blacklist.conf.
>The single line:
>blacklist nouveau
>suffices. Then you have to boot to get rid of nouveau
>and then you can load the nvidia module.
>>> Anyone got the binary package for nvidia to work and if so which
>>> version.
>>Your're not the brighest crayon in the box, are you? And when I look up
>>'stubbon' in the dictionary, I see Ron Gibson.
> What an asshole. I just solved the problem and the answer was nothing
> like what you state.
> Piece of advice - give up you night job as a "guru" sheet for brains.
> I've been using Slackware since kernel 0.9, child.
> Now quit embarrassing yourself. People are watching and laughing.
Actually, I'd say it's you who's embarrassed themselves.
Installing the binary Nvidia driver is trivial, and has been for years.
You keep whining about a fucking Slackbuild, and the lack of a "source" file. Well, guess what? The goddam Nvidia driver is a *BINARY* and there is no fucking source, because it's NOT open-source. You didn't fucking know that?
Jesus, at least you blundered in to getting it running. Now you can run along and STFU, perhaps.
On 04 Nov 2012 03:20:53 GMT, Dan C <youmustbejok...@lan.invalid> wrote:
>> Piece of advice - give up you night job as a "guru" sheet for brains.
>> I've been using Slackware since kernel 0.9, child.
>> Now quit embarrassing yourself. People are watching and laughing.
>Actually, I'd say it's you who's embarrassed themselves.
>Installing the binary Nvidia driver is trivial, and has been for years.
Oh what a genius. Sure it is but getting it to run when you have the
hardware is not, Mandrake boy.
>You keep whining about a fucking Slackbuild, and the lack of a "source" >file. Well, guess what? The goddam Nvidia driver is a *BINARY* and >there is no fucking source, because it's NOT open-source. You didn't >fucking know that?
What do you think idiot. I told you that years before you switched from
the hand holding distro you were using. And now you are a guru and are
so dense you don't remember the many times I defended you despite the
throng of people calling you a loud mouth chest thumping troll.
What's up - dense dan - You going senile?
See the difference is some know how to solve problems and others look
for "pack manager help". I make stuff work when it shouldn't or won't
and golly gee whiz the result of any compile process is a binary - Woo
hoo.
Guess what - this would have failed even with your beloved package
managers of old.
>Jesus, at least you blundered in to getting it running. Now you can run >along and STFU, perhaps.
>Friggin n00bs.
Frigging moron - Used Slackware since 1993.
You are obscuring something important I came across that will surely be
of help to others.
Did you have a solution? No. Oh you can add is "Nvidia always works" and
it doesn't - The reasons for the recent problems are well documented. I
suggest you get your head out your ass and reduce the noise as some
actually want to see this stuff for when they have similar problems.
If you really want to add something follow the link I posted and ask
questions about why this affected my installation.
Or is that too difficult for you to squeeze in your busy schedule of net
troll and general loud mouth.
Ron Gibson wrote:
> On 04 Nov 2012 03:20:53 GMT, Dan C <youmustbejok...@lan.invalid> wrote:
>>> Piece of advice - give up you night job as a "guru" sheet for brains.
>>> I've been using Slackware since kernel 0.9, child.
>>> Now quit embarrassing yourself. People are watching and laughing.
>>Actually, I'd say it's you who's embarrassed themselves.
>>Installing the binary Nvidia driver is trivial, and has been for years.
> Oh what a genius. Sure it is but getting it to run when you have the
> hardware is not, Mandrake boy.
>>You keep whining about a fucking Slackbuild, and the lack of a "source"
>>file. Well, guess what? The goddam Nvidia driver is a *BINARY* and
>>there is no fucking source, because it's NOT open-source. You didn't
>>fucking know that?
> What do you think idiot. I told you that years before you switched from
> the hand holding distro you were using. And now you are a guru and are
> so dense you don't remember the many times I defended you despite the
> throng of people calling you a loud mouth chest thumping troll.
> What's up - dense dan - You going senile?
> See the difference is some know how to solve problems and others look
> for "pack manager help". I make stuff work when it shouldn't or won't
> and golly gee whiz the result of any compile process is a binary - Woo
> hoo.
> Guess what - this would have failed even with your beloved package
> managers of old.
>>Jesus, at least you blundered in to getting it running. Now you can run
>>along and STFU, perhaps.
>>Friggin n00bs.
> Frigging moron - Used Slackware since 1993.
> You are obscuring something important I came across that will surely be
> of help to others.
> Did you have a solution? No. Oh you can add is "Nvidia always works" and
> it doesn't - The reasons for the recent problems are well documented. I
> suggest you get your head out your ass and reduce the noise as some
> actually want to see this stuff for when they have similar problems.
> If you really want to add something follow the link I posted and ask
> questions about why this affected my installation.
> Or is that too difficult for you to squeeze in your busy schedule of net
> troll and general loud mouth.
On Sun, 04 Nov 2012 08:13:38 -0500, "John K. Herreshoff"
<jkh...@winntel.net> wrote:
>> http://www.question-defense.com/2010/05/14/nvidia-could-not-open-the- >device-file-devnvidia-inputoutput-error
>Ron! That's enough. Get it working and you'll be a happy camper. Forget >the ego stuff, both of you!
>John, resident psychologist and handyman geek.
Yeah, you're right. I do have it working now, finally.
I should add some more details on exactly how this unfolded as it was
sneaky.
I've had a TV capture card for many years. It was coupled with AGP video
cards in the past.
I added PCIe video a while back - Nvidia binary still worked. I added a
different model capture card.
Still it worked - Actually the older kernels did not have the code
necessary to make the newer tuner card work.
Now when they started adding support for my tuner card the nvidia driver
stopped working for me.
The tuner card also needs more vmalloc allocated memory as does the PCIe
video card and a resource collision occurred.
The bad is I chased other solutions for almost a year now - I was
thinking the rift between Nvidia and Linus was the cause. So I waited
hoping things would sort themselves out as time went on when in fact it
was a memory problem on 32 bit architecture.
I should try a 64 bit version now I guess but I always wait for a while
to try the latest stuff as in the past that has been the easy way to
avoid problems. In this case that backfired.
The link at the top explains this problem as conflict between graphic
devices.
"The error happens on 32 bit linux systems when you try to initiate more
graphics cards than the kernel can allocate memory for."
The tuner card uses needs memory in the same way the graphics card does.
His solution is for grub users. For lilo with memory hungry graphic
devices...
image=/boot/vmlinuz-2.2.17-14
label = 2.2.17
append="vmalloc=256MB" # Use more if necessary
read-only
root=/dev/sda9
And a few words on vmalloc...
"We describe vmalloc here because it is one of the fundamental Linux
memory allocation mechanisms. We should note, however, that use of
vmalloc is discouraged in most situations. Memory obtained from vmalloc
is slightly less efficient to work with, and, on some architectures, the
amount of address space set aside for vmalloc is relatively small. Code
that uses vmalloc is likely to get a chilly reception if submitted for
inclusion in the kernel. If possible, you should work directly with
individual pages rather than trying to smooth things over with vmalloc."
>>Ron! That's enough. Get it working and you'll be a happy camper. Forget
>>the ego stuff, both of you!
>>John, resident psychologist and handyman geek.
> Yeah, you're right. I do have it working now, finally.
> I should add some more details on exactly how this unfolded as it was
> sneaky.
> I've had a TV capture card for many years. It was coupled with AGP video
> cards in the past.
> I added PCIe video a while back - Nvidia binary still worked. I added a
> different model capture card.
> Still it worked - Actually the older kernels did not have the code
> necessary to make the newer tuner card work.
> Now when they started adding support for my tuner card the nvidia driver
> stopped working for me.
> The tuner card also needs more vmalloc allocated memory as does the PCIe
> video card and a resource collision occurred.
> The bad is I chased other solutions for almost a year now - I was
> thinking the rift between Nvidia and Linus was the cause. So I waited
> hoping things would sort themselves out as time went on when in fact it
> was a memory problem on 32 bit architecture.
> I should try a 64 bit version now I guess but I always wait for a while
> to try the latest stuff as in the past that has been the easy way to
> avoid problems. In this case that backfired.
> The link at the top explains this problem as conflict between graphic
> devices.
> "The error happens on 32 bit linux systems when you try to initiate more
> graphics cards than the kernel can allocate memory for."
> The tuner card uses needs memory in the same way the graphics card does.
> His solution is for grub users. For lilo with memory hungry graphic
> devices...
> image=/boot/vmlinuz-2.2.17-14
> label = 2.2.17
> append="vmalloc=256MB" # Use more if necessary
> read-only
> root=/dev/sda9
> And a few words on vmalloc...
> "We describe vmalloc here because it is one of the fundamental Linux
> memory allocation mechanisms. We should note, however, that use of
> vmalloc is discouraged in most situations. Memory obtained from vmalloc
> is slightly less efficient to work with, and, on some architectures, the
> amount of address space set aside for vmalloc is relatively small. Code
> that uses vmalloc is likely to get a chilly reception if submitted for
> inclusion in the kernel. If possible, you should work directly with
> individual pages rather than trying to smooth things over with vmalloc."
Glad it's working for you, Ron, and sorry to hear about chasing ghosts for a year ;-) BTDT, but then that's the fun of Linux: a solution is out there.
> On Sat, 3 Nov 2012 18:09:56 +0000 (UTC), root <NoEM...@home.org> wrote:
> Here was the problem with the binary driver FOR 32 bit installation.
> You may get this error
> /dev/nvidia0 can not be loaded I/O error
> The problem is a shortage of virtual memory allocation
> The solution is to add
> append="vmalloc=512MB" to your lilo stanzas.
> Now it works with Suse 11.1, Slackware 13.37 and Slackware 14 with the
> Nvidia supplied binary.
> The results are excellent and I played a round of UT2004. The Desktop in
> 14 is excellent and I've yet to add several other tweaks..
Hey, thanks Ron! You just solved a mistery snag I have at work, on one
32bit laptop, that I've never solved (nor even tried to solve yet since
I was off)
I'll cure that trouble tomorrow and stinch a silver notch in my local howtos :D)
On Sun, 04 Nov 2012 08:02:34 -0500, Ron Gibson wrote:
> On 04 Nov 2012 03:20:53 GMT, Dan C <youmustbejok...@lan.invalid> wrote:
>>> Piece of advice - give up you night job as a "guru" sheet for brains.
>>> I've been using Slackware since kernel 0.9, child.
>>> Now quit embarrassing yourself. People are watching and laughing.
>>Actually, I'd say it's you who's embarrassed themselves.
>>Installing the binary Nvidia driver is trivial, and has been for years.
> Oh what a genius. Sure it is but getting it to run when you have the
> hardware is not, Mandrake boy.
Mandrake boy? LOL! So you *are* clueless. OK. "Getting it to run" was included in my statement that installing it is trivial, n00b.
>>You keep whining about a fucking Slackbuild, and the lack of a "source"
>>file. Well, guess what? The goddam Nvidia driver is a *BINARY* and
>>there is no fucking source, because it's NOT open-source. You didn't
>>fucking know that?
> What do you think idiot. I told you that years before you switched from
> the hand holding distro you were using. And now you are a guru and are
> so dense you don't remember the many times I defended you despite the
> throng of people calling you a loud mouth chest thumping troll.
> What's up - dense dan - You going senile?
I'm not the one wondering why there's no source for the Nvidia driver, you retard.
> See the difference is some know how to solve problems and others look
> for "pack manager help". I make stuff work when it shouldn't or won't
> and golly gee whiz the result of any compile process is a binary - Woo
> hoo.
"Package manager help"? Who the fuck is talking about that? Jesus, you're really drifting off here... *YOU* are the one talking about trying to make a "package" for this thing, not me. I install the .run script directly from Nvidia, and it works just fine for me. <BOGGLE>
> Guess what - this would have failed even with your beloved package
> managers of old.
Oh, I see. You're still frothing at the mouth about the "Mandrake Days", which were *TEN* *FUCKING* *YEARS* ago. Jesus, try to keep up, feeb.
>>Jesus, at least you blundered in to getting it running. Now you can run
>>along and STFU, perhaps.
>>Friggin n00bs.
> Frigging moron - Used Slackware since 1993.
Right. And yet..... you still can't install an Nvidia driver. Got it.
<l...@thedarkdesign.free.fr.INVALID> wrote:
>> Here was the problem with the binary driver FOR 32 bit installation.
>> You may get this error
>> /dev/nvidia0 can not be loaded I/O error
>> The problem is a shortage of virtual memory allocation
>> The solution is to add >> append="vmalloc=512MB" to your lilo stanzas. # vmalloc=512M also is proper
>> Now it works with Suse 11.1, Slackware 13.37 and Slackware 14 with the
>> Nvidia supplied binary.
>> The results are excellent and I played a round of UT2004. The Desktop in
>> 14 is excellent and I've yet to add several other tweaks..
>Hey, thanks Ron! You just solved a mistery snag I have at work, on one
>32bit laptop, that I've never solved (nor even tried to solve yet since
>I was off)
Sure. It had me stymied for almost a year and is an obscure error. I
only found 1 hit after numerous google searches that pointed this out.
While originally discovered by people who had dual video cards installed
(those wacky gamers) I also noticed an error thrown of by a video
tuner/capture card at boot that alerted - add vmalloc parameter to lilo
for this device.
So in general if you have multiple memory hungry video devices and get
errors when trying to load them kernel memory space collisions are
likely. Adding the vmalloc item will not hurt anything unless you have
very limited RAM memory. It's certainly worth a try.
On 05 Nov 2012 00:44:10 GMT, Dan C <youmustbejok...@lan.invalid> wrote:
Oh yeah I keep windows on - two versions. I also have 4 linux versions
installed and also have had BSD and OS/2 at various times.
So what - I use the best tool for the job at hand. Get over it. This is
not parade of goose steppers.
You have become a pathetic joke. It was posts by me that helped sway you
away from mandrake years ago. You are forgetting who your daddy is.
Anyone who has been posting a long while knows you are really an ass at
times. I defended you pointing out that you add good things to add at
times but your tone needed serious work.
Now you have forgotten that.
I've received many personal thanks over the years (one in the last 2
days over this issue I solved) a acknowledgement from Pat V himself for
years of helpful contributions.
I've been here since Slackware came on floppy images.
Since my purpose to be here is to help and be helped any further contact
with you is counterproductive and uncomfortable for others.
Benjamin Tappan <tappan.benja...@gmail.com> writes:
>On 2012-11-03, Ron Gibson <rsgib...@tampabay.rr.com> wrote:
>> Anyone got the binary package for nvidia to work and if so which
>> version.
>Yes, it works flawlessly on my machines. I use the version from
>slackbuilds.org. Be sure to install the nouveau-blacklist driver
>and reboot first.
I use the official NVidia package and it also works fine.
-- Aaron W. Hsu | arcf...@sacrideo.us | http://www.sacrideo.us Programming is just another word for the lost art of thinking.
