On Sat, 2002-05-04 at 20:48, Kyle Super wrote: > > I recently downloaded and installed XFree86 version 4.2.0. I was using > kernel version 2.4.2-2 and had to install the latest DRI r128 binary from > http://dri.sourceforge.net/download.phtml. This went fine and I had no > problems starting the xserver. > > I then updated the kernel to version 2.4.9-31 to fix some mtrr problems. > Once again, I installed the latest DRI r128 binary, but now on xserver > startup r128.o does not load (although the xserver does start). This is what > appeared in the dri.log file after I installed r128.o for the new kernel: > > make: `r128.o' is up to date. > /usr/X11R6/lib > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: unresolved > symbol boot_cpu_data_R3gig_0657d037 > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: unresolved > symbol do_mmap_pgoff_R3gig_1b290628 > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: unresolved > symbol __pollwait_R3gig_918efb08 > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: unresolved > symbol si_meminfo_R3gig_7e9ed292 > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: unresolved > symbol fasync_helper_R3gig_a2f89fd0 > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: unresolved > symbol remove_wait_queue_R3gig_6db6b627 > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: unresolved > symbol create_proc_entry_R3gig_e59fa486 > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: unresolved > symbol kill_fasync_R3gig_c299f6cc > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: unresolved > symbol init_mm_R3gig_ae8035af > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: unresolved > symbol register_chrdev_R3gig_27f77796 > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: unresolved > symbol remove_proc_entry_R3gig_8a3df140 > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: unresolved > symbol mem_map_R3gig_0826217e > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: unresolved > symbol add_wait_queue_R3gig_307a0918 > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: unresolved > symbol pci_find_slot_R3gig_0517f8e1 > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: insmod > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o failed > /lib/modules/2.4.9-31custom-May02/kernel/drivers/char/drm/r128.o: insmod > r128 failed
The kernel module needs to be built against the source which was used to build the kernel you want to run it with. Usually, just make -f Makefile.linux clean r128.o should work while you're running that kernel, but if it picks up the wrong tree for some reason, try make -f Makefile.linux TREE=<path/to/kernel/source>/include clean r128.o -- Earthling Michel D�nzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
