Thank you for the advice. The problem I had before with the DRM modules (drm.ko and radeon.ko) from the r300 CVS was that drm.ko would load fine but loading radeon.ko was causing my computer to lock up after a kernel panic. I had tried it rebuilding both it and the kernel several times without success. However, last night I went back to a 2.6.10 kernel and was able to get things working; I unpacked the vanilla kernel sources, compiled the kerne and rebooted, then compiled and successfully loaded the right DRM modules. :D
glxgears runs at about 200fps without DRI, and 600-700fps with DRI (though the gears appear to turn rather slowly with DRI enabled). I also get 30 to 60 fps running Scorched3D at 800x600 with the options "Don't draw water", "No multi texture", "No combined textures", and "No VBO" (vertex buffer objects) checked--unchecking any of the last three causes the game to die when starting the first round, otherwise the game is playable. I'll be sure to test out the new DRM code tonight or tomorrow. - Brian --- Vladimir Dergachev <[EMAIL PROTECTED]> wrote: > > > On Tue, 1 Mar 2005 [EMAIL PROTECTED] wrote: > > > Hi, > > > > I'm new to DRI development but am interested in helping with the > r300 > > driver. I am trying to get the driver working with my Radeon 9550 > and > > I have glxinfo reporting that direct rendering is enabled and the > > OpenGL renderer string is "Mesa DRI R300 20040924 AGP 4x > > x86/MMX+/3DNow!+/SSE NO-TCL", but glxgears exits almost immediately > > with the last message it prints out being "drmRadeonCmdBuffer: -22 > > (exiting)". I am running a 2.6.11-rc5 kernel using the DRM modules > > that come with it (I can't get the DRM modules from CVS to load > with a > > 2.6.10 kernel), the latest Xorg, Mesa, and r300_driver sources from > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > You need the right DRM module. I am running 2.6.10 as well and there > were > no compilation problems. Make sure to cd into linux-core and type > make > there. > > best > > Vladimir Dergachev > > > anonymous CVS as of about 11am today (2005-03-01). Everything has > been > > compiled against glibc 2.3.4 using gcc 3.4.3. I'm not using > merged-fb > > nor is the kernel radeon framebuffer module loaded. The error is > > identical regardless of whether I have immediate mode or VB mode > > enabled (I don't think it is making it that far in the driver code > > before exiting...). I have attached the output from glxgears with > > LIBGL_DEBU=verbose and RADEON_DEBUG=all. Any ideas, or advice for > > debugging this problem? > > > > - Brian > > > > __________________________________________________ > > Do You Yahoo!? > > Tired of spam? Yahoo! Mail has the best spam protection around > > http://mail.yahoo.com > > > ------------------------------------------------------- > 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 > [email protected] > https://lists.sourceforge.net/lists/listinfo/dri-devel > __________________________________ Celebrate Yahoo!'s 10th Birthday! Yahoo! Netrospective: 100 Moments of the Web http://birthday.yahoo.com/netrospective/ ------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/dri-devel
