hi rick, i got it! thanks so much for your help! it works now!
xv seems to pick up on the first card defined in XF86Config. so i just had to switch the order of the card listings in the config file, and now xvinfo shows info on the ATI card, not the Matrox. thanks again! joe Rick Scott wrote: >You understand I'm not an expert in this, right :) > >Yes, I have a 5446 agp, but it is the only card I have in this box. xvinfo >certainly doesn't show the ATI overlay port. I would need to see the >XFree86.?.log to have any clues, and even then I can't be sure :) r128 is >loaded, I compiled agpgart in, kernel is 2.4.4. I don't think the drm is a big >deal at this point. It looks like you have 2 heads on the matrox card, do all 3 >monitors work as expected, or at least work? > >If you send a log, you could take out the traces of the R128BlockHandler, I >need to take that trace out of the source :) > >On 18-Oct-01 at 19:26, Joseph Cheek ([EMAIL PROTECTED]) wrote: > >>thank you rick! it compiles [which if further than i had gotten before]! >>but it doesn't work 8-( >> >>xvinfo only shows the matrox card. you have a 5446, right? agp or pci? >>would you mind passing along your XF86Config-4? do you have r128 [and >>agpgart, if agp] loaded? >> >>i also don't get any more drm errors, but i still get: >> >>(II) R128(2): Direct rendering disabled >> >>here's the xvinfo output: >> >>any clues? >> >>thanks! >> >>joe >> >>X-Video Extension version 2.2 >>screen #0 >> Adaptor #0: "Matrox G-Series Backend Scaler" >> number of ports: 1 >> port base: 55 >> operations supported: PutImage >> supported visuals: >> depth 16, visualID 0x23 >> depth 16, visualID 0x24 >> depth 16, visualID 0x25 >> depth 16, visualID 0x26 >> number of attributes: 3 >> "XV_COLORKEY" (range 0 to 16777215) >> client settable attribute >> client gettable attribute (current value is 2110) >> "XV_BRIGHTNESS" (range -128 to 127) >> client settable attribute >> client gettable attribute (current value is 0) >> "XV_CONTRAST" (range 0 to 255) >> client settable attribute >> client gettable attribute (current value is 128) >> maximum XvImage size: 1024 x 1024 >> Number of image formats: 4 >> id: 0x32595559 (YUY2) >> guid: 59555932-0000-0010-8000-00aa00389b71 >> bits per pixel: 16 >> number of planes: 1 >> type: YUV (packed) >> id: 0x32315659 (YV12) >> guid: 59563132-0000-0010-8000-00aa00389b71 >> bits per pixel: 12 >> number of planes: 3 >> type: YUV (planar) >> id: 0x30323449 (I420) >> guid: 49343230-0000-0010-8000-00aa00389b71 >> bits per pixel: 12 >> number of planes: 3 >> type: YUV (planar) >> id: 0x59565955 (UYVY) >> guid: 55595659-0000-0010-8000-00aa00389b71 >> bits per pixel: 16 >> number of planes: 1 >> type: YUV (packed) >> >>On Thu, 18 Oct 2001, Rick Scott wrote: >> >>>On 18-Oct-01 at 16:43, Joseph Cheek ([EMAIL PROTECTED]) wrote: >>> >>>>i'd love to have it if the list doesn't want it. i still can't get drm >>>> on the ATI card, or tv in. >>>> >>>I'm not sure whether I do or not, what with dri, drm, and all the other >>>things, I'm not real sure how they all fit together. >>> >>> >>>>one thing i am unclear about: how does the ati.2 unified driver drive >>>>/dev/video? i am used to having to load a module, say "modprobe bttv", >>>> and then running xawtv. how does it work now? >>>> >>>There ain't no /dev/video. The TV image is retrieved with the Xv >>>extension (there's another one :). You can use xvinfo to figure out if >>>it's available. xawtv, or better yet motv, knows how to deal with this if >>>it is configured with the --enable-xvideo option. >>> >>>The diff is from the current devel branch. You need to have pulled from >>>the linuxvideo cvs with: >>> >>>cvs co -r devel >>> >>>for the diff to patch. With this patch, console switches work, and >>>everything else I have tried so far.... For me at least :) >>> >>>>joe >>>> >>>>Rick Scott wrote: >>>> >>>>>I could post a diff from the linuxvideo devel branch if anyone is >>>>>interested. It weighs in around 16K. >>>>> >>>>>On 18-Oct-01 at 16:08, Joseph Cheek ([EMAIL PROTECTED]) wrote: >>>>> >>>>>>thanks mike! i've now got past this and have compared the gatos >>>>>>4.1.0 source with current cvs source. it appears that most of the >>>>>>functionality in their patches has been moved to XFree86 HEAD. >>>>>> >>>>>>while using HEAD, r128 drm gives these errors: >>>>>> >>>>>>(II) R128(2): Direct rendering disabled >>>>>>Symbol drmFreeBufs from module >>>>>>/usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved! >>>>>>Symbol drmR128TextureBlit from module >>>>>>/usr/X11R6/lib/modules/drivers/r128_drv.o >>>>>>is unresolved! >>>>>>Symbol drmFreeBufs from module >>>>>>/usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved! >>>>>> >>>>>>i do get a display now, but i'm examining every possibility while i >>>>>>try to get the tv tuner working [still not 8-(]. r128 has been >>>>>>modprobed, as well as mga and agpgart [for the g450 primary card]. >>>>>> >>>>>>thanks! >>>>>> >>>>>>joe >>>>>> >>>>>>Mike A. Harris wrote: >>>>>> _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
