From: Jeremy Nickurak <alsa-devel@atrus.rifetech.com>
To: alsa-devel@alsa-project.org
Subject: Non-functional Altec Lansing FX5051 USB-soundcard + speakers
Date: Sun, 9 Nov 2008 21:09:34 -0700 [thread overview]
Message-ID: <20081110040933.GA29870@katran.rifetech.com> (raw)
About 14 months ago I purchased a nice new ~$300 set of altec lansing
5.1 speakers, which include a USB-sound card. Since that time they've
largely gone unused, or at least not properly used. I brought this up on
the mailing list at the time, but didn't get much response, so I thought
I'd poke my head up again and see if anybody has any insight.
First off, the set works correctly, out-of-the-box under windows,
without having to install any special drivers or software at all.
Under linux, plugging them in instantly freezes the usb sound card up,
and locks it at 100% volume, in such a way that there's absolutely no
way to turn the volume down: not from alsamixer, and not from the
speaker's hardware control dial. Sound does play, but again, it's
unbearably loud, to the point where I don't do it for risk of damaging
my speakers and/or ears.
I filed the bug away on the bug-tracker, but haven't heard much out of
it since. The bug contains my lsusb -v information, the "contents"
output from amixer for this card, and some preliminary results showing
some ability to tweak the volume with amixer, but not reliably.
Any suggestions are welcome. I'm happy to experiment with this set more
if it can help, run experimental code, etc. Heck, I'd go at the thing
with a screwdriver for chipset information if I know what I was looking
for or thought it could help.
next reply other threads:[~2008-11-10 4:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 4:09 Jeremy Nickurak [this message]
2008-11-10 10:45 ` Non-functional Altec Lansing FX5051 USB-soundcard + speakers Jelle de Jong
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=20081110040933.GA29870@katran.rifetech.com \
--to=alsa-devel@atrus.rifetech.com \
--cc=alsa-devel@alsa-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.