Posts by sky42

5schatten i had trouble with 4.11.12. Then moved on to 4.13 and not really better. Found a patch for 4.13 that helped. And since 4.14 all ist fine and all the LSPCon fixing was already in the kernel.

One big issue is the Firmware in the LSPCon. For Parade PS176 it should be 7.85 and for MDCP2800 for ASrock 1.66 for some Intel NUCs 1.72 and i did see also 1.71. From your HTPC setup description i would guess you nee MDCP2800 Firmware and it must be at least 1.66.

The description says LSPCon fix for my 8.2.5-3.42 beause the kernel 4.14. fixes it. Sorry that you searched in my patches, because i did not state it clear.

You can check what you have with

cat /sys/kernel/debug/dri/0/i915_display_info

NINjak try this one HiDrive with kernel 4.16.8 build just now and still with a wrong version numnber 8.2.5-5.42. I am just doing a full rebuild and that takes about 90min. On my i3-8100 the testing version bootet just now, but no testing at all so far.

The real 8.2.5-6.42 wil follow and here are the changes so far

8.2.5-6.42 with kernel 4.16.8 and Coffee Lake support

- based on 8.2.5-5.42

- Coffee Lake Support without i915 alpha features

- additional driver disabled bcm_sta RTL8192CU RTL8192DU RTL8192EU RTL8188EU RTL8812AU

- kernel driver enabled RTL8XXXU RTL8192CU

- removed kernel patch linux-051-ouya_controller_support.patch and linux-053-spinelplus-remote-0.2.patch

Thanks!

I will apply and check it with my comminity build.

Edit: 2018-05-09 Sorry erro corrected: i did see cryptsetup needs lvm2 too

Interessting change. I will try to incorporate the PR in my community build LE 8.2.5 with UHD 630 / Coffee Lake support and luks, lvm2, dm-raid and test it. When i checked all the changes i will report back.

But the encryption needs one more feature request cryptsetup luks/truecrypt/veracrypt/loopaes, lvm2 and probably dm-raid too (patches included)

There is a small kernel config change and the cryptsetup, lvm2 packages are needed. The package mdadm is in there too, because the kernel has all what is needs to do dm-raid.

I am fairly familiar with encryption and hope to make it easy enough with some dokumentation and some scripts. With the help of a developer it should be not that hard to mount encrypted usb drives as they are attached. That will work too for e.g. veracrypt encryption and a exfat fs on there (created and useable on windows).

This commit should do the trick. I will try changing my community build and check. Tomorrow i am on vacation for 5 days and will have time to check it.

Sorry i am not yet familiar how to quote in the forum. I try to answer in order.

What do i want to do with these hooks:

- probably tweak the update process some how after flash is mounted, but no plans for that so far

- when storage is mounted i will try to mount .kodi/userdata encrypted on a different partition (working on that), at the moment i have a solution to do that as systemd unit before kodi starts

- my first PoC was getting a password from the user in the boot process (if the user wants) and post-storage.sh calls get-pw-init.sh.txt and then from autostart.sh do this mount-all.sh.txt done with OE 5 and truecrypt

- the real goal is when there is encrypted storage (partition) and i can open it umount unecrypted storage and mount the encrypted one instead

- after that mounting encrypted data disks with the help of a crypttab, that is mainly for offline usage on the road with no server to get the keys/data from (NUC and disks with some films in my luggage)

- this need the password from the boot process

- when all i need is in the LE image and not a addon (like truecrypt in OE 5) i can do it earlier and since there is no truecrypt anymore (and it is old and needs replacing) i use cryptsetup, that can mount also truecrypt/veracrypt volumes

I am fine with 1- 3 and the commit looks fine

And yes i know i need to lern git and start to use it. I still use cvs (dont laugh) for versioning my server configs/scripts. I need to sit down with one of our developers at work and learn how to use git, have my own github repo and doing pull requests. Sorry for the inconvenience with the patches.

For grub2 that depends on your grub version. On CentOS and Ubuntu they are diffrent.

On my pxe server at home i use one /uefi/grub.cfg and in all the other places is a grub.cfg with "configfile /uefi/grub.cfg", because for secure boot i need to use the grub from the distro.

So yes it should be possible and the content of /flash/EFI/BOOT/grub.cfg must be "configfile /grub.cfg"

There is also a way to write one grub.cfg which does different things if it is uefi or not. I had my guys at work build one with this differentiation to start the correct memtest. I dont thing that is needed for LE, but i can get these configs.

Thanks for the informations. The UID feature is cool. And with PXE i did full diskless with OE 4 (i think) and my old Zotac min PC with Nvidia GPU.

And now as you say it: yes the last sd card problem was a long time ago. I dont hang on the SYSTEM_TORAM_LIMIT feature. It was just there and i used it (i think) some years sind OE 5.

I was just excided that i finally did take the time to share my work in the forum and i like giving it back. And sometimes a nice sideeffect is that i have something less to maintain.

I created it for OpenELEC 5 to get around some trouble with sd cards, so that my 3 RPi2 need the sd card only for booting and the storage was on nfs. It was to get the sd card out of the picture as much as possible.

If i find time next week i try todo the part of my wishlist and build a version 8.2.5-6.42 with kernel 4.16.

By messing around with encryption of LibreELEC i patched init with 2 hooks to mount things/ask user for password and so on, so that i dont need to rebuild LE every time i change the init script.

The second one is to configure how much RAM is needed to copy the SYSTEM file to RAM before mounting it. For me on RPi2 it workt very well with "SYSTEM_TORAM_LIMIT=680000" as kernel parameter. The hardcoded limnit in init is 1GB.

So here it is init_patch.txt

Thanks for reading my proposal

Edit: 2018-05-09 corrected the dependencies of cryptsetup, lvm2 (more exact libdevmapper) is needed and therefor only mdadm as pkg is optional

I like all my systems cold secure, that means all data are fully encrypted. The one exception are my kodi boxes. I did try to get all the infos away from the kodi box, but at least the Textures13.db is on the box, when i mounted .kodi/temp as tmpfs and redirected Thumbnail to the server.

So i build a community version (my latest) LE 8.2.5 with UHD 630 / Coffee Lake support and luks, lvm2, dm-raid and since the end of last year i also shared it in the forum.

features tested:

- truecrypt with "cryptsetup open --type tcrypt /dev/sda6 tcrypt-sda6 ; mount /dev/mapper/tcrypt-sda6 <your mountpoint>" created on OE 5.0 with truecrypt

- veracrypt with "cryptsetup open --veracrypt --type tcrypt /dev/sdb6 vcrypt-sdb6 ; mount.exfat /dev/mapper/vcrypt-sdb6 <your mountpoint>" created on Windows 10 with veracypt and formated as exfat

- cryptsetup luks i used to create and mount encrypted userdata

I striped down all my changes to the minimum to have cryptsetup luks usable and for Generic enabled AES-NI to have it hardware accelerated. The lvm2 package is needed by cryptsetup. The kernel config also contains all to use mdadm.

All what is needed is in cryptsetup-lvm2-dm-raid.zip and the RPi2 kernel patch should apply to other architerures without so much trouble. There are only kernel config patches for Generic and RPi2 build for 8.2.5 with a kernel 4.14 (like the LE git master at the moment).

Sadly my script tools to mount userdata encrypted are not yet ready for the public, but i would love to see all what is needed in LE so that only a addon is needed or i patch the init to support it at boot time. For curious persons here are my scripts without any support for it from /storage/.cryptluks scripts-cryptluks.zip and it uses a backend webserver and gets all the parameter from the kernel command line.

For boot time support i have a plan to use nework bound disc encryption (NBDE) with tang and clevis to make it totaly unattended bootup with encryption.

Thanks for reading my proposal.

There are 2 syslinux.cfg files, 1 for BIOS and 1 for UEFI. I do forghet that some time and edit the wrong one on my UEFI boxes. The reason i do edit them is that i have at least 2 LE versions on my box (stable, nightly) and select with the help of menu.c32 or vesamenu.c32.

My solution is the UEFI one just includes the BIOS one.

/flash/syslinux.cfg normal as ever

/flash/EFI/BOOT/syslinux.cfg only with one line "INCLUDE /syslinux.cfg"

That works perfect for me. But at least in packages/sysutils/busybox/scripts/init and the getedid tool the syslinux.cfg is manipulated and copied.

Thanks for reading my proposal

That would be very sad to dont use it. It is very usefull to me for some years to boot more than 1 OpenELEC/LibreELEC version on one box (after enlaging /flash of course). For me there are at least 3 version on my box: the stable one, the nightly and since 8.2 a patched version with Xin1 playback, which is not very stable.

The BOOT_IMAGE is set by syslinux because of a kernel line with /kern-82. I set the SYSTEM_IMAGE in the kernel command line.

It is very practicle to have multiple LibreELEC versions on one box (each one with its own /storage) and to use the automatic update within. I do select them with the help of menu.c32 or vesamenu.c32 and some rewritten syslinux.cfg.

I can rewrite my patch to only act on the Generic version (if i can find out in the init script which one is booting). Or should i make a feature request of it? If not i can live with only using .tar for updates.

Here is something about new NUCs Intel NUC Roadmap 2018 – 2019 – Gemini Lake, Coffee Lake, and Kaby Lake H

I think all the new NUCs dont have any optical audio out.

Sorry i am not a developer. I just gather information, patches, new software versions and try to build them.

If i had to guess i would say the plugin.video.quasar ist the problem, but i am just guessing. The other thing that looks probably problematic is the cec.

You have a lot of plugins. For me it is just kodi + tvheadend client + unpause jumpback. That is pretty stable for me (so far).

Oh I see. For only new and not old reruns there is no rule.

What you want does already exist in tvheadend and it is quit good. I use tvheadend some years. For me it is running on my server. For you it is a addon of your kodi box (if i understand you correct).

Go to http://<ip or name of your kodi box>:9981/ e.g. 192.168.178.57:9981 or whatever the ip or name of your kodi box is.

The klick "Digital Video Recorder" now "Autorecs" and there are the rules for automatic recordings.

If there is already a rule klick on it and then klick edit and select "Duplicate handling" as you like.

You dont need kodi to setup new Autorecs. You can do it entirely in the tvheadend Webinterface and still see the recordings in kodi. The most simple one for me is: Select something in the tvheadend Webinterface EPG -> klick Info Icon -> klick Autorec -> goto Autorecs and edit it for duplicate handling.

Hope that helps