Bug #3483
closedScan returns 'scan no data, failed' after upgrade from 3.4.x to 4.0.8-3
0%
Description
Greetings:
I'm not sure how much detail you need/want here. I've got a Raspberry Pi(B+) that's been serving me well as a DVR for the past year or so. Late December, I ran my usual monthly sudo apt-get update/sudo apt-get dist-upgrade. I didn't notice(doh!) that this would install a new version of tvheadend until it was done. My DVR has not been working since. I worked my way through the config under the new system(most had been pulled forward), but it still fails to work. After much frustration and lots of Googling, I opened a post on your Forum(https://tvheadend.org/boards/5/topics/19282). No luck here, so I added onto another post about the same basic issue(https://tvheadend.org/boards/4/topics/18637). In this thread, Mark Clarkstone has finally suggested I open this ticket. Part way through the frustration part, I blew away my existing Muxes and Services. I then began re-creating my Muxes. While I was doing this, the system was adding Services for these Muxes. This leads me to believe the tuner and much of the system is working. I'm using a Hauppauge WinTV-HVR Hybrid TV Stick(950Q) for my tuner. When I run a Force Scan on the Network tab, the syslog shows one entry for each Mux as follows:
Jan 6 17:55:19 carter-pi tvheadend2034: mpegts: 485.028MHz in _dev_dvb_adapter0_Auvitek_AU8522_QAM_8VSB_Frontend - tuning on Auvitek AU8522 QAM/8VSB Frontend : ATSC #0
Jan 6 17:55:24 carter-pi tvheadend2034: subscription: 0018: "scan" subscribing to mux "485.028MHz", weight: 6, adapter: "Auvitek AU8522 QAM/8VSB Frontend : ATSC #0", network: "_dev_dvb_adapter0_Auvitek_AU8522_QAM_8VSB_Frontend", service: "Raw PID Subscription"
Jan 6 17:55:24 carter-pi kernel: [82185.323860] xc5000: Firmware dvb-fe-xc5000c-4.1.30.7.fw loaded and running.
Jan 6 17:55:24 carter-pi tvheadend2034: mpegts: 485.028MHz in _dev_dvb_adapter0_Auvitek_AU8522_QAM_8VSB_Frontend - scan no data, failed
Jan 6 17:55:24 carter-pi tvheadend2034: subscription: 0018: "scan" unsubscribing
So, hopefully this syslog and/or debug log will be able to point out either what I've got set incorrectly, or where there is a bug that needs to be fixed.
Apologies if I've selected an incorrect category or whatever.
Thanks SO much!!
Neil
Files