LinHES Forums
http://forum.linhes.org/

HVR-1600 - Beta drivers
http://forum.linhes.org/viewtopic.php?f=15&t=17502		 Page 1 of 2
Author:  acipolone [ Sun Dec 30, 2007 2:18 am ]
Post subject:  HVR-1600 - Beta drivers
My sister and brother-in-law were kind enough to get my a tuner card for my myth box, but unfortunately they picked up an HVR-1600, which has no real linux support. (Mostly my fault -- I think I copied a wrong link ... I was sure whatever I had on my list was something that would work with MythTV! Oops!)

I did a bit of investigating before asking them to return it for me (which I would feel kinda bad about), and apparently there are some beta drivers out there:

http://ivtvdriver.org/index.php/Cx18

I'll be testing it when I get back home in a few days. I have no HDTV, so I'm not concerned about the ATSC stuff just yet.

Only posting to share, as a search for 'HVR 1600' here only brings up two posts and no mention of the beta drivers. Anyone else been making use of these? Any luck?
Author:  wmcvetty [ Mon Dec 31, 2007 8:10 am ]
Post subject: 
If you get it working please post, as I was wondering if there was any additional support for this card yet too.

Thanks!
Author:  marc.aronson [ Mon Dec 31, 2007 9:55 am ]
Post subject: 
Thanks for posting about this -- I'm very interested in the outcome. This card supports analog, ATSC and QAM. OTA analog transmissions cease in Feb, 200. Comcast is also planning to cease analog cable transmissions in the same time frame. If it works well, this will be a great product for bridging the transition: Use the analog capability for now; use the digital capability once you're ready to transition.

Marc
Author:  wmcvetty [ Mon Dec 31, 2007 2:02 pm ]
Post subject: 
With CompUSA going out of business I took a stroll through there on my lunch break. No real deals, but I did get one of these cards for the heck of it as it seems that they are have some cooperation with the analog side, and hopeful future work on the digital side.

One warning, not all of the HVR-1600's support QAM. Seems that there is a tuner specification that has to be met. From the website:

QAM is only supported on product codes 74021 and 74041 (found on the tuner label)

I picked up one for 109, less 20% off that ended up having the 74021 tuner even though compusa's website seems to convey it will not work with QAM Hauppauge's says it will. Now, I guess I will see when and if support for it makes it to the open source world....

Figured this was as good as any place to mention this...
Author:  marc.aronson [ Mon Dec 31, 2007 6:57 pm ]
Post subject: 
wmcvetty wrote:
One warning, not all of the HVR-1600's support QAM. Seems that there is a tuner specification that has to be met. From the website:

QAM is only supported on product codes 74021 and 74041 (found on the tuner label)

Thanks for the heads-up -- I hadn't noticed this before.


Marc
Author:  bigbro [ Tue Jan 01, 2008 12:55 pm ]
Post subject: 
I used one of these in another installation on a different O/S. It was a 74021 version.
The cable was Comcast. I was able to tune and capture in both Analog and Qam on this card at that same time. It also offers ATSC but there was no line of site so we didn't get to try that.

Only comments, Tuning QAM was a little kludgy to get setup, and it didn't like the "Watch Live TV" function on the digital QAM, seemed to skip and stutter a bunch. I could capture and go back in about a minute behind the capture and that seemed decent while it was still capturing.

This was not Media Center and as such the maturity of that platform packages are still happening.

I welcome the Open source drivers for this card, I believe it would work a lot better.
Author:  marc.aronson [ Tue Jan 01, 2008 4:58 pm ]
Post subject: 
bigbro, thanks for the info but from your post it's unclear if your information is based on experience with mythtv under Linux or with a different application under a different O/S. Thanks for clarifying!

Marc
Author:  bigbro [ Tue Jan 01, 2008 5:41 pm ]
Post subject: 
Sorry my experience was with another open source application under Windoze XP

Since this was and is a Linux based application forum I didn't choose to mention that, probably should have been a little clearer.

I can say the captured images coming through the HVR-1600 were much clearer and sharper than even the supplied Comcast digital box, Both were output via Component to a 22" monitor capable of running at 1680x1050.

The Comcast box seemed to limit display to about 1440x900 while the PC output from HVR-1600 through an AMD X2 5600+ and nvidia based 8600 video ran the monitor in native at 1680x1050.

Again the main issue I saw was lack of maturity of the drivers and the application. I expect it will be a great card once the drivers for the Linux world are resolved. I was impressed with how much it could do for the price even with the driver issues then. This was last September.
Author:  acipolone [ Fri Jan 04, 2008 1:18 am ]
Post subject: 
Unfortunately I can't get the driver to compile. There's apparently some problems with the 2.6.18 kernel and this driver ... I'm not all that much of a coder so some of the threads I've read are totally over my head.

Threads:

http://www.gossamer-threads.com/lists/ivtv/devel/37175
http://www.gossamer-threads.com/lists/ivtv/users/37029 (mentions the 2.6.18 problem)

Basically, here's my error:

Code:
make -C /home/acipolone/tip/cx18-1a65fdfd182d/v4l
make[1]: Entering directory `/home/acipolone/tip/cx18-1a65fdfd182d/v4l'
creating symbolic links...
Kernel build directory is /lib/modules/2.6.18-chw-13/build
make -C /lib/modules/2.6.18-chw-13/build SUBDIRS=/home/acipolone/tip/cx18-1a65fdfd182d/v4l  modules
make[2]: Entering directory `/usr/src/linux-source-2.6.18-chw-13'
  CC [M]  /home/acipolone/tip/cx18-1a65fdfd182d/v4l/videodev.o
/home/acipolone/tip/cx18-1a65fdfd182d/v4l/videodev.c:126: error: unknown field 'dev_attrs' specified in initializer
/home/acipolone/tip/cx18-1a65fdfd182d/v4l/videodev.c:126: warning: initialization from incompatible pointer type
/home/acipolone/tip/cx18-1a65fdfd182d/v4l/videodev.c:127: error: unknown field 'dev_release' specified in initializer
/home/acipolone/tip/cx18-1a65fdfd182d/v4l/videodev.c:127: warning: missing braces around initializer
/home/acipolone/tip/cx18-1a65fdfd182d/v4l/videodev.c:127: warning: (near initialization for 'video_class.subsys')
/home/acipolone/tip/cx18-1a65fdfd182d/v4l/videodev.c:127: warning: initialization from incompatible pointer type
make[3]: *** [/home/acipolone/tip/cx18-1a65fdfd182d/v4l/videodev.o] Error 1
make[2]: *** [_module_/home/acipolone/tip/cx18-1a65fdfd182d/v4l] Error 2
make[2]: Leaving directory `/usr/src/linux-source-2.6.18-chw-13'
make[1]: *** [default] Error 2
make[1]: Leaving directory `/home/acipolone/tip/cx18-1a65fdfd182d/v4l'
make: *** [all] Error 2


I'll tinker with it later and see if I can get it to work. Too sick and full of cough medicine to think straight. :P
Author:  BigMoneyJim [ Sun Jan 06, 2008 8:39 am ]
Post subject: 
I grabbed one of these as a second tuner. I looked for support before opening the box, so the box is just sitting here sealed.

Mine came with a remote control and IR blaster. Does anyone know if the remote works with mythtv?

I only want to capture ATSC, so I'm not sure if I want to open this and wait for support or take it back and lose the remote.
Author:  dwaine [ Thu Jan 10, 2008 9:42 am ]
Post subject: 
Tried the patch mentioned in the message thread. v4l CVS now compiles under the 2.6.18 kernel.

diff -r b9523a14ccea linux/drivers/media/video/v4l1-compat.c
--- a/linux/drivers/media/video/v4l1-compat.c Sun Nov 04 14:34:05 2007
-0200
+++ b/linux/drivers/media/video/v4l1-compat.c Wed Nov 07 00:00:45 2007
-0600
@@ -145,7 +145,7 @@ const static unsigned int palette2pixelf
[VIDEO_PALETTE_YUV422P] = V4L2_PIX_FMT_YUV422P,
};

-static unsigned int __pure
+static unsigned int /* __pure */
palette_to_pixelformat(unsigned int palette)
{
if (palette < ARRAY_SIZE(palette2pixelformat))
diff -r b9523a14ccea linux/drivers/media/video/videodev.c
--- a/linux/drivers/media/video/videodev.c Sun Nov 04 14:34:05 2007
-0200
+++ b/linux/drivers/media/video/videodev.c Tue Nov 06 19:31:57 2007
-0600
@@ -111,7 +111,7 @@ static void video_release(struct device
vfd->release(vfd);
}

-#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,13)
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,19)
static struct device_attribute video_device_attrs[] = {
__ATTR(name, S_IRUGO, show_name, NULL),
__ATTR_NULL
@@ -120,7 +120,7 @@ static struct device_attribute video_dev

static struct class video_class = {
.name = VIDEO_NAME,
-#if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,13)
+#if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,19)
.release = video_release,
#else
.dev_attrs = video_device_attrs,
Author:  Pain [ Fri Jan 11, 2008 1:42 am ]
Post subject: 
Sounds promising. I got a HVR-1600 (74041) that I can't return so it is just sitting in a box waiting for support. From what I read elsewhere, the QAM models have a different chip then the older ones so it might be tricky to know which product codes of the HVR-1600 will work.
Author:  BigMoneyJim [ Fri Jan 11, 2008 3:29 am ]
Post subject: 
I just got the driver compiled (I went with a newer kernel instead of patching the driver). And I copied the firmware and loaded the module. It's there. Now I'm searching for what to do with it next. Can I add it to MythTV yet? I don't expect it to work correctly with ATSC yet, but what can I do with it?

I think I saw somewhere to try cat'ing the /dev/video0, but I think I have to tune it first. Off to search some more...

EDIT: No, I can't get anything out of my /dev/video0 . I have some messages about invalid eeprom and a bad packet header. I'll have to recheck all my settings and then maybe post a message to the mailing list.
Author:  acipolone [ Sun Jan 13, 2008 9:12 pm ]
Post subject: 
Got the driver compiled okay (had to make the patch by hand -- couldn't get it to work via the patch command, but that might just have been me ... never patched before).

I can sometimes get video from it. Sometimes.

After running "cat /dev/video0 > test.mpg" I get:

Code:
cx18-0: Unknown cmd 9b
cx18-0: Unknown cmd 9f
cx18-0: Unknown cmd a1
cx18-0: Unknown cmd 9d
cx18-0: Unknown cmd 9b
cx18-0: Unknown cmd 9f
cx18-0: Unknown cmd a1
cx18-0: Unknown cmd 9d
cx18-0: Unknown cmd 9b
cx18-0: Unknown cmd 9f
cx18-0: Unknown cmd a1
cx18-0: Unknown cmd 9d
cx18-0: Unknown cmd 9b
cx18-0: Unknown cmd 9f
cx18-0: Unknown cmd a1
cx18-0: Unknown cmd 9d

Someone just posted this morning about this exact problem:
http://www.gossamer-threads.com/lists/ivtv/devel/37457#37457

Only difference I have is that when I run "lspci -v" I see:

Code:
02:0a.0 Multimedia video controller: Conexant Unknown device 5b7a
        Subsystem: Hauppauge computer works Inc. Unknown device 7444
        Flags: bus master, medium devsel, latency 64, IRQ 11
        Memory at f4000000 (32-bit, non-prefetchable) [size=64M]
        Capabilities: [44] Vital Product Data
        Capabilities: [4c] Power Management version 2

Which has "Unknown device 5b7a" instead of "Conexant CX23418 Single-Chip MPEG-2," but otherwise all messages are the same.

BigMoneyJim, have you tried doing a complete power off and reboot? After I compiled the code I did a soft reboot and was getting all of those eeprom errors. After powering off, it loaded fine.
Author:  acipolone [ Sun Jan 13, 2008 9:42 pm ]
Post subject: 
As a side note, when I try and use Watch TV it goes to a black screen for a few seconds (where those Unknown cmd messages seem to appear) then dumps back to the menu with no opportunity to change capture cards.

However, running "mplayer /dev/video0" does, indeed, produce playback every time.
Page 1 of 2 All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/