Does anyone know how to get a module from slackbuilds working?

[joop g]

I thought it might be better to download my nvidia drivers from
slackbuilds.org. However, I am clearly missing something. As stated in the
instructions, I run nvidia-kernel.Slackbuild, and I get nvidia-Linux-
x86.302.17.run "no such file or directory". Which is true, it is not there.
Nor can I find a place (within slackbuilds) where it can be found.

Should I simply download it fromnvidia.org? But what is then the point of
slackbuilds?

[r4f]

It should be in /tmp

[joop g]

Well, it isn't. I have now simply downloaded the install module from
geforce.com. But I still do not understand what was worng with (my use of)
slackbuilds.

[slakmagik]

If I'm understanding you correctly, you do need to download the source
tarball and to place it in the same directory with the slackbuild. (The
location of the source is recorded in the .info file that goes along
with the slackbuild.) The purpose of the slackbuilds is to run the build
process, along with any needed patches or setup or other tweaks, and to
create a slackware package that can be managed with the usual slackware
package tools. But you still need to get the source that the slackbuild
operates on. There are third party tools to do that part for you but you
might want to play around with the process - even installing directly
from source yourself - to see what the slackbuilds and those tools are
automating for you.

However, if you've been using slack since 1.0 and so on, then never
mind. :)

[greymaus]

AFAIRemember, that file, which is probably propriatry, is downloadable from
www.nvidia.com, so you put it in the slackbuild. (Actually, never did that
myself)

--
maus
.
.
...

[Robby Workman]

You've seen this? http://slackbuilds.org/howto/

You have to download the source tarball(s) yourself; they're listed in
the .info file. If you want more automation, look into something like
sbopkg or some others (there are some newer ones whose names escape me
now).

-RW

[joop g]

Robby Workman wrote:

> On 2012-10-29, joop g <jj...@xs4all.nl> wrote:
>> I thought it might be better to download my nvidia drivers from
>> slackbuilds.org. However, I am clearly missing something. As stated in
>> the instructions, I run nvidia-kernel.Slackbuild, and I get nvidia-Linux-
>> x86.302.17.run "no such file or directory". Which is true, it is not
>> there. Nor can I find a place (within slackbuilds) where it can be found.
>>
>> Should I simply download it fromnvidia.org? But what is then the point of
>> slackbuilds?
>
>
> You've seen this? http://slackbuilds.org/howto/

Ah, I missed that one. Will try to do better next time.

[ishmale]

I am delighted to offer help to those who know far more than I of how to
twiddle Slackware.
It should be ./nvidia-kernel.SlackBuild

[ishmale]

On Mon, 29 Oct 2012 19:57:27 +0100, joop g wrote:

Try: ./nvidia-kernel.SlackBuild

[Ron Gibson]

It's looking for a tar.bz file (source file) and the link on slackbuild
is a link to the binary package - A major error that needs fixing.

I just finished trying to find the source package on nvidia's site with
no luck.

Maybe I'll have some answers soon but am doubtful. I just made a backup
and intend on trying some install and hope approaches.

This has been going on for a year now (or more) and is unacceptable in
this day and age - 15 years ago maybe but not now.

[Ron Gibson]

On Tue, 30 Oct 2012 03:35:33 +0000, Robby Workman
<newsg...@rlworkman.net> wrote:

>You have to download the source tarball(s) yourself; they're listed in
>the .info file. If you want more automation, look into something like
>sbopkg or some others (there are some newer ones whose names escape me
>now).

Well that clears that up. Usually the link on the main page points to
the source file but they have a bad link listed. The info file does
indeed give the proper URL.

I'm leery of this, seeing how bad links usually don't make me very
confident - going to try binary file first. Maybe I'll get lucky and it
will work.

[Ron Gibson]

On 02 Nov 2012 00:28:43 GMT, ishmale <ish...@nopsam.com> wrote:

>Try: ./nvidia-kernel.SlackBuild

Lazy way...

./*Build

:)

[Henrik Carlqvist]

On Sat, 03 Nov 2012 09:20:00 -0400, Ron Gibson wrote:
> I just finished trying to find the source package on nvidia's site with
> no luck.

Thats because nVidia does not provide the source for their binary driver.
The nVidia driver is a non-free binary driver were others are not allowed
to look at the source. Loading that driver will taint your kernel.

If you wan't a free driver with source the non-accelerated nv driver or
the not so stable, not so fast nouveau drivers are your only choices.

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc351(at)poolhem.se Examples of addresses which go to spammers:
root@localhost postmaster@localhost

[Ron Gibson]

On 04 Nov 2012 11:28:25 GMT, Henrik Carlqvist

<Henrik.C...@deadspam.com> wrote:

>> I just finished trying to find the source package on nvidia's site with
>> no luck.

>Thats because nVidia does not provide the source for their binary driver.
>The nVidia driver is a non-free binary driver were others are not allowed
>to look at the source. Loading that driver will taint your kernel.

>If you wan't a free driver with source the non-accelerated nv driver or
>the not so stable, not so fast nouveau drivers are your only choices.

I'm aware of that but the build script clearly call for the source file
- I don't get it.

In the info file (expanded build script) it gives a URL for a source
package, different from the *run binary.

The file is
ftp://download.nvidia.com/XFree86/nvidia-installer/nvidia-installer-302.17.tar.bz2

It definitely is a source file. I included it in the Build tree but when
you execute the Build script it throws an error for name mismatch.

However this is now a moot point (for me) as I fixed the problem that I
was having (vmalloc) and now useing the standard binary works like a
charm. Actually it always worked - But X would not load the results.
However my interest is still perked. I've had very good results with
Slack Builds otherwise.

I considered trying to modify the build script to call for the correct
file name to see if it would go then but that effort was abandoned when
I discovered my "vmalloc problem". The script is not so easy for a
non-progammer like me to follow.

[Henrik Carlqvist]

On Thu, 08 Nov 2012 10:41:32 -0500, Ron Gibson wrote:
> I'm aware of that but the build script clearly call for the source file
> - I don't get it.

Ok, I haven't used the slackbuild script myself. Usually I just download
the nvidial run binary and install it using checkinstall to get myself a
Slackware package. After that I manually clean out the /lib/modules/*/
modules* from the package and istead do "depmod -a" in the package
install script.

> In the info file (expanded build script) it gives a URL for a source
> package, different from the *run binary.
>
> The file is
> ftp://download.nvidia.com/XFree86/nvidia-installer/nvidia-
installer-302.17.tar.bz2

That file is not the source for the driver itself. It seems to be the
source for an install tool used to "install, upgrade, or uninstall the
NVIDIA Accelerated Graphics Driver Set". I haven't used that tool myself,
but the tool seems to have a GPL license.

> However this is now a moot point (for me) as I fixed the problem

Good that the problem is fixed!