Re: 2.5.6x Sound frustration

[Scott Robert Ladd <coyote@coyotegulch.com>]

Takashi Iwai wrote:
> if it's not the case, try to unmute and raise "Headphone" volume.
> some devices use True LINEOUT as the wave lineout.
> if this solves the problem, please let me know the output of
> "lspci -vv" and "lspci -nv" (for the sound deice only).

That didn't solve the problem, but here's the output anyway, in case 
it's of any use to you.

The output from lspci -vv (rewrapped for clarity)

00:1f.5 Multimedia audio controller: Intel Corp. 82801BA/BAM AC'97 Audio 
(rev 04)
         Subsystem: Intel Corp.: Unknown device 4d44
         Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- 
ParErr- Stepping- SERR- FastB2B-
         Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium 
 >TAbort-                <TAbort- <MAbort- >SERR- <PERR-
         Latency: 0
         Interrupt: pin B routed to IRQ 17
         Region 0: I/O ports at e800 [size=256]
         Region 1: I/O ports at ef00 [size=64]

And lspci -nv

00:1f.5 Class 0401: 8086:2445 (rev 04)
         Subsystem: 8086:4d44
         Flags: bus master, medium devsel, latency 0, IRQ 17
         I/O ports at e800 [size=256]
         I/O ports at ef00 [size=64]

The above was generated while running the 2.5.66 kernel. I've run 
several different mixers, looking for any unusual "

This morning, I compiled 2.5.68; while I'm running Rusty's latest 
modutils, I had many symbol errors when trying to compile sound support 
as modules.  With sound compiled into the kernel, the ALSA driver 
appeared to load, but none of the devices were created; when the boot 
tried to restore mixer settings, for example, it reported that the mixer 
could not be found.

Everything else on the system seems to work fine with both .66 and .68.

I have had sound working on this machine using Debian sid's stock 2.4.20 
kernel.

-- 
Scott Robert Ladd
Coyote Gulch Productions (http://www.coyotegulch.com)