On Mon, 20 Dec 2004 10:31:13 +0000, Christer Backstrom <[EMAIL PROTECTED]> wrote: > ----- Original Message ----- > From: "Roland Scheidegger" <[EMAIL PROTECTED]> > To: "Christer Backstrom" <[EMAIL PROTECTED]> > Subject: Re: IGP 340M textures? > Date: Mon, 20 Dec 2004 00:32:28 +0100 > > > > > Christer Backstrom wrote: > > > Here, the lappy hangs hard when trying any 3D application on > > > x.org-6.8.1, but while using XFree-4.4.0 I can get about 400fps > > > with glxgears. Trying anything more advanced gives (kfountain.kss > > > 3D screensaver): > > > > > > disabling TCL support > > > drmCommandWrite: -22 > > > drmRadeonCmdBuffer: -22 (exiting) > > > > > > on the console. Furthermore I get: > > I don't think the bugs with xfree-4.4 and xorg you're seeing are > > related at all. afaik XFree86 4.4 does not support dri with IGPs > > properly, so I wouldn't worry about that (I'd suspect the other > > notebook wouldn't work with XFree86 4.4 neither). > > OK, should have written XFree86-4.4.0 patched with IGP drm patch (bug 314) > > http://bugs.xfree86.org/show_bug.cgi?id=314 > > My bad. But the AMD lappy actually works fine with the 314 patch. > > > The dri driver has no separate code for igp 340/320/345 chipsets at > > all (except the pci ids), the 3d graphic core is 100% identical > > afaik (safe maybe from different clocks). > > Thats pretty much what I thought, but because the error message identified a > R100 chip, I still wondered if there was a bug somewhere. Perhaps the error > message should say "R100/RS200" instead. Whatever. > > > > > It looks to me like the lockups could be related to the dynamic > > clock code, though I'm no expert on that. This code is even asic > > revision dependant in some cases, so it's exactly the sort of issue > > you'd expect to show up with some igp but not another seemingly > > identical one. > > It should be fixed in xorg cvs and in xorg 6.8.2 branch. > > https://bugs.freedesktop.org/show_bug.cgi?id=1912 > > > > You're 100% right here. Sorry, I didn't get the connection there. I pathched > up 6.8.1 and recompiled. Works fine now. Thanks a bunch! Still only got > 400fps on glxgears, though, whereas I would have expected about 1000fps. On > another note: anyone know why atitvout stopped working when I upgraded to > x.org? >
There was code added to disable BIOS output toggling since the X server doesn't yet support acpi events so there's no way to validate modes for a new output device and the bios can potentially do things behind the driver's back. I added an option to xorg cvs to re-enable the old behavior, BIOSHotkeys. Alex > Cheers, > > /Chris > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
