From: Miles Lane <miles@speakeasy.org>
To: linux-sound@vger.kernel.org
Subject: Re: mad16 & ad1848 problems in kernel 2.3.50.
Date: Thu, 09 Mar 2000 16:04:22 +0000 [thread overview]
Message-ID: <marc-linux-sound-95261789511562@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-95261137204527@msgid-missing>
Hi Christoph,
I seem to be getting a very similar problem with 2.3.50.
I have sound stuff compiled into the kernel. One observation
is that in 2.3.50, when sound support is compiled into the
kernel, I no longer have the option of specifying the IRQ,
Port and DMA values. It seems to be trying to use Plug and
Play.
Mar 8 23:14:06 spot kernel: ad1848/cs4248 codec driver Copyright (C) by
Hannu Savolainen 1993-1996
Mar 8 23:14:06 spot kernel: MSS: I/O port conflict
Mar 8 23:14:06 spot kernel: YM3812 and OPL-3 driver Copyright (C) by
Hannu Savolainen, Rob Hooft 1993-1996
Mar 8 23:14:06 spot kernel: cs4232.c: I/O port 0xffffffff not free
Mar 8 23:14:06 spot kernel: adlib: must specify I/O address.
Christoph Hellwig wrote:
>
> On Thu, Mar 09, 2000 at 02:09:51PM +0100, Diego Liziero wrote:
> >
> > Kernel 2.3.50
> > depmod: *** Unresolved symbols in /lib/modules/2.3.50/misc/mad16.o
> > depmod: exit_mad16
> >
> > I got the symbol resolved with this patch:
> >
> > --- mad16.c.2.3.50.original Thu Mar 9 11:59:38 2000
> > +++ mad16.c Thu Mar 9 12:00:08 2000
> > @@ -1098,7 +1098,7 @@
> > return 0;
> > }
> >
> > -static void __exit cleanup_mad16(void)
> > +static void __exit exit_mad16(void)
> > {
> > if (found_mpu)
> > unload_mad16_mpu(&cfg_mpu);
>
> Ok, but module_exit needs to be adjusted, too.
>
> >
> > But when I issue a modprobe mad16 I get the following error:
> >
> > MSS: I/O port conflict
> > /lib/modules/2.3.50/misc/ad1848.o: init_module: Device or resource busy
> > /lib/modules/2.3.50/misc/ad1848.o: insmod /lib/modules/2.3.50/misc/ad1848.o failed
> > /lib/modules/2.3.50/misc/ad1848.o: insmod mad16 failed
> >
> > If I use the ad1848.o of a 2.3.49 kernel all works fine.
>
> Hmm, with ad1848 something seems to be not ok, I'll look at it ...
>
> Christoph
>
> --
> Always remember that you are unique. Just like everyone else.
prev parent reply other threads:[~2000-03-09 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-09 14:07 mad16 & ad1848 problems in kernel 2.3.50 Christoph Hellwig
2000-03-09 14:08 ` Christoph Hellwig
2000-03-09 14:08 ` Christoph Hellwig
2000-03-09 14:08 ` Christoph Hellwig
2000-03-09 14:08 ` Christoph Hellwig
2000-03-09 16:04 ` Miles Lane [this message]
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=marc-linux-sound-95261789511562@msgid-missing \
--to=miles@speakeasy.org \
--cc=linux-sound@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox