From owner-freebsd-multimedia Fri Mar 7 10:13:44 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA04183 for multimedia-outgoing; Fri, 7 Mar 1997 10:13:44 -0800 (PST) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA04178 for ; Fri, 7 Mar 1997 10:13:43 -0800 (PST) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.6.12) with SMTP id KAA00287; Fri, 7 Mar 1997 10:13:38 -0800 (PST) Date: Fri, 7 Mar 1997 10:13:37 -0800 (PST) From: Doug White X-Sender: dwhite@localhost Reply-To: Doug White To: Amancio Hasty cc: multimedia@FreeBSD.ORG Subject: Re: Mixed results w/ WinCast/TV In-Reply-To: <199703070753.XAA01799@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-multimedia@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 6 Mar 1997, Amancio Hasty wrote: > Try running the X server with 15bits. 15 bpp isn't a valid value for this X server. > > 2. With tv, I get a red box covering the upper-right 2/3 of the display, > > and the following kernel message: > > > > bktr0: ioctl: tsleep error 35 10000a8 > > I will loook into this over here since I have a wincast card. I get this when I capture with vic also, so it may just be a driver tweak. vic throws out this note when I turn transmit on: vic: meteor sees no signal(1)-using ntsc. I think you and I are virtually in the same boat, only you have an S3 and I have a Mach64. > Not sure but I think that wincast expects the channels connected > to the cable style input port. It is. I have standard coax TV cable on the screw-on nub. I don't have any composite devices here at the moment. I have the SVideo-out audio patch cable connected to my GUS PnP -- haven't gotten it to put out any audio yet. > > Amancio, you mentioned you had to tweak the driver to work -- could you > > perhaps post the patch so I could try it? > > Not sure that you need my driver. The problem with tv is that you may > be using the wrong input port. But I will let you know later on tonite. OK, keep us posted. I'm sure it's connected right though. > > I have this sinking feeling that direct tv may not work because of the > > Mach64. Maybe I should budget this weekend trying to extract the S3 968 > > from the P166 and not crash Win95 in the process...:) > > Well, if you have a linear buffer presented to you by the X server then > I should be able to tweak the driver to work for you. The Mach has the > opposite order of RGB pixel values however I should be able to reverse > the pixels in the bt848 driver. That's the thing - there's no mention of a linear frame buffer during the X boot probe. The Mach64 README makes no mention of a linear framebuffer option either. The red screen makes sense if the bits are backwards -- it's really a blue screen. Does tv need to select the input? Here's the X server output: XFree86 Version 3.2 / X Window System (protocol Version 11, revision 0, vendor release 6100) Release Date: Oct 26 1996 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (see http://www.XFree86.Org/FAQ) Operating System: FreeBSD 2.1.5 Configured drivers: Mach64: accelerated server for ATI Mach64 graphics adaptors (Patchlevel 0) Using syscons driver with X support (version 2.0) (using VT number 9) XF86Config: /etc/XF86Config (**) stands for supplied, (--) stands for probed/default values (**) Mouse: type: Microsoft, device: /dev/cuaa0, baudrate: 1200, 3 button emulation (timeout: 50ms) (**) Mach64: Graphics device ID: "ATI WinTurbo" (**) Mach64: Monitor ID: "Mag DX17F" (**) FontPath set to "/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/" (--) Mach64: PCI: Mach64 GX rev 3, Aperture @ 0xf9000000, Sparse I/O @ 0x02ec (**) Mach64: Option "power_saver" (--) Mach64: card type: PCI (--) Mach64: Memory type: 5 (--) Mach64: Clock type: ATI18818-1/ICS2595 (--) Mach64: Maximum allowed dot-clock: 135.000 MHz (**) Mach64: Mode "1024x768": mode clock = 85.000 (**) Mach64: Mode "640x480": mode clock = 31.500 (**) Mach64: Mode "800x600": mode clock = 50.000 (**) Mach64: Mode "1024x768": mode clock = 85.000 (**) Mach64: Virtual resolution: 1024x768 (--) Mach64: videoram: 2048k (--) Mach64: Using hardware cursor (--) Mach64: Using 8 MB aperture @ 0xf9000000 (--) Mach64: Ramdac is ATI68860 Rev C (--) Mach64: Using 8 bits per RGB value (--) Mach64: Pixmap cache: 2 256x256 slots, 8 128x128 slots, 32 64x64 slots (--) Mach64: Font cache: 16 fonts PEX extension module not loaded XIE extension module not loaded Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major