On Tuesday, March 8, 2005 12:01 am, Vladimir Dergachev wrote: > Hi Jesse ! > > On Mon, 7 Mar 2005, Jesse Barnes wrote: > > Ok, so I've applied Stephane's fixes and sample_server comes up and > > miniglxtest no longer segfaults. However, after setting the mode, > > sample_server seems to die and wedge my display. miniglxtest just fails > > right away with this message: > > > > [EMAIL PROTECTED] miniglx]$ ./miniglxtest > > [miniglx] probed chipset 0x4e4b > > CreateNotify > > Authorize - magic 1 > > Unknown device ID 4E4B, please report. Assuming plain R300. > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > This is a bit odd - if the r300 driver does not know about the device why > does the DRM driver load ? > > Also, are you using the drm driver from r300.sf.net ? The message > below (error -22) might be indicative of wrong drm driver, try to insmod > it with explicit path, like this: > > insmod ./drm.ko > insmod ./radeon.ko
Yeah, I'm using that driver and it seems to work ok with recent X.org bits (modulo some tiling issues that I saw--though sroland said that was to be expected on the particular tree I'm running). I'm updating my X tree now to see if that goes away. As for the solo stuff, Stephane suggested that I might have to port some of the X DDX bits to the solo driver code (mostly 2d & setup stuff I guess?), could that explain what I'm seeing? Thanks, Jesse ------------------------------------------------------- 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
