View previous topic :: View next topic |
Author |
Message |
sverzel n00b
Joined: 26 Jan 2008 Posts: 5
|
Posted: Sat Jan 26, 2008 1:17 am Post subject: gentoo-sources-2.6.24 alsa-driver (1.0.14 & 1.0.15) fail |
|
|
After getting the new gentoo-sources and using the new kernel, media-sound/alsa-drivers fails to emerge (both 1.0.14 and 1.0.15).
Error log:
Code: |
make -C /usr/src/linux M=/var/tmp/portage/media-sound/alsa-driver-1.0.15/work/alsa-driver-1.0.15 O=/lib/modules/2.6.24-gentoo/build CPP="i686-pc-linux-gnu-gcc -E" CC="i686-pc-linux-gnu-gcc" modules
make[1]: Entering directory `/usr/src/linux-2.6.24-gentoo'
/usr/src/linux-2.6.24-gentoo/scripts/Makefile.build:46: *** CFLAGS was changed in "/var/tmp/portage/media-sound/alsa-driver-1.0.15/work/alsa-driver-1.0.15/acore/Makefile". Fix it to use EXTRA_CFLAGS. Stop.
make[3]: *** [/var/tmp/portage/media-sound/alsa-driver-1.0.15/work/alsa-driver-1.0.15/acore] Error 2
make[2]: *** [_module_/var/tmp/portage/media-sound/alsa-driver-1.0.15/work/alsa-driver-1.0.15] Error 2
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.24-gentoo'
make: *** [compile] Error 2
*
* ERROR: media-sound/alsa-driver-1.0.15 failed.
* Call stack:
* ebuild.sh, line 1701: Called dyn_compile
* ebuild.sh, line 1039: Called qa_call 'src_compile'
* ebuild.sh, line 44: Called src_compile
* alsa-driver-1.0.15.ebuild, line 143: Called die
* The specific snippet of code:
* emake LDFLAGS="$(raw-ldflags)" HOSTCC="$(tc-getBUILD_CC)" CC="$(tc-getCC)" || die "Make Failed"
* The die message:
* Make Failed
|
Anyone experiencing the same problem? Advice? |
|
Back to top |
|
|
gimpel Advocate
Joined: 15 Oct 2004 Posts: 2720 Location: Munich, Bavaria
|
Posted: Sat Jan 26, 2008 2:16 am Post subject: Re: gentoo-sources-2.6.24 alsa-driver (1.0.14 & 1.0.15) |
|
|
Use in-kernel alsa drivers. _________________ http://proaudio.tuxfamily.org/wiki - pro-audio software overlay
|
|
Back to top |
|
|
schachti Advocate
Joined: 28 Jul 2003 Posts: 3765 Location: Gifhorn, Germany
|
Posted: Sat Jan 26, 2008 8:07 am Post subject: Re: gentoo-sources-2.6.24 alsa-driver (1.0.14 & 1.0.15) |
|
|
gimpel wrote: | Use in-kernel alsa drivers. |
In some cases, this might be not a good idea...
I have the same problem here...
EDIT: There is already a bugreport on this. _________________ Never argue with an idiot. He brings you down to his level, then beats you with experience.
How-To: Daten verschlüsselt auf DVD speichern. |
|
Back to top |
|
|
michel7 Guru
Joined: 04 May 2006 Posts: 461 Location: localhost
|
Posted: Sat Jan 26, 2008 10:49 am Post subject: |
|
|
The same here, i dont like build-in alsa drivers. And media-sound/alsa-drivers fails to compile ... _________________ Software is like sex. It's better when it's free |
|
Back to top |
|
|
bunder Bodhisattva
Joined: 10 Apr 2004 Posts: 5934
|
Posted: Sat Jan 26, 2008 10:59 am Post subject: |
|
|
Moved from Portage & Programming to Kernel & Hardware. _________________
Neddyseagoon wrote: | The problem with leaving is that you can only do it once and it reduces your influence. |
banned from #gentoo since sept 2017 |
|
Back to top |
|
|
mantoo Tux's lil' helper
Joined: 08 Dec 2007 Posts: 98 Location: Germany
|
Posted: Sat Jan 26, 2008 11:14 am Post subject: |
|
|
i use the 999-version by unmasking in packages.mask and adding with "**" to packages.use,
really works fine; also recognized some optical improvements/changes in alsamixer
give it a try |
|
Back to top |
|
|
sverzel n00b
Joined: 26 Jan 2008 Posts: 5
|
Posted: Sat Jan 26, 2008 7:43 pm Post subject: Kernel driver |
|
|
To get around the problem I compiled alsa in the kernel and the driver as a module instead. Problem with alsa-driver persists. See bug, as linked by schachti: https://bugs.gentoo.org/show_bug.cgi?id=207427 |
|
Back to top |
|
|
michel7 Guru
Joined: 04 May 2006 Posts: 461 Location: localhost
|
Posted: Tue Jan 29, 2008 12:40 pm Post subject: |
|
|
is this issue still unsolved? _________________ Software is like sex. It's better when it's free |
|
Back to top |
|
|
mantoo Tux's lil' helper
Joined: 08 Dec 2007 Posts: 98 Location: Germany
|
Posted: Tue Jan 29, 2008 12:44 pm Post subject: |
|
|
depends... for the modules 1.0.14 an 1.0.15 yeah, i dont know if there is a newer one one maybe now.. i used the unstable (9999) and that worked for me
maybe i should change the title not to "[solved]" but "[workaround]" ? |
|
Back to top |
|
|
Paapaa l33t
Joined: 14 Aug 2005 Posts: 955 Location: Finland
|
Posted: Tue Jan 29, 2008 9:56 pm Post subject: |
|
|
BTW, why don't people use the kernel driver? _________________ Paludis, the way packages are meant to be managed. |
|
Back to top |
|
|
keenblade Veteran
Joined: 03 Oct 2004 Posts: 1087
|
Posted: Tue Jan 29, 2008 10:04 pm Post subject: |
|
|
Paapaa wrote: | BTW, why don't people use the kernel driver? |
As a module it is updated more often, than a builtin kernel driver. And if you are a musician, than you are more obsessive about bleeding edge multimedia
sverzel wrote: | After getting the new gentoo-sources and using the new kernel, media-sound/alsa-drivers fails to emerge (both 1.0.14 and 1.0.15)...
Anyone experiencing the same problem? Advice? |
Norberto Bensa's suggestion at bugzilla worked for me, too;
Code: |
mv alsa-driver-1.0.15.ebuild to alsa-driver-1.0.16_rc1.ebuild
ebuild alsa-driver-1.0.16_rc1.ebuild digest
emerge alsa-driver
|
I did this on my local overlay, btw. _________________ Anyway it's all the same at the end...
Need help to get it working: "x-fi surround 5.1" |
|
Back to top |
|
|
beatryder Veteran
Joined: 08 Apr 2005 Posts: 1138
|
Posted: Thu Jan 31, 2008 9:42 pm Post subject: |
|
|
keenblade wrote: | Paapaa wrote: | BTW, why don't people use the kernel driver? |
As a module it is updated more often, than a builtin kernel driver. And if you are a musician, than you are more obsessive about bleeding edge multimedia
sverzel wrote: | After getting the new gentoo-sources and using the new kernel, media-sound/alsa-drivers fails to emerge (both 1.0.14 and 1.0.15)...
Anyone experiencing the same problem? Advice? |
Norberto Bensa's suggestion at bugzilla worked for me, too;
Code: |
mv alsa-driver-1.0.15.ebuild to alsa-driver-1.0.16_rc1.ebuild
ebuild alsa-driver-1.0.16_rc1.ebuild digest
emerge alsa-driver
|
I did this on my local overlay, btw. |
This also seems to have worked for me. _________________ Dont make it idiot proof, make it work.
Neucode.org
<suppressed key> |
|
Back to top |
|
|
Paapaa l33t
Joined: 14 Aug 2005 Posts: 955 Location: Finland
|
Posted: Thu Jan 31, 2008 9:55 pm Post subject: |
|
|
keenblade wrote: | Paapaa wrote: | BTW, why don't people use the kernel driver? |
As a module it is updated more often, than a builtin kernel driver. And if you are a musician, than you are more obsessive about bleeding edge multimedia |
I don't think you necessarily get more "bleeding edge multimedia" if you use a slightly newer Alsa driver. Usually the driver either works, or doesn't.
And the latest kernel 2.6.24 has the latest ALSA 1.0.15. But true, 2.6.24 is not yet in stable. At least people with problems should try the in-kernel driver. That is what the kernel team also recommends. IIRC, there has also been some discussion whether to drop the separate drivers completely.
I don't understand why there is a separate ALSA module in the first place. Kernel should handle all the needed device drivers. _________________ Paludis, the way packages are meant to be managed. |
|
Back to top |
|
|
keenblade Veteran
Joined: 03 Oct 2004 Posts: 1087
|
Posted: Fri Feb 01, 2008 4:02 am Post subject: |
|
|
Paapaa wrote: |
I don't think you necessarily get more "bleeding edge multimedia" if you use a slightly newer Alsa driver. Usually the driver either works, or doesn't.
And the latest kernel 2.6.24 has the latest ALSA 1.0.15. But true, 2.6.24 is not yet in stable. At least people with problems should try the in-kernel driver. That is what the kernel team also recommends. IIRC, there has also been some discussion whether to drop the separate drivers completely.
I don't understand why there is a separate ALSA module in the first place. Kernel should handle all the needed device drivers. |
I like to use module, because;
If a version of alsa driver does not work for you, than you just emerge a previous or a working version easily, for the sake of low latency.
No need to compile all kernel, just alsa-driver.
When I was a windows user, there was creative drivers for sblive soundcard. It was far better than ms ones. Then came kX drivers. It was better than all and pushed the card limits to all possibilities. Finaly, later asio4all driver was the nirvana for low latency audio. It was incredibly made my pc an effect processor for my guitar. Sometimes previous versions worked better.
So the sound driver is important for me. I don't think it is different for linux.
As you see using a module, I could use driver that is not in portage and in kernel. Isn't that wonderful? Possibly one can integrate the new driver into kernel himself, but thats to much work. I hope they provide the driver as a module in the future, too. _________________ Anyway it's all the same at the end...
Need help to get it working: "x-fi surround 5.1" |
|
Back to top |
|
|
Paapaa l33t
Joined: 14 Aug 2005 Posts: 955 Location: Finland
|
Posted: Fri Feb 01, 2008 10:11 am Post subject: |
|
|
keenblade wrote: | If a version of alsa driver does not work for you, than you just emerge a previous or a working version easily, for the sake of low latency. |
Have actually you had a situation where the ALSA in the latest stable kernel doesn't work but an older one does? I'd like to know how possible this scenario is in actual life. Similarly we could have every single device driver both in kernel and in portage tree. What a mess would that be, _________________ Paludis, the way packages are meant to be managed. |
|
Back to top |
|
|
PaulBredbury Watchman
Joined: 14 Jul 2005 Posts: 7310
|
Posted: Fri Feb 01, 2008 10:17 am Post subject: |
|
|
Paapaa wrote: | an older one does? |
I've seen loads of ALSA threads complaining that 1.0.15 breaks what used to work in 1.0.14
Then again, 1.0.15 fixes lotsa stuff. |
|
Back to top |
|
|
Paapaa l33t
Joined: 14 Aug 2005 Posts: 955 Location: Finland
|
Posted: Fri Feb 01, 2008 10:26 am Post subject: |
|
|
PaulBredbury wrote: | I've seen loads of ALSA threads complaining that 1.0.15 breaks what used to work in 1.0.14 |
But are we talking about 1.0.15 in kernel, not the 1.0.15 driver? Those are not, AFAIK, identical. _________________ Paludis, the way packages are meant to be managed. |
|
Back to top |
|
|
Fuchs Tux's lil' helper
Joined: 27 Apr 2005 Posts: 133 Location: Confoederatio Helvetica
|
Posted: Fri Feb 01, 2008 10:57 am Post subject: |
|
|
First of all: creating a 1.0.16_r1 or 1.0.16_r2 ebuild works,
same goes for unmasking 9999, as this is a known
problem which has been fixed in alsa-drivers svn.
For in-kernel VS external: There are good reasons for using not the
in kernel alsa-drivers, as they might be, at least
if you are using a stable kernel, rather old.
I have a new santa rosa intel chipset here,
and the onboard sound (hda-intel) works
with >= 1.0.15 and there it is still buggy.
The mute behaviour is correct now in 1.0.16_r2,
while it wasn't even in 1.0.16_r1.
So there are people who definitely have good reasons
for using the external alsa drivers.
Fuchs _________________ --omg-optimized |
|
Back to top |
|
|
keenblade Veteran
Joined: 03 Oct 2004 Posts: 1087
|
Posted: Sun Feb 03, 2008 2:46 am Post subject: |
|
|
Paapaa wrote: |
Have actually you had a situation where the ALSA in the latest stable kernel doesn't work but an older one does? I'd like to know how possible this scenario is in actual life. Similarly we could have every single device driver both in kernel and in portage tree. What a mess would that be, |
I had not tried the latest in kernel alsa driver until now. But I have just tried. It compiled fine. Works fine. But performance is much better with the newer 1.0.16_r1 and r2. Just did a quick audacity benchmark. New alsa drivers is twice fast for audacity. Ok audacity is not a benchmark tool but, it shows new driver is faster. But I know some people could not compile in kernel alsa, too. So what is happening is an actual life scenario.
Also I agree there is no need to have every single device driver both in kernel and in portage tree. But sound and graphic are not one of them. I don't think this makes a mess. Gentoo is all about choices. Also what is wrong with being modular? Haven't xorg and kde gone better as being modular. Even internal kernel alsa driver is built as a module, too. Thats the preferred way, other ways, it won't work.
Being modular and using modules rock for me. That's freedom. _________________ Anyway it's all the same at the end...
Need help to get it working: "x-fi surround 5.1" |
|
Back to top |
|
|
pappy_mcfae Watchman
Joined: 27 Dec 2007 Posts: 5999 Location: Pomona, California.
|
Posted: Sun Feb 03, 2008 7:36 am Post subject: |
|
|
Personally, I am not all that impressed with the alsa drivers that come with vanilla and gentoo-sources-2.6.24. Come to think of it, I'm not all that impressed with the new kernel at all.
In my opinion, the driver for my new laptop sound chip (intel-hda) went backwards. The headphone jack still doesn't work properly, and when the new driver takes hold of the sound chip, it doesn't let go. Much like when I switch between Windoze and Gentoo, in order to get the sound to work, I have to power the system down. Same thing with the new drivers. If I use the 2.6.24 kernel, and swtich back to one that works (2.6.22.16), I get no sound, unless I completely power down.
I guess I'll have to be stuck at 2.6.22.16 until they fix the alsa drivers...oh, yeah, and that pesky broadcom wireless adapters no longer work thing, too.
Color me unimpressed.
Blessed be!
Pappy _________________ This space left intentionally blank, except for these ASCII symbols. |
|
Back to top |
|
|
PaulBredbury Watchman
Joined: 14 Jul 2005 Posts: 7310
|
Posted: Sun Feb 03, 2008 7:48 am Post subject: |
|
|
ALSA bugs should go in the ALSA bugzilla.
The people who are capable of fixing ALSA bugs don't read this forum, AFAICT. |
|
Back to top |
|
|
schachti Advocate
Joined: 28 Jul 2003 Posts: 3765 Location: Gifhorn, Germany
|
|
Back to top |
|
|
josedb Apprentice
Joined: 03 Nov 2006 Posts: 222
|
Posted: Sun Feb 17, 2008 9:45 am Post subject: |
|
|
could anybody tell how do i install svn alsa-driver? |
|
Back to top |
|
|
schachti Advocate
Joined: 28 Jul 2003 Posts: 3765 Location: Gifhorn, Germany
|
Posted: Sun Feb 17, 2008 10:20 am Post subject: |
|
|
Add the following to /etc/portage/package.unmask:
Code: | =media-sound/alsa-driver-9999
=media-sound/alsa-headers-9999 |
Add the following to /etc/portage/package.keywords:
Code: | =media-sound/alsa-driver-9999
=media-sound/alsa-headers-9999 |
emerge the latest version:
Code: | emerge =media-sound/alsa-driver-9999 |
_________________ Never argue with an idiot. He brings you down to his level, then beats you with experience.
How-To: Daten verschlüsselt auf DVD speichern. |
|
Back to top |
|
|
josedb Apprentice
Joined: 03 Nov 2006 Posts: 222
|
Posted: Sun Feb 17, 2008 3:46 pm Post subject: |
|
|
alsa-driver already emerged but the problem persist, when i try to play any sound the program crash.
http://img513.imageshack.us/img513/2806/screenshotpc0.png
this is what i mean
http://img405.imageshack.us/img405/1783/screenshot1be8.png
localhost ~ # lsmod
Module Size Used by
snd_hda_intel 356312 0
snd_pcm 57032 1 snd_hda_intel
snd_timer 16712 1 snd_pcm
snd_page_alloc 7120 2 snd_hda_intel,snd_pcm
snd_hwdep 6408 1 snd_hda_intel
snd 36424 4 snd_hda_intel,snd_pcm,snd_timer,snd_hwdep
nvidia 6997716 26
soundcore 7584 1 snd
Last edited by josedb on Sun Feb 17, 2008 4:35 pm; edited 2 times in total |
|
Back to top |
|
|
|