USB DVB Tuner not recognized

Hi,

I’ve just installed my Vero4k+. All available updates have been installed.

Afterwards, I connected my TBS5580 USB DVB-S2 Tuner (connected to satellite) to the Vero 4k+ USB port.
Then I followed the instructions given here: Watching live TV with a USB DVB tuner or network TV tuner

Unfortunately, I’m stuck at the step where I should specify the type of network, because I can not find my USB DVB-S2 tuner. All I see is this:

How shall I proceed?

Are you sure that OSMC has a driver for your USB Tuner?

Maybe start with output of
lsusb -tv
and
lsmod

Doesn’t look that good based on here
https://www.linuxtv.org/wiki/index.php/DVB-S2_USB_Devices#Supported_DVB-S2_USB_Devices

No, I am not sure. How/where can I check?
(FYI: of course I meant to say “I can not find my USB DVB-S2 Tuner”)

How do I do that? Where should I put that? (note: unfortunately, I’m a complete Linux newby)

Well, it’s definitely not on the list. But that doesn’t mean it can’t work right? It just means, that it’s probably not supported out of the box?

I have the following model: TBS 5580 (TBS GmbH | 5580 Single Tuner, CI - TBS GmbH)
Linux drivers can be found here (link from manufacturer website): Home · tbsdtv/linux_media Wiki · GitHub

How can I install driver to OSMC?

See explanation below but actually not needed anymore I guess I got enough info.

Details regarding how to access the command line interface can be found here on our Wiki: Accessing the command line - General - OSMC

Well the building and installation is explained on that page. You would need to have a build environment (login with the steps explained above and then run)
sudo apt-get update
sudo apt-get build-essential

But if that drivers build on ARM might be another question

So I access the CLI (e.g. via Putty) and do the following?

  1. run commands
    sudo apt-get update
    sudo apt-get build-essential

  2. run commands as instructed by Home · tbsdtv/linux_media Wiki · GitHub

Yeah give it a try. The most likely issues will come in the make stages of the steps.
While based on this

You also need the headers which might be another issue.

I already fail at the first command from Home · tbsdtv/linux_media Wiki · GitHub

git clone https://github.com/tbsdtv/media_build.git

Result:
-bash: git: command not found

sudo apt-get install git

Well, it seemed to work fine, but there were some “Error 2” during make process.

I can still NOT see my DVB tuner listed under network type when starting the Wizard.

How do you suggest I should proceed? :\

What was the actual error message?

Thanks Tom.

First “error” messages are following (in bold) when issuing command make allyesconfig

make -C /home/osmc/media_build/v4l allyesconfig
make[1]: Entering directory ‘/home/osmc/media_build/v4l’
make[2]: Entering directory ‘/home/osmc/media_build/linux’
Syncing with dir …/…/media
Applying patches for kernel 3.14.29-160-osmc
patch -s -f -N -p1 -i …/backports/api_version.patch
patch -s -f -N -p1 -i …/backports/pr_fmt.patch
patch -s -f -N -p1 -i …/backports/debug.patch
patch -s -f -N -p1 -i …/backports/drx39xxj.patch
patch -s -f -N -p1 -i …/backports/v5.9_tasklet.patch
patch -s -f -N -p1 -i …/backports/v5.7_mmap_read_lock.patch
patch -s -f -N -p1 -i …/backports/v5.7_vm_map_ram.patch
patch -s -f -N -p1 -i …/backports/v5.7_pin_user_pages.patch
patch -s -f -N -p1 -i …/backports/v5.6_pin_user_pages.patch
patch -s -f -N -p1 -i …/backports/v5.6_const_fb_ops.patch
patch -s -f -N -p1 -i …/backports/v5.6_pm_runtime_get_if_active.patch
patch -s -f -N -p1 -i …/backports/v5.5_alsa_pcm_api_updates.patch
patch -s -f -N -p1 -i …/backports/v5.5_memtype_h.patch
patch -s -f -N -p1 -i …/backports/v5.5_dev_printk_h.patch
patch -s -f -N -p1 -i …/backports/v5.4_revert_spi_transfer.patch
patch -s -f -N -p1 -i …/backports/v5.4_dma_buf.patch
patch -s -f -N -p1 -i …/backports/v5.1_vm_map_pages.patch
patch -s -f -N -p1 -i …/backports/v5.1_devm_i2c_new_dummy_device.patch
patch -s -f -N -p1 -i …/backports/v5.0_ipu3-cio2.patch
patch -s -f -N -p1 -i …/backports/v5.0_time32.patch
patch -s -f -N -p1 -i …/backports/v4.20_access_ok.patch
patch -s -f -N -p1 -i …/backports/v4.18_fwnode_args_args.patch
patch -s -f -N -p1 -i …/backports/v4.18_smiapp_bitops.patch
patch -s -f -N -p1 -i …/backports/v4.17_i2c_check_num_msgs.patch
patch -s -f -N -p1 -i …/backports/v4.15_pmdown_time.patch
patch -s -f -N -p1 -i …/backports/v4.14_saa7146_timer_cast.patch
patch -s -f -N -p1 -i …/backports/v4.14_module_param_call.patch
patch -s -f -N -p1 -i …/backports/v4.14_fwnode_handle_get.patch
patch -s -f -N -p1 -i …/backports/v4.13_remove_nospec_h.patch
patch -s -f -N -p1 -i …/backports/v4.13_drmP.patch
patch -s -f -N -p1 -i …/backports/v4.13_fwnode_graph_get_port_parent.patch
patch -s -f -N -p1 -i …/backports/v4.12_revert_solo6x10_copykerneluser.patch
patch -s -f -N -p1 -i …/backports/v4.11_drop_drm_file.patch
patch -s -f -N -p1 -i …/backports/v4.10_sched_signal.patch
patch -s -f -N -p1 -i …/backports/v4.10_fault_page.patch
patch -s -f -N -p1 -i …/backports/v4.10_refcount.patch
patch -s -f -N -p1 -i …/backports/v4.9_mm_address.patch
patch -s -f -N -p1 -i …/backports/v4.9_dvb_net_max_mtu.patch
patch -s -f -N -p1 -i …/backports/v4.9_probe_new.patch
patch -s -f -N -p1 -i …/backports/v4.8_user_pages_flag.patch
patch -s -f -N -p1 -i …/backports/v4.8_em28xx_bitfield.patch
patch -s -f -N -p1 -i …/backports/v4.8_dma_map_resource.patch
patch -s -f -N -p1 -i …/backports/v4.8_drm_crtc.patch
patch -s -f -N -p1 -i …/backports/v4.7_dma_attrs.patch
patch -s -f -N -p1 -i …/backports/v4.7_pci_alloc_irq_vectors.patch
patch -s -f -N -p1 -i …/backports/v4.7_copy_to_user_warning.patch
patch -s -f -N -p1 -i …/backports/v4.7_objtool_warning.patch
patch -s -f -N -p1 -i …/backports/v4.6_i2c_mux.patch
patch -s -f -N -p1 -i …/backports/v4.5_gpiochip_data_pointer.patch
patch -s -f -N -p1 -i …/backports/v4.5_get_user_pages.patch
patch -s -f -N -p1 -i …/backports/v4.5_uvc_super_plus.patch
patch -s -f -N -p1 -i …/backports/v4.5_copy_to_user_warning.patch
patch -s -f -N -p1 -i …/backports/v4.4_gpio_chip_parent.patch
patch -s -f -N -p1 -i …/backports/v4.3_bt87x_const_fix.patch
patch -s -f -N -p1 -i …/backports/v4.2_atomic64.patch
patch -s -f -N -p1 -i …/backports/v4.2_frame_vector.patch
patch -s -f -N -p1 -i …/backports/v4.1_pat_enabled.patch
patch -s -f -N -p1 -i …/backports/v4.1_drop_fwnode.patch
patch -s -f -N -p1 -i …/backports/v4.0_dma_buf_export.patch
patch -s -f -N -p1 -i …/backports/v4.0_drop_trace.patch
patch -s -f -N -p1 -i …/backports/v4.0_fwnode.patch
patch -s -f -N -p1 -i …/backports/v3.19_get_user_pages_unlocked.patch
patch -s -f -N -p1 -i …/backports/v3.19_get_user_pages_locked.patch
patch -s -f -N -p1 -i …/backports/v3.18_drop_property_h.patch
patch -s -f -N -p1 -i …/backports/v3.18_ktime_get_real_seconds.patch
patch -s -f -N -p1 -i …/backports/v3.17_fix_clamp.patch
patch -s -f -N -p1 -i …/backports/v3.17_remove_bpf_h.patch
patch -s -f -N -p1 -i …/backports/v3.16_netdev.patch
patch -s -f -N -p1 -i …/backports/v3.16_wait_on_bit.patch
patch -s -f -N -p1 -i …/backports/v3.16_void_gpiochip_remove.patch
patch -s -f -N -p1 -i …/backports/v3.16_drop_pointing_stick.patch
Patched drivers/media/dvb-core/dvbdev.c
Patched drivers/media/v4l2-core/v4l2-dev.c
Patched drivers/media/rc/rc-main.c
Syncing with dir …/…/media
make[2]: Leaving directory ‘/home/osmc/media_build/linux’
./scripts/make_kconfig.pl /lib/modules/3.14.29-160-osmc/build /lib/modules/3.14.29-160-osmc/build 1
Preparing to compile for kernel version 3.14.29
File not found: /lib/modules/3.14.29-160-osmc/build/.config at ./scripts/make_kconfig.pl line 33, line 4.
make[1]: *** [Makefile:388: allyesconfig] Error 2
make[1]: Leaving directory '/home/osmc/media_build/v4l’
make: *** [Makefile:26: allyesconfig] Error 2

The command make -j4 as the next command provides following error messages (in bold):

make[1]: Entering directory ‘/home/osmc/media_build/v4l’
scripts/make_makefile.pl
Updating/Creating .config
make[2]: Entering directory ‘/home/osmc/media_build/linux’
make[2]: Entering directory ‘/home/osmc/media_build/linux’
Syncing with dir …/…/media
Syncing with dir …/…/media
Patches for 3.14.29-160-osmc already applied.
make[2]: Leaving directory ‘/home/osmc/media_build/linux’
Patches for 3.14.29-160-osmc already applied.
make[2]: Leaving directory ‘/home/osmc/media_build/linux’
./scripts/make_kconfig.pl /lib/modules/3.14.29-160-osmc/build /lib/modules/3.14.29-160-osmc/build
Preparing to compile for kernel version 3.14.29
File not found: /lib/modules/3.14.29-160-osmc/build/.config at ./scripts/make_kconfig.pl line 33, line 4.
make[1]: INTERNAL: Exiting with 1 jobserver tokens (should be 0)!
Preparing to compile for kernel version 3.14.29
File not found: /lib/modules/3.14.29-160-osmc/build/.config at ./scripts/make_kconfig.pl line 33, line 4.
Updating/Creating .config
make[2]: Entering directory ‘/home/osmc/media_build/linux’
make[2]: Entering directory ‘/home/osmc/media_build/linux’
Syncing with dir …/…/media
Syncing with dir …/…/media
Patches for 3.14.29-160-osmc already applied.
make[2]: Leaving directory ‘/home/osmc/media_build/linux’
./scripts/make_kconfig.pl /lib/modules/3.14.29-160-osmc/build /lib/modules/3.14.29-160-osmc/build
Patches for 3.14.29-160-osmc already applied.
make[2]: Leaving directory ‘/home/osmc/media_build/linux’
Preparing to compile for kernel version 3.14.29
File not found: /lib/modules/3.14.29-160-osmc/build/.config at ./scripts/make_kconfig.pl line 33, line 4.
Preparing to compile for kernel version 3.14.29
File not found: /lib/modules/3.14.29-160-osmc/build/.config at ./scripts/make_kconfig.pl line 33, line 4.
make[1]: *** No rule to make target ‘.config’, needed by ‘.myconfig’. Stop.
make[1]: Leaving directory ‘/home/osmc/media_build/v4l’
make: *** [Makefile:26: all] Error 2

Hi,

As @fzinken says, I think you need to install the kernel headers. Please try installing the following packages:

vero364-source-3.14.29-160-osmc
vero364-headers-3.14.29-160-osmc

Then re-run

make allyesconfig
make -j4
sudo make install

Thanks Tom.

I think you might need to run this comand:

sudo ln -s /usr/src/vero364-headers-$(uname -r) /lib/modules/$(uname -r)/build

That said, I can’t get it to compile in the standard (armhf) environment, probably because it’s building for an aarch64 kernel. You might need to use the aarch64-toolchain-osmc package. The error I see is:

osmc@osmc-4k:~/media_build$ make -j4
make -C /home/osmc/media_build/v4l 
make[1]: Entering directory '/home/osmc/media_build/v4l'
make -C firmware prep
creating symbolic links...
make[2]: Entering directory '/home/osmc/media_build/v4l/firmware'
make[2]: Nothing to be done for 'prep'.
make[2]: Leaving directory '/home/osmc/media_build/v4l/firmware'
make -C firmware
make[2]: Entering directory '/home/osmc/media_build/v4l/firmware'
make[2]: Nothing to be done for 'default'.
make[2]: Leaving directory '/home/osmc/media_build/v4l/firmware'
Kernel build directory is /lib/modules/3.14.29-160-osmc/build
make -C ../linux apply_patches
make[2]: Entering directory '/home/osmc/media_build/linux'
Patches for 3.14.29-160-osmc already applied.
make[2]: Leaving directory '/home/osmc/media_build/linux'
make -C /lib/modules/3.14.29-160-osmc/build M=/home/osmc/media_build/v4l  modules
make[2]: Entering directory '/usr/src/vero364-headers-3.14.29-160-osmc'
gcc: error: unrecognized command line option '-mstrict-align'; did you mean '-Wstrict-aliasing'?
KBUILD_CFLAGS_MODULE:-DMODULE  
  CC [M]  /home/osmc/media_build/v4l/altera-lpt.o
gcc: error: unrecognized command line option '-mstrict-align'; did you mean '-Wstrict-aliasing'?
  CC [M]  /home/osmc/media_build/v4l/altera-jtag.o
gcc: error: unrecognized command line option '-mgeneral-regs-only'
gcc: error: unrecognized command line option '-mstrict-align'; did you mean '-Wstrict-aliasing'?
make[3]: *** [scripts/Makefile.build:308: /home/osmc/media_build/v4l/altera-lpt.o] Error 1
make[3]: *** Waiting for unfinished jobs....
gcc: error: unrecognized command line option '-mgeneral-regs-only'
make[3]: *** [scripts/Makefile.build:308: /home/osmc/media_build/v4l/altera-jtag.o] Error 1
make[2]: *** [Makefile:1291: _module_/home/osmc/media_build/v4l] Error 2
make[2]: Leaving directory '/usr/src/vero364-headers-3.14.29-160-osmc'
make[1]: *** [Makefile:53: default] Error 2
make[1]: Leaving directory '/home/osmc/media_build/v4l'
make: *** [Makefile:26: all] Error 2

Unfortunately, I’ll not have a lot of free time today or tomorrow to investigate further.

This didn’t help. I still got the same results as mentioned in my post above.

This seemed to help though. I did not get any errors when issuing command make allyesconfig

But I got following errors (in bold) when issuing command make -j4

make -C /home/osmc/media_build/v4l
make[1]: Entering directory ‘/home/osmc/media_build/v4l’
scripts/make_makefile.pl
./scripts/make_myconfig.pl
[ ! -f “./config-mycompat.h” ] && echo “/* empty config-mycompat.h */” > “./config-mycompat.h” || true
make -C firmware prep
perl scripts/make_config_compat.pl /lib/modules/3.14.29-160-osmc/build ./.myconfig ./config-compat.h
creating symbolic links…
make[2]: Entering directory ‘/home/osmc/media_build/v4l/firmware’
make[2]: Nothing to be done for ‘prep’.
make[2]: Leaving directory ‘/home/osmc/media_build/v4l/firmware’
make -C firmware
make[2]: Entering directory ‘/home/osmc/media_build/v4l/firmware’
make[2]: Nothing to be done for ‘default’.
make[2]: Leaving directory ‘/home/osmc/media_build/v4l/firmware’
Kernel build directory is /lib/modules/3.14.29-160-osmc/build
make -C …/linux apply_patches
make[2]: Entering directory ‘/home/osmc/media_build/linux’
Syncing with dir …/…/media
Patches for 3.14.29-160-osmc already applied.
make[2]: Leaving directory ‘/home/osmc/media_build/linux’
make -C /lib/modules/3.14.29-160-osmc/build M=/home/osmc/media_build/v4l modules
make[2]: Entering directory ‘/usr/src/vero364-headers-3.14.29-160-osmc’
gcc: error: unrecognized command line option ‘-mstrict-align’; did you mean ‘-Wstrict-aliasing’?
KBUILD_CFLAGS_MODULE:-DMODULE
CC [M] /home/osmc/media_build/v4l/altera-lpt.o
gcc: error: unrecognized command line option ‘-mstrict-align’; did you mean ‘-Wstrict-aliasing’?
gcc: error: unrecognized command line option '-mgeneral-regs-only’
CC [M] /home/osmc/media_build/v4l/altera-jtag.o
gcc: error: unrecognized command line option ‘-mstrict-align’; did you mean ‘-Wstrict-aliasing’?
make[3]: *** [scripts/Makefile.build:308: /home/osmc/media_build/v4l/altera-lpt.o] Error 1
make[3]: *** Waiting for unfinished jobs…
gcc: error: unrecognized command line option '-mgeneral-regs-only’
make[3]: *** [scripts/Makefile.build:308: /home/osmc/media_build/v4l/altera-jtag.o] Error 1
make[2]: *** [Makefile:1291: module/home/osmc/media_build/v4l] Error 2
make[2]: Leaving directory ‘/usr/src/vero364-headers-3.14.29-160-osmc’
make[1]: *** [Makefile:53: default] Error 2
make[1]: Leaving directory ‘/home/osmc/media_build/v4l’
make: *** [Makefile:26: all] Error 2
osmc@VERO4K:~/media_build$ sudo apt-get install gcc
Reading package lists… Done
Building dependency tree
Reading state information… Done
gcc is already the newest version (4:8.3.0-1).
gcc set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Any ideas how to proceed?

@dillthedog
Did you get a chance to investigate further?

Btw: Happy new year everyone!

Not on the 3.14 kernel. I noticed that when I ran make allyesconfig, it produced a large number of warnings suggesting that the kernel was too old:

osmc@osmc-4k:~/media_build$ make allyesconfig
make -C /home/osmc/media_build/v4l allyesconfig
make[1]: Entering directory '/home/osmc/media_build/v4l'
make[2]: Entering directory '/home/osmc/media_build/linux'
Patches for 3.14.29-160-osmc already applied.
make[2]: Leaving directory '/home/osmc/media_build/linux'
./scripts/make_kconfig.pl /lib/modules/3.14.29-160-osmc/build /lib/modules/3.14.29-160-osmc/build 1
Preparing to compile for kernel version 3.14.29

***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.

WARNING: This is the V4L/DVB backport tree, with experimental drivers
	 backported to run on legacy kernels from the development tree at:
		http://git.linuxtv.org/media-tree.git.
	 It is generally safe to use it for testing a new driver or
	 feature, but its usage on production environments is risky.
	 Don't use it in production. You've been warned.
BPF_LIRC_MODE2: Requires at least kernel 3.17.0
IR_GPIO_CIR: Requires at least kernel 3.17.0
IR_GPIO_TX: Requires at least kernel 3.17.0
RC_ST: Requires at least kernel 3.15.0
CEC_CORE: Requires at least kernel 3.19.0
MEDIA_CEC_SUPPORT: Requires at least kernel 3.19.0
CEC_CH7322: Requires at least kernel 4.16.0
CEC_CROS_EC: Requires at least kernel 9.255.255
CEC_SECO: Requires at least kernel 4.1.0
V4L2_H264: Requires at least kernel 9.255.255
V4L2_FLASH_LED_CLASS: Requires at least kernel 3.18.0
VIDEO_SOLO6X10: Requires at least kernel 4.5.0
VIDEO_IPU3_CIO2: Requires at least kernel 9.255.255
RADIO_SI470X: Requires at least kernel 3.17.0
I2C_SI4713: Requires at least kernel 3.17.0
RADIO_WL128X: Requires at least kernel 4.13.0
VIDEO_CAFE_CCIC: Requires at least kernel 4.2.0
VIDEO_ASPEED: Requires at least kernel 4.9.0
VIDEO_MUX: Requires at least kernel 4.13.0
VIDEO_OMAP3: Requires at least kernel 9.255.255
VIDEO_XILINX: Requires at least kernel 4.10.0
VIDEO_XILINX_CSI2RXSS: Requires at least kernel 4.13.0
VIDEO_VIMC: Requires at least kernel 3.17.0
VIDEO_TDA1997X: Requires at least kernel 4.15.0
VIDEO_ADV7180: Requires at least kernel 3.17.0
VIDEO_ADV748X: Requires at least kernel 4.8.0
VIDEO_ADV7604: Requires at least kernel 3.17.0
VIDEO_TC358743: Requires at least kernel 3.17.0
VIDEO_TVP5150: Requires at least kernel 3.17.0
VIDEO_TW9910: Requires at least kernel 3.17.0
VIDEO_MAX9286: Requires at least kernel 4.19.0
SDR_MAX2175: Requires at least kernel 3.19.0
VIDEO_I2C: Requires at least kernel 4.17.0
VIDEO_ST_MIPID02: Requires at least kernel 4.10.0
VIDEO_HI556: Requires at least kernel 4.10.0
VIDEO_IMX214: Requires at least kernel 4.10.0
VIDEO_IMX219: Requires at least kernel 4.10.0
VIDEO_IMX258: Requires at least kernel 4.10.0
VIDEO_IMX274: Requires at least kernel 3.17.0
VIDEO_IMX290: Requires at least kernel 4.10.0
VIDEO_IMX319: Requires at least kernel 4.10.0
VIDEO_IMX355: Requires at least kernel 4.10.0
VIDEO_OV2640: Requires at least kernel 3.17.0
VIDEO_OV2659: Requires at least kernel 3.17.0
VIDEO_OV2680: Requires at least kernel 4.10.0
VIDEO_OV2685: Requires at least kernel 3.17.0
VIDEO_OV2740: Requires at least kernel 4.17.0
VIDEO_OV5640: Requires at least kernel 3.19.0
VIDEO_OV5645: Requires at least kernel 3.17.0
VIDEO_OV5670: Requires at least kernel 4.10.0
VIDEO_OV5675: Requires at least kernel 4.10.0
VIDEO_OV5695: Requires at least kernel 3.17.0
VIDEO_OV7251: Requires at least kernel 4.10.0
VIDEO_OV772X: Requires at least kernel 4.19.0
VIDEO_OV7670: Requires at least kernel 3.19.0
VIDEO_OV7740: Requires at least kernel 4.3.0
VIDEO_OV8856: Requires at least kernel 4.10.0
VIDEO_OV9640: Requires at least kernel 3.17.0
VIDEO_OV9650: Requires at least kernel 4.19.0
VIDEO_OV13858: Requires at least kernel 4.5.0
VIDEO_MT9M001: Requires at least kernel 3.17.0
VIDEO_MT9M111: Requires at least kernel 3.18.0
VIDEO_MT9P031: Requires at least kernel 3.17.0
VIDEO_MT9T112: Requires at least kernel 3.17.0
VIDEO_MT9V032: Requires at least kernel 3.19.0
VIDEO_MT9V111: Requires at least kernel 4.10.0
VIDEO_RDACM20: Requires at least kernel 4.10.0
VIDEO_RJ54N1: Requires at least kernel 3.17.0
VIDEO_SMIAPP: Requires at least kernel 4.0.0
VIDEO_ET8EK8: Requires at least kernel 3.17.0
VIDEO_AD5820: Requires at least kernel 3.17.0
VIDEO_AK7375: Requires at least kernel 4.10.0
VIDEO_DW9714: Requires at least kernel 4.10.0
VIDEO_DW9768: Requires at least kernel 4.10.0
VIDEO_DW9807_VCM: Requires at least kernel 4.10.0
VIDEO_ADP1653: Requires at least kernel 3.17.0
MEDIA_TUNER_TDA18250: Requires at least kernel 4.3.0
DVB_M88DS3103: Requires at least kernel 4.7.0
DVB_AF9013: Requires at least kernel 4.7.0
DVB_CXD2820R: Requires at least kernel 4.3.0
DVB_RTL2830: Requires at least kernel 4.7.0
DVB_RTL2832: Requires at least kernel 4.7.0
DVB_MN88443X: Requires at least kernel 4.9.0
SND_BT87X: Requires at least kernel 9.255.255
INTEL_ATOMISP: Requires at least kernel 9.255.255
VIDEO_HANTRO: Requires at least kernel 9.255.255
VIDEO_ROCKCHIP_VDEC: Requires at least kernel 9.255.255
VIDEO_ZORAN: Requires at least kernel 4.18.0
VIDEO_IPU3_IMGU: Requires at least kernel 9.255.255
Created default (all yes) .config file
./scripts/fix_kconfig.pl
make[1]: Leaving directory '/home/osmc/media_build/v4l'

Unfortunately, something is currently broken on my V4K that’s stopping me installing the aarch64-toolchain-osmc package. Short of a full reinstall, I think I’m not going to be able to use the toolchain.

I did try the build on a Pi 3B (kernel 4.19.122). The list of warnings when running make allyesconfig is very short and the errors we see on the V4K don’t occur. The build does fail, but because of a known problem with the headers, for which there is a workaround.

Any idea what I could try to get rid of my above mentioned gcc errors?

EDIT: FWIW, I just checked and I also got the same/similar messages when I ran make allyesconfig that my kernel is too old.

I can get rid of the initial error messages by editing a couple of Makefiles but that just produces new errors. Perhaps things will improve in the 4.9 kernel.

When is 4.9 kernel gonna be available?