public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Frans Pop <elendil@planet.nl>
Cc: linux-media@vger.kernel.org
Subject: Re: pac207: problem with Trust USB webcam
Date: Tue, 16 Feb 2010 22:05:30 +0100	[thread overview]
Message-ID: <4B7B089A.4060504@redhat.com> (raw)
In-Reply-To: <201002150038.03060.elendil@planet.nl>

Hi,

You need to use libv4l and have your apps patched
to use libv4l or use the LD_PRELOAD wrapper.

Here is the latest libv4l:
http://people.fedoraproject.org/~jwrdegoede/libv4l-0.6.5-test.tar.gz

And here are install instructions:
http://hansdegoede.livejournal.com/7622.html

Regards,

Hans


On 02/15/2010 12:38 AM, Frans Pop wrote:
> Hello,
>
> I'm having a problem with a (cheap) Trust USB webcam I bought yesterday.
> It works fine under Windows XP.
>
> The device is:
> ID 093a:2460 Pixart Imaging, Inc. Q-TEC WEBCAM 100
>
> For Linux I've found that it is recognized by the gspca_pac207 driver.
> But opening the video device using xawtv or vlc shows nothing.
> Problem seems to be that after I plug it in the led on the device goes
> on, but after a very short time (less than a second) it goes out again.
>
> When I plug it in (after a clean boot), dmesg shows:
> usb 1-2.1: new full speed USB device using ehci_hcd and address 7
> Linux video capture interface: v2.00
> gspca: main v2.8.0 registered
> gspca: probing 093a:2460
> pac207: Pixart Sensor ID 0x27 Chips ID 0x09
> pac207: Pixart PAC207BCA Image Processor and Control Chip detected (vid/pid 0x093A:0x2460)
> gspca: video0 created
> usbcore: registered new interface driver pac207
> pac207: registered
>
> And the following (extra) modules get loaded:
> Module                  Size  Used by
> gspca_pac207            6021  0
> gspca_main             22454  1 gspca_pac207
> videodev               37424  1 gspca_main
> v4l1_compat            12201  1 videodev
> v4l2_compat_ioctl32     9867  1 videodev
>
> I'm running 2.6.33-rc8 (x86_64) on a Debian stable ("Lenny") system.
>
> Kernel config, relevant contents from /sys/kernel/debug/usb/devices and
> output from v4l-info attached. Some other info below.
>
> This is the first time I'm trying a webcam, so it may be that I'm missing
> something obvious. I googled around a fair bit, but nothing I tried helped.
> Any help would be appreciated. I can provide any additional info that's
> needed and test any kernel version.
>
> Cheers,
> FJP
>
> $ ls -l /dev/video0
> crw-rw---- 1 root video 81, 0 2010-02-14 23:16 /dev/video0
> My user account is a member of the video group.
>
> $ xawtv -hwscan
> This is xawtv-3.95.dfsg.1, running on Linux/x86_64 (2.6.33-rc8)
> looking for available devices
> port 100-115
>      type : Xvideo, image scaler
>      name : Intel(R) Textured Video
>
> port 116-116
>      type : Xvideo, image scaler
>      name : Intel(R) Video Overlay
>
> /dev/video0: OK                         [ -device /dev/video0 ]
>      type : v4l2
>      name : CIF Single Chip
>      flags:  capture

  reply	other threads:[~2010-02-16 21:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-14 23:38 pac207: problem with Trust USB webcam Frans Pop
2010-02-16 21:05 ` Hans de Goede [this message]
2010-02-17  0:04   ` Adam Baker
2010-02-17  8:57     ` Hans de Goede
2010-02-17 12:33       ` Frans Pop
2010-02-21 11:29         ` Frans Pop

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B7B089A.4060504@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=elendil@planet.nl \
    --cc=linux-media@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox