At Mon, 1 Jul 2002 10:59:55 +0300,
Dr. Dan White <[EMAIL PROTECTED]> wrote:
> How do I put the modprobe snd-via823, alsamixer unmuting and esd
> commands in some start up script so each time I re boot all this
> happens automatically??
it's not via823 but via8233.
> >1. don't have double binaries for both 0.5.x and 0.9.0?
>
> I have the 0.5 driver form realtech sources in my /usr/src/ should I
> remove them.....or are you telling me to remove something
> else.....the actual installed stuff that was written when i
> configured and compiled the 0.5 real tek driver????????
the old driver modules must be removed.
the old library can stay, though.
>
> > for example, run "which aplay" and check the correct path
> > (e.g. /usr/bin/aplay).
>
> OK, that is fine, I get /usr/bin/aplay
>
> > then run "ldd /usr/bin/aplay" to check whether it's linked
> > with /usr/lib/libasound.so.2
>
> the first of several other lines I get:
> libasound.so.2 => /usr/lib/libasound.so.2 (0x4002e000)
>
> so I guess that is ok?
yes.
> >
> >2. removed old /etc/asound.conf?
>
> I have no /etc/asound.conf !!!!!!!!!!!!
ok, just asked in case you had it. never mind.
> >3. having correct /etc/modules.conf entries?
>
> I think my file might be ok, but I lack any mention of codec 97 in
> this file, which I think there possibly should be, looking at Mark's
> file???????
>
> here is my modules.conf followed my Mark's modules.conf. we have the
> same hardware, but there are big differences in our files....esp. the
> option line.....
>
> ........dans modules.conf
> alias eth0 eepro100
> alias parport_lowlevel parport_pc
> alias usb-controller usb-uhci
> # ALSA portion
> alias char-major-116 snd
> alias snd-card-0 snd-via8322
^^^^^^^^^^^ snd-via8233
> alias snd-card-1 snd-via8322
this line is not necessary.
> options snd-card-via8233 snd_id="Via8233" snd_index=0
it's ok.
> # OSS/Free portion
> alias char-major-14 soundcore
> alias sound-slot-0 snd-card-via8322
^^^^^^^^^^^^^^^^ snd-via8233 (without card-, too)
> alias sound-service-0-0 snd-mixer-oss
> alias sound-service-0-1 snd-seq-oss
> alias sound-service-0-3 snd-pcm-oss
> alias sound-service-0-8 snd-seq-oss
> alias sound-service-0-12 snd-pcm-oss
> alias char-major-10-179 xsvc
>
> ........marks modules.conf
> alias char-major-116 snd
> alias char-major-14 soundcore
> options snd snd_major=116 snd_cards_limit=1
>
> # ALSA portion
> alias snd-card-0 snd-via8233
> options snd-via8233 snd_index=0 snd_id="AC97"
> # OSS/Free portion
> alias sound-slot-0 snd-card-0
>
> # OSS/Free portion - card #0
> alias sound-service-0-0 snd-mixer-oss
> alias sound-service-0-1 snd-seq-oss
> alias sound-service-0-3 snd-pcm-oss
> alias sound-service-0-8 snd-seq-oss
> alias sound-service-0-12 snd-pcm-oss
>
>
> >
> >ok, now you can restart the new alsa system.
>
> how do I do that?
it depends on your system.
sorry, i forgot the detail of yours. if it's redhat-based one like
suse or mandrake, you can use alsasound init script installed from
alsa-driver package.
as root, run "/etc/init.d/alsasound restart"
the path might be different, depending on the system.
also, please make sure that all mixers are set up correctly,
especially check whether PCM is unmuted.
btw, about AC97: AC97 corresponds to only a mixer part of the sound
system. that's why you couldn't find a driver mentioning your ac97
chip. the heart of the sound system (in your case) is VIA8233
southbridge. that's the name of the driver.
ciao,
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Alsa-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-user
