Jump to content
Vaa

linux-headers-5.10.160

Recommended Posts

This is 5.10.110 headers for previous version Debian 3.0.6

Does it suit for a new Debian 3.0.11 which has 5.10.160 kernel?

Share this post


Link to post
Share on other sites

Downloaded once again, still the same situation.

What I did:

1. sudo apt update && sudo apt upgrade

2. uname -a

Linux infopro 5.10.160 #1 SMP Tue Oct 24 03:20:27 UTC 2023 aarch64 GNU/Linux

3. sudo apt reinstall ./linux-headers-5.10.160_5.10.160-1_arm64.deb

...

Setting up linux-headers-5.10.160 (5.10.160-1) ...
W: Repository is broken: linux-headers-5.10.160:arm64 (= 5.10.160-1) has no Size information
 

4. Reboot and Trying to install v4l2loopback-dkms package anyway.

...

DKMS: install completed.
Module build for kernel hci_uart.ko was skipped since the
kernel headers for this kernel does not seem to be installed.
Module build for kernel rtk_btusb.ko was skipped since the
kernel headers for this kernel does not seem to be installed.
 

5. sudo modprobe v4l2loopback devices=1 video_nr=10

Fails

 

Share this post


Link to post
Share on other sites

hello @Vaa

we tested and confirmed that v4l2loopback can be installed.

install header:

sudo dpkg -i linux-headers-5.10.160_5.10.160-1_arm64.deb
sudo apt update
sudo apt-get -y install v4l2loopback-dkms

logs of v4l2loopback installation:

root@linaro-alip:/# sudo apt-get -y install v4l2loopback-dkms
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  liba52-0.7.4 libdca0
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  dctrl-tools dkms
Suggested packages:
  debtags menu v4l2loopback-utils
Recommended packages:
  fakeroot linux-headers-686-pae | linux-headers-amd64 | linux-headers-generic
  | linux-headers
The following NEW packages will be installed:
  dctrl-tools dkms v4l2loopback-dkms
0 upgraded, 3 newly installed, 0 to remove and 26 not upgraded.
Need to get 215 kB of archives.
After this operation, 835 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bullseye/main arm64 dctrl-tools arm64 2.24-3 [101 kB]
Get:2 http://deb.debian.org/debian bullseye/main arm64 dkms all 2.8.4-3 [78.2 kB]
Get:3 http://deb.debian.org/debian bullseye/main arm64 v4l2loopback-dkms all 0.12.5-1 [36.2 kB]
Fetched 215 kB in 0s (579 kB/s)
Selecting previously unselected package dctrl-tools.
(Reading database ... 87411 files and directories currently installed.)
Preparing to unpack .../dctrl-tools_2.24-3_arm64.deb ...
Unpacking dctrl-tools (2.24-3) ...
Selecting previously unselected package dkms.
Preparing to unpack .../archives/dkms_2.8.4-3_all.deb ...
Unpacking dkms (2.8.4-3) ...
Selecting previously unselected package v4l2loopback-dkms.
Preparing to unpack .../v4l2loopback-dkms_0.12.5-1_all.deb ...
Unpacking v4l2loopback-dkms (0.12.5-1) ...
Setting up dctrl-tools (2.24-3) ...
Setting up dkms (2.8.4-3) ...
Setting up v4l2loopback-dkms (0.12.5-1) ...
Loading new v4l2loopback-0.12.5 DKMS files...
It is likely that 5.10.160 belongs to a chroot's host
Building for 5.10.160, hci_uart.ko and rtk_btusb.ko
Building initial module for 5.10.160
Done.

v4l2loopback.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.10.160/updates/dkms/

depmod.....

DKMS: install completed.
Module build for kernel hci_uart.ko was skipped since the
kernel headers for this kernel does not seem to be installed.
Module build for kernel rtk_btusb.ko was skipped since the
kernel headers for this kernel does not seem to be installed.
Processing triggers for man-db (2.9.4-2) ...
root@linaro-alip:/#

 

15 hours ago, Vaa said:

W: Repository is broken: linux-headers-5.10.160:arm64 (= 5.10.160-1) has no Size information

however we didn't see this warning -- have you modified the sourcelist? 

Share this post


Link to post
Share on other sites

Thank you very much for your support.

I made clean installation, not touching anything and not making any other installations and system settings.

I Installed what you suggest in previous post.

I got It "looks like everything is installed well", but in the end I run modprobe v4l2loopback and I got Segmentation fault.

Looks like the v4l2loopback-dkms package is not well communicate to kernel.

So, after all, I give back and return to previous Debian 3.0.6 installation.

Thank you again!

 

 

Share this post


Link to post
Share on other sites

hello @Vaa

it's strange because it should work on v.3.0.11. does the same problem persist when you use v.3.0.6?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...