On Mon, 2003-10-20 at 12:01, [EMAIL PROTECTED] wrote: > Gilad Ben-Yossef wrote: > > > I don't like to give consultation on non free software, but I'll try to help > > Thanks. > > What are other options if I want to get the most out of my hardware? > I did a lot of googling over the last month since I bought this > hardware and am still confused. If I get it right then there is some > effort to write an open driver for ATI but it's not complete, and that > the 2.6 kernel is supposed to include better built-in support for DRI, > am I right? >
There is the dri cvs tree which has support for Radeon up to 9000 or 9200 iirc and drivers from ATI. both work, I don't know the comparisons. The kernel modules on 2.4 are for X 4.2, for X 4.3 you need to download the drivers from dri cvs (don't know what ati provides). mach64 doesn't have built in support, you need the cvs version. I think that the 2.6 ac kernels have mach64 don't think the regular ones have. > > anyway - is the fglrx kernel module loaded? what does "dmesg" say when you > > try to load it if you do? > > Dmesg: > ----------------------------------------------------------------------- > [fglrx] Maximum main memory to use for locked dma buffers: 430 MBytes. > [fglrx:firegl_stub_register] *ERROR* Fire GL kernel module has to be > loaded prior to any other DRM kernel module! > ----------------------------------------------------------------------- > I tried to reboot to single user (real reboot, not "down from > multiuser") and force load of this module from there, but still get the > same message. > > The "modprobe -v fglrx" says: > ----------------------------------------------------------------------- > /sbin/insmod /lib/modules/2.4.22-dri/misc/fglrx.o > Using /lib/modules/2.4.22-dri/misc/fglrx.o > Symbol version prefix '' > Warning: loading /lib/modules/2.4.22-dri/misc/fglrx.o will taint the > kernel: non-GPL license - Proprietary. (C) 2002 - ATI Technologies, > Starnberg, GERMANY > See http://www.tux.org/lkml/#export-tainted for information about > tainted modules > /lib/modules/2.4.22-dri/misc/fglrx.o: init_module: Operation not permitted > Hint: insmod errors can be caused by incorrect module parameters, > including invalid IO or IRQ parameters. > You may find more information in syslog or the output from dmesg > /lib/modules/2.4.22-dri/misc/fglrx.o: insmod > /lib/modules/2.4.22-dri/misc/fglrx.o failed > /lib/modules/2.4.22-dri/misc/fglrx.o: insmod fglrx failed > ----------------------------------------------------------------------- > > Thanks, > > --Amos > > > > ================================================================= > To unsubscribe, send mail to [EMAIL PROTECTED] with > the word "unsubscribe" in the message body, e.g., run the command > echo unsubscribe | mail [EMAIL PROTECTED] -- Micha Feigin [EMAIL PROTECTED] ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
