Thilo, You make it sound as though you propose an easy and obvious solution with no adverse side-effects. Such is not the case. You are implicitly assuming a compatibility model in which any newer version of r128.o is GUARANTEED to work with any older version of the DRI. In ideal world that would be an ideal objective. In the real world, that is an unrealistic objective given rate at which the DRI code base has been evolving. After having fought (and lost) many battles with DRI and kernel installs (but now having a number of working installs), it is my feeling that it would be preferable to REMOVE the kernel drivers from the kernel source, thus making them module-only, and distribute them with XFree and/or the DRI-CVS. In that way, a person doing a complete build of X or DRI will end up with a compatible set of components and a person doing a kernel upgrade need only rebuild the kernel driver module associated with the compatible X/DRI distribution from source. At some point in the future things may stabilize to the point that your proposal becomes feasible, but I don't think we are quite there yet. Mike (not speaking for DRI developers) Westall Thilo Kopp wrote: > > to: [EMAIL PROTECTED] > > Dear Sirs: > > My notebook (Dell C800 Latitude) has a built-in RAGE MOBILITY 128 AGP 4X > graphics card. > The chiptype is M4 AGP4X. The corresponding kernel module is the > r128.o which also enables DRI. The following setup works > perfectly fine --- including DRI: > > kernel 2.4.3 > XFree86_4.1.0 > r128.o from http://dri.sourceforge.net/ compiled in May > (it is necessary to replace the r128 module from the kernel > module compilation by the r128 of the DRI-project!!!) > > It would now be reasonable that one could use a working r128 module > with a newer kernel release. However, www.kernel.org is still > implementing an old r128 module --- they obviously don't know that their > > module is outdated. I just tried it with kernel release 2.4.6, > and the r128 module will not be loaded! : > [drm] failed to load kernel module "r128" > (II) R128(0): [drm] drmOpen failed > (EE) R128(0): [dri] DRIScreenInit failed. Disabling DRI. > > On the other hand, you can't replace the kernel module by the one > which is working so nicely with kernel 2.4.3 because, if you would do > so, > the module dependencies were not correct with kernel 2.4.6 > (try: /sbin/depmod and, of course, you will get > depmod: *** Unresolved symbols in > /lib/modules/2.4.6/kernel/drivers/char/drm/r128.o > and /sbin/modprobe will not load the module which was not compiled for > kernel 2.4.6). > > So I would like to ask the people from the DRI-project to make their > r128 > module available for the coming official kernel releases. Thank you! > > Sincerely yours, Thilo Kopp > > e-mail: [EMAIL PROTECTED] > > _______________________________________________ > Dri-devel mailing list > [EMAIL PROTECTED] > http://lists.sourceforge.net/lists/listinfo/dri-devel _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dri-devel
