Posts by HiassofT

FYI: dvb driver addons are now disabled for imx6 in LE master and current imx6 nightly builds are available on our test server again. eg LibreELEC-iMX6.arm-9.80-nightly-20200623-7d65b9e-cubox-dl.img.gz

so long,

Hias

I thought it was documented in the wiki, but quick search didn't turn up anything - maybe that info was lost at some point...

Wiki rework is already planned for the near future, hope the missing bits will be added then.

so long,

Hias

You have to store the settings to /storage/.config/sound.conf

alsactl store -f /storage/.config/sound.conf

so long,

Hias

Please tell us which buttons exactly are not working anymore and provide a full kodi debug log where you press these buttons and a journal log with the upload log function in LibreELEC settings.

so long,

Hias

The imx6 builds on test.libreelec.tv are outdated and don't contain the remote fix - our buildserver is tripping over the same dvb driver addons build issue. You either need to build yourself or wait a bit until the issue is fixed in LE master we have current nightly images available.

so long,

Hias

ssd mounting late seems odd, if /storage can't be mounted at boot time LE won't start at all...

Just noticed your blkid shows a "Microsoft reserved partition" - my guess is that it might be this partition that gets mounted.

I think it may be best to re-partition the SSD, using a classic MBR partition table ("Microsoft reserved partition" and the other PARTLABEL entries look like it's partitioned as GPT) and make sure the VFAT partition is the first one. GPT and/or VFAT partition on anything else than number one could be problematic for USB boot later (not 100% sure, maybe that's already implemented, but it's easier/safer to just follow the default partitioning scheme we also use on SD card).

so long,

Hias

All the settings are stored in hidden directories (.kodi, .config, .cache), copying via kodi will probably have missed these - and it's not quite ideal to copy config files while they are being used (eg .kodi folder while kodi is running).

I usually copy filesystems on my linux PC, mount eg both SD card and USB drive and then run `rsync -a ...` as root.

An easier method is probably to use the backup and restore functions in LibreELEC settings. Boot from SD, backup everything eg to an external hdd/flash drive, then switch over to storage on SSD and choose restore.

Stopping kodi and then using rsync (from the system tools addon) or tar to copy the /storage partition would be another method.

so long,

Hias

Quote from ray1112

I can confirm it's working.

Thank you Hias.

Thanks a lot for reporting back!

so long,

Hias

Quote from goinsledn

I'm new to libreelec and kodi. where do i find the config.txt file to add the commands to allow the pi 4 8gb to display on my yamaha receiver and samsung tv. It's blank but the pi 4 works here on my desktop via hdmi. Thanks

See here Raspberry Pi Config.txt [LibreELEC.wiki]

If you have display problems please search the forum and create a separate thread if necessary.

so long,

Hias

Quote from NOLAguy

Do you know if the rest of the ram is usable? Can Librelec even make use of that much ram? I have Librelec running on the Pi4 8gig, but doubt that much ram even does any good..

Linux can use the full RAM for filesystem cache/buffers and background programs / docker containers etc can make use of it. I wouldn't recommend though to run too much stuff on the RPi, it's CPU is still a lot slower than current gen Intel/AMD CPUs.

If you just want to run Kodi then 8GB is overkill. All programs are compiled as 32bit, so each process can use max 3GB (and Kodi won't even need that). 2 or 4GB will do just fine.

so long,

Hias

Please try to replace the firmware files on the FAT partition of a LE 9.2.3 installation with the ones from this ZIP rpi-firmware-9e3c23c.zip - you can do that eg on a windows (or linux/mac) PC.

See also this thread RPi3 Updade to 9.2.3 ending in Black Screen

It's a rather rare issue on RPi3s, but it's the reason why we haven't enabled auto-update to 9.2.3 yet. LE 9.2.4 will ship with the same firmware files as the one in the ZIP - so far this fixed all RPi3 boot issues.

so long,

Hias

The latest nightly build from here Index of / (ATM LibreELEC-RPi4.arm-9.80-nightly-20200621-7864ad7.img.gz) contains current state of RPi4 development.

Hardware H264 decoding is currently disabled by default (as it causes crashes when seeking or stopping), if you're willing to take the risk you can enable it in player settings. 4k HEVC hardware decoding works fine, though.

The KMS driver doesn't support 4k output yet, so it'll be limited to 1080p. HBR, HDR aren't implemented either and proper multichannel output is also missing ATM.

So, you have been warned, test it at your own risk.

so long,

Hias

Ah, seems the imx6 change was incomplete, it missed to disable the optional dvb drivers (which aren't compatible with the current 5.7 kernel and disabled in most other projects). I'll ping our imx6 maintainer again

You can easily fix that yourself, just set DRIVER_ADDONS_SUPPORT="no" in ~/.libreelec/options. You can also change that in projects/NXP/options but if you don't need these drivers disabling globally is easier (and saves a bit of build time).

Whenever you change DRIVER_ADDONS_SUPPORT you have to rebuild kodi (just scripts/clean kodi before the build), otherwise kodi may end in a crash-loop.

so long,

Hias

Please post your full samba.conf. And also please post full logs to a paste site and snippets as inline code - dealing with screenshots is a PITA.

You will get the incompatible/old style message in journal if you removed the line which says "do not remove":

# samba.conf v4 (do not remove)

You'll also get that (or similar warnings) in journal if you use a have an old .config/samba.conf created on earlier libreelec versions which shipped with samba3.

That line is used by the config script to check if the config file matches the currently used samba version, and if it's missing or on the wrong version the file will be ignored.

so long,

Hias

Your .config/samba.conf will only be picked up if you restart the samba-config systemd service before restarting the samba systemd services. Or just reboot LE.

so long,

Hias

If you want to move to a USB/SSD only setup later it'd be best to partition the SSD with a 512MB VFAT as #1 (this will become the "/flash" boot partition later) and then the remaining space as an ext4 partition for storage.

just copy the data from the ext4/storage partition on the SD card to the ext4/storage partition on the SSD and then change the disk=UUID=.... parameter in cmdline.txt (in the FAT partition of your SD card) to the UUID of the ext4 partition of the SSD (use "blkid" to get the UUID values).

so long,

Hias

1366x768 is a know problematic resolution on the RPi4 and there doesn't seem to be some offical fix for it yet.

If you search the RPi forums you'll find a lot of reports and also proposed workarounds.

eg one suggestion is to try this

hdmi_group=2
hdmi_mode=87
hdmi_cvt=1366 768 60 3 0 0 1

see Rpi 4 not working at 1366x768 - Raspberry Pi Forums

so long,

Hias

throttled= 0x80000 means that the RPi3B+ went over the soft temperature limit of 60°C and throttled the CPU down from 1400 to 1200MHz at some time in the past. Your power supply is fine.

See Raspberry Pi Documentation and Raspberry Pi Documentation

so long,

Hias