All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russ Dill <Russ.Dill@asu.edu>
To: dbronaugh@opensourcedot.com, linux-kernel@vger.kernel.org
Subject: Re: Breakage of opl3sax cards since 2.4.3 (at least)
Date: Wed, 02 May 2001 00:09:58 -0700	[thread overview]
Message-ID: <3AEFB2C6.24F7B40D@asu.edu> (raw)

Actually, this occured at 2.4.2

I searched though the archives, and the only people who were able to get
this resolved were those with a non-isapnp card (by added isapnp=0).
However, I have an isapnp card and the driver doesn't think my card
exists. If I lod it, withot options, I get:

russ kernel: opl3sa2: ISA PnP activate failed
russ kernel: opl3sa2: No PnP cards found
russ kernel: opl3sa2: 0 PnP card(s) found.

OK, so I use my old isapnp.conf 

russ:/home/russ# isapnp /etc/isapnp.conf

then insmod it like this:
Board 1 has Identity 81 ff ff ff ff 20 00 a8 65:  YMH0020 Serial No -1
[checksum 81]
YMH0020/-1[0]{OPL3-SAX Sound Board}: Ports 0x240 0xE80 0x388 0x300
0x100; IRQ10 DMA0 DMA3 --- Enabled OK
YMH0020/-1[1]{OPL3-SAX Sound Board}: Port 0x204; --- Enabled OK

russ:/home/russ# insmod opl3sa2 irq=10 io=0x240 dma=0 dma2=3
mss_io=0xe80 isapnp=0
Using /lib/modules/2.4.4-ac1-lpp/kernel/drivers/sound/opl3sa2.o
/lib/modules/2.4.4-ac1-lpp/kernel/drivers/sound/opl3sa2.o: init_module:
No such device
Hint: insmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters


hmm, and kern.log says:

russ kernel: opl3sa2: Control I/O port 0x240 is not a YMF7xx chipset!

something in the changeover forgot about my card

             reply	other threads:[~2001-05-02  7:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-02  7:09 Russ Dill [this message]
2001-05-02  8:30 ` Breakage of opl3sax cards since 2.4.3 (at least) Vivek Dasmohapatra
2001-05-02  8:50   ` Russ Dill
2001-05-02  8:55     ` Vivek Dasmohapatra
  -- strict thread matches above, loose matches on Subject: below --
2001-05-01 22:39 David Bronaugh
2001-05-01 23:26 ` Vivek Dasmohapatra

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=3AEFB2C6.24F7B40D@asu.edu \
    --to=russ.dill@asu.edu \
    --cc=dbronaugh@opensourcedot.com \
    --cc=linux-kernel@vger.kernel.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.