Re: Strange issue with opl3sa2 driver under linux 2.4.4

[David Nedved <dnedved@nuvox.net>]

Merci beaucoup Jérôme!  You are indeed correct, somehow you saw through my
rantings, and although I thought I had tested everything extensively and
scientifically, it does indeed work with 0x370...

Now I have an alias in /etc/modules.conf so that all I have to do is 
modprobe opl3sa2 and everything works... if you don't mind I'd like to ask a
few questions about getting it a little more automated...

1.) any idea how to get it automatically inserted when I try to use the sound
    card?  (For ethernet cards I know you alias eth0 to the driver name, 
    but aliasing dsp and sound to opl3sa2 don't seem to work)
2.) any ideas how to avoid the "opl3sa2: Control I/O port 0x370 is not free"
    messages since they are apparently bogus?
3.) any ideas what to do to make it work when compiled into the kernel?
    a line in lilo to pass parameters to the kernel?

Thanks again,

David

On Thu, Jun 28, 2001 at 09:04:29PM +0200, Jérôme Augé wrote:
> David Nedved wrote:
> > 
> > Hi all,
> > 
> > I'm trying to get sound working on my laptop, and  I'm having some strange
> > problems getting it work as expected, and I hope that you can give me some
> > insight.  I have a Toshiba Libretto 70CT, which is one of the hardware
> > platforms that is mentioned as working in the docs... I CAN get sound out of
> > it, but only after a strange ritual...
> > 
> > I have to do this to get it to work:
> > 
> > #modprobe opl3sa2 io=0x220 mss_io=0x530 mpu_io=0x330 irq=5 dma=1 dma2=0
> > opl3sa2: Control I/O port 0x220 is not a YMF7xx chipset!
> > #modprobe opl3sa2 io=0x370 mss_io=0x530 mpu_io=0x330 irq=5 dma=1 dma2=0
> > opl3sa2: Control I/O port 0x370 is not free
> > opl3sa2: Control I/O port 0x370 is not free
> > opl3sa2: Control I/O port 0x370 is not free
> > #modprobe opl3sa2 io=0x220 mss_io=0x530 mpu_io=0x330 irq=5 dma=1 dma2=0
> > 
> > notice that I have to modprobe it FIRST at 0x370, it fails, then it will
> > insert into 0x220!  I have verified all the settings through both the BIOS
> > setup utility and by dual-booting into Windows98.
> > 
> > This is with kernel version 2.4.4.  Do you have any idea about why it is
> > acting so strange upon inserting?  In /proc/ioports it lists 0x370 as belonging
> > to OPL3-SA3, and 0x220 is not listed, however 0x220 is
> > the address that it ends up working under both in Windows98 and Linux.
> > 
> > Thanks very much, I really hope you have some idea how to work around this
> > more elegantly (so that maybe I can boot and have sound without typing all
> > that junk!)  If there's anything I can do to experiment around that would help
> > others, just let me know and I'll be happy to do it.
> > 
> 
> Are you sure it really fails when modprobing at 0x370 ?
> 
> Try to modprobe at 0x370 and immediatly look at the output of "lsmod" to
> see if the driver is really loaded or not ... ???
> 
> -- 
> Jérôme Augé
> echo cdqgm@vnqb-hklmpkml.yp | tr khplmndvqyc nirtelacufj
> -
> To unsubscribe from this list: send the line "unsubscribe linux-laptop" in
> the body of a message to majordomo@vger.kernel.org
> 
-
To unsubscribe from this list: send the line "unsubscribe linux-sound" in
the body of a message to majordomo@vger.kernel.org