Bug#570365: nvidia-glx: problem confirmed in with latest xen hypervisor
michelbriand at free.fr
Sat Jan 15 16:25:36 UTC 2011
I'm sorry Andreas, but I didn't have the time to test your proposed
change before now. It seems that someone did it (Joseph) and that the
driver does not compile.
It does not compile here either:
In file included from .../tmp/nvidia-195.36.31/nv.c:14:
.../tmp/nvidia-195.36.31/nv-linux.h:153:23: error: asm/maddr.h: Aucun fichier ou dossier de ce type
/usr/src/linux-headers-2.6.32-5-common/include/xen/interface/memory.h: At top level:
/usr/src/linux-headers-2.6.32-5-common/include/xen/interface/memory.h:32: error: expected specifier-qualifier-list before 'GUEST_HANDLE'
... plus 3 more definition errors.
.../tmp/nvidia-195.36.31/nv.c: In function 'nv_kern_open':
.../tmp/nvidia-195.36.31/nv.c:2245: error: implicit declaration of function 'HYPERVISOR_memory_op'
maddr.h does not exist on my machine.
I've found that HYPERVISOR_memory_op is defined in hypercall.h.
So I've added hypercall.h to try to make this compile :
#if defined(CONFIG_XEN) // && !defined(CONFIG_PARAVIRT)
But it fails soon after :
.../tmp/nvidia-195.36.31/nv-vm.c: In function 'nv_vm_malloc_pages':
.../tmp/nvidia-195.36.31/nv-vm.c:507: error: implicit declaration of function 'phys_to_machine'
I believe this comes from :
#define NV_GET_DMA_ADDRESS(phys_addr) phys_to_machine(phys_addr)
#define NV_GET_DMA_ADDRESS(phys_addr) (phys_addr)
However I managed to try a new test at work : I've installed latest
squeeze kernel, xen and nvidia packages (as of 09/01/2011).
I used the dkms -- great tool ;) -- to try nvidia driver version 195
and version 260 (from experimental). Both of them are nicely
compiled and installed by dkms !
But none of them would work under Xen (DOM0). Same problem with black
screen and freeze a few seconds after X starts.
More information about the pkg-nvidia-devel