Bug 2420925

Summary: Camera not working even with qcam on new Dell Pro 14 Premium PA14250
Product: [Fedora] Fedora Reporter: tgkim
Component: kernelAssignee: Justin M. Forbes <jforbes>
Status: NEW --- QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 43CC: acaringi, adscvr, airlied, axel.elfner, hans, hpa, jforbes, josef, kernel-maint, linville, masami256, mchehab, ptalbert, steved, suraj.ghimire7, traxtopel
Target Milestone: ---Keywords: Desktop
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2413656    
Bug Blocks:    
Attachments:
Description Flags
journalctl -b 0 -k > kernel.txt
none
ls -l /sys/bus/i2c/devices/ > i2c-devices.txt
none
lsusb > lsusb.txt
none
ls -l /sys/bus/spi/devices/ > spi-devices.txt
none
qcam command output
none
qcam output
none
journalctl -b 0 -k > kernel.1211.txt
none
Analysis of issue from Claude Code / Opus 4.7 none

Description tgkim 2025-12-10 08:42:43 UTC
1. Please describe the problem:
I have a new PC of Dell Pro 14 Premium PA14250.  The internal camera is not working.  qcam returns errors like "Unable to get rectangle 2 on pad 0/0: Inappropriate ioctl for device" and finally results in "No such device" 

2. What is the Version-Release number of the kernel:
uname -r
6.17.10-300.fc43.x86_64

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
Not working ever since new fresh install of Fedora 43.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
Reboot & run qcam 

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:
Didn't tried.

6. Are you running any modules that not shipped with directly Fedora's kernel?:
None.

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.




Reproducible: Always

Comment 1 tgkim 2025-12-10 08:46:42 UTC
Created attachment 2118270 [details]
journalctl -b 0 -k > kernel.txt

Comment 2 tgkim 2025-12-10 08:47:27 UTC
Created attachment 2118271 [details]
ls -l /sys/bus/i2c/devices/ > i2c-devices.txt

Comment 3 tgkim 2025-12-10 08:47:48 UTC
Created attachment 2118272 [details]
lsusb > lsusb.txt

Comment 4 tgkim 2025-12-10 08:48:11 UTC
Created attachment 2118273 [details]
ls -l /sys/bus/spi/devices/ > spi-devices.txt

Comment 5 tgkim 2025-12-10 08:48:51 UTC
Created attachment 2118274 [details]
qcam command output

Comment 6 Hans de Goede 2025-12-10 09:57:49 UTC
This seems to be the same problem as bug 2413656, see bug 2413656 comment 1 for a workaround.

Looking at your logs you can skip step 6. of the workaround.

Comment 7 tgkim 2025-12-11 04:08:56 UTC
Created attachment 2118342 [details]
qcam output

Comment 8 tgkim 2025-12-11 04:10:10 UTC
Created attachment 2118343 [details]
journalctl -b 0 -k > kernel.1211.txt

Comment 9 tgkim 2025-12-11 04:11:43 UTC
Actions checked/done following bug 2413656 comment 1 
1~4: checked & okay
5. done
6. skipped
7. qcam works with low resolution.  qcam return 4 errors of "Unable to get rectangle" and several warning msgs. (see attached log: qcam-output.1211.txt). 
Tried camera test with Teams site(https://teams.microsoft.com/v2/) in Chrome browser (chrome://flags/  PipeWire Camera support = enabled)
> camera seems to be detected but only black screen comes out (see attached log: journalctl -b 0 -k > kernel.1211.txt)

Comment 10 axel.elfner 2026-05-09 16:06:36 UTC
Created attachment 2140482 [details]
Analysis of issue from Claude Code / Opus 4.7

I encountered this same issue with my new laptop for work and and was told by internal support to open a report, but first searched and found this.  Will try workaround, but wanted to assist if possible by submitting analysis from Claude, in case it helps.

Comment 11 axel.elfner 2026-05-09 16:16:00 UTC
Ah, I will not be performing the workaround, as this is a system maintained by my employer and kernel/driver hacking won't mesh w/that.  Will wait for a patch through standard update channel.  Thanks.

Comment 12 traxtopel 2026-05-14 15:48:24 UTC
I opened a new bug report for the same issue to avoid cluttering the existing one. My hardware may be slightly different, and the workaround isn’t working
https://bugzilla.redhat.com/show_bug.cgi?id=2477461