public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: walt shekrota <penguinacity@yahoo.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Ubuntu 7.04 / plugz need success info
Date: Wed, 4 Jul 2007 07:23:07 -0700 (PDT)	[thread overview]
Message-ID: <14304.83655.qm@web62306.mail.re1.yahoo.com> (raw)
In-Reply-To: <874594.50250.qm@web62305.mail.re1.yahoo.com>


[-- Attachment #1.1: Type: text/plain, Size: 2092 bytes --]

I'm starting to think this is in alsa?
 It may be that this plugin only works with some chipsets (or drivers).
 The system here is a compaq S5000V with integrated dual channel intel sound.
 Yes alsa configured working sound but when headset specified it acts like the soundcard is in use or not there.
 I tried and ensonic soundcard this morning, it configed properly in alsa and sound worked yet producing the same results with headsetd.

 Can I get information from people who have gotten plugz working?
 what sound chipset or driver
 what linux version
 
 Does Fabien read this list perhaps he has some thoughts? Either something is being overlooked in the install or we have some hardware sets that just don't work properly.
 Good isolation tactic would be steps to prove certain phases of the installation work?
 If someone could post sequential steps to check the validity of this installation it would be helpful.
 Like I have said in past normal sound works then when 'headset' string inserted in xmms options, total blockage like having no soundcard.
 
 Thanks for any info.
 -Walt
 
walt shekrota <penguinacity@yahoo.com> wrote: Anybody using this combination?
 success / problems
 any feedback appreciated.
 
 I get the alsa device headset permission denied. (on headsetd log) Or in some cases a timeout.
 .asoundrc is cloned from the cvs directory as in the doc.
 
 Thanks.
 -Walt
         

---------------------------------
Got a little couch potato? 
 Check out fun summer activities for kids.-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users


 
---------------------------------
Never miss an email again!
Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out.

[-- Attachment #1.2: Type: text/html, Size: 2666 bytes --]

[-- Attachment #2: Type: text/plain, Size: 286 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2007-07-04 14:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-03 14:42 [Bluez-users] Ubuntu 7.04 / plugz walt shekrota
2007-07-04 14:23 ` walt shekrota [this message]

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=14304.83655.qm@web62306.mail.re1.yahoo.com \
    --to=penguinacity@yahoo.com \
    --cc=bluez-users@lists.sourceforge.net \
    /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