Intel8x0 error message

[Nicholas.Walker]

[Sheepdogj15]

yes, if it's reported in dmesg, and amixer reports something other than "device not found" (not exact words ), then the Alsa driver is loaded. Therefore, the problem is in your windows manager(s).

oh yeah. and run alsamixer in the command line. this will open a gui-like mixer which you can use to set your volume levels. make sure your Master, Master Mono, and PCM volumes are unmuted and are turned up. (just don't turn PCM up all the way, on some systems that causes distortion!)

if alsamixer results in a "command not found" error, this means you have to emerge alsa-utils. then use alsamixer (alternatively, you could use amixer, but i like the UI for alsamixer better)


beyond that,i can't help too much. i know off hand that with kdebase, arts is a separate package and thus you probably have to emerge that itself. anything else, check teh Gentoo documentation, the documentation for the WM, or ask here.



Edit: Nick, i reread the output from amixer and i see something wrong:

[Sheepdogj15]

BTW, this is a general comment which might help you guys out: if you are using the alsa-driver package from portage, it breaks every time you recompile your kernel. i don't know why, something to do with modules. anyhoo, to fix it you will have to rerun "emerge alsa-driver" after every time you compile your kernel. it's a bit annoying, but it will save you neck-aches later on.

[donjuan]

Actually not every time you recompile your kernel. It's every time you switch kernel versions, even between releases of the same kernel, like from 2.6.11-r1 to 2.6.11-r2. The same thing happens with video card drivers. And at least with the ATI video card drivers it's pretty obvious, it says "failed to load module fglrx."
_________________
Command-line ACCEPT_KEYWORDS is considered harmful, use the package.* files.

The Stage 1 on 3 Install

[Morimando]

Actually it was I who proposed him to use ACCEPT_KEYWORDS, so to see if it has been a problem with xmms and also because xmms-alsa hadn't been marked stable till uhm yesterday i think.
So the keywords where merley to make sure a) xmms-alsa is pulled in and b) a compatible xmms is pulled in. I wonder why xmms-alsa is now marked stable but still gives an annoying error (doesn't stop because of that, but errors are annoying) as long as one doesn't use xmms-unstable.. well for me the unstable versions are all working, including xmms-alsa,xmms-vorbis and main xmms, so that's why i thought he should give it a try.
However the PCM should solve the problem as soon as Nicholas turns it on, i forgot to let him post the output of amixer in ICQ but well, it was late ^^
@WeirDave still got errors or solved it?

@rebuild of alsa-driver: Only if the kernel-version is different, but well then you also need nvidia and ati remerged
_________________
That young girl is one of the least benightedly unintelligent organic life forms it has been my profound lack of pleasure not to be able to avoid meeting.
-- Marvin

[Sheepdogj15]

a ha. it's no biggie. the ~x86 was out of the ordinary so for a bit it was my prime suspect.

strange, i've needed to emerge alsa-driver every time i changed my kernel. maybe my setup is moobarred? ah well.

[donjuan]

[Nicholas.Walker]

Nice it works now.

Seems compiling the drivers from the make menuconfig options did the trick. Thank you for all your help.

Nicholas

[Morimando]

Sure it wasn't the PCM-thing?
One more thing i discovered lately: One has to emerge the complete unstable XMMS branch to get the (marked as stable now!) xmms-alsa working. Else aclocal will keep giving errors and interrupting the compiling..maybe it's fixed when the next xmms is marked stable.
_________________
That young girl is one of the least benightedly unintelligent organic life forms it has been my profound lack of pleasure not to be able to avoid meeting.
-- Marvin

[WeirDave]

[Sheepdogj15]

excellent!

[Nicholas.Walker]

Yeah, the PCM did the trick as well.

Now sound works, but only in root. I can't use su -c "xine", says it can't open display 0.0

It complains on startup that it can't find "unlink" in GLOBAL

in my normal user account xmms still complains that it can't find the ALSA 1.2.0 driver and mpg123 won't run either.

When I reboot or shutdown it says error stopping xdm.

[Sheepdogj15]

[Morimando]

That "cant find unlink in GLOBAL" makes something tickle...
say does this error come from PAM?
If yes then this would be my approach (yes i know, it's not a real mature approach but its the only i have and it works for me)
ACCEPT_KEYWORDS="~x86" emerge pam
If it ain't pam that's giving you the error forget everything i wrote here for it might make your system fuzzy. I write that without knowing if it IS pam because i won't be here the next 3 days, and that way you know at least how i got that thing "solved".
Cheers
_________________
That young girl is one of the least benightedly unintelligent organic life forms it has been my profound lack of pleasure not to be able to avoid meeting.
-- Marvin

[blacknyx]

Ok this thread is OLD but it's worth a try, rather than posting a new one.
I'm on 2005.0 with a 2.6.11 r6 Kernel
Im trying to load my Alsa Emu10k1 sound
I followed the wiki gentoo guide which said to DEactivate all alsa sound in my kernel
and then install all alsa lib, utils, etc.
Which gives me the same exact error the post starter had.
So should I unmerge all of the alsa utils, libs, etc, add them as M to my kernel, and then edit it out in my alsasound config file?
Is that, as i understand it, how it should be for it to work?

[WeirDave]