•   
  • 1
  • 162
  • 163
  • 164(current)
  • 165
  • 166
  • 168
  •   
  Thread Closed
OpenELEC Testbuilds for RaspberryPi (Kodi 16.0)
(2015-12-10, 14:42)Milhouse Wrote: There should be no space between ! and /

(2015-12-10, 14:12)doveman2 Wrote: : not found# .config/autostart.sh: line 6:

Save the autostart.sh file in Unix format - don't save it with Windows line endings. Use an editor like Notepad++ or TextPad that understand Unix line endings. Or use vi or nano to create the file in ssh on the Pi itself.

I'm using Notepad++. I'm pretty sure I copied this exactly from gendo's post but I've removed the space between ! and / now and still get the same output when I run autostart.sh.

I even tried opening it with nano and saving it, both with and without pressing return to go to a newline after the last command and now when I run it I get

: not foundostart.sh: line 6:

EDIT: OK, if I create a file from scratch with nano it works and gives

rmmod: ERROR: Module dvb_usb_af9035 is in use
modprobe

so it seems I can't even use Notepad++ to create these files.

After rebooting "journalctl --no-pager | grep autostart" still doesn't produce any output but "systemctl status kodi-autostart" now gives me

â kodi-autostart.service - Kodi user autostart script
Loaded: loaded (/usr/lib/systemd/system/kodi-autostart.service; disabled; vendor preset: enabled)
Active: active (exited) since Thu 1970-01-01 01:00:04 BST; 45 years 11 months ago
Process: 332 ExecStart=/bin/sh -c . /etc/profile; exec /bin/sh /storage/.config/autostart.sh (code=exited, status=0/SUCCESS)
Main PID: 332 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/kodi-autostart.service

Dec 10 13:12:07 OpenELEC sh[332]: rmmod
Dec 10 13:12:07 OpenELEC sh[332]: rmmod: ERROR: Module dvb_usb_af9035 is in use
Dec 10 13:12:07 OpenELEC sh[332]: modprobe
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
Hint: Some lines were ellipsized, use -l to show in full.

so it seems to be running properly now.
Still having problems with scanning/updating and playback. I'm on #1204 currently and using the same Hanewin NFS server that I've always used without any problem until recently.

Scan was started at 23:29:12 and got stuck on "Preparing" for ages but eventually worked. Then I played a bit of Marvels Episode 10, stopped it and played Ep.9, then went to play Ep.10 again at 00:03:13 and just got the spinner for a while before "Playback failed" at 00:04:35.

Log (8MB): https://drive.google.com/file/d/0B1fDI89...sp=sharing
No new build (since 04/12) ?
  • Raspberry Pi 3 - Libreelec 9.0.1
  • Odroid C2 - Libreelec 8.2.5 & Libreelec 9.0.1
You have to change to the kodi 17 test build thread.
looks like mine... shoudl work..

(2015-12-10, 14:59)doveman2 Wrote:
(2015-12-10, 14:17)gendo Wrote: doveman output of lsmod please..

Module Size Used by
rc_it913x_v1 1065 0
it913x 3720 2
regmap_i2c 2753 1 it913x
af9033 26349 2
8021q 15840 0
dvb_usb_af9035 15956 2
dvb_usb_v2 12163 1 dvb_usb_af9035
dvb_core 75397 1 dvb_usb_v2
rc_core 14676 4 rc_it913x_v1,dvb_usb_v2,dvb_usb_af9035
bcm2835_wdt 2713 0
bcm2835_gpiomem 2652 0
(2015-12-13, 12:17)gendo Wrote: looks like mine... shoudl work..

Thanks. I had time to set the autostart.sh up on my brother's Pi yesterday and when I ran it there was no "ERROR: Module dvb_usb_af9035 is in use" message, which confirms it wasn't working. After I'd run it, the tuner was properly detected in TVh, so hopefully your advice has solved the problem Smile
(2015-12-11, 02:28)doveman2 Wrote: Still having problems with scanning/updating and playback. I'm on #1204 currently and using the same Hanewin NFS server that I've always used without any problem until recently.

Scan was started at 23:29:12 and got stuck on "Preparing" for ages but eventually worked. Then I played a bit of Marvels Episode 10, stopped it and played Ep.9, then went to play Ep.10 again at 00:03:13 and just got the spinner for a while before "Playback failed" at 00:04:35.

Log (8MB): https://drive.google.com/file/d/0B1fDI89...sp=sharing

I've dropped back to #1128 to try and work out when this problem started and it's happening with that too (at least the long Preparing bit is). I also found that CEC wasn't working, which seems to happen if the Pi input on the TV doesn't have focus when booting.

This is the non-working CEC log. I zipped it down to 830KB from 16MB! It's possible the CEC was working at boot and stopped later as I hadn't touched it after updating and rebooting until now but it seems more likely that it wasn't working due to the lack of focus when booting https://drive.google.com/file/d/0B1fDI89...sp=sharing

This is the preparing bug log. Only 328KB this one, as I'd just rebooted. https://drive.google.com/file/d/0B1fDI89...sp=sharing
In your #1128 and #1204 logs:
Code:
23:29:12 37038.968750 T:1625289632  NOTICE: VideoInfoScanner: Starting scan ..
23:29:12 37038.968750 T:1625289632   DEBUG: CAnnouncementManager - Announcement: OnScanStarted from xbmc
23:29:12 37038.968750 T:1625289632   DEBUG: GOT ANNOUNCEMENT, type: 16, from xbmc, message OnScanStarted
23:29:12 37038.968750 T:1625289632   DEBUG: AddOnLog: Tvheadend HTSP Client: pvr.hts - Announce(flag=VideoLibrary, sender=xbmc, message=OnScanStarted)
23:29:12 37038.968750 T:1625289632  NOTICE: WakeOnAccess [192.168.1.64] trigged by accessing : nfs://192.168.1.64/Media/Videos/Movies to Watch/
23:29:13 37040.000000 T:1625289632    INFO: WakeOnLan - Magic packet send to '10:C3:7B:6D:51:A2'
...
23:30:34 37121.117188 T:1625289632  NOTICE: WakeOnAccess timeout/cancel while waiting for response
23:30:34 37121.117188 T:1625289632 WARNING: WakeOnAccess failed to bring up [192.168.1.64] - there may be trouble ahead !
23:30:34 37121.117188 T:1625289632   ERROR: Exists - Error checking for nfs://192.168.1.64/Media/Videos/Movies to Watch/
23:30:34 37121.117188 T:1625289632 WARNING: Process directory 'nfs://192.168.1.64/Media/Videos/Movies to Watch/' does not exist - skipping scan.

So it looks like a WakeOnAccess issue. Can you try with a build which doesn't include PR7030, ie. #1202b (or with build #1204, disable WakeOnAccess support, turn on the server 192.168.1.64 and perform another scan - do you still have the delay?)

Finally, test with the latest build #1213 as PR7030 has been updated since build #1204, with updated WOL support.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
(2015-12-13, 11:52)nalor Wrote: You have to change to the kodi 17 test build thread.

Yeah I saw that thanks
I'm already using the Kodi 17

Was just wondering since Kodi is still not final and Kodi 17 is in early alpha
  • Raspberry Pi 3 - Libreelec 9.0.1
  • Odroid C2 - Libreelec 8.2.5 & Libreelec 9.0.1
(2015-12-09, 23:36)slymobi Wrote: Hi, I think I'm in the right place ! Just installed the latest version via Leopold dev add-on and all is good on the system, the GUI is so smooth and responsive its like coming from pi to pi2 all over again Wink I have no playback issues or anything but what I am having issues with and unable to find any reports on is CEC. All versions upto Jarvis have worked perfect with my Samsung remote via CEC but after initial install of Jarvis it just won't work.
I install Jarvis and CEC remote works,so I set everything up and then after a reboot my CEC remote becomes...... Unresponsive only when I hard reset will CEC return. Has anyone had similar issue ?

Regards.
This keeps happening but I have found a solution.... If I switch off the pi via shutdown and the switch off my TV from the mains, turn TV on and then pi its resolved and CEC is back to normal. Wink
Using Tapatalk
(2015-12-14, 17:35)slymobi Wrote: This keeps happening but I have found a solution.... If I switch off the pi via shutdown and the switch off my TV from the mains, turn TV on and then pi its resolved and CEC is back to normal. Wink

The Pi reads the TV's EDID on boot. This includes the CEC physical address.
Some TVs allow the EDID to be read when powered off (this is possible as the Pi provides 5V through HDMI cable for this purpose).
Some TVs only allow EDID to be read when powered on (and some only if on the correct AV input).

For TVs that don't allow reading the EDID you can capture the EDID to a file:
http://kodi.wiki/view/Raspberry_Pi_FAQ#T...d_on_first

This may help your issue. Make sure you remove or update the setting if you want to use the Pi with a different TV (or you change HDMI input on TV).
(2015-12-14, 08:44)Milhouse Wrote: So it looks like a WakeOnAccess issue. Can you try with a build which doesn't include PR7030, ie. #1202b (or with build #1204, disable WakeOnAccess support, turn on the server 192.168.1.64 and perform another scan - do you still have the delay?)

Finally, test with the latest build #1213 as PR7030 has been updated since build #1204, with updated WOL support.

I tested with #1115, #1202b and #1213 and it's fine with all three. Thanks for your assistance. Note the server (actually my PC) has always been on when testing, so it seems like there was a bug introduced into the WOL support somewhere.

On the CEC issue, I've been using the forced edid.dat for some time now and still have issues with the remote not working occasionally. It's not often enough to be bothersome though. I'll try recreating the file anyway, as I guess it might have got corrupted.
(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
Hello!

Can confirm these findings. Just updated to #1204 because I wanted to try MVC Support -no succes (would only play as 2D). After I read the above, I downgraded to #1203 and it works like a charm. Undecided
I just wanted to let you know, that a maybe new occured bug can be recognized as early as possible!

Cheers and thanks a lot for your great work!!
(2015-12-18, 15:31)HomerJayS Wrote: Can confirm these findings. Just updated to #1204 because I wanted to try MVC Support -no succes (would only play as 2D). After I read the above, I downgraded to #1203 and it works like a charm. Undecided
I just wanted to let you know, that a maybe new occured bug can be recognized as early as possible!

Cheers and thanks a lot for your great work!!

These builds are superceded by Kodi 17 builds. Thy the latest build there and report (on that thread) if there is still a problem.
I am using mysql. If I were to keep my OSX / Win builts on Kodi 16 Beta 4 / RC / stable, what would be the ideal version for OE keeping mysql working. Would this be #1204 above?
Server: Asus Sabertooth Z77 | Intel Core i5 3.4 GHz | 16 GB DDR3 | 128 GB SSD, 82 TB (9 x 6 TB, 7 x 4 TB)
HTPC 1: Raspberry Pi 2 | HTPC 2: Raspberry Pi 2 | HTPC 3: Raspberry Pi
  •   
  • 1
  • 162
  • 163
  • 164(current)
  • 165
  • 166
  • 168
  •   
  Thread Closed
 
Thread Rating:
  • 10 Vote(s) - 5 Average



Logout Mark Read Team Forum Stats Members Help
OpenELEC Testbuilds for RaspberryPi (Kodi 16.0)510