I was rather hoping I could configure this to set the Pi NOT to boot until the button was pressed on initial power on...
I'm not familiar with that SHIM. I assume when you plug in the PSU, it will always boot, no matter what's in the scripts.
Posts by Da Flex
-
-
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
Just a small hint: Users love to know what a wizard does under the hood. Something like a visual checklist would be nice.
-
What do I save this as (filename and filetype) is it autostart.sh or as it's a python script is it whatever.py ?
Both. Call the Python script from this /storage/.config/autostart.sh:
Bash#!/bin/sh ( python /storage/.kodi/userdata/scripts/whatever.py ) &Create the script folder: mkdir /storage/.kodi/userdata/scripts
Copy whatever.py into /storage/.kodi/userdata/scripts.
Make both files executable:
chmod +x /storage/.config/autostart.sh
chmod +x /storage/.kodi/userdata/scripts/whatever.pyCan I create both of these files directly on the SD card when its in my local machine or is it best to do so via SSH using nano?
Doesn't matter.
-
enabled passthrough DISPLAYPORT and output on displayport (NUC8i3) doesnt have a displayport.
buy it worked anyway from hdmi
That's because your NUC uses DisplayPort protocol internally, and then it's converted to HDMI by an LSPCon chip. LSPCon issues are unsolvable by us, so you're lucky. I think the HDMI firmware update was the real fix.
-
On TV's people can usually select different color schemes for HDMI input (I did so for my RPi). Maybe you'll find such an option for the projector, too.
-
Can you provide a log on Generic? Then we know which HDMI modes the projector is offering. Maybe a hi-contrast RGB mode is available, but not in use.
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
ain't that for RGB limited ?
I think so. I suggest to play with xrandr options, before you invest serious time by compiling your kernel. I don't know how exactly HDMI negotiation works, but there is a chance that you can enforce an HDMI mode, which has better contrast on RGB. So update to Generic-Legacy, and go back to Generic, if it doesn't work.
-
Maybe you can tweak RGB output with this (I guess xrandr needs Generic-Legacy):
-
Thanks! If the other three audio output options also deliver no audio, then we need a log file...
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
This is my second RPi4 bricked after using soft "power off."
Try another PSU.
-
Normally I would investigate that WiFi bug now, but without an updated BIOS it makes no sense.
-
You can use the shutdown or poweroff command on SSH.
There are KODI RC apps for Android/iOS, who can do the same. Maybe that's more comfortable.
-
updated the bios didnt work.
Please check whether your HDMI firmware is up-to-date, too. Audio is related to HDMI.
-
- update to LE 12 Beta
- make sure your BIOS is up-to-date
-
Do you have the same issue, if you don't have the WiFi adapter attached? It seems to make trouble in the log.
-
It seems to be an FFmpeg issue, so first you should try LE 12 Beta. If the issue remains, post a proper log...
We need log level 1 or 2 on a complete log file. The log file has to be located at our own log server.
- activate log level 1 or 2 by creating an advancedsettings.xml file
- reboot
- replicate the problem
- login by SSH
- post the resulting URL of pastekodi command
-
Just to explain my suggestion: Here is a user, who had no audio after suspend, and firmware update was the fix:
