From: <ch...@ya...> - 2004-07-01 10:56:13
|
>On Wed, 30 Jun 2004 22:09:56 +0200 >Roland Scheidegger <a href=3D"javascript:sendMsg('<rsc...@hi...>');"><rsc...@hi...></a> wrote: >> <a href=3D"javascript:sendMsg('ch...@ya...');">ch...@ya...</a> wrote: >> > Hi!, >> > >> > I have a Debian SID runing on hp-compaq nx9010 laptop with ATI Radeon >> > Mobility IGP345M After a lots of tries to compile dri+drm+mesa I got >> > the errors attached in this mail. >> Hmm, no idea there. There were some very recent commits in that area >> I've not yet synced up to. >> >> > So, I've decide to install the common-20040629-linux.i386.tar.bz2 and >> > r200-20040629-linux.i386.tar.bz2 binary snapshots from >> > <a href=3D"/app/message?l=3Des&o=3D8&url=3Dhttp%3A%2F%2Fwww%2Efreedesktop%2Eorg%2F%7Edri%2Fsnapshots%2F" target=3D"_blank">http://www.freedesktop.org/~dri/snapshots/</a> >> > >> > After installation, I recompiled and install the radeon kernel module >> > with success, then I reload the module, reconfigure XF86Config-4 and >> > the thing seemt to work: Here's some kernel output: >> > >> > Linux agpgart interface v0.100 (c) Dave Jones agpgart: Detected Ati >> > IGP345M chipset agpgart: Maximum main memory to use for agp memory: >> > 149M agpgart: AGP aperture is 64M @ 0xd4000000 >> > >> > [drm] Initialized radeon 1.11.0 20020828 on minor 0: ATI Technologies >> > Inc Radeon IGP 340M <<< I have 345M, there's no difference? [drm] >> Probably not in the graphics core (though could be clocked differently). >> >> > Used old pci detect: framebuffer loaded agpgart: Found an AGP 2.0 >> > compliant device at 0000:00:00.0. agpgart: Putting AGP V2 device at >> > 0000:00:00.0 into 4x mode agpgart: Putting AGP V2 device at >> > 0000:01:05.0 into 4x mode >> > >> > However, after enter the X and run some 3d apps to test the 3d >> > acceleration (Blender, Tuxracer, glxgears), the systems hangs >> > (Blender in concrete, stills with his grey background however I can >> > move the mouse). Then I run glxinfo to assure that DRI is working and >> > got this message: >> > >> > name of display: :0.0 unknown chip id, assuming full radeon support >> > display: :0 screen: 0 direct rendering: Yes .....and lots of >> > output.... >> That's not good (your chip will certainly crash when the driver assumes >> full support, as it doesn't have a TCL unit). What's the pci id of the >> chip (lspci -v)? >If it doesn't have a TCL unit then it's probably R100-based (I guess, >don't know much about IGPs). So you need the radeon snapshot, not r200. Yes, the right snapshot was Radeon :) A last question, I have problems in Blender: the app doesn't draw correctly some buttons. However, I try other 3d programs (like amoeba demo) to test the acceleration and the draw was correct. My question is: is due to DRI the blender button-draw problem or could be a Blender bug? Thanks everybody for your help Chronoh >> >> Roland >> >Felix >| Felix K=FChling <a href=3D"javascript:sendMsg('<fx...@gm...>');"><fx...@gm...></a> <a href=3D"/app/message?l=3Des&o=3D8&url=3Dhttp%3A%2F%2Ffxk%2Ede%2Evu" target=3D"_blank">http://fxk.de.vu</a> | >| PGP Fingerprint: 6A3C 9566 5B30 DDED 73C3 B152 151C 5CC1 D888 E595 | >------------------------------------------------------- >This SF.Net email sponsored by Black Hat Briefings & Training. >Attend Black Hat Briefings & Training, Las Vegas July 24-29 - >digital self defense, top technical experts, no vendor pitches, >unmatched networking opportunities. Visit www.blackhat.com >-- >_______________________________________________ >Dri-users mailing list ><a href=3D"javascript:sendMsg('Dri...@li... >https://lists.sourceforge.net/lists/listinfo/dri-users');">Dri...@li... >https://lists.sourceforge.net/lists/listinfo/dri-users</a> |