Posts by Da Flex

I can feel your pain.

I think it's a lot easier to take a ~1.5mm driller, and physically destroy the LED by drilling in.

Read here about sending commands.

Thanks for the log! Looks like the settings wizard has trouble to start in LE 9.2. Try LE 9.1.002. Update to 9.2 by GUI after the setup.

Put it into .kodi/userdata at the STORAGE partition. The leading point makes the directory invisible for some OS'es.

phob08 :

LE creates a symbolic link (symlink) for every connected (and mountable) external storage medium.

External storage access always has to go over such a symlink.

But that's a problem for JDownloader, it can't access files beyond such a symlink.

The easiest solution for you is not to use an external drive as a destination of JDownloader files. Use internal storage instead.

Thanks for testing a different resolution.

1. Use Etcher to write the LE image to microSD card.
2. If booting still fails, activate logging. Because you have no access to the GUI settings, use advancedsettings.xml to activate log level 2. Create and edit the file on your PC. After failed booting, grab kodi.log on your PC, upload it to Pastebin and post the link.

Quote from metamorphic

Cheap but recent HDMI TV set.

...

Everything works as expected under Rasbian, which I have on a separate SD card, after I added the the hdmi_safe=1 to config.txt.

Maybe Raspbian boot into a lower resolution, and your HDMI cable isn't good enough to deal with the higher resolution of LE.

Enforce a lower resolution for LE by using config.txt. If that works, replace the HDMI cable (use "HDMI High Speed (Premium)" standard).

Sounds pretty much like this.

Quote from Blackbeard

If I trigger an LED from autostart.sh I know that the autostart-script is loaded. But I also want to know if KODI is loaded.

That's nearly the same time, and as written, Kodi always runs from that point, if you don't explicitly stop that process.

Read here how to trigger a status LED.

PS: Watch the video at the linked thread to see when Kodi and status LED will start working - should be exactly what you need.

Quote from aBnoBa

I need a libreelec containing Kodi v18.3 on Raspberry Pi 4

Check the Milhouse testbuilts. Maybe you'll find the right Kodi version for your very special needs.

Yes, automatic updates can be prevented by GUI.

Quote from jgibson706

I'd think if this was a common thing the forum would be full of this problem. Did I get an odd-ball board?

Could be a cable issue, too, especially if it appears randomly.

Quote from Blackbeard

And if possible, I would like to use a LED, like a heardbeat to show whether KODI is running or not.

I'm still puzzling...

Which hardware do you use, and why do you need to know the status of Kodi? Kodi always runs by default.

If you use an RPi, you could trigger an LED from autostart.sh.

I wouldn't do that heartbeat thing, because it will freak people out after some time.

2019-12-24 21:39:04.943 T:140611201242880   ERROR: ## LibreELEC Addon ## bluetooth::dbus_error_handler ## ERROR: (Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

If other Bluetooth devices pair, then it's probably option one of the log line.

Quote from jgibson706

Okay, second try, got to the network setup again and ... black screen.

Please try the last 9.1.x version, and in case of success upgrade by GUI to the latest.

No problem. Marry X-Mas and some great time in 2020!

I bet Steam OS has the capability to re-install the boot loader (BIOS MBR in your case). Then you don't need an unwanted extra Linux.

The point is that sometimes (like after major Win 10 updates) you have to re-install the boot loader. Do a research whether Steam OS has such capability, just to be sure. The boot loader will find all installed OS'es, including LE.

I'm not sure whether Win 10 likes the shrinking. If you have to re-install all OS's, do Win 10 first, then Steam OS (if it can re-install the boot loader), then LE.

Quote from Mydriaze

Is there a easier way to proceed? Is there any update on this? My ultmate goal is to use my Intel Nuc with Windows 10, LibreElec, then Steam OS.

You will have those problems with any other multi-boot Linux OS, too. That is no special LE question.

However, I had dual boot Win 10 / Ubuntu for a long time. This year Win 10 updates sucked so much, that I've been deleted Win 10.

My multi-boot install was like this:

1. create all partitions you need (for all OS'es, use "Gparted Live" or "Parted Magic" for instance)
2. install Win 10 on a selected partition
3. install the next OS on a selected partition and so on

If you have trouble to find any OS after reboot, use Super Grub2 Disk to boot into Linux, and reinstall the boot loader (EFI partition).

The problem is that LE don't have the capability to do this. So, I suggest to have one Linux OS installed (Ubuntu etc.), which let you reinstall the boot loader. This means, the first OS after the Win 10 installation should be such a complete Linux. Maybe Steam OS has such capability, too, but I don't know.

Sometimes, if you can't reboot into an OS, you have to re-select the first bootable partition at the EFI settings (usually the Linux partition, which leads to the GRUB boot selection screen).

Mounting network shares (NFS)