ERROR: from element /GstPipeline:pipeline0/Gstcamerasrc:camerasrc0: src pad: Internal data flow error. #21
Comments
|
Unlikely to fix but can you uninstall and then try installing using the latest script with icamerasrc-git included and ivsc-driver removed? I'm wondering what would show up in the installation logs this time. |
|
I tried again (Kernel 6.3.5-2-MANJARO) with latet changes from today (8f2b062), and now the install.sh script runs perfectly. test.sh outputarchlinux-ipu6-webcam $ ./test.sh |
|
I also added |
|
Don't need to add the udev rule manually if you used the latest. Man why is it always Manjaro xd |
|
@hinricht dunno what to do with you case. It's working perfectly with my fresh install of Manjaro 22.1. Check out #26 (comment) for the complete environment and logs. I would say at the first glance that your laptop might be using a camera that requires another branch of ipu6-drivers (https://github.com/intel/ipu6-drivers/tree/ccg_plat_adlp) but then #22 (comment) literally has the same laptop and managed to get the camera working. So yeah, no bloody idea. Hey @elhossary If you don't mind, could you give us your laptop model and environment? Let me try in Linux 6.3 in a bit. |
|
@striczkof |
Thanks! So it's neither a hardware issue (literally same laptop) nor Manjaro issue (running on my Manjaro installation right now) so idk lol |
|
See my comment at #26 (comment) that I'm actually using manjaro-sway with Wayland, if this makes a difference. |
|
@striczkof I saw your comment at install.sh logtest.sh logWhich is basically the same as before. I don't know how to proceed, happy to provide more details if needed. |
|
I really don't get why it's trying to get the wrong device instead of OV01A10. Can't really think of anything other than doing a fresh install or so. If you haven't tried already, uninstall every single package related to the camera then try installing again. Trying to think of something else that might be affecting it. WAIT! @hinricht can you show me what comes out of Edit: I'm wrong, it should be OV2740 |
I tried starting the |
|
@hinricht can you show me what comes out of these commands? |
|
@striczkof Sure, here we go: Btw, thank you so much for taking care of my edge case (as it seems) ! |
|
@hinricht literally the same versions as mine :/ No worries mate. Ye, yours is an edge case. You can prolly solve it by just reinstalling Manjaro but I am genuinely interested on why your installation is not working and do something about it if possible to help others too. |
|
Reinstalling is not really an option for me at this moment... Besides that I'm happy to provide as much details as neccessary, just let me know. |
|
After a while I ran Click meI also tried with kernel versions |
|
It keeps getting the wrong device, even though it's supposed to get OV01A10. This literally happened to me months ago before I found this script and I don't even know how that fixed itself other than reinstalling my Arch. It either has to be the HAL or the IPU6 drivers messing up. What comes out of this?: |
Btw, I don't remember if I added this udev rule myself or if it is placed there by the installation process, hope I didn't mess it up: |
|
Doesn't matter if you added it yourself since it's literally the same as the one added by icamerasrc PKGBUILD. And even then, it's only to let you use the camera as non-root. Not at that stage yet lol Your modules check out with mine. So your laptop has OV2740 which is supported and the one that the HAL should get. This is mine: lsmod | grep "ivsc\|ipu\|ov"So now we need to figure up what causes the HAL to keep grabbing the wrong device. Another idea. Try running this with hopes that it will give us more errors to work on: Then after running the tests. Check this one out Last question, does your webcam have an LED indicator? Does it light up when you boot up your PC? Mine does. |
So it looks like the firmware fails in the first place.
I really don't know, at least no LED does light up during boot / after powering on. |
|
TBH I'm having pretty similar issues (XPS 9320) It worked when this script was still quite new, now it doesn't anymore (I had removed it because of hibernation not working at the time) Here is the info that I think might be relevant / useful archlinux-ipu6-webcam/test.sharchlinux-ip6-webcam/install.sh -assudo modprobe -c | grep v4l2loopbackpacman -Q | grep "ipu6\|ivsc\|hal"lsmod | grep "ivsc\|ipu\|ov"dkms statusv4l2-ctl --list-devicessystemctl status v4l2-relayd.serviceI'm running I also have an indicator led, as mentioned by @striczkof, which does not light up when restarting |
|
This seems related: intel/ipu6-drivers#38 (comment) I tried it, but it didn't work for me, same test.sh output as @hinricht , tried several kernals, including standard linux and linux-lts, and linux-zen on arch / garuda Host: 21CB007GPB ThinkPad X1 Carbon Gen 10 |
|
Hey everyone, sorry for disappearing. I keep forgetting to drop an answer because I literally have no idea what could be causing it. Can't do much help until next week because my XPS 9320's screen keeps blacking out when I open the lid too far and it won't get fixed until Monday. (Probably ribbon issue) By the way. I just like to add that this exact issue, with @alba4k logs was literally the same that I experienced before I gave up trying to install it and did a fresh reinstall months after my last attempt with this script, where it worked first try. My idea is that if you try to install the drivers and stuff in some other way before this one. There might be leftover files or symlink. They would then need to be manually removed if the uninstallation keeps missing them. Another idea is that there might be some package that is interacting somehow but extremely unlikely. Gotta come up with better ideas later once I can use my laptop again without crying after the screen turns black for the nth time and have to close and reopen the lid again lol |
|
Hey, though it might be left overs too, tried with a fresh install of garuda-sway and garuda-i3, both failed with the same test.sh results, though different dmesg output due to wayland vs X. Would try with vanilla arch, but it would take some time, so last resort. If there is anything I can do to help, let me know. Brand new X1 Carbon, so no problem reinstalling or installing anything, since there is nothing I need on it yet. |
|
So the error appears when you So, the error seems to come from the files shipped by intel/ipu4-camera-bins either not being signed correctly, or maybe Adler-Lake-P is different from Adler Lake |
|
dmesg has Requesting signed firmware failed sudo dmesg | grep ipu[ 1.645288] intel_ipu6: loading out-of-tree module taints kernel. [ 1.645295] intel_ipu6: module verification failed: signature and/or required key missing - tainting kernel [ 1.646998] intel-ipu6 0000:00:05.0: enabling device (0000 -> 0002) [ 1.647180] intel-ipu6 0000:00:05.0: Device 0x465d (rev: 0x2) [ 1.647199] intel-ipu6 0000:00:05.0: physical base address 0x603c000000 [ 1.647201] intel-ipu6 0000:00:05.0: mapped as: 0x0000000022a35e41 [ 1.647263] intel-ipu6 0000:00:05.0: IPU in secure mode [ 1.647266] intel-ipu6 0000:00:05.0: IPU secure touch = 0x0 [ 1.647268] intel-ipu6 0000:00:05.0: IPU camera mask = 0xff [ 1.662632] intel-ipu6 0000:00:05.0: IPC reset done [ 1.662636] intel-ipu6 0000:00:05.0: cpd file name: intel/ipu6ep_fw.bin [ 1.662669] intel-ipu6 0000:00:05.0: Direct firmware load for intel/ipu6ep_fw.bin failed with error -2 [ 1.662672] intel-ipu6 0000:00:05.0: Requesting signed firmware failed [ 1.662673] intel-ipu6: probe of 0000:00:05.0 failed with error -2 Test shows ov13b10, instead of ov2740, aiqb is looking for wrong file name ./test.sh[07-22 10:00:40.280] CamHAL[ERR] Malformed ET range in exposure time range configuration [07-22 10:00:40.280] CamHAL[ERR] Parse AE eExposure time range failed [07-22 10:00:40.280] CamHAL[ERR] Malformed ET range in exposure time range configuration [07-22 10:00:40.280] CamHAL[ERR] Parse AE gain range failed [07-22 10:00:40.281] CamHAL[ERR] Malformed ET range in exposure time range configuration [07-22 10:00:40.281] CamHAL[ERR] Parse AE eExposure time range failed [07-22 10:00:40.281] CamHAL[ERR] Malformed ET range in exposure time range configuration [07-22 10:00:40.281] CamHAL[ERR] Parse AE gain range failed [07-22 10:00:40.281] CamHAL[ERR] Malformed ET range in exposure time range configuration [07-22 10:00:40.281] CamHAL[ERR] Parse AE eExposure time range failed [07-22 10:00:40.281] CamHAL[ERR] Malformed ET range in exposure time range configuration [07-22 10:00:40.281] CamHAL[ERR] Parse AE gain range failed [07-22 10:00:40.281] CamHAL[ERR] Malformed ET range in exposure time range configuration [07-22 10:00:40.281] CamHAL[ERR] Parse AE eExposure time range failed [07-22 10:00:40.281] CamHAL[ERR] Malformed ET range in exposure time range configuration [07-22 10:00:40.281] CamHAL[ERR] Parse AE gain range failed [07-22 10:00:40.281] CamHAL[ERR] Malformed ET range in exposure time range configuration [07-22 10:00:40.281] CamHAL[ERR] Parse AE eExposure time range failed [07-22 10:00:40.281] CamHAL[ERR] Malformed ET range in exposure time range configuration [07-22 10:00:40.281] CamHAL[ERR] Parse AE gain range failed [07-22 10:00:40.282] CamHAL[ERR] Malformed ET range in exposure time range configuration [07-22 10:00:40.282] CamHAL[ERR] Parse AE eExposure time range failed [07-22 10:00:40.282] CamHAL[ERR] Malformed ET range in exposure time range configuration [07-22 10:00:40.282] CamHAL[ERR] Parse AE gain range failed [07-22 10:00:40.282] CamHAL[ERR] Malformed ET range in exposure time range configuration [07-22 10:00:40.282] CamHAL[ERR] Parse AE eExposure time range failed [07-22 10:00:40.282] CamHAL[ERR] Malformed ET range in exposure time range configuration [07-22 10:00:40.282] CamHAL[ERR] Parse AE gain range failed [07-22 10:00:40.282] CamHAL[ERR] Malformed ET range in exposure time range configuration [07-22 10:00:40.282] CamHAL[ERR] Parse AE eExposure time range failed [07-22 10:00:40.282] CamHAL[ERR] Malformed ET range in exposure time range configuration [07-22 10:00:40.282] CamHAL[ERR] Parse AE gain range failed [07-22 10:00:40.284] CamHAL[ERR] Malformed ET range in exposure time range configuration [07-22 10:00:40.284] CamHAL[ERR] Parse AE eExposure time range failed [07-22 10:00:40.284] CamHAL[ERR] Malformed ET range in exposure time range configuration [07-22 10:00:40.284] CamHAL[ERR] Parse AE gain range failed Setting pipeline to PAUSED ... [07-22 10:00:40.644] CamHAL[INF] aiqb file name ov13b10.aiqb [07-22 10:00:40.644] CamHAL[ERR] there is no aiqb file:ov13b10 [07-22 10:00:40.644] CamHAL[INF] aiqb file name ov13b10.aiqb [07-22 10:00:40.644] CamHAL[ERR] there is no aiqb file:ov13b10 [07-22 10:00:40.644] CamHAL[INF] aiqb file name ov8856.aiqb [07-22 10:00:40.644] CamHAL[ERR] there is no aiqb file:ov8856 [07-22 10:00:40.644] CamHAL[INF] aiqb file name ov8856.aiqb [07-22 10:00:40.644] CamHAL[ERR] there is no aiqb file:ov8856 [07-22 10:00:40.644] CamHAL[INF] aiqb file name ov01a10.aiqb [07-22 10:00:40.645] CamHAL[INF] aiqb file name ov01a10.aiqb [07-22 10:00:40.645] CamHAL[INF] aiqb file name ov01a10.aiqb [07-22 10:00:40.645] CamHAL[INF] aiqb file name ov01a10.aiqb [07-22 10:00:40.645] CamHAL[INF] aiqb file name OV02C10_1BG203N3_ADL.aiqb [07-22 10:00:40.645] CamHAL[INF] aiqb file name OV02C10_1BG203N3_ADL.aiqb [07-22 10:00:40.645] CamHAL[INF] aiqb file name OV02C10_1SG204N3_ADL.aiqb [07-22 10:00:40.646] CamHAL[INF] aiqb file name OV02C10_1SG204N3_ADL.aiqb [07-22 10:00:40.646] CamHAL[INF] aiqb file name OV02C10_CIFME14_ADL.aiqb [07-22 10:00:40.647] CamHAL[INF] aiqb file name OV02C10_CIFME14_ADL.aiqb [07-22 10:00:40.647] CamHAL[INF] aiqb file name OV02C10_1BG203N3_ADL.aiqb [07-22 10:00:40.647] CamHAL[INF] aiqb file name OV02C10_1BG203N3_ADL.aiqb [07-22 10:00:40.647] CamHAL[INF] aiqb file name OV02C10_1SG204N3_ADL.aiqb [07-22 10:00:40.647] CamHAL[INF] aiqb file name OV02C10_1SG204N3_ADL.aiqb [07-22 10:00:40.647] CamHAL[INF] aiqb file name OV02C10_CIFME14_ADL.aiqb [07-22 10:00:40.647] CamHAL[INF] aiqb file name OV02C10_CIFME14_ADL.aiqb [07-22 10:00:40.647] CamHAL[INF] aiqb file name OV2740_CJFLE23_ADL.aiqb [07-22 10:00:40.647] CamHAL[INF] aiqb file name OV2740_CJFLE23_ADL.aiqb [07-22 10:00:40.647] CamHAL[INF] aiqb file name HM2170_1SG205N3_ADL.aiqb [07-22 10:00:40.648] CamHAL[INF] aiqb file name HM2170_1SG205N3_ADL.aiqb [07-22 10:00:40.648] CamHAL[INF] aiqb file name HM2170_CJFME18_ADL.aiqb [07-22 10:00:40.649] CamHAL[INF] aiqb file name HM2170_CJFME18_ADL.aiqb [07-22 10:00:40.649] CamHAL[INF] aiqb file name HI556_1BG502T3_ADL.aiqb [07-22 10:00:40.649] CamHAL[INF] aiqb file name HI556_1BG502T3_ADL.aiqb [07-22 10:00:40.649] CamHAL[INF] aiqb file name HI556_CJFLE25_ADL.aiqb [07-22 10:00:40.650] CamHAL[INF] aiqb file name HI556_CJFLE25_ADL.aiqb [07-22 10:00:40.650] CamHAL[INF] aiqb file name ov01a1s.aiqb [07-22 10:00:40.650] CamHAL[INF] aiqb file name ov01a1s.aiqb [07-22 10:00:40.651] CamHAL[ERR] Failed to find DevName for cameraId: 0, get video node: ov13b10 , devname: /dev/v4l-subdev1 [07-22 10:00:40.653] CamHAL[ERR] MediaControl init failed Failed to set pipeline to PAUSED. Setting pipeline to NULL ... Freeing pipeline ... dkms status has "original module exists" dkms statusipu6-drivers/r103.8e410803b, 6.4.4-zen1-1-zen, x86_64: installed (original_module exists) v4l2loopback/r10.cae2954, 6.4.4-zen1-1-zen, x86_64: installed I don't see the ipu6 devices 4l2-ctl --list-devicesVirtual Camera (platform:v4l2loopback-000): /dev/video0 Otherwise, everything else looks normal sudo modprobe -c | grep v4l2loopbackoptions v4l2loopback exclusive_caps=1 card_label="Virtual Camera" pacman -Q | grep "ipu6\|ivsc\|hal"intel-ipu6-dkms-git r103.8e410803b-1 intel-ipu6ep-camera-bin r44.276859f-1 intel-ipu6ep-camera-hal-git-fix r56.884b81a-1 intel-ivsc-firmware r8.29c5eff-1 lsmod | grep "ivsc\|ipu\|ov"intel_ipu6_isys 180224 0 videobuf2_dma_contig 28672 1 intel_ipu6_isys videobuf2_v4l2 40960 1 intel_ipu6_isys videobuf2_common 90112 4 videobuf2_dma_contig,videobuf2_v4l2,intel_ipu6_isys,videobuf2_memops ov2740 24576 0 intel_ipu6_psys 131072 0 v4l2_fwnode 36864 2 intel_ipu6_isys,ov2740 v4l2_async 28672 3 v4l2_fwnode,intel_ipu6_isys,ov2740 videodev 385024 7 v4l2_async,v4l2_fwnode,videobuf2_v4l2,v4l2loopback,intel_ipu6_isys,ov2740 intel_ipu6 143360 2 intel_ipu6_isys,intel_ipu6_psys mc 90112 6 v4l2_async,videodev,videobuf2_v4l2,intel_ipu6_isys,videobuf2_common,ov2740 systemctl status v4l2-relayd.service● 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 Sat 2023-07-22 09:57:11 CEST; 19min ago
Process: 8205 ExecCondition=/usr/bin/test -n ${VIDEOSRC} (code=exited, status=0/SUCCESS)
Process: 8207 ExecCondition=/usr/bin/test -n $FORMAT (code=exited, status=0/SUCCESS)
Process: 8209 ExecCondition=/usr/bin/test -n $WIDTH (code=exited, status=0/SUCCESS)
Process: 8210 ExecCondition=/usr/bin/test -n $HEIGHT (code=exited, status=0/SUCCESS)
Process: 8211 ExecCondition=/usr/bin/test -n $FRAMERATE (code=exited, status=0/SUCCESS)
Process: 8212 ExecCondition=/usr/bin/test -n ${CARD_LABEL} (code=exited, status=0/SUCCESS)
Main PID: 8213 (v4l2-relayd)
Tasks: 5 (limit: 38098)
Memory: 14.2M
CPU: 107ms
CGroup: /system.slice/v4l2-relayd.service
└─8213 /usr/bin/v4l2-relayd -i icamerasrc -o "appsrc name=appsrc caps=video/x-raw>
|
|
I got rid of the "original module exists" by uninstalling, deleting /var/lib/dkms and reinstalling |
|
Don't think the original module exists matter here as my working DKMS module is saying Sorry guys I am really running out of ideas here if it fails to work on fresh installs too. Just need more data and people with same issues. Seriously, I literally had the same issue and exact errors before and I have no bloody idea how it got fixed. |
|
Thanks! Based on my testing, the icamerasrc blacklist issue appears to be irrelevant anyways as the kernel_install part of my kernel upgrade kills the camera stack permanently anyway by causing the firmware to fail loading. Gotta try to narrow it down furthermore. But fresh logs are still awesome to work on. @alba4k can you send me a log of your |
|
sorry for the delay. I am currently installing from your fork, will post the outputs of everything asap |
|
@striczkof Update on this As someone already mentioned in #42, The build seems to fail with |
|
Oh man, I forgot about that file again. It's added manually by package function but I forgot to remove it from the sources oops |
|
Should be fixed now, let's see how this goes |
sudo pacman -S linux-zentest.shsudo dmesg | grep ipusystemctl status v4l2-relaydv4l2-ctl --list-devicessudo gst-inspect-1.0 icamerasrcRunning without sudo gives back the following: gst-inspect-1.0groups |
|
Uh hey everyone. Sorry, I just murdered my Dell XPS 13 Plus in an extremely stupid liquid metal repasting accident. (100/10 thermals but ded in 10 hours after going home from uni due to blobs of death running amok so 10/10 would recommend again if using barriers) Until Dell support replaces my motherboard, (Dell Premium Support with Accident Protection worth it) I can't help at all with debugging and stuff but I will be completing my PR since that fixes the issue for most people without this extremly rare issue. @alba4k I've noticed that your firmware somehow loads successfully but your HAL seems to get the wrong device again. I'm starting to think it might be a HAL issue. I gotta check once I get my laptop sorted out. Your test logs seem to be interesting though, think I saw that sometime ago but not so sure: @hinricht Since @alba4k is not using kernel-install itself and you do, and the firmware fails to you unlike his setup. Kernel-install is most likely the culprit. Now, time to figure out how kernel-install works then see how it messes up the firmware somehow. But you might also still have the HAL issue like him. Massive thanks to all your help mates! I will keep investigating this weekend or after hopefully. Either I get my motherboard replaced or I have to grind my arse for a month to buy a new one lmao |
|
Damm, sorry for your laptop ahah, did you just not at all use barriers for the metal? What temps were you getting before and after, jusr out of curiosity? that script you see should not be the issue, all it does is copy the old kernel modules into a backup folder and copying them back after pacman deleted the original ones (so the system remains usable), which should not be related to our issue here. I believe you can find it in extra as As for the camera issues, is there anything that you'd want me to try while wating? |
|
I installed kernel |
|
Hey everyone, just got my laptop fixed a week ago but schoolwork and stuff happened. I will be working on testing and getting those workarounds. But I have a very good news for people using dracut. Especially @hinricht ! Thanks to #33 (comment) I just figured out a dracut config that works best (for now). Unlike his comment, I thought that it would just be better to drop the drivers from early loading unless someone wants to take a picture of themselves whilst booting up Arch lol sudo sh -c 'echo -e omit_drivers+=\" intel_ipu6 intel_ipu6_isys intel_ipu6_psys intel_vsc mei_vsc v4l2loopback \" > /etc/dracut.conf.d/ipu6.conf'and just in case: sudo rm /root/.cache/gstreamer-1.0/registry.x86_64.bin
rm ~/.cache/gstreamer-1.0/registry.x86_64.binLet me know what you guys think! I will also post pictures taken before/after the liquid metal disaster tomorrow lol |
|
Hej @striczkof thanks for getting back to this. I tried
Sadly, no luck still :( Here's the test.sh output: Click me |
|
rip. Can you send me your entire dmesg logs? |
|
@striczkof Sure, here you go: Click me |
|
@hinricht it's still loading in the initramfs for some reason, even though omitted. Can you try doing something like |
|
Here you go: |
ipu6 is indeed not included in the dracut and should never even load in the initramfs. did you ever rerun dracut/reinstall the kernel before testign the camera? can you do something like |
|
@striczkof YEAH 🥳 Thanks so much !!! I still cannot access my camera with cheese or chromium though, wonder where I should continue from here.. |
|
how are you running install.sh? you might need -as |
I'll try that in a bit. |
|
So now the WebRTC test works, as well as video in a zoom call. |
|
I'll close this issue now, as it is reported as successfully working in PR #51 . |
|
@striczkof wanna hear something funny? I had the webcam disabled in the firmware... Anyway, it still does not work, but that may or may not be linked to this driver being broken in 6.6, as I had disabled it a long time ago because of the driver not working at the time Again, I still have no idea if it will work now, guess we'll have to see. Maybe |
I came up with that idea but when I tried disabling the camera in the firmware, it showed me different errors in the logs, so ruled against it. @alba4k Intel just fixed their driver now, see if it starts working for you. |
@striczkof Do you mean they fixed the issue related to kernel |
yup they did. the interesting thing is, it prolly breaks reverse compatibility with previous versions due to V4L2 changes. meaning, the current version only works with 6.6.x and beyond. I'm doing it rn, and its gonna be a big one too |
|
@striczkof yes it works!
|
|
@striczkof Thanks again for your help. I'm super happy with the camera support, and am wondering about the long term solution. I guess the official support will be integrated in the mainline kernel, making this project obsolete ? Or how can I imagine the transition to the official kernel module ? Do we need to uninstall drivers from this project at some point once the kernel ships the official modules/drivers ? |
|
they will eventually get into the official kernel, there is work being done We're probably not, however, talking about the next weeks or months: people have been working on this for pretty much 2 years already. But yes, Probably the easiest thing will be to uninstall the packages from this repo as dkms won't be needed anymore |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
I'm trying to get my webcam working on
First, the installation failed during compiling
icamerasrc-gitbut I got it succeeding following these instructions patching icamerasrc-git, and I could succeed with the install script. Here's the installation log:install.sh log
But after reboot the
test.shscript failed withERROR: from element /GstPipeline:pipeline0/Gstcamerasrc:camerasrc0: src pad: Internal data flow error.test.sh log
I also tried with kernel 6.3.5-1 with the same error. What am I missing ?
The text was updated successfully, but these errors were encountered: