CC'ing dri-devel... Ian any ideas on the texture bugs?
Alex On Wed, 6 Oct 2004 23:14:10 +0200, Jörg Walter <[EMAIL PROTECTED]> wrote: > On Wed, Oct 06, 2004 at 10:05:38PM +0200, J?rg Walter wrote: > > On Wed, Oct 06, 2004 at 08:49:55AM -0400, Alex Deucher wrote: > > > On Wed, 6 Oct 2004 01:43:05 +0200, Jörg Walter > > > <[EMAIL PROTECTED]> wrote: > > > > [ This is forwarded from unichrome-users, they pointed me here. ] > > > > > > > > Hi! > > > > > > > > I've got a problem using the unichrome driver. > > > > > > > > The system is a VIA Epia M-10000 (Nehemiah) board and serves mainly as my > > > > mythtv box. I was able to get latest mythtv running with libviaXvMC > > > > acceleration (input is a PVR-250), xine plays using the (now removed) > > > > xine-plugin, the box works better than ever before. I'm using latest > > > > Xorg as X server, Gentoo as distribution, latest $everything as of 2 weeks > > > > ago. > > > > > > > > > > Ian just fixed some bugs in the unichrome driver earlier this week and > > > last week. you might want to try a later snapshot: > > > http://freedesktop.org/~fxkuehl/snapshots/ > > > or rebuild from mesa/xorg cvs. > > > > Yes, that did it! Recompiling Xorg & Mesa made the first problem disapear, > > loading the latest drm module made the second problem disappear. > > > > Alas, not all is well: Now I have a bad texture bug. "Water" is showing up > > as bright white area instead of the usual blueish animated and glowing > > texture, same with toxic waste and lava), but I'll first try some > > combinations of old libs/driver with new drm module. > > Before, those areas were showing up okayish, with the occasional white > > flicker. Now it's opposite: white, with the occasional dark flicker. > > Oh well, looks like it didn't work. The crashes described in my original > post still occur, only less often. I've found out a bit more about the > texture problem, however: doomsday darkens the edges of most surfaces, using > the white texture and blending it with the original texture. That works > fine, except for water. Also, the crashes only occur when water is visible, > and when the engine lags for a moment due to new objects/textures entering > the view. > > Attaching gdb to the crashed process, I get the following position of the > endless loop (also see original post): > > flush_agp (vmesa=0x8ce4850, agpCmd=0xbfffcc70) at via_ioctl.c:1546 > 1546 if ((nStatus & 0xFFFEFFFF) == 0x00020000) > > (gdb) p/x nStatus > $2 = 0x30005 > > (The second thread is the sound thread which plays along happily, the third > thread seems to be the SDL audio helper thread, I have no idea what the > fourth thread does - could also be SDL internal.) > > Hope this is of some use, tell me if I should examine something else. > > > > -- > CU > Joerg ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
