On Don, 2002-11-07 at 22:11, Manuel Bilderbeek wrote: > Michel Dänzer wrote: > > goemon:/usr/src# dpkg -i > drm-trunk-module-2.4.19-k7_10.00.Custom+2002.10.02-1_i386.deb > (Reading database ... 88700 files and directories currently installed.) > Unpacking drm-trunk-module-2.4.19-k7 (from > drm-trunk-module-2.4.19-k7_10.00.Custom+2002.10.02-1_i386.deb) ... > dpkg: error processing > drm-trunk-module-2.4.19-k7_10.00.Custom+2002.10.02-1_i386.deb (--install): > trying to overwrite > `/lib/modules/2.4.19-k7/kernel/drivers/char/drm/tdfx.o', which is also > in package kernel-image-2.4.19-k7
kernel-image-2.4.19-k7 also contains some DRM modules, use --force-overwrite . > > D'oh, I meant Option "SWcursor" of course. The device section is the > > right place. > > YES! This solves the problem! > So, what could be the cause of the problem and what is the disadvantage > of the SWcursor? (I guess it's slower in some way...) HW cursor is better for various reasons. I've never heard of such a problem before. You may want to report it to the Xpert list. > I never knew this was a valid option for the Driver. Is there a list of > options somewhere? In the source. :) Other drivers have manpages, the radeon driver not yet unfortunately. Someone posted a draft to the Xpert list a while ago, would be nice if that would make it into 4.3.0 . -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast
