[pvrusb2] Only static, no channels found, hauppauge wintv-hvr-1950 on mythbuntu

Bill Kristan wkristan at gmail.com
Sun Sep 26 20:27:53 CDT 2010


That did it, thanks Tomas!

Bill

On Sun, Sep 26, 2010 at 9:31 AM, Tomas Hylander <tomas.hylander at gmail.com>wrote:

> Hi Bill!
> Just got mine 1900 to work so this might apply to you aswell since your
> problem sounds like the same as mine.
>
> What I did was upgrade to kernel 2.6.35.5.
> Its very easy (Im a linux noob).
>
> go here<
> http://kernel.ubuntu.com/%7Ekernel-ppa/mainline/v2.6.35.5-maverick/>first
> and download 3 packages;
> linux-headers-2.6.35-02063505-generic_2.6.35-02063505.201009211107_i386.deb
> linux-headers-2.6.35-02063505_2.6.35-02063505.201009211107_all.deb
> linux-image-2.6.35-02063505-generic_2.6.35-02063505.201009211107_i386.deb
>
> DONT install them when you get the question by firefox (or whatever)
>
> After you have downloaded them install them in this order
> - header-all
> - header
> - image
>
> Restart and you should be up and running!
>
> Good luck!
> /Tomas
>
> 2010/9/26 Bill Kristan <wkristan at gmail.com>
>
> > Hello - I'm trying to get my wintv-hvr-1950 working on the most recent
> > Mythbuntu. I've confirmed that the hvr-1950 works (it's fine in Windows
> for
> > both analog and qam stations). I'm using firmware downloaded from
> > iseley.net(the firmware on the driver cd was 16 kb, and my kernel
> > can't use it yet).
> > The firmware is loaded, and devices are created (I have /dev/video0 and
> > /dev/dvb/adapter0... nodes), but all I get from /dev/video0 is static.
> > Channel scanning (in mythtv or with w_scan) never finds any stations
> (I've
> > tried both analog and digital, and neither works). Eventually I'd like
> both
> > analog and digital to work, but for the moment my priority is analog.
> >
> > Relevant dmesg output is here:
> >
> > [    0.000000] Linux version 2.6.32-21-generic (buildd at rothera) (gcc
> > version
> > 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #32-Ubuntu SMP Fri Apr 16 08:10:02 UTC
> 2010
> > (Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2)
> > [    7.365169] i2c i2c-0: nForce2 SMBus adapter at 0x4d00
> > [   12.576742] pvrusb2: V4L in-tree version:Hauppauge WinTV-PVR-USB2
> MPEG2
> > Encoder/Tuner
> > [   12.576753] pvrusb2: Debug mask is 31 (0x1f)
> > [   13.547908] cx25840 1-0044: cx25843-24 found @ 0x88 (pvrusb2_a)
> > [   13.549470] pvrusb2: Attached sub-driver cx25840
> > [   14.767862] tuner 1-0042: chip found @ 0x84 (pvrusb2_a)
> > [   15.527922] tda9887 1-0042: creating new instance
> > [   15.527933] tda9887 1-0042: tda988[5/6/7] found
> > [   15.528800] pvrusb2: Attached sub-driver tuner
> > [   15.542485] cx25840 1-0044: firmware: requesting v4l-cx25840.fw
> > [   18.867442] cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382
> bytes)
> > [   18.968372] tveeprom 1-00a2: Hauppauge model 75111, rev D2F5, serial#
> > 7274248
> > [   18.968382] tveeprom 1-00a2: MAC address is 00-0D-FE-6E-FF-08
> > [   18.968389] tveeprom 1-00a2: tuner model is NXP 18271C2 (idx 155, type
> > 54)
> > [   18.968397] tveeprom 1-00a2: TV standards NTSC(M) ATSC/DVB Digital
> > (eeprom 0x88)
> > [   18.968404] tveeprom 1-00a2: audio processor is CX25843 (idx 37)
> > [   18.968409] tveeprom 1-00a2: decoder processor is CX25843 (idx 30)
> > [   18.968415] tveeprom 1-00a2: has radio, has IR receiver, has IR
> > transmitter
> > [   18.968430] pvrusb2: Supported video standard(s) reported available in
> > hardware: PAL-M/N/Nc;NTSC-M/Mj/Mk;ATSC-8VSB/16VSB
> > [   18.968442] pvrusb2: Mapping standards mask=0x300b700
> > (PAL-M/N/Nc;NTSC-M/Mj/Mk;ATSC-8VSB/16VSB)
> > [   18.968449] pvrusb2: Setting up 6 unique standard(s)
> > [   18.968456] pvrusb2: Set up standard idx=0 name=PAL-M
> > [   18.968462] pvrusb2: Set up standard idx=1 name=PAL-N
> > [   18.968468] pvrusb2: Set up standard idx=2 name=PAL-Nc
> > [   18.968474] pvrusb2: Set up standard idx=3 name=NTSC-M
> > [   18.968479] pvrusb2: Set up standard idx=4 name=NTSC-Mj
> > [   18.968485] pvrusb2: Set up standard idx=5 name=NTSC-Mk
> > [   18.968492] pvrusb2: Initial video standard (determined by device
> type):
> > NTSC-M
> > [   18.968517] pvrusb2: Device initialization completed successfully.
> > [   18.968740] pvrusb2: registered device video0 [mpeg]
> > [   18.968752] DVB: registering new adapter (pvrusb2-dvb)
> > [   19.033098] cx25840 1-0044: firmware: requesting v4l-cx25840.fw
> > [   20.044047] hda_codec: ALC1200: BIOS auto-probing.
> > [   20.140222] input: HDA Digital PCBeep as
> > /devices/pci0000:00/0000:00:08.0/input/input6
> > [   21.541472] cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382
> bytes)
> > [   21.776109] usb 1-2: firmware: requesting v4l-cx2341x-enc.fw
> > [   22.295980] cx25840 1-0044: 0x0000 is not a valid video input!
> > [   22.768497] DVB: registering adapter 0 frontend 0 (Samsung S5H1411
> > QAM/8VSB Frontend)...
> > [   22.943056] tda18271 1-0060: creating new instance
> > [   22.943368] tda18271_read_regs: ERROR: i2c_transfer returned: -5
> > [   22.943379] Unknown device detected @ 1-0060, device not supported.
> > [   22.943611] tda18271_read_regs: ERROR: i2c_transfer returned: -5
> > [   22.943619] Unknown device detected @ 1-0060, device not supported.
> > [   22.943626] tda18271_attach: error -22 on line 1243
> > [   22.943633] tda18271 1-0060: destroying instance
> > [   30.888702] cx25840 1-0044: firmware: requesting v4l-cx25840.fw
> > [   33.396816] cx25840 1-0044: loaded v4l-cx25840.fw firmware (16382
> bytes)
> >
> > I can see there's an error in the tda18271 lines, but I don't know what
> it
> > means. I think all the required modules are loading - lsmod |grep pvrusb2
> > shows:
> >
> > pvrusb2               130786  0
> > dvb_core               86142  1 pvrusb2
> > cx2341x                12469  1 pvrusb2
> > v4l2_common            15431  4 tuner,cx25840,pvrusb2,cx2341x
> > videodev               34361  4 tuner,cx25840,pvrusb2,v4l2_common
> > v4l1_compat            13251  2 pvrusb2,videodev
> > tveeprom               11102  1 pvrusb2
> >
> > I saw in one of Mike's replies to somebody with this device that it's
> > probably a problem with the tuner module, is that the best guess at this
> > point? I'm not sure what to do about that, other than wait for the next
> > release of Mythbuntu next month (it's supposed to use a 2.6.35 kernel, I
> > think), but is there a way I can try to fix this now? This is a brand new
> > install on a new computer, so I'm up for switching to a different distro
> if
> > that would help...does anyone know if this device works with the current
> > Mythdora or Linhes releases?
> >
> > Thanks for the help,
> > Bill
> > _______________________________________________
> > pvrusb2 mailing list
> > pvrusb2 at isely.net
> > http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
> >
> _______________________________________________
> pvrusb2 mailing list
> pvrusb2 at isely.net
> http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
>


More information about the pvrusb2 mailing list