Wish me luck on my venture to fix my Linux partition...

[magomago]

...no sound no modem....That is what I'm trying to fix...I'll read the damn thingies (I have a Lucent Winmodena nad a Aureal Vortex Chipset)


If i encounter problems I will sure as hell ask for help...

plus one thing...why is m8.1 so slow for me! I have a 500mhz processor with 320 megs of ram and when i click on the linux version of "my explorer" it takes line 10-15 seconds to load....

 

[magomago]

Help men! We are taking a hard beating on the front!


Okay okay...after 1 hour I've come out Unsuccessful in making my Vortex 1 chip work. here are the instuction i got from aureal.linux.com in the msg boards at sourceforge

By: drfalkyn ( Patrick Raphael )
RE: Problem with Aureal 8830&Mandrake 8.1 fix
2001-12-16 02:26
Got it working! At least XMMS under Gnome. This is what i did:

1) These directions assume you have pretty much a default install of Mandrake 8.1. If you have something messed up like not having the kernel sound module, make sure you do all that first (look elsewhere, e.g. Linux-SOUND-HOWTO, but follow step 2 first if you don't have kernel source or else your system will get really messed up, Mandrake doesn't like the plain-vanilla source)

2) You need to download the package kernel-source-2.4.8-26mdk.i586.rpm. See http://www.linux-mandrake.com/en/ftp.php3 for a list of mirrors.

3) Install the package by typing

rpm -ivh --nodeps kernel-source-2.4.8-26mdk.i586.rpm.

If you don't use --nodeps, it will complain that you don't have ncurses-devel, which you don't need for this (and I think you only need for make menuconfig) Now you should have a directory /usr/src/linux-2.4.8
4) Make sure you have the aureal source package unzipped to a handy directory read to compile

5) Now its time to set up some links. Make sure you are root and type:

ln -s /usr/bin/lspci /sbin/lspci
mv /usr/include/linux /usr/include/linux-2.4.8mdk
ln -s /usr/src/linux-2.4.8/include/linux

6) Change to the directory where you have the aureal source code installed, and try:

make install-all

If that doesn't work you will need to find out what the soundcard is, whether its an Aureal 8830, 8820, or 8810. Check your sound card manufacturer for more info. The other option is to pull out the sound card and insepct the board for the chip type. If the above did not work for you, type

make <chip-name>

where <chip-name> is either au8830, au8820, or
au8810.

7) Now that you have the module compiled you need to load it into the kernel. Type

ls /lib/modules/linux-2.4.8-26mdk/drivers/sound

And there should be a module au88x0.o where x is either 3, 2 or 1. Now type

modprobe au88x0

substiting x for your chip

8) Test out the sound somehow, I tried it with XMMS and it worked.





By: drfalkyn ( Patrick Raphael )
RE: Problem with Aureal 8830&Mandrake 8.1 fix
2001-12-16 02:28
Oops, the last command on step 5 should read

ln -s /usr/src/linux-2.4.8/include/linux /usr/include/linux

all went well...except for this setp

ls /lib/modules/linux-2.4.8-26mdk/drivers/sound

There was no linux-2.4.8-26mdk folder, only linux-2.4.8 folder.

I said "whatever" and made the subsitute....I ran the command and I'm assuming it worked (no errors, but no screen flashing saying "good job!") because it didn't seem to have an error.

Then i loaded up XXXMS [whatever] in KDE b/c that is what I use (It seems easier to use)

It would load my mp3 and no sound would come out

I exited to Gnome and it wouldn't even play the file...it just gave an error of some srot.


I tried KDE once more, and then booted up windoze to ask for your help.

- So, waddya say all you Linux- Gurus

My Specs:
=500mhz k6-2
=Vortex 1 soundcard (Hi-val)
=320 megs of ram
=2 gigs parititoned to linux with ~8-900 megabytes free out of a possible 20 (If i can get my modem and sound working I'll increase it substancially...but till them...)
=Mandrake Linux 8.1


I'll give a cookie to whoever helps me out

 

[cleverhandle]

Ick, what a messy solution. Seems like there has to be a better way to do it. Would be nice if distros would stop custom tagging their kernels - I really don't see what purpose it serves. Anyway, if modprobe didn't cough up an error, I'm guessing it should be OK. Do an "lsmod" and see if the driver is listed there. If it is, then the kernel accepted it, which means your problem lies elsewhere. Check your mixer settings. Check permissions - /dev/mixer*, /dev/dsp*, /dev/audio* should be mode 666. Check your logs and/or switch to the console with ctrl-alt-f1 to see if there are helpful error messages.

I could be wrong - it's late, and that's a messy procedure - but I think the module part of the configuration is fine.

 

[magomago]

Is there an easier solution then? I'd try to start from the beginning if possible

 

[Nothinman]

Would be nice if distros would stop custom tagging their kernels - I really don't see what purpose it serves.

It serves the purpose of labeling them as non-standard. Most of them include patches not in the official kernel and if it just says linux-2.4.18 is it Linus' kernel or not? You can't tell easily.

type 'dmesg' and the end of that output will most likely say something about finding a sound card.
Run a mixer and check the volume levels.
Check the permissions on the /dev/dsp and /dev/mixer files.

 

[cleverhandle]

It serves the purpose of labeling them as non-standard. Most of them include patches not in the official kernel and if it just says linux-2.4.18 is it Linus' kernel or not? You can't tell easily.

I would think a big, bold-lettered README-MANDRAKE dropped into /usr/src/linux or even just /usr/src could describe which patches had been applied in a more detailed manner, and without causing versioning conflicts with modules. Anybody who needs to add custom kernel patches should reasonably be expected to look there.

 

[magomago]

type 'dmesg' and the end of that output will most likely say something about finding a sound card.
Run a mixer and check the volume levels.
Check the permissions on the /dev/dsp and /dev/mixer files. [/H}

Huh? Dmesg? In the console in which folder? Run a mixer? oy....

I'll keep searcing on the net and hope I can find an answer or someone here can help me out (even better if they have a vortex card)

All I can say is that when i build my new pc...i will make sure each part supports linux first

 

[cleverhandle]

I'll keep searching on the net and hope I can find an answer or someone here can help me out (even better if they have a vortex card)

Why should anyone spend time helping you if you won't take some initiative to help yourself? Nothinman said "type 'dmesg'". Did you even try typing dmesg? Anywhere? Or did you just throw your hands up in the air? Did you look around to see if maybe you had a program called mixer? Or maybe even go to a help program, and type "mixer" in the search box?

How's this? Open up a terminal, type "dmesg" without the quotes. It doesn't matter which folder you're in. You probably will have to be root, however. You can become "root" by typing "su" and then giving your root password when requested. Dmesg will give you a lot of output. If you stop to examine it, you may conclude that this is the very same stuff you see when the machine boots up - congratulations. Probably, your terminal program has a bar at the right called a scroll bar. Use it to scroll back through the output and look for some evidence of your sound card. It might say "Sound card found at..." or "Aureal Vortex" or maybe it will mention that module au8830. If you want to get really fancy, try "dmesg | less" - then you can use the PageUp key to move up a page in the output and the PageDown key to move down a page. Write down the stuff that dmesg says about the sound card and post it here. Or, if it says nothing about the sound card, tell us that.

Next up...

Check your mixer levels - this means: click the K/Foot/RedHat/Start/whatever button in the lower left corner of your screen. It will bring up a menu with lots of categories in it. One of them might be called something suggestive, like "Sound" or "Multimedia". Move your mouse to that entry - that should bring up a new menu. Perhaps there will an entry called "Mixer," "Sound Mixer," or "Volume Control". Perhaps your mixer is being tricky and using a funny name, or hiding in a different menu category. You might have to experiment. Yes I know... what a scary, uncertain world we live in. When you find this "mixer," open it by clicking on its icon. It will probably show you a bunch of little boxes that slide up and down. Those are "sliders" or "volume sliders." If they are all the way down, at the mark with a "0", then that audio channel will have... you guessed it, zero volume. Make sure your volume levels are not set to zero. There may also be a little box that says "mute" near the slider. Make sure that such a box is not checked or otherwise selected. Being "mute" is like having zero volume. This is like your stereo - you cannot hear it if the volume is zero.

Please - if I left anything out, let me know...

 

[magomago]

b]Why should anyone spend time helping you if you won't take some initiative to help yourself? Nothinman said "type 'dmesg'". Did you even try typing dmesg? Anywhere? Or did you just throw your hands up in the air? Did you look around to see if maybe you had a program called mixer? Or maybe even go to a help program, and type "mixer" in the search box?[/b


] Actually I had no idea where to type dmesg so i was scared to try it. Unlike many of you guys I'm not very proficeint in Linux. And I HAVE been reading up on it. I know that su [whatever it stands for] lets you enter as root, and the difference is that a regular user will have a $ while the root will have a #. I have been reading, but at a slower pace. I checked the Linux "Howtos" and tehre was no "compile kernel with sound". There was a compile kernel, but it seemed more in general. I also tried sound and searched the rest of the howtos with no result.

I really am trying, however I am not one who won't ask because I do not know everything in the world like some of you (including you cleverhandle ) I'll heed what you said and try that + a couple other things that I found (which were more responses to help posts on the aureal.linux.com sourceforge's forums)

And thank you VERY MUCH for trying to help me out and even offering to continue to help me if I can't get it working. /me runs off to boot up linux While other people don't care,

I really am trying to switch to linux. I'm trying to get my sound working first, then i'll move onto modem and finish it off with the printer (Linux recognizes my printer but when it boots up it spews out shiznit until i shut it off or until the ink runs out). If i can somehow acheive these three the only use of win2k for me will be counterstrike ]


But for me, it is a "1 step at a time deal"

 

[magomago]

Did it:

Demsg results:




au88xx: loading...
PCI: Found IRQ 11 for device 00:0a.0
au88xx: Found Vortex PCI device
au88xx: id=0x0001
au88xx: bar 0=0xf2000000
au88xx: irq=11
au88xx: mem(or n...i wrote it sloppily) 0x2000000-0xf203ffff in use
au88xx: add device, audio=3, mixer=0, midi=2



Hrm...by the looks of it perhaps I have some of it installed?


Sound Mixer Results

Sound Mixer has no "bars" or sliders to speak of. If I choose "New Mixer" or someting along those lines I have a box with "avalible mixers" and I have nothing to choose from

When I load up KDE Media Player i can load the song but it will not move in the time-thingy which means the song stalls or something




Hope this gives a clue as to what might be the problem

 

[cleverhandle]

Originally posted by: magomago

Hrm...by the looks of it perhaps I have some of it installed?

Yep, the driver looks to be installed fine. It strikes me as odd that it says "mixer=0", but maybe that's normal, too...

Sound Mixer has no "bars" or sliders to speak of. If I choose "New Mixer" or someting along those lines I have a box with "avalible mixers" and I have nothing to choose from. When I load up KDE Media Player i can load the song but it will not move in the time-thingy which means the song stalls or something.

Hmm... I don't have KDE installed anywhere to check it out right now, but I'm guessing this just means that the Sound Mixer can't access the mixer device, not that one doesn't exist.

Try the mixer and media player again as root - so if you have a graphical login screen, go back to that so that the whole X-session has root privileges. If you use a text login, just login as root, and do a startx. If the sound works as root, then we'll know it's a permission issue. If not, then it's something else.

Hope this gives a clue as to what might be the problem

It's definitely a lot more to work with.

 

[cleverhandle]

Actually I had no idea where to type dmesg so i was scared to try it.

Why? It's not gonna make your computer explode. About the only thing in Linux that could possibly damage hardware is a really bad X configuration. The very, very, very worst thing that could happen is that you hose your disk, and I know you have backups, right? You can trust that nobody on the forum would suggest running a potentially dangerous command without being very, very specific about how to do it.

I'm honestly trying to help - the only way to understand Linux/Unix is to jump off the cliff and experiment with things you don't understand. If that's not your style, then you will not like Linux.

I really am trying to switch to linux. I'm trying to get my sound working first, then i'll move onto modem and finish it off with the printer (Linux recognizes my printer but when it boots up it spews out shiznit until i shut it off or until the ink runs out).

Sounds good - that's pretty much increasing order of difficulty.

If i can somehow acheive these three the only use of win2k for me will be counterstrike.

Why? Pay $5 a month for WineX - all Half-Life versions run perfectly well with Winex 2.2.

 

[magomago]

Yes sir! Yahoo! Somehow the driver got installed (I thought I f'ed up my system too with trying all sorts of methods!)


I'm assuming you use Gnome...actually scratch that, you seem to know what you talk about so i'll say you don't even use mandrake and just use slackware


I'll try it in Gnome as my username and in root in both KDE and Gnome


back in 10 minutes

 

[magomago]

I'm back with unpromising results.


As root in KDE it still had absolutely nothing in the sound mixer.


As root in Gnome I ran Audio Mixer

Here is the error:

Unable to open audio devic. Please check that you have permission to open /dev/mixer and that sound upport is compiled into the kernel


So now I didn't install it??

 

[cleverhandle]

Hmm... this is getting a little weird. OK, let's do some things to check if this module is actually loading correctly first of all. As root, do

lsmod

That lists all the modules currently loaded. au8820 should be listed. If not, do a

modprobe au8820

That part should be OK, since it showed up in the dmesg output before. Now what? Hmm... let's make sure we know what mixer devices we have and where they are. That module is pretty old - maybe it's expecting something in a different place. Do

updatedb

This update your file location database and could take a while. When it's done,

locate mixer | grep dev

That should list one or mixer devices. What are they?

 

[magomago]

I stopped at modprobe 8820

I was supposed to do that in different instructions and all i get is "Module not loaded" or something along those lines

 

[cleverhandle]

Huh??? Then how did we get the dmesg output before? Now I'm grasping... maybe the driver install script loaded the module correctly, but it's not being reloaded correctly when you reboot. First off, let's figure out what the heck we were loading before. Do:

locate au88 | grep lib

That should list the au88?0.o files somewhere in the /lib/modules/ directory. cd to the directory where au8820.o is located. Do

modprobe soundcore (make sure the core sound module is loaded, if it wasn't already)
insmod ./au8820.o (insert the module manually)

What do we get from that?

 

[magomago]

Get this":


I went back and ran the other commands and here is what I got:


lsmod

Module Size Used By
Au8820 116448 1
soundcore 4208 5 [au8820]


updatedb worked fine

then


locate mixer | grep dev

/lib/dev-state/sound/mixer


I'll go try the new stuff and see if this helps you at all. brb

 

[magomago]

I went ahead and did the next step of instructions anyways for info purposes":


locate au88 | grep lib

/lib/modules/2.4.8-25mdk/misc/au8820.o

modprobe soundcore

Nothing happened, I'm assuming it worked

insmod ./au8820.o

Initially it sai No such file/directory but then i replaced the ./ with /lib/modules/2.4.8-25mdk/misc/ and then it said someting to the effect of

au8820.o already loaded <- not exact wording but something like that.


So...have i perplexed you enough?

 

[magomago]

Its 10:45 right now. I'll wait till 11 and hten go to bed. I'll check it tomorrow if there is no reply and hope maybe its something really trivial.

Thanks!

In the mean time i'll keep searching sites for answers

 

[manly]

Originally posted by: cleverhandle

That should list the au88?0.o files somewhere in the /lib/modules/ directory. cd to the directory where au8820.o is located. Do

modprobe soundcore (make sure the core sound module is loaded, if it wasn't already)
insmod ./au8820.o (insert the module manually)

In my limited experience, you can just load a single sound module (basically the "root" module) and it'll satisfy any additional module dependencies automatically.

Why would you insmod the file manually instead of modprobe module-name which is the convenient, sane wrapper?

The "raw" (i.e. CLI) kernel modules user interface is way too arcane for typical PC users. I like how SuSE wraps a pretty functional configuration GUI around it (YaST2 sound setup), and I would have assumed any other respectable commercial distro (targetting desktop users) would have done the same by now. I'll have to play w/ Mandrake 9.0 and RH 8.0 to see how far they've come along.

For starters, I think magomago should play with an up to date distro rather than Mandrake 8.1 if at all possible although I don't yet personally know how solid the new GCC 3.2 based distros are. If they have too many wrinkles, any of the previous releases would be a good choice (SuSE 8.0, Mandrake 8.2, Red Hat 7.3, et al).

Btw cleverhandle is better at diagnosing these issues and providing help than I am; I'm just trying to clarify w/ my two cents.

 

[cleverhandle]

I've got to go to work right now, so I don't have time to make a long post. But the long and the short of it is that you're probably screwed. From what I can tell, the module loads, but the mixer component isn't functional. Why not? Dunno... probably that the module is really old - it was barely tested on 2.4. Or it could be a custom Mandrake patch or something. I doubt that any recent distro would do a better job, either. Perhaps someone else will see something I don't, however. I'll post again later when I've got more time.

 

[TonyRic]

Check for the proper device path in the mixer app. Should (probably be) /dev/dsp or /dev/mixer. Also, check the permissions on /dev/dsp and make sure they are -rw-rw-rw- if not then as root issue the following command chmod 666 /dev/dsp (do a man chmod and it will explain the command).

Sounds like you are almost there. Keep us updated on your progress.

 

[Nothinman]

Alsa needs additional modules to drive the Open Sound System compatible devices (/dev/dsp, /dev/mixer, etc), it has to say somewhere in the docs what they're called.

 

[cleverhandle]

(At work, typing quickly...)

But the Aureal driver isn't an ALSA device. Drake 8.1 uses devfs, and the lack of a /dev/mixer or /dev/sound/mixer device device suggests to me that the mixer part of the module just isn't working correctly - if the mixer works on a hardware level, devfs should provide for it.

Gotta go, sorry...