-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday 04 June 2004 12:22, Michel DÃnzer wrote: > > Currently, if you set the gart size manually higher than what's possible > > (set in bios), dri will just get disabled due to missing agp support, > > which I consider bad behaviour, and that you get a useless error message > > in that case doesn't help neither. > > (II) RADEON(0): [agp] 262144 kB allocated with handle 0x00000001 > > (EE) RADEON(0): [agp] Could not bind > > (EE) RADEON(0): [agp] AGP failed to initialize. Disabling the DRI. > > (II) RADEON(0): [agp] You may want to make sure the agpgart kernel > > module is loaded before the radeon kernel module. > > IMHO only the 'Could not bind' error could use some clarification, > otherwise I find this the only sane way to deal with an impossible > configuration.
Would it be possible to do an automatic fallback to the largest allowed gart size, along with an appropriate warning/error message? Tell me to shut up if it's not possible to query the maximum size ;) cu, Nicolai -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAwFrssxPozBga0lwRAqn6AKDX6knsbuksaX3KoAC/A5kG852mbQCgzpxv 9wEb+fLrX40yADNIfAZeCww= =kgbs -----END PGP SIGNATURE----- ------------------------------------------------------- This SF.Net email is sponsored by the new InstallShield X. >From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
