-
Notifications
You must be signed in to change notification settings - Fork 535
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
Invalid IOCTL call in 4.16 #172
Comments
@umlaeute Hey, is there anything I can do to help debug this? I don't know if the issue is in the kernel, ffmpeg, or v4l2loopback. Thank you, |
i don't know (and will wait until 4.16 shows up in Debian/unstable to do any testing myself). in the meantime, you can enable debugging in the module, and see whether it gives you any additional information:
|
Thanks. I tried it and didnt see any extra output when running ffmpeg, only the same spam. Also, the Ubuntu kernel from below would likely work if you are willing to test it: |
Hi I have the same problem on 4.16.5 Loading the module with Then running With print out on
I don't know what to look for at the moment, but I have noticed that in 4.16.5 at least meta nodes have been added for each device (now when I plug in a real webcam I get to devices I can see that there are errors in dmesg starting with
I may be wrong but is this looking for the meta node at the next index? It does seem that Version used:
|
Have the same issue on Ubuntu 17.10 with 4.16.8. |
I'm on Arch Linux. I had to modify the command a bit but this produces the aforementioned output as well: Also, this results in the same error:
|
I have the same problem. I'm running Arch Linux on a X1 Carbon, 5th gen., with a vanilla 4.18.8-1 kernel and Running the command:
gives:
And running:
gives:
|
Same thing over here.
It's enough to write
for it to fail |
@umlaeute It looks like 4.16 is available in Debian unstable. Are you able to take a look into this issue? Thanks. |
yep. so far I've been able to reproduce the problem (but haven't had time to dig into it) |
@umlaeute The 'solution' is quiet easy: Change line 2096 (https://github.com/umlaeute/v4l2loopback/blob/master/v4l2loopback.c#L2096) to I put solution in quotation marks, because I know too little about v4l2 to guarantee that this change is side effect free. |
It seems the macro is really called KERNEL_VERSION, and if I use that instead everything seems to work. I also don't know if it's correct but it seems to fix this bug. Thanks flipreverse! |
I can confirm that changing line 2096 on v4l2loopback.c to |
Has this been committed into a stable release? I'm still getting the error on version EDIT: I'm stupid. But it would be nice to get it stable nonetheless. ;) |
I had the exact problem and the solution @flipreverse suggested worked for me. Now it is line |
@nimatrueway are you saying that when compiling against linux-4.x, you get different results for that looks very fishy to me (the |
@SicariusNoctis yes, it's in |
@umlaeute Yeah, that's what screwed with my head too. So I tried everything all over again, but this time a bit more carefully, and I realized that I was wrong. Sorry! For everyone else who reads this later: Make sure you remove any older version of v4l2loopback installed your system first:
|
Patch according to umlaeute#172
No success here. Tried all above. Same error. Ubuntu 18.04. @umlaeute |
Still getting this on Ubuntu 18.04 after removing the old version and compiling 0.12.2. from github Kernel version is 4.15.0-62-generic |
@robstewart57 you need a producer first. |
Can you publish a signed version of patched module? I have some problems with inserting unsigned module on my machine with secure boot and |
i only publish source code. but you need the binary to be signed (so: sign yourself :-)) |
I think I have the same exact issue. I've looked up every post online that talks about v4l2loopback issues and nothing has worked so far. My knowledge about kernels, signing binaries and secure boot is 0 so I can't even understand how to use the solutions given above. What I've tried so farFirst I installed the v4l2loopback in a machine without secure boot and everything worked flawlessly. I could use pyfakewebcam or ffmpeg to create streams without any issues. Then I tried installing v4l2loopback in another machine with secure boot (downloading the code from the repository and following the readme instructions). After the installation I got the following error
After this I uninstalled everything using @nimatrueway comment above and tried the following commands:
Which worked as expected creating the /dev/video* files.
Executing ffmpeg I got this error
|
Might be useful if you're stupid like me - I was getting this issue on Arch, and forgot that v4l2loopback comes from the AUR and I didn't update the package (v4l2loopback-dkms) after |
Enviroment
Problem
I cannot use v4l2loopback in 4.16. Reverting to 4.15 works fine. When I try, I get an error about invalid arguments to an IOCTL.
Steps to reproduce:
Load v4l2loopback
Run this script in FFMPEG:
Results of above:
I was not able to find what changed in 4.16 through the kernel release notes.
Thank you, and let me know if you need any more information
Sarnex
The text was updated successfully, but these errors were encountered: