From: Jonathan Coles <jcoles0727@rogers.com>
To: Michael Krufky <mkrufky@linuxtv.org>,
Devin Heitmueller <devin.heitmueller@gmail.com>
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Still unclear how to use Hauppage HVR-950 and v4l-dvb
Date: Sun, 21 Sep 2008 11:44:33 -0400 [thread overview]
Message-ID: <48D66BE1.7020900@rogers.com> (raw)
In-Reply-To: <48D65E36.9070003@linuxtv.org>
Michael Krufky wrote:
> Devin Heitmueller wrote:
>
>> On Sun, Sep 21, 2008 at 10:22 AM, Jonathan Coles <jcoles0727@rogers.com> wrote:
>>
>>> It would really help if there was a single set of instructions specific
>>> to the HVR-950 with tests at each stage. I'm really confused as to the
>>> status of my installation.
>>>
>>> I compiled the firmware according to the instructions on
>>> http://linuxtv.org/repo/. The result:
>>>
>>> $ lsusb
>>> Bus 005 Device 002: ID 2040:7200 Hauppauge
>>>
>> Hold the phone! You don't have an HVR-950. You have an HVR-950Q.
>> Please be sure to mention this in all future messages, since it's a
>> totally different device and the HVR-950 directions do not apply.
>>
>> I'm not sure whether the HVR-950Q support has been merged yet. Steven
>> could comment on that. I suspect it's still in a separate branch,
>> which would mean you would need to do an hg clone of a different tree.
>>
>
>
> HVR950Q ATSC / QAM is supported in the master development repository, and it is in upstream 2.6.26 and later.
>
> You need the xc5000 firmware.
>
> [ 17.247610] usb 5-2: new high speed USB device using ehci_hcd and
> address 2
> [ 17.380387] usb 5-2: unable to read config index 0 descriptor/all
> [ 17.380434] usb 5-2: can't read configurations, error -71
>
>
> ^^ This is not a firmware problem, but looks fishy. If using the latest drivers from linuxtv.org doesnt work for you, then try another USB port, or confirm that it also works in windows.
>
> Good Luck,
>
> Mike
>
Thanks guys!
The box says HVR-950 on it and that the device "Cannot receive digital
cable TV". However, the device itself is labeled "NTSC/ATSC/QAM HD TV
receiver" and there is a small, stylized Q following the "950". Great! I
got this on sale. Lack of QAM support was my reason for not buying
earlier at the usual price. Perhaps the store didn't realize that this
is the newer model.
I had added the XC5000 firmware, dvb-fe-xc5000-1.1.fw, in case I had a
950Q. But if, as you say, I need a later kernel, that might be why it
doesn't work. I have kernel 2.6.24-19.
I'll look for more info on linuxtv.org. Perhaps I just need to wait a
little for the support for this to be developed.
_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
next prev parent reply other threads:[~2008-09-21 15:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-21 14:22 [linux-dvb] Still unclear how to use Hauppage HVR-950 and v4l-dvb Jonathan Coles
2008-09-21 14:30 ` Devin Heitmueller
2008-09-21 14:46 ` Michael Krufky
2008-09-21 15:44 ` Jonathan Coles [this message]
2008-09-21 16:11 ` Michael Krufky
2008-09-21 17:03 ` Steven Toth
2008-09-21 17:17 ` Jonathan Coles
2008-09-21 15:52 ` BOUWSMA Barry
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=48D66BE1.7020900@rogers.com \
--to=jcoles0727@rogers.com \
--cc=devin.heitmueller@gmail.com \
--cc=linux-dvb@linuxtv.org \
--cc=mkrufky@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