On Wednesday 16 March 2005 08:46 am, Jerome Glisse wrote: > On Tue, 15 Mar 2005 18:36:21 -0500, Jung-uk Kim <[EMAIL PROTECTED]> wrote: > > On Tuesday 15 March 2005 05:06 pm, Aapo Tahkola wrote: > > > > After reading all the promising success stories about the > > > > r300 project, I am > > > > wondering whether anybody successfully tried it on a *BSD. > > > > Some time ago I tried on DragonFly BSD and in Xorg.0.log I > > > > found a message that DRI was enabled, but glxinfo said > > > > "direct rendering: No". > > > > > > DRMs BSD support was added blindfold without any testing so it > > > might not work as expected. > > > You might want to check out steps after Xorg says DRI is > > > enabled from http://dri.freedesktop.org/wiki/DriTroubleshooting > > > . > > > > I have sort of working drm but I always get this from drm when I > > run glxinfo or glxgears: > > > > drm0: <ATI Radeon RV300 Mobility 9600 M10> port 0x2000-0x20ff mem > > 0xd0100000-0xd010ffff,0xd8000000-0xdfffffff irq 16 at device 0.0 > > on pci1 info: [drm] AGP at 0xe0000000 256MB > > info: [drm] Initialized radeon 1.15.0 20050208 on minor 0 > > info: [drm] Loading R300 Microcode > > error: [drm:pid12690:r300_do_cp_cmdbuf] *ERROR* bad cmd_type 255 > > at 0xffffff0000baf800 > > > > and > > > > Using 8 maximum texture units.. > > sizeof(drm_r300_cmd_header_t)=4 > > sizeof(drm_radeon_cmd_buffer_t)=32 > > Allocating 284420 bytes command buffer (max state is 11140 bytes) > > *********************************WARN_ONCE*********************** > >********** File r300_state.c function r300Enable line 516 > > Don't know how to enable polygon offset point/line. Help me ! > > ***************************************************************** > >********** drmRadeonCmdBuffer: -22 (exiting) > > > > Any idea? BTW, it's FreeBSD/amd64 6-CURRENT with today's r300. > > > > Thanks, > > > > Jung-uk Kim > > Did you get lastest Xorg CVS, this likely due to the fact > that you got a too old Xorg.
I rebuilt Xorg from CVS. It's actually ran glxgears this time! However in few seconds it just locked up OS (i. e., infinitely looping syscalls -> 100% CPU load). Another interesting thing is the gears are twice bigger than normal size and it looks interlaced. r300_demo shows the same symptom. Any thought? Thanks! Jung-uk Kim > Jerome Glisse ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
