WINTV HVR 950 and HARDY (sound issues)

[msrinath80]

Hi all,

Has anybody got the WINTV HVR 950 to work with sound on Hardy. I had it working perfectly well in Gutsy. Now, in hardy the sound does not work. I would appreciate if anyone could post the instructions they followed to get both audio and video working!

Thanks!

[bronson]

FWIW, it works 100% for me. Here are the notes I took:

http://u32.net/MythTV/WinTV-HVR-950/index.html

[granicus]

Were you ever able to get MythTV to recognize the input? You stated on that page that you got MPlayer to stream the DVB signal fine but had problems with MythTV, and I seem to be at the same point. MPlayer streams the DVB fine, and I have audio, but MythTV says it cannot get a channel lock. It will recognize the HVR-950 fine, and it can scan and pick up the correct channels, but no channel lock.

Any suggestions? Thanks.

[VirtualSandBox]

I would like to try my hvr-950 on my install.

For some reasons, the site http://u32.net/ seems to down (times out after a long time.)

Is there any other alternate sites to this?

thanks

[damienallen]

Here a Google cache for what I think is the U32 page:

http://bit.ly/4yrVHu

(Just Googled "hvr-950 hardy" and it was first page)


I followed the steps for installing it, but I don't want Myth (space issue). The only thing that I need to work is the composite input. Strangely the top 1/4 of the video is a distortion of the actual video and the other 3/4 is green. Does anyone know of any fixes for this? I read that it might be xgl, so I installed xgame but that didn't help.

[VirtualSandBox]

Tks Damien, I will try it and update.

[VirtualSandBox]

.... Well it sure didnt go well. It has hosed up my installation.

Choppy freezes and unresponsive windows every few seconds....

I am wondering if HVR950 has worked for anyone on 8.0.4.1 at all...

How can I uninstall this so I can possibly try again in a working condition?

[VirtualSandBox]

Removing MythTV and all its plug-in has stabilized the machine. Now I am going to try adding them in bye-sizes...

[VirtualSandBox]

Completely reinstalled Ubuntu. Tried the same again. As soon as I did the make install the keyboard froze (although I was able to still use the mouse.).

After trying for sometime, I rebooted to see the scream of thousands of lines of errors that complained about the new driver.

Infinite repetition of lines with
"....em28xx new video device (2040:6513): interface 0, class 255"

After rebooting couple of times, removed the HVR 950 and rebooted successfully (but ofcourse connecting the HVR 950 immediately causes the keyboard freeze.)

Has anybody else faced / overcame this?

Thanks,

[Hal58]

Completely reinstalled Ubuntu. Tried the same again. As soon as I did the make install the keyboard froze (although I was able to still use the mouse.).

"....em28xx new video device (2040:6513): interface 0, class 255"

After rebooting couple of times, removed the HVR 950 and rebooted successfully (but ofcourse connecting the HVR 950 immediately causes the keyboard freeze.)

This is exactly what I am seeing now, except I don't have the repeating lines. I have tried both stable and experimental em28xx trees, including the old patch to experimental (now included), firmware v3 and v4 with identical results; after building and rebooting, when the receiver is plugged into the USB, the keyboard dies (both on a HP2133 mininote and Athlon64 both with Hardy 32-bit). This USB device (2040:6513) is NOT listed in the em28xx documentation and is different from the other HVR-950 devices.

Booting with a vga=794 kernel directive instead of the splash screen and the HVR plugged in, I see the stick recognized, firmware loaded, setup, then a 'kernel Oops 0000 [#1]' and stack traces. This seems to happen when the em28xx_audio module is loaded.

Exactly the same happens on the same systems (all Hardy 8.04.1) with a Pinnacle PCTV HD Pro Stick (2304:0227) in all cases (firmware v3 and v4, and either the v4l-dvb stable or experimental modules). The Oops happens at the same point, and keyboards are disabled if the stick is plugged in after boot/login.

If the sticks are left out after booting, and the following instructions are given before the sticks are plugged in, the keyboards continue to work, but a 'dmesg' will show the Oops.
sudo modprobe em28xx
sudo modprobe em28xx-audio
sudo modprobe em2880-dvb

I have not tried an earlier release of Ubuntu where some if this seemed to work.