Two upgrades were installed today, but I’ve lost TV (only after the second update, first was ok) and I cannot (re)install tvheadend client add-on (it’s there, but will not install). Is there any way I can get this back? Is anyone else experiencing this problem?
The TVHeadend client does not need to be installed
Please check for updates again and ensure you are up to date
Sam
Hi Sam, after operating the tvheadend (server and client) for several months without any problems, the tvheadend client simply disappeared after the second update today. When I found it again in the add-ons it was not installed. However, it was installed up until the second update. When I tried to install it from the add-ons nothing happened, ie it will not install. I have not found a solution to this problem. So I tried to install xbmc-pvr-tvheadend-hts with apt-get but there is now a version problem:
xbmc-pvr-tvheadend-hts : Depends: xbmc (>= 2:13.1~beta2+dfsg1-1)
So at the moment I cannot get live tv, even though the tvheadend server is working just fine.
Trying to manually update the system as you suggested now to see if this helps.
Hi
No need to install any addons via APT. This won’t work on OSMC.
If you have found it, then it is installed. It may not be enabled however. You should be able to select it and configure it.
Let me know how you get on
Sam
OK. After manually updating as you suggested it reappeared in the add-ons as being installed and enabled. Prior to this update it was not installed, and of course it was not enabled as it was only found by searching. Strangely though Live TV had been disabled in the settings. So after updating and enabling Live TV in the settings, it all works again.
In future if I experience any problems I’ll follow your advice and just make sure the update process is completed manually first.
Thank you for your help and also for your excellent work on this software. I tested OpenElec and OSMC and in my view OSMC is a far better system. It seems to be much lighter on machine resources, as well as being more flexible and configurable.
Ditto, tvheadend is now not working.
History :
- installed OSMC back in March; supplied tvheadend could not get to work (as reported elsewhere)
- installed “tvheadend unstable” (3.9) from tvheadend website & it worked fine for months
- installed 1.0 a month ago, uninstalled “tvheadend unstable” & setup “built-in” version 4.0.5, worked fine 1st time, been running fine for a month
Current Issue :
- applied update on 5 Aug & kodi reports “no free adaptor” so no TV
- checked tvheadend web interface (which I use almost daily to schedule &/or check on recordings);
tvheadend configuration shows nothing in the “DVB Inputs”, “TV Adaptors” tab; the muxes, channels info remain as before - tvheadend web interface operates fine & the EPG happily updates
- tvheadend add-on is version 2.1.16
From kodi.log :
xxxxx ERROR: AddOnLog: Tvheadend HTSP Client: pvr.hts - Command hello failed: No response received
xxxxx ERROR: AddOnLog: Tvheadend HTSP Client: pvr.hts - failed to send hello
xxxxx ERROR: AddOnLog: Tvheadend HTSP Client: pvr.hts - unable to connect to 127.0.0.1:9982
From syslog :
xxxxx osmc kernel: [ 2.869025] usb 1-1.4.3: Product: WinFast Dongle mini D
xxxxx osmc kernel: [ 2.869043] usb 1-1.4.3: Manufacturer: realtek
… a bit later
xxxxx osmc kernel: [ 5.105726] usb 1-1.4.3: dvb_usb_v2: found a ‘Leadtek Winfast DTV Dongle Mini D’ in warm state
xxxxx osmc kernel: [ 5.147784] dvb_usb_rtl28xxu: probe of 1-1.4.3:1.0 failed with error -32
Do I have a driver issue ?
thanks
Wayne
Looks like a possible driver issue. I believe the RTL28xx driver changed in 4.1 as we had to make some changes to some of our patches to it.
Sam
I’ll just mention a couple of things that I’ve experienced that might give you some ideas. Your problem might be entirely different from mine though.
I built and installed TVHeadend from GitHub. A few weeks back, after an update, I found that there was also an OSMC tvheadend server add-on (launch the ‘OSMC Settings’ add-on and check the App Store). The two versions were both installed and appeared to be in conflict (I may have installed them during initial set up and forgot about it). I uninstalled the OSMC version and did another make-install of the custom one. Since then I’ve not had any problems with the tvheadend server.
However the dongle I use is a low priced one that is not fully supported, but still works. Its an August DVB-T202 that is recognized in OSMC as an ITE 9135(9006) Generic Afatech AF9033. I recently installed a wireless (air)mouse and disabled lircd but the wireless mouse dongle and dvb tuner dongle have a conflict. This means that after rebooting OSMC, the tuner does not show up in the tvheadend DVB inputs. I have to remove and reinsert it after rebooting and it works again. I can probably address this problem by altering the module loading sequence but I haven’t got the time at the moment. So as a suggestion you might want to try to hotplug the tuner and see what happens, then do a ‘dmesg’ and ‘sudo lshw’ to see what OSMC reports for your hardware.
My next plan was always going to be swap the “Winfast Mini Dongle D” with a cheap(er) clone RTL28xxx tuner that I have on my PC … just to see what happens.
But you were 1/2 right, hot-plugging resulted in the adaptor re-appearing in the tvheadend web config but kodi reports “no input detected”.
dmesg reports :
[55642.571747] rtl2832 3-0010: i2c reg write failed -32
[55642.576772] rtl2832 3-0010: i2c reg read failed -32
[55642.576820] i2c i2c-4: fc0012: I2C write reg failed, reg: 01, val: 05
[55642.576836] i2c i2c-4: fc0012: fc0012_writereg failed: -121
[55642.576930] usb 1-1.4.3: DVB: adapter 0 frontend 0 frequency 0 out of range (174000000…862000000)
[55642.581870] rtl2832 3-0010: i2c reg read failed -32
[55642.590882] rtl2832 3-0010: i2c reg read failed -32
[55642.593559] rtl2832 3-0010: i2c reg read failed -32
[55642.593622] i2c i2c-4: fc0012: I2C write reg failed, reg: 01, val: 05
[55642.593643] i2c i2c-4: fc0012: fc0012_writereg failed: -121
[55642.597695] rtl2832 3-0010: i2c reg read failed -32
My time window has finished this time so I will try the swap next (ie tomorrow).
Is regressing drivers going to help ?
If there is any more detailed debugging that I can do, am happy to participate but not available for another couple of days.
You’re using a Raspberry Pi, is that correct? For my system, RPi2, ‘dmesg | grep i2c’ doesn’t turn up anything, it’s not needed. Do you need i2c?
Throwing out some ideas…sometimes i2c read/write errors can be caused by faulty connections/inadequate power. Is the Winfast dongle on a powered hub? I’ve seen cases where replacing a cable has solved the problem.
If indeed you do have i2c devices, say /dev/i2c-0 … /dev/i2c-N, where N is the bus number, another suggestion is to ssh into osmc and do ‘sudo apt-get install i2c-tools’ and investigate with i2cdetect. This could give some clues.
Hi - i have the same error messages. Maybe a clue: after the first update tv-headend worked for me…
Sorry, should have said I have a RPi2. Winfast dongle is on a powered hub which seems fine.
dmesg is full of :
[208934.177105] i2c i2c-4: fc0012: I2C write reg failed, reg: 01, val: 05
[208934.177126] i2c i2c-4: fc0012: fc0012_set_params failed: -121
[208934.179623] rtl2832 3-0010: i2c reg read failed -32
[208934.189322] rtl2832 3-0010: i2c reg read failed -32
[208938.184503] rtl2832 3-0010: i2c reg read failed -32
Do not know what an i2c device is … [looks it up] … no /dev/i2c* devices listed.
It is std. RPi2 with SD card plus USB keyboard & mouse plus tuner which is on a powered hub.
My limited understanding of i2c suggests that a RTL2832 USB tuner is not a i2c device so perplexed by above dmesg errors.
While a particular gut feeling says re-install from scratch, (for the challenge/curiosity) I am running a full LXDE desktop environment using RDP to my desktop at the other end of the house. Plus a full Apache/PHP/MYSQL server as a test platform. But none of that “should” have fiddled with devices.
(Note that the challenge/curiosity is also fed by the fact that the Pi as a web server platform saves (within a year) in reduced power costs more than the cost of the Pi itself. I shutdown my 10 year-old clunker unix box which once served that function.)
Now that I have a bit more time, I removed the USB wireless mouse receiver (k/b was not plugged in anyway) & re-plugged all USB plug connections. dmesg seems to happily detect the Winfast now but there is a curious reference to i2c :
[ 2.618980] usb 1-1.2.3: new high-speed USB device number 6 using dwc_otg
[ 2.728941] usb 1-1.2.3: New USB device found, idVendor=0413, idProduct=6f0f
[ 2.728975] usb 1-1.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.728993] usb 1-1.2.3: Product: WinFast Dongle mini D
[ 2.729011] usb 1-1.2.3: Manufacturer: realtek
… LATER …
[ 6.146089] usb 1-1.2.3: dvb_usb_v2: found a ‘Leadtek Winfast DTV Dongle Mini D’ in warm state
[ 6.180239] usb 1-1.2.3: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
[ 6.180484] DVB: registering new adapter (Leadtek Winfast DTV Dongle Mini D)
[ 6.206178] i2c i2c-3: Added multiplexed i2c bus 4
[ 6.206216] rtl2832 3-0010: Realtek RTL2832 successfully attached
[ 6.206273] usb 1-1.2.3: DVB: registering adapter 0 frontend 0 (Realtek RTL2832 (DVB-T))…
[ 6.237205] i2c i2c-4: fc0012: Fitipower FC0012 successfully identified
[ 6.256226] Registered IR keymap rc-empty
[ 6.256982] input: Leadtek Winfast DTV Dongle Mini D as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2.3/rc/rc0/input0
[ 6.257044] rc0: Leadtek Winfast DTV Dongle Mini D as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2/1-1.2.3/rc/rc0
[ 6.266196] IR NEC protocol handler initialized
[ 6.270109] IR RC5(x/sz) protocol handler initialized
[ 6.294886] IR Sony protocol handler initialized
[ 6.295967] IR RC6 protocol handler initialized
[ 6.299272] IR Sharp protocol handler initialized
[ 6.301977] IR SANYO protocol handler initialized
[ 6.301982] IR JVC protocol handler initialized
[ 6.312753] lirc_dev: IR Remote Control driver registered, major 245
[ 6.312951] IR MCE Keyboard/mouse protocol handler initialized
[ 6.313915] input: MCE IR Keyboard/Mouse (dvb_usb_rtl28xxu) as /devices/virtual/input/input1
[ 6.314740] usb 1-1.2.3: dvb_usb_v2: schedule remote query interval to 200 msecs
[ 6.318226] rc rc0: lirc_dev: driver ir-lirc-codec (dvb_usb_rtl28xxu) registered at minor = 0
[ 6.318269] IR LIRC bridge handler initialized
[ 6.323738] IR XMP protocol handler initialized
[ 6.328003] usb 1-1.2.3: dvb_usb_v2: ‘Leadtek Winfast DTV Dongle Mini D’ successfully initialized and connected
[ 6.328226] usbcore: registered new interface driver dvb_usb_rtl28xxu
… LATER …
[ 19.563085] rtl2832 3-0010: i2c reg read failed -32
[ 19.565675] rtl2832 3-0010: i2c reg read failed -32
[ 19.565708] i2c i2c-4: fc0012: I2C write reg failed, reg: 01, val: 05
[ 19.565722] i2c i2c-4: fc0012: fc0012_writereg failed: -121
[ 19.565816] usb 1-1.2.3: DVB: adapter 0 frontend 0 frequency 0 out of range (174000000…862000000)
[ 19.568456] rtl2832 3-0010: i2c reg read failed -32
[ 19.571284] rtl2832 3-0010: i2c reg read failed -32
[ 19.601283] rtl2832 3-0010: i2c reg read failed -32
[ 19.603907] rtl2832 3-0010: i2c reg read failed -32
[ 19.603943] i2c i2c-4: fc0012: I2C write reg failed, reg: 01, val: 05
[ 19.603956] i2c i2c-4: fc0012: fc0012_writereg failed: -121
[ 19.612084] rtl2832 3-0010: i2c reg read failed -32
[ 21.064931] rtl2832 3-0010: i2c reg read failed -32
[ 21.064973] i2c i2c-4: fc0012: I2C write reg failed, reg: 01, val: 04
[ 21.064987] i2c i2c-4: fc0012: fc0012_set_params failed: -121
[ 21.067535] rtl2832 3-0010: i2c reg read failed -32
[ 21.074642] rtl2832 3-0010: i2c reg read failed -32
[ 24.117876] rtl2832 3-0010: i2c reg read failed -32
[ 24.117913] i2c i2c-4: fc0012: I2C write reg failed, reg: 12, val: 00
[ 24.117928] i2c i2c-4: fc0012: fc0012_get_rf_strength failed: -121
[ 24.122027] rtl2832 3-0010: i2c reg read failed -32
[ 24.745383] Console: switching to colour dummy device 80x30
[ 55.339642] rtl2832 3-0010: i2c reg read failed -32
[ 55.339691] i2c i2c-4: fc0012: I2C write reg failed, reg: 01, val: 05
[ 55.339712] i2c i2c-4: fc0012: fc0012_set_params failed: -121
[ 55.342256] rtl2832 3-0010: i2c reg read failed -32
[ 55.351543] rtl2832 3-0010: i2c reg read failed -32
[ 59.346473] rtl2832 3-0010: i2c reg read failed -32
[ 59.346512] i2c i2c-4: fc0012: I2C write reg failed, reg: 12, val: 00
[ 59.346527] i2c i2c-4: fc0012: fc0012_get_rf_strength failed: -121
[ 59.351537] rtl2832 3-0010: i2c reg read failed -32
[ 91.339640] rtl2832 3-0010: i2c reg read failed -32
[ 91.339675] i2c i2c-4: fc0012: I2C write reg failed, reg: 01, val: 05
[ 91.339689] i2c i2c-4: fc0012: fc0012_set_params failed: -121
[ 91.342180] rtl2832 3-0010: i2c reg read failed -32
[ 91.351793] rtl2832 3-0010: i2c reg read failed -32
[ 95.345899] rtl2832 3-0010: i2c reg read failed -32
[ 95.345938] i2c i2c-4: fc0012: I2C write reg failed, reg: 12, val: 00
[ 95.345951] i2c i2c-4: fc0012: fc0012_get_rf_strength failed: -121
Note reference to Fitipower FC0012 identified as an ic2 device. I checked the Winfast (a USB tuner) specs & it includes the Fitipower FC0012 (tuner) and RealTek RTL2832U (demodulator).
Pre-upgrade boots show a similar pattern but slight changes in wording suggest changes were made to driver.
My novice suspicion is directed at the line above “i2c i2c-3: Added multiplexed i2c bus 4” whereas in previous boots, it showed :
i2c i2c-0: Added multiplexed i2c bus 1
i2c i2c-0: Added multiplexed i2c bus 2
There is no /dev/i2c* entry.
Next step is to try my el-cheapo RTL12832 tuner.
Can confirm identical behaviour with generic RTL2832
Except tuner is a “Rafael Micro r820t”
So driver problem is assumed. I am not sure I can go any further without assistance.
I have the same problem, I have 2 RTL2832U+R820T tuners and they have both disappeared from tvhead adapter page.
dmesg gives me a lot of these messages…
[ 13.518830] usb 1-1-port2: over-current change
[ 13.754125] usb 1-1-port2: over-current change
[ 14.288957] usb 1-1-port2: over-current change
[ 14.522252] usb 1-1-port2: over-current change
[ 15.058930] usb 1-1-port2: over-current change
[ 15.290388] usb 1-1-port2: over-current change
[ 15.829040] usb 1-1-port2: over-current change
[ 16.058501] usb 1-1-port2: over-current change
[ 16.599018] usb 1-1-port2: over-current change
[ 16.826613] usb 1-1-port2: over-current change
The only errors I see are…
[ 3.620164] systemd[1]: Job kbd.service/start deleted to break ordering cycle starting with basic.target/start
[ 3.620792] systemd[1]: Job rpcbind.service/start deleted to break ordering cycle starting with basic.target/start
Not sure if thats related.
OK, I got my tuners back in TvHead, I had a DVD rom player that was trying to use too much power, so once I unplugged everything my tuners lit up and are now showing up.
However, I still dont get any TV, it now says “No Input detected”.
I’ll try removing my config and re-adding it.
Ok, deleting my .hts folder didn’t help things, when I tried to re-add everything most of my MUX’s failed doing the scan, and the 2 that didn’t fail, didn’t work either.
Is there a log file that I can send that would be helpful?
It seems that the RTL28xx driver has undergone some changes and is broken. We will need to wait for upstream to fix it.
Sam
Same problem over here.
Could we downgrade the kernel until the fix is ready?