-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Saturday 13 December 2003 10:35 am, Langsley T Russell wrote: > Hi again Charlie. > > You said: > > I thought that was fixed, or have I confused this thread with another? > > What sound card (on-board, PCI card???) chip-set? Do you have aumix > > installed, if > > not I recommend you do so and post the output of > > > > aumix -q > > OK, I installed aumix and below is the output resulting from aumix -q. > > vol 64, 64 > pcm 64, 64 > speaker 64, 64 > line 64, 64, R > mic 64, 64, P > cd 64, 64, P > igain 64, 64, P > line1 64, 64, P > phin 64, 64, P > phout 64, 64 > video 64, 64, P > > I hope it means something to you because it sure doesn't to me. ;~)
So shoot me, I prefer plain text configuration files. Besides that was easier to copy and paste than a lot of individual displays from a GUI wasn't it? Smaller than a screen shot too. (-; Those are the volume levels set for your sound system. The next thing you need to do is open a terminal, become super user and run the command drakxservices. Be sure sound is set to start at boot as well as alsa if that's what you're using. Just scroll down the list and find the services set to start at boot. If those two aren't in state "running" click the relevant Start buttons to activate them. Anything you aren't sure of just click the info button. After you've done that close the services by clicking OK and when you are back at the command prompt run the draksound command. We shall see what results from clicking the trouble shooting button. Follow the instructions displayed. Post any interesting messages you see in the terminal or any problems or errors and warnings. We'll try different alternatives if we can't make the setup work as it is now. Later. (-: The list needs to know what driver your sound system is currently set to use and whether you are offered any alternatives. The output of the commands you run as suggested in the trouble shooting dialogue. Assuming of course this doesn't result in having sound working. Even if it does you'll need to keep a text file of what you did, what you had to do, and the result of any aggravation from well meaning idiots like me. <g> If you don't document the steps and solutions and how you achieved the results Anne Wilson will string us both up. You have to post your trials and tribulations and their resolution on the Community Wiki. http://twiki.mdklinuxfaq.org That's the price of admission these days. lol > I'm running a âSound Blaster AudioPCI64V/AudioPCI128 That's the way it > is listed by HardDrake in Mandrake Control Center, which I believe is > reasonably accurate. It is an old PCI card from a previous box. > > Thanks again. > > LTR }}:{( > [EMAIL PROTECTED] Hang in there Langsley. I still say you can do this. Charlie - -- Edmonton,AB,Canada User #244963 at http://counter.li.org Mandrake Linux release 9.2 (FiveStar) for i586 kernel 2.4.22-21mdk 10:59:45 up 1 day, 19:32, 1 user, load average: 0.15, 0.27, 0.28 It's always darkest just before the lights go out. -- Alex Clark -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/21xJZqvqlrLPr5YRAtEuAKCAi8066kGQK6ofxUusEALtel7e5gCgolFN cD5CyQltdNdUlzkfUVWQsRs= =DG7S -----END PGP SIGNATURE-----
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
