From: Andreas Fink <finkandreas@web.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] guvcview - no video device (/dev/video0) found
Date: Sun, 14 May 2023 06:31:21 +0200 [thread overview]
Message-ID: <20230514063121.16ee6141@anfink-laptop> (raw)
In-Reply-To: <3d3d3015-a9f9-ea68-32cb-0a9be38ca5ab@sys-concept.com>
On Sat, 13 May 2023 14:50:33 -0600
thelma@sys-concept.com wrote:
> Getting an error message when trying to start usb-cam:
>
> guvcview
> ENCODER: no video codec detected for VP9 (VP9)
> ENCODER: no video codec detected for Theora (ogg theora)
> GUVCVIEW: version 2.0.8
> GUVCVIEW: couldn't open /home/joseph/.config/guvcview2/video0 for read: No such file or directory
> V4L2_CORE: ERROR opening V4L interface: No such file or directory
> GUVCVIEW (2): Guvcview error
> no video device (/dev/video0) found
> GUVCVIEW (Qt5): fatal error (0 devices detected)
> GUVCVIEW (Qt5): creating error dialog
>
> dmesg:
>
> [935066.984348] usb 1-1.4: Product: Vega USB2.0 Camera
> [935066.984350] usb 1-1.4: Manufacturer: Vimicro Corp.
> [936075.049430] usb 1-1.4: USB disconnect, device number 47
> [936080.312412] usb 1-1.4: new high-speed USB device number 48 using xhci_hcd
> [936080.504291] usb 1-1.4: New USB device found, idVendor=0ac8, idProduct=0331, bcdDevice= 1.00
> [936080.504296] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> [936080.504297] usb 1-1.4: Product: Vega USB2.0 Camera
> [936080.504299] usb 1-1.4: Manufacturer: Vimicro Corp.
>
Do you have read/write access to /dev/video0? Try with:
ls -lh /dev/video*
next prev parent reply other threads:[~2023-05-14 4:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-13 20:50 [gentoo-user] guvcview - no video device (/dev/video0) found thelma
2023-05-14 4:31 ` Andreas Fink [this message]
2023-05-15 19:33 ` [gentoo-user] [SOLVED] " thelma
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=20230514063121.16ee6141@anfink-laptop \
--to=finkandreas@web.de \
--cc=gentoo-user@lists.gentoo.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