3.4 to 4.0.8-3 leaves system unusable - "no input source available for subscription" errors (raspbian Wheezy)

Neil Carter

Greetings:

A couple of days ago, I foolishly (it appears) ran an apt-get update/dist-upgrade on my Raspberry Pi (Raspbian Wheezy). Included in this run was the upgrade to TVHeadEnd 4.0.8-3 (from 3.4.?). This system uses ONLY the web gui, no Kodi, etc, and is used only as a DVR. It's connected to a Hauppauge 950Q USB tuner stick.

The next time I signed in to record a program I noticed a substantial change to the front-end and became apprehensive. So, it turns out I now cannot record anything! Everything I try to do, from test recordings to scans, fails and the syslog is full of lines similar to this:

Dec 29 21:20:00 dvr-pi tvheadend[2034]: subscription: 0088: No input source available for subscription "DVR: test" to channel "4.1 CBS"

I've rebooted, I've fiddled with some of the settings, no change.

Suggestions, please!!!!!!?

mpmc

Make sure that you've enabled the adapter & assigned it a network.

Neil Carter

Greetings:

Thanks for the reply!

I did enable the adapter +and+ made certain that it's assigned to the only network configured (_dev_dvb_adapter0_Auvitek_AU8522_QAM_8VSB_Frontend) prior to posting the original request.

One thing to add: When I tell the network to 'Force Scan', the syslog displays something like this for every channel/service enabled:

Dec 30 15:02:15 dvr-pi tvheadend[2034]: mpegts: 79.028MHz indevdvb_adapter0_Auvitek_AU8522_QAM_8VSB_Frontend - tuning on Auvitek AU8522 QAM/8VSB Frontend : ATSC #0
Dec 30 15:02:15 dvr-pi tvheadend[2034]: subscription: 010F: "scan" subscribing to mux "79.028MHz", weight: 6, adapter: "Auvitek AU8522 QAM/8VSB Frontend : ATSC #0", network: "_dev_dvb_adapter0_Auvitek_AU8522_QAM_8VSB_Frontend", service: "Raw PID Subscription"
Dec 30 15:02:20 dvr-pi tvheadend[2034]: mpegts: 79.028MHz indevdvb_adapter0_Auvitek_AU8522_QAM_8VSB_Frontend -scan no data, failed

Dec 30 15:02:20 dvr-pi tvheadend[2034]: subscription: 010F: "scan" unsubscribing

Any other ideas, anyone?

Thanks!!

Neil Carter

Here's the latest syslog, if it will help.

Thanks!!

mpmc

79.028MHz and the points in the frequencies look wrong.

Neil Carter

I'm sorry, but I don't understand what that indicates.

None of the services, muxes, etc, have been changed, to my knowledge, in well over two years.

Should I delete everything and start over? What would have prompted this need?

Thanks!

mpmc

You need to make sure the frequencies are correct & 79.028 seems far too low for TV..

I'm not sure it's the same for Cable in the US but here in the UK I have to enter frequencies like 123000000 for DVB-T try adding a mux with additional zeros, e.g. 491028000.

Neil Carter

Greetings:

Attached are my latest syslog as well as the screenshots I took prior to performing the following steps. I deleted all of the services and muxes on my system, then added the muxes manually. The system populated the services itself as I was adding the muxes, so I think this means the system is able to receive signals.

However, the Scan Result column of the Muxes tab shows 'Fail' for all of the muxes.

So, the system can create services from the manually entered muxes, but can't scan those muxes?

Hope this helps clarify.

Thanks!!