public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Still haveing problems with audio and guvcview
Date: Sun, 5 Jun 2011 18:41:28 +0100	[thread overview]
Message-ID: <201106051841.30532.michaelkintzios@gmail.com> (raw)
In-Reply-To: <20110605170333.GD3043@solfire>

[-- Attachment #1: Type: Text/Plain, Size: 2363 bytes --]

On Sunday 05 Jun 2011 18:03:33 meino.cramer@gmx.de wrote:
> Mick <michaelkintzios@gmail.com> [11-06-05 19:00]:
> > On Sunday 05 Jun 2011 13:53:49 meino.cramer@gmx.de wrote:
> > > this is becoming interesting beyond the goal of solving the problem as
> > > such more and more ;)
> > > 
> > > Is there a way to get the default settings of the listed parameters
> > > above when the module is loading without giving any additional params
> > > on the command line?
> > 
> > Yes.  They ought to show in dmesg when the module is loaded and the
> > device probed.  Sometimes they also show if you run modprobe with -v and
> > the debug module parameter is switched to verbose (only some modules
> > have this parameter).
> > 
> > They also show conveniently under alsa-info (since we're talking here
> > about a sound module):
> > 
> > !!Module: snd_usb_audio
> > 
> >         async_unlink : Y
> >         device_setup : 0,0,0,0,0,0,0,0
> >         enable : Y,Y,Y,Y,Y,Y,Y,Y
> > 
> > (this is the array we were talking about and it is enabled)
> > 
> >         id : (null),(null),(null),(null),(null),(null),(null),(null)
> >         ignore_ctl_error : N
> > 
> > (this is the ignore ctl error and is not ignored, so you could switch
> > this to yes and see if it makes a difference)
> > 
> >         index : -1,-1,-1,-1,-1,-1,-1,-1
> >         nrpacks : 8
> >         pid : -1,-1,-1,-1,-1,-1,-1,-1
> >         vid : -1,-1,-1,-1,-1,-1,-1,-1
> > > 
> > > If yes, I could exclude that default setting from the list of possible
> > > working setups and additionally -- may be -- I get a hint, what to
> > > twiddle first....
> > 
> > Ideally, you should not need to tweak anything to be honest.  This
> > mechanism is to tune some modules in case there are conflicts between
> > devices, or you want to switch on a hardware functionality which may be
> > switched off by default (e.g. QoS, debugging, etc).
> 
> Hi Mick,
> 
> thank you very much for your explanations! I have learned many things I
> didn't know before ... :)
> 
> Hopefully I will get back audio on my cam soon.
> 
> Have a nice week!

You're welcome.  Sorry we couldn't get you going.  I suggest to get in touch 
with the alsa devs who will be able to hopefully fix what's not working with 
the driver or the configuration.

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2011-06-05 18:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2011-06-04 23:29       ` Paul Hartman
     [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

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=201106051841.30532.michaelkintzios@gmail.com \
    --to=michaelkintzios@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