Hi,

I have this PC with a VIA sound chip with Mandrake 9.1. My card seems to be detected but I am not getting sound out.

Here are the parameters I could dug up by searching on the various tool:

My sound server is set up on auto detection

When I tried to change something in there I got this message back: Can't set real-time scheduling priority. You need to run arts wrapper as root or set vid root (anyone knows what this relates to or what this would mean?)

When I go to info system in the PCI section I got:

OO:11:5 MULTIMEDIA
AUDIO CONTROLER: VIA TECHNOLOGIES, INC.
VT8233 AC97 AUDIO CONTROLER (REV(5C)
SUBSYSTEM: VIA TECH, INC,
UNKNOWN DEVICE 416)
FLAGS: MEDIUM DEVSEL, IRQ5
I/O PORTS AT E000 (SIZE:256)
CAPABILITIESAVAILABLE ONLY TO ROOT)

IN THE MODULE CONFIGURATION OF SOUND:

SOUNDDRIVERS:3.8.1A-98706(ALSA VO.9.0RC8 MEULATION CODE)
KERNEL: LINUX LOCALHOST 2.4.21-0.13MDK#1 FRI MAR 14 15:08
CONFIG OPTION: 0

INSTALLED DRIVER:
TYPE 10: ALSA EMULATION

CARD CONFIG:
VIA 8235 AT 0xe000, IRQ 5

AUDIO DEVICES:
0: VIA 8235 (DUPLEX)
SYNTH - NOT ENABLED
MIDI - NOT ENABLED
TIMES:
7:SYSTEM TIMES
MIXERS:
0:VIA TECHNOLOGIES VIA1612A


I am too unexperienced with Linux to fully understand this information and cannot tell if the driver is really install or not.

Help!!

Cheers!

hmm, don't know a sausage about your card. But its pci.

try installing off the cds "sndconfig" and run it by opening a terminal typing su then when prompted your password then sndconfig. There will a a long pause, for me feels like 1.5 mins while it probes my pci card and then if correctly finds it gives options to run a sample sound file.

You will need to have sound turned on In mdk control Centre - Services.

If it does not find your card correctly, and you have yet to get sound, choose the option to not run a sample and it gives you a list of card manufacturers. Hopefully you will find one that will work. Sometimes selecting soundblaster works as most try to emulate its functions.

Hi,

I checked these services, the sound is activated, starts up on bootup. I installed soud config and upon detection it tells me the card is detected but is not currently managed..

Do you know how to solve that?


cheers!

This may not be related, but Mandrake 9.1 has always given me sound problems. I've had this problems on 2 different computer and with 3 different sound cards. In all cases the soundcard worked fine and was detected properly, Mandrake would simply boot up with the sound muted by default. From what I gather, this is a widespread problem.

If this is the problem, the fix is simple: Try running "aumix" (either in a terminal window or via the "Run Command" dialog in KDE/GNOME.) Set the sound to full and see if that works.

If it does, you'll probably find that everytime you boot up the sound is muted again. If so I can tell you how to write a script that will unmute the sound everytime you logon to KDE.

Cheers,
Tim

umm did you have a go and trying different manufacturers thru sndconfig? To get the list I cancel the request to run a sample test file. Can you tell me exactly what you do if you can not bring up this list, If you choose my suggestion

found this
http://www.alsa-project.org/~goemon/

via 8235 is not there but that does not mean you can't try the others

I have a similar problem. I instaslled mandrake 9.2 and the sound card is detected (via vt8233/ac97 but not working. I downloaded the latest mandrake 9.2 rpm driver from viaarena. The rpm install failed. I tried a non rpm install but have got stuck. From nautilus it looks like I've got the unpacked src in usr//RPM/SOURCES/viaudiocombo-2.3. I can see these files. install.sh, makefile, viasound, viaudio_interface.c and viaudio_regop.o
Doubleclicking install doesnt seem to work (although it offers you to run in tereminal) and when I try to run it in terminal by command line it says file not found.
Can you advise me what to do now?
I have a gigabyte GA7VA with built in vt8233 sound and athlon xp 2400 .
thanks
Mel

My problem was simply that the settings would go back to mute every time I booted - Hoopyfrood if you happen to come back to this thread yes I would really appreciate knowing how to create a script that would handle that !


hmnk - if I were you I would try to install an other sound card - I found this super cool program called Synaptic which makes dealing with install and uninstall really easy

Cheers!

ok, well the suggestion was to run aumix, you could also try kmix and save the settings when you are happy with them

They hopefully will create a config file in you home directory. However, we were running sndconfig in ROOT mode so its aumix or kmix etc config will not be in the user account.

Try logging out and logging in as a normal user, then run aumix / kmix etc and see if you have a config file?

hope it works.

BTW, i am now playing with slackware, and ALSA works for me altho it uses a lot more modules.

It above or others can not help try a search on alsa.
heres the main site for your card notice if you do scroll down you get some posts on mdk
http://www.alsa-project.org/alsa-doc...module=via82xx

b4 getting excited by this, if alsa is the way you want to go, have a look at the command INSMOD in lower case and try
insmod snd-via82xx OR if that fails insmod via82xx and do this in a terminal and in su mode. I don't have your card so have no idea if it works

Hi,

ok great - I am away from the machine at this moment - but these are great tips - this site is excellent too

cheers!

Hey WhiteTornado,

Since updating to MDK 9.2, the problem pretty much cleared itself up. Let's see if I can recall what I did to work around the problem in 9.1.

1) Open Aumix, set the mixer prefs as you like.
2) Then File-->Save To, and save the .aumixrc where ever. Mine was just /home/user/
3) Create a new text file called aumix.sh. In it place the command "aumix -f /home/user/.aumixrc" (without the quotes, obviously)
4) Save/Copy this file to the /home/user/.kde/Autostart/ directory

Everytime KDE boots up, the mixer settings will be set to the default (mute). However, during the KDE splash it'll execute everything in the autostart directory, and the script will direct Aumix to load the settings as they were saved to your local home directory. As Aumix is a console command (as well as a GUI), this should happen with no output onto the screen. ie, it's completely transperent. The only sideeffect is that the first few beats of the default KDE startup sound are cut off, but otherwise sound levels will be restored to the preset condition in the /home/user/.aumixrc file!

Hope this helps out!
Tim

Hi Tim,

Hey man, this is really cool, thanks - I will do just that, boy this will be a relief!

Cheers!