Yes now it compiles and the Anysee tuner works! Thank you all so much, and chewitt in particular! And I learned so much, I might be able to figure it out myself the next time
Posts by Rataplan626
-
-
I can't get it to build, during the build it can't find that specific version of fakeroot:
--2024-06-10 17:29:26-- http://sources.libreelec.tv/mirror/fakeroo…oot-1.34.tar.gz
Resolving sources.libreelec.tv (sources.libreelec.tv)... 65.109.172.87
Connecting to sources.libreelec.tv (sources.libreelec.tv)|65.109.172.87|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2024-06-10 17:29:26 ERROR 404: Not Found.Doesn't matter if I take 12.0.0 or the latest nightly.
I'm currently finding out how I can add sources to the building mechanism, as I found multiple repositories with that version in.
-
I was just typing a reply when your last update popped up. Weird how I came up with another patch that borked it twice. Still, for the time being, how would I build the kernel for now without the borked patch, or with yout update? I can find my way in Linux, but I'm not into kernel building apart from al the builds I made during this bisecting. By the way, on my laptop the initial LE build took like 45 minutes, but with the changed kernel only a few minutes.
-
I did it on the real hardware but a vm could work I guess. It didn't even take as much time as I expected, but yes it's a bit of a hassle. I did it twice and came on the same patch both times. I wonder if you end up on the same erroneous patch.
-
Anyone? How could I continue from here reporting this bug in the kernel? Would it make sense to try a linux box with a newer kernel and see if it works again? Would I be right to assume if that would work, at some point it would work in LE again when they incorporate newer kernels as well?
-
Sorry for the late reply, life hit me hard the last couple of weeks. Getting everything back on track now. This weekend I updated to LE12 on a test SD-card, and it still doesn't work. My build-vm is still on 11 though.
git seems to report that patch is present:
Code
Display Moregit show 5d0fe30be4e28abe373bf951416f29afb0651e01 commit 5d0fe30be4e28abe373bf951416f29afb0651e01 (refs/bisect/bad) Author: Christoph Hellwig <[email protected]> Date: Tue Aug 1 19:35:44 2023 +0200 modules: only allow symbol_get of EXPORT_SYMBOL_GPL modules commit 9011e49d54dcc7653ebb8a1e05b5badb5ecfa9f9 upstream. It has recently come to my attention that nvidia is circumventing the protection added in 262e6ae7081d ("modules: inherit TAINT_PROPRIETARY_MODULE") by importing exports from their proprietary modules into an allegedly GPL licensed module and then rexporting them. Given that symbol_get was only ever intended for tightly cooperating modules using very internal symbols it is logical to restrict it to being used on EXPORT_SYMBOL_GPL and prevent nvidia from costly DMCA Circumvention of Access Controls law suites. All symbols except for four used through symbol_get were already exported as EXPORT_SYMBOL_GPL, and the remaining four ones were switched over in the preparation patches. Fixes: 262e6ae7081d ("modules: inherit TAINT_PROPRIETARY_MODULE") Signed-off-by: Christoph Hellwig <[email protected]> Reviewed-by: Greg Kroah-Hartman <[email protected]> Signed-off-by: Luis Chamberlain <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> diff --git a/kernel/module/main.c b/kernel/module/main.c index 7a6f43d2b775..7a376e26de85 100644 --- a/kernel/module/main.c
and some more after that.
So that patch seems to be incorporated.
-
Sounds good. So when Raspbian incorporates that into their builds, it will one day 'automatically' end up in LE? Is that how things work? Now I have this build system up and running, can I build an 11.0.6 with this patch incorporated?
-
I'm really sorry for my compile noobness, but how do I check?
-
This is what came out:
Code
Display More5d0fe30be4e28abe373bf951416f29afb0651e01 is the first bad commit commit 5d0fe30be4e28abe373bf951416f29afb0651e01 Author: Christoph Hellwig <[email protected]> Date: Tue Aug 1 19:35:44 2023 +0200 modules: only allow symbol_get of EXPORT_SYMBOL_GPL modules commit 9011e49d54dcc7653ebb8a1e05b5badb5ecfa9f9 upstream. It has recently come to my attention that nvidia is circumventing the protection added in 262e6ae7081d ("modules: inherit TAINT_PROPRIETARY_MODULE") by importing exports from their proprietary modules into an allegedly GPL licensed module and then rexporting them. Given that symbol_get was only ever intended for tightly cooperating modules using very internal symbols it is logical to restrict it to being used on EXPORT_SYMBOL_GPL and prevent nvidia from costly DMCA Circumvention of Access Controls law suites. All symbols except for four used through symbol_get were already exported as EXPORT_SYMBOL_GPL, and the remaining four ones were switched over in the preparation patches. Fixes: 262e6ae7081d ("modules: inherit TAINT_PROPRIETARY_MODULE") Signed-off-by: Christoph Hellwig <[email protected]> Reviewed-by: Greg Kroah-Hartman <[email protected]> Signed-off-by: Luis Chamberlain <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> kernel/module/main.c | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-)
It talks about NVidia, which doesn't have much to do with this I suppose, but it seemingly affects these TV tuners in TVHeadend.
So... now what
-
I got it to build. I'll try to find the breaking commit and report.
-
Had some time to fiddle with it again, but I can't get it to work. In my last try I checked out 11.0.3, build that, which builds and works fine (as expected). When I change packages/linux/package.mk to reflect the suggested commit, it fails again with the same overlay_map.dtb error.
If anyone has a clue hoe to get the kernel to build properly, that's be awesome.
-
*sigh* these are the moments I was afraid of, feeling like a total noob. I checked out 11.0.6 which was the most recent at the time. First build an image, went fine. Then I modified package.mk to reflect the bisect suggested commit. Build again and then:
[QA CHECK] [linux] [safe_remove]:
path does not exist: /home/rataplan_/http://LibreELEC.tv/build.LibreELEC-RPi4.arm-11.0-devel/install_pkg/linux-2368afd60f647889d90fa4a42c7b27548f77dbd9/usr/share/bootloader/overlay_map.dtb
cp: cannot stat 'arch/arm64/boot/dts/overlays/README': No such file or directory
FAILURE: scripts/build linux:target during makeinstall_target (package.mk)
*********** FAILED COMMAND ***********
cp -p arch/${TARGET_KERNEL_ARCH}/boot/dts/overlays/README ${INSTALL}/usr/share/bootloader/overlays
**************************************
*********** FAILED COMMAND ***********
${SCRIPTS}/build "${1}" "${PARENT_PKG}"
**************************************
FAILURE: scripts/install linux:target has failed!The following log for this failure is available:
/home/rataplan_/http://LibreELEC.tv/build.LibreELEC-RPi4.arm-11.0-devel/.threads/logs/142.log>>> linux:target seq 142 >>>
[273/280] [FAIL] install linux:targetThe following log for this failure is available:
/home/rataplan_/http://LibreELEC.tv/build.LibreELEC-RPi4.arm-11.0-devel/.threads/logs/142.logLog attached. I've been looking for a bit to get that fixed. I checked https://github.com/raspberrypi/linux/issues/5272 but so far no sigar.
-
That figures. To learn for the future, could I have known that? I've looked into the 'how to build LibreElec' tutorial, but that didn't help.
-
And here is question number one. I cloned the linux kernel (git clone https://git.kernel.org/pub/scm/linux/…valds/linux.git) which worked fine on it's own. However when I go into that dir, and do
rataplan_@ubuntu01:~/linux$ git bisect start
rataplan_@ubuntu01:~/linux$ git bisect bad d23900f974e0fb995b36ef47283a5aa74ca25f51
fatal: Bad rev input (not a commit): d23900f974e0fb995b36ef47283a5aa74ca25f51
Same for the good 61fd484b2cf6bc8022e8e5ea6f693a9991740ac2. So that leads me to think I cloned from the wrong repository? Anyway, a push in the right direction is needed By the way, the initial LE build I did to test works fine (apart from the tuner of course) so that's a win already -
Wow, yes indeed, the initial build took 54 minutes on my laptop... this will sure take some time Anyway, I'm on it and will report when I have news (or questions).
-
Smells like a complex thing if you've never done it. It'll take me some time to work through that, but I will test.
-
And... Is that something I can do or help with? I can work with Linux and am a MS systems and storage engineer, but building kernels would be new for me
-
I was trying to, but it seems https://ix.io/ is 'taking a break'. Seems that service is down. 11.0.3 uses that, so can't paste that log (or can I upload it somewhere, you are very clear I shouldn't upload it here). For now, because of that I'll allow myself to paste a few lines that I think matter. By the way, I tried with 11.0.5 but also no TV adapter available anymore it seems.
11.0.3:
LibreELEC:~ # lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 1c73:861f AMT Anysee E30 USB 2.0 DVB-T Receiver
Bus 001 Device 003: ID 1915:1028 Nordic Semiconductor ASA Smart Control
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubdmesg output:
[ 2.598648] usb 1-1.2: New USB device found, idVendor=1c73, idProduct=861f, bcdDevice= 1.00
[ 2.598661] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.598672] usb 1-1.2: Product: anysee-FA(LP)
[ 2.598681] usb 1-1.2: Manufacturer: AMT.CO.KR
[ 5.468386] usb 1-1.2: dvb_usb_v2: found a 'Anysee' in warm state
[ 5.471744] usb 1-1.2: dvb_usb_anysee: firmware version 1.2 hardware id 15
[ 5.472160] usb 1-1.2: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer
[ 5.472281] dvbdev: DVB: registering new adapter (Anysee)
[ 5.472295] usb 1-1.2: media controller created
in 11.0.5 pastekodi DOES work: https://paste.libreelec.tv/enabling-vervet.logAs far as lsusb and dmesg go, they show the same. So I guess the driver is still there. However, TVHeadend Server (which seems to run fine on 11.0.4 / 11.0.5) show no adapters in the config-screen, and obviously when I switch to a TV channel, Kodi says something like 'no free adapter'.