SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've installed X11R7.1 on Slackware 11 using bits from this guide, and got it to compile just fine. Everything worked until I tried to install the latest nvidia driver. The installer complains about a missing xorg devel package, and tells me it can't find where to put the drivers. X complains on startup that it can't find the nvidia and glx modules.
I went to look for them and found the nvidia installer had created two files:
However, startx still complains it can't find the modules. If I change my xorg.conf back to use the nv module, and comment out the glx module, X starts normally.
What to do?
[EDIT]
Tried installing older nvidia drivers, 87.74, and I have the same thing. In both cases, modprobe nvidia seems to work fine and the module shows up on lsmod.
This thread is confusing... It's a wonder anyone got this beast to work. I've posted some .SlackBuilds for 7.1.1 that work rather nicely if people are still struggling with doing this the hard way.
I am running a fresh install of Slackware 11 with the 2.6.17.13 kernel. The only thing I have done so far is install madwifi for teh wireless.
I have downloaded all the tar.bz2 files from here, and installed them under /usr/X11R7/src/everything and edited the build-from-tarballs.sh to load only the savage, vesa and vga video drivers (installing on an IBM Thinkpad T23, not going to be changing the video card).
My problem is this-- when I try to build using the command (as root) build-from-tarballs.sh -e /usr/X11R7/ I get the following error:
Either you didn't download the build-from-tarballs.sh script or you forgot to put it in your path and make it executable. Since you are building as root it needs to be in roots path.
Either you didn't download the build-from-tarballs.sh script or you forgot to put it in your path and make it executable. Since you are building as root it needs to be in roots path.
... so, I need to put it in root, and not in the /usr/X11R7/src/everything directory? I made it executable across the board.
<edit>... nope, tired it from root, still nogo. </edit>
I suppose this means I will have to reinstall slack again...
Why? Sounds like you just need to find some extra space. The script build-from-tarballs.sh leaves all the tarballs and directories in place after building each package, so this will take alot of drive space. You could modify the script to remove the package directory after it is done building each module. Look at the beginning of the script in the build() function and add this line:
rm -fr $TARDIR
See below:
Code:
build() {
test "$USEMODULEDIRS" = "yes" && cd $1
TARBALL=`ls -1rt $2-*.tar.$COMPRESSION 2> /dev/null | tail -1`
if test x"$TARBALL" = x; then
echo "WARNING: $2 does not exist -- skipping"
test "$USEMODULEDIRS" = "yes" && cd ..
return
fi
TARDIR=`echo $TARBALL | sed "s,.tar.$COMPRESSION,,"`
echo "Building $1 module component $TARDIR..."
case $COMPRESSION in
bz2)
tar xjf $TARBALL
break;;
gz)
tar xvf $TARBALL
break;;
esac
cd $TARDIR
if test "$1" = "xserver" && test "$2" = "xorg-server" && test -n "$MESAPATH"; then
MESA=-"-with-mesa-source=${MESAPATH}"
else
MESA=
fi
eval sh configure --prefix=${PREFIX} ${MESA} ${QUIET:+--quiet} \
${CACHE:+--cache-file=}${CACHE} ${CONFFLAGS} || failed configure $1 $2
make || failed make $1 $2
if test x"$CLEAN" = x1; then
make clean || failed clean $1 $2
fi
if test x"$DIST" = x1; then
make dist || failed dist $1 $2
fi
if test x"$DISTCHECK" = x1; then
make distcheck || failed distcheck $1 $2
fi
$SUDO env LD_LIBRARY_PATH=$LD_LIBRARY_PATH make install || \
failed install $1 $2
cd ..
# Add this to create some more space
rm -fr $TARDIR
test "$USEMODULEDIRS" = "yes" && cd ..
}
like Ladak says, it is doesn't appear to be a problem with permissions. i chmoded 755 to all of them and i am logged on with root. This is caused by the "make install" command so....
To get around this i am manually copying over the files
Last edited by chrisortiz; 02-16-2007 at 07:51 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.