public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Yusik Kim <yusikk@gmail.com>
To: Steven Toth <stoth@linuxtv.org>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Hauppauge HVR-1950 digital part
Date: Sat, 26 Jul 2008 12:29:42 -0700	[thread overview]
Message-ID: <200807261229.42608.yusikk@gmail.com> (raw)
In-Reply-To: <200807261130.39977.yusikk@gmail.com>

On Saturday 26 July 2008 11:30:39 Yusik Kim wrote:
> On Saturday 26 July 2008 08:39:16 Steven Toth wrote:
> > Yusik Kim wrote:
> > > Hi,
> > >
> > > Has anyone got the digital part of this device to work properly?
> > >
> > > Modules are compiled from the latest (7/26) v4l-dvb snapshot with a
> > > 2.6.25.4 kernel. The modules seem to load properly and the analog part
> > > works in mythtv. The digital part kind of works.
> > > The problems I can observe are:
> > > 1. Can only scan 3 digital channels using both the command line scan
> > > and mythtv. My other PCI TV card scans 36 of them.
> > > 2. Only occasionally locks in to a channel.
> > > 3. Takes 5 minutes to lock in to a channel when it actually does
> > > succeed.
> > >
> > > I saw from another mailing list that people were trying to get the
> > > remote control to work so I'm guessing the core of the device functions
> > > properly. If this is the current state of support, I'd be glad to help
> > > testing.
> >
> > What steps did you take to prove your hardware is function properly, or
> > your digital cable feed is reliable?
> >
> > The drivers works for me, it sounds like you have an environmental issue.
> >
> > - Steve
>
> Thank you for replying Steve.
> I have a windows partition on the same machine and it works perfectly
> there. So I don't think there is a problem with the cable feed or hardware
> itself.
>
> Not sure if it has any relevance but I noticed in windows, the red LED
> light in the front is always on whereas in linux, it only turns on right
> before it tries to lock in to a channel.
>
> I should add that the 3 channels that were successfully scaned do not
> always get picked up in subsequent attempts. It seems like it has trouble
> tuning. At least it's good to know it's a problem on my end. Just have to
> find a way to fix it.

Also, I tried re-extracting the firmware with the perl script
http://www.isely.net/downloads/fwextract.pl
I downloaded today and used it on the installation CD to get the following 
files
376836 2008-07-26 11:59 v4l-cx2341x-enc.fw
  12559 2008-07-26 11:59 v4l-cx25840.fw
    8192 2008-07-26 11:59 v4l-pvrusb2-29xxx-01.fw
    8192 2008-07-26 11:59 v4l-pvrusb2-73xxx-01.fw
but still no luck. By the way, the filesize for the old v4l-cx25840.fw was 
16382. Everything else the same.

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

  reply	other threads:[~2008-07-26 19:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-26 10:53 [linux-dvb] Hauppauge HVR-1950 digital part Yusik Kim
2008-07-26 15:39 ` Steven Toth
2008-07-26 18:30   ` Yusik Kim
2008-07-26 19:29     ` Yusik Kim [this message]
2008-07-26 20:43       ` Mike Isely
2008-07-26 20:40     ` Mike Isely
2008-07-27  0:25       ` Yusik Kim
2008-07-27  1:33         ` Michael Krufky
2008-07-27  2:37           ` Yusik Kim

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=200807261229.42608.yusikk@gmail.com \
    --to=yusikk@gmail.com \
    --cc=linux-dvb@linuxtv.org \
    --cc=stoth@linuxtv.org \
    /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