Content-Type: multipart/alternative; boundary="------------030503030903030100020807" --------------030503030903030100020807 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by mailg.telia.com id g5QNtGZ00806 > Peter, Colin, I've just commited the necessary changes. They won't fix = the > problem, but they will [hopefully] help to better determine what's=20 > causing them. > > You know the drill: get those /proc/kmsg ! > It is included as usual. Dri locks the system when running glxgears just after it has drawn the=20 first frame. (I am not sure about it but i think it also may have caused=20 a kernel crash as the top "pixels" in the display might have been a=20 distorted I also checked out the textures when running prboom (doom=20 clone) and they also look the same as before (i belive i sent you a=20 screenshot), eg the colors are all wrong. The strange thing is that the=20 game seems playable so i dumped a kmsg out of that one too. I also tried to make a installable binary by cloning the=20 "i810-20020626-linux.i386.tar.bz2" file from the dri webpage (as i=20 promised yesterday) but i didn=B4t get it to work properly (not very=20 surprising). My guess is that the kernel modules doesn=B4t get compiled=20 when i am running the installation script. It was based on the=20 2002-04-29 version of the mach64-0-0-4-branch which works great. It=20 still has the errors in the textures (the jagged edges i bugged you=20 about before (i think you said before that it was caused by big-endian=20 byteswapping)) but other than that it works great. If you are interested=20 in making it your selves i have all the requred files on my computer. Regards Peter --------------030503030903030100020807 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit
Peter, Colin, I've just commited the necessary changes. They won't fix theIt is included as usual.
problem, but they will [hopefully] help to better determine what's causing them.
You know the drill: get those /proc/kmsg !