: ISAPNP cards (opl3sa2 in particular) are not detected properly on 2.6 kernels
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1326>
======================================================================
Reported By: ahaning Assigned To: perex ====================================================================== Project: ALSA - utils Issue ID: 1326 Category: alsaconf Reproducibility: always Severity: major Priority: normal Status: assigned ====================================================================== Date Submitted: 08-10-2005 03:39 CEST Last Modified: 08-11-2005 23:59 CEST
======================================================================
Summary: ISAPNP cards (opl3sa2 in particular) are not
detected properly on 2.6 kernels
Description:
When brute-force detecting my OPL3SA2 card, the IRQ and DMA1/DMA2 settings are incorrectly detected by alsaconf from alsa-utils. For example, the default BIOS settings are IRQ=11, DMA1=0, DMA2=1, but alsaconf detects IRQ=5, DMA1=1, DMA2=0. No matter the BIOS settings, alsaconf always detects those settings (IRQ=5, DMA1=1, DMA2=0). If I set the BIOS settings to that, then the card will make sound (after touching the mixer while playing audio).
According to perex (author of the opl3sa2 driver):
"The alsaconf tries to gather free resources (irq/dma/ports) from the /proc filesystem. It might be extended to gather this information also from /sys filesystem."
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0000879 (snd_)opl3sa2 (isa) doesn't work (fails...
======================================================================
----------------------------------------------------------------------
ahaning - 08-11-05 00:24
----------------------------------------------------------------------
Well, I'm going to guess that last time, my system was in some odd state.
Here are the BIOS settings for my card (I had it set them to the defaults):
PnP = On
I/O = 220H-22FH
MPU-401 I/O = 330H - 333H
IRQ = 11
DMA 1 = CH0
WAVE 2 DMA = CH1
When I run the above alsaconf and have it bruteforce detect my card, it produces the following /etc/modprobe.conf:
# --- BEGIN: Generated by ALSACONF, do not edit. ---
# --- ALSACONF version 1.0.9a ---
alias snd-card-0 snd-opl3sa2
alias sound-slot-0 snd-opl3sa2
options snd-opl3sa2 fm_port=-1 midi_port=-1 port=0x370 wss_port=0x530 isapnp=0 dma1=1 dma2=0 irq=5
# --- END: Generated by ALSACONF, do not edit. ---
Also, when it is doing the detection, I get the following badness in dmesg:
pnp: the driver 'opl3sa2' has been registered
pnp: the driver 'opl3sa2' has been unregisteredkobject_register failed for snd_generic_pm (-17)
[<c020bdf4>] kobject_register+0x44/0x70 [<c0290417>] bus_add_driver+0x57/0xd0 [<cca92984>] snd_generic_device_register+0x24/0xa0 [snd] [<cca92b13>] snd_card_set_generic_pm_callback+0x13/0x60 [snd] [<ccaaa7b5>] snd_cs4231_create+0x1f5/0x380 [snd_cs4231_lib] [<ccaaa280>] snd_cs4231_pm_suspend+0x0/0x30 [snd_cs4231_lib] [<ccaaa2b0>] snd_cs4231_pm_resume+0x0/0x30 [snd_cs4231_lib] [<ccaa3a17>] snd_opl3sa2_probe+0x227/0x520 [snd_opl3sa2] [<cc8607ad>] alsa_card_opl3sa2_init+0x8d/0x97 [snd_opl3sa2] [<c0135ac7>] sys_init_module+0x1f7/0x220 [<c0103205>] syscall_call+0x7/0xb kobject_register failed for snd_generic_pm (-17) [<c020bdf4>] kobject_register+0x44/0x70 [<c0290417>] bus_add_driver+0x57/0xd0 [<cca92984>] snd_generic_device_register+0x24/0xa0 [snd] [<cca92b13>] snd_card_set_generic_pm_callback+0x13/0x60 [snd] [<ccaa3b4b>] snd_opl3sa2_probe+0x35b/0x520 [snd_opl3sa2] [<ccaa36b0>] snd_opl3sa2_suspend+0x0/0x50 [snd_opl3sa2] [<ccaa3700>] snd_opl3sa2_resume+0x0/0x90 [snd_opl3sa2] [<cc8607ad>] alsa_card_opl3sa2_init+0x8d/0x97 [snd_opl3sa2] [<c0135ac7>] sys_init_module+0x1f7/0x220 [<c0103205>] syscall_call+0x7/0xb
pnp: the driver 'opl3sa2' has been registered
Occasionally, I get a lockup when my system goes to reboot. The drives are all un/re-mounted and everything's shut down, but there's an error like the above.
HTH and thanks.
----------------------------------------------------------------------
ahaning - 08-11-05 23:59
----------------------------------------------------------------------
I searched bugzilla.kernel.org today and found a bug
<http://bugzilla.kernel.org/show_bug.cgi?id=4561> that looks like it's related to this bug.
I tried the comment to list devices detected by pnp in /sys. Here's what I get:
# find */id | xargs cat PNP0c02 PNP0c01 PNP0c02 NMX2210 NMX2220 PNP0a03 PNP0200 PNP0000 PNP0100 PNP0b00 PNP0303 PNP0c04 PNP0800 PNP0f13 PNP0501 PNP0510 PNP0401 #
The two NMX lines look promising. I tried the hack to enable the devices before inserting the module with no luck.
Anyway, thought I'd mention this.
Issue History
Date Modified Username Field Change
======================================================================
08-10-05 03:39 ahaning New Issue
08-10-05 03:39 ahaning Distribution => Slackware 9.1 (but
it's not distribution-specific)
08-10-05 03:39 ahaning Kernel Version => 2.6.12.2 08-10-05 13:26 perex Status new => assigned 08-10-05 13:26 perex Assigned To => perex 08-10-05 13:26 perex File Added: alsaconf 08-10-05 13:28 perex Note Added: 0005747 08-10-05 13:29 perex Project ALSA - driver => ALSA - utils 08-10-05 13:30 perex Relationship added related to 0000879 08-10-05 13:31 perex Category 1_OTHERS => alsaconf 08-10-05 14:55 ahaning Note Added: 0005748 08-11-05 00:24 ahaning Note Added: 0005752 08-11-05 23:59 ahaning Note Added: 0005763
======================================================================
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf