Re: nvidia but no glx
since I know about this problem I only done a ln -s /emul/ia32-linux/lib /lib32 and voila I got my /lib32 directory, for me it works. But for now I need to have agpgart disable for full control over the nvidia module like fastwrites etc. lsmod does not show me the agpgart module but its loaded by default dmesg: gpgart: Detected AGP bridge 0 agpgart: Maximum main memory to use for agp memory: 940M agpgart: AGP aperture is 512M @ 0xc00gpgart: Detected AGP bridge 0 agpgart: Maximum main memory to use for agp memory: 940M agpgart: AGP aperture is 512M @ 0xc00 therefore I looked in the kernel config of kernel 2.8.6-3 (/usr/src/kernel-headers-2.6.8-3-amd64-k8/.config) to compile a new one with agpgart as module, but I can not enable it as module or compile it into the kernel, menuconfig is not able to switch between the two options, what Iam doing wrong here, how can agpgart be loaded when its not there? thank you andree
Re: nvidia but no glx
Raul Miller wrote: > On Sat, Sep 18, 2004 at 03:16:18PM -0600, Bob Proulx wrote: > > However, having said that, working toward multiarch is definitely a > > high priority. > > Multiarch, as proposed, will not address the issue indicated in the > subject line. Agreed. But if nVidia supported multiarch, then we would have something. I was trying to imply that but failed. > To address that issue requires other measures (one was already described > in this thread -- other possibilities some way of remapping the file > system so the nvdia install puts things thing in the right places, or > cooperation from nvidia to support what is now the debian amd64 file > system layout (for example, they might offer to not install the 32 bit > libs at all -- that would allow them to stay FHS compliant and still > support /lib64 being the same as /lib)). That would be a safe compromise for nvidia until there was general agreement. However, if they were making changes to their installer then they could detect if lib64 pointed to lib and if so automatically do the right thing. That would be even better! Bob pgpvaDSF5cQaV.pgp Description: PGP signature
Re: nvidia but no glx
On Sat, Sep 18, 2004 at 03:16:18PM -0600, Bob Proulx wrote: > However, having said that, working toward multiarch is definitely a > high priority. Multiarch, as proposed, will not address the issue indicated in the subject line. To address that issue requires other measures (one was already described in this thread -- other possibilities some way of remapping the file system so the nvdia install puts things thing in the right places, or cooperation from nvidia to support what is now the debian amd64 file system layout (for example, they might offer to not install the 32 bit libs at all -- that would allow them to stay FHS compliant and still support /lib64 being the same as /lib)). -- Raul
Re: nvidia but no glx
Sebastian Steinlechner wrote: > The problem here is, that /usr/lib64 is a symlink to /usr/lib in debian > pure64 (though I don't know why that is). You answered your own question-statement without realizing it. By "pure64" you can tell that it is a pure 64-bit system in the same way that an i386 installation is a pure 32-bit system. That is to say that /usr/lib is the native architecture. On amd64 the native architecture is 64-bits so /usr/lib is the natural location for the native 64-bit libraries. As a pure system it does not have accommodations for the older, troubled, and obsolete biarch nor the newer but not yet implemented multiarch. The symlink from lib64 pointing to lib is an accommodation for the older biarch model. However, having said that, working toward multiarch is definitely a high priority. And the underlying cpu and kernel does have the capability to run both 64-bit and 32-bit architectures on the same system. It is possible to run both and most of us do. But it is not not wonderfully pretty at the moment. That is what multiarch is supposed to solve. Much of the add-on software from non-debian origin is targeting less enlightened distributions using a different system architecture model and so issues like these are going to be common on Debian amd64 for a while. That is going to be a task that many on this list will be working through in the days ahead. Debugging, patching, educating, and advocating. I still would not trade it out since I believe the effort to create a better Debian is worthwhile. Bob pgpjVHc0qrzoD.pgp Description: PGP signature
Re: nvidia but no glx
> The problem here is, that /usr/lib64 is a symlink to /usr/lib in debian > pure64 (though I don't know why that is). The nvidia installer tries to > install all its 64bit libs in /usr/lib64 (so they are effectively > written to /usr/lib) and then writes the 32bit libs in /usr/lib. That's > where you get the error - because the 64bit libs are already there. > It's > obviously a Bad Thing and I'd like to see this fixed... Yes this would be nice, I was running gentoo and fedora 2 before wich has this lib32 directory, > Whatever, if you don't need the 32bit libraries, then you might just > remove the /usr/lib64 symlink and create a real directory instead. Run > the installer, then copy the contents of /usr/lib64 over to /usr/lib and > make it a symlink again. If you want to use the 32bit libraries as well, > you have to manually copy them to /emul/ia32-linux/usr/lib - it's > probably easiest to tell the nvidia installer to just extract all the > files in a directory and then copy them over by hand. This worked, glx is now running, thank you
Re: nvidia but no glx
On Sat, 2004-09-18 at 20:47, Andree Zeulner wrote: > could someone give me an explanation about how to install the newest > nvidia-drivers? The problem here is, that /usr/lib64 is a symlink to /usr/lib in debian pure64 (though I don't know why that is). The nvidia installer tries to install all its 64bit libs in /usr/lib64 (so they are effectively written to /usr/lib) and then writes the 32bit libs in /usr/lib. That's where you get the error - because the 64bit libs are already there. It's obviously a Bad Thing and I'd like to see this fixed... Whatever, if you don't need the 32bit libraries, then you might just remove the /usr/lib64 symlink and create a real directory instead. Run the installer, then copy the contents of /usr/lib64 over to /usr/lib and make it a symlink again. If you want to use the 32bit libraries as well, you have to manually copy them to /emul/ia32-linux/usr/lib - it's probably easiest to tell the nvidia installer to just extract all the files in a directory and then copy them over by hand. > install log from installer: > > Installing 'NVIDIA Accelerated Graphics Driver for Linux-x86_64' >(1.0-6111): > ERROR: Unable to determine properties for file >'/usr/X11R6/lib64/modules/extensions/libglx.a' (No such file or >directory). > -> The installer has encountered the following error during installation: > 'Cann >ot backup /usr/X11R6/lib64/modules/extensions/libglx.a'. Continue anyway? > ( >"no" will abort)? (Answer: Yes) signature.asc Description: This is a digitally signed message part
