This is a discussion on Re: Linux kernel image 2.6.23-1 + sound card yamaha YMF-754 - Debian ; On Dec 29, 2007 11:31 AM, Javier Vasquez wrote: > > Happy holidays ! > > I have a toshiba satellite 2800-S202, with a yamaha sound card > YMF-754. From the lspci output I see: > > ... > > ...
On Dec 29, 2007 11:31 AM, Javier Vasquez
> Happy holidays !
> I have a toshiba satellite 2800-S202, with a yamaha sound card
> YMF-754. From the lspci output I see:
> 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
> 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
> 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 to the Debian-User mailing list, it was uncovered that the
firmware generation from the kernel was removed through patching by
Debian. Any reason for that? What's the expectation from the users?
Are they supposed to download the firmware sources from the alsa web,
and compile it and install it themselves? Or are they supposed to
compile the kernel "unpatching" the Debian removal of the firmware
generation under kernel compilation?
My supposition is that the attempt is for the user to go download the
firmware and place it in this case under /lib/firmware/yamaha, since
that's way simpler than "unpatching"... However I'd like to know what
do you guys expect from the users, ...
BTW, downloading and installing the firmware actually worked out, as I
reported in the debian-user mailing list...
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org