If any mailing list discussion came up in my google search I would have read it. As it was, I found the bug listing first. It matched my experience and my expectation that the kernel named linux-image-2.6.25-2-686 wouldn't contain xen since there was a linux-image-2.6.25-2-xen-686 kernel image.
Sorry you had to spend time sending me down a path of checking the kernel configs when the expectation of the image name wasn't valid anymore. Just so the next person who sees this bug listing can know, set IGNORE_XEN_PRESENCE to something in the shell before trying to install the NVidia driver and it will ignore the new XEN options in the kernel. Looks like it is time to drop the debian packaged kernels again and go back to my own rolled kernels. Was nice while the trust level was there guys. ----- "maximilian attems" <[EMAIL PROTECTED]> wrote: > again one of those losers who can't read a mailinglist archive. > > On Wed, Aug 27, 2008 at 02:46:25PM -0500, Steven S. Critchfield > wrote: > > > > The test the NVidia installer is using is to include > > <linux/autoconf.h>, then uses an #ifdef to see if CONFIG_XEN is > > defined. If CONFIG_XEN is defined, it fails. The other test being > used > > is to grep the .config file for CONFIG_XEN=Y. > > > > So I point out, the 2 methods they use seem to be valid tests. The > > /boot/config-2.6.25-2-686 file and the > > /usr/src/linux-headers-2.6.25-2-686/.config file have CONFIG_XEN=y. > So > > is the headers package broken, and the kernel package including the > > wrong header, or is it just that the package was misconfigured. > > > > I am very open to how I might test for XEN in the kernel. I will > even > > reboot to get that data for you. > > please learn to use your <enter> key to wrap long sentences! > > enabled paravirt xen allows to run a kernel under xen, > but is only guest support until now. > > kthxbye > > -- > maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
