[sf-lug] sf-lug Digest, Vol 5, Issue 20

[John Lowry]

Oh, yes, sorry. All of those commands were meant to come as root. Also, the
lack of a dsp device is a bit troubling, can anyone else help us out here on
this issue? I know you can mknod but not sure what he should do beyond
that.
Here is what I would try next, again as root:

modprobe snd-sb16
modprobe snd-pcm-oss
modprobe snd-mixer-oss
modprobe snd-seq-oss


The semicolons were a way of separating the commands, while hitting enter
only once. You can also run them one at a time. I am not sure, but these
might make the dsp device in the /dev directory. Anyone who has more
experience at this car to help us out? I am still learning and can use some
guidance here as well.

> On 4/20/06, Alex Kleider <a_kleider at yahoo.com> wrote:
> > First, thankyou very much for the help I'm getting;
> > Here's what I can report so far-
> > 1. I tried the modinfo soundcore command which went unrecognized until
> > I   got the  bright idea of trying it as Root user with the  following
> > result:
> > [root at localhost alex]# modinfo soundcore
> > filename:       /lib/modules/2.6.8.1-12mdk/kernel/sound/soundcore.ko.gz
> > description:    Core sound module
> > author:         Alan Cox
> > license:        GPL
> > alias:          char-major-14-*
> > vermagic:       2.6.8.1-12mdk 686 gcc-3.4
> > depends:
> >
>  > the alsaconfig command is unrecognized  even if comming from root:
> > [root at localhost alex]# alsaconf
> > bash: alsaconf: command not found
> > [root at localhost alex]#
> >
> > Another clue is that at  boot I get the  following message:
> > Sound server informational message:
> > Error while initializing the sound driver:
> > device  /dev/dsp can't be  oopened (no such file or directory)
> > The sound server will continue using the null output device.
> >
> > in fact it's true: there is no dsp file on the /dev directory.
> >
> > I'm a little timid about typing:
> >
> > modprobe snd-sb16;modprobe snd-pcm-oss;modprobe snd-mixer-oss;modprobe
>  > snd-seq-oss
> >
> > is  this literally what I should type? I've not seen terminal commands
> > contain semi-colons.
> > I'll do it with a little reassurance and encouragement!
> >
> > Thanks, John (and to Davide who has been sending me some help as well.)
> >
> > I'll keep at this for a while but am also in the process of following
> > Davide's advice and burning a Kbuntu live CD to see if I might want to
> > switch from Mand..linux.
> >
> >
>  >
> >
> > alex at kleider.net
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam?  Yahoo! Mail has the best spam protection around
> > http://mail.yahoo.com
> >
> > _______________________________________________
> > sf-lug mailing list
> > sf-lug at linuxmafia.com
> > http://linuxmafia.com/mailman/listinfo/sf-lug
> >
>
>
>
>
> --
>
> John Lowry
>
>



--
John Lowry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://linuxmafia.com/pipermail/sf-lug/attachments/20060423/a97f34fb/attachment.html>