Post Last Edited by maxwell at 2014-8-7 17:49 |
it has been quite a ride the last couple of days, steep learning curve and I had probably given up earlier without your hints and tips. So a big thanks to you!
As I read some text about one having problems cross compiling earlier, there was a suggestion to compile exactly like his target system configuration. So yes, I got me the .config from /proc/config.gz today for both RPi and BPi, just to be save. But nothing changed though. At least I now know that I use the exact kernel config in the future.
I actually stumbled upon those error messages when compiling for the Raspberry. I got me that file for the RPi from the repo and the message went away but now I was left with another error "Source EABI 0 -> Target EABI 5" error messages.
** UPDATE EABI error ***
Duh, just found out, that I used the sit2.o for Cortex A9 instead of the also available RPi sit2.o to compile! Probably the error reason AND why I didn't get anything to work on the pi :-D
When I headed back for the more important BPi cross compile I just compiled and everything went smooth, so I thought I had the one for the BPi. But I just noticed I don't have it on my CompilerBox, I have it on my real BPi though. I will just copy it over from my BPi to my VM and recompile as my last action tonight and see if those modules are finally accepted as they are :-D
I will read up on "make modules_prepare" and try that (of course). And yes, maybe I will do my complete own image, because MaxUbuntu doesn't sound too bad. :-D
Just a quick summary, what is needed to make this CT2-4400 (and some other new models from Technotrend):
Get media_build-bst from Manufacturer
Get precompiled closed source module Sit2.o for ARM
Get BPi Kernel Sources and build it with its modules
Compile media_build-bst (sit2fe.ko, dvb-usb-v2.ko, dvb-usb-dvbsky,ko are the three modules that don't exist in vanilla BPi)
Make Install media_build-bst on BPi
Sound like 5 quick steps to victory, normally. :-D
I head back to some more testing now and will probably do a roundup/how to in another post.
Oh and the tainted message, at least in this context here, isn't all too bad?
I WILL keep you posted.