[linux-audio-user] Tweaking alsamixer for the Echo Indigo IO - Linux-audio-user

wes schreiner

14 Feb 14 Feb

8:06 p.m.

Jon B wrote:

I just got an Echo Indigo IO card. It works (and I like it a lot so far), but alsamixer's sliders are all mixed up. Left channel over here, corresponding right channel way over there on the other page, etc. After I figure out what each one does, can I submit a bug report somewhere and have them rearranged and labeled better?

That's not a bug, that's a feature! :-) Alsamixer lays out the controls just as the driver numbers them, and the driver in turn numbers the controls the way that they are found in the sound hardware itself. So pry open your new Echo Indigo, see who made the chip inside, and file a bug report with them to revise their silicon :-) What you are asking for isn't wrong, but it isn't a bug, it's a new feature request. Some other mixers might support control renaming and reordering, but alsamixer is too simple for that. Some of us think that's a good thing. Alsamixer shows everything that the driver reports, in control number order. That might not be the best user interface, but it is good for seeing exactly what possibilities exist. wes

Reply

Andres Cabrera

10:54 p.m.

I think you need a recent alsa and hotplug, not sure which though... Can you try as root: tail -f /var/log/messages then connecting the Indigo? It might thell you where the problem lies. Andrés On Mon, 2005-03-14 at 21:44, Janina Sajka wrote:

...

Jon B writes:

I just got an Echo Indigo IO card. It works (and I like it a lot

I can't seem to get mine to load its firmware. Is there some magic to loading it? What actually does the loading? Just modprobe for snd-indigo loads the driver, but aplay -l doesn't list the Indigo, and lspci shows it as an "unknown device." I must be missing something fundamental here. Thanks for any help. Janina

Reply

Janina Sajka

11:07 a.m.

ix(a)replic.net writes:

...

On Mon, Mar 14, 2005 at 09:54:33PM -0500, Andres Cabrera wrote: > I think you need a recent alsa and hotplug, not sure which though... > Can you try as root: > tail -f /var/log/messages > then connecting the Indigo? It might thell you where the problem lies.

It can't find the firmware. Here's the output: kernel: PCI: Enabling device 0000:03:00.0 (0000 -> 0002) kernel: ACPI: PCI interrupt 0000:03:00.0[A] -> GSI 11 (level, low) -> IRQ 11 kernel: ALSA /usr/local/src/alsa/alsa-driver-1.0.9rc1/pci/echoaudio/echoaudio.c:41: get_firmware(): Firmware not available (-2) kernel: Echoaudio Indigo: probe of 0000:03:00.0 failed with error -2

...

make sure youre using alsa-driver + alsa-firmware 1.0.8 or newer, as echo support is built in. also make sure youve enabled hotplug and firmware loading in kernel config (one is near the top, another is in generic device driver options), and installed hotplug and fxload packages in your OS.

This is Fedora Core 3, and I update via yum nightly. I will chase these down to double-check, but it seems they're all there. I know my ipw2100 wifi ethernet mini-pci nic firmware loads, and I see /sbin/fxload. On the other hand, I see hotplug is from March of last year. Is that possibly too ancient?

...

finally, make a symlink /lib/firmware -> /usr/lib/hotplug/firmware since alsa installs the firmware stuff where the old hotplug code doesnt know to look.

I've made these both directly in /lib/firmware and /lib/firmware/ea, just in case. Still get the same error. Is there a way to get more verbose debugging data?

...

this isnt windows, so theres way too many steps just to get sound working.. also, why are you using gnome-alsamixer? theres a great app "Emixer" made especially for the echo cards. its in alsa-utilities or maybe alsa-tools...

I'm using the console because it's accessible to me via my "eyes-free" interface. Regretably for me, echomixer is written for Gnome 1.2 which isn't ever going to be accessible. Would it were written with stock gtk+ (Gnome 2) widgets! Thanks.

...

c > Andr??s > > On Mon, 2005-03-14 at 21:44, Janina Sajka wrote: > > Jon B writes: > > > I just got an Echo Indigo IO card. It works (and I like it a lot > > > > > > I can't seem to get mine to load its firmware. Is there some magic to > > loading it? What actually does the loading? Just modprobe for snd-indigo > > loads the driver, but aplay -l doesn't list the Indigo, and lspci shows > > it as an "unknown device." > > > > I must be missing something fundamental here. > > > > Thanks for any help. > > > > Janina > > > > > > >

-- Janina Sajka Phone: +1.202.494.7040 Partner, Capital Accessibility LLC http://www.CapitalAccessibility.Com Chair, Accessibility Workgroup Free Standards Group (FSG) janina(a)freestandards.org http://a11y.org If Linux can't solve your computing problem, you need a different problem.

Reply

Janina Sajka

24 Mar 24 Mar

12:05 p.m.

Just a note of follow up on this ... The latest CCRMA rpms have fixed me right up. All's well that ends well, and I can now also say the Indigo sounds marvelous. Very nice addition to the traveling rig. Janina Sajka writes: