Posts by Iridium

I own and use (Currently on osmc RPi3) the XBox One DVB2 stick

Slowly slowly....

Failed on

patch -s -f -N -p1 -i ../backports/linux-057-Removed-MCE-customer-code-restriction-in-rc6-decode.patch
1 out of 2 hunks FAILED

So commented out.

Now failed on:

Quote

patch -s -f -N -p1 -i ../backports/linux-203-stb0899_enable_low_symbol_rate.patch
patch -s -f -N -p1 -i ../backports/linux-220-Xbox-One-DVB-T2-stick-support.patch
1 out of 1 hunk FAILED
2 out of 2 hunks FAILED
1 out of 4 hunks FAILED
1 out of 1 hunk FAILED
make[3]: *** [Makefile:139: apply_patches] Error 1
make[3]: Leaving directory '/home/iridium/http://LibreELEC.tv/build.LibreELEC-imx6.arm-8.2-devel/media_build-526f51c/linux'

Display More

Which of course is the item I am most interested in.

Glad you found a solution - this seems to be case in a lot of situations.

Compile works without the media_build.

In packages/linux-drivers/media_build/package.mk

PKG_NAME="media_build"
PKG_VERSION="2017-04-17-rpi" ----------------------------- should this be RPi?
PKG_ARCH="any"
PKG_LICENSE="GPL"
PKG_SITE="https://github.com/crazycat69/linux_media" -------------------- This does not exist.

Can I just replace package.mk with package.mk

That didn't work:

patch -s -f -N -p1 -i ../backports/linux-052-XBOX_remote_support.patch
1 out of 1 hunk FAILED
make[3]: *** [Makefile:139: apply_patches] Error 1
make[3]: Leaving directory '/home/iridium/http://LibreELEC.tv/build.LibreELEC-imx6.arm-8.2-devel/media_build-526f51c/linux'
make[2]: *** [Makefile:374: stagingconfig] Error 2
make[2]: Leaving directory '/home/iridium/http://LibreELEC.tv/build.LibreELEC-imx6.arm-8.2-devel/media_build-526f51c/v4l'
make[1]: *** [Makefile:26: stagingconfig] Error 2
make[1]: Leaving directory '/home/iridium/http://LibreELEC.tv/build.LibreELEC-imx6.arm-8.2-devel/media_build-526f51c'
Makefile:12: recipe for target 'image' failed
make: *** [image] Error 2

Well it finds something:

[    2.164440] input: FREEWAY TECHNOLOGY as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.2/0003:1D57:AD03.0001/input/input0
[    2.219037] hid-generic 0003:1D57:AD03.0001: input,hiddev0,hidraw0: USB HID v1.01 Keyboard [FREEWAY TECHNOLOGY] on usb-3f980000.usb-1.1.2/input2
[    2.223163] input: FREEWAY TECHNOLOGY as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.2/1-1.1.2:1.3/0003:1D57:AD03.0002/input/input1
[    2.223437] hid-generic 0003:1D57:AD03.0002: input,hidraw1: USB HID v1.01 Mouse [FREEWAY TECHNOLOGY] on usb-3f980000.usb-1.1.2/input3

Can you provide a full kodi log file - as explained in my signature.

Also as this is a RPi3B+ can you try a LE9 Milhouse build as it may be related.

On 16.04 it compiled, however on running, after resize and reboot, it fails with a kernel panic:

[ 8.338680] Internal error: Oops: 5 [#1] PREEMPT SMP ARM
[ 8.338693] Modules linked in: uio_pdrv_genirq(+) gpio_ir_recv(O+) uio sch_fq_codel ipv6

and just reboots on an endless loop.

Rest of text Kernel Panic

I'll compile without media_build and see if anything improves.

I'm not too sure what the problem is - are you saying that mouse mode works but keyboard mode doesn't?

So firstly lets get some logging info.

Provide full logs as detailed below. Also include "dmesg | paste" and "lsmod | paste"

It might show up any issues. However you have to remember that not all remotes are supported and you may just be unlucky.

You are the man - Top Dog or should that be Top Cat. Yes it was on 18.04. I'll try again on a Ubuntu 16.04 VM tomorrow.

Ok - I've been barking up the wrong tree.

edit ../projects/imx6/options 

ADDITIONAL_DRIVERS="media_build"

PROJECT=imx6 ARCH=arm make image

Bwahh: Even without media_build, it fails to compile. Number of things I noticed - unsure if relevant.

a) /home/iridium/http://LibreELEC.tv/build.LibreELEC-imx6.arm-8.2-devel/make-4.2.1/configure: line 9807: /home/iridium/http://LibreELEC.tv/build.LibreELEC-imx6.arm-8.2-devel/toolchain/bin/pkg-config: No such file or directory.

b) - U-Boot configuration: mx6_cubox-i_config matrix

(Looks odd mx6 - I would have expected it to be imx6) Doesn't make a difference if I change it though.

Then fails at:

make[3]: Entering directory '/home/iridium/http://LibreELEC.tv/build.LibreELEC-imx6.arm-8.2-devel/make-4.2.1/.x86_64-linux-gnu'
/usr/bin/gcc -O2 -Wall -pipe -I/home/iridium/http://LibreELEC.tv/build.LibreELEC-imx6.arm-8.2-devel/toolchain/include -Wno-format-security -Wl,--export-dynamic -Wl,-rpath,/home/iridium/http://LibreELEC.tv/build.LibreELEC-imx6.arm-8.2-devel/toolchain/lib -L/home/iridium/http://LibreELEC.tv/build.LibreELEC-imx6.arm-8.2-devel/toolchain/lib -o make ar.o arscan.o commands.o default.o dir.o expand.o file.o function.o getopt.o getopt1.o guile.o implicit.o job.o load.o loadapi.o main.o misc.o posixos.o output.o read.o remake.o rule.o signame.o strcache.o variable.o version.o vpath.o hash.o remote-stub.o glob/libglob.a -ldl
glob/libglob.a(glob.o): In function `glob_in_dir':
glob.c:(.text+0x2c1): undefined reference to `__alloca'
glob.c:(.text+0x43e): undefined reference to `__alloca'
glob.c:(.text+0x5f8): undefined reference to `__alloca'
glob.c:(.text+0x658): undefined reference to `__alloca'
glob/libglob.a(glob.o): In function `glob':
glob.c:(.text+0x95b): undefined reference to `__alloca'
glob/libglob.a(glob.o):glob.c:(.text+0x101a): more undefined references to `__alloca' follow
collect2: error: ld returned 1 exit status
Makefile:655: recipe for target 'make' failed

---------------------------------------------------------------------------------------------------------

Log: pastebin

So do I just need PROJECT=imx6 ARCH=arm scripts/build media_build ?

I have a defunct Cubox-i IMX-6 which works well with LE 8.2.5, however because this technology is limited in future releases I want to use this box to be my TVheadend server. I know that the 8.2.5 does not include media_build which is what I hope to do.

I've run the "normal" media_build compilation on a number of machines and O/S with mixed results, including the Cubox-i on Armbian which worked - alas the tuner although recognised only found one MUX within tvheadend - even though the same H/W and aerial work on a RPi3

I'm quite happy to cross compile - but I have no idea what I need to do it to include media_build.

Is it a fairly easy procedure to add the media_build? .. and if so what steps are required.

In response to your second question. I have a Samsung 960 pro M.2 and it is fast. (This is my home desktop)

If you have loads of cash, then it is definitely worth it – but for Kodi I think it will be a waste of money. Far better to spend it on something else. My guess would be that your scanning and cleaning is more than likely due to the NAS or N/W. You’ll need to do some tests to see where your bottleneck is – remember each time it does a scan, it has to query the internet to update the database. How often do you scan your videos? .. and why clean so often?

An alternative (depending on you NAS) is to install emby-server and let emby update it’s database at a convenient time and access your files via the emby add-on in LE.

The other radical alternative, is to forget the HTPC build, but utilise the parts for a new faster NAS, and just use a cheap Armlogic (or something with x265 support) box to serve as the client.

As a “New” AML fan, previously Rpi I run a £35 Mecool and it’s perfect for what I want.

When someone invents a crystal ball that predicts technology, it will be a lot easier to predict “future proof”.

At the moment for a lot of people – me included (and it does cause some contention) is buy cheap replace often.

In my experience the advantage of moving the boot partition to eMMC/USB/eSata etc is limited - yes it takes slightly longer to boot, but most LE systems are 24/7 so any advantage is negated.

However, what does make a difference is moving the /Storage usually the partition called "root" or "LIBREELEC_DISK" or "Storage" on later AML. to eMMC. This is what I did on a AML S905x Here

It may not work for you but might give you some pointers

As far as I know there are no LEGAL karaoke add-ons - so no further support will be offered.

I think you need to refer your question to openelec - this is LibreELEC.

A simple web search "Kodi podcast" would have provided This

There is now a LE pi-hole docker add-on. See Here

There is now a LE pi-hole docker add-on. See Here