mjasner Posted May 10, 2022 Share Posted May 10, 2022 Armbianmonitor: http://ix.io/3Xsq I am attempting to install the v4l2loopback module for my device (Le Potato running Armbian 22.02.1 Bullseye) and am running to some issues. I installed linux-headers-5.10.102-meson64 since that matches the kernel image installed: marc@lepotato:/usr/src$ dpkg -l |grep linux-image ii linux-image-current-meson64 22.02.1 arm64 Linux kernel, armbian version 5.10.102-meson64 current marc@lepotato:/usr/src$ dpkg -l |grep linux-headers ii linux-headers-current-meson64 22.02.1 arm64 Linux kernel headers for 5.10.102-meson64 on arm64 current But when I try and install the v4l2loopback-dkms package I get the following: marc@lepotato:/usr/src$ sudo apt-get 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: caffeine python3-ewmh python3-xlib Use 'sudo apt autoremove' to remove them. Suggested packages: v4l2loopback-utils The following NEW packages will be installed: v4l2loopback-dkms 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/36.2 kB of archives. After this operation, 115 kB of additional disk space will be used. Selecting previously unselected package v4l2loopback-dkms. (Reading database ... 195673 files and directories currently installed.) Preparing to unpack .../v4l2loopback-dkms_0.12.5-1_all.deb ... Unpacking v4l2loopback-dkms (0.12.5-1) ... Setting up v4l2loopback-dkms (0.12.5-1) ... Loading new v4l2loopback-0.12.5 DKMS files... Building for 5.10.102-meson64 Building initial module for 5.10.102-meson64 Error! Bad return status for module build on kernel: 5.10.102-meson64 (aarch64) Consult /var/lib/dkms/v4l2loopback/0.12.5/build/make.log for more information. dpkg: error processing package v4l2loopback-dkms (--configure): installed v4l2loopback-dkms package post-installation script subprocess returned error exit status 10 Errors were encountered while processing: v4l2loopback-dkms E: Sub-process /usr/bin/dpkg returned an error code (1) Looking into the error logs I see: marc@lepotato:/usr/src$ cat /var/lib/dkms/v4l2loopback/0.12.5/build/make.log DKMS make.log for v4l2loopback-0.12.5 for kernel 5.10.102-meson64 (aarch64) Tue 10 May 2022 01:21:37 PM EDT Building v4l2-loopback driver... make -C /lib/modules/5.10.102-meson64/build M=/var/lib/dkms/v4l2loopback/0.12.5/build modules make[1]: Entering directory '/usr/src/linux-headers-5.10.102-meson64' CC [M] /var/lib/dkms/v4l2loopback/0.12.5/build/v4l2loopback.o MODPOST /var/lib/dkms/v4l2loopback/0.12.5/build/Module.symvers make[3]: *** No rule to make target 'scripts/module.lds', needed by '/var/lib/dkms/v4l2loopback/0.12.5/build/v4l2loopback.ko'. Stop. make[3]: *** Waiting for unfinished jobs.... CC [M] /var/lib/dkms/v4l2loopback/0.12.5/build/v4l2loopback.mod.o make[2]: *** [scripts/Makefile.modpost:130: __modpost] Error 2 make[1]: *** [Makefile:1726: modules] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.10.102-meson64' make: *** [Makefile:43: v4l2loopback.ko] Error 2 I googled around for that error and found a lot of posts about it and found a suggested solution of downloading the module.lds file from git using: sudo wget https://raw.githubusercontent.com/torvalds/linux/master/scripts/module.lds.S -O /usr/src/[your linux header version here]/scripts/module.lds sudo sed -i '$ d' /usr/src/[your linux header version here]/scripts/module.lds but when I try and reinstall the v4l2loopback module after that I now get the following: marc@lepotato:/usr/src$ sudo apt-get install v4l2loopback-dkms Reading package lists... Done Building dependency tree... Done Reading state information... Done v4l2loopback-dkms is already the newest version (0.12.5-1). The following packages were automatically installed and are no longer required: caffeine python3-ewmh python3-xlib Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up v4l2loopback-dkms (0.12.5-1) ... Removing old v4l2loopback-0.12.5 DKMS files... ------------------------------ Deleting module version: 0.12.5 completely from the DKMS tree. ------------------------------ Done. Loading new v4l2loopback-0.12.5 DKMS files... Building for 5.10.102-meson64 Building initial module for 5.10.102-meson64 Error! Bad return status for module build on kernel: 5.10.102-meson64 (aarch64) Consult /var/lib/dkms/v4l2loopback/0.12.5/build/make.log for more information. dpkg: error processing package v4l2loopback-dkms (--configure): installed v4l2loopback-dkms package post-installation script subprocess returned error exit status 10 Errors were encountered while processing: v4l2loopback-dkms E: Sub-process /usr/bin/dpkg returned an error code (1) marc@lepotato:/usr/src$ cat /var/lib/dkms/v4l2loopback/0.12.5/build/make.log DKMS make.log for v4l2loopback-0.12.5 for kernel 5.10.102-meson64 (aarch64) Tue 10 May 2022 01:27:58 PM EDT Building v4l2-loopback driver... make -C /lib/modules/5.10.102-meson64/build M=/var/lib/dkms/v4l2loopback/0.12.5/build modules make[1]: Entering directory '/usr/src/linux-headers-5.10.102-meson64' CC [M] /var/lib/dkms/v4l2loopback/0.12.5/build/v4l2loopback.o MODPOST /var/lib/dkms/v4l2loopback/0.12.5/build/Module.symvers CC [M] /var/lib/dkms/v4l2loopback/0.12.5/build/v4l2loopback.mod.o LD [M] /var/lib/dkms/v4l2loopback/0.12.5/build/v4l2loopback.ko ld:scripts/module.lds:6: ignoring invalid character `#' in expression ld:scripts/module.lds:6: syntax error make[3]: *** [scripts/Makefile.modfinal:40: /var/lib/dkms/v4l2loopback/0.12.5/build/v4l2loopback.ko] Error 1 make[2]: *** [scripts/Makefile.modpost:130: __modpost] Error 2 make[1]: *** [Makefile:1726: modules] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.10.102-meson64' make: *** [Makefile:43: v4l2loopback.ko] Error 2 At this point I am stuck. Am I missing something obvious? Can someone point me in the right direction? Thanks in advance! 0 Quote Link to comment Share on other sites More sharing options...
Werner Posted May 10, 2022 Share Posted May 10, 2022 I think this is a known issue. Still odd since Armbian does not touch modules.lds on packaging IIRC... 0 Quote Link to comment Share on other sites More sharing options...
mjasner Posted May 10, 2022 Author Share Posted May 10, 2022 Is there a workaround or does this just not work at the moment? 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.