-
Notifications
You must be signed in to change notification settings - Fork 15
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
Only working in some programs #1
Comments
I'm an idiot, I didn't have linux-headers installed Now I am able to compile the modules and I do have some /dev/video* devices:
I still don't get any video output tho (I can select a "Virtual Camera" webcam) |
I have the same issue, but I did some steps some steps to get further. And I hope that you or someone can see if these steps get you further. And maybe you can see if you can get even further, and document what you did. I can currently get image from the
Made this file, instead of the instructions @stefanpartheym wrote here Its possible to add more settings here if they may help. The issue is that Firefox and Cheese still does not see the camera. The original test.sh did not work for me, several error, and I got different errors while trying different variations of the command. What worked for me is to replace the contents of
This works for me, if you have wayland I hope it will work for you too. If you have X11 then I believe you can replace I have a Dell XPS 13 Plus 9320 with alder lake |
I also tested this command as the test command, and it works
notable changes are that I removed I have yet to figure out why the test command now works but not v4l2-relayd |
Hi @alba4k,
For me, I also can only select "Virtual Camera". How did out test camera input? Using the test.sh script or in a chromium based browser using this website. Also, I'm currently on kernel Best regards |
I used that website, on firefox tho, and discord (which counts as chromium based ig) I might try this evening in chromium |
Hi @alba4k, I'm gonna be honest: Best regards |
HOLY SH*T, thanks a lot @stefanpartheym The camera actually works in chromium! I had never seen that light turn on! This basically means that whenever I need it for something I can still use it via chromium! Also, while still keeping my expectations low, I also tried cheese (it did not work). What was interesting tho was that is also found an "ipu6" device other than a the Virtual Camera one (I see 2 Virtual Camera and 2 ipu6). huh
Also, about the IR camera, do you think Howdy would now work, as that would be the main use I'd have for the cam. linux-enable-ir-emitter seems to turn on the webcam light when using /dev/video0, but I don't see anyhting flashing using my phone's camera. After some testing: firefox, cheese, discord and gphoto/kamera do NOT work; webcord, chromium and obs work edit: both firefox and discord work with this workaround. edit 2: chese now works too |
Hi @alba4k, I'm glad it works for you on Chromium :)
Unfortunately, I don't know if (or how) Howdy works. I have not yet tried it. I didn't even know such a thing exists. But good hint, I think I'll try it out at some point ;) Best regards |
@stefanpartheym I would certainty recommend trying it out. Apart from that, let me know if you (or some other guy(e.g. on the archlinux forums) get the camera to work in more or, ideally, all scenarios. Congrats on the nice works on creating this repository, also :) |
Hi @alba4k, thank you! I'll let you know, if there are any news on this. ;) I wanted to rename the packages in the repo anyways, as they always appear in the available updates list of my package manager due to the same name of the packages on AUR. Best regards |
Yeah noticed that yesterday, and unfortunately the updates breaks stuff maybe just rename the *-git or * to *-fix-git or *-fix? The best of luck on your continuation! |
Uff, yeah didn't try to update yet, but good to know, that it's not an option haha.
Exactly, something like that, hopefully I'll have the time for this in the next few days. 😬 |
@stefanpartheym @alba4k Has Howdy been updated to python 3 yet? I uninstalled it when python 2 was deprecated on Arch. Howdy worked quite well for me after it was configured properly, but I did not want to have a security related program depend on python 2 after it was deprecated from the repos |
Amazing, chromium does indeed work with the webcam. I didn't test it because I used cheese to test instead. I wonder why it doesn't work with firefox |
@stefanpartheym it sadly does not seem to work anymore on 6.1 |
Hi. I have just finalized the setup on my XPS 13 9320, and indeed I have had to tweak the ipu6_driver installation, because its build is currently broken on 6.1. The fix is ready to merge on Intel's repository but it seems to be stalled 🤷
I am able to get a valid stream from |
@Tropicao Do you want to make a pull request to this repo with this change? It works for me, in fact, both hans' master branch and the ipu6-kernel6.1-build-fix works for me on 6.1.1. But you are maybe correct in using the specific branch in case the master branch is used for something else in the future. Another merge request would be needed to revert this change, if when Intel merges this PR |
I am not convinced it is desirable to point to jwrdegoede repository/branches "by default", because it will multiply the sources to monitor for drivers updates (it would be best to assume that its PR on Intel repository will eventually be merged), but if @stefanpartheym thinks otherwise, I'll gladly submit a PR |
@Tropicao what about temporarily pointing the PKGBUILD file to a specific git commit in the intel repo, and then add Hans' changes as a patch file? That is how many AUR packages do it anyway When the PKGBUILD is updated to get a newer version, the patch can be removed at the same time, so its almost self regulating Just thinking about making it easy for the user who just want to follow some instructions instead of finding comments here and there to compliment the instructions |
I am not very familiar with Arch packaging good practices, so I trust you on this. Its sounds convenient for both user and maintainer.
|
Hey, Thanks for all your effort in this! 😄 I believe the issue with Firefox is the lack of support for the NV12 format, as identified here - https://bugzilla.mozilla.org/show_bug.cgi?id=1761519 In the meanwhile, I got it working by forcing v4l2-relayd to convert to a supported format (YUY2). I'm sure this is not the best way to do it, but I overwrote the service ExecStart by creating the file
It just adds After |
@maharifu I think the theoretical "propper way" to configure this would be in sudo cp /etc/default/v4l2-relayd /etc/v4l2-relayd
sudo -e /etc/v4l2-relayd I changed FORTMAT= to YUY2, the webcam looks like it works in firefox after I do that, but it just shows a single color black. If it can work by editing that file, it can probably be shipped already working in this repo |
@sigboe I believe that FORMAT specifies the input format from the webcam, so it should be NV12. That's why you get the black screen when changing it. The problem is Firefox doesn't handle that format, so we need to convert it before the v4l2sink. Maybe we could have a patch to change the systemd unit file of v4l2-relayd when building the package? |
Hi @Tropicao , thanks a lot for your effort! I merged your PR as requested. Best regards |
I can confirm that it now seems to work on 6.1 :D Also, the workaround proposed by @maharifu does indeed make the webcam work in firefox, and actually in discord too! As for the mentioned workaround, I opened a pull request that allows the changes to be applied automatically when launching the |
That is interesting
|
I select |
Nevermind, it does seem to work now in cheese too! I'm guessing some kernel between 6.1.6 and 6.1.8 did the trick, maybe in combination with the workaround for changing the video format (?). Well, anyway, I think it's working basically everywhere for me now. |
@Tropicao tried with custom patches removed and updated revision and I still cannot get applications seeing the webcam, even though |
Well, I have no clue why applications do not detect camera on your device 🤔 Since |
As a pretty sad sidenote, it eventually stopped working for me too. Something weird I noticed, is that the camera still does turn off for a split second when I turn my laptop on (which it also did when the driver was working.) Anyway, I think I will temporarily be removing the driver, since I don't really need the webcam anyway. |
I think that the issue might be on the driver-side. |
No idea what's going on there, but I've noticed this running ● v4l2-relayd.service - v4l2-relay daemon service
Loaded: loaded (/usr/lib/systemd/system/v4l2-relayd.service; enabled; preset: disabled)
Drop-In: /etc/systemd/system/v4l2-relayd.service.d
└─override.conf
Active: active (running) since Thu 2023-02-02 18:19:44 CET; 14h ago
Main PID: 1182 (v4l2-relayd)
Tasks: 2 (limit: 18692)
Memory: 14.8M
CPU: 59ms
CGroup: /system.slice/v4l2-relayd.service
└─1182 /usr/bin/v4l2-relayd -i icamerasrc -o "appsrc name=appsrc caps=video/x-raw,format=NV12,width=1280,height=720,framerate=30/1 ! videoconvert ! video/x-raw,format=YUY2 ! v4l2sink name=v4l2sink device=/dev/video0"
févr. 02 18:19:43 GuilhemArch systemd[1]: Starting v4l2-relay daemon service...
févr. 02 18:19:44 GuilhemArch systemd[1]: Started v4l2-relay daemon service.
févr. 02 18:19:44 GuilhemArch v4l2-relayd[1182]: gst_element_set_state: assertion 'GST_IS_ELEMENT (element)' failed EDIT : After some investigations, I found out that I needed to install |
Congratulations on finding the solution and making it work :) We should probably add a mention to this in the README or even automate it in the install script |
I might do this tomorrow, if I find a couple of minutes :) |
Yep, could definitively help someone else !
That would be great, thanks ! Just to mention, I'm using pipewire ;) |
Same I would be curious to see if the same happened if someone using pulseaudio would be experiencing the same (most likely, the answer is yes, since pipewire handles a lot of non-audio related media stuff), but I'm too lazy to install it just to check out ;P Anyway, I think I will be opening the PR later this evening (it's 20.28 at the moment of typing for me) |
Ok so, it's not working for me, which I expected, but if any of you can confirm that it works with Also, the reason I suppose it is not working for me, is that the
TL;DR: DKMS doesn't seem to like those modules already (seemingly) being there. One more thing: paru warns about |
Hi @alba4k ,
I'm experiencing the exact same issue. However, it seems like webcam does work regardless (at least in my browser, not with
Yes, same for me when using Best regards |
Well my only opinion is that it's implicit this is a fix for arch, and many AUR packages have -fix suffix while no AUR package has -archfix suffix. So if you are interested in pushing this to AUR, then maybe the -fix suffix would suffice. |
ops forgot to ping @stefanpartheym |
Hi @sigboe,
You're right. However, I didn't plan to push those packages to AUR. With the archfix suffix I wanted to avoid any possible conflicts with packages from AUR. Hope you guys agree, otherwise I'm gonna change the suffix. |
@stefanpartheym Just as an FYI here are the packaging guidelines, I guess you know about them already https://wiki.archlinux.org/title/Arch_package_guidelines |
I guess using Also, @stefanpartheym @sigboe , can you confirm that my fork works, so I know whether to open a pr or not. |
Hi @stefanpartheym. Before seeing your last answer, I was about to preach for a push to AUR : not only for a "fix" package, but to improve existing AUR packages by providing your modifications to those. IMHO, while this whole repository is currently the best way to make the webcam work on alder lake hardware, this package conflict issues (and your suggestion to add a suffix to fix this) highlights a more general issue, which is that we are kind of "forking" what already exists in AUR. While it seems valid as a short term solution (since the webcam support mess is here to stay for a while), any newcomer wanting to make the camera work will be confronted to multiple packages sources : the AUR packages, and your repository. |
Thanks @sigboe @alba4k @Tropicao for all the suggestions. I your answers give a clear direction as to what the suffix should be. Not that I would want to make a huge deal out of this, but you convinced me to use a simple Again thanks to all of you for your input and contributions :) |
Hi @alba4k,
sorry, I didn't check your fork before committing my changes. But yes, go ahead and create a PR, so I can merge your commit :) |
I also agree on not pushing to the aur, to be honest, as it would only add complexity to the already existing mess. I could though add a note on the Arch Wiki mentioning this, as it already mentions the arch support thread from which this was created. I'm currently merging everything with your branch so I can open a pr. Also, @stefanpartheym , if you get the same errors while building the modules, I believe that the only reason the camera works for you is that you already have the modules installed and never uninstalled them (I'm just assuming). Does Also, I do see the webcam led turn on for a split second when running
Edit: Here it is. |
I think this issue could be closed now. Camera still not working in all programs probably. However, with the |
Fully agree. I think that now that the bulk of thee problem is gone (due to the "implicit" format conversion) new issues should be waaay more specific ahah |
First of all, I know this isn't your work, as you mention in the readme, but maybe you'll be able to help anyway, as you probably have a better understanding than me.
Basically, my webcam still doesn't seem to work.
What I find curious and that might be related is a series of errors that pop up while installing the
v4l2loopback
,ipu6-drivers
andivsc-driver
modules packages:(same errors, all that changes is the module name and version)
As you probably noticed, the list of elements is simply a list of the files and directories in my root. My competence in kernel module building is close to none.
Also, if I try to load any of those modules, I get nothing (e.g.
modprobe v4l2loopbaclk
:modprobe: FATAL: Module v4l2loopback not found in directory /lib/modules/6.0.9-arch1-1
;modprobe -r v4l2loopback
:modprobe: FATAL: Module v4l2loopback not found.
)I don't have any /dev/video* virtual devices
Tested on both linux and linux-zen, XPS 13 Plus (i7-1260P)
The text was updated successfully, but these errors were encountered: