Bug 16068

Summary:	uvcvideo gives a black screen for some hardware
Product:	Mageia	Reporter:	AL13N <alien>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	alien, tmb
Version:	4
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	kernel	CVE:
Status comment:

Description AL13N 2015-06-01 22:01:56 CEST

i noticed my webcam has a black video output, and it didn't used to be this way (could be a while ago, like mga2 or something).

in any case, i found out that uvcvideo has 0xffff as default for quirks option.

i'm not certain, but after reading more about this, it has more chance to be a wrong commit rather than a design choice. since the quirks are autodetected anyway and some have very specific quirks which would make it unusable for others.

my device is:

0ac8:3420 Z-Star Microelectronics Corp. Venus USB2.0 Camera

Sweex Hi-Def Webcam

at least 3 quirks need to be turned off:
0x0098

in other words, i need to initialize with "modprobe uvcvideo quirks=0xff67" to make it work.

(quirks=0 also makes it work)

i cannot do much testing about quality cause this is a PoC camera that can only do 176x144@10Hz

the specified quirks that don't work for me are:
( http://www.ideasonboard.org/uvc/faq/ )

UVC_QUIRK_BUILTIN_ISIGHT 0x00000008 The device is an Apple iSight camera. Some versions of those cameras advertise UVC compatibility but use proprietary video data encapsulation that needs to be handled specifically.
UVC_QUIRK_STREAM_NO_FID 0x00000010 Don't use the Frame ID field from the video payload headers. UVC devices are required to toggle the FID bit at every frame, and the uvcvideo driver uses it by default to detect the start of a new frame. Try to set this quirk if the driver doesn't return any frame to applications after successfully starting the video stream.
UVC_QUIRK_FIX_BANDWIDTH 0x00000080 Try to estimate the bandwidth required for uncompressed streams instead on relying on the value reported by the camera. See FAQ 7 for more information.

since these seem to be very specific and seemingly quite disruptive for most devices, i think this is a wrongful commit and should be reverted.

Reproducible:

Steps to Reproduce:

AL13N 2015-06-01 22:02:27 CEST

CC: (none) => alien, tmb

Comment 1 Samuel Verschelde 2015-09-21 13:21:08 CEST

Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Comment 2 Marja Van Waes 2015-10-27 06:58:14 CET

As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too).

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Status: NEW => RESOLVED
Resolution: (none) => OLD