Project

General

Profile

Bug #3483

Scan returns 'scan no data, failed' after upgrade from 3.4.x to 4.0.8-3

Added by Neil Carter almost 9 years ago. Updated almost 9 years ago.

Status:
Invalid
Priority:
Normal
Assignee:
-
Category:
Configuration
Target version:
-
Start date:
2016-01-07
Due date:
% Done:

0%

Estimated time:
Found in version:
4.0.8-3~gc870eb9~wheezy
Affected Versions:

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

tvh_debug.log (436 KB) tvh_debug.log Neil Carter, 2016-01-07 01:03
Muxes.png (95.7 KB) Muxes.png Neil Carter, 2016-01-07 17:54
tvh_debug.log (112 KB) tvh_debug.log Neil Carter, 2016-01-07 17:54
Muxes2.png (101 KB) Muxes2.png Neil Carter, 2016-01-07 17:59
tvh_debug.log (140 KB) tvh_debug.log Neil Carter, 2016-01-07 18:03

History

#1

Updated by Jaroslav Kysela almost 9 years ago

Could you provide '--trace linuxdvb' ? https://tvheadend.org/projects/tvheadend/wiki/Traces

Also, add a screenshot of your mux settings (only the mux edit window).

#2

Updated by Neil Carter almost 9 years ago

I hope this is what you're after. I used 'The second way' to gather.

Thanks!!

#3

Updated by Jaroslav Kysela almost 9 years ago

Ok, could you add mpegts to trace ('linuxdvb,mpegts') ?

#4

Updated by Neil Carter almost 9 years ago

Maybe this is what you wanted to see.

#5

Updated by Neil Carter almost 9 years ago

new one

#6

Updated by Jaroslav Kysela almost 9 years ago

Have you tried to force modulation to 8VSB ?

#7

Updated by Neil Carter almost 9 years ago

Sorry, 8VSB? I'm recording DVB in the US and am not familiar with 8VSB.

Please explain.

Thanks!!

#9

Updated by Neil Carter almost 9 years ago

OK, but how do I try 'to force modulation to 8VSB'?

I'm not finding anything on your website about8VSB other than the term in several network names.

Thanks!

#10

Updated by Jaroslav Kysela almost 9 years ago

It's mux tuning parameter - see your picture in comment number 4:

Click on modulation combobox...

#11

Updated by Neil Carter almost 9 years ago

Nope, sorry.

Same result.

#12

Updated by Neil Carter almost 9 years ago

WAIT!!!

As it happens, SOME of the Muxes DID scan successfully. And, it appears I'm able to record on at least one of them.

So, does this mean the 'AUTO' setting, in this case, is either defective or just not a good idea?

Thanks!!

Neil

#13

Updated by Neil Carter almost 9 years ago

Greetings:

I now have 19 of 21 desired channels working. So I thank you TREMENDOUSLY!!!!

Of course, this means I still have two channels that are AWOL.

According to my TV, they are both on 599MHZ and 8VSB with a signal strength of 87(I assume out of 100). Just as good a signal as most of the other channels. They are channels 5.1 and 5.7. They are the only channels that should be available on the 599MHz mux.

I've tried several variations in the mux config, but they continue to throw the 'scan no data, failed' error in the syslog.

Is there anything in the earlier debug logs for this mux that shows a different issue?

Please advise.

Thanks!!

Neil

#14

Updated by Jaroslav Kysela almost 9 years ago

According this: https://git.linuxtv.org/dtv-scan-tables.git/tree/atsc/us-ATSC-center-frequencies-8VSB , the center frequency should be 599028615 Hz, try to set this.

There's not much to set. Do you see a signal level in the status tab ?

#15

Updated by Neil Carter almost 9 years ago

Greetings:

Thank you for your continued assistance!

I set that frequency in the mux settings, then clicked Force Scan on the Network tab while watching the Status/Stream tab in another browser window. I currently have ten muxes configured, so I watch the Muxes tab while the scan is running, paying attention to the Signal Strength column. All of the muxes return a 71% Signal Strength reading, including the now 599.028MHz mux.

The syslog file at first received a 'scan no data, failed' message and the Scan Status column still showed 'Fail', for a couple of minutes. Then it changed to 'OK'. I looked on the Services tab and two new services were listed which are the two missing channels. Hallelujah!

The final entry in the syslog file reads:

Jan 8 18:30:24 carter-pi tvheadend4536: subscription: 0049: "scan" subscribing to mux "599.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 8 18:30:29 carter-pi tvheadend4536: mpegts: 599.028MHz in _dev_dvb_adapter0_Auvitek_AU8522_QAM_8VSB_Frontend - scan complete
Jan 8 18:30:29 carter-pi tvheadend4536: subscription: 0049: "scan" unsubscribing

Woohoo!!

At this time, my system is working as I think it should! Thank you, thank you, thank you!!!

My only question would have to do with the default 'AUTO' setting for the Modulation, and why it completely failed in this situation. Maybe I'm expecting too much.

In any case, I can't thank you enough!

Thanks you!!

Neil

#16

Updated by Mark Clarkstone almost 9 years ago

Neil Carter wrote:

Greetings:

Thank you for your continued assistance!

I set that frequency in the mux settings, then clicked Force Scan on the Network tab while watching the Status/Stream tab in another browser window. I currently have ten muxes configured, so I watch the Muxes tab while the scan is running, paying attention to the Signal Strength column. All of the muxes return a 71% Signal Strength reading, including the now 599.028MHz mux.

The syslog file at first received a 'scan no data, failed' message and the Scan Status column still showed 'Fail', for a couple of minutes. Then it changed to 'OK'. I looked on the Services tab and two new services were listed which are the two missing channels. Hallelujah!

The final entry in the syslog file reads:

Jan 8 18:30:24 carter-pi tvheadend4536: subscription: 0049: "scan" subscribing to mux "599.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 8 18:30:29 carter-pi tvheadend4536: mpegts: 599.028MHz in _dev_dvb_adapter0_Auvitek_AU8522_QAM_8VSB_Frontend - scan complete
Jan 8 18:30:29 carter-pi tvheadend4536: subscription: 0049: "scan" unsubscribing

Woohoo!!

At this time, my system is working as I think it should! Thank you, thank you, thank you!!!

My only question would have to do with the default 'AUTO' setting for the Modulation, and why it completely failed in this situation. Maybe I'm expecting too much.

In any case, I can't thank you enough!

Thanks you!!

Neil

Some drivers expect exact values in order to correctly scan a frequency. I have the same problem with a number of sticks.

#17

Updated by Jaroslav Kysela almost 9 years ago

  • Status changed from New to Invalid

Neil Carter wrote:

My only question would have to do with the default 'AUTO' setting for the Modulation, and why it completely failed in this situation. Maybe I'm expecting too much.

This is definitely the bug or missing part in the linux driver code. This settings is just passed without any modification to the linux driver. I don't know the source of your mux settings (did you use the predefined muxes?). At least for US central frequency settings, the modulation is set to 8VSB in latest tvheadend for predefined muxes (not sure if it's same in tvh 4.0.x - sorry, working with latest 4.1.x only).

#18

Updated by Neil Carter almost 9 years ago

I entered the mux data manually as there are no predefined muxes for my area available, as far as I could find. The odd thing was that the other channels did no thave this issue. No worries!

Again, thanks very much for your help with this!!

Neil

Also available in: Atom PDF