| View previous topic :: View next topic |
| Author |
Message |
scawa
Apprentice
Joined: 11 Feb 2003
Posts: 178
Location: Villa Rica, Georgia
|
 Posted: Tue Feb 27, 2007 7:58 pm Post subject: [SOLVED] alsa-driver emerge problem |
 |
|
When I
| Code: | | #emerge alsa-driver |
I get the following problem:
| Code: | * Checking for suitable kernel configuration options...
* ALSA is already compiled into the kernel.
* Please check to make sure these options are set correctly.
* Failure to do so may cause unexpected problems.
* Once you have satisfied these options, please try merging
* this package again.
!!! ERROR: media-sound/alsa-driver-1.0.14_rc1 failed.
Call stack:
ebuild.sh, line 1630: Called dyn_setup
ebuild.sh, line 702: Called qa_call 'pkg_setup'
ebuild.sh, line 38: Called pkg_setup
alsa-driver-1.0.14_rc1.ebuild, line 91: Called linux-mod_pkg_setup
linux-mod.eclass, line 458: Called linux-info_pkg_setup
linux-info.eclass, line 572: Called check_extra_config
linux-info.eclass, line 471: Called die
!!! Incorrect kernel configuration options
!!! If you need support, post the topmost build error, and the call stack if relevant.
!!! A complete build log is located at '/var/tmp/portage/media-sound/alsa-driver-1.0.14_rc1/temp/build.log'.
|
even though I have done several things to preclude this.
I have recompiled my gentoo-sources removing the alsa use flag:
| Code: | | #USE="-alsa" emerge gentoo-sources |
I run genkernel and ensure that the sound configuration is as follows:
| Code: | Device Drivers --->
Sound --->
<M> Sound card support
Advanced Linux Sound Architecture --->
<M> Advanced Linux Sound Architecture
<M> Sequencer support
< > Sequencer dummy client
<M> OSS Mixer API
<M> OSS PCM (digital audio) API
[*] OSS PCM (digital audio) API - Include plugin system
[*] OSS Sequencer API
<M> RTC Timer support
[*] Use RTC as default sequencer timer
[ ] Dynamic device file minor numbers
[ ] Support old ALSA API
Open Sound System --->
.......
PCI devices --->
<M> Emu10k1 (SB Live!, Audigy, E-mu APS) |
My sound card from an lspci call is
| Code: | 02:01.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 0a)
|
My /etc/make.conf file has the following USE flags set and uses the correct devices:
| Code: | USE="-gtk -gnome"
USE="${USE} X xorg opengl png truetype xscreensaver"
USE="${USE} qt3 qt4 kde -arts"
USE="${USE} alsa dvd cdr midi"
USE="${USE} ipv6 nls nptl cups"
USE="${USE} perl python fortran php ruby sql cvs"
USE="${USE} java nsplugin source examples"
INPUT_DEVICES="keyboard mouse"
VIDEO_CARDS="nvidia"
ALSA_CARDS="emu10k1" |
(I saw the above use of the ${USE} statement in another post and it helps keep my USE flags grouped. Works correctly.)
I reboot my system to ensure that the kernel is the newest compiled kernel.
Does anyone have any ideas where I can look further?
_________________
Boredom is a personal Defect
-- Lamar Stephens
Last edited by scawa on Fri Mar 02, 2007 6:09 pm; edited 1 time in total |
|
| Back to top |
|
 |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54420
Location: 56N 3W
|
| Posted: Tue Feb 27, 2007 10:30 pm Post subject: |
|
|
scawa,
There are no USE flags that affect the kernel code and you should not apply USE on the command line anyway.
Portage will not know about it. Read and use /etc/portage/package.use for per packages settings.
You still have ALSA in your kernel. | Code: | Device Drivers --->
Sound --->
<M> Sound card support |
is the only sound setting you should use in the kernel if you wish to use alsa-drivers.
With an emu10k1 based card, I would recommend the kernel provided alsa. The emu10k1 is a stable well supported chip.
You will have less problems with the in kernel support.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
scawa
Apprentice
Joined: 11 Feb 2003
Posts: 178
Location: Villa Rica, Georgia
|
| Posted: Wed Feb 28, 2007 12:38 am Post subject: |
|
|
I was following the Gentoo Documentation on ASLA set up Gentoo Linux ALSA Guide that suggests
ALSA be set up as modules.
I don't understand how I can have all the features set up as Modules using the "M" option and still
have ALSA compiled into the Kernel.
Are you saying that I should have the
| Code: |
Device Drivers --->
Sound --->
<*> Sound Card Support
|
Enabled for "in kernel" use - using the "*". Then, should all the others be set up as modules using the "M" option?
There was a time way way back when I had this whole thing set up under kernel 2.4 but now it's all messed up.
Thanks for the help. I guess like most people who use Gentoo, the reason I'm using it (besides it screams on my machine) is I like to understand what's going on under the hood.[/url]
_________________
Boredom is a personal Defect
-- Lamar Stephens |
|
| Back to top |
|
|
ecks
n00b
Joined: 27 Feb 2007
Posts: 64
|
| Posted: Wed Feb 28, 2007 4:50 am Post subject: |
|
|
| Quote: | You still have ALSA in your kernel.
Code:
Device Drivers --->
Sound --->
<M> Sound card support
is the only sound setting you should use in the kernel if you wish to use alsa-drivers. |
Thank you, this is exactly what I was not understanding how to do, I thought I was supposed to have Sound card support with the <*> option, since it wasn't very clear in the guide. It said that when you `grep SOUND .config` you should get CONFIG_SOUND=y, which only works with the * option. With m set, the output would be CONFIG_SOUND=m instead. I hope that is changed in the future for those just starting out and not knowing their way around too well. For the poster above, if you emerge alsa-driver, you dont need to include ALSA in your kernel, so as was mentioned above only set Sound card support to <M> and leave everything else blank. So far so good, but now when I try to play something with aplay, I get a bunch of static from my speakers, and I don't even have /dev/dsp anymore! I am using intel8x0 driver, can anyone help me where I should look next?
UPDATE: I tried using mpg321 and it plays files, but mpg123 does not. I still don't have /dev/dsp, do I need it? Firefox-bin works with flash too, by the way. |
|
| Back to top |
|
|
big
Tux's lil' helper
Joined: 18 Jan 2007
Posts: 87
|
| Posted: Wed Feb 28, 2007 5:52 am Post subject: |
|
|
According to the guide,if you want to emerge alsa-driver,you should check CONFIG_SOUND,CONFIG_SOUND_PRIME and CONFIG_SND before.Do as the guide says will enable alsa support in your kernel either directly into the kernel or as a module:
| Code: | Sound --->
<M> Sound card support
Advanced Linux Sound Architecture --->
<M> Advanced Linux Sound Architecture
<M> Sequencer support
< > Sequencer dummy client
<M> OSS Mixer API ... |
If we want to meet the needs of "emerge alsa-driver" mentioned in the guide,the configuration should be:
| Code: | Sound --->
<M> Sound card support ------------------choose <Y> to make CONFIG_SOUND=y or it will be CONFIG_SOUND=M
Advanced Linux Sound Architecture --->
<> Advanced Linux Sound Architecture-----------------------just leave it blank to make "CONFIG_SND is not set |
I always built alsa-support into the kernel,so i just emerge alsa-utils and execute alsaconf to config my sound card.Luckly,it is really nice. 
Sorry for my poor English, did I make myself clear?
_________________
be big,no bug |
|
| Back to top |
|
|
scawa
Apprentice
Joined: 11 Feb 2003
Posts: 178
Location: Villa Rica, Georgia
|
| Posted: Wed Feb 28, 2007 1:36 pm Post subject: |
|
|
I did all this... emerged it in kernel etc etc and am STILL not getting sound.
When alsasound loads, I get no errors... etc etc
I have no problem with sound when I run a SuSE linux setup....
I look through the forums and the ALSA guide and How-to's and get conflicting confusing information....
I love Gentoo, but I wish this were easier.
And I didn't get an answer to my question on how, when I compiled everything like modules that I STILL have alsa compiled into my kernel?
_________________
Boredom is a personal Defect
-- Lamar Stephens |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54420
Location: 56N 3W
|
| Posted: Wed Feb 28, 2007 11:01 pm Post subject: |
|
|
scawa,
Compiled into your your kenel can me two things, you have alsa settings a as <*>, so the code goes into the kernel file in /boot or you have the alsa settings as <M>, so its loadable modules for your kernel. emerge alsa-drives detects this and fails with an error as its always a bad idea to have two drivers for the same hardware item loaded at the same time.
If you have rebuilt and reinstalled your kernel in line with my post above and alsa-drive still will not build, I suspect you have a problem either with your /usr/src/linux symbolic link or your kernel install which may well result in you not running the kernel you think you are.
What does show?
It tells you the running kernel version and compile date/time, does that tie in with what you expect ?
For your emu10k1, I would use the kernel provided ALSA.
With 2.4 kernels, the in kernel ALSA often failed but thats fixed in 2.6
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
scawa
Apprentice
Joined: 11 Feb 2003
Posts: 178
Location: Villa Rica, Georgia
|
| Posted: Wed Feb 28, 2007 11:23 pm Post subject: |
|
|
I really appreciate you taking the time to explain it to me.
I recompiled the kernel and compiled alsa in kernel with the "<*>" option. I got Amarok working beautifully, but couldn't understand why I couldn't get KDE sounds.
After searching the forums and posts I found a post on KDE - No Sound. This had a discussion on how to get rid of aRTS, which I did. I used the sox sound player. But I still had no sound.
I kept getting a message in the KDE logs that sox it couldn't decode the format "ogg". Well, I searched the forum posts for that. And found several posts on the xine-lib and what USE flags to set to get them to decode the proper sound formats. So, I set those USE flags (see the above post) and did an
| Code: | | emerge --newuse world |
which recompiled the necessary ebuilds with the correct flags.
Low and behold when I restarted my KDE session, I had KDE sounds... my Amarok player plays beautiful music and all is now right with the world .
Thank you for your help. It might be nice to have all of these ideas distilled into a how-to or maybe as an addendum to the ALSA sound configuration Docs so others can use them. My expertise isn't in this area, but would be happy to help.
_________________
Boredom is a personal Defect
-- Lamar Stephens |
|
| Back to top |
|
|
d2_racing
Bodhisattva
Joined: 25 Apr 2005
Posts: 13047
Location: Ste-Foy,Canada
|
| Posted: Thu Mar 01, 2007 2:27 am Post subject: |
|
|
Can you edit your first post and add [SOLVED] in the title plz 
Great post by the way.
It's the first time that a look at the alsa-driver not builtin the kernel.
Thank you for the information |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Multimedia
