Problems with alsa-driver

Message

xavier10 · Post by **xavier10** » Wed Jun 30, 2004 11:57 am

Hello,

I notice I cannot emerge any of the alsa-driver ebuilds.

The most recent non experimental one does not emerge because it needs some modversion.h file in its build tree. No big deal, I can add the file from my kernel sources (this is what I guess it should be since it is a linux/ subdirectory of the tree).

Then, I get a compilation error.

I reported a bug, but would like to get sound working sometime and have no time debugging the source right now.

Any suggestion ?

Regards,

Xavier

agent_jdh · Post by **agent_jdh** » Wed Jun 30, 2004 12:15 pm

What kernel are you using?

2.6 kernels don't need the alsa-driver ebuild, the drivers are already included with the kernel.

xavier10 · Post by **xavier10** » Wed Jun 30, 2004 12:39 pm

I have always been using a 2.6 kernel.

I remember emerging alsa-driver with the first one.

I have upgraded the kernel and not only I do not get sound but also I see that other packages require alsa-driver to get emerged/upgraded.

So I am completely confused now.

Regards,

Xavier

agent_jdh · Post by **agent_jdh** » Wed Jun 30, 2004 12:56 pm

Newer 2.6 kernels should provide the dependency required by apps that need alsa-driver. 2.6.7 certainly does. iirc the the first couple of 2.6 releases did not provide this dependency.

What 2.6 kernel do you have?

xavier10 · Post by **xavier10** » Wed Jun 30, 2004 12:59 pm

Right now, I am using 2.6.4pegasos

I am searching for the 2.6.7, just in case...

Regards,

Xavier

agent_jdh · Post by **agent_jdh** » Wed Jun 30, 2004 1:03 pm

What about just the normal development-sources ebuild? Have you tried that? Certainly here that provides the alsa-driver dependency.

xavier10 · Post by **xavier10** » Wed Jun 30, 2004 1:06 pm

This is what I am trying right now...

Regards,

Xavier

xavier10 · Post by **xavier10** » Wed Jun 30, 2004 2:01 pm

The 2.6.7 kernel did not work any better than the 2.6.4

In fact it was even worse: I have not been able to recomple loop-AES for it (did not want to work), so I tried to downgrade to 2.6.4, which left me with a non booting system.

After quite a few attemps, I successfully downgraded to 2.6.1 (my original kernel).

The only difference with this morning is that now, the sound does not work anymore. And I am more than angry: this looks pretty crappy to me.

Time to go back to normal work.

agent_jdh · Post by **agent_jdh** » Wed Jun 30, 2004 2:44 pm

You could try gentoo-dev-sources or pegasos-dev-sources as well.

meowsqueak · Post by **meowsqueak** » Wed Aug 04, 2004 9:38 pm

I have a problem where alsa-driver is being pulled in as a dependency of kdelibs (with 'alsa' USE flag):

Code: Select all

# emerge -Duavt world
...
ebuild     U ]  kde-base/kdelibs-3.2.3 [3.2.2-r1] +alsa -arts -cups -debug +doc -ipv6 +ldap +ssl  12,438 kB 
[ebuild     U ]   kde-base/arts-1.2.3 [1.2.2] +alsa -arts -artswrappersuid -debug -debug -esd -mad +oggvorbis  941 kB 
[ebuild  N    ]   media-sound/alsa-driver-1.0.5a  -debug +oss  1,688 kB

I'm using Linux 2.6.7 and I have development-sources-2.6.7 emerged. There's no sign of alsa-driver in either the /var/cache/edb/world or virtuals file, but there is this line in /etc/make.profile/virtuals:

Code: Select all

virtual/alsa                    media-sound/alsa-driver

I've read about adding this package to /etc/portage/packages.mask but this simply broke the dependency chain and emerge failed to build the depgraph. I could try injecting but I had hoped there is a proper way of fixing this somehow. alsa-driver is not currently installed either.

Does anyone know of the 'proper' way to prevent this situation please?

MasonMouse · Post by **MasonMouse** » Sat Aug 07, 2004 10:56 pm

I would love to know too. I'm running 2.6.6-mm2 and am getting the same error (configure: error: You have built-in ALSA in your kernel.) I emerge sync every couple of days to see if the dependency problem has been fixed but so far no luck.

Dolemite · Post by **Dolemite** » Mon Oct 25, 2004 6:26 am

This is still broken- I cannot block the alsa drivers without killing kdelibs which in turn kills my emerge -U world.

Anyone get this working??????????

I have a 2.6.8 kernel i compiled myself with ck sources with ALSA included- too bad it can tell I have ALSA in my kernel but can't go ahead and install kde-libs

I tried IRC but the people there are too used to telling n00bs how to use keywords.

This sucks. With the deprecation of -U shouldn't masking packages work better??

JoseJX · Post by **JoseJX** » Mon Oct 25, 2004 9:47 am

Yes, it works fine here. You haven't really provided enough information to diagnose the problem though.

Can you please provide the output of emerge --info?

If you've compiled the kernel yourself without emerging a kernel that provides the ALSA headers/driver, you will also experience similar behaviour. If you do not want to emerge kernel sources, emerge the latest version of portage (2.0.51) and use /etc/portage/package.provided to supply the required dependancies.

The more information you provide, the more likely it is someone can fix your problem.

Dolemite · Post by **Dolemite** » Mon Oct 25, 2004 11:46 am

JoseJX wrote:Yes, it works fine here. You haven't really provided enough information to diagnose the problem though.

Can you please provide the output of emerge --info?

If you've compiled the kernel yourself without emerging a kernel that provides the ALSA headers/driver, you will also experience similar behaviour. If you do not want to emerge kernel sources, emerge the latest version of portage (2.0.51) and use /etc/portage/package.provided to supply the required dependancies.

The more information you provide, the more likely it is someone can fix your problem.

Thanks - package.provided is a new one I havent seen in any of the threads or man emerge and yes I have portage 2.0.51
I have tried adding the media-sound/alsa-driver to package.provided and it didnt work, I used the same syntax as package.mask and package.keywords.

When I run emerge -Up world with nothing in package.mask or package.provided I get the following -

Code: Select all

 emerge -pU world

*** Warning: --upgradeonly is a deprecated option in portage-2.0.51-r2
***          and will likely be removed in a future version.

>>> --upgradeonly implies --update... adding --update to options.

These are the packages that I would merge, in order:

Calculating world dependencies ...done!
[ebuild     U ] net-print/cups-1.1.20-r4 [1.1.20-r3]
[ebuild  N    ] media-gfx/graphviz-1.10
[ebuild  N    ] app-doc/doxygen-1.3.8
[ebuild  N    ] media-sound/alsa-driver-1.0.6a
[ebuild  NS   ] kde-base/kdelibs-3.3.0
[ebuild     U ] app-portage/guitoo-0.47.0 [0.46.1]
[ebuild     U ] x11-misc/synaptics-0.13.6 [0.13.5]
[ebuild     U ] sys-apps/baselayout-1.9.4-r6 [1.9.4-r5]
[ebuild     U ] media-libs/libogg-1.1.2 [1.1]
[ebuild     U ] media-libs/libvorbis-1.1.0 [1.0.1-r2]
[ebuild     U ] media-sound/sox-12.17.5-r1 [12.17.4-r1]
[ebuild     U ] app-cdr/k3b-0.11.17 [0.11.12-r1]

If I try emerge -p world I get no upgrades to anything with kde-base dependencies- but there is one media-sound/alsa-driver which pops up

Code: Select all

 emerge -p world

These are the packages that I would merge, in order:

Calculating world dependencies
*** Package in world file is not installed: sys-apps/sh-utils

*** Package in world file is not installed: sys-apps/fileutils

*** Package in world file is not installed: sys-apps/textutils
 ...done!
[ebuild  N    ] media-sound/alsa-driver-1.0.6a
[ebuild     UD] media-libs/alsa-lib-1.0.5-r3 [1.0.6]
[ebuild     U ] app-portage/guitoo-0.47.0 [0.46.1]
[ebuild     U ] x11-misc/synaptics-0.13.6 [0.13.5]
[ebuild     U ] net-print/cups-1.1.20-r4 [1.1.20-r3]
[ebuild     U ] sys-apps/baselayout-1.9.4-r6 [1.9.4-r5]
[ebuild     U ] app-cdr/k3b-0.11.17 [0.11.12-r1]
[ebuild     U ] media-libs/libogg-1.1.2 [1.1]

I have alsa drivers built into my kernel so if I try to emerge media-sound/alsa-driver it will fail every time seeing that it is in my kernel - like so

Code: Select all

 emerge  world
Calculating world dependencies
*** Package in world file is not installed: sys-apps/sh-utils

*** Package in world file is not installed: sys-apps/fileutils

*** Package in world file is not installed: sys-apps/textutils
 ...done!
>>> emerge (1 of 8) media-sound/alsa-driver-1.0.6a to /
>>> md5 src_uri ;-) alsa-driver-1.0.6a.tar.bz2
>>> Unpacking source...
>>> Unpacking alsa-driver-1.0.6a.tar.bz2 to /var/tmp/portage/alsa-driver-1.0.6a/work
 * Applying alsa-driver-1.0.5-devfix.patch ...                            [ ok ] * Applying alsa-driver-1.0.5a-cs46xx-passthrough.patch ...               [ ok ] * Applying alsa-driver-1.0.6a-emu10k1-passthrough.patch ...              [ ok ] * Applying alsa-driver-1.0.6a-kbuild.patch ...                           [ ok ] * /usr/src/linux is a symbolic link
 * Determining the real directory of the Linux kernel source code
 * Building for Linux 2.6.8.1-cko8 found in /usr/src/linux
 * /usr/src/linux is a symbolic link
 * Determining the real directory of the Linux kernel source code
 * Building for Linux 2.6.8.1-cko8 found in /usr/src/linux
>>> Source unpacked.
./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --with-oss --with-kernel=/usr/src/linux --with-isapnp=yes --with-sequencer=yes --with-cards=all
configure: WARNING: If you wanted to set the --build type, don't use --host.
    If a cross compiler is detected then cross compile mode will be used.
checking for i686-pc-linux-gnu-gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for i686-pc-linux-gnu-ranlib... no
checking for ranlib... ranlib
checking for a BSD-compatible install... /bin/install -c
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking whether time.h and sys/time.h may both be included... yes
checking whether gcc needs -traditional... no
checking for current directory... /var/tmp/portage/alsa-driver-1.0.6a/work/alsa-driver-1.0.6a
checking cross compile...
checking for directory with kernel source... /usr/src/linux
checking for kernel version... 2.6.8.1-cko8
checking for GCC version... Kernel compiler: gcc 3.3.4 20040623 (Gentoo Linux 3.3.4-r1, ssp-3.3.2-2, pie-8.7.6) Used compiler: gcc (GCC) 3.3.4 20040623 (Gentoo Linux 3.3.4-r1, ssp-3.3.2-2, pie-8.7.6)
checking for built-in ALSA... "yes"
configure: error: You have built-in ALSA in your kernel.

!!! ERROR: media-sound/alsa-driver-1.0.6a failed.
!!! Function econf, Line 449, Exitcode 1
!!! econf failed
!!! If you need support, post the topmost build error, NOT this status message.

I have alsa built in and I want it that way, like many other people. But emerge dies with that error. I can add that alsa-driver to packages.mask and continue being able to emerge world but I cannot upgrade kde-base or k3b.

This is what I was getting with

Code: Select all

=media-sound/alsa-driver

in /etc/portage/packages.mask

Code: Select all

 emerge -Up world

*** Warning: --upgradeonly is a deprecated option in portage-2.0.51-r2
***          and will likely be removed in a future version.

>>> --upgradeonly implies --update... adding --update to options.

These are the packages that I would merge, in order:

Calculating world dependencies -
!!! All ebuilds that could satisfy "media-sound/alsa-driver" have been masked.
!!! One of the following masked packages is required to complete your request:
- media-sound/alsa-driver-1.0.5a (masked by: package.mask)
- media-sound/alsa-driver-1.0.3 (masked by: package.mask)
- media-sound/alsa-driver-1.0.6a (masked by: package.mask)
- media-sound/alsa-driver-0.9.8 (masked by: package.mask)

For more information, see MASKED PACKAGES section in the emerge man page or
section 2.2 "Software Availability" in the Gentoo Handbook.
!!!    (dependency required by "kde-base/kdelibs-3.2.3-r2" [ebuild])


!!! Problem with ebuild app-portage/guitoo-0.47.0
!!! Possibly a DEPEND/*DEPEND problem.

!!! Depgraph creation failed.

I don't see any work around for getting the upgrade to kde-base installed besides changing alsa to a module in my kernel - which I will not and should not have to do. I don't even use or like kde- I only have the libraries for some apps like k3b that I do use.

I'd appreciate any assistance you could provide on this. I didn't have any luck with packages.provided.

JoseJX · Post by **JoseJX** » Mon Oct 25, 2004 12:11 pm

You didn't provide the information that I asked for, did you install a kernel with portage or did you use your own sources? Can I see the output of:

Code: Select all

emerge --info

The package.provided is actually located in your profile's directory, sorry about that.

Dolemite · Post by **Dolemite** » Mon Oct 25, 2004 1:11 pm

Sorry - I didnt see that emerge info request- tired-

I have more than one kernel- the one Ive been using of late is from ck sources that I got myself. But I also have a 2.6.7-gentoo-r8 kernel made from gentoo sources and it gives the exact same errors about alsa being in the kernel

here is emerge --info for my normal/current setup

Code: Select all

 emerge --info
Portage 2.0.51-r2 (default-x86-2004.0, gcc-3.3.4, glibc-2.3.4.20040808-r1, 2.6.8.1-cko8 i686)
=================================================================
System uname: 2.6.8.1-cko8 i686 Mobile Intel(R) Pentium(R) 4 - M CPU 2.00GHz
Gentoo Base System version 1.4.16
Autoconf: sys-devel/autoconf-2.59-r5
Automake: sys-devel/automake-1.8.5-r1
Binutils: sys-devel/binutils-2.14.90.0.8-r1
Headers:  sys-kernel/linux-headers-2.4.21-r1
Libtools: sys-devel/libtool-1.5.2-r5
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O2 -mcpu=pentium4 -march=pentium4  -pipe -fomit-frame-pointer -mfpmath=sse"
CHOST="i686-pc-linux-gnu"
COMPILER=""
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -mcpu=pentium4 -march=pentium4  -pipe -fomit-frame-pointer -mfpmath=sse"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache distlocks sandbox"
GENTOO_MIRRORS="ftp:///ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ ftp://mir.zyrianes.net/gentoo/ http://mirror.datapipe.net/gentoo http://ftp-mirror.internap.com/pub/gentoo/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X alsa apm arts avi berkdb bitmap-fonts cdr crypt cups debug doc dvd encode esd f77 foomaticdb gdbm gif gnome gpm gtk gtk2 imlib java jpeg kerberos ldap libg++ libwww mad mikmod motif mozilla mpeg mysql ncurses nls nntp oggvorbis opengl oss other_var1 other_var2 pam pda pdflib perl png ppds python quicktime readline samba sdk sdl slang spell ssl svga tcpd truetype usb x86 xml2 xmms xprint xv zlib"

JoseJX · Post by **JoseJX** » Mon Oct 25, 2004 2:42 pm

If you at one point had the alsa-driver installed or injected on your computer, it may still be in your world file. What is the output of emerge -p unmerge alsa-driver? If it is installed, unmerge it and the problem should go away.

Dolemite · Post by **Dolemite** » Mon Oct 25, 2004 2:49 pm

nope its not there

--- Couldn't find alsa-driver to unmerge.

>>> unmerge: No packages selected for removal.

I did manage to upgrade most other things like k3b- and now emerge world and emerge -U world is clean but I can't emerge alsa-drivers so no kdelibs and no amorok emerging

Dolemite · Post by **Dolemite** » Mon Oct 25, 2004 3:20 pm

I fixed it. Basically the alsa-driver build process looks to /usr/src/linux for evidence of what is in your kernel- first before beginning to compile it checks your .config- i have some gentoo 2.4* kernel sources so I changed the linux directory link and it began to build- but it failed when it didnt see /usr/src/linux/include/linux/poll.h:4:22: - so im gonna run genkernel on it and everything should be fine after that

Dolemite · Post by **Dolemite** » Mon Oct 25, 2004 4:46 pm

looks like this is a reproduceable bug
and this is NOT PPC specific

http://bugs.gentoo.org./show_bug.cgi?id=65702

this is from my addition to the bug report

this is reproduceable - i also use 2.6.8 ck sources and have alsa built into the kernel- so alsa-driver build fails every time- I had to use gentoo sources in order to get the make process to even begin when emerge alsa-driver was run- and it failed with the same errors as previously mentioned

from rate.c:2:
/usr/src/linux/include/linux/poll.h:4:22: asm/poll.h: No such file or directory
/usr/src/linux/include/linux/poll.h:11:25: asm/uaccess.h: No such file or directory
In file included from /var/tmp/portage/alsa-driver-1.0.6a/work/alsa-driver-1.0.6a/include/sound/pcm.h:29,
from /var/tmp/portage/alsa-driver-1.0.6a/work/alsa-driver-1.0.6a/alsa-kernel/core/oss/rate.c:25,
from rate.c:2:
/usr/src/linux/include/linux/bitops.h:69:24: asm/bitops.h: No such file or directory
make[3]: *** [fastdep] Error 1
make[3]: Leaving directory `/var/tmp/portage/alsa-driver-1.0.6a/work/alsa-driver-1.0.6a/acore/oss'
make[2]: *** [_sfdep_oss] Error 2
make[2]: Leaving directory `/var/tmp/portage/alsa-driver-1.0.6a/work/alsa-driver-1.0.6a/acore'
make[1]: *** [dep] Error 1
make[1]: Leaving directory `/var/tmp/portage/alsa-driver-1.0.6a/work/alsa-driver-1.0.6a'
make: *** [include/sndversions.h] Error 2

!!! ERROR: media-sound/alsa-driver-1.0.6a failed.
!!! Function src_compile, Line 91, Exitcode 2
!!! Parallel Make Failed
!!! If you need support, post the topmost build error, NOT this status message.

Not to cool to have to emerge genkernel and build a fake kernel just to install some drivers which arent needed and wont be used by the real kernel- this is breaking the installation of apps that have alsa-driver listed as a dependency
such as kde-base and kde-libs

others have this issue too - see http://forums.gentoo.org/posting.php?mo ... y&t=192097

workaround is to link kernel sources to /usr/src/linux and generate a kernel with no alsa or alsa as a module or - i didnt have to change permission like the other reporter did- easiest automated solution is to
emerge gentoo-sources
emerge genkernel (if you dont already have it)
genkernel all
then emerge alsa-driver will work

JoseJX · Post by **JoseJX** » Tue Oct 26, 2004 12:10 am

You should *not* need to install the alsa-driver, the virtual should be satisfied by emerging a 2.6 kernel.

Have you tried the solution here?
http://forums.gentoo.org/viewtopic.php? ... alsadriver

Dolemite · Post by **Dolemite** » Tue Oct 26, 2004 1:37 am

JoseJX wrote:You should *not* need to install the alsa-driver, the virtual should be satisfied by emerging a 2.6 kernel.

Have you tried the solution here?
http://forums.gentoo.org/viewtopic.php? ... alsadriver

That would have helped 10 hours ago possibly. I worked around it by using some gentoo sources and genkernel all, which I will never use.

Next time I run into that problem I will try that I already have alsa-drivers and kdelibs 3.3 installed so I'm not gonna go back and try again. This is definitely a bug. I had previously emerged a 2.6 kernel from gentoo and I do have the sources in /usr/src and I never unmerged it- but I had unmerged all the post updated kernel sources that emerge world dropped on me because I value 300mb of disk space.

Are you a portage dev? Someone should add virtuals and provided references to the emerge man. I didn't think to man portage which details virtuals.

Unfortunately it looks like I had gentoo-dev-sources installed and /usr/portage/profiles/default-x86-2004.2/virtuals and the few other virtuals I looked in have only gentoo-sources listed.

Well at least I know alot more about portage now and Amarok 1.1.1 is great and worth it- who says opensource is free lol

john.robinson · Post by **john.robinson** » Wed Oct 27, 2004 6:07 pm

If I'd built my own kernel from 3rd-party sources, and it included the ALSA driver - as it should, being a 2.6 kernel - I think I'd just `emerge --inject sys-kernel/gentoo-dev-sources-2.6.9-r1` in order to satisfy the alsa-driver dependency. I did something similar when I decided to build my own xfree86 with the drivers for my system that the stock ebuild didn't provide.

Dolemite · Post by **Dolemite** » Wed Oct 27, 2004 6:42 pm

john.robinson wrote:If I'd built my own kernel from 3rd-party sources, and it included the ALSA driver - as it should, being a 2.6 kernel - I think I'd just `emerge --inject sys-kernel/gentoo-dev-sources-2.6.9-r1` in order to satisfy the alsa-driver dependency. I did something similar when I decided to build my own xfree86 with the drivers for my system that the stock ebuild didn't provide.

The thing is, I have emerged gentoo-dev-sources 2.6.7-r8 and others before it, for real, not just injected, since my initial installation. It is not just a portage installation entry issue- if alsa-driver's script doesnt see a .config with alsa as a module it will fail. If kernel sources are installed but not configured, it will fail for lack of installation paths in /usr/src/linux/lib/include.

The best bet I'm guessing is virtuals aside from fixing the ebuild.

john.robinson · Post by **john.robinson** » Wed Oct 27, 2004 7:22 pm

I was working from the premise that wherever you'd got your real sources from, you'd configured them with ALSA, and the /usr/src/linux symlink will point to them, so /usr/src/linux/.config would include ALSA as a module, and all the other headers etc. would be there. Then you don't (shouldn't) need alsa-driver at all, because you've already built ALSA in the kernel, and injecting the gentoo sources will satisfy the alsa dependency, so you can build e.g. alsa-utils without ever actually building alsa-driver.