This issue turns out to have been a false alarm. I sent in my questions about it after having spent a good part of a couple days testing the equipment. Late last night in some final testing, I adjusted some additional settings and now both tuners seem to be working fine. There are a few strange things when watching live TV--e.g., when changing channels the tuner sometimes goes back to a channel that had been previously tuned. But test recordings I've tried so far have worked fine. Since I watch very little live TV, I don't expect the intermittent strange issue mentioned to be much of a factor. So, sorry to have bothered the list which what seems actually to have been a user issue (ignorance).

On Tue, 31 Mar 2015, J Miller wrote:

Hi. This list seems to be somewhat dead, but when I try searching on my issue, results from this list always come up. So it seems worth a try to ask for some help here.

I got a couple of these tuners used for a pretty good price and am currently trying to test them. I'm want to determine at this stage whether they are functional so that, if not, I can send them back to the seller for a refund.

The target system is a new Gentoo install on the Liva X, which is also running MythTV. So I've hooked up the tuners, loaded the firmware (firmware gotten via Gentoo) and modules, gotten them recognized in mythtv-setup--and even written udev rules--and am trying to proceed further.

I tried a channel scan under mythtv-setup, which gives some odd results; I'm not any kind of myth-guru, so maybe the results are only odd to me. The scan does finish and seems to find channels or to update channels, but it finishes with the message "no new channels found."

When I attempt to watch live TV through the MythTV interface, though, the only channels I can seem to tune are 5 and 6: trying others results in either a blank black screen or an error message (something like "failed jump"). So something is not working right here. Perhaps I should mention that I'm using the up/down arrows on an attached keyboard to select channels (no remote). In any case, those may be MythTV issues, or MythTV user issues, which cannot be addressed here.

But what perhaps can be addressed are errors I'm seeing in dmesg output. Both tuners output the error message seen in the subject heading of this e-mail as I try to tune stations.

I'll append below some dmesg output that may provide further insight into the issues I'm confronting:

[   11.453937] cx25840 9-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
[   11.556504] tda829x 9-0042: setting tuner address to 60
[   11.577379] tda18271 9-0060: creating new instance
[   11.607502] TDA18271HD/C1 detected @ 9-0060
[   11.919566] tda829x 9-0042: type set to tda8295+18271
[   18.461510] cx25840 9-0044: 0x0000 is not a valid video input!
[ 18.547765] usb 1-3.1: DVB: registering adapter 1 frontend 0 (Samsung S5H1411 QAM/8VSB Frontend)...
[   18.549074] tda829x 9-0042: type set to tda8295
[   18.580554] tda18271 9-0060: attaching existing instance
[   18.613959] pvrusb2: Binding ir_rx_z8f0811_haup to i2c address 0x71.
[   18.613998] pvrusb2: Binding ir_tx_z8f0811_haup to i2c address 0x70.
[   18.618293] cx25840 10-0044: cx25843-24 found @ 0x88 (pvrusb2_b)
[   18.627399] pvrusb2: Attached sub-driver cx25840
[   18.631792] tuner 10-0042: Tuner -1 found with type(s) Radio TV.
[   18.631808] pvrusb2: Attached sub-driver tuner
[   20.784470] cx25840 10-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
[ 20.875111] tveeprom 10-00a2: Hauppauge model 75111, rev D1F5, serial# 6523363
[   20.875119] tveeprom 10-00a2: MAC address is 00:0d:fe:63:89:e3
[ 20.875124] tveeprom 10-00a2: tuner model is NXP 18271C2 (idx 155, type 54) [ 20.875129] tveeprom 10-00a2: TV standards NTSC(M) ATSC/DVB Digital (eeprom 0x88)
[   20.875133] tveeprom 10-00a2: audio processor is CX25843 (idx 37)
[   20.875137] tveeprom 10-00a2: decoder processor is CX25843 (idx 30)
[ 20.875141] tveeprom 10-00a2: has radio, has IR receiver, has IR transmitter [ 20.875150] pvrusb2: Supported video standard(s) reported available in hardware: PAL-M/N/Nc;NTSC-M/Mj/Mk;ATSC-8VSB/16VSB [ 20.875154] pvrusb2: Initial video standard (determined by device type): NTSC-M
[   20.875169] pvrusb2: Device initialization completed successfully.
[   20.877732] pvrusb2: registered device video1 [mpeg]
[   20.877740] DVB: registering new adapter (pvrusb2-dvb)
[   23.071488] cx25840 10-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
[   23.178551] tda829x 10-0042: setting tuner address to 60
[   23.200431] tda18271 10-0060: creating new instance
[   23.230531] TDA18271HD/C2 detected @ 10-0060
[   23.514810] tda18271: performing RF tracking filter calibration
[   23.575224] cx25840 9-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
[   34.970666] tda18271: RF tracking filter calibration complete
[   35.008577] tda829x 10-0042: type set to tda8295+18271
[   39.270725] cx25840 10-0044: 0x0000 is not a valid video input!
[ 39.354481] usb 1-3.2: DVB: registering adapter 2 frontend 0 (Samsung S5H1411 QAM/8VSB Frontend)...
[   39.356058] tda829x 10-0042: type set to tda8295
[   39.387436] tda18271 10-0060: attaching existing instance
[  350.784919] cx25840 10-0044: loaded v4l-cx25840.fw firmware (16382 bytes)
[ 411.124297] pvrusb2: ***WARNING*** device's encoder appears to be stuck (status=0x00000003)
[  411.124304] pvrusb2: Encoder command: 0x81
[ 411.124308] pvrusb2: Giving up on command. This is normally recovered via a firmware reload and re-initialization; concern is only warranted if this happens repeatedly and rapidly. [ 433.140820] pvrusb2: ***WARNING*** device's encoder appears to be stuck (status=0x00000003)
[  433.140827] pvrusb2: Encoder command: 0x81
[ 433.140831] pvrusb2: Giving up on command. This is normally recovered via a firmware reload and re-initialization; concern is only warranted if this happens repeatedly and rapidly. [ 492.719711] pvrusb2: ***WARNING*** device's encoder appears to be stuck (status=0x00000003)
[  492.719719] pvrusb2: Encoder command: 0x81
[ 492.719723] pvrusb2: Giving up on command. This is normally recovered via a firmware reload and re-initialization; concern is only warranted if this happens repeatedly and rapidly. [ 581.206124] pvrusb2: ***WARNING*** device's encoder appears to be stuck (status=0x00000003)
[  581.206131] pvrusb2: Encoder command: 0x81
[ 581.206135] pvrusb2: Giving up on command. This is normally recovered via a firmware reload and re-initialization; concern is only warranted if this happens repeatedly and rapidly. [ 1132.451724] pvrusb2: ***WARNING*** device's encoder appears to be stuck (status=0x00000003)
[ 1132.451732] pvrusb2: Encoder command: 0x81
[ 1132.451735] pvrusb2: Giving up on command. This is normally recovered via a firmware reload and re-initialization; concern is only warranted if this happens repeatedly and rapidly.

Thanks.
_______________________________________________
pvrusb2 mailing list
[email protected]
http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2

_______________________________________________
pvrusb2 mailing list
[email protected]
http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2

Reply via email to