Happy holidays !
I have a toshiba satellite 2800-S202, with a yamaha sound card
YMF-754. From the lspci output I see:
00:0c.0 Multimedia audio controller: Yamaha Corporation YMF-754 [DS-1E
Audio Controller]
Subsystem: Toshiba America Info Systems Unknown device 0001
Flags: medium devsel, IRQ 11
Memory at efdf0000 (32-bit, non-prefetchable) [size=32K]
I/O ports at fec0 [size=64]
I/O ports at febc [size=4]
Capabilities: <access denied>
This output is from kernel 2.6.23, see "uname -a" output:
Linux ojvn 2.6.23-1-686 #1 SMP Fri Dec 21 13:57:07 UTC 2007 i686 GNU/Linux
Under linux kernel image 2.6.22-3 and mostly all previous kernels for
quiet a while, I haven't had problems using this card, but for some
reason now on 2.6.23-1 the card request for interrupt is failing.
>From dmesg:
ACPI: PCI Interrupt 0000:00:0c.0[A] -> Link [LNKB] -> GSI 11 (level,
low) -> IRQ 11
firmware request failed: -2
ACPI: PCI interrupt for device 0000:00:0c.0 disabled
Yamaha DS-1 PCI: probe of 0000:00:0c.0 failed with error -2
Which kind of gets confirmed when trying to select the card from alsaconf:
amixer: Mixer attach default error: No such device
Or when trying to use alsamixer:
alsamixer: function snd_ctl_open failed for default: No such device
Weird thing is that the corresponding module actually got intalled:
# lsmod | grep ymfpci
snd_ymfpci 34720 0
gameport 15112 1 snd_ymfpci
snd_ac97_codec 92388 1 snd_ymfpci
snd_pcm 72132 3 snd_ymfpci,snd_ac97_codec,snd_pcm_oss
snd_opl3_lib 9952 1 snd_ymfpci
snd_page_alloc 10088 2 snd_ymfpci,snd_pcm
snd_mpu401_uart 8128 1 snd_ymfpci
snd_timer 21156 4 snd_ymfpci,snd_pcm,snd_opl3_lib,snd_seq
snd 48356 13
snd_ymfpci,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_opl3_lib,snd_hwdep,snd_mpu401_uart,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
firmware_class 9472 2 snd_ymfpci,pcmcia
Maybe the problem is not with the hardware itself, but with some
firmware issue, as indicated by dmesg (firmware request failed).
I'm attaching the dmesg output, the lspci -v output, the alsaconf output...
Did something particularly special changed with kernel 2.6.23-1, which
might be 2.6.23-2 instead according to aptitude (reading from aptitude
linux-image-2.6.23-1-686, version 2.6.23-2)?
By the way, I'm using unstable, which I have been for some time now...
Thanks,
--
Javier
Attachment:
lspci_v.log
Description: Binary data
Attachment:
dmessg.log
Description: Binary data
Attachment:
alsaconf.log
Description: Binary data