Also, to answer a previous question, the r300 GL demo looks great, but the triangle demo does not. It comes out shifted and with some garbage. However, the triangles are visible.
-------- Original Message -------- Subject: r300 Report. Date: Sun, 31 Oct 2004 00:15:19 -0400 From: Pat Suwalski <[EMAIL PROTECTED]> To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Hello,
I just spent the evening fiddling with the two r300 patches from r300.sf.net.
This eMail is a summary of my experiences, and I am willing to pursue the issues and keep trying.
I am running the following system: - AMD 64 fx-51 - Radeon 9800XT - Kernel 2.6.9 - X.org 6.8.0
Initially, I was having a good deal of trouble getting it going. X would start, but as soon as any program would try to connect to the X server, the screen would go blank, but the computer was still in a responsive state. However, the X server was in state "R", and was not killable. I later discovered these dmesg messages (AGP basically killed itself):
[drm] Initialized radeon 1.11.0 20020828 on minor 0: agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0. agpgart: Badness. Don't know which AGP mode to set. [cmd:1f000a0a tmp:1f000a1a fell back to:- cmd:1f000a08 tmp:1f000a1a] agpgart: Bridge couldn't do AGP x4. agpgart: Graphic card couldn't do AGP x4. agpgart: Badness. Don't know which AGP mode to set. [cmd:1f000a08 tmp:ff00021b fell back to:- cmd:1f000208 tmp:ff00021b] agpgart: Bridge couldn't do AGP x4. agpgart: Putting AGP V3 device at 0000:00:00.0 into 0x mode agpgart: Putting AGP V3 device at 0000:01:00.0 into 0x mode [drm] Loading R300 Microcode
However, as you can see, the dri patch worked.
The problem was that the gart can't seem to handle AGP8x, so I reduced it to 4x in the BIOS. At that point, the X server started working properly:
[drm] Initialized radeon 1.11.0 20020828 on minor 0: agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0. agpgart: Putting AGP V3 device at 0000:00:00.0 into 4x mode agpgart: Putting AGP V3 device at 0000:01:00.0 into 4x mode [drm] Loading R300 Microcode
If anyone has any insight into the 8x issue, please let me know.
The X server confirmed success:
(...) (II) RADEON(0): [drm] Added 32 65536 byte vertex/indirect buffers (II) RADEON(0): [drm] Mapped 32 vertex/indirect buffers (II) RADEON(0): [drm] dma control initialized, using IRQ 169 (II) RADEON(0): [drm] Initialized kernel GART heap manager, 5111808 (II) RADEON(0): Direct rendering enabled (...)
However, glxinfo tells me: "direct rendering: No". The r300_demo confirms this by crapping out, suggesting the BusID is wrong, which it is not.
One way or another, the PCI id of my card is 1002:4e48, and it seems to have no negative effects on the hardware, so it might as well be added to the list of pci id's.
If anyone has any insight into what's up with all of this, I'm all ears. Again, I'll help out as much as I can. Thanks.
--Pat
------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
