Bug 2415297

Created attachment 2114718 [details]
lsusb > lsusb.txt

Created attachment 2114719 [details]
ls -l /sys/bus/i2c/devices/ > i2c-devices.txt

Created attachment 2114720 [details]
ls -l /sys/bus/spi/devices/ > spi-devices.txt

Created attachment 2114721 [details]
journalctl --no-hostname -k > dmesg.txt

Thank you for reporting this as a new bug report. It does work in qcam, right ?

I think that the problem with snapshot and Firefox is that qcam defaults to using the highest resolution which is 3840x2400 where as snapshot will default to 1920x1080 and in Firefox it depends on the website but it typically uses even lower resolutions.

To test this theory I've prepared a test kernel build with the lower resolutions disabled in the sensor. Note that the softISP will still give snapshot the desired resolution by cutting of the excess pixels, so if this works you will get the a quarter of the full-view from the camera centered in the middle of the full-view. Which will give the impression that things are zoomed in. This may be even worse in Firefox.

The kernel test-build to test this is currently building here:

https://koji.fedoraproject.org/koji/taskinfo?taskID=139002470

This should be done building in a couple of hours.

Here are instructions to install a test kernel-build directly from koji (Fedora's build system):

https://fedorapeople.org/~jwrdegoede/kernel-test-instructions.txt

Hi,

So with the original kernel the webcam works with both qcam and snapshot, but doesn't work with browsers I have tried (firefox and chrome).

However running the test kernel you provided it actually works through firefox and is cropped/zoomed in as you describe! While in both qcam and snapshot it looks normal (no zoom).

Thank you for helping me with this,
Kieran.

(In reply to Kieran from comment #6)
> However running the test kernel you provided it actually works through
> firefox and is cropped/zoomed in as you describe! While in both qcam and
> snapshot it looks normal (no zoom).

That is good to know, thank you. I think this may be caused by the presence
of the "SLS Lattice AI USB 2.0" chip listed in your lsusb output.

Let me ask another user with a laptop with a hi556 sensor but without
that chip and then I'll get back to you on this.

We're still trying to figure out why the lower-res modes (which are typically used for video-conferencing) work on some laptop models and not on others:

Can you please run the following command from a terminal:

for i in /sys/bus/acpi/devices/INTC10*; do echo -n "$i "; cat $i/status; done

and copy and paste the output here ?

Note the "cat" part of the command may fail in some cases, this is ok in that case the failure itself tells us what we need to know.

Hi,

Running the command 'for i in /sys/bus/acpi/devices/INTC10*; do echo -n "$i "; cat $i/status; done' gives the output:
/sys/bus/acpi/devices/INTC1042:00 15
/sys/bus/acpi/devices/INTC1062:00 15
/sys/bus/acpi/devices/INTC1062:01 15
/sys/bus/acpi/devices/INTC1062:02 15
/sys/bus/acpi/devices/INTC1062:03 15
/sys/bus/acpi/devices/INTC1062:04 15
/sys/bus/acpi/devices/INTC1062:05 15
/sys/bus/acpi/devices/INTC1064:00 15
/sys/bus/acpi/devices/INTC1077:00 15
/sys/bus/acpi/devices/INTC1083:00 15
/sys/bus/acpi/devices/INTC1092:00 0
/sys/bus/acpi/devices/INTC109D:00 15
/sys/bus/acpi/devices/INTC10D1:00 cat: '/sys/bus/acpi/devices/INTC10D1:00/status': No such file or directory
/sys/bus/acpi/devices/INTC10D2:00 cat: '/sys/bus/acpi/devices/INTC10D2:00/status': No such file or directory
/sys/bus/acpi/devices/INTC10D2:01 cat: '/sys/bus/acpi/devices/INTC10D2:01/status': No such file or directory
/sys/bus/acpi/devices/INTC10D3:00 0

Thank you for the quick response.