You can try it now [TESTING] Linux 4.9 kernel and improved video stack for Vero 4K / 4K +
I successfully upgraded to 4.9 Kernel:
Linux VERO4K 4.9.113-29-osmc #1 SMP PREEMPT Thu Dec 31 06:21:12 UTC 2020 aarch64
But I’m still getting the same “Requires at least kernel …” messages (see below) when running make allyesconfig
When running make allyesconfig, the code also says “Applying patches for kernel 3.14.29-160-osmc” and “Preparing to compile for kernel version 3.14.29”. Why is that? (since I have 4.9 kernel now)
Results when running make allyesconfig:
osmc@VERO4K:~/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’
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.29WARNING: 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/.config
cd
make all modules_install installPlease 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’
I haven’t looked that this package, but you probably need to run ./configure again. At least that’s how many packages are built. So try
./configure
make allyesconfigDid you get the 4.9 kernel headers as well as the kernel itself?
Did you reboot?
Running uname -a will tell you which kernel is running.
./configure returns:
-bash: ./configure: No such file or directory
I followed the instruction in the link you posted above only.
So I guess I’m missing proper 4.9 kernel headers? Where/how do I get them?
The latest headers package is vero364-headers-4.9.113-26-osmc.
You’ll once again need to run the link command described above.
The media_build we used for 3.14 was based off the 4.9 media stack, so it doesn’t make sense to use media_build anymore. Instead - you can either use a newer media_build (could be complex to sync with media_tree); or backport / port the driver to 4.9. If it’s present in the media_build we use for 3.14, then it should already be present in the 4.9 kernel as an option.
Have you checked if your dongle is already supported by the current 4.9 test image?
I got latest header package and also run the command you mentioned (results see below). Still, I get the exact same results when running make allyesconfig as mentioned in post #22.
osmc@VERO4K:~$ sudo apt-get install vero364-headers-4.9.113-26-osmc
Reading package lists… Done
Building dependency tree
Reading state information… Done
The following package was automatically installed and is no longer required:
vero364-image-3.14.29-158-osmc:arm64
Use ‘sudo apt autoremove’ to remove it.
Suggested packages:
module-init-tools:arm64
Recommended packages:
libc6-dev:arm64 | libc-dev:arm64 gcc:arm64 | c-compiler:arm64 make:arm64
binutils:arm64
The following NEW packages will be installed:
vero364-headers-4.9.113-26-osmc:arm64
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 8465 kB of archives.
After this operation, 54.6 MB of additional disk space will be used.
Get:1 Index of /osmc/osmc/apt videoimprovevero49/main arm64 vero364-headers-4.9.113-26-osmc arm64 26 [8465 kB]
Fetched 8465 kB in 29s (291 kB/s)
Selecting previously unselected package vero364-headers-4.9.113-26-osmc:arm64.
(Reading database … 58310 files and directories currently installed.)
Preparing to unpack …/vero364-headers-4.9.113-26-osmc_26_arm64.deb …
Unpacking vero364-headers-4.9.113-26-osmc:arm64 (26) …
Setting up vero364-headers-4.9.113-26-osmc:arm64 (26) …
Examining /etc/kernel/header_postinst.d.
osmc@VERO4K:~$ sudo ln -s /usr/src/vero364-headers-$(uname -r) /lib/modules/$(uname -r)/build
No. Don’t know where to check that. :\
Yes, I did reboot.
uname -a provides:
Linux VERO4K 4.9.113-29-osmc #1 SMP PREEMPT Thu Dec 31 06:21:12 UTC 2020 aarch64 GNU/Linux
Then there must be something already configured for 3.14. Run make clean and then run the steps from the beginning.
I went to media_build and ran make clean.
After that, I ran make dir DIR=../media and make allyesconfig again. Same result as in post #22.
I’m still not sure why you are trying to build media_build.
You would also need a media_tree.
It’s probably going to be easier to backport it on 4.9 with a custom kernel, then submit PR so we can upstream it.
I’m just following the instructions of those nice guys telling me what to do.
I myself have not much clue about this stuff.
So I guess it comes to me having to buy a new DVB tuner after all.
I’m going to get a Terratec S7. Hope I have more luck with that model. Should be supported, according to the list fzinken shared.
I would be careful there, on the device page it says
Revision 1 and 2 are supported. There is a patch for revision 3, but it never seems to have made it to v4l-dvb
I believe getting the TBS driver compiled might be safer then just getting a different device
Well, so far I’ve failed in getting it to compile.
If anyone knows what else I can besides what’s already been suggested, then let me know. I would be happy to get it running!
So I got a Terratec S7 DVB tuner wie CI Slot.
I ran the TVheadend setup wizard again and found the tuner:
As “pre-defined muxes” I select 19.2E Astra (proper for my region). When I start the scan, it immediately jumps to 100% scan progress without finding any services:
Do I need to configure the TV adapter?
