[PlanetCCRMA] Self-configuring system Was:*Solved* Midisport 8x8/s Was:Chasing my tail with ALSA

Michael mikes@tbc.net
Tue Feb 17 05:25:02 2004


Hi all...

This is weird.

Today I turn on my system, and guess what? I don't have my Midisport 8x8 
in the ALSA Patchbay anymore. So, I do a little investigating, only to 
find lsmod showing snd-seq-oss, and snd-mixer-oss in the setup again.  I 
wonder what causes this? One thing I notice, is that Kudzu will pause a 
bit on boot, look for new hardware, and then continue to load. Could 
this be the problem?

Cheers,
-Mike

[root@localhost sbin]# ./lsmod
Module                  Size  Used by    Not tainted
ppp_deflate             4568   0  (autoclean)
zlib_deflate           21560   0  (autoclean) [ppp_deflate]
ppp_async              10144   1  (autoclean)
ppp_generic            28672   3  (autoclean) [ppp_deflate ppp_async]
slhc                    6860   1  (autoclean) [ppp_generic]
snd-seq-oss            36352   0  (autoclean) (unused)
snd-seq-midi            5312   0  (autoclean) (unused)
snd-mixer-oss          16272   0  (autoclean)
i810                   69220  12
agpgart                57572   7  (autoclean)
parport_pc             19268   1  (autoclean)
lp                      9252   0  (autoclean)
parport                39904   1  (autoclean) [parport_pc lp]
snd-emu10k1-synth       6076   0  (unused)
snd-emux-synth         36156   0  [snd-emu10k1-synth]
snd-seq-midi-emul       7332   0  [snd-emux-synth]
snd-seq-virmidi         5320   0  [snd-emux-synth]
snd-seq-midi-event      6720   0  [snd-seq-oss snd-seq-midi snd-seq-virmidi]
snd-seq                53072   2  [snd-seq-oss snd-seq-midi 
snd-emux-synth snd-seq-midi-emul snd-seq-virmidi snd-seq-midi-event]
snd-emu10k1            89428   0  [snd-emu10k1-synth]
snd-pcm                91936   0  [snd-emu10k1]
snd-timer              22308   0  [snd-seq snd-pcm]
snd-page-alloc         10356   0  [snd-emu10k1 snd-pcm]
snd-rawmidi            20288   0  [snd-seq-midi snd-seq-virmidi snd-emu10k1]
snd-ac97-codec         59180   0  [snd-emu10k1]
snd-util-mem            3400   0  [snd-emux-synth snd-emu10k1]
snd-seq-device          6336   0  [snd-seq-oss snd-seq-midi 
snd-emu10k1-synth snd-emux-synth snd-seq snd-emu10k1 snd-rawmidi]
snd-hwdep               7200   0  [snd-emu10k1]
snd                    49956   0  [snd-seq-oss snd-seq-midi 
snd-mixer-oss snd-emux-synth snd-seq-virmidi snd-seq-midi-event snd-seq 
snd-emu10k1 snd-pcm snd-timer snd-rawmidi snd-ac97-codec snd-util-mem 
snd-seq-device snd-hwdep]
soundcore               7204   7  [snd]
ipt_REJECT              4344   6  (autoclean)
iptable_filter          2444   1  (autoclean)
ip_tables              16512   2  [ipt_REJECT iptable_filter]
sg                     38604   0  (autoclean)
sr_mod                 18200   0  (autoclean)
microcode               5408   0  (autoclean)
ide-scsi               12400   0
scsi_mod              112820   3  [sg sr_mod ide-scsi]
ide-cd                 36224   0
cdrom                  34464   0  [sr_mod ide-cd]
nls_iso8859-1           3516   1  (autoclean)
nls_cp437               5148   1  (autoclean)
vfat                   13324   1  (autoclean)
fat                    40856   0  (autoclean) [vfat]
printer                 9376   0
keybdev                 2976   0  (unused)
mousedev                5720   1
hid                    24740   0  (unused)
input                   6176   0  [keybdev mousedev hid]
usb-uhci               28524   0  (unused)
usbcore                84000   1  [printer hid usb-uhci]
ext3                   74596   2
jbd                    58320   2  [ext3]


Michael wrote:

> Found the problem.....
> Somehow the snd-mixer-oss, and snd-seq-oss drivers got reactivated. I 
> removed them with the following command:
>
> '/sbin/rmmod snd-mixer-oss'
> and...
> '/sbin/rmmod snd-seq-oss'
>
> When I rebooted, I was able to see all eight ports in the ALSA 
> Patchbay. Cool! In the ALSA Patchbay status window, I still see "Could 
> not connect to LADCCA Server, LADCCA Disabled" What is this, and is 
> this "normal"? Other than that, all appears to be operating normally 
> now :-)
>
> Thanks all for the help :-)
>
> Cheers,
> Mike
>
>
>