> After looking at the source, support for multiple cards is only enabled > in the tdfx DRM yet. The attached hack might serve as a quick'n'dirty > way to find out the next problem. :)
I added in the #define from the patch. When I insmod, it now sees both cards. I get something like: [drm] Initialized radeon 1.6.0 20020828 on minor 0 [drm] Initialized radeon 1.6.0 20020828 on minor 1 ( Here's "the next problem" :) ) X, however, doesnt work. I get 1 blank screen and one with crazy lines zipping around. both cards are seen by X now: (II) RADEON(0): [drm] created "radeon" driver at busid "PCI:0:9:0" ... (II) RADEON(1): [drm] created "radeon" driver at busid "PCI:0:13:0" ... but then I get (II) RADEON(1): X context handle = 0x00000001 (II) RADEON(1): [drm] installed DRM signal handler (II) RADEON(1): [DRI] installation complete (II) RADEON(1): [drm] Added 32 65536 byte vertex/indirect buffers (II) RADEON(1): [drm] Mapped 32 vertex/indirect buffers (EE) RADEON(1): RADEONDRICPInit: CP start -1007 (EE) RADEON(1): RADEONCPGetBuffer: CP GetBuffer -1007 (EE) RADEON(1): GetBuffer timed out, resetting engine... (EE) RADEON(1): RADEONCPGetBuffer: CP reset -1007 (EE) RADEON(1): RADEONCPGetBuffer: CP start -1007 (EE) RADEON(1): RADEONCPGetBuffer: CP GetBuffer -1007 (EE) RADEON(1): GetBuffer timed out, resetting engine... (EE) RADEON(1): RADEONCPGetBuffer: CP reset -1007 (EE) RADEON(1): RADEONCPGetBuffer: CP start -1007 (EE) RADEON(1): RADEONCPGetBuffer: CP GetBuffer -1007 (EE) RADEON(1): GetBuffer timed out, resetting engine... and so on. The full log is at http://www.eyetap.org/~fungja/radeon/XFree86.0.log.dualradeon -James ------------------------------------------------------- This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
