Posts by sky42
-
-
-
I see the same problem and i fear that will take me a while to investigate.
I created a new thread for LE 9.0 here LE 9.0-devel for more Hardware (Gemini / Coffee / Cannon / Ice Lake, AMD Vega / Raven APU) and luks, lvm2, dm-raid
-
The frist attempt was a miss.
See the infos for the 1st attempt in this post #106 in my 8.2.5 thread , where KarstenL680 and tomtomclub had the same problems i did see today after testing the build from last night on my i3-8100.
A new 1.42 and 5.42 are just now compiling.
-
I will try to build versions with more supported Hardware for Generic x86_64. My first quick test for a 5.42 was not succesfull and it looks like i need to build up changes slow, to see what works and what does not.
My daily driver is my 8.2.5-6.42 for my main LE with Coffee Lake i3-8100 from this thread LE 8.2.5 with UHD 630 / Coffee Lake / Gemini Lake support and luks, lvm2, dm-raid.
I have no Gemini Lake or AMD hardware for testing.
LE9 milhouse testbuild for x86_64 are now with kernel 4.17. See this post #105 or go drectly over here LibreELEC Testbuilds for x86_64 (Kodi 18.0) and download #0616 or later.
I you really want to have a LE9 with luks, lvm2 or dm-raid respond in this thread and i will build one.
Edit:So the planned release versions in this post are rubbish (i deleted them), because LE master is a too fast moving target. I will make builds and post the difference between LE master commit id and my build. Sorry that will be long but that is the only way that you know what you are installing.target hardware (read the release posts):- Intel Gemini Lake- Intel Coffee Lake- Intel Cannon Lake- Intel Ice Lake- AMD Vega- AMD Ravendownload link HiDrive1st release post #26 (gcc 7.3.0)2nd release post #29 (gcc 8.1.0)3rd release post #35 (gcc 8.1.0)Have Fun
sky42
-
Here you go (hopefully). If it does work for you i will think about making a new thread for that.
Thanks for all the pointers on AMD GPUs.
I build a LE 9.0 version with all the patches and config from my 8.2.5-7.42.0, because AMD Vega and Raven APU will never work with 4k and VAAPI on Kodi 17. Thanks mglae for pointing that out.
So here is the next attempt to get AMD Vega and Raven APU running.
And for Gemini Lake users the 2 workarounds are also in this version.
9.0-devel-20180609010255-dfdae5e-5.42.0-4.17
- kernel 4.17 with config from my 8.2.5-7.42.0-4.17
- kernel-firmware update to git 2a9b2cf5 from date 2018-05-18
- PR init: add sky42 enhancements/bug fixes by MilhouseVH · Pull Request #2689 · LibreELEC/LibreELEC.tv · GitHub already merged and created by milhouse ... thank you
- added packages cryptsetup, lvm2, mdadm and needed kernel config for encryption
- Mesa 3D 18.1.1
- created/added xorg-server-1.19.6-sync_pci_ids_1.20.0.patch
- added Gemini Lake HDMI bug 105887 workarounds and to activate put i915.glkhdmi=1 or i915.glkhdmi=2 in /flash/syslinux.cfg
- created/added amdgpu-firmware with latest firmware for vega10, vega12, vegam, raven from here Index of /~agd5f/radeon_ucode
- disabled kernel driver RTL8192CU RTL8192DU RTL8192EU RTL8188EU RTL8812AU bcm_sta
- disabled addon driver crazycat digital_devices hauppauge
my LE 9.0 testing versions are here HiDrive
-
I will try to build a LE 9.0 with all the changes i have done to my 7.42.0 for AMD support. Compiling just started and if the speed is like 8.2.5 this build should be done in about 2h.
-
As you did see in the post of mglae , i dont have a chance with Kodi 17. So i give up AMD with VAAPI and 4k HW decoding.
piotrasd has build a special AMD version see this thread Experimental build AMD GPU (Vega, Ryzen APU)
-
Thanks for that info. I will switch off vaapi for AMD in my next releases.
-
some updates ... what was done:
8.2.5-3.42.2-4.14.48
- just the kernel 14.14.48
8.2.5-5.42.2-4.14.48
- just the kernel 4.14.48
8.2.5-6.42.2-4.16.14
- just the kernel 4.16.14
-
xorg 1.20 released, to build for AMD use kernel from here ~agd5f/linux - Unnamed repository; edit this file 'description' to name the repository.
Do you have a PKG_URL for this AMD kernel for me please. I can not figure out what is the right URL for the kernel packae.mk
-
So it was not just me with the refresh rates. I am very happy to hear that it helped.
-
If i find time i will setup a tvheadend on my 2 Intel LE systems and check if i can see a problem with tvheadend. But please be patient. My tvheadend server is running on my backend server for all my LE boxes. The 3.42.2 is the right choise with all you need for Gemini Lake (i hope), but as little as possible change from 8.2.5, except adding encryption.
Pleaee show me a "ldd <tvheadend binary>", so that i can see about linked libraries.
-
My lastest 7.42.0 is with Mesa 18.1.1. and for AMD i do not know what else to do except make a build with a special AMD kernel. I will look into it on the weekend. My 6.42.2 and 7.42.0 (since kernel 4.16.13) are for AMD and Gemini Lake.
-
some updates ... what was done:
a testing version 6.42 with kernel 4.17
8.2.5-6.42.2-201806041418-4.17 HiDrive
- kernel 4.17
- look for -CC suffix if you need CrasyCat DVB drivers, now there are 2 builds for each release
-
correction of the last update ... what was done:
the date needs to be before the kernel version in the filename
8.2.5-7.42.0-201806041407-4.17 HiDrive
- kernel 4.17
- look for -CC suffix if you need CrasyCat DVB drivers, now there are 2 builds for each release
-
some updates ... what was done:
8.2.5-7.42.0-4.17-201806040840deleted look next post- kernel 4.17
- look for -CC suffix if you need CrasyCat DVB drivers, now there are 2 builds for each release
with slightly different timestamps -
I fear that looks like a decoding and/or color space conversion problem and i have no idea what to do. LE 9.0 uses ffmpeg 4.0 and building kodi 17.6 with ffmpeg4 seems not possible, because kodi is kind of hardwired to a ffmpeg version. I just did try and it downloaded 3.1 when only 4.0 was compiled and avariable.
So just for clarification of your test:
You did try 3.42.2, 5.42.2, 6.42.2?
The GLK HMDI bug workaround did also work for 3.42.2 and 5.42.2? That one i needed to rewrite and i am not really a developer and was not sure if it is working at all.
I just build a new version with 4.17 kernel release, but i think that one will not help you.