Broken mesa build.

Following the instructions on dri.sourceforge.net and stupidly expecting them to work, I got this error from Mesa: (I've highlighted the line I think is causing it to fail.) ../../../../../src/mesa/tnl_dd/t_dd_tritmp.h:405: warning: 'spec[0]' may be used uninitialized in this function

R200 CVS crashes

When I run the CVS R200 kernel modules, many megabytes of synchronization errors appear in xorg.log and it still crashes when I run any GL app, including glxinfo. It doesn't matter what version of Mesa I'm running, it should be impossible to crash the kernel like this. =\ -- If you tell a linux

dmesg dump from mach 64 driver

[drm] Initialized drm 1.1.0 20060810 [drm] Initialized mach64 2.0.0 20060718 on minor 0: [drm] Used old pci detect: framebuffer loaded [drm:mach64_dma_init] *ERROR* mach64_dma_init called without lock held, held 0 owner f72941c0 [drm:drm_unlock] *ERROR* Process 5048 using kernel context

BeOS build error, Mesa 6.3

I tried to build Mesa on BeOS and this is a summary of the errors... Apparently the beos port is quite stale... errors Description: Binary data BeOS Attributes Description: application/be_attribute

normal arrays and color arrays.

I'm not sure if this is on topic, but I figured out how to parameterize GL so that it can emulate the N64's lighting unit (using vertex arrays). While that seemed to work well enough, I noticed that in doing so, the system was nolonger processing the color array! Is this normal behavior? What do I

CVS changelog?

I've noticed a stream of updates for both the drm and Mesa trees. Because it takes a certain ammount of effort to test a build of these trees, I was wondering if there was a changelog I might use to help me determine wheather a recient change in the source might address the issues I'm dealing

Re: R280 texture pipe bug still there [PATCH]

Daniel Stone wrote: On Thu, 2005-08-25 at 00:44 -0500, Alan Grimes wrote: ^^^ Just install libdrm from DRM CVS. It's a requirement now. IN FILE xf86drm.h AND include/GL/internal/dri_interface.h CHANGE #include drm.h #include drm/drm.h All that does is paper over the cracks

Info dumps on my Mach64:

[ this is the card that crashes when I try to do anything 3D with it.] ### :02:07.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro 215GP (rev 5c) ### (II) ATI(1): VESA BIOS detected (II) ATI(1): VESA VBE Version 2.0 (II) ATI(1): VESA VBE Total Mem: 8192 kB (II) ATI(1):

Re: R280 texture pipe bug still there

I think this should be fixed in CVS, though I couldn't test due to libGL issues. Could you test and see if it works now? I just tried a build and got this error: [EMAIL PROTECTED] ~/source/Mesa $ make linux-dri-x86 (cd configs rm -f current ln -s linux-dri-x86 current) make default

Re: R280 texture pipe bug still there [PATCH]

^^^ Just install libdrm from DRM CVS. It's a requirement now. IN FILE xf86drm.h AND include/GL/internal/dri_interface.h CHANGE #include drm.h #include drm/drm.h -- Friends don't let friends use GCC 3.4.4 GCC 3.3.6 produces code that's twice as fast on x86! Non-sequiter item:

Re: R280 TEST RESULTS;

PPRACER: Works but has nasty texture bug affecting the ground textures.. (Problem disappears when I run it on the other, unaccelerated monitor..) n64 emulator: Par behavior (sucks due to my lack of coding skill...) flightgear: Works, no obvious problems. Celestia: Works, no obvious problems

Mach 64 DRM total ice-up.

Because I need to get Croquet working. And because it crashes after 3 seconds on 6.2.1, and because it doesn't work at all with the CVS sources... the CVS sources can't even do ppracer (a tuxracer derivative) right, I decided to ignore the fact that I just invested $40 in a video card with a

PCI, AGP, PCI-E

The few sources I've read have said that the hardware for AGP, and PCI-E was designed to emulate the software interface of PCI so that the underlying hardware would be transparent to software. This can be seen in the output of lspci, where my marginally supported R200 (Where's 6.2.2 when you need

R280 texture pipe bug still there

I installed the latest CVS DRM source a few days ago. (the kernel modules), and it is still broken! =( Maybe if someone could point me in the general vicinity of the culprit, I could take a whack at it myself... [EMAIL PROTECTED] ~/Croquet0.3 $ squeak DRM_RADEON_TEXTURE: return = -11

GRONK???

[notice the path names and nearly identical files] So what's the story here? [EMAIL PROTECTED] ~/source/drm/libdrm $ ls -l * -rw-r--r-- 1 atg users 2866 Jul 12 19:13 Makefile.am -rw-r--r-- 1 atg users 19978 Aug 6 20:22 Makefile.in -rw-r--r-- 1 atg users 1454 Aug 8 11:38 config.h.in

Update on R200/Squeak/croquet crash

I changed bit depths from 16-bit to 32-bit and the crash disappeared... This made me extremely happy for all of about two seconds, During that time I ordered the thing to go fullscreen and it gave me this error: I don't know exactly where these errors are coming from (UNIX IS EVIL) but here they

OGL compliance, and DRI interface...

I've been hacking on my version of the N64 emulator again and I noticed I was getting an invalid value error from the texImage2D command... I assumed that it was because it required textures to be a power of two in size... Then I checked the GL spec and the only mention I found was that for cube

R200 update

I'm still having trouble with my R200... This is a variant of Croquet 0.1, the heavy demo gallery. loads but there are some shading and texture glitches... Otherwise it's quite fast compared to my R128... http://www.citris-uc.org/hosted/projects/ith/gallery/downloads.html The Croquet mainline

AAAARRRGH!!!

I spent all day dl'ing and installing: # This is a pre-release version of the The X.Org Foundation X11. X Window System Version 6.8.99.1 # And my reward for spending $40 on a card that appeared to be supported by Linux? ### [EMAIL PROTECTED] ~/Croquet0.3 $ ppracer

I need the R200 to work!

Hello, I need my ATI R9250 based board to work because I need it for RD work. -- possibly even remunitive RD work =\ I managed to get the Mesa CVS sources to work but it caused my critical application ( www.croquetproject.org ) to hang... (run it with unix Squeak VM 3.7-7 from www.squeak.org

MSI RX9250-T128

Hey, I just installed the card mentioned in the subject line hoping to be able to get better performance with OpenCroquet than I could with my R128... I open it up and it crashes and locks the screen... Using a second computer to de-lock the console, I was able to recover this message from GDB: