anything I can do?
Wait for now – there will be some DVB improvements which will probably add support for your adapter.
I tried compiling it myself with my almost non-existent knowledge of Linux and kernels…
I pretty much followed [HowTo] Compile DVB Media Build drivers on RPi 3 this explanation except changing the version from the RPi to 3.14.29-55-osmc for my Vero 4k.
And I used the driver source from the manufacturers web site (media_build-bst-14-141106 from DVBSky - Enjoy HDTV on PC! DVB-T2 / DVB-S2 Professional TV Tuner Card and Box for PC. .
Guide used here: http://www.dvbsky.net/download/doc/Linux_driver_installation_Guide
But when trying any “make” commands I get the following message:
gcc: error: unrecognized command line option ‘-mstrict-align’; did you mean ‘-Wstrict-aliasing’?
Is there any way around it?
In another thread you told someone to fix the Makefile. How would I do that?
Didn’t change anything unfortunately
Also try export CROSS_COMPILE with the same
osmc@vero:/lib/modules/3.14.29-55-osmc/build$ export CC=/usr/bin osmc@vero:/lib/modules/3.14.29-55-osmc/build$ export CROSS_COMPILE=/usr/bin osmc@vero:/lib/modules/3.14.29-55-osmc/build$ sudo make oldconfig gcc: error: unrecognized command line option ‘-mstrict-align’; did you mean ‘-Wstrict-aliasing’? KBUILD_CFLAGS_MODULE:-DMODULE scripts/kconfig/conf --oldconfig Kconfig drivers/amlogic/wifi/bcmdhd/Kconfig:50:warning: defaults for choice values not supported # # configuration written to .config #
Still not able to make anything… Sorry for bothering you with my shallowness
I think you are using the wrong toolchain
okay, I think I messed something up big time…
after rebooting, I am stuck in a sad face loop without being able to ssh or anything…
Guess I will reinstall osmc on the vero and try again from scratch.
Will keep you posted
As long as you haven’t lost anything important, then no harm done. Reinstalling the kernel will probably fix this for you however, as you probably just borked your kernel modules.
I reinstalled, only thing I did after freshly installing was apt-get gcc and make.
I then downloaded the (supposedly) correct driver for kernel 3.14.x - 3.17.0.
It’s manual said
—Compile and install driver
1)Enter the source code directory
2)Check and choose one of the target systems, run â€˜uname -aâ€™ to get os informaton.
./v4l/build_x86.sh if build for 32 bit system os to support multi-standard, include DVB-T,DVB-T2 and DVB-C.
./v4l/build_dvbc_x86.sh if build for 32 bit system os to support DVB-C.
./v4l/build_x64.sh if build for 64 bit system os to support multi-standard, include DVB-T,DVB-T2 and DVB-C.
./v4l/build_dvbc_x64.sh if build for 64 bit system os to support DVB-C.
3)Compile the source code:
I used the x64 for the Vero4k version of osmc.
The .sh-File contains
#!/bin/bash cp ./v4l/sit2_op.o.x64 ./v4l/sit2_op.o cp ./v4l/sit2_mod.dvb ./linux/drivers/media/dvb-frontends/sit2_mod.c
and “make” results in
osmc@vero:~/media_build-bst-14$ make make -C /home/osmc/media_build-bst-14/v4l make: Verzeichnis „/home/osmc/media_build-bst-14/v4l“ wird betreten Updating/Creating .config Preparing to compile for kernel version 3.14.29 File not found: /lib/modules/3.14.29-55-osmc/build/.config at ./scripts/make_kconfig.pl line 33, <IN> line 4. make: *** Keine Regel vorhanden, um das Ziel „.config“, benötigt von „.myconfig“, zu erstellen. Schluss. make: Verzeichnis „/home/osmc/media_build-bst-14/v4l“ wird verlassen Makefile:26: die Regel für Ziel „all“ scheiterte make: *** [all] Fehler 2
sorry for it being German…
So you mentioned earlier I might be using the wrong toolchain… How would I use the correct one in this?
From the other mentioned HowTo ([HowTo] Compile DVB Media Build drivers on RPi 3) I tried to copy the /boot/config-3.14.29-55-osmc to /lib/modules/3.14.29-55-osmc/.config to avoid the make-process not finding any .config… But that resulted in the error mentioned in my first post.
You just run make under kernel-osmc after a clone.
maybe that’s it? How would I do that?
sudo apt-get install aarch64-toolchain-osmc
mount --bind (in another session) your working directory and build there.
still getting the same error
mounted my working directory to /opt/osmc-tc/aarch64-toolchain-osmc/mediakram
root@vero:/mediakram# make make -C /mediakram/v4l make: Entering directory '/mediakram/v4l' /bin/sh: 1: /sbin/lsmod: not found Updating/Creating .config Preparing to compile for kernel version 3.14.29 File not found: /lib/modules/3.14.29-55-osmc/build/.config at ./scripts/make_kconfig.pl line 33, <IN> line 4. make: *** No rule to make target '.config', needed by '.myconfig'. Stop. make: Leaving directory '/mediakram/v4l' Makefile:26: recipe for target 'all' failed make: *** [all] Error 2
Install the kmod package
via apt-get install kmod it is already installed apparently.
the scripts/make_kconfig.pl says
WARNING: You do not have the full kernel sources installed.
This does not prevent you from building the v4l-dvb tree if you have the
kernel headers, but the full kernel source may be required in order to use
make menuconfig / xconfig / qconfig.
If you are experiencing problems building the v4l-dvb tree, please try building against a vanilla kernel before reporting a bug. Vanilla kernels are available at http://kernel.org. On most distros, this will compile a newly downloaded kernel: cp /boot/config-`uname -r` <your kernel dir>/.config cd <your kernel dir> make all modules_install install Please see your distro's web site for instructions to build a new kernel.
I think I am getting closer… but I am too inexperienced to know my way out…
The driver ist just a version of the media_build.git which I am trying to get to work for my kernel - if that helps…
It might be a bit tricky to explain this one in detail.
Support for media_build will arrive soon so waiting may be the best solution.
Okay, at least there is hope.
I just wanted to make sure that the adaptor can work with the Vero at all, since I bought it just for that purpose.
Otherwise I would have returned it to maybe buy a Sundtek or something.
If it works under media_build it will eventually (hopefully soon) work under OSMC.
Sweet. Will media_build work for RPI? Although you mentioned a few weeks its not. Would the patch work in that geniatech thread when media_build is available?
No — I don’t plan to use media build for RBP