17 Aug
2005
17 Aug
'05
2:30 p.m.
On Wednesday 17 August 2005 19:04, linux-audio-user-request(a)music.columbia.edu
wrote:
index=2 irq=-1 port=0x300
I tried putting in pnp=0. No change. I believe that an "apm" is working rather
than the full "acpi" on my MB.
This is done
on startup. Get device not found or busy.
What parameters are set in /etc/modprobe.conf for this module? Is
ACPI enabled, or are you using "pnp=0"? 
18 Aug
18 Aug
5:30 a.m.
David Baron wrote:
On Wednesday 17 August 2005 19:04,
linux-audio-user-request(a)music.columbia.edu
wrote:
index=2 irq=-1 port=0x300
I tried putting in pnp=0. No change. I believe that an "apm" is working rather
than the full "acpi" on my MB.
You should always use "pnp=0" because that parameter is present when
the generic PnP code is enabled in the kernel.
If you have an older ALSA version, this parameter might be named
acpipnp instead of pnp; see the output of "modinfo snd-mpu401".
There is no reason why the driver should refuse to load because it
doesn't actually check for the presence of the hardware. This seems
to be a bug in Demudi/Debian similar to the snd-virmidi bug.
Regards,
Clemens
This is
done on startup. Get device not found or busy.
What parameters are set in /etc/modprobe.conf for this module? Is
ACPI enabled, or are you using "pnp=0"?
7039
days inactive
7040
days old
linux-audio-user@lists.linuxaudio.org
1 comments
2 participants
participants (2)
-
Clemens Ladisch -
David Baron