Mailinglist Archive: opensuse (2425 mails)

[karen@xxxxxxxxxx (Karen)]

In article <39368071.3317E649@xxxxxxxxxxxxxxxxx>, Rafael E. Herrera
<raffo@xxxxxxxxxxxxxxxxx> writes
>"Paul W. Abrahams" wrote:
>> My experience is that "modprobe es1371" doesn't cause "sound" to be loaded,
>> although executing certain programs that refer to the sound module will
>> cause it to be loaded.  You can check: use rmmod to remove all the
>> sound-related modules and then try "modprobe es1371".  See if lsmod now
>> shows "sound" to be loaded.  For me, it isn't.  So I load it explicitly.
>
>Each module has dependencies that are resolved when you run 'depmod'.
>So, when you run 'modprobe', it will load the modules it depends on. If
>it doesn't load 'sound', then it doesn't need it. You can just load a
>module with 'insmod', this will just load the module if it can. 
>

I was using modprobe in preference to 'insprobe' partly because this is
recommended by the SuSE manual, and partly because I thought it would
resolve any dependencies. 
Either way modprobe'd modules are lost on reboot even though I thought I
had compensated for that by coding the relevant lines in the boot file,
as per Jon's recommendation. This bothers me because I am unfamiliar
with the SuSE system and suspect I am misunderstanding or simply missing
something about the way in which SuSE is handling the boot
sequence/system.
My experience with dependent modules seems to match Paul's here.

>If you have recompiled your kernel but not the modules, you may have
>failed dependencies and your modules may not load right. If you use SuSE
>supplied kernels and modules, then dependency problems are less likely.

I haven't recompiled - this is a plain Yast install of the 2.2.14 kernel
as per 6.4, going through the sound card configuration. The kids used
Yast 2 to install theirs under supervision (well they like the moving
penguin...) and the results with respect to sound configuration were the
same. All are using SuSE kernels and modules because I haven't gotten
configured yet to start any tinkering with the system...

>
>Right now I'm using  the ALSA drivers, and these are what it loads:
>
[list]
>
>From karen's email, it seems that that is what she is using, because
>when your con't use ALSA, then oinly es1371 and soundcore are loaded.

I haven't run any form of ALSA configuration as part of the install - do
you mean I may have some sort of conflict going on?

>
>Using dd and piping doesn't give good results, that may be the reason
>her recordings are bad quality.

perhaps - and krecord presumably has some amplification/whatever built
into it. However I so should the ViaVoice speech engine which I have
used extensively under Windows and on other Linux boxes. I doubt there
is something intrinsically wrong with the input to the engine itself but
I will check out any possible configuration problems further. 

However the factor which seemed to make the difference when I *did* have
everything working was inserting that 'soundlow' module. I did this
because I found a bit in the SuSE support database emphasising the
importance of the sound, soundcore and soundlow modules and found that
it was missing, just as sound had been. Reboot meant reloading those
modules and it hasn't worked since.

>
>Right now I just used grecord and gmix from the Helix package. I
>recorded my voice only after I disabled the window manager and desktop
>sounds.
>
I'll try them and see what happens, although it is really the voice
engine I need to get the microphone working with. If they work with
current set up perhaps I need to revisit the voice engine itself but
that is one thing which hasn't been touched since install. So if the
problem is a change there, I am mystified as to why. 

If I get no joy with current set up quickly I'll try running the ALSA
configuration. I have also had the OSS system suggested but I prefer to
stay open source where possible. However I also have to get something
running fairly quickly so although I had it working once I should really
be looking at other options I guess.

regards,


-- 
Karen Hunter-Jones                          karen@xxxxxxxxxx 
 

-- 
To unsubscribe send e-mail to suse-linux-e-unsubscribe@xxxxxxxx
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx             
Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/