RE: [Dri-devel] Re: Fixed binaries on SF
he using 20020625 snapshot from XFree86.0.log ... (II) RADEON(0): [drm] drmSetBusid failed (7, PCI:1:0:0), Permission denied (EE) RADEON(0): [dri] DRIScreenInit failed. Disabling DRI. ... Huh? Hi might try as root. If it works then something with per user file permissions or sticky bits is odd. other idea: for the odd case of legacy problems i would suspect that there is an API mismatch due to file inconsistency or the drm devices just do have the device file id. (there was a change in that area some time ago.) --- This sf.net email is sponsored by: Jabber Inc. Don't miss the IM event of the season | Special offer for OSDN members! JabberConf 2002, Aug. 20-22, Keystone, CO http://www.jabberconf.com/osdn ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] Re: Fixed binaries on SF
On Tue, Jun 25, 2002 at 12:06:36PM +0400, Konstantin Lepikhov wrote: Hi Jos?! Monday 24, at 10:16:51 PM you wrote: As some of you already noticed, fixed binaries - i.e, including libdri.a -, are now available on SF. When [and if] the binary compatability of libdri.a is restored, let me know and I'll restore the things as they were. José Fonseca Problem is gone away for voodoo3 (again :) DRI is working again after trivial compilation installation binaries. So whats happen? What's happened was that changes in libdri.a in the Radeon tcl-0-0-branch which were after included in the trunk broke compatability with previous versions of the library so drivers after this changes require an updated libdri.a. José Fonseca --- Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
