Posts by lrusak

You can set individual devices to enable standby mode

try adding setfbres=1080 to the kernel append line in syslinux.cfg

Pull the latest git and rebuild.

Quote from NeroBoron

I knew it and was pretty sure that it worked for me some time ago at least back in OpenELEC times.
Just thought this is/was a bug in the last alpha/beta builds.

Well i can tell on my Intel NUC it worked smoothly without any user (ssh) interaction. Any chance that i can get that back? Now i have to add every bluetooth device manually. That is really annoying cause back then I could easily hook up a friend's phone to my box so they could steam some audio.

It was only ever in the milhouse test builds for a brief period.

No it probably won't be added back as it was rather hacky.

What we need is a pulseaudio configuration gui in kodi.

Try removing the "\" from your password

Quote from Shoog

When I grab the firmware from that source (kernel,start.elf,bootloader.bin,bcm2710-rpi-3-b.dtb, bcm2709-rpi-2-b.dtb) and load it into the boot folder it gets stuck at the rainbow splash.

The question is has anyone actually got a working system with this method and precisely what files did you use to get it ?
Stephen

Don't replace the kernel!!!!!!!!!!!!!!

We actually rename some files.
See, LibreELEC.tv/package.mk at master · LibreELEC/LibreELEC.tv · GitHub

start_x.elf -> start.elf
fixup_x.dat -> fixup.dat

No.

I'm not even sure if we provide the chroot command.

What are you wanting to do?

Quote from Shoog

There is a problem with trying this as there is a known bug which means that when you enable boot from USB only 119MB of ram is available on the system. This is cured on the Raspbian system by using an updated version of bootcode.bin, but this doesn't cure the issue when used in a Libreelec build.

At the moment it would seem that this facility is broken until someone looks at the specifics of the Libreelec and firmware integration.

Update: if you try copying all the firmware across from the Raspbian next build, you get a broken system with everything stuck at the rainbow splash screen.

Stephen

just grab the firware from here, firmware/boot at next · raspberrypi/firmware · GitHub

You can always use docker

Quote from MikeBuzz

Anyone using the on board infrared receiver?

I have just ordered a CM3 Lite to test with booting direct from the HDD.

Yes I am.

It should use aml platform not default

Not really.

What are you wanting to change?

Quote from tocisz

I'd love to have LVM support in the host system. I only tried to do this in docker because it seemed easier than changing host system...

I know that I should probably use Ubuntu instead of libreelec but it's not so easy to have so fine tuned kodi there like the one ready to use in libreelec

Then don't use LVM because well, it's really not needed

You don't need LVM support in docker (we don't even build it in anyway)

You can mount directories into your docker containers, so even if your container runs your nfs server, etc. You can just mount directories from the host inside it.

Basically the graph driver dictates what the container layers are stored on (btrfs, overlayfs, lvm, etc) We use ext4 so overlayfs works perfectly with that.

You don't need LVM support in docker in order to use LVM formatted disk, however, we don't support LVM on the host system either.

Quote from gouwa

New LibreELEC ROM released.

LibreELEC ROM released [SD INSTALLATION] - Announcements - Khadas Community

Where is the source code?

Why do they change the root password? What other changes are there?

Why do they change the default tarball name? Why are they packing it as a 7z?

Always be careful about blindly installing anything.

Once you're Bluetooth device is paired you can see it via pulseaudio with the command

pactl list short sinks

Then set it

pactl set-default-sink <sink-name>

Then in kodi just select the pulseaudio device as the audio output

You are free to change the key map however you see fit.

You can specify a resolution in kodi so that it stays at 1080p.

Settings -> system -> display

Otherwise please ssh and post the output of the following command and we can put something together

xrandr | pastebinit