Repository navigation
Replies: 35 comments 130 replies
|
Looks like IPU6 may be landing in kernel 6.10! |
|
Does this mean that the camera on my Surface Pro 7+ will work soon (or is working already)? Are any other steps required? I have the linux-surface kernel 6.8.11-300.fc40.x86_64. If I understand correctly, the follow link suggests a patch, but I am unsure how to use the patch: https://github.com/intel/ipu6-drivers. If this patch will be integrated into the kernel within the next few months, I would probably just wait; is this likely? |
It should Just Work™ with the new kernel. You could try patching it yourself, but kernel patching is a bit over my head too. 6.10 is expected to release next month (July), so if you don't mind waiting a bit for the kernel to come out and for it to appear in this repo, that's your best option. |
|
Thanks for the response! That sounds good, I have no problem waiting. |
|
Unfortunately it might take more work than that: The IPU-6 core drivers are a part of it. The other part are the actual sensor(-controller?) drivers. I assume the ones that support IPU-6 are here: https://github.com/intel/ipu6-drivers/tree/master/drivers/media/i2c. I'm not sure if the ones currently in the kernel will support IPU-6 from the start. |
|
According to https://github.com/linux-surface/linux-surface/wiki/Camera-Support, the Surface Pro 7+ uses an OV5693 as its front sensor and an OV8865 as its back sensor. Both have drivers in the mainline kernel. They are also used in IPU3-based machines which are supported by libcamera, so I would expect them to work fine. This being said, depending on the hardware implementation, the kernel may need to hardcode some information related to how power to the sensor is controlled. Many IPU3-based machines needed this, which required some per-machine reverse engineering to figure out the data. I have been told that the IPU6-based machines designed for Windows that are on the market today don't need this, as they don't use a camera power management IC. Depending on whether or not that's correct for the Surface Pro 7+, some more work may be needed. |
|
While IPU-6 work is still ongoing, it's possible that not all sensors used on the IPU-6 Surface devices are going to be supported upstream (at least in the near future). However, there seems to be a guide for writing IPU-6 compatible sensor drivers: https://github.com/hao-yao/ipu6-sensor-guide. Could be useful for anyone willing to look into that. |
|
This is for the proprietary IPU6 camera stack, and fully applicable to libcamera and the ISYS driver merged in the mainline kernel. The requirements of libcamera for the camera sensor driver are listed in https://gitlab.freedesktop.org/camera/libcamera/-/blob/master/Documentation/sensor_driver_requirements.rst?ref_type=heads |
|
Ah I see, thanks for the clarification! |
|
I'm still a little lost: Does this mean for me as a simple end user that the cameras will work with kernel 6.10, or will I have to manually add various fixes, with uncertain outcome? |
|
it means there's a chance the kernel side will work as expect on v6.10 without any further modification, but only testing will confirm. On the userspace side you will need libcamera with soft ISP support. This is under active development, most of the patches have been merged,a few are still missing (IIRC). The soft ISP is a CPU-based implementation of a very simple ISP, needed to work around the lack of a driver for the hardware ISP (the IPU6 PSYS). It will give you somehow usable images, at the cost of extra CPU usage. |
|
Thanks for the explanation! |
|
I can't quite tell when Linux 6.10.x will hit the release for this project. Anyone have any insights on estimates of that? I tried to look around but I'm not entirely sure... 🤔🤔🤔 |
|
We're currently at release candidate 5 (6.10-rc5) in the development cycle. Usually there are 7 RCs (sometimes 8 if a lot of bug reports/fixes come up). Linus generally releases new versions on sunday. So a bit more than 2 weeks until the upstream 6.10 release, if things go well. After that, we need to update our patches. So let's say in about 3 weeks, depending on how much other stuff I have going on. |
|
OH I thought that 6.10 had gone RELEASE, hah. Thanks for clarifying! Much appreciated ;) I guess this project is closer to latest than I realised hehe. But yeah, I do appreciate these estimates, and do realise that they are approximate numbers. ;) |
|
Not really sure if this is the right place to post. Maybe someone can give me hint where to start for "Surface Go 4". I thought this thread could fit, cause for me (as a noob) it seems that that the Go 4 uses IPU6 instead of IPU3 like in Surface Go 1,2 and 3. |
|
IPU6 support isn't included in any released version of libcamera. All patches but one have been merged, so you'll have to compile the master branch from sources, and apply https://patchwork.libcamera.org/patch/20661/. We will likely merge that patch next week and release a new version shortly after. |
|
I thought IPU6 was in Linux 6.10 by default? That's what I thought I saw in the release notes for that version. Either way, yay! Looking forward to this! Thanks! \o/ |
|
So, kernel 6.10 dropped for Arch Linux today (6.10.0-arch1-2) and I installed it as part of a regular update. I did "sudo modprobe intel-ipu6" and then "lsmod | grep ipu". To my joy I got the following back: intel_ipu6_isys 143360 0 It looks like the modules were loaded for my Surface Pro 8's cameras (OV5693 front, OV13858 back). Running "cam --list" returned: [0:16:33.263919051] [4706] ERROR IPAModule ipa_module.cpp:172 Symbol ipaModuleInfo not found So it doesn't look like libcamera has been updated to include the patch. When will this happen? Edit: I'm currently running libcamera 0.3.0-1 on EndeavourOS/Arch Linux. |
|
All required patches have been merged in the libcamera's master branch (to the best of my knowledge). We will likely tag a new version within a week. In the meantime, you can install libcamera from sources. |
|
Thanks, but I think I'll wait until the binary version of libcamera has dropped for my distribution. I've had issues in the past with stuff compiled from source wreaking havoc with official binaries later. Do you know what the version number will be for the next version of libcamera with the patched support, that way I can look out for it? |
|
We've just tagged v0.3.1, that should contain everything you need to get basic IPU6 support (fingers crossed, I don't have an IPU6 machine myself, so I couldn't test it). |
|
"Linux 6.10" refers to the Linux kernel. That's just one component, you also need libcamera (https://libcamera.org/) in userspace. |
|
So what happens after this? Will it be as simple as updating to the new 6.10 kernel and new (patched) version of libcamera to get the cameras to work on the Surface Pro 8? Also, will the camera instructions on the main page be updated to say exactly what's needed to get everything working? Edit: I forgot to ask, what is the status of the 6.10 kernel for Surface devices? |
|
In theory it will be that simple (or complicated). There could be bugs here and there, but that's business as usual. You will get camera support in any application based on libcamera, either directly, such as the qcam test application, or indirectly through pipewire or gstreamer. Given that support for the PSYS is missing, image quality won't be amazing (whether it will match one's expectations or not will depend on subjective criteria), and the camera will burn quite some CPU time (and thus battery). |
|
Thanks for the quick reply. I'm patiently looking forward to this. I would like to do video calls with my family and use Windows Hello (Howdy) while in Linux. |
|
Are we going to need patches from this repository for kernel 6.10? Since it's technically been out for a week. What do we need to do to update to 6.10? |
|
Any update on this? |
|
I'm confused on how to get my cameras working. I'm running EndeavourOS (Arch Linux) with the default 6.10 kernel: [kelvin@kelvin-surfacepro8 ~]$ uname -a I loaded the intel-ipu6 kernel module and verified that it was loaded, like I did before in this thread. I have the 0.3.1-1 version of libcamera installed from the Arch extra-testing repository. However, when I run cam, the cameras are still not recognized: [kelvin@kelvin-surfacepro8 ~]$ cam --list Is there something else I need to do? |
|
I now have permission to those files, and that error about not having permission to open the dma-buf is now gone. It opens However, just running Cheese as my user: Cheese as root: |
Let's try to fix one problem at a time. Can you test the qcam application that comes with libcamera, and see if it works as a normal user ? |
|
I'm pretty sure this works? The webcam light turns on. If I add the Oh and I also used the |
|
OK, so things to be working on the libcamera side, that's good news :-) I'm not very experienced with cheese (I've never used it myself), so I may not be able to help much. From the logs, it seems that running cheese as your user first tries to access the camera through libcamerasrc, and then through the pipewire camera source. The latter fails, and then a fatal error occurs. I don't know if the pipewire source failure is related or not. When running as root, it appears cheese only uses libcamerasrc (or maybe tries the pipewire source element and silently skips it, I suppose because it can't connect to the pipewire session running for your user). |
|
I ran it on my surface pro 8, with the 6.15 kernel and latest libcamera, but no lucks. 0:33:53.222926948] [10615] WARN IPAManager ipa_manager.cpp:108 Public key not valid |
|
A great! Yeah I've noticed this much too. I guess it's just a cheese problem. Fortunately who cares about cheese.
Unfortunately though, I don't see the ipu6 device in applications like Slack. It just doesn't even show up as an option. Firefox shows 32 input devices, none of which work.
Do you know how that can be?
…---- On Thu, 01 Aug 2024 16:42:55 +0200 ***@***.*** wrote ----
OK, so things to be working on the libcamera side, that's good news :-)
I'm not very experienced with cheese (I've never used it myself), so I may not be able to help much. From the logs, it seems that running cheese as your user first tries to access the camera through libcamerasrc, and then through the pipewire camera source. The latter fails, and then a fatal error occurs. I don't know if the pipewire source failure is related or not.
When running as root, it appears cheese only uses libcamerasrc (or maybe tries the pipewire source element and silently skips it, I suppose because it can't connect to the pipewire session running for your user).
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
|
but in your case, it looks like you do not have |
|
Which kernel are you running and on which device? No, |
|
|
|
Oh, you wanted to start slack, the conference tool with libcamerify :D But I can select a Virtual Camera and like 30 different ipu6 cameras, but all of them output a black image.. |
|
Indeed, like this entire thread is commenting about... 🙄 Firefox-wise, I do not need to use libcamerify. It "just works", with one input. I have modified |
|
Hi, everyone. I'm trying to replicate what is being shown in this thread (with the hope of getting the camera to show up) on my i5 SP9 running Zorin OS 17.1. So far, I made sure that:
and built/installed it with the following commands (making sure to mention "simple" in both Dpipelines and Dipas params) Also tried variants like using "all" pipeline/setting Dipas to just simple and rebuilding+reinstalling, but it changed nothing.
Did I miss something? Has anyone else attempted this on their SP9 running ZorinOS or any other Ubuntu-based distro? |
|
Based on the information you've provided, I think the issue is on the kernel side. You may want to check dmesg to see if the intel-ipu6 driver prints any error message. Does the driver get loaded automatically, or do you have to manually load it ? The latter may also indicate something is wrong on the kernel side. |
|
Thank you for the quick reply. Here is the dmesg output Is there anything that can be done on my end (as a layman)? |
|
I'm running the latest surface kernel for Arch, and it seems like the intel-ipu6 module is not included: uname -r sudo modprobe intel-ipu6 What's going on? |
|
I'm frustrated because the 6.10 surface kernel has been out for Arch Linux for well over a week and it's missing the intel_ipu6 modules. I reported it here (#1354 (comment)) and I created a new issue for it (#1531). However, there hasn't been a response to this at all. Has anyone else using Arch on their Surface Pro 8 or greater noticed that the 6.10 surface kernel for Arch is completely missing ipu6 modules? |
|
Yes, I had installed all the packages before with archlinux-ipu6-webcam and now completely removed all packages in the hope that it would just work with the new kernel, but I have no indication of it working.. Is there something we have to do in order to "activate" it or something? I am on Surface Pro 9 |
|
I don't know what's going on, but for some reason the intel_ipu6 kernel modules weren't include in the surface linux Arch 6.10 kernel, but they are included in the standard Arch 6.10 kernel. I keep mentioning this here, but no one is responding with a reason why these modules were omitted. Also, the official libcamera package for Arch was not compiled with 'simple' pipeline handler enabled, so libcamera cannot see the cameras even if the kernel module was present. I filed a issue on libcamera's Arch Gitlab (https://gitlab.archlinux.org/archlinux/packaging/packages/libcamera/-/issues/1) this morning. So, Arch users don't have an ipu6 kernel module for the surface kernel, plus the cameras won't be recognized in user space due to issues with the libcamera package... Ugh! Did the archlinux-ipu6-webcam packages cause the cameras to work before? |
|
Thank you for your research!
It was recognized and I had a virtual camera but no output (only a black picture) |
|
@pinchartl I installed Nobara 40 (Fedora 40) to a spare drive on my Surface 8 last night. I built libcamera from source. It's still not working correctly: kelvin@nobara-surface:/etc/ld.so.conf.d$ lsmod | grep ipu kelvin@nobara-surface:/etc/ld.so.conf.d$ LIBCAMERA_LOG_LEVELS=0 cam --list |
|
You need access to either |
Are udmabuf or dma_heap groups? I can't find them in /etc/group... How do I make these devices accessibile to my username? |
|
No, they are devices, in |
@k4ever, Do you see any 'PLD' warnings in dmesg log? |
|
See answer below. I apologize for the late reply. |
|
Thanks to everyone involved in helping this work reliably! \o/ |
|
@k4ever, Do you see any 'PLD' warnings in dmesg log? |
|
@bingbucao I did not see any "PLD" warnings. My dmesg is attached. |
You may add to this list a HP laptop: HP ENVY x360 2-in-1 Laptop 13-bf0xxx. It has 12th gen Intel core CPU with Alder Lake chipset, and has a ipu6 camera (with hi556 aka INT3537 sensor), and Intel Precise Touch & Stylus (IPTS) touch screen. The camera works nicely with Fedora 41 and the Surface kernel (6.12.7-1). |
Will give it a go again. Tried it before, the camera was 'on' via the light but nothing showed. Really hoping this works so I can make a slow switch to Linux fully. |
|
Can confirm I had the camera working on SP7+ with Fedora 42 live USB ... however: Strangely the GNOME camera app only worked the second time I launched it. Not the first time, here however I was prompted for the camera permission. I forgot if I closed the camera app or if it crashed, but the second time I launched it the camera was working, during this, I observed the curser moving with a delay from using the trackpad. I booted into live USB twice with same observation. The quirks are too strange for me, so decided not to install. |
|
Can't confirm on my SP9 with Fedora 42 |
|
Short followup on SP7+ with Fedora 42: I did install as well as booting with the surface kernel, and haven't experienced the latency with mouse cursor, as described with the live USB. The indicator LED turns on every time the camera app is launched, but an image is only displayed some times, it feels arbitrary and I would approximate it to 1/10 times I open the app. Circulating through other cameras does not produce any images but will crash the camera app. Presumably other cameras would be rear camera and IR camera, but neither of those have been observed to work. |
|
SP7+ on Fedora 43 beta live USB does ask for camera access when opening the GNOME camera app, but no camera detected. |
|
I've attempted to use the camera on SP8 running Fedora 42, but I'm experiencing problems with libcamera. I'm using the latest libcamera (v0.5.0+rpt20250429): When running Full outputFrom debug logs, it appears that |
|
how do you launch camera apps with the version of libcamera you built yourself? I wanted to try v.0.5.1 but after building it, cam/cheese automatically seem to just use the version that came with fedora42. I did btw have image in both cam as well as cheese after relaunching the apps a few times and noted that the default cam app is cropped to the center compared to cheese which appears to display the whole image. (SP7+) |
|
Did you run |
|
Hi! I have a SP10 with Fedora 42, however in my situation, libcamera cannot detect any of the 3 cameras (front, back, IR). I wonder if you have done any previous setup to make them work, thank you! |
|
On SP8, I haven't done anything other than upgrading to the latest kernel to enable camera detection with |
Ah good catch! I assumed that the cameras would be the same for SP8 and 10 given that I saw OV13858 in my terminal. But I booted back to Windows and indeed I have different front cameras: I got I guess that would require further developing right? I'll do more search later but please educate me if you know more! |
|
This Discussion thread is for IPU6, but Surface Book 1 uses IPU3. Here's the relevant Discussion for that. |
|
AI (grok) says the problem can be fixed when |
|
I tried to get the cam working on an surface 8. cam --list any hints how to proceed? |
|
You might want to follow this issue. (#1753 (comment)) |
|
On a Surface Pro 7+ with a Fedora Silverblue 42 derivative, using GNOME Camera (Snapshot), |
|
Any update on the compatibility with newer surface cameras (8, 9 and 10)? |
|
9: #1867 |
|
Good afternoon I am running a SP8 with 6.18.7-surface-1 and I noticed that both back and front cameras are now working but are inverted. Has anyone found a way to change that when using the Camera app in gnome? |
|
It's being worked on linux-surface/kernel#160 |
Thanks for the reply.. I see there is a patch but as I mentioned before, I am pretty new to Linux and I cannot seem to find it for the SP8. Is there a link for it? |
You can try to follow this guide. If you encounter any problem you can open an issue on this repository. |
|
Hi, First, thank you to everyone working on this. I see that there was a PR merge (#1867) that addressed SP9 camera issues. My SP9 rear camera works, while my front camera does not (which reflects the table here: https://github.com/linux-surface/linux-surface/wiki/Camera-Support). I also see that the recent build of the Debian release failed (which I assume contains the fix?). Will the release be live soon? |
|
Good afternoon, cam-l uname -r I know @ruslanbay has been working on 6.19.3 but after I updated, it broke my forward camera and back camera would not display an image. Gonzo |
|
Sorry if my previous comment sounded too harsh or defensive. I just don’t want the trust in the IPU4 project to be undermined, and I also spent several hours double-checking the patches and rebuilding the kernel to make sure everything was correct. |
nope ruslanbay, no need for a sorry or even a response, your post is 100% correct and not too harsh or so. Just ignore that crybabies who require to be sugarcoated 24/7 and cannot control their hurt egos. |
@ruslanbay You did right by apologizing for sounding too harsh or defensive. I've interacted with many people from many different cultures around the world and I have learned that civilized people value civility. When working on projects with many different people, it's civility that allows everyone to participate in the conversation freely without getting emotions involved. It's usually the folks who talk about others being "crybabies" or "sugarcoating" things, particular in my home in the US, that can't handle incivility that is directed towards them. Always keep it civil, and always apologize for any real or perceived incivility on your part. That being said, I haven't been on this thread in quite some time. I'm still experiencing issues with my Surface Pro 8's cameras. I'm using EndeavourOS/Arch Linux, with the latest surface kernel. The rear camera is working now, but the image is also upside down, just like the front camera used to be. The front camera is hit or miss, mostly not working, and throwing a "Failed to set viewfinder format" error when the front camera is selected while running qcam. Here is my total qcam output: qcam |
|
@k4ever It looks like your packaging has a custom tuning file which is out of date and not compatible with some changes that were made upstream: Shows you need to adapt your tuning file to make the camera work again. |
|
After spending some time trying to roll back all of the problems I definitely caused by over a year of tinkering with the camera files, I decided to just do a fresh install of EndeavourOS/Arch Linux. I got the front camera to work. It took a few tries. It worked great and the rotation was correct! I tried to get it to work with Zoom (flatpak), and tried to get it to work with KDE Plasma's v4l2 camera application with libcamerify. It did not work. Now, I can't get the front camera to work at all again, despite a reboot. qcam |
|
Hi! I'm using a Microsoft Surface Go 4 and managed to get the IPU6 rear camera working on Ubuntu 25.10 (kernel 6.17). Rear camera (OV8865) is working via libcamera simple pipeline + PipeWire. I made a setup script for anyone who wants to try: |
|
Just tried out the camera on a fresh fedora 44 install on my SP7+ While the camera was on, I noticed an oscillation in the brightness that didn't happen on fedora 42 or 43. I also noticed that the camera was cropped to what looks like 2x zoom, I guess this is something in the gnome camera app as I have seen this before while not being the case in other webcam apps. If anyone have any ideas how to debug I am happy to try it out. cheers |
Surface Pro 9 (Intel): front camera working - runtime-PM udev rule + cold-boot priming WorkaroundSurface Pro 9 (Intel) camera status with 1. Front camera works with
|
|
Thank you so much for the write-up. I can confirm after going through these steps the front camera now activates reliably in qcam on my SP9 running CachyOS/Arch. As you said, it has a strong blue tint. |
|
Oh I just saw this here. I posted my findings in: #2153 got quite far with both front and back cams for SP10 (sorry posted this earlier with my work account xD oops) |
Surface Pro 10 for Business — IMX681 + OV13858 Camera StatusWhat's workingBoth cameras are detected and functional on Ubuntu 26.04 / kernel 7.0.0-15-generic using the
Driver detailsNew
Key technical challenges solved:
Known issues / remaining work
PRAll patches are on the DKMS modules for testing: |
and others
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
This is a general discussion space for camera support on IPU6 devices. You can use this if you want to ask broad, general questions that don't warrant their own ticket, or you want to share news / your own work (i.e. scripts).
Devices that use IPU6 are:
If you are NOT dealing with hardware, drivers or any other device specific things, please post in the general camera discussion:
If you have a specific issue, please DO NOT post here. Open an issue on the issue tracker instead.
All reactions