• 1
  • 58
  • 59
  • 60(current)
  • 61
  • 62
  • 126
Intel Apollo Lake
No, I just enable DRI3 by copy-pasting the xorg.conf file from https://forum.libreelec.tv/thread-4323.html
Reply
Yeah - was just curious that it really helps ...

Will upload another build tonight with mesa 17 and DRI3 by default. Latest and greatest, bumped without testing it - like in the good old open ELEC times ...

Edit: will end up here (uploading - and as germany is a 3rd world land when it comes to broadband - it will need another hour): http://fritsch.fruehberger.net/openelec/hevc10/dri3/ (231 MB)
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
@xwire: i suspect some issue with your case or you mix-up some of the front panel cables. The switch is not supposed to do anything at all when not pressed.

Sent from my HTC One_M8
Reply
@fritsch do you know if there is a difference using modsetting in xorg.conf instead of intel?
Reply
You mean concerning performance? Nope. Should be pretty straight forward these days, especially for kodi which is an GL application anyways.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
(2017-02-25, 23:28)fritsch Wrote: Will upload another build tonight with mesa 17 and DRI3 by default.

Can you help me cherry picking the intel/hevc stuff into a "milhouse" build (https://github.com/LibreELEC/LibreELEC.tv) ? I seem to have missed some commits in my first attempt on my own.
Reply
(2017-02-25, 23:41)fritsch Wrote: You mean concerning performance? Nope. Should be pretty straight forward these days, especially for kodi which is an GL application anyways.

yup thats what I meant. thanks
Reply
(2017-02-25, 23:47)DerPat Wrote:
(2017-02-25, 23:28)fritsch Wrote: Will upload another build tonight with mesa 17 and DRI3 by default.

Can you help me cherry picking the intel/hevc stuff into a "milhouse" build (https://github.com/LibreELEC/LibreELEC.tv) ? I seem to have missed some commits in my first attempt on my own.

No. I provide tech demos and not the best build on the planet - everything you need is on my github, branch: hevc10ffmpeg31
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
(2017-02-25, 23:50)fritsch Wrote: branch: hevc10ffmpeg31

That already helps me a lot, I used the hevc10bit branch. Thanks!
Reply
(2017-02-25, 23:51)DerPat Wrote:
(2017-02-25, 23:50)fritsch Wrote: branch: hevc10ffmpeg31

That already helps me a lot, I used the hevc10bit branch. Thanks!

Milhouse builds v18, That means the cherry-picks won't build .. as they are backported from kodi-agile (roling tree v18 based) to v17 ...
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
(2017-02-25, 23:28)fritsch Wrote: Yeah - was just curious that it really helps ...

Will upload another build tonight with mesa 17 and DRI3 by default. Latest and greatest, bumped without testing it - like in the good old open ELEC times ...

Edit: will end up here (uploading - and as germany is a 3rd world land when it comes to broadband - it will need another hour): http://fritsch.fruehberger.net/openelec/hevc10/dri3/ (231 MB)

Great! It helps a lot, the animations are a lot smoother. It's hard to see in a 60 fps video, so I have recorded two short videos at 240 fps to illustrate the difference:

Your LE 8.0 build with no changes (select to download it if you want it in full resolution):
https://drive.google.com/file/d/0B-_nZam...sp=sharing

Your LE 8.0 build with the xorg.conf file I linked in my last post:
https://drive.google.com/file/d/0B-_nZam...sp=sharing
Reply
Can you see a difference with my dri3, mesa 17 build? (still uploading, 1min left)
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
Absolutely, your DRI3 / Mesa 17 build is visually as smooth as your Mesa 13 build with DRI3 enabled through xorg.conf Smile So no custom xorg.conf needed in your Mesa 17 build.

Your Mesa 17 build for comparision:
https://drive.google.com/file/d/0B-_nZam...sp=sharing

Thanks..
Reply
(2017-02-26, 00:02)fritsch Wrote: Milhouse builds v18, That means the cherry-picks won't build .. as they are backported from kodi-agile (roling tree v18 based) to v17 ...

I only had to correct one patch (kodi-999.999-hqscaling.patch) and one pick (10e9ceec24d2cbb8c8e18bf387d1380614a11816 - mesa: bump to 13.0.4) seems to be empty now.

Even though you don't want to support this, can you tell me if those commits are all I need?

50c643e4ebf753734d9fc2578f566651c5634806 - FFmpeg: Backport HEVC-10 bit enable patch
fb2e844e9f998ecd9002564a45c91cb2658914c9 - Linux: Add drm fourcc codes for 16 bit R and RG (vaapi hevc 10 bit)
adc60df7f71f3f253e20ea369e1e4e2cd2bb5542 - Mesa: Allow 16 bit R and GR images to be exported via drm buffers (va…
c2500b01a4c3e4ab04bccb695dcda9fa162d956d - Kodi: Backport VAAPI hevc10 bit from fernet (vaapi hevc 10 bit - test...)
59431c920427de9f9ffd224c76f0ae35f29e22a8 - kodi: don't use hq scaling when involving sizes > 2560 we are too slow
516b258c2b5e06011eca76f3437d915352c95880 - mesa: update hevc-10 bit sharing patch
bd52f2c496a392593a9a8c0f2e966ccb00ea94f3 - FS: Increase chunksize to 512 KB
31c6af960e88aa74936fdab6b038040d16d12426 - Mesa: Bump to 13.0.5
e9257ab6fc38829f26a2cdebc54fea749c5e9556 - xorg-i915: enable dri3 by default
df8a3af92d7a02b03434e5964cfb0ed6f101e416 - llvm: bump to 3.9.1
0ae9659732252b30200cb5f2484701396ac336ee - mesa: bump to 17.0.0

Thanks... again!

/Edit: image build just finished. I'll check if hevc 10 is now working and keep you updated
Reply
(2017-02-25, 18:09)fritsch Wrote: My ASRock J4205 never had any issue. It always powers up without an issue.

PowerSupply / Memory Issue?

Tried 3 different PSUs that have been working flawlessly in other systems for many years as well.
Is memory incompatibility still an actual thing? Of all the various systems I've assembled the last 5 years, RAM incompatibility never occurred when using unlisted RAM. For this system I'm using Kingston HX321LS11IB2K2/8, which is part of the same line as the HX318LS11IBK2/16 that is on ASRock's J4205-ITX Memory Support List.

(2017-02-25, 23:30)dexter98 Wrote: @xwire: i suspect some issue with your case or you mix-up some of the front panel cables. The switch is not supposed to do anything at all when not pressed.

Sent from my HTC One_M8 (typie typie)
Case is a Streacom F7C Alpha. Board is properly mounted. No front I/O cables attached, apart from that of the power switch. Poles on the power switch side as well as on the motherboard are all properly line-ed up. I've unscrewed the power switch module from the Streacom enclosure, and connected it onto the motherboard of a different system. The power switch shows normal behaviour on that system (flawlessly boots up the system from cold at every actuation as it should), so the power switch module of the Streacom enclosure shouldn't be the culprit.

I've placed the J4205-ITX in a different case (Fractal Desgin Define R4). The funny thing is that the power switch of that case is that, despite it neither can actuate a proper POST from cold 100% all the time, it does at least manage to start the system up every now and then. Meaning that the power switch of the Define R5 has got fewer issues, which is weird, as the Define R5 and Streacom enclosures and their power switches perform exactly the same as each when having tried an other motherboard.
Reply
  • 1
  • 58
  • 59
  • 60(current)
  • 61
  • 62
  • 126

Logout Mark Read Team Forum Stats Members Help
Intel Apollo Lake9