[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Wich Debian system with Intel Core 2 CPU: i386 or amd64?



On 2007-12-23 17:39 +0100, Paul Csanyi wrote:

> OK but I try to use Debian Etch i386 arch with linux-image-2.6-amd64.
> I think I must use this linux-image because of my Intel Core 2 CPU.

No, linux-image-2.6-686 would just work fine.  In fact, it would spare
you from the mess with the Nvidia modules you get here.

> So I try to install nvidia driver for my nvidia card (from lspci)
> nVidia Corporation G70 [GeForce 7600 GT]
>
> but get an error message:
> -------->
> module-assistant, interactive mode
> Build of the package nvidia-kernel-source failed!
> How do you wish to proceed?
> VIEW   Examine the build log file
> OK
> ...
>   LD [M]  /usr/src/modules/nvidia-kernel/nv/nvidia.o
> ld: Relocatable linking with relocations from format elf32-i386 \
>  (/usr/src/modules/nvidia-kernel/nv/nv-kernel.o) to format \
>  elf64-x86-64 (/usr/src/modules/nvidia-kernel/nv/nvidia.o) is not \
>  supported
> make[4]: *** [/usr/src/modules/nvidia-kernel/nv/nvidia.o] Error 1
> make[3]: *** [_module_/usr/src/modules/nvidia-kernel/nv] Error 2
> make[3]: Leaving directory `/usr/src/linux-headers-2.6.18-5-amd64'
> NVIDIA: left KBUILD.
> nvidia.ko failed to build!
> make[2]: *** [mdl] Error 1
> make[2]: Leaving directory `/usr/src/modules/nvidia-kernel/nv'
> make[1]: *** [build-stamp] Error 2
> make[1]: Leaving directory `/usr/src/modules/nvidia-kernel'
> make: *** [kdist_image] Error 2
> --------<
>
> What this error mean?

It means that you have rediscovered bug 437128¹.  This is probably
unfixable, since the nvidia-kernel-"source" consists mainly of a big
object file that is compiled for i386, not amd64.

> Must I leave the i386 arch and install amd64 before can proceed with
> nvidia install?

You may try to install the amd64 version of nvidia-kernel-source with
"dpkg --force-architecture" and see if m-a works then.  USE AT YOUR OWN
RISK!

Regards,
        Sven

¹ http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=437128


Reply to: