Arch Linux

MadCat_X

Member

Registered: 2009-10-08

Posts: 189

nVidia 195.36 Failed Xen sanity check [sort of solved]

Hi,

I'm using custom 2.6.33.2 kernel and since the PKGBUILD of nVidia 195.36.15 drivers has been updated to release 2 I get the *** Failed Xen sanity check. Bailing out! *** message when I run "makepkg" to build the new driver. Although I customized my kernel configuration, I don't remember changing anything related to paravirtualization or Xen and it has been working fine until now. 195.36.15-1 driver had built just fine when I updated to 2.6.33.2 kernel. My .config looks like this

grep "XEN"

# CONFIG_XEN is not set

grep "PARAV"

CONFIG_PARAVIRT_GUEST=y
CONFIG_PARAVIRT=y
# CONFIG_PARAVIRT_SPINLOCKS is not set
CONFIG_PARAVIRT_CLOCK=y
# CONFIG_PARAVIRT_DEBUG is not set

I have the BFS and xorg-autoiso patches applied, but I've been using them for a while and never ran into an issue with them.

I haven't tried disabling paravirtualization altogether yet. I use VirtualBox for virtualization, which compiles its own module. Would it work with no paravirt support in kernel?

The 195.36.15-1 I built about 2 weeks ago works perfectly fine with the new Xorg and 2.6.33.2 kernel, primary reason I'd like to have this resolved is that the "nVidia 195.36.15-2" package obstructs any update through "pacman -Syu" as it appears in updates and it wouldn't work with my custom kernel.

Last edited by MadCat_X (2010-04-15 13:38:34)

MadCat_X

Member

Registered: 2009-10-08

Posts: 189

Re: nVidia 195.36 Failed Xen sanity check [sort of solved]

OK, I tried cutting the paravirtualization completely, but no to avail. Then tried building older 190.53 drivers and it worked fine, so I guess it's some sort of bug in Xen sanity detection specific to 195.36.15 drivers and maybe even 2.6.33.2 kernel...