On Fri, Oct 15, 2004 at 09:47:29 -0400, Vladimir Dergachev wrote:
> >>>>Try using DRI CVS, module drm. Do a fresh checkout, just in case.
> >>>
> >>>Yes, I used the CVS from r300.sf.net. Thanks for the hint.
> >>
> >>Still no luck.
> >>
> >>grep "4150" drm_pciids.h
> >> {0x1002, 0x4150, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R300}, \
> >>
> >>After modprobe:
> >>
> >>ACPI: PCI interrupt 0000:02:00.0[A] -> GSI 19 (level, high) -> IRQ 19
> >>[drm] Initialized radeon 1.12.0 20020828 on minor 0: ATI Technologies Inc
> >>RV350 AP [Radeon 9600]
> >
> >Just to be sure: will the microcode only be loaded if the device will
> >be used, e.g. by the X.org driver? Until now I just load the module and
>
> Yes. In fact DRM driver needs Xserver to tell it which microcode to load.
OK, now I got it:
agpgart: Putting AGP V3 device at 0000:02:00.0 into 8x mode
[drm] Loading R300 Microcode
I grabbed the Mesa source, applied the mesa.patch, compiled the
r300_dri.so driver and copied it to the X.org dri drivers directory,
but strace glxinfo shows that only the r200_dri.so driver will be used.
What I am missing?
Regards,
Tino
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
--
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
