Bloody hell man
cant even get on the alsa webpage..

modprobe does not work??/ :S :'( . ive had linux for 5 days now and im getting upset with it now!

how can i make modprobe work?

sites up... what did the kernel report when you modprobed the alsa module?

here's the alsa page that tells specifics for the 8233
http://www.alsa-project.org/alsa-doc...module=via82xx

the sites down again, ive worked out how how to do mod-probe tho

also in the install instructions it says:

6) Edit your /etc/modules.conf
i dont get what im supose to do..

/sbin/modprobe (but what do i put here)
whats the alsa module called :S?

ta

the module is called snd-[sound-card-specific bit here]

yes but i dont know what to put

most often the name of the non-alsa module. example:
emu10k1 is the name of the non-alsa module for the
sound blaster series. snd-emu10k1 is the name of the
alsa module.

HELP!

linuxsoundprob... hang on... I'll take a look at the alsa page when I get home and we'll get this all sorted out... figure in about 5 hours?

this link might be of interest to you:

http://www.newtolinux.org.uk/forum/i...y;threadid=200

i too went through these same steps this week (including the alsa site being down!)

ok, compile and install with this command:
./configure --with-cards=via82xx --with-sequencer=yes;make;make install

then install alsa-lib with this
./configure;make;make install

then install alsa-utils with this
./configure;make;make install

then insert the newly built modules into the kernel like this
modprobe snd-via82xx;modprobe snd-pcm-oss;modprobe snd-mixer-oss;modprobe snd-seq-oss

(note: make sure that the soundcore module is loaded before loading the alsa modules)

let me know how it goes ...

what do i have do edit in modules.conf and how to i make sure the thingy is loaded?

hmm... alsa site still down (cause if it weren't, the instructions
would be there for you to follow)... quite a shaky site.. or just
very heavily used by too many causing it to fold.

linuxsoundprob, don't worry about modules.conf just yet... for now execute the modprobe commands... oh! and I must make a correction / clarification, in my earlier post that stated execute 'modprobe snd-via82xx'... the 'xx' portion is specific to your chipset... which I think you said is an 8233 right? so you would execute 'modprobe snd-via8233'.

if all these modprobes go off without a hitch then you're in business. To see if their loaded / what's loaded execute 'lsmod'.

there are 4 'mod'-type commands
modprobe -- insert a module into kernel
insmod -- insert a module into kernel (called by modprobe)
lsmod -- get a listing (ls ?) of modules in kernel
rmmod -- remove a module from kernel

all of them can / must be executed by root... not just by any user. I'll have more info on modules.conf here in a bit... I've never used it though so it can't be that important. For the most part I think that it is responsible for passing configuration options to your modules but I could be wrong. let me know how the probing goes. hehe... that sounds funny.

P.S. you can learn more about modules.conf by typing 'man modules.conf'. this will open the manual page for modules.conf... if one is installed on your system.