On 2002.04.30 09:38 Sergey V. Udaltsov wrote: > > From this moment the mach64 binary snapshots in > > http://dri.sourceforge.net/snapshots/bleeding-edge/ are taken from the > > 0-0-4 branch. > Thanks. Just tried. Well, it seems 0-0-4 has long way to go:) > First, I just run "install.sh" and restarted X. I got segmentation fault > on glxinfo - after displaying most (or all?) of the info in xterm. Then > glxgears just did not want to start - some drmMach64Clean... (sorry, I > forget to write it down) returned -22. What could this be? > > Well, then I wanted to stop X and switched to vconsole 1 - and the whole > display froze (but not the whole system!) - so I managed to reboot > correctly. >
It seems that the mach64 kernel moduled wasn't replaced from memory, causing a kernel oops. Usually you need to run install.sh without X running (I usually do init 3). > After this point, I managed to run X and even run glxgears and glxinfo > without problems (though glxgears gives 268fps vs 286 in 0-0-3 - anyway, There shouldn't be much difference since DMA is off. (DMA at this time even slows things more) > better than 191 in Mesa). Anyway, X is still unable to shut down > gracefully - at "killall X" in xterm I get frozen screen (though > Ctl-Alt-Del works as if I were in console). mmm.. I don't see what it could be. > > In XFree86.0.log DRM is reported "on" (glxinfo has same idea). > > Well, later I will play more... As said, there could be some problems with the install.sh not replacing everything properly. That's the more likely. > > BTW, is there any way to check whether DMA is on or off? Can I see it in > /proc/dma? No. There isn't any yet. But we can arrange to something be printed on the system log when the DMA is enabled on runtime. > > Thanks for your efforts, > > Lazy tester Sergey > :) Jos� Fonseca _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
