Altec Lansing FX5051 USB Speakers Lock on Maximum Volume

[Jeremy Nickurak]

Altec Lansing FX5051 USB speakers are locked at 100% volume as soon as they're plugged in, and no tweaking from alsamixer or the gnome mixer apps seems to be able to undo this.

I filed the issue upstream ( https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3841 ), and there's more information about the issue there.

I'm a bit concerned about allowing these speakers to be connected to my ubuntu machines, as playing as loud as they do would seem to present some risk of damage to the speakers and/or my ears.

In summary:

The mixer doesn't work at all with alsa, everything is locked at 100% volume, which is pretty unhelpful, as it's the only way to adjust the volume. (no analog controls, the only other control is a digital wheel, which exhibits the same behavior as alsamixer).

Also, the digital control panel locks up when the speakers power up, further preventing any access to the volume controls.

[Gavin Silver (gavin++)]

is this bug fix still in progress?

i would happily play guinea pig if someone would mentor me through fixing this and/or i could test things etc..

the fx5051 is my only speaker system right now so i have nop sound with ubuntu at all :(

[Jeremy Nickurak (nickurak)]

Likewise. The weird this is that this device works fully out-of-the-box in windows without installing any altec-lansing software. I'd assume it's gotta be following some kind of standard that's just not implemented in alsa...

[Daniel T Chen (crimsun)]

Using pavucontrol in 8.10 allows you to control per-stream volumes.

[Jeremy Nickurak (nickurak)]

That's still only controlling it in software, and the volume in general will still be at a eardrum-blasting, speaker-destroying super-high volume that's at best useless, at worst dangerous.

[Jeremy Nickurak (nickurak)]

Confirmed still present in intrepid with 2.6.27-7

[Jeremy Nickurak (nickurak)]

This isn't really a wishlist bug... it's a "my device doesn't work" situation

[RedVivi (redvivi)]

This is a bug to me, not a wishlist.

[Jeremy Nickurak (nickurak)]

Still present in Maverick.

[Gavin Silver (gavin++)]

I wouldn't be surprised. Although my set has officially kicked the bucket at a hardware level. Sounds comes in and out as the wires are moved / jostled etc.

It's a lost cause.

I will be looking to get a new set of 7.1 for the holiday.

Sent from my iPhone

On Nov 3, 2010, at 9:23 PM, Jeremy Nickurak <email address hidden> wrote:

> Still present in Maverick.
>
> --
> Altec Lansing FX5051 USB Speakers Lock on Maximum Volume
> https://bugs.launchpad.net/bugs/219990
> You received this bug notification because you are a direct subscriber
> of the bug.

[dave jackson (davjacks)]

I'm having a similar problem with 11.04. I have altc lansing ADA70 power cube with usb, sounds great for awhile, then it'll blast your brains with static , no drivers needed , but manual says it works through windows 98. so I installed wine and clicked win98 box but no help... anybody?

[penalvch (penalvch)]

Jeremy Nickurak, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested and remove the tag:
needs-upstream-testing

This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the text:
needs-upstream-testing

If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested.

Please let us know your results. Thank you for your understanding.

Helpful Bug Reporting Tips:
https://help.ubuntu.com/community/ReportingBugs

[Raymond (superquad-vortex2)]

post the output of alsa-info.sh

seem only support 5.1

http://mailman.alsa-project.org/pipermail/alsa-devel/2007-December/004743.html