public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: William Case <billlinux@rogers.com>
To: CityK <cityk@rogers.com>
Cc: video4linux-list <video4linux-list@redhat.com>
Subject: Re: TYPO [Hauppauge WinTV-hvr-1800 PCIe won't work with tvtime or mplayer.]
Date: Mon, 11 May 2009 00:16:48 -0400	[thread overview]
Message-ID: <1242015408.3277.31.camel@localhost.localdomain> (raw)
In-Reply-To: <1242013532.3277.28.camel@localhost.localdomain>

On Sun, 2009-05-10 at 23:45 -0400, William Case wrote:
> Hi CityK;
> 
> On Sun, 2009-05-10 at 20:33 -0400, CityK wrote:
> > William Case wrote:
> 
> > Note: cx88 associated modules do NOT apply to this device (cx88 driver
> > modules are for the PCI based cx2388x chipsets, where x=0/1,2,3).  This
> > is a PCIe based device which is serviced, amongst others, by the cx23885
> > driver module. 
> 
> I have removed all the extra modules I have been playing with and
> removed any modprobe instructions I had been trying.
> 
> > 
> > Also, have a look in the wiki for the device article which appears to
> > contain some info that would be useful for you.
> 
> I re-installed v4l-dvb-4c7466ea8d64.tar.bz2, as suggested on the wiki.
> The extracted files are in /lib/modules/["kernel
> version"]/kernel/drivers/media with today's installation date. (last
> modified)
> 
> > With a hardware encoding device, the /dev/video0 should be the MPEG2
> > stream whereas /dev/video1 would be the raw stream compatible with apps
> > like tvtime.  mplayer /dev/video0 should work. .... note that the node
> > number (N) of the character device (/dev/videoN) will be different if
> > you have multiple devices installed in the system, so you will have to
> > adjust accordingly.
> 
> I am trying to set up analog viewing through my cable provider.
> tvtime.xml is set to video0. It still gives me an excellent picture but
> no sound. video1 just gives me a black screen - no sound.
> 
> On mplayer device=/dev/video0 remains the same --terrible picture; no
> sound. mplayer device=/dev/video0 produces the error message 
> 'vo: x11 uninit called but X11 not initialized..' and quits.
> 
			 \/
mplayer device=/dev/video1 produces the error message  'vo: x11 uninit
called but X11 not initialized..' and quits.

> The mplayer script I am using is a slightly modified copy of the command
> suggested on the wiki.
> 
> Basically the info I submitted originally remains the same except the
> cx2388x modules are gone.
> 
> Usually I like to work away at these kind problems until I conquer them
> myself.  But I have been on this one for over two weeks and I am driving
> myself to distraction.  I really do appreciate your time and advice.
> 
-- 
Regards Bill
Fedora 10, Gnome 2.24.3
Evo.2.24.5, Emacs 22.3.1

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

  reply	other threads:[~2009-05-11  4:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-10 19:05 Hauppauge WinTV-hvr-1800 PCIe won't work with tvtime or mplayer William Case
2009-05-11  0:33 ` CityK
2009-05-11  3:45   ` William Case
2009-05-11  4:16     ` William Case [this message]
2009-05-11  4:46     ` Gene Heskett
2009-05-13 20:07 ` Completely flummoxed -- " William Case

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1242015408.3277.31.camel@localhost.localdomain \
    --to=billlinux@rogers.com \
    --cc=cityk@rogers.com \
    --cc=video4linux-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox