From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0002219]: snd-mpu401 don't load
Date: Sun, 18 Jun 2006 17:41:22 +0200 [thread overview]
Message-ID: <cf8ec2bb2e1e1dfd918260e83e72c2c3@bugtrack.alsa-project.org> (raw)
The following issue has been SUBMITTED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2219>
======================================================================
Reported By: El Santo
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 2219
Category: GENERIC - mpu401
Reproducibility: always
Severity: major
Priority: normal
Status: new
Distribution: Debian etch (2006-06-18)
Kernel Version: 2.6.15-1-686
======================================================================
Date Submitted: 06-18-2006 17:41 CEST
Last Modified: 06-18-2006 17:41 CEST
======================================================================
Summary: snd-mpu401 don't load
Description:
I have a Aopen MX63LE board with onboard sound managed by snd-via82xx
driver. It loads all necesary modules, includind snd-mpu401-uart, but no
snd-mpu401
The audio part of the driver works perfectly, but the midi port doesn't
work.
In BIOS i can set (and see) the mpu401 port (0x300 or 0x330) but there is
not a MPU401 IRQ setting in bios. When i tried to manually load snd-mpu401
(setting the port accordingly to BIOS) it doesnt work. I don't know the
mpu401 irq setting but i tryed them all. None of them worked. The driver
says "device not found".
Under windows xp the port works perfectly, so the hardware is ok. Anyway
under windows xp, i use a "system inspector" to monitor ioports and irq
usage, and i didnt see any irq assigned for mpu401 port, and the port
(0x330) wasn't occupied neither.
any idea?
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
06-18-06 17:41 El Santo New Issue
06-18-06 17:41 El Santo Distribution => Debian etch
(2006-06-18)
06-18-06 17:41 El Santo Kernel Version => 2.6.15-1-686
======================================================================
next reply other threads:[~2006-06-18 15:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-18 15:41 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-19 1:45 [ALSA - driver 0002219]: snd-mpu401 don't load bugtrack
2006-06-20 17:49 bugtrack
2006-06-20 21:30 bugtrack
2006-06-20 21:39 bugtrack
2006-06-20 21:54 bugtrack
2006-06-20 22:00 bugtrack
2006-06-20 22:04 bugtrack
2006-06-20 22:12 bugtrack
2006-06-20 22:18 bugtrack
2006-06-20 22:36 bugtrack
2006-06-20 23:30 ` Rene Herman
2006-06-20 23:35 ` Lee Revell
2006-06-20 23:46 ` Rene Herman
2006-06-20 23:54 ` Lee Revell
2006-06-20 23:57 ` Rene Herman
2006-06-20 22:52 bugtrack
2006-06-20 22:56 bugtrack
2006-06-21 0:02 bugtrack
2006-06-21 2:51 bugtrack
2006-06-21 16:00 bugtrack
2006-06-22 1:19 bugtrack
2006-06-22 1:29 bugtrack
2006-06-22 12:30 bugtrack
2006-06-24 7:43 bugtrack
2006-06-25 20:02 bugtrack
2006-06-26 4:52 bugtrack
2006-06-26 16:44 bugtrack
2006-06-26 16:51 bugtrack
2006-06-26 17:14 bugtrack
2006-06-26 17:25 bugtrack
2006-06-27 6:41 bugtrack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cf8ec2bb2e1e1dfd918260e83e72c2c3@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.