Failure to scan
Added by Stephen Galbraith almost 9 years ago
I'm using HTS Tvheadend 4.1
with Silicon Labs i2168 adapter
I'm having difficulty scanning the mixes (for Sutton Coldfield (uk freeview)). It seems to be intermittent... sometimes the scan succeeds, but mostly the scans fail with
2016-01-05 10:10:15.000 mpegts: 650MHz in sutton - tuning on Silicon Labs Si2168 : DVB-T #0
2016-01-05 10:10:15.001 subscription: 0038: "scan" subscribing to mux "650MHz", weight: 6, adapter: "Silicon Labs Si2168 : DVB-T #0", network: "sutton", service: "Raw PID Subscription"
2016-01-05 10:10:20.000 mpegts: 650MHz in sutton - scan no data, failed
(I've called my network sutton - adapters enabled, all mixes enabled).
The previous version I used seemed to work just fine (3.8 I think). Is this a known issue?
Thanks
Replies (11)
RE: Failure to scan - Added by Mark Clarkstone almost 9 years ago
As you can see it's working fine here on 4.1.x
What device and what firmware?
I'm using 4.0.4 4.0.19 doesn't work with the August T210v2.
RE: Failure to scan - Added by Stephen Galbraith almost 9 years ago
Thanks for the response. I'm using this on a pi2,
uname -a
Linux OpenELEC 4.4.0-rc7 #1 SMP Tue Jan 5 09:59:03 GMT 2016 armv7l GNU/Linux
the tuner is an august t210.
The really strange thing is it tuned fine on this version last night. Strange! I'm kinda at a loss to explain.
any help appreciated!
RE: Failure to scan - Added by Stephen Galbraith almost 9 years ago
oh yeah... and the version of tvheadend is HTS Tvheadend 4.1-1258~gb480c92
RE: Failure to scan - Added by Mark Clarkstone almost 9 years ago
I'm using kernel 4.3.0. Have you tried a replug?
RE: Failure to scan - Added by Stephen Galbraith almost 9 years ago
weird... rebuilt from head and it seems to be working again... I'll keep an eye on it to see if it re-occurs. Odd... no ideas why it happened.
RE: Failure to scan - Added by Stephen Galbraith almost 9 years ago
back again.... I could understand it if it was always broken... but on a fresh install it seems to work... how odd.
RE: Failure to scan - Added by Stephen Galbraith almost 9 years ago
still no joy...
In dmesg I see...
[ 8.058654] dvb-usb: schedule remote query interval to 100 msecs.
[ 8.058776] dvb-usb: Mygica T230 DVB-T/T2/C successfully initialized and connected.
[ 8.058898] usbcore: registered new interface driver dvb_usb_cxusb
[ 8.423265] IPv6: ADDRCONF: eth0: link becomes ready
[ 8.430860] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1
[ 8.445400] 8021q: 802.1Q VLAN Support v1.8
[ 10.314071] si2168 3-0064: found a 'Silicon Labs Si2168-B40'
[ 10.325595] si2168 3-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
[ 11.801259] si2168 3-0064: firmware version: 4.0.19
[ 11.811884] si2157 4-0060: found a 'Silicon Labs Si2148-A20'
[ 11.822756] si2157 4-0060: downloading firmware from file 'dvb-tuner-si2158-a20-01.fw'
[ 12.806794] si2157 4-0060: firmware version: 2.1.6
[ 12.806942] usb 1-1.3.2: DVB: adapter 0 frontend 0 frequency 0 out of range (55000000..862000000)
which looks okay (apart from the frequency out of range comment on startup..). So it looks like that's all loaded and recognised. And I can see the adapter in the tvheadend web ui. So again good. Could it be something in the firmware maybe? Anyone know where the dvb firmware is in openelec? (and links to an old version)
Edit...
Well I found the firmware in /lib/firmware.. its readonly mount.. so can't modify it...
RE: Failure to scan - Added by Mark Clarkstone almost 9 years ago
Stephen Galbraith wrote:
still no joy...
In dmesg I see...[ 8.058654] dvb-usb: schedule remote query interval to 100 msecs.
[ 8.058776] dvb-usb: Mygica T230 DVB-T/T2/C successfully initialized and connected.
[ 8.058898] usbcore: registered new interface driver dvb_usb_cxusb
[ 8.423265] IPv6: ADDRCONF: eth0: link becomes ready
[ 8.430860] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1
[ 8.445400] 8021q: 802.1Q VLAN Support v1.8
[ 10.314071] si2168 3-0064: found a 'Silicon Labs Si2168-B40'
[ 10.325595] si2168 3-0064: downloading firmware from file 'dvb-demod-si2168-b40-01.fw'
[ 11.801259] si2168 3-0064: firmware version: 4.0.19
[ 11.811884] si2157 4-0060: found a 'Silicon Labs Si2148-A20'
[ 11.822756] si2157 4-0060: downloading firmware from file 'dvb-tuner-si2158-a20-01.fw'
[ 12.806794] si2157 4-0060: firmware version: 2.1.6
[ 12.806942] usb 1-1.3.2: DVB: adapter 0 frontend 0 frequency 0 out of range (55000000..862000000)which looks okay (apart from the frequency out of range comment on startup..). So it looks like that's all loaded and recognised. And I can see the adapter in the tvheadend web ui. So again good. Could it be something in the firmware maybe? Anyone know where the dvb firmware is in openelec? (and links to an old version)
Edit...
Well I found the firmware in /lib/firmware.. its readonly mount.. so can't modify it...
Looks like the same firmware issue I had then. If you have a spare SD card try installing raspbian using https://github.com/debian-pi/raspbian-ua-netinst & try out the different firmwares.
RE: Failure to scan - Added by Stephen Galbraith almost 9 years ago
That was it!
I downgraded the firmware to 4.0.11 from here http://palosaari.fi/linux/v4l-dvb/firmware/Si2168/Si2168-B40/4.0.11/
OpenElec has a firmware override mechanism...
so if you paste that firmware into /storage/.config/firmware (you may need to make the firmware directory!) it'll be used in preference to the ones in /lib/firmware.
Result!
Thanks all for your help. I'm documenting the solution here in case someone else needs it.
RE: Failure to scan - Added by Mark Clarkstone almost 9 years ago
Stephen Galbraith wrote:
That was it!
I downgraded the firmware to 4.0.11 from here http://palosaari.fi/linux/v4l-dvb/firmware/Si2168/Si2168-B40/4.0.11/
OpenElec has a firmware override mechanism...
so if you paste that firmware into /storage/.config/firmware (you may need to make the firmware directory!) it'll be used in preference to the ones in /lib/firmware.
Result!
Thanks all for your help. I'm documenting the solution here in case someone else needs it.
I'm guessing you found the same thread as I did on the openelec forums, I was looking into whether it still overrides if the firmware version is older.
But anyway glad to hear you got it working, if your mygica/august stick is anything like mine you may get a few errors at the start of the stream so you may want to set skip initial bytes.
RE: Failure to scan - Added by Stephen Galbraith almost 9 years ago
yeah. definitely overrides the firmware if older. On my damsel it now says using driver version 4.0.11 instead of 4.0.19.
Thanks for the advice on the skip initial bytes.