If you haven't already, it may be worth a call to tech support to request that it be enabled. I had to do this when I first started using the firewire port on my box. The default version of the firmware Cox had rolled out did not have the ports enabled, but after being persistent they did send down a new version that got them working.
--Dave Madsen On Wed, 16 Feb 2005 15:05:25 -0800, Scott Alfter <[EMAIL PROTECTED]> wrote: > On Wed, Feb 16, 2005 at 01:12:17PM -0500, Tom Dombrosky wrote: > > That ebuild worked great for me. You should try to submit it for > > inclusion in portage. > > It depends on source obtained from a source-control system (even though I'm > hosting a static copy in a tarball), so they probably wouldn't accept it for > inclusion. (The MythTV CVS ebuilds have a note on Bugzilla attached to them > that CVS ebuilds aren't included in Portage.) > > It's good to know that it's working for somebody. Here in Las Vegas, Cox > hasn't enabled FireWire output yet. :-( When the box is plugged in, dmesg > reports problems reading information from the box. Looks like all I can do > is watch live TV or record from the S-video output (which is of course SD, > not HD). > > _/_ > / v \ Scott Alfter (remove the obvious to send mail) > (IIGS( http://alfter.us/ Top-posting! > \_^_/ rm -rf /bin/laden >What's the most annoying thing on Usenet? > > > _______________________________________________ > mythtv-users mailing list > [email protected] > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users > > > >
_______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
