public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Indi <thebeelzebubtrigger@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Still haveing problems with audio and guvcview
Date: Sat, 4 Jun 2011 07:47:21 -0400	[thread overview]
Message-ID: <20110604114721.GB4200@gaurahari.merseine.nu> (raw)
In-Reply-To: <gZVl7-3yX-7@gated-at.bofh.it>

On Sat, Jun 04, 2011 at 11:30:01AM +0200, Mick wrote:
> On Friday 03 Jun 2011 21:10:29 meino.cramer@gmx.de wrote:
> 
> > When i start alsamixer and select with the "soundcard"-selector
> > the audio device of my usb cam ... alsamixer crashes with:
> > 
> >   cannot load mixer controls: Invalid argument
> > 
> > 
> > ...still no sound via usb cam and it seems no chance to use alsamixer
> > with it...damn...this /had/ worked and I dont know what it kills...
> > 
> > mylinux:/home/user>aplay -l
> > **** List of PLAYBACK Hardware Devices ****
> > card 0: SB [HDA ATI SB], device 0: VT2020 Analog [VT2020 Analog]
> >   Subdevices: 2/2
> >   Subdevice #0: subdevice #0
> >   Subdevice #1: subdevice #1
> > card 0: SB [HDA ATI SB], device 1: VT2020 Digital [VT2020 Digital]
> >   Subdevices: 2/2
> >   Subdevice #0: subdevice #0
> >   Subdevice #1: subdevice #1
> 
> Your camera's sound card is not shown here (stating the obvious).
> 
> Have you tried building it as a module and modprobe -v <driver> to see what 
> messages you get?
> 
> > mylinux:/home/user>arecord -l
> > **** List of CAPTURE Hardware Devices ****
> > card 0: SB [HDA ATI SB], device 0: VT2020 Analog [VT2020 Analog]
> >   Subdevices: 2/2
> >   Subdevice #0: subdevice #0
> >   Subdevice #1: subdevice #1
> > card 1: CameraB404271 [USB Camera-B4.04.27.1], device 0: USB Audio [USB
> > Audio] Subdevices: 1/1
> >   Subdevice #0: subdevice #0
> [snip...]
> 
> 
> 
> > !!Loaded ALSA modules
> > !!-------------------
> > 
> > 
> > 
> 
> I would suggest that you build alsa as modules at least for troubleshooting 
> purposes.  I had to do that in the past to get things working in a box, 
> following the recommendation of the devs.
> 

I second that. For years I built the ALSA drivers into the kernel, but
for some reason that started giving me trouble some months back and
after switching to using modules instead it's back to being a carefree
setup.

-- 
caveat utilitor
♫ ❤ ♫ ❤ ♫ ❤ ♫ ❤ 



       reply	other threads:[~2011-06-04 11:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gZHrQ-5lZ-27@gated-at.bofh.it>
     [not found] ` <gZHLc-5Nq-5@gated-at.bofh.it>
     [not found]   ` <gZJ0B-84I-1@gated-at.bofh.it>
     [not found]     ` <gZVl7-3yX-7@gated-at.bofh.it>
2011-06-04 11:47       ` Indi [this message]
2011-06-03 18:32 [gentoo-user] Still haveing problems with audio and guvcview meino.cramer
2011-06-03 18:55 ` Paul Hartman
2011-06-03 20:10   ` meino.cramer
2011-06-04  8:59     ` Mick
2011-06-04 11:42       ` meino.cramer
2011-06-04 19:13         ` Mick
2011-06-04 20:56           ` meino.cramer
2011-06-04 22:25             ` Mick
2011-06-05  3:51               ` meino.cramer
2011-06-05 12:35                 ` Mick
2011-06-05 12:53                   ` meino.cramer
2011-06-05 16:56                     ` Mick
2011-06-05 17:03                       ` meino.cramer
2011-06-05 17:41                         ` Mick
2011-06-04 23:29       ` Paul Hartman

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=20110604114721.GB4200@gaurahari.merseine.nu \
    --to=thebeelzebubtrigger@gmail.com \
    --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