14 Nov
2006
14 Nov
'06
11:12 a.m.
2006/11/13, Clemens Ladisch <cladisch(a)fastmail.net>et>:
Sorry I made a mess out of this, the parameters for my AmiBIOS setup
should have read "Port 0x300" and "IRQ 5".
I tried this and unfortunately that doesn't change things for me (even
when passing 32 zeroes to pnp)... I am still getting this:
[17180009.552000] pnp: Device 00:09 activated.
[17180009.552000] pnp: Device 00:09 disabled.
and
[17180088.212000] cmd: 0xff failed at 0x300 (status = 0xff, data = 0xff)
when trying to access the port.
I have also tried passing the "enable" option to the module, no luck.
Besides why shouldn't it work with pnp? ACPI is working fine for
everything else.
I tested a new configuration with different values by rebooting and
setting the MPU IOPort to 0x330 and IRQ to 11 on the BIOS. When the
system came up again I "rmmoded" and modprobed again snd-mpu401
without passing any option to it and it got the right values from the
bios:
# cat /proc/ioports | grep MPU
0330-0331 : MPU401 UART <- that's corret I set this to 330 int the BIOS setup
cat /proc/interrupts | grep MPU
11: 1 IO-APIC-edge MPU401 UART <- that's also correct
IRQ set to 11 in the BIOS
I still got the same syslog entries, it didn't work.
I went the trouble of upgrading the BIOS(version 1.90 to 2.60) with an
msdos bootcd but that didn't help either with pnp on or off.
The way AmiBios works you can't have the midi port disabled and still
set it's I/O and IRQ addresses so *I am sure* it's not due to the port
being disabled.
I also have the gameport enabled at IOPort 0x200 but that shouldn't be
a problem AFAIK, I tried disabling it but that didn't help either.
Here's "an ascii screenshot" of my Bios setup (and possible values you
can have):
OnBoard MidiPort 300 (this can be "300", "330", or
"disabled")
Midi IRQ Select 5 ("5", "10", "11" or
grayed out
if midiport above is "disabled")
OnBoard Game Port 200 ("200" or "disabled")
Again those values cannot be set if those peripherals aren't enabled
as they would be grayed out. Unless the HW on this MB is faulty the
mpu module doesn't IMHO.
Hard to describe the mess that's going on with this (not saying it's
your fault of course), master volume control seems to not be working
but for lowering line-in monitoring levels, changing line-in
monitoring does nothing.
Previous kernel versions (2.6.13 or 14 if I memory serves me well)
would fail to recognize this MB's HW mixer and completely fail to
present it to the system, so I couldn't launch any mixer app but sound
worked fine, I just could not set my levels...
cmd: 0xff
failed at 0x300 (status = 0xff, data = 0xff)
········································································
This means there is no MPU-401 device at this address (either the port
address is wrong, or the device is disabled).
My MPU port is set at IRQ 0x300 DMA 5,
Is
that how your BIOS labels these numbers? :) modprobe -v snd_mpu401 pnp=0 port=0x300 irq=5
Oops, the module actually supports eight devices, and PnP is enabled
by default for all of them. Use:
modprobe snd-mpu401 pnp=0,0,0,0,0,0,0,0 port=0x300 irq=5
(Unless you have configured the kernel to use dynamic device numbers for
ALSA devices, then it supports 32 devices ...) [17179872.004000] pnp: Device 00:09 activated.
[17179872.004000] pnp: Device 00:09 disabled.
I just noticed this now, it seems like it's trying to initialize the
MPU port but silently fails?
There should be some message in case of an error.
I am starting to think that this particular
motherboard audio codec is
either buggy, or not well supported by ALSA
The MIDI port is implemented in a different chip.
as I also have issues with the HW mixer... things
are swapped around,
and there is no "ac97_quirk" module parameter for remapping things
that works.
Which mixer controls are routed to which hardware outputs? What mainboard model is this?
This is an old AthlonXP 2800+ system, the MB is an ASRock K7S41
(SIS7012 sound) http://www.asrock.com/product/K7S41.htm
Thanks for looking into this.
Regards,
-Giuseppe