Skip to contentSkip to conversation

ice1712 driver broken in 2.6.1-mm kernels

DISCUSSION Torrey Hoffman 7 participants 19 messages Jan 20, 2004 – Jan 25, 2004

lore
Share & tools
lore
#0 lore raw

You may already know this, but the ice1712 driver doesn't work in Andrew Morton's 2.6.1-mm? kernels which include the latest ALSA updates.

Tested with an M-Audio Audiophile 24/96.

2.6.1-vanilla works, so does the 2.4 Fedora Core 1 kernel with ALSA drivers from FreshRPMs.

Thanks!

Signature · 9 lines
Torrey Hoffman <[email protected]>



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
#1 lore raw
Quoted 5 lines · Torrey Hoffman

You may already know this, but the ice1712 driver doesn't work in Andrew Morton's 2.6.1-mm? kernels which include the latest ALSA updates.

Tested with an M-Audio Audiophile 24/96.

What exactly does not work? I tested EWX 24/96 with mm3 and it works pretty well.

Jaroslav

-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs

-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

#2 lore raw
Quoted 10 lines · Jaroslav Kysela
Quoted 5 lines · Torrey Hoffman

You may already know this, but the ice1712 driver doesn't work in Andrew Morton's 2.6.1-mm? kernels which include the latest ALSA updates.

Tested with an M-Audio Audiophile 24/96.

What exactly does not work? I tested EWX 24/96 with mm3 and it works pretty well.

In 2.6.1-mm5, which I'm running at the moment, I just get no sound output. No error messages. The envy24control level meters don't show any sound output.

2.6.1 vanilla works fine. So does the 2.4 kernel that comes with Fedora Core 1, using the latest ALSA driver sets from FreshRPMs.

I'm not the only one having problems with this driver in the latest ALSA versions... on the ALSA development mailing list, Klaus-Peter Schrage <[email protected]> told me today that he and others on the alsa-user list have reported problems as well.

I'm very motivated to get this working, and am happy to apply patches, recompile my kernel, or do anything else that would help debug the problem.

Signature · 9 lines
Torrey Hoffman <[email protected]>



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
#3 lore raw
Quoted 5 lines · Torrey Hoffman

In 2.6.1-mm5, which I'm running at the moment, I just get no sound output. No error messages. The envy24control level meters don't show any sound output.

I have the same problem with my Terratec DMX6fire, running gentoo / 2.6.1 with the alsa-kernel directory from alsa-driver-1.0.1 merged into the kernel sources as described in the wiki. Sometimes I hear some kind of looped noise instead of silence which stays the same no matter what I try to play.

I found out that unloading all alsa modules, recompiling alsa-lib and restarting alsa seemes to make it work again until the next reboot.

Quoted 6 lines

I'm very motivated to get this working, and am happy to apply patches, recompile my kernel, or do anything else that would help debug the problem.

Same here, I could try out some stuff or send you more information, but I don't know where to start.

gruss,
Steffen

-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

#4 lore raw
Quoted 9 lines · Steffen Sauder
Quoted 5 lines · Torrey Hoffman

In 2.6.1-mm5, which I'm running at the moment, I just get no sound output. No error messages. The envy24control level meters don't show any sound output.

I have the same problem with my Terratec DMX6fire, running gentoo / 2.6.1 with the alsa-kernel directory from alsa-driver-1.0.1 merged into the kernel sources as described in the wiki. Sometimes I hear some kind of looped noise instead of silence which stays the same no matter what I try to play.

I'm getting this nasty looped noise as well using a M-Audio Delta 1010lt with alsa 1.0.1 merged into kernel 2.6.1

This also occured using Alsa 1.0.0rc2.

This is definetely an annoying bug.

-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

#5 lore raw
In reply to Torrey Hoffman
Quoted 12 lines · Torrey Hoffman
Quoted 10 lines · Jaroslav Kysela
Quoted 5 lines · Torrey Hoffman

You may already know this, but the ice1712 driver doesn't work in Andrew Morton's 2.6.1-mm? kernels which include the latest ALSA updates.

Tested with an M-Audio Audiophile 24/96.

What exactly does not work? I tested EWX 24/96 with mm3 and it works pretty well.

Quoted 6 lines

In 2.6.1-mm5, which I'm running at the moment, I just get no sound output. No error messages. The envy24control level meters don't show any sound output.

2.6.1 vanilla works fine. So does the 2.4 kernel that comes with Fedora Core 1, using the latest ALSA driver sets from FreshRPMs.

Can you try 2.6.1-rc1 with alsa-bk-2004-01-20.patch.gz available at our ftp site (/pub/kernel-patches)? It should fix your problem.

Jaroslav

-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs

-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

#6 lore raw
Quoted 4 lines · Jaroslav Kysela

Can you try 2.6.1-rc1 with alsa-bk-2004-01-20.patch.gz available at our ftp site (/pub/kernel-patches)? It should fix your problem.

Thanks a lot Jaroslav! That fixed the problem for me. One small hint for everyone else trying this: Don't forget to readjust your mixer settings, the previously saved settings seem to get lost with the new driver!

Is there any reason why the patch is against 2.6.1-rc1? I was quite satisfied with 2.6.1 and don't really want to go back to its first rc. Should I just try to apply the patch to 2.6.1 or 2.6.1-mmX? Will it work for sure, probably or definetly not?

Or could you perhaps post your changes as a patch against alsa-driver 1.0.1, so that I can merge alsa into the kernel-sources by myself?

gruss,
Steffen

-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

#7 lore raw

At Wed, 21 Jan 2004 16:08:51 +0100,

Quoted 8 lines · Steffen Sauder
Quoted 5 lines · Jaroslav Kysela

Can you try 2.6.1-rc1 with alsa-bk-2004-01-20.patch.gz available at our ftp site (/pub/kernel-patches)? It should fix your problem.

Quoted 8 lines

Thanks a lot Jaroslav! That fixed the problem for me. One small hint for everyone else trying this: Don't forget to readjust your mixer settings, the previously saved settings seem to get lost with the new driver!

Is there any reason why the patch is against 2.6.1-rc1? I was quite satisfied with 2.6.1 and don't really want to go back to its first rc. Should I just try to apply the patch to 2.6.1 or 2.6.1-mmX? Will it work for sure, probably or definetly not?

i guess it's a typo of 2.6.2-rc1?

Quoted 2 lines

Or could you perhaps post your changes as a patch against alsa-driver 1.0.1, so that I can merge alsa into the kernel-sources by myself?

you can try alsa-driver cvs version.

Takashi

-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

#8 lore raw
Quoted 4 lines · Takashi Iwai

At Wed, 21 Jan 2004 16:08:51 +0100,
Steffen Sauder wrote:

Quoted 9 lines
Quoted 3 lines

Is there any reason why the patch is against 2.6.1-rc1? I was quite satisfied with 2.6.1 and don't really want to go back to its first rc. Should I just try to apply the patch to 2.6.1 or 2.6.1-mmX? Will it work for sure, probably or definetly not?

i guess it's a typo of 2.6.2-rc1?

oh, silly me thought that pros never do typos :o)

works fine with 2.6.2-rc1 as well, I'm so glad...

Steffen

-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

#9 lore raw
In reply to Takashi Iwai
Quoted 1 line · Takashi Iwai

i guess it's a typo of 2.6.2-rc1?

Yes, it was. I prepare these patches against the actual Linus's BK tree.

Jaroslav

-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs

-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

#10 lore raw
In reply to Jaroslav Kysela
Quoted 2 lines · Jaroslav Kysela

Can you try 2.6.1-rc1 with alsa-bk-2004-01-20.patch.gz available at our ftp site (/pub/kernel-patches)? It should fix your problem.

Jaroslav

The patch worked flawlessly against a plain 2.6.1 kernel.
My distortion troubles with my Terratec DMX6fire 24/16, which date back to the 2.6.0rcX days, seem to be over. I think you made all of us 'iceies' very happy! Klaus

-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

#11 lore raw
In reply to Jaroslav Kysela

OK, 2.6.2-rc1 with the alsa-bk-2004-01-20.patch.gz gets my sound working again, thanks!

Just one problem remains to be solved for this card: The Audiophile 24/96 is a 4-in, 4-out card (stereo analog input and output, plus independent SPDIF input and output). But only one set of inputs and outputs is showing up for use:

[thoffman@moria thoffman]$ cat /proc/asound/cards
0 [ICH5 ]: ICH - Intel ICH5

                     Intel ICH5 at 0xfc102000, irq 17
1 [M2496          ]: ICE1712 - M Audio Audiophile 24/96
                     M Audio Audiophile 24/96 at 0x6000, irq 20

[thoffman@moria thoffman]$ cat /proc/asound/devices
0: [0- 0]: ctl
20: [0- 4]: digital audio playback
27: [0- 3]: digital audio capture
26: [0- 2]: digital audio capture
25: [0- 1]: digital audio capture
16: [0- 0]: digital audio playback
24: [0- 0]: digital audio capture
33: : timer
32: [1- 0]: ctl
40: [1- 0]: raw midi
48: [1- 0]: digital audio playback
56: [1- 0]: digital audio capture

[thoffman@moria thoffman]$ cat /proc/asound/pcm 00-00: Intel ICH : Intel ICH5 : playback 1 : capture 1 00-01: Intel ICH - MIC ADC : Intel ICH5 - MIC ADC : capture 1 00-02: Intel ICH - MIC2 ADC : Intel ICH5 - MIC2 ADC : capture 1 00-03: Intel ICH - ADC2 : Intel ICH5 - ADC2 : capture 1 00-04: Intel ICH - IEC958 : Intel ICH5 - IEC958 : playback 1 01-00: ICE1712 multi : ICE1712 multi : playback 1 : capture 1

Shouldn't there be separate devices for the analog & SPDIF inputs and outputs? If not, how do I send different signals to the analog & digital outputs?

Thanks,

Torrey Hoffman

Quoted 30 lines · Jaroslav Kysela
Quoted 12 lines · Torrey Hoffman
Quoted 10 lines · Jaroslav Kysela
Quoted 5 lines · Torrey Hoffman

You may already know this, but the ice1712 driver doesn't work in Andrew Morton's 2.6.1-mm? kernels which include the latest ALSA updates.

Tested with an M-Audio Audiophile 24/96.

What exactly does not work? I tested EWX 24/96 with mm3 and it works pretty well.

Quoted 6 lines

In 2.6.1-mm5, which I'm running at the moment, I just get no sound output. No error messages. The envy24control level meters don't show any sound output.

2.6.1 vanilla works fine. So does the 2.4 kernel that comes with Fedora Core 1, using the latest ALSA driver sets from FreshRPMs.

Can you try 2.6.1-rc1 with alsa-bk-2004-01-20.patch.gz available at our ftp site (/pub/kernel-patches)? It should fix your problem.

Jaroslav

-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs

Signature · 9 lines
Torrey Hoffman <[email protected]>



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
#12 lore raw
Quoted 11 lines

Just one problem remains to be solved for this card: The Audiophile 24/96 is a 4-in, 4-out card (stereo analog input and output, plus independent SPDIF input and output). But only one set of inputs and outputs is showing up for use:

[thoffman@moria thoffman]$ cat /proc/asound/pcm 01-00: ICE1712 multi : ICE1712 multi : playback 1 : capture 1

Shouldn't there be separate devices for the analog & SPDIF inputs and outputs? If not, how do I send different signals to the analog & digital outputs?

You have to create .asoundrc to your home directory.

for spdif, put:

pcm.2496_spdif

{
        type plug
        ttable.0.8 1
        ttable.1.9 1
        slave.pcm {
                type hw
                card 1
                device 0
        }
}

(If I remember correctly, your card was no. 1, if not, change 'card 1')

This device can be used like this:

aplay -D 2496_spdif foo.wav
arecord -D 2496_spdif -f dat bar.wav

For combined analog & digital performance (4 channels):

pcm.2496_4ch

{
        type plug
        ttable.0.0 1
        ttable.1.1 1
        ttable.2.8 1
        ttable.3.9 1
        slave.pcm {
        type hw
        card 1
        device 0
        }
}

then record 4 channels:

arecord -D 2496_4ch -c 4 -f cd foobar.wav

I'm not sure how you can easily send different signals to analog & digital outputs. I guess if you have 4 channel wav, the first two channels will be played to analog and 3&4 to digital output.

Tommi Uimonen

-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

#13 lore raw

On Wed, 2004-01-21 at 12:25, Tommi Sakari Uimonen wrote:
...

Quoted 8 lines
Quoted 6 lines

[thoffman@moria thoffman]$ cat /proc/asound/pcm 01-00: ICE1712 multi : ICE1712 multi : playback 1 : capture 1

Shouldn't there be separate devices for the analog & SPDIF inputs and outputs? If not, how do I send different signals to the analog & digital outputs?

You have to create .asoundrc to your home directory.

(example as below)

Thanks for the tip. I tried your suggestion, but it doesn't work for me. My .asoundrc now has this in it:

pcm.maudio_analog {
type hw
card 1
device 0
}

pcm.maudio_spdif {
	type plug
        ttable.0.8 1
        ttable.1.9 1
        slave.pcm {
                type hw
                card 1
                device 0
        }
}

I can play sound fine through the analog channel:
[thoffman@moria thoffman]$ aplay -D plug:maudio_analog 12.wav Playing WAVE '12.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo

But when I try to use the spdif channel, I get an error:

[thoffman@moria thoffman]$ aplay -D plug:maudio_spdif 12.wav Playing WAVE '12.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
aplay: pcm_write:1083: write error: Invalid argument

So, still no success using the digital output channel...

Signature · 9 lines
Torrey Hoffman <[email protected]>



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
#14 lore raw
Quoted 25 lines

Thanks for the tip. I tried your suggestion, but it doesn't work for me. My .asoundrc now has this in it:

pcm.maudio_analog {
type hw
card 1
device 0
}

pcm.maudio_spdif {
	type plug
        ttable.0.8 1
        ttable.1.9 1
        slave.pcm {
                type hw
                card 1
                device 0
        }
}

I can play sound fine through the analog channel:
[thoffman@moria thoffman]$ aplay -D plug:maudio_analog 12.wav Playing WAVE '12.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo

Quoted 6 lines

But when I try to use the spdif channel, I get an error:

[thoffman@moria thoffman]$ aplay -D plug:maudio_spdif 12.wav Playing WAVE '12.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Stereo
aplay: pcm_write:1083: write error: Invalid argument

It should be -D maudio_spdif, so lose the plug: and it will work. I think the analog should also work without plug.

Tommi

-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

#15 lore raw
Quoted 2 lines · Tommi Sakari Uimonen
Quoted 2 lines

Thanks for the tip. I tried your suggestion, but it doesn't work for me. My .asoundrc now has this in it:

(snip)

Quoted 2 lines

It should be -D maudio_spdif, so lose the plug: and it will work. I think the analog should also work without plug.

Thanks! That did it, mostly... I now can play sound through the SPDIF!

The analog doesn't work without "plug", I get an error "aplay:
set_params:827: Sample format non available". I think it's because the 2496 driver only does 24bit, so 16bit pcm requires translation.

But that's not a problem - plug works fine.

The one problem is I still can't play different wave files simultaneously through the two outputs.

If I start "aplay -D maudio_spdif 12.wav &" and then try to do "aplay -D plug:maudio_analog 11.wav" at the same time, the second one just blocks until the first one is done.

This is unfortunate, since I'd really like to be able to run two-room sound from my computer into different amplifiers and speakers. I'm sure there's a way to do it, since the hardware is capable of it...

Signature · 9 lines
Torrey Hoffman <[email protected]>



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
#16 lore raw
Quoted 8 lines
Quoted 2 lines

It should be -D maudio_spdif, so lose the plug: and it will work. I think the analog should also work without plug.

Thanks! That did it, mostly... I now can play sound through the SPDIF!

The analog doesn't work without "plug", I get an error "aplay:
set_params:827: Sample format non available". I think it's because the 2496 driver only does 24bit, so 16bit pcm requires translation.

Yes, of course.

Quoted 5 lines

But that's not a problem - plug works fine.

The one problem is I still can't play different wave files simultaneously through the two outputs.

Quoted 7 lines

If I start "aplay -D maudio_spdif 12.wav &" and then try to do "aplay -D plug:maudio_analog 11.wav" at the same time, the second one just blocks until the first one is done.

This is unfortunate, since I'd really like to be able to run two-room sound from my computer into different amplifiers and speakers. I'm sure there's a way to do it, since the hardware is capable of it...

Well, some kind of dmix approach might do it.

app1 >-- --> analog

        \    /
         dmix
        /    \

app2 >-- --> spdif

I don't know how to do it. I think this kind of plug device would be popular among 5.1 owners, where you could define what input goes to what output. Something like:

-D dmix_rear
-D dmix_front

etc..

But how to separate them from the mix? Anyway, dmix allows multiple instances to use the soundcard, so it's a start.

Maybe the plugins can be linked so that output of one goes to input of the other. I guess this can be done, but I'm not any .asoundrc magician.

Or ttable & bindings...

http://www.alsa-project.org/alsa-doc/doc-php/asoundrc.php3

Tommi

-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

#17 lore raw
Quoted 10 lines
Quoted 10 lines

The one problem is I still can't play different wave files simultaneously through the two outputs.

If I start "aplay -D maudio_spdif 12.wav &" and then try to do "aplay -D plug:maudio_analog 11.wav" at the same time, the second one just blocks until the first one is done.

This is unfortunate, since I'd really like to be able to run two-room sound from my computer into different amplifiers and speakers. I'm sure there's a way to do it, since the hardware is capable of it...

Now after thinking this, I think ecasound is the right tool for this.

Create a device to .asoundrc: (with correct card number of course)

pcm.2496_4ch

{
        type plug
        ttable.0.0 1
        ttable.1.1 1
        ttable.2.8 1
        ttable.3.9 1
        slave.pcm {
        type hw
        card 0
        device 0
        }
}

Then use ecasound with this device, and take input from two sources and send them to the appropriate channels, first input to channels 1&2, second to channels 3&4.

I don't know the right way to do this, but I know that it can be done. Since ecasound can split 4 channel wav to separate channels, I don't see why it wouldn't join two stereo samples to one 4 channel sample.

Maybe you'll have to ask this from ecasound-list

http://www.eca.cx/mlists.html

Tommi

-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

#18 lore raw
In reply to Jaroslav Kysela
Quoted 2 lines · Jaroslav Kysela

Can you try 2.6.1-rc1 with alsa-bk-2004-01-20.patch.gz available at our ftp site (/pub/kernel-patches)? It should fix your problem.

Jaroslav

The patch worked flawlessly against a plain 2.6.1 kernel.
My distortion troubles with my Terratec DMX6fire 24/16, which date back to the 2.6.0rcX days, seem to be over. I think you made all of us 'iceies' very happy!
Klaus

-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn