Maestro 2E (rev 10) not found or device busy w/ 0.9.2

Maestro 2E (rev 10) not found or device busy w/ 0.9.2

[alsa]

The 'maestro' driver included with Linux 2.4.x loads, and for the most
part works okay.  However trying to use the latest ALSA results in:

kernel: es1968: not attempting power management.
kernel: ALSA ../../alsa-kernel/pci/ac97/ac97_codec.c:1960: AC'97 0:0 does not respond - RESET
kernel: ESS Maestro soundcard not found or device busy

Anyone have any suggestions on how to fix this?

If you need more info please let me know.  Thanks!

 - Ted


-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en

Re: Maestro 2E (rev 10) not found or device busy w/ 0.9.2

[Takashi Iwai]

At Wed, 26 Mar 2003 17:12:55 -0700 (MST),
alsa@0x00.my-ho.st wrote:
> 
> The 'maestro' driver included with Linux 2.4.x loads, and for the most
> part works okay.  However trying to use the latest ALSA results in:
> 
> kernel: es1968: not attempting power management.
> kernel: ALSA ../../alsa-kernel/pci/ac97/ac97_codec.c:1960: AC'97 0:0 does not respond - RESET
> kernel: ESS Maestro soundcard not found or device busy
> 
> Anyone have any suggestions on how to fix this?

which version of alsa did you test exactly?
i thought this was fixed in the recent version.  please try the cvs
version if not tried yet.


Takashi


-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en

Re: Maestro 2E (rev 10) not found or device busy w/ 0.9.2

[alsa]

On Thu, 27 Mar 2003, Takashi Iwai wrote:

> At Wed, 26 Mar 2003 17:12:55 -0700 (MST),
> alsa@0x00.my-ho.st wrote:
> >
> > The 'maestro' driver included with Linux 2.4.x loads, and for the most
> > part works okay.  However trying to use the latest ALSA results in:
> >
> > kernel: es1968: not attempting power management.
> > kernel: ALSA ../../alsa-kernel/pci/ac97/ac97_codec.c:1960: AC'97 0:0 does not respond - RESET
> > kernel: ESS Maestro soundcard not found or device busy
> >
> > Anyone have any suggestions on how to fix this?
>
> which version of alsa did you test exactly?
> i thought this was fixed in the recent version.  please try the cvs
> version if not tried yet.

Thanks for the quick response.  I have tried 0.9.2 and the latest cvs;
both give the same errors.  :(

Any suggestions?

 - Ted


-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en

Re: Maestro 2E (rev 10) not found or device busy w/ 0.9.2

[alsa]

On Thu, 27 Mar 2003 alsa@0x00.my-ho.st wrote:

> On Thu, 27 Mar 2003, Takashi Iwai wrote:
>
> > At Wed, 26 Mar 2003 17:12:55 -0700 (MST),
> > alsa@0x00.my-ho.st wrote:
> > >
> > > The 'maestro' driver included with Linux 2.4.x loads, and for the most
> > > part works okay.  However trying to use the latest ALSA results in:
> > >
> > > kernel: es1968: not attempting power management.
> > > kernel: ALSA ../../alsa-kernel/pci/ac97/ac97_codec.c:1960: AC'97 0:0 does not respond - RESET
> > > kernel: ESS Maestro soundcard not found or device busy
> > >
> > > Anyone have any suggestions on how to fix this?
> >
> > which version of alsa did you test exactly?
> > i thought this was fixed in the recent version.  please try the cvs
> > version if not tried yet.
>
> Thanks for the quick response.  I have tried 0.9.2 and the latest cvs;
> both give the same errors.  :(
>
> Any suggestions?

Since I didn't get any response yet I decided to look into this more
closely myself.

The problem appears to be that although 0x8a05 is written to the
AC97_REC_GAIN register, a subsequent read returns 0xa05.  Anyone know why
this might occur?  Could someone more familiar with the ALSA code give me
some pointers on where to go from here?

Thanks.

 - Ted


-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: 
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/

Re: Maestro 2E (rev 10) not found or device busy w/ 0.9.2

[Takashi Iwai]

At Sun, 6 Apr 2003 12:55:56 -0600 (MDT),
alsa@0x00.my-ho.st wrote:
> 
> On Thu, 27 Mar 2003 alsa@0x00.my-ho.st wrote:
> 
> > On Thu, 27 Mar 2003, Takashi Iwai wrote:
> >
> > > At Wed, 26 Mar 2003 17:12:55 -0700 (MST),
> > > alsa@0x00.my-ho.st wrote:
> > > >
> > > > The 'maestro' driver included with Linux 2.4.x loads, and for the most
> > > > part works okay.  However trying to use the latest ALSA results in:
> > > >
> > > > kernel: es1968: not attempting power management.
> > > > kernel: ALSA ../../alsa-kernel/pci/ac97/ac97_codec.c:1960: AC'97 0:0 does not respond - RESET
> > > > kernel: ESS Maestro soundcard not found or device busy
> > > >
> > > > Anyone have any suggestions on how to fix this?
> > >
> > > which version of alsa did you test exactly?
> > > i thought this was fixed in the recent version.  please try the cvs
> > > version if not tried yet.
> >
> > Thanks for the quick response.  I have tried 0.9.2 and the latest cvs;
> > both give the same errors.  :(
> >
> > Any suggestions?
> 
> Since I didn't get any response yet I decided to look into this more
> closely myself.
> 
> The problem appears to be that although 0x8a05 is written to the
> AC97_REC_GAIN register, a subsequent read returns 0xa05.  Anyone know why
> this might occur?  Could someone more familiar with the ALSA code give me
> some pointers on where to go from here?

it seems that the codec is not 100% compliant to the ac97 spec.
which ac97 codec is on yours?  (you can proceed the process there by
replacing 0x8a05 to 0x0a05...)

also, please give the detail of your hardware (the product name and
the output of lspci -nv).


thanks,

Takashi


-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: 
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/

Re: Maestro 2E (rev 10) not found or device busy w/ 0.9.2

[alsa]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 2060 bytes --]

On Tue, 8 Apr 2003, Takashi Iwai wrote:

> At Sun, 6 Apr 2003 12:55:56 -0600 (MDT),
> alsa@0x00.my-ho.st wrote:
> >
> > On Thu, 27 Mar 2003 alsa@0x00.my-ho.st wrote:
> >
> > > On Thu, 27 Mar 2003, Takashi Iwai wrote:
> > >
> > > > At Wed, 26 Mar 2003 17:12:55 -0700 (MST),
> > > > alsa@0x00.my-ho.st wrote:
> > > > >
> > > > > The 'maestro' driver included with Linux 2.4.x loads, and for the most
> > > > > part works okay.  However trying to use the latest ALSA results in:
> > > > >
> > > > > kernel: es1968: not attempting power management.
> > > > > kernel: ALSA ../../alsa-kernel/pci/ac97/ac97_codec.c:1960: AC'97 0:0 does not respond - RESET
> > > > > kernel: ESS Maestro soundcard not found or device busy
> > > > >
> > > > > Anyone have any suggestions on how to fix this?
> > > >
> > > > which version of alsa did you test exactly?
> > > > i thought this was fixed in the recent version.  please try the cvs
> > > > version if not tried yet.
> > >
> > > Thanks for the quick response.  I have tried 0.9.2 and the latest cvs;
> > > both give the same errors.  :(
> > >
> > > Any suggestions?
> >
> > Since I didn't get any response yet I decided to look into this more
> > closely myself.
> >
> > The problem appears to be that although 0x8a05 is written to the
> > AC97_REC_GAIN register, a subsequent read returns 0xa05.  Anyone know why
> > this might occur?  Could someone more familiar with the ALSA code give me
> > some pointers on where to go from here?
>
> it seems that the codec is not 100% compliant to the ac97 spec.
> which ac97 codec is on yours?

$ cat /proc/asound/card0/ac97\#0
0-0/0: SigmaTel STAC9721/23

>  (you can proceed the process there by
> replacing 0x8a05 to 0x0a05...)

This change allows the driver to load, but:

$ aumix
aumix:  no device found

$ alsamixer
No mixer elems found

> also, please give the detail of your hardware (the product name and
> the output of lspci -nv).

It's a Compaq Armada E500 laptop.  Output from 'lspci -nv' attached.

Thanks for the reply!  Any suggestions where to go from here?

  - Ted

[-- Attachment #2: Type: TEXT/PLAIN, Size: 2938 bytes --]

00:00.0 Class 0600: 8086:7190 (rev 03)
	Subsystem: 0e11:b110
	Flags: bus master, medium devsel, latency 64
	Memory at 50000000 (32-bit, prefetchable) [size=64M]
	Capabilities: [a0] AGP version 1.0

00:01.0 Class 0604: 8086:7191 (rev 03)
	Flags: 66Mhz, medium devsel
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 00002000-00002fff
	Memory behind bridge: 40000000-410fffff

00:04.0 Class 0607: 104c:ac1c (rev 01)
	Subsystem: 0e11:b121
	Flags: bus master, medium devsel, latency 168, IRQ 11
	Memory at 41100000 (32-bit, non-prefetchable) [size=4K]
	Bus: primary=00, secondary=02, subordinate=02, sec-latency=176
	Memory window 0: 10000000-103ff000 (prefetchable)
	Memory window 1: 10400000-107ff000
	I/O window 0: 00004400-000044ff
	I/O window 1: 00004800-000048ff
	16-bit legacy interface ports at 0001

00:04.1 Class 0607: 104c:ac1c (rev 01)
	Subsystem: 0e11:b121
	Flags: bus master, medium devsel, latency 168, IRQ 11
	Memory at 41180000 (32-bit, non-prefetchable) [size=4K]
	Bus: primary=00, secondary=03, subordinate=03, sec-latency=176
	Memory window 0: 10800000-10bff000 (prefetchable)
	Memory window 1: 10c00000-10fff000
	I/O window 0: 00004c00-00004cff
	I/O window 1: 00005400-000054ff
	16-bit legacy interface ports at 0001

00:07.0 Class 0680: 8086:7110 (rev 02)
	Flags: bus master, medium devsel, latency 0

00:07.1 Class 0101: 8086:7111 (rev 01) (prog-if 80 [Master])
	Flags: bus master, medium devsel, latency 64
	I/O ports at 3420 [size=16]

00:07.2 Class 0c03: 8086:7112 (rev 01)
	Flags: bus master, medium devsel, latency 64, IRQ 11
	I/O ports at 3400 [size=32]

00:07.3 Class 0680: 8086:7113 (rev 03)
	Flags: medium devsel, IRQ 9

00:08.0 Class 0401: 125d:1978 (rev 10)
	Subsystem: 0e11:b112
	Flags: bus master, medium devsel, latency 64, IRQ 11
	I/O ports at 3000 [size=256]
	Capabilities: [c0] Power Management version 2

00:09.0 Class 0200: 8086:1229 (rev 09)
	Subsystem: 8086:2204
	Flags: bus master, medium devsel, latency 66, IRQ 11
	Memory at 41280000 (32-bit, non-prefetchable) [size=4K]
	I/O ports at 3440 [size=64]
	Memory at 41200000 (32-bit, non-prefetchable) [size=128K]
	Expansion ROM at <unassigned> [disabled] [size=1M]
	Capabilities: [dc] Power Management version 2

00:09.1 Class 0700: 11c1:0445
	Subsystem: 8086:2204
	Flags: medium devsel, IRQ 11
	I/O ports at 3430 [size=8]
	Memory at 41300000 (32-bit, non-prefetchable) [size=4K]
	Capabilities: [dc] Power Management version 2

01:00.0 Class 0300: 1002:4c4d (rev 64)
	Subsystem: 0e11:b160
	Flags: bus master, stepping, medium devsel, latency 66, IRQ 11
	Memory at 40000000 (32-bit, non-prefetchable) [size=16M]
	I/O ports at 2000 [size=256]
	Memory at 41000000 (32-bit, non-prefetchable) [size=4K]
	Expansion ROM at <unassigned> [disabled] [size=128K]
	Capabilities: [50] AGP version 1.0
	Capabilities: [5c] Power Management version 1

Re: Maestro 2E (rev 10) not found or device busy w/ 0.9.2

[Takashi Iwai]

At Tue, 8 Apr 2003 12:15:42 -0600 (MDT),
alsa@0x00.my-ho.st wrote:
> 
> >  (you can proceed the process there by
> > replacing 0x8a05 to 0x0a05...)
> 
> This change allows the driver to load, but:

there are two places which check AC97_REC_GAIN.
line 1980 and line 2064 in the latest cvs.
you'll need to change both parts.


Takashi


-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost and 
disoriented. TotalView can help you find your way. Available on major UNIX 
and Linux platforms. Try it free. www.etnus.com

Re: Maestro 2E (rev 10) not found or device busy w/ 0.9.2

[alsa]

On Wed, 9 Apr 2003, Takashi Iwai wrote:

> At Tue, 8 Apr 2003 12:15:42 -0600 (MDT),
> alsa@0x00.my-ho.st wrote:
> >
> > >  (you can proceed the process there by
> > > replacing 0x8a05 to 0x0a05...)
> >
> > This change allows the driver to load, but:
>
> there are two places which check AC97_REC_GAIN.
> line 1980 and line 2064 in the latest cvs.
> you'll need to change both parts.

Thanks, that seemed to do the trick.  I did have to force the building of
the PC Speaker controls as well, but it seems to work okay now (the mixer
controls actually seem to work better than with the 'maestro' kernel
driver :)).

It does seem that something still isn't quite right though.  I'm getting
quite a few of these types of messages:

kernel: ALSA ../alsa-kernel/core/pcm_lib.c:156: Unexpected hw_pointer
value (stream = 0, delta: -922, max jitter = 1024): wrong interrupt
acknowledge?
kernel: ALSA ../alsa-kernel/core/pcm_lib.c:215: Unexpected hw_pointer
value (stream = 0, delta: -998, max jitter = 1024): wrong interrupt
acknowledge?
kernel: ALSA ../alsa-kernel/core/pcm_lib.c:156: Unexpected hw_pointer
value (stream = 0, delta: -694, max jitter = 1024): wrong interrupt
acknowledge?
kernel: ALSA ../alsa-kernel/core/pcm_lib.c:156: Unexpected hw_pointer
value (stream = 0, delta: -1094, max jitter = 8192): wrong interrupt
acknowledge?
kernel: ALSA ../alsa-kernel/core/pcm_lib.c:156: Unexpected hw_pointer
value (stream = 0, delta: -972, max jitter = 8192): wrong interrupt
acknowledge?
kernel: ALSA ../alsa-kernel/core/pcm_lib.c:215: Unexpected hw_pointer
value (stream = 0, delta: -688, max jitter = 8192): wrong interrupt
acknowledge?
kernel: ALSA ../alsa-kernel/core/pcm_lib.c:156: Unexpected hw_pointer
value (stream = 0, delta: -1488, max jitter = 8192): wrong interrupt
acknowledge?
kernel: ALSA ../alsa-kernel/core/pcm_lib.c:215: Unexpected hw_pointer
value (stream = 0, delta: -532, max jitter = 8192): wrong interrupt
acknowledge?

I've also had the system hang once when unloading the ALSA kernel modules,
as well as very rarely seeing these messages:

kernel: spurious 8259A interrupt: IRQ7.
kernel: spurious 8259A interrupt: IRQ15.

Any thoughts on what might be the problem?  Thanks.

  - Ted


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf