|
[RESOLVED] Using v4l2loopback-dkms with liquorix on latest Ubuntu Mint 20.04
Few months back when I had tried to install v4l2loopback-dkms on my Ubuntu Mint 20.04 setup, running liquorix kernel (because I require low-latency for some audio processing, music applications), it led to some issues. Unfortunately, due to time pressure I had to quickly undo/revert changes, so I don't have the issue logs, or exact messages. However, wondering if there are any already known issues with using v4l2loopback-dkms on this system.
Output of inxi -bxz: :: Code :: $ inxi -bxz
System: Kernel: 5.10.0-14.1-liquorix-amd64 x86_64 bits: 64 compiler: N/A Desktop: MATE 1.24.0 Distro: Ubuntu 20.04.2 LTS (Focal Fossa) Machine: Type: Desktop Mobo: Micro-Star model: H310M PRO-VH (MS-7B33) v: 1.0 serial: <filter> UEFI: American Megatrends v: 1.30 date: 04/02/2018 CPU: 6-Core: Intel Core i5-8400 type: MCP arch: Kaby Lake speed: 1400 MHz min/max: 800/2801 MHz Graphics: Device-1: Intel UHD Graphics 630 vendor: Micro-Star MSI driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz, 1600x900~60Hz OpenGL: renderer: Mesa Intel UHD Graphics 630 (CFL GT2) v: 4.6 Mesa 20.2.6 direct render: Yes Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI driver: r8169 v: kernel port: 3000 bus ID: 01:00.0 Device-2: Qualcomm Atheros AR9271 802.11n type: USB driver: ath9k_htc bus ID: 1-9.1:8 Drives: Local Storage: total: 1.58 TiB used: 565.84 GiB (34.9%) Info: Processes: 305 Uptime: 3d 4h 04m Memory: 15.51 GiB used: 7.39 GiB (47.6%) Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17 inxi: 3.0.38 Thanks for any tips, guidance around potential issues in advance. Back to top |
|||||
|
Overall I recommend you upgrade to Ubuntu 20.10. The DKMS packages for Ubuntu track the kernels in the frozen repository, so even if a new version comes out supporting newer kernels, there's no expectation that Canonical will backport it. The best you can do with Ubuntu is:
1) Stay on latest short lived release 2) Pull / build updated DKMS packages from development release (Hirsute at the moment) 3) Try rebuilding the DKMS package with updated sources from Arch Linux (this can be difficult) 4) Use a different distribution that matches your needs and preferences better Back to top |
|||||
|
Thanks @damentz. I prefer staying on LTS because I use some apps that are not supported so well across new releases. However, I got your point and noted for future updates.
Luckily for me, looks like this time the v4l2loopback-dkms package installation went ahead without any hitch. I could modprobe to add/activate the driver and successfully use the loopback device. Back to top |
|||||
|
Glad you could make it work! Marking as resolved.
Back to top |
|||||
|
All times are GMT - 8 Hours
|
|||||