Ubuntu

cannot get any sound from my sound blaster extigy

Bug #122942 reported by bradleesargent on 2007-06-29

Affects		Status	Importance	Assigned to	Milestone
	Ubuntu	Invalid	Low	Ubuntu Audio Team

Bug Description

Binary package hint: gnome-media

I tried connecting my sound blaster extigy usb sound card and no sound is coming out.
I had originally an internal on the motherboard via sound and that apparently stopped working.
so I tried the extigy and that does not work either.

ProblemType: Bug
Architecture: i386
Date: Thu Jun 28 21:05:55 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/gnome-sound-recorder
Package: gnome-media 2.18.0-0ubuntu1
PackageArchitecture: i386
ProcCmdline: gnome-sound-recorder
ProcCwd: /home/bradlee
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:.:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-media
Uname: Linux bradlee-desktop 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux

Revision history for this message

bradleesargent (bradlee-sargent) wrote on 2007-06-29:

Dependencies.txt Edit (4.8 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (25.4 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (674 bytes, text/plain; charset="utf-8")

Revision history for this message

bradleesargent (bradlee-sargent) wrote on 2007-06-29:

I got my motherboard sound to work again.
I was playing with the volume control and I am not sure how it started working again but it did.
But the extigy I still don't know if it can work at all...

Revision history for this message

Daniel T Chen (crimsun) wrote on 2007-06-29:

Please execute the following command in a Terminal:

asoundconf list

If your Audigy is listed, please pass that string as follows:

asoundconf set-default-card Audigy

(The above command presumes that the `asoundconf list` command returned "Audigy" as one of the cards.) Afterward, please log out and back into GNOME/KDE.

Changed in alsa-lib:
assignee:	nobody → ubuntu-audio
importance:	Undecided → Low
status:	New → Incomplete

Revision history for this message

bradleesargent (bradlee-sargent) wrote on 2007-06-30: Re: [Bug 122942] Re: cannot get any sound from my sound blaster extigy

I did that, but still no sound from the extigy.
What's next?

On 6/29/07, Daniel T Chen <email address hidden> wrote:
>
> Please execute the following command in a Terminal:
>
> asoundconf list
>
> If your Audigy is listed, please pass that string as follows:
>
> asoundconf set-default-card Audigy
>
> (The above command presumes that the `asoundconf list` command returned
> "Audigy" as one of the cards.) Afterward, please log out and back into
> GNOME/KDE.
>
> ** Changed in: alsa-utils (Ubuntu)
> Sourcepackagename: alsa-lib => alsa-utils
> Importance: Undecided => Low
> Assignee: (unassigned) => Ubuntu Audio Team
> Status: New => Incomplete
>
> --
> cannot get any sound from my sound blaster extigy
> https://bugs.launchpad.net/bugs/122942
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message

StrayTheNomad (chrismenning) wrote on 2007-09-10:

Bradlee
I think what Daniel meant was to enter the command
asoundconf set-default-card Extigy
Now restart <Cntrl>+<Alt>+<Backspace>
You should hear the Ubuntu Login sound after entering your password
My Extigy wouldn't work at first either, but this worked for me.

Revision history for this message

bradleesargent (bradlee-sargent) wrote on 2007-09-10:

I believe this issue can be closed because I have my extigy working.
When will gutsy gibbon be coming out?
Thanks

On 9/10/07, StrayTheNomad <email address hidden> wrote:
> Bradlee
> I think what Daniel meant was to enter the command
> asoundconf set-default-card Extigy
> Now restart <Cntrl>+<Alt>+<Backspace>
> You should hear the Ubuntu Login sound after entering your password
> My Extigy wouldn't work at first either, but this worked for me.
>
> --
> cannot get any sound from my sound blaster extigy
> https://bugs.launchpad.net/bugs/122942
> You received this bug notification because you are a direct subscriber
> of the bug.
>