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

Bug#482305: kernel 2.6.25-2-686 has xen support



Package: linux-image-2.6.25-2-686
Version: 2.6.25-3

	Hi,

I updated sid/unstable a few minutes ago and when I try to re-compile nvidia propietary module, this message appears:

 Detected compiler version : 4.1.2

 Using compiler gcc-4.1 version 4.1.2

 touch /usr/src/modules/nvidia-kernel/nv/gcc-check

 touch /usr/src/modules/nvidia-kernel/nv/cc-sanity-check

 ## Main Make ##

IGNORE_CC_MISMATCH=1 CC="gcc-4.1" /usr/bin/make -C /usr/src/modules/nvidia
 make[2]: Entering directory `/usr/src/modules/nvidia-kernel/nv'

 The kernel you are installing for is a Xen kernel!



 The NVIDIA driver does not currently work on Xen kernels. If

 you are using a stock distribution kernel, please install

 a variant of this kernel without Xen support; if this is a

 custom kernel, please install a standard Linux kernel.  Then

 try installing the NVIDIA kernel module again.


...then, I think about what kernel is running and this is the "standard" (I mean, no xen support)


root@cube:~# uname -a
Linux cube.dns-local.net 2.6.25-2-686 #1 SMP Wed May 14 16:42:03 UTC 2008 i686 GNU/Linux
root@cube:~#

	apt-cache reveals the following kernels availables

linux-image-2.6.25-2-486 - Linux 2.6.25 image on x86
linux-image-2.6.25-2-686 - Linux 2.6.25 image on PPro/Celeron/PII/PIII/P4
linux-image-2.6.25-2-686-bigmem - Linux 2.6.25 image on PPro/Celeron/PII/PIII/P4linux-image-2.6.25-2-amd64 - Linux 2.6.25 image on AMD64
linux-image-2.6.25-2-xen-686 - Linux 2.6.25 image on i686

	but I have installed (none with xen) only these packages:

ii linux-image-2.6-686 2.6.25+14 Linux 2.6 image on PPro/Celeron/PII/PIII/P4 ii linux-image-2.6-k7 2.6.25+14 Linux 2.6 image on AMD K7 - transition packa ii linux-image-2.6.25-2-686 2.6.25-3 Linux 2.6.25 image on PPro/Celeron/PII/PIII/

So I don't know if there was a bug while generating -686 version and includes xen support (as the package linux-image-2.6.25-2-xen-686) or if I have another problem (maybe related to nvidia propietary module)



Reply to: