Re: [Dri-devel] how to enable i810 DRI with XFree4.0.1

[Keith W. <ke...@va...>]

David Raulo wrote:
> 
> > > I'm using 2.4.0-test3 kernel. I couldn't find i810 DRI support in kernel config, only i810 agpgart support. However I thought that no kernel module apart from agpgart was needed. Is a special kernel module needed for DRI? I've seen a reference to a kernel-module named i810.o in X documentation, but couldn't find it. Probably there's another explanation...
> >
> > You need to build the i810.o kernel module.  It lives in
> > xc/xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel.  Make with
> > 'make -f Makefile.linux' on the target system.
> >
> > Keith
> 
> Thank you for the fast response!
> 
> I downloaded a DRI snapshot and build the i810.o module. Didn't work with linux-2.4.0-test3, succeeded with linux-2.3.99-pre6. Now I get unresolved symbol while loading the module:
> 
> # modprobe i810
> /lib/modules/2.3.99-pre6/misc/i810.o: unresolved symbol mtrr_add
> /lib/modules/2.3.99-pre6/misc/i810.o: unresolved symbol __generic_copy_from_user
> /lib/modules/2.3.99-pre6/misc/i810.o: unresolved symbol create_proc_entry
> /lib/modules/2.3.99-pre6/misc/i810.o: unresolved symbol boot_cpu_data
> /lib/modules/2.3.99-pre6/misc/i810.o: unresolved symbol iounmap
> /lib/modules/2.3.99-pre6/misc/i810.o: unresolved symbol __ioremap
> /lib/modules/2.3.99-pre6/misc/i810.o: unresolved symbol mtrr_del
> /lib/modules/2.3.99-pre6/misc/i810.o: unresolved symbol remove_proc_entry
> /lib/modules/2.3.99-pre6/misc/i810.o: unresolved symbol pci_find_slot
> /lib/modules/2.3.99-pre6/misc/i810.o: unresolved symbol kill_fasync
> /lib/modules/2.3.99-pre6/misc/i810.o: unresolved symbol __generic_copy_to_user
> /lib/modules/2.3.99-pre6/misc/i810.o: insmod /lib/modules/2.3.99-pre6/misc/i810.o failed
> /lib/modules/2.3.99-pre6/misc/i810.o: insmod i810 failed
> 
> Probably I missed some options while configuring my kernel (I enabled support for MTRR, DRM, and i810 AGPGART). Is there a documentation about that?

You probably don't want DRM, as you are replacing that with a new one from the
X tree.  Is it possible that the module was compiled with different header
files than the ones belonging to that kernel version?  The functions you are
missing seem quite fundamental, so I'm not sure how they can be missing...  

Keith