Posts by brianjg

I've had the same issue after upgrading to beta1 from the alpha release. I'll get a picture later. I've a spare SD card too so will see if a clean install resolves it.

I had to download it via the USB creator tool.

I'm having the same issue which means its unusable for me also. Did you manage to get yours any better?

So I'm guessing this has something to do with it but if so its very disappointing. Licence key and codec options in config.txt - Raspberry Pi Documentation

I've been running Intel NUC (Celeron 3000, SSD, 4GB RAM) with a DVBlink backend for sometime now they've been perfect. I purchased a Wetek Play 2 for a 3rd TV installed LE8 via the NAND method.

Watching SD channels is fine but when I try to watch either HD channels live or HD recording I get issues such as the channel fails to load (the buffering counter just keeps spinning) or with recording the image becomes 'jumpy' every few frames.

Again there are no problems watching the same content on the NUCs.

I've attached some logs.

So I managed to set the xrorg values in an autostart.sh script so thats fine on boot up, but the settings don't persist when resuming from sleep.

Anyone?

Is it normal that I'm having to set the xrandr again after resuming from sleep?

I'm trying to set my GPU to limited mode but the setting is lost on sleep/resume. I can manually run the following command it works.

xrandr --output HDMI3 --set "Broadcast RGB" "Limited 16:235"

I then added a script to /storage/.config/sleep.d called 02-gpu.power (I already have another called 01-restart.power which restarts kodi on resume as I've a problem with the dvblink plugin at the moment). The 01- script runs fine each time but the 02- script doesn't seem to be called. If I run 'sh pathtoscript post' it works.

Can anyone point out what I'm missing?

01-restart.power
#!/bin/sh
case "$1" in
pre)
systemctl stop kodi
;;
post)
sleep 1
systemctl start kodi
;;
esac

02-gpu.power
#!/bin/sh
case "$1" in
post)
xrandr --output HDMI3 --set "Broadcast RGB" "Limited 16:235"
;;
esac

Also tested with the milhouse build (beta6) and the issue is still there, however when I use the default skin now its doesn't seem to hang kodi and if I just back out to a menu, wait for some time and try again the list of recordings appears.

debug log collected.

IFKe

I actually hit the issue again this morning. This time the box wasn't in sleep mode it was just idle since last night. When I tried to access the recording section, it hung. I collected the kodi.log before killing the kodi process via ssh and then collecting the logs again.

New logs GgWb

Hi,

I hope this is right forum. I've noticed that when trying to access TV/Recordings library every time after resuming from sleep it fails to display the contents. Sometimes kodi will hang and show a black screen with a reboot being the only solution (if I ssh to the machine and kill the kodi process it will recover), sometimes if I wait for a while (up to 60 seconds) and retry the contents will display.

I thought that disabling the suspend function would be enough but my wife claims that the same can happen if the box is left idle for a long time but I've not seen this myself.

Logs uploaded to ZeTf (sleep/resume tested around 21:39) (i've a remote syslog running to so can provide more if required).

I gave up since I was getting no help. Installed to local SSD instead.

So is this feature even supported any more?

So I've been testing this some more and it works with OE6.0.3 and its broken in OE6.95.3/LE7.0. The older version of OE is using Kernel 4.1 while the newer versions have changes to 4.4. Is it possible to revert the kernel in LE to a lower version so I can test/confirm this?

Can anyone provide assistance with this one? I went back and tried 7.0.0 and again it gets stuck on shutdown/reboot. Was there any changes to iSCSI/PXE support in LE?

For comparison I tested with OE 6.0.3 and this has no problem booting/rebooting/shutting down etc. Let me know if there is anything you need from my side. I can upload the image files if anyone wants to reproduce the issue.

Following on from this thread about problems with USB for installation (LibreELEC) I went playing with PXE booting my libreelec installations. (pfsense for dhcp, solarwinds tftp, kernsafe iscsi server, vhdx images build with an ubuntu server VM).

I used the following links to get my installation going and the machines are booting up fine.

Network Boot - iSCSI - OpenELEC

Manual Installation - OpenELEC

The problem is on reboot or shutdown the system hangs at "reached target shutdown". My guess is that the network is shutting down before the unmount happens cleanly. Can anyone shed some light on how I might correct this?

Thanks for the detailed response. Yes my fear was having to switch to SSDs and was simply reluctant to do so due to cost and the waste aspect (I've nothing locally to store on the SSDs everything is on my server).

I'm not sure where to start with this one so appreciate any help. I've 2 Gigabyte Brix 3000 units booting from USB which are running LEv7.0.2. I'm using the DVBlink PVR & EMBY client add-ons but that's it. Both units are controlled using the Kore android app. I was using Yatse but switch to Kore to rule it out.

From time to time (could be days between events) I see a message pop up on the screen saying 'removable storage unmounted' followed quickly by 'remove storage mounted' (or word to that effect). The box continues to run as does Kodi itself but the filesytem I'm guessing has gone readonly as settings will no longer toggle, new content isn't added from emby, guide wont update, etc, until I perform a reboot.

Once I reboot some settings are lost (home screen layout, playback preferences, etc) but everything functions again until the next pop up. I used to run OE on these and didn't have the issue. I've ruled out the USB devices by replacing both and the issue remains. I've also tried reinstalling both boxes from scratch and again it comes back.

What logs can I provided that may assist? Thanks in advance.