Bug 5400

Summary: video aquisition card Hauppage Bt878 Video Capture does not work
Product: Mageia Reporter: papoteur <yvesbrungard>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal CC: dan, nic, rwobben
Version: CauldronKeywords: NEEDINFO
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: tvtim xawtv CVE:
Status comment:
Attachments: lspcidrake -v and dmesg

Description papoteur 2012-04-14 16:29:08 CEST
Description of problem:
The card can not used with this two applications. When launched in console:
$ tvtime
Utilise tvtime 1.0.2.
Lit la configuration depuis /etc/tvtime/tvtime.xml
I/O warning : failed to load external entity "/root/.tvtime/tvtime.xml"
xvoutput: No XVIDEO port found which supports YUY2 images.

*** tvtime requires hardware YUY2 overlay support from your video card
*** driver. If you are using an older NVIDIA card (TNT2), then
*** this capability is only available with their binary drivers.
*** For some ATI cards, this feature may be found in the experimental
*** GATOS drivers: http://gatos.souceforge.net/
*** If unsure, please check with your distribution to see if your
*** X driver supports hardware overlay surfaces.

$ xawtv
This is xawtv-3.99.rc6, running on Linux/x86_64 (3.3.1-desktop-2.mga2)
xinerama 0: 1400x1050+0+0
WARNING: No DGA direct video mode for this display.
WARNING: keeping fbuf pitch at: 5600, as no base addr was detected
WARNING: couldn't find framebuffer base address, try manual
configuration ("v4l-conf -a <addr>")
v4l2: WARNING: framebuffer base address mismatch
v4l2: me=(nil) v4l=(nil)
ioctl: VIDIOC_QBUF(index=0;type=VIDEO_CAPTURE;bytesused=0;flags=0x0 [];field=ANY;;timecode.type=0;timecode.flags=0;timecode.frames=0;timecode.seconds=0;timecode.minutes=0;timecode.hours=0;timecode.userbits="";sequence=0;memory=MMAP): Périphérique ou ressource occupé
libv4l2: error turning on stream: Périphérique ou ressource occupé
ioctl: VIDIOC_STREAMON(int=1): Périphérique ou ressource occupé
ioctl: VIDIOC_QBUF(index=0;type=VIDEO_CAPTURE;bytesused=0;flags=0x0 [];field=ANY;;timecode.type=0;timecode.flags=0;timecode.frames=0;timecode.seconds=0;timecode.minutes=0;timecode.hours=0;timecode.userbits="";sequence=0;memory=MMAP): Périphérique ou ressource occupé
libv4l2: error dequeuing buf: Argument invalide
ioctl: VIDIOC_DQBUF(index=0;type=VIDEO_CAPTURE;bytesused=0;flags=0x0 [];field=ANY;;timecode.type=0;timecode.flags=0;timecode.frames=0;timecode.seconds=0;timecode.minutes=0;timecode.hours=0;timecode.userbits="";sequence=0;memory=MMAP): Argument invalide
Comment 1 papoteur 2012-04-14 16:30:39 CEST
Created attachment 1990 [details]
lspcidrake -v and dmesg
Comment 2 papoteur 2012-04-14 16:33:24 CEST
I precise that xawtv displays a black screen which is dead.
Comment 3 Marja Van Waes 2012-05-26 13:10:27 CEST
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 4 roelof Wobben 2013-01-03 09:47:29 CET
Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,

Roelof

CC: (none) => r.wobben

Comment 5 Dan Fandrich 2013-07-22 22:30:21 CEST
Mageia 3 comes with kernel drivers for PCI devices 109e:036e and 109e:0878. Are you able to get the card to work with any other software besides those two? Do you get a picture in test.jpg after running the command:

gst-launch-1.0 v4l2src device=/dev/video0 num-buffers=1 ! jpegenc ! filesink location=test.jpg

Change /dev/video0 to be the video device name of your capture card, and try gst-launch-0.10 if you don't have the one above.

CC: (none) => dan

Comment 6 Nic Baxter 2015-03-31 02:47:27 CEST
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

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