Solved: Krell Foundation, Beebox and Openelec
#31
Intel posted a patch to the above bug.

I have never compiled a kernel before so is there a handy HOWTO for building and installing the updated driver?
Reply
#32
(2016-03-02, 05:17)artur9 Wrote: Intel posted a patch to the above bug.

I have never compiled a kernel before so is there a handy HOWTO for building and installing the updated driver?

I'll put together an updated 6.0.x-EGL build tomorrow with this patch for you
Reply
#33
@MattDevo: Please PR this patch to OpenELEC, it is useful for everyone (with that issue).
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#34
(2016-03-02, 10:24)fritsch Wrote: @MattDevo: Please PR this patch to OpenELEC, it is useful for everyone (with that issue).
Will do once fix is confirmed working Smile
Reply
#35
(2016-03-02, 05:17)artur9 Wrote: Intel posted a patch to the above bug.

I have never compiled a kernel before so is there a handy HOWTO for building and installing the updated driver?

try this build and LMK if it works:
https://dl.dropboxusercontent.com/u/9830...0.398a.tar
Reply
#36
(2016-03-02, 22:38)Matt Devo Wrote:
(2016-03-02, 05:17)artur9 Wrote: Intel posted a patch to the above bug.

I have never compiled a kernel before so is there a handy HOWTO for building and installing the updated driver?

try this build and LMK if it works:
https://dl.dropboxusercontent.com/u/9830...0.398a.tar

That build will work on the Asrock Beebox n3000? Asking because currently I'm using one of fritsch's Kodi 17 build.
Reply
#37
(2016-03-03, 06:53)artur9 Wrote: That build will work on the Asrock Beebox n3000? Asking because currently I'm using one of fritsch's Kodi 17 build.

you can't downgrade easily from v17 to v15.2, so use this link instead to create new install media, then run it in live mode (type 'live' at the boot prompt): https://dl.dropboxusercontent.com/u/9830...98a.img.gz

if that works, I'll rebase it into OE master and then fritsch can pick it up for his next build.
Reply
#38
(2016-03-03, 06:53)artur9 Wrote: That build will work on the Asrock Beebox n3000? Asking because currently I'm using one of fritsch's Kodi 17 build.

any luck testing yet?
Reply
#39
(2016-03-05, 19:09)Matt Devo Wrote:
(2016-03-03, 06:53)artur9 Wrote: That build will work on the Asrock Beebox n3000? Asking because currently I'm using one of fritsch's Kodi 17 build.

any luck testing yet?

Haven't done it yet but will shortly (like within a few hours).
Reply
#40
(2016-03-05, 19:09)Matt Devo Wrote:
(2016-03-03, 06:53)artur9 Wrote: That build will work on the Asrock Beebox n3000? Asking because currently I'm using one of fritsch's Kodi 17 build.

any luck testing yet?

Seems to work fine. Tried a few movies DTS-HD, Dolby TrueHD, DTS.

Thanks a ton! I think fritsch's v17 video looks a bit better :-)


In case you want to look at it
das-schoen:~ # dmesg | pastebinit
http://sprunge.us/YTiE

das-schoen:~ # pastebinit < .kodi/temp/kodi.log
http://sprunge.us/ORST

das-schoen:/proc/asound/card0 # cat eld\#2.0 | pastebinit
http://sprunge.us/RDQA
Reply
#41
BTW, please let me know which builds (official and fritsch) end up with this patch.
Reply
#42
(2016-03-05, 20:14)artur9 Wrote: Seems to work fine. Tried a few movies DTS-HD, Dolby TrueHD, DTS.

Thanks a ton! I think fritsch's v17 video looks a bit better :-)


In case you want to look at it
das-schoen:~ # dmesg | pastebinit
http://sprunge.us/YTiE

das-schoen:~ # pastebinit < .kodi/temp/kodi.log
http://sprunge.us/ORST

das-schoen:/proc/asound/card0 # cat eld\#2.0 | pastebinit
http://sprunge.us/RDQA

Great, I'll submit a PR to get this into OE master, and then it will be in any subsequent test builds from fritsch/Milhouse etc

edit: PR accepted into OE master, so any builds after today should include the fix
Reply
#43
Can someone post a link to this Intel fix with SII REPEATOR. I have the same problem with my HTPC no outputing surround sounds.
Reply
#44
Here: http://www.spinics.net/lists/dri-devel/msg102334.html

it was merged into 4.6-rc kernel
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply

Logout Mark Read Team Forum Stats Members Help
Solved: Krell Foundation, Beebox and Openelec0