On Thursday 22 July 2004 21:51, [EMAIL PROTECTED] wrote:
> On Thu, 2004-07-22 at 20:35, Frans Ketelaars wrote:
> > On Wednesday 21 July 2004 23:37, [EMAIL PROTECTED] wrote:
> > > On Wed, 2004-07-21 at 22:44, Frans Ketelaars wrote:
> > > > > # lsmod
> > > > > Module Size Used by
> > > > > ...
> > > > > sound 78956 6 opl3,sb_lib,uart401
> > > >
> > > > The above says you are using OSS now. You can't use ALSA until
> > > > the OSS modules are removed.
> > >
> > > That sounds like a very good lead. How do I know which modules I
> > > should remove to eliminate OSS? From /proc/modules:
> > >
> > > snd-opl3-lib 9984 0 - Live 0xccaf1000
> > > snd-hwdep 8928 1 snd-opl3-lib, Live 0xccaed000
> > > snd-es1688-lib 14224 0 - Live 0xccaca000
> > > snd-pcm 93156 1 snd-es1688-lib, Live 0xccb09000
> > > snd-page-alloc 11972 1 snd-pcm, Live 0xccac6000
> > > snd-timer 24484 2 snd-opl3-lib,snd-pcm, Live 0xccae6000
> > > snd-mpu401-uart 7072 0 - Live 0xccac3000
> > > snd-rawmidi 23616 1 snd-mpu401-uart, Live 0xccadf000
> > > snd-seq-device 8008 2 snd-opl3-lib,snd-rawmidi, Live 0xccac0000
> > > snd 52484 8
> > > snd-opl3-lib,snd-hwdep,snd-es1688-lib,snd-pcm,snd-timer,
> > > snd-mpu401-uart,snd-rawmidi,snd-seq-device, Live 0xccad1000 opl3
> > > 15276 0 - Live 0xccabb000
> > > sb 10372 0 - Live 0xcc9fc000
> > > isofs 33912 0 - Live 0xcca54000
> > > zlib_inflate 22656 1 isofs, Live 0xcca43000
> > > sb_lib 47664 1 sb, Live 0xcca23000
> > > uart401 11364 1 sb_lib, Live 0xcc95a000
> > > sound 78956 6 opl3,sb_lib,uart401, Live 0xcca0e000
> > > soundcore 9248 9 snd,sb_lib,sound, Live 0xcc956000
> > > scsi_mod 114648 4 sg,st,sr_mod,sd_mod, Live 0xcc9da000
> > > autofs4 14656 2 - Live 0xcc91b000
> > > nfsd 173152 8 - Live 0xcc9ae000
> > > ... (cut)
> > >
> > > I don't see a way to identify which modules are OSS and which are
> > > ALSA. I think the snd-something ones are ALSA, right?
> >
> > Yes, and soundcore is also needed. '/sbin/modinfo <module_name>'
> > gives module info. Soundcore is needed for both OSS and ALSA. All
> > sound related modules not beginning with snd- are OSS modules
> > AFAIK.
> >
> > > So I'm guessing
> > > sb_lib, uart401 and opl3 are OSS. Is this correct? Any others I
> > > should also remove?
> > >
> > > Thanks,
> > > GermÃn.
> >
> > Some of the modules to remove may be used by another module so you
> > would have to know which ones to remove first. I think it's easier
> > to undo what sndconfig did. Sndconfig is an old program to set up
> > the OSS soundsystem, I think it should in general _not_ be used.
> >
> > Please post your /etc/modules.conf, that's the most important file
> > that is changed by sndconfig. The 2.6 kernel uses
> > /etc/modprobe.conf so post that too.
>
> /etc/modules.conf:
> probeall usb-interface usb-uhci
> alias sound-slot-0 sb
> options sound dmabuf=1
> alias synth0 opl3
> options opl3 io=0x388
> options sb io=0x220 irq=11 dma=0 dma16=5 mpu_io=0x330
>
> /etc/modprobe.conf:
> alias sound-slot-0 sb
> options sound dmabuf=1
> alias synth0 opl3
> options opl3 io=0x388
> options sb io=0x220 irq=11 dma=0 dma16=5 mpu_io=0x330
> install usb-interface /sbin/modprobe usb-uhci; /bin/true
>
> If I understand this sndconfig has loaded the following modules: sb,
> sound, opl3. No mention here of uart401, but I don't know if that has
> any significance.
>
> > If it worked in 9.0 it should work with 10.0 and it should work
> > with ALSA but that doesn't mean that it will :-( I think the best
> > way is to undo what sndconfig did,
>
> How would I go about that? Simply unloading sb, sound and opl3 (and
> maybe uart401)?
Yes, and edit /etc/modules.conf and /etc/modprobe.conf as Raffaele
BELARDI wrote. If you then reboot the OSS modules simply shouldn't load
anymore during that boot (no need to remove them manually first). I
would also use a cold boot (power off the machine for at least 30
seconds) to ensure that the card is in a 'standard' state when booting.
One of the reasons I say this is that the OSS sb module was loaded and
you wrote about the soundsystem being 'Soundblaster compatible'. Maybe
the OSS driver put the card in some 'Soundblaster compatible mode' and
maybe a warm reboot nor loading the ALSA driver do remedy that. Maybe I
am just paranoid ;-)
> > reboot (not strictly needed) and start again
> > configuring your sound if needed: first try the Mandrake tools, if
> > that doesn't work ALSA's alsaconf utility. If that doesn't work you
> > can try sndconfig again when ALSA isn't loaded. At the moment you
> > have an interesting mix of OSS and ALSA modules :-)
>
> You know, MCC doesn't even show any option to configure sound, and in
> the hardware section there is no mention of a sound card. If I reboot
> with CD1 and reach the post-install config I can configure the
> keyboard, display etc, but no mention of sound. Weird. I'll take one
> more look after undoing sndconfig's evil workings, but I'm not too
> hopeful.
Yes, I think it's because it's an ISA card. Alsaconf is able to setup
ISA cards though.
> Thanks a lot for your help.
> GermÃn.
You're very wellcome, that's what this list is for :-)
-Frans
____________________________________________________
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com
____________________________________________________
