Posts by sky42

    dkhait

    I recommend using bluetooth for a remote or at least a FLIRC. Only for wake up using IR.

    I did start with IR RC6 on my Haswell NUC. That was painfull slow with my Harmony 650.

    The i moved on to FLIRC with Harmony FLIRC HTPC profile, that was much faster. A FLIRC acts as a keyboard and works all the time without OS software support. But you need a windows to make firmware updates. I did an update only once as it was new and use the preprogrammed factory profiles.

    Now i use a Harmony Elite with bluetooth. This is faster then my eyes, when it is scrolling.

    eightball70 i follow the bug 105887 but i did see there is already a workaround

    So for all Gemini Lake user: I have build some LE version with the 1st workaround for Bug 105887.

    I think your best bed is a 6.42 or 7.42 version, but 5.42 and probably 3.42 should work too.

    Edit: First try LibreELEC-Generic.x86_64-8.2.5-6.42.1-201805201701-kernel-4.16.9, because for eightball70 / dkhait this one works and dkhait had some problems with other versions ( see this post #50 )

    download here HiDrive one of

    ./3.42/LibreELEC-Generic.x86_64-8.2.5-3.42.1-201805201731-kernel-4.14.41-bug-105887-workaround.img.gz

    ./3.42/LibreELEC-Generic.x86_64-8.2.5-3.42.1-201805201731-kernel-4.14.41-bug-105887-workaround.tar

    ./5.42/LibreELEC-Generic.x86_64-8.2.5-5.42.1-201805201657-kernel-4.14.41-bug-105887-workaround.img.gz

    ./5.42/LibreELEC-Generic.x86_64-8.2.5-5.42.1-201805201657-kernel-4.14.41-bug-105887-workaround.tar

    ./6.42/LibreELEC-Generic.x86_64-8.2.5-6.42.1-201805201653-kernel-4.17-rc5-bug-105887-workaround.img.gz

    ./6.42/LibreELEC-Generic.x86_64-8.2.5-6.42.1-201805201653-kernel-4.17-rc5-bug-105887-workaround.tar

    ./6.42/LibreELEC-Generic.x86_64-8.2.5-6.42.1-201805201701-kernel-4.16.9-bug-105887-workaround.img.gz

    ./6.42/LibreELEC-Generic.x86_64-8.2.5-6.42.1-201805201701-kernel-4.16.9-bug-105887-workaround.tar

    ./7.42/LibreELEC-Generic.x86_64-8.2.5-7.42.0-201805201705-kernel-4.16.9-bug-105887-workaround.img.gz

    ./7.42/LibreELEC-Generic.x86_64-8.2.5-7.42.0-201805201705-kernel-4.16.9-bug-105887-workaround.tar

    ./7.42/LibreELEC-Generic.x86_64-8.2.5-7.42.0-201805201708-kernel-4.17-rc5-bug-105887-workaround.img.gz

    ./7.42/LibreELEC-Generic.x86_64-8.2.5-7.42.0-201805201708-kernel-4.17-rc5-bug-105887-workaround.tar

    some updates ... what was done:

    8.2.5-3.42.1-kernel-4.14.41

    - added CrasyCat dvb driver from 5schatten git as media_build replacement

    - kernel-firmware update to git 2a9b2cf5 from date 2018-05-18

    - iwlwifi-firmware from 5schatten git

    - intel-ucode from 5schatten git

    8.2.5-5.42.1-kernel-4.14.41

    - all update from 8.2.5-3.42.1-kernel-4.14.41

    - Mesa 3D 18.0.4

    - libdrm 2.4.92

    - xf86-video-amdgpu 18.0.1

    - xf86-video-nvidia 390.59

    - created/added xorg-server-1.19.6-sync_pci_ids_1.20.0.patch

    - created/added libva1 for compatibility, so that tvheadend42 should work

    8.2.5-6.42.1-kernel-4.16.9 and in testing 4.17-rc5

    - all update from 8.2.5-5.42.1-kernel-4.14.41

    8.2.5-7.42.0-kernel-4.16.9 and 4.17-rc5

    - this is for testing only

    - all update from 8.2.5-6.42.1-kernel-4.16.9

    - LLVM 6.0.0 for Mesa 3D 18.1.0 compile

    - Mesa 3D 18.1.0

    - this is a attempt to get AMDGPU Raven Ridge running (not working so far)

    @eightball70 you did catch my latest 8.2.5-6.42.1-kernel-4.16.9 and i was not done with the 4.17-rc5. The testing 8.2.5-6.42.1-kernel-4.17-rc now should work too with your bluetooth. When you get me or point me to the "No Signal" patch i will build a version with that patch.


    here are the versions that are new the last 2 days (if you downloaded before you should do it again) HiDrive

    ./3.42/Generic/LibreELEC-Generic.x86_64-8.2.5-3.42.1-kernel-4.14.41.img.gz

    ./3.42/Generic/LibreELEC-Generic.x86_64-8.2.5-3.42.1-kernel-4.14.41.tar

    ./3.42/RPi2/LibreELEC-RPi2.arm-8.2.5-3.42.1-kernel-4.14.41.img.gz

    ./3.42/RPi2/LibreELEC-RPi2.arm-8.2.5-3.42.1-kernel-4.14.41.tar

    ./5.42/Generic/LibreELEC-Generic.x86_64-8.2.5-5.42.1-kernel-4.14.41.img.gz

    ./5.42/Generic/LibreELEC-Generic.x86_64-8.2.5-5.42.1-kernel-4.14.41.tar

    ./6.42/Generic/LibreELEC-Generic.x86_64-8.2.5-6.42.1-kernel-4.16.9.img.gz

    ./6.42/Generic/LibreELEC-Generic.x86_64-8.2.5-6.42.1-kernel-4.16.9.tar

    ./6.42/Generic_testing/LibreELEC-Generic.x86_64-8.2.5-6.42.1-201805201119-kernel-4.17-rc5.img.gz

    ./6.42/Generic_testing/LibreELEC-Generic.x86_64-8.2.5-6.42.1-201805201119-kernel-4.17-rc5.tar

    ./7.42/LibreELEC-Generic.x86_64-8.2.5-7.42.0-201805191444-kernel-4.17-rc5.img.gz

    ./7.42/LibreELEC-Generic.x86_64-8.2.5-7.42.0-201805191444-kernel-4.17-rc5.tar

    ./7.42/LibreELEC-Generic.x86_64-8.2.5-7.42.0-201805192229-kernel-4.16.9.img.gz

    ./7.42/LibreELEC-Generic.x86_64-8.2.5-7.42.0-201805192229-kernel-4.16.9.tar

    @bullrin i just build 2 with alle the lastest things for AMDGPU (i hope)

    - kernel-firmware from yesterday with brand new AMDGPU firmware

    - kernel 4.17-rc5 and 4.16.9

    - xorg server 1.19.6 updated with all pci ids from 1.20.0+ (many new AMD)

    - LLVM 6.0.0 update to build Mesa 18.1.0

    - mesa 3d 18.1.0

    - xf86-video-amdgpu latest 18.0.1

    you can try this one from here HiDrive

    The one thing what is left (as far as i can tell) is to do it with xorg server 1.20.0, but this makes things a little bit more complicated.

    @5schatten the tip to fix tvheadend helped me to see the problem and i have build a new version with old libva too. Yes i need to use git. Sorry so far there are only my patches which apply agains git version ov LE 8.2.5 and they are here HiDrive

    new version 8.2.5-6.42.1 with kernel 4.16.9

    - most updates are from the git repo of @Sschatten GitHub - 5schatten/LibreELEC.tv: A bit more OS for KODI

    - update iwlwifi-firmware from Sschatten git

    - update intel-ucode from Sschatten git

    - new package cc-dvb from Sschatten git as media_build replacement, so dvb drivers should be fine again

    - created a new package libva1 to fix tvheadend42, so old 1.7.3 libva (as in original LE 8.2.5) version exists too

    - kernel 4.16.9

    - carefull i just builded it and did no testing at all (so far)

    @psycmos try my new version 8.2.5-6.42.1-kernel-4.16.9 from here HiDrive and you should not need the suggested workaround from Sschatte (which gave me the hint for probably solving it)

    8.2.5-5.42.1 with kernel 4.14.40 and Coffee Lake support

    ...

    - libva-intel-driver disabled and replaced by intel-vaapi-driver 2.1.0 (this could break tvheadend42 plugin VAAPI support)

    ...

    Sorry @psycmos i needed to update the intel lib and my fear was that will break tvheadend and it did. I just did a short try to build tvheadend42 in my 8.2.5-6.42.1 build env, but it wont build with or without transcoding.

    The last 2 days i rebuild all my image files and began from scratch for more order in my configs and patches.

    All the new versions are now with a .1 like 8.2.5-X.42.1.

    what was done

    - rebuild all kernel config from scratch and used menuconfig to switch on what is needed, after that diff and applied this to the kernel config from git

    - added to all versions PR init: add sky42 enhancements/bug fixes by MilhouseVH · Pull Request #2689 · LibreELEC/LibreELEC.tv · GitHub

    - removed all config/patches from 3.42, 5.42 and 6.42 for architektures that are not build

    - added Wetek_Play to 1.42

    - added RPi to 1.42, but i dont have one to test

    - wrote a small readme and put it in all the 8.2.5 download folders

    So if your setup is running fine you dont need to do anything, but you can.

    I see a potetial problem or two.

    A old installation is updated with a image with PR 2698. After that the user does getedid which changes syslinux.cfg, but it is a UEFI system with a existing /flash/EFI/BOOT/syslinux.cfg and getedid only changes /flash/syslinux.cfg. So the UEFI system will still use the /flash/EFI/BOOT/syslinux.cfg which is not changed.

    Move the /flash/EFI/BOOT/syslinux.cfg to /flash/EFI/BOOT/syslinux.cfg.off will solve that. Deleting it may destroy work in syslinux.cfg what somebody did on his box.

    @milhouse and chewitt thanks for the explanation. I did read all the old requests and expected such answer and understand it too. @milhouse you did kind of ask "is that all you need for encryption" and i could not resist to ask for my cryptsetup feature request and also practicly knowing what the answer will be. Sorry.

    I do like less is more too. At work i do whenever possible working by the KISS principal.

    How about giving the community the change to build addons with the encryption, lvm2, mdadm tools, but for that we need support in the kernel. Then i will lern to build addons. And there is less discussion why this tool gets into LE and that not. Most of them need kernel support.

    I checked out le master and build 5 differen le versions in 2 flavors

    PROJECT=Generic ARCH=x86_64

    PROJECT=RPi DEVICE=RPi ARCH=arm

    PROJECT=RPi DEVICE=RPi2 ARCH=arm

    PROJECT=Rockchip DEVICE=RK3399 ARCH=arm UBOOT_SYSTEM=rockpro64

    PROJECT=Amlogic DEVICE=S912 ARCH=arm

    1st full build with IMAGE_SUFFIX=git (fresh and clean from git)

    then i changed the kernel config for encryption, lvm2, raid

    2nd just make again with IMAGE_SUFFIX=git+md+crypt+lvm+raid

    2 concerns i did read about the kernel

    - size for the kernel: that changes less than 10KB and the system around 1MB

    - i am pretty sure there is no mesurable performance impact as long as you dont use the new modules

    You can see for your self here HiDrive all images i build and the git diff for the kernel changes

    ls -g kernel/system sizes le-9.0-testing-images-ls.txt

    kernel config patch le-9.0-kernel-config-git+md+crypt+lvm+raid.patch.txt

    Please consider the support in the kernel. I will build all the kernel config diff or more images for testing. Just ask and say what to build. Sorry for the patches again, i promise i will learn git.


    Thanks for reading

    sky42