Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

modprobe: ERROR: could not insert 'v4l2loopback': Exec format error #288

Closed
ghost opened this issue Apr 20, 2020 · 3 comments
Closed

modprobe: ERROR: could not insert 'v4l2loopback': Exec format error #288

ghost opened this issue Apr 20, 2020 · 3 comments
Labels
invalid not an issue; or the description doesn't make it clear what the actual problem is; or...

Comments

@ghost
Copy link

ghost commented Apr 20, 2020

I installed it with these commands:

git clone https://github.com/umlaeute/v4l2loopback.git
cd v4l2loopback
make CC=/usr/bin/gcc-8
sudo make install
sudo depmod -a

When I run

sudo modprobe v4l2loopback

I get

modprobe: ERROR: could not insert 'v4l2loopback': Exec format error

From sudo dmesg | grep -i v4l2loopback I get

[ 7100.576031] v4l2loopback: loading out-of-tree module taints kernel.
[ 7100.576130] v4l2loopback: module verification failed: signature and/or required key missing - tainting kernel

From uname -a I get

Linux anton 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5+deb10u2 (2019-08-08) x86_64 GNU/Linux

From lsb_release -a I get

No LSB modules are available.
Distributor ID:	PureOS
Description:	PureOS
Release:	9.0
Codename:	amber
@wick-ed
Copy link

wick-ed commented Apr 21, 2020

Hi @unicornofdeath

was the same for me (Ubuntu 18.04).
This issue's comment gave me the solving hint.
Just did make CC=/usr/bin/gcc instead of a blank make.
After that the modprobe command worked. Using the loopback to stream from OBS. :)

@ghost
Copy link
Author

ghost commented Apr 21, 2020

I have tried that and still get same error

@umlaeute
Copy link
Owner

I get this error

which one (probably the one from the title; but it makes a bug-report much easier to read if you don't have to jump through the page for each line)

I have tried to build from source I have download with apt-get I have tried everything and still get error

sorry, i don't understand this sentence.

I get when installed with apt-get

this doesn't look bad (as in: there's no error here).

anyhow: what did you install with apt-get?

I have tried that and still get same error

the point is you must use the same compiler as was used to build your kernel.
this might be /usr/bin/gcc (which is really just an alias to "some" compiler), it might be /usr/bin/gcc-8 (which is a specific compiler, but there's no guarantee that this is the one used to build the kernel)?

you might also consider adding information (as per the template which you seem to have ignoed), such as the kernel you are actually using, and which distribution.

@umlaeute umlaeute added the invalid not an issue; or the description doesn't make it clear what the actual problem is; or... label Apr 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid not an issue; or the description doesn't make it clear what the actual problem is; or...
Projects
None yet
Development

No branches or pull requests

2 participants