Logo United Kingdom

Register | Login 

Hauppauge WinTV HVR-850 (USB, HDTV Stick)

Multimedia Hauppauge, HDTV, TV, USB

Hauppauge WinTV HVR-850 (USB, HDTV Stick)
Linux compatibility: Only the Linux compatibility is rated on this page, not the general quality of the product. If you use this product with Linux, please rate it and share your experience in the comment area of this page (bottom) to support other Linux users.
2 votes, average: 5.0 out of 52 votes, average: 5.0 out of 52 votes, average: 5.0 out of 52 votes, average: 5.0 out of 52 votes, average: 5.0 out of 5
  ( 5 with 2 ratings)

Review of Linux Compatibility

The Hauppauge WinTV HVR-850 is a HDTV USB Stick, which exists in three different version. All versions are working under Linux, but use different chipsets and therefore different drivers.

Model 65301 – USB ID 2040:651f

This version of the Hauppauge WinTV HVR-850 uses the same chipset as the HVR-950. It therefore needs the same firmware file xc3028-v27.fw in /lib/firmware. If the file was not included in the Linux distribution, it can be extracted from the Windows driver file. After downloading and extracting the windows driver by:

unzip -j Driver85/hcw85bda.sys

the firmware can be extracted by the script, which is loaced under linux/Documentation/video4linux:

cd linux/Documentation/video4linux

The generated file xc3028-v27.fw has to be copied to /lib/firmware in order to be found by the Linux kernel:

cp xc3028-v27.fw /lib/firmware

(Details about HVR-950 installation and configuration can be found at

Model 72301 – USB ID 2040:7240

This version of the HVR-850 has the USB ID 2040:7240

Bus 001 Device 002: ID 2040:7240 Hauppauge

and needs the file firmware file xc5000-1.6.114.fw in /lib/firmware:

sudo wget -O /lib/firmware/dvb-fe-xc5000-1.6.114.fw

to successfully load the driver xc5000. This driver (i.e. kernel module) is already part of the latest Linux kernels (or more precisely: part of v4l-dvb drivers) and loads automatically:

usb 4-3: new high speed USB device using ehci_hcd and address 2
usb 4-3: configuration #1 chosen from 1 choice
tveeprom 2-0050: Hauppauge model 72301, rev B3F0, serial# 4752928
tveeprom 2-0050: MAC address is 00-0D-00-00-00-00
tveeprom 2-0050: tuner model is Xceive XC5000 (idx 150, type 4)
tveeprom 2-0050: TV standards NTSC(M) ATSC/DVB Digital (eeprom 0x88)
tveeprom 2-0050: audio processor is AU8522 (idx 44)
tveeprom 2-0050: decoder processor is AU8522 (idx 42)
tveeprom 2-0050: has no radio, has IR receiver, has no IR transmitter
hauppauge_eeprom: hauppauge eeprom: model=72301
xc5000 2-0061: creating new instance
xc5000: Successfully identified at address 0x61
xc5000: Firmware has not been loaded previously
DVB: registering new adapter (au0828)
DVB: registering adapter 1 frontend 0 (Auvitek AU8522 QAM/8VSB Frontend)...
Registered device AU0828 [Hauppauge HVR850]
usb 4-3: New USB device found, idVendor=2040, idProduct=7240
usb 4-3: New USB device strings: Mfr=1, Product=2, SerialNumber=10
usb 4-3: Product: WinTV HVR-850
usb 4-3: Manufacturer: Hauppauge
usb 4-3: SerialNumber: 4031284768

Model 01200 – USB ID 2040:b140

This newer version of the Hauppauge WinTV HVR-850 has the USB ID 2040:b140. This stick is fully and automatically supported by Linux (at least since Ubuntu 12.04) this was functional using the same xc5000 firmware and v4l-dvb driver as used for the model 72301 (see above).

Similar Linux Hardware

scroll left scroll right


One response to “Hauppauge WinTV HVR-850 (USB, HDTV Stick)”

  • Mike Somerville says:

    My WinTV HVR-850 is not working under Ubuntu 16.04

    mike@sophie:~$ uname -a
    Linux sophie 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

    [366684.806625] usb 3-1: new high-speed USB device number 76 using xhci_hcd
    [366684.937060] usb 3-1: New USB device found, idVendor=2040, idProduct=b140
    [366684.937062] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [366684.937064] usb 3-1: Product: Hauppauge Device
    [366684.937065] usb 3-1: Manufacturer: Hauppauge
    [366684.937066] usb 3-1: SerialNumber: 4034705435
    [366684.940536] cx231xx 3-1:1.1: New device Hauppauge Hauppauge Device @ 480 Mbps (2040:b140) with 7 interfaces
    [366684.940613] cx231xx 3-1:1.1: Identified as Hauppauge EXETER (card=8)
    [366684.941165] i2c i2c-10: Added multiplexed i2c bus 12
    [366684.941223] i2c i2c-10: Added multiplexed i2c bus 13
    [366685.152198] cx25840 9-0044: cx23102 A/V decoder found @ 0×88 (cx231xx #0-0)
    [366687.106786] cx25840 9-0044: loaded v4l-cx231xx-avcore-01.fw firmware (16382 bytes)
    [366687.138700] Chip ID is not zero. It is not a TEA5767
    [366687.138705] tuner 12-0060: Tuner -1 found with type(s) Radio TV.
    [366687.138710] tda18271 12-0060: creating new instance
    [366687.140144] Unknown device (110) detected @ 12-0060, device not supported.
    [366687.140146] tda18271_attach: [12-0060|M] error -22 on line 1285
    [366687.140147] tda18271 12-0060: destroying instance
    [366687.145169] tuner 12-0060: Tuner has no way to set tv freq
    [366687.146181] cx231xx 3-1:1.1: v4l2 driver version 0.0.3
    [366687.269209] tuner 12-0060: Tuner has no way to set tv freq
    [366687.269340] cx231xx 3-1:1.1: Registered video device video0 [v4l2]
    [366687.269394] cx231xx 3-1:1.1: Registered VBI device vbi0
    [366687.269693] cx231xx 3-1:1.1: audio EndPoint Addr 0×83, Alternate settings: 3
    [366687.314946] cx231xx 3-1:1.1: dvb_init: looking for tuner / demod on i2c bus: 12
    [366687.315154] cx231xx 3-1:1.1: cx231xx_send_usb_command: failed with status –32
    [366687.315157] lgdt3305_read_reg: error (addr 0e reg 0001 error (ret == -32)
    [366687.315158] lgdt3305_attach: error -32 on line 1143
    [366687.315159] lgdt3305_attach: unable to detect LGDT3305 hardware
    [366687.315160] cx231xx 3-1:1.1: Failed to attach LG3305 front end
    [366687.315254] cx231xx 3-1:1.1: video EndPoint Addr 0×84, Alternate settings: 5
    [366687.315256] cx231xx 3-1:1.1: VBI EndPoint Addr 0×85, Alternate settings: 2
    [366687.315257] cx231xx 3-1:1.1: sliced CC EndPoint Addr 0×86, Alternate settings: 2
    [366687.315258] cx231xx 3-1:1.1: TS EndPoint Addr 0×81, Alternate settings: 6

    mike@sophie:/dev$ sudo ls -lR |grep -i v4l
    [sudo] password for mike:
    drwxr-xr-x 4 root root 80 Jan 23 15:10 v4l
    mike@sophie:/dev$ sudo ls -lR |grep -i vbi
    crw-rw—-+ 1 root video 81, 1 Jan 23 15:10 vbi0
    lrwxrwxrwx 1 root root 7 Jan 23 15:10 81:1 -> ../vbi0
    lrwxrwxrwx 1 root root 10 Jan 23 15:10 pci-0000:00:14.0-usb-0:1:1.1-video-index1 -> ../../vbi0

    mike@sophie:~$ lsusb
    Bus 002 Device 002: ID 8087:8000 Intel Corp.
    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 001 Device 002: ID 8087:8008 Intel Corp.
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 003 Device 002: ID 413c:3016 Dell Computer Corp. Optical 5-Button Wheel Mouse
    Bus 003 Device 003: ID 04f3:0103 Elan Microelectronics Corp. ActiveJet K-2024 Multimedia Keyboard
    Bus 003 Device 076: ID 2040:b140 Hauppauge
    Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

    Any ideas why the device won’t attach?

Start new Discussion

Please use the comment section to submit corrections to the article as well as relevant excerpts of lspci, lsusb, lshw, dmesg e.t.c. Furthermore, use the section for the exchange of experiences with this hardware component or search for configuration help from other owners of this hardware.

Email address will not be published.

Rate Linux compatibility

Use the following HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Allowed file types: txt, jpg, png, gif, maximum file size: 2MB.