Kodi Community Forum
OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Printable Version

+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: Raspberry Pi (https://forum.kodi.tv/forumdisplay.php?fid=166)
+---- Thread: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) (/showthread.php?tid=231092)



RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - popcornmix - 2015-12-05

(2015-12-05, 20:56)nalor Wrote: I analyzed the aacs.c a little bit and I think I know where it crashed - there's a division by zero in one of the procedures because of the len=0 return value.

But I think we need to decide what the result of those fixes should be - should the iso finally play? After fixing the code above libaacs finally exits with 'AACS_ERROR_CORRUPTED_DISC' because the disc contains an AACS folder - but no valid AACS data....

So I think in the end all we can reach is that nothing is crashing, but as the disc is still corrupt it won't play Sad

Ideally it should behave the same as it does when libaacs is not present.
The disk is playable on the Pi - at least with 3D/MVC enabled where we just play the ssif file.


RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - afremont - 2015-12-05

@popcornmix
Was the debug log file of any help?


OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - Caramba69 - 2015-12-06

(2015-12-05, 19:06)niwa2 Wrote:
(2015-12-05, 18:37)popcornmix Wrote:
Quote:I tried this as well on #1204 with the same result. But #1204 does not play anything in 3D. With #1203 3D is working fine.
I don't see anything 3D related in changes for #1204. Can you double check? If still a problem,
then a more detailed description of exactly how it doesn't work and a debug log (wiki) would be useful.

ok i double checked and 1204 really does not play 3d.
I played a 3d iso on 1203 in 3d.
Then updated to 1204 without changeing any settings and the same movie starts in 2d. I do not get the prompt that asks me with 3d mode i prefere. Also when i press m while playing the movie, the 3d icon next to the audio and video settings is missing in 1204.
Downgrade to 1203 and the same movie plays in 3d again.
Here is the log of 1204 with broken 3d:
http://xbmclogs.com/pp9emem6e

And here is a log of 1203 with working 3d:
http://xbmclogs.com/pmlbue7gz

Same problem with 3D here as well.


RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - motorherz - 2015-12-06

(2015-12-02, 23:55)motorherz Wrote:
(2015-12-02, 22:41)popcornmix Wrote:
(2015-12-02, 22:26)motorherz Wrote: I've changed all settings as you adviced. My testvideo: "edge of tomorrow". When playing now, my projector tells me, that 1080p/24fp mode is activated. But no audio. Now I left all adviced settings and went back to DESKTOP, the projector shows: 1080i/60sbs and I have audio.
So, here are the messages from "tvservice -s":

when I play the video with the 1080p setting: (no audio)
state 0x12000a [HDMI CEA (32) 3D FP RGB lim 16:9], 1920x1080 @ 23.98Hz, progressive

when I play the video with the DESKTOP setting: (with audio)
state 0x12000a [HDMI CEA (5) 3D SbS RGB lim 16:9], 1920x1080 @ 60.00Hz, interlaced

Don't use DESKTOP. Your scaler is wrong in reporting 1080i as its preferred resolution, so you should override that. Set it to 1080p and framerate to 60.
How does it behave if you enable/disable passthrough? With passthrough disabled any different with number of channels set to 5.1 or 2.0?
Any different with omxplayer enabled/disabled?
How does it behave with "Use Full HD modes for 3D" disabled?

I tested all your advices separateley. In all modes I have no audio. In all modes (except the mode below) the projector shows 1080p/24(FP).

when I enable OMXplayer and disable MMAL player and disable "use full HD modes for 3D", my projector tels me 1080p/50(sbs). This must be true, because the screen size is changed smaller. no audio.

Should I try some other combinations with the setting OMXplayer enabled? What do you need?

Hi Popcornmix, do you have any ideas for this problem?
in the meanwhile, I removed the 1080i-mode in the EDIT-setup from the LUMAGEN scaler, but this had not any effects... So i must switch back to the DESKTOP mode to have HD-audio :-(


RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - doveman2 - 2015-12-07

Still having major problems with my brother's Kworld Freeview tuner on his RPi v2.

I updated to #1204 with TVh #1205 and it works fine on my end, with just the tuner plugged into the RPi and an empty Belkin USB Hub. My brother's using an old composite TV though, so he can't use CEC and has to use a USB remote and would also quite like to use a USB flash drive for recording TV programmes.

My brother had the remote receiver and the flash drive plugged into his RPi and the tuner plugged into the hub. After updating him (and adding max_usb_current=1 to config.txt) the tuner wasn't visible. This is the dmesg.
http://pastebin.com/QkaUnsCz

Then I got him to plug the tuner directly into the RPi and put the remote receiver and flash drive in the hub, disconnect the hub and reboot. Then the tuner showed up in dmesg and in the TVh web GUI under Adapters. http://pastebin.com/xSsNTrSK

Then I got him to plug the remote receiver into the RPi and reboot and the tuner wasn't working again. http://pastebin.com/wauCpEt6

In all three instances dmesg shows "1-1.2: Product: DVB-T TV Stick" but after that the first and third tests show
usb 1-1.2: dvb_usb_v2: 2nd usb_bulk_msg() failed=-110
dvb_usb_af9035: probe of 1-1.2:1.0 failed with error -110

whilst the second shows:
usb 1-1.2: dvb_usb_af9035: prechip_version=83 chip_version=01 chip_type=9135
usb 1-1.2: dvb_usb_v2: found a 'Kworld UB499-2T T09' in cold state
usb 1-1.2: dvb_usb_v2: downloading firmware from file 'dvb-usb-it9135-01.fw'

and a lot more messages relating to the tuner. I've already sent him a spare tuner which I tested (as in fact I had the first one, with his RPi v2 before I gave it to him) so I'm sure the tuner isn't faulty but I haven't got a clue what's wrong and it's driving me nuts!


RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - gendo - 2015-12-07

Have similar problem with mine which is a generic chinese tuner... I fails on first init but is fine on second..

[ 8.994637] usb 1-1.4.3: dvb_usb_v2: 2nd usb_bulk_msg() failed=-110
[ 8.994684] dvb_usb_af9035: probe of 1-1.4.3:1.0 failed with error -110

Worked around it by adding the following to autostart.sh

#! /bin/sh
(sleep 10;
rmmod dvb_usb_af9035
modprobe dvb_usb_af9035) &

now it works fine after a reboot
[ 8.994637] usb 1-1.4.3: dvb_usb_v2: 2nd usb_bulk_msg() failed=-110
[ 8.994684] dvb_usb_af9035: probe of 1-1.4.3:1.0 failed with error -110
[ 8.994807] usbcore: registered new interface driver dvb_usb_af9035
[ 9.742701] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
[ 9.742903] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 11.321709] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 11.322988] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[ 11.341166] 8021q: 802.1Q VLAN Support v1.8
[ 19.567540] usbcore: deregistering interface driver dvb_usb_af9035
[ 19.590565] usb 1-1.4.3: dvb_usb_af9035: prechip_version=83 chip_version=02 chip_type=9135
[ 19.591028] usb 1-1.4.3: dvb_usb_v2: found a 'ITE 9135 Generic' in cold state
[ 19.604032] usb 1-1.4.3: dvb_usb_v2: downloading firmware from file 'dvb-usb-it9135-02.fw'
[ 19.699710] usb 1-1.4.3: dvb_usb_af9035: firmware version=3.40.1.0
[ 19.699749] usb 1-1.4.3: dvb_usb_v2: found a 'ITE 9135 Generic' in warm state
[ 19.700981] usb 1-1.4.3: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
[ 19.701127] DVB: registering new adapter (ITE 9135 Generic)
[ 19.722186] af9033 3-0038: firmware version: LINK 3.40.1.0 - OFDM 3.40.1.0
[ 19.722215] af9033 3-0038: Afatech AF9033 successfully attached
[ 19.722286] usb 1-1.4.3: DVB: registering adapter 0 frontend 0 (Afatech AF9033 (DVB-T))...
[ 19.752513] it913x 3-001c: ITE IT913X BX successfully attached
[ 19.797984] Registered IR keymap rc-it913x-v1
[ 19.798479] input: ITE 9135 Generic as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4/1-1.4.3/rc/rc1/input3
[ 19.802210] rc1: ITE 9135 Generic as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4/1-1.4.3/rc/rc1
[ 19.802248] usb 1-1.4.3: dvb_usb_v2: schedule remote query interval to 500 msecs
[ 19.802265] usb 1-1.4.3: dvb_usb_v2: 'ITE 9135 Generic' successfully initialized and connected
[ 19.802442] usbcore: registered new interface driver dvb_usb_af9035
[ 21.619810] usb 1-1.4.3: DVB: adapter 0 frontend 0 frequency 0 out of range (174000000..862000000)



(2015-12-07, 00:03)doveman2 Wrote: Still having major problems with my brother's Kworld Freeview tuner on his RPi v2.

I updated to #1204 with TVh #1205 and it works fine on my end, with just the tuner plugged into the RPi and an empty Belkin USB Hub. My brother's using an old composite TV though, so he can't use CEC and has to use a USB remote and would also quite like to use a USB flash drive for recording TV programmes.

My brother had the remote receiver and the flash drive plugged into his RPi and the tuner plugged into the hub. After updating him (and adding max_usb_current=1 to config.txt) the tuner wasn't visible. This is the dmesg.
http://pastebin.com/QkaUnsCz

Then I got him to plug the tuner directly into the RPi and put the remote receiver and flash drive in the hub, disconnect the hub and reboot. Then the tuner showed up in dmesg and in the TVh web GUI under Adapters. http://pastebin.com/xSsNTrSK

Then I got him to plug the remote receiver into the RPi and reboot and the tuner wasn't working again. http://pastebin.com/wauCpEt6

In all three instances dmesg shows "1-1.2: Product: DVB-T TV Stick" but after that the first and third tests show
usb 1-1.2: dvb_usb_v2: 2nd usb_bulk_msg() failed=-110
dvb_usb_af9035: probe of 1-1.2:1.0 failed with error -110

whilst the second shows:
usb 1-1.2: dvb_usb_af9035: prechip_version=83 chip_version=01 chip_type=9135
usb 1-1.2: dvb_usb_v2: found a 'Kworld UB499-2T T09' in cold state
usb 1-1.2: dvb_usb_v2: downloading firmware from file 'dvb-usb-it9135-01.fw'

and a lot more messages relating to the tuner. I've already sent him a spare tuner which I tested (as in fact I had the first one, with his RPi v2 before I gave it to him) so I'm sure the tuner isn't faulty but I haven't got a clue what's wrong and it's driving me nuts!



RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - doveman2 - 2015-12-07

Thanks gendo, I'll try that and hopefully it will do the trick. Although I don't seem to have the problem with my own RPi v2 and the same tuner, it appears that it mainly occurs with other devices connected, which I don't have currently. Having said that, I have had some intermittent issues with the tuner disappearing randomly (not after booting but just when I go to use it I find it's disappeared) so hopefully your workaround will help with that.

EDIT: How do I check that autostart.sh has worked? If I run dmesg it ends at [ 9.956804] so doesn't show the tuner being re-initialised.


RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - niwa2 - 2015-12-07

(2015-12-05, 19:06)niwa2 Wrote:
(2015-12-05, 18:37)popcornmix Wrote:
Quote:I tried this as well on #1204 with the same result. But #1204 does not play anything in 3D. With #1203 3D is working fine.
I don't see anything 3D related in changes for #1204. Can you double check? If still a problem,
then a more detailed description of exactly how it doesn't work and a debug log (wiki) would be useful.

ok i double checked and 1204 really does not play 3d.
I played a 3d iso on 1203 in 3d.
Then updated to 1204 without changeing any settings and the same movie starts in 2d. I do not get the prompt that asks me with 3d mode i prefere. Also when i press m while playing the movie, the 3d icon next to the audio and video settings is missing in 1204.
Downgrade to 1203 and the same movie plays in 3d again.
Here is the log of 1204 with broken 3d:
http://xbmclogs.com/pp9emem6e

And here is a log of 1203 with working 3d:
http://xbmclogs.com/pmlbue7gz

I also noticed, that the configured delay between switching the refreshrate and starting the movie does not work as well.

And another question:
Since the PI cannot bitstream HD audio. Is it possible to configure Kodi so that everything is passed through BUT HD audio, which schould be decoded to LPCM?
While this seems to be working for TRUE HD it is not for DTS-HD MA. With a DTS-HD MA track the DTS core gets passed through.


RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - gendo - 2015-12-07

no probably did not work then.. autostart.sh must be in /storage/.config/ and make sure that it is executable by using chmod +x autostart.sh



(2015-12-07, 12:02)doveman2 Wrote: Thanks gendo, I'll try that and hopefully it will do the trick. Although I don't seem to have the problem with my own RPi v2 and the same tuner, it appears that it mainly occurs with other devices connected, which I don't have currently. Having said that, I have had some intermittent issues with the tuner disappearing randomly (not after booting but just when I go to use it I find it's disappeared) so hopefully your workaround will help with that.

EDIT: How do I check that autostart.sh has worked? If I run dmesg it ends at [ 9.956804] so doesn't show the tuner being re-initialised.



RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - doveman2 - 2015-12-07

(2015-12-07, 12:12)gendo Wrote: no probably did not work then.. autostart.sh must be in /storage/.config/ and make sure that it is executable by using chmod +x autostart.sh

Check on both. I created it with WinSCP and added the x bit using that but checked it at the commandline and ran chmod to doublecheck.

The contents of autostart.sh are exactly:

#! /bin/sh
(sleep 10;
rmmod dvb_usb_af9035
modprobe dvb_usb_af9035) &

EDIT: If I manually run rmmod dvb_usb_af9035 I get "Error - Module is in use" which is OK as it initialised properly already.If I run modprobe dvb_usb_af9035 it doesn't return any output and doesn't add anything to dmesg but maybe that's normal when the module is already initialised as well?


RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - gendo - 2015-12-07

Yes if initialized correctly rmmod will give that output, its normal... did you try it on the pii giving problems??

(2015-12-07, 12:21)doveman2 Wrote:
(2015-12-07, 12:12)gendo Wrote: no probably did not work then.. autostart.sh must be in /storage/.config/ and make sure that it is executable by using chmod +x autostart.sh

Check on both. I created it with WinSCP and added the x bit using that but checked it at the commandline and ran chmod to doublecheck.

The contents of autostart.sh are exactly:

#! /bin/sh
(sleep 10;
rmmod dvb_usb_af9035
modprobe dvb_usb_af9035) &

EDIT: If I manually run rmmod dvb_usb_af9035 I get "Error - Module is in use" which is OK as it initialised properly already.If I run modprobe dvb_usb_af9035 it doesn't return any output and doesn't add anything to dmesg but maybe that's normal when the module is already initialised as well?



RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - doveman2 - 2015-12-07

No, haven't tried on my brother's Pi yet as I need to arrange to Team viewer to his PC to do that, so I thought I'd try it on mine in the meantime to make sure I've got it right and check if I still get any instances of the tuner disappearing. Should modprobe produce any output on the command line or in dmesg?


RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - gendo - 2015-12-07

(2015-12-07, 15:15)doveman2 Wrote: No, haven't tried on my brother's Pi yet as I need to arrange to Team viewer to his PC to do that, so I thought I'd try it on mine in the meantime to make sure I've got it right and check if I still get any instances of the tuner disappearing. Should modprobe produce any output on the command line or in dmesg?

no output..


RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - J_E_F_F - 2015-12-07

(2015-10-05, 20:40)J_E_F_F Wrote: RPi2 fails to connect to USB SMB Share when moved from direct USB port to USB hub.
I use SMB share from a Win8.1 file server.
The SMB share drive letter does not change (D:\) and the SMB address does not change (smb://192.168.xxx.xxx/Video/)
A windows build of Kodi handles this fine, the RPi2 fails to open files.
Moving the USB drive from the hub back to a direct connection fixes the problem.
Very odd.

Finally found a resolution to this problem.

Edit or create IRPStackSize in the Windows registry.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanServer\Parameters

1. Locate IRPStackSize
2. If this value does not exist Right Click on Parameters key and Click on New > Dword Value and type in IRPStackSize under the name.
3. The name of the value must be exactly (combination of uppercase and lowercase letters) the same as what I have above.
4. Right Click on the IRPStackSize and click on Modify
5. Select Decimal enter a value higher than 15(Maximum Value is 50 decimal) and Click Ok (I used 50)
8. You can close the registry editor and restart your computer.


RE: OpenELEC Testbuilds for RaspberryPi (Kodi 16.0) - username145 - 2015-12-08

(2015-12-05, 12:49)Milhouse Wrote:
(2015-12-05, 06:14)username145 Wrote: Any chance we could get this in these builds? Doesn't look like it will make it into Jarvis: 7020 (PR)

No chance, I'm afraid - too many issues, disagreement, plus it's now locked and hasn't been updated for almost 6 months. At the moment it it doesn't look like it will make it into any release, Jarvis or K* - perhaps if it's ever unlocked, rebased and cleaned up then it can be reconsidered...

Yeah I thought it might be a long shot when looking through some of the comments, thanks anyway.

For anyone who wants to run two PVR backends though, using a skin with an intro animation/video makes it work, probably because it gives time for them both to load. The Arctic: Zephyr skin works for me