Forums

Skip to content

Advanced search
  • Quick links
    • Unanswered topics
    • Active topics
    • Search
  • FAQ
  • Login
  • Register
  • Board index Architectures & Platforms Gentoo on PPC
  • Search

Problems with alsa-driver

Have a PowerPC specific problem? This is the spot.
Post Reply
Advanced search
34 posts
  • Previous
  • 1
  • 2
Author
Message
Dolemite
Tux's lil' helper
Tux's lil' helper
User avatar
Posts: 77
Joined: Mon Jul 05, 2004 7:49 am
Location: Where the pirates hang out

  • Quote

Post by Dolemite » Wed Oct 27, 2004 7:39 pm

john.robinson wrote: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.
I have 2.6.7-r8 of gentoo-dev-sources installed and configured to include alsa.

The problem is all my kernel sources that I was using had alsa in them which caused the alsa-driver build to fail upon noticing it was not needed, but that broke the dependency for kdelibs.
What you are saying is right, but I had in place everything that your suggestion would have brought to the table.

I think you are on to something though, maybe injecting alsa-driver was the best approach. Add that to my list of new portage techniques.
Seems so f-ing simple now.
Linux 0mega 2.6.8.1-cko8
----------------------------
Screenshot http://dolemite777.spymac.net/shot1.png
-----------------------------
update - ubuntu is ok but I hate debian and I dislike precompiled shit that doesnt work
Top
newLux
n00b
n00b
Posts: 15
Joined: Sat Sep 13, 2003 4:07 pm
Location: Abilene, Texas
Contact:
Contact newLux
Website

alsa-driver compilation failure

  • Quote

Post by newLux » Wed Nov 03, 2004 7:33 pm

I have heard that some other people are having this same type of problem, but the answer that they have does not work, nor do I think that it is the exact same problem. It seems that when I attempt to emerge alsa-driver, it cannot find a header file that it needs. It is looking in one of the directories that it creates for installation, but cannot find it. I have the header file elsewhere on my computer. The file is:

/usr/src/linux-2.6.7-gentoo-r14/include/config/modversions.h

Here is the pertinent output:

gcc -M -D__KERNEL__ -D__isapnp_now__ -DMODULE=1 -I/var/tmp/portage/alsa-driver-0.9.8/work/alsa-driver-0.9.8/include -I/usr/src/linux/include -O2 -D__powerpc__ -fsigned-char -fno-builtin -msoft-float -ffixed-r2 -Wno-uninitialized -mmultiple -mstring -DLINUX -Wall -Wstrict-prototypes -fomit-frame-pointer -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -DALSA_BUILD -I/var/tmp/portage/alsa-driver-0.9.8/work/alsa-driver-0.9.8/alsa-kernel/core/oss mixer_oss.c pcm_oss.c pcm_plugin.c io.c copy.c linear.c mulaw.c route.c rate.c > .depend
In file included from /var/tmp/portage/alsa-driver-0.9.8/work/alsa-driver-0.9.8/include/sound/driver.h:42,
from mixer_oss.c:22:
/var/tmp/portage/alsa-driver-0.9.8/work/alsa-driver-0.9.8/include/adriver.h:42:31: linux/modversions.h: No such file or directory
In file included from /var/tmp/portage/alsa-driver-0.9.8/work/alsa-driver-0.9.8/include/sound/driver.h:42,
from pcm_oss.c:29:
/var/tmp/portage/alsa-driver-0.9.8/work/alsa-driver-0.9.8/include/adriver.h:42:31: linux/modversions.h: No such file or directory
In file included from /var/tmp/portage/alsa-driver-0.9.8/work/alsa-driver-0.9.8/include/sound/driver.h:42,
from /var/tmp/portage/alsa-driver-0.9.8/work/alsa-driver-0.9.8/include/../alsa-kernel/core/oss/pcm_plugin.c:27,
from pcm_plugin.c:2:
/var/tmp/portage/alsa-driver-0.9.8/work/alsa-driver-0.9.8/include/adriver.h:42:31: linux/modversions.h: No such file or directory
In file included from /var/tmp/portage/alsa-driver-0.9.8/work/alsa-driver-0.9.8/include/sound/driver.h:42,
from /var/tmp/portage/alsa-driver-0.9.8/work/alsa-driver-0.9.8/include/../alsa-kernel/core/oss/io.c:22,
from io.c:2:
/var/tmp/portage/alsa-driver-0.9.8/work/alsa-driver-0.9.8/include/adriver.h:42:31: linux/modversions.h: No such file or directory
In file included from /var/tmp/portage/alsa-driver-0.9.8/work/alsa-driver-0.9.8/include/sound/driver.h:42,
from /var/tmp/portage/alsa-driver-0.9.8/work/alsa-driver-0.9.8/include/../alsa-kernel/core/oss/copy.c:22,
from copy.c:2:
/var/tmp/portage/alsa-driver-0.9.8/work/alsa-driver-0.9.8/include/adriver.h:42:31: linux/modversions.h: No such file or directory
In file included from /var/tmp/portage/alsa-driver-0.9.8/work/alsa-driver-0.9.8/include/sound/driver.h:42,
from /var/tmp/portage/alsa-driver-0.9.8/work/alsa-driver-0.9.8/include/../alsa-kernel/core/oss/linear.c:23,
from linear.c:2:
/var/tmp/portage/alsa-driver-0.9.8/work/alsa-driver-0.9.8/include/adriver.h:42:31: linux/modversions.h: No such file or directory
In file included from /var/tmp/portage/alsa-driver-0.9.8/work/alsa-driver-0.9.8/include/sound/driver.h:42,
from /var/tmp/portage/alsa-driver-0.9.8/work/alsa-driver-0.9.8/include/../alsa-kernel/core/oss/mulaw.c:24,
from mulaw.c:2:
/var/tmp/portage/alsa-driver-0.9.8/work/alsa-driver-0.9.8/include/adriver.h:42:31: linux/modversions.h: No such file or directory
In file included from /var/tmp/portage/alsa-driver-0.9.8/work/alsa-driver-0.9.8/include/sound/driver.h:42,
from /var/tmp/portage/alsa-driver-0.9.8/work/alsa-driver-0.9.8/include/../alsa-kernel/core/oss/route.c:22,
from route.c:2:
/var/tmp/portage/alsa-driver-0.9.8/work/alsa-driver-0.9.8/include/adriver.h:42:31: linux/modversions.h: No such file or directory
In file included from /var/tmp/portage/alsa-driver-0.9.8/work/alsa-driver-0.9.8/include/sound/driver.h:42,
from /var/tmp/portage/alsa-driver-0.9.8/work/alsa-driver-0.9.8/include/../alsa-kernel/core/oss/rate.c:22,
from rate.c:2:
/var/tmp/portage/alsa-driver-0.9.8/work/alsa-driver-0.9.8/include/adriver.h:42:31: linux/modversions.h: No such file or directory
make[3]: *** [fastdep] Error 1
make[3]: Leaving directory `/var/tmp/portage/alsa-driver-0.9.8/work/alsa-driver-0.9.8/acore/oss'
make[2]: *** [_sfdep_oss] Error 2
make[2]: Leaving directory `/var/tmp/portage/alsa-driver-0.9.8/work/alsa-driver-0.9.8/acore'
make[1]: *** [dep] Error 1
make[1]: Leaving directory `/var/tmp/portage/alsa-driver-0.9.8/work/alsa-driver-0.9.8'
make: *** [include/sndversions.h] Error 2

I am running on a PowerBook G4 15" Aluminum and I have kernel-2.6.7
There are 10 things in life.
God and Linux.
Top
bruda
Guru
Guru
User avatar
Posts: 377
Joined: Thu May 06, 2004 4:49 pm
Location: Sherbrooke, QC, Canada
Contact:
Contact bruda
Website

  • Quote

Post by bruda » Wed Nov 03, 2004 10:57 pm

It does relate to everything in this thread: It does not make sense to interpret your errors, since you try to emerge alsa-driver (for 2.4 kernels) with a 2.6 kernel--this will certainly fail no matter what you do. The 2.6 kernel tree has the ALSA drivers already included so you do not need to emerge the drivers separately.
Quid latine dictum sit altum videtur
Top
Dolemite
Tux's lil' helper
Tux's lil' helper
User avatar
Posts: 77
Joined: Mon Jul 05, 2004 7:49 am
Location: Where the pirates hang out

  • Quote

Post by Dolemite » Fri Nov 05, 2004 1:12 pm

^^^
what he said

0.9.8?
Linux 0mega 2.6.8.1-cko8
----------------------------
Screenshot http://dolemite777.spymac.net/shot1.png
-----------------------------
update - ubuntu is ok but I hate debian and I dislike precompiled shit that doesnt work
Top
lost-distance
Tux's lil' helper
Tux's lil' helper
Posts: 77
Joined: Thu Apr 10, 2003 3:07 pm

  • Quote

Post by lost-distance » Sun Nov 07, 2004 3:08 pm

I've been having exactly the same problems.

I have a non-gentoo linux-2.6.9 kernel build linked to /usr/src/linux and something, somewhere, *insists* on trying to pull in alsa-driver, even after I removed it from /var/cache/edb/virtuals.

However, I think I've now found the problem. Running "emerge -d -up --deep world" produces, amongst reams of output, the following:

[code]Parent: ebuild / media-sound/alsa-utils-1.0.6 nomerge
Depstring: >=sys-libs/ncurses-5.1 dev-util/dialog >=media-libs/alsa-lib-1.0.3 >=sys-libs/ncurses-5.1 dev-util/dialog >=media-libs/alsa-lib-1.0.3 sys-apps/pciutils
Candidates: ['>=sys-libs/ncurses-5.1', '>=media-libs/alsa-lib-1.0.3', 'dev-util/dialog', 'sys-apps/pciutils']
ebuild: sys-libs/ncurses-5.4-r5
binpkg: None
ebuild: media-libs/alsa-lib-1.0.5-r3
binpkg: None

Parent: ebuild / media-libs/alsa-lib-1.0.5-r3 nomerge
Depstring: >=sys-devel/automake-1.7.2 >=sys-devel/autoconf-2.57-r1 virtual/alsa >=media-sound/alsa-headers-1.0.5a
Candidates: ['>=sys-devel/autoconf-2.57-r1', '>=sys-devel/automake-1.7.2', '>=media-sound/alsa-headers-1.0.5a', 'media-sound/alsa-driver']
ebuild: sys-devel/autoconf-2.59-r5
binpkg: None
ebuild: sys-devel/automake-1.8.5-r1
binpkg: None
ebuild: media-sound/alsa-headers-1.0.6a
binpkg: None

Parent: ebuild / media-sound/alsa-headers-1.0.6a nomerge
Depstring: !bootstrap? ( sys-devel/patch )
Candidates: ['sys-devel/patch']
ebuild: sys-devel/patch-2.5.9
binpkg: None
Exiting... ebuild / media-sound/alsa-headers-1.0.6a nomerge
ebuild: media-sound/alsa-driver-1.0.6a
binpkg: None

Parent: ebuild / media-sound/alsa-driver-1.0.6a merge
Depstring: virtual/modutils ~media-sound/alsa-headers-1.0.6a virtual/linux-sources sys-devel/autoconf sys-apps/debianutils !bootstrap? ( sys-devel/patch ) !bootstrap? ( sys-devel/patch ) !bootstrap? ( sys-devel/patch ) virtual/modutils ~media-sound/alsa-headers-1.0.6a
Candidates: ['sys-apps/module-init-tools', '~media-sound/alsa-headers-1.0.6a', 'sys-kernel/gentoo-sources', 'sys-devel/patch', 'sys-devel/autoconf', 'sys-apps/debianutils']
ebuild: sys-apps/module-init-tools-3.0-r2
binpkg: None[/code]

At a guess, this looks like:

alsa-utils pulls in alsa-lib
alsa-lib pulls in alsa-headers
alsa-headers pulls in alsa-driver

If this is the case then, yes, the ebuilds are broken.
Top
JoseJX
Retired Dev
Retired Dev
Posts: 2774
Joined: Sun Apr 28, 2002 8:21 pm
Contact:
Contact JoseJX
Website

  • Quote

Post by JoseJX » Sun Nov 07, 2004 10:29 pm

The ebuilds are not broken. You need to have a 2.6 kernel from the portage tree installed, otherwise it will try to install the alsa-driver. It doesn't have to be the one linked to /usr/src/linux, you don't need to use it, it just needs to be installed. If you're still having problems, please give more details about your setup.
Top
lost-distance
Tux's lil' helper
Tux's lil' helper
Posts: 77
Joined: Thu Apr 10, 2003 3:07 pm

  • Quote

Post by lost-distance » Mon Nov 08, 2004 12:53 am

This solves it for me:

Code: Select all

echo media-sound/alsa-driver-1.0.6a >> /etc/portage/profile/package.provided
Top
mattsavigear
Apprentice
Apprentice
User avatar
Posts: 224
Joined: Wed Jan 08, 2003 11:16 am
Location: Wales, UK

  • Quote

Post by mattsavigear » Mon Nov 29, 2004 7:13 pm

Bump.

JoseJX - I have ck sources installed from portage (and in /usr/src/linux), and if I try to install alsa-jack I get alsa-lib and alsa-driver in the dependencies. alsa-driver of course refuses to build.

I don't have an /etc/portage/profile directory, so I don't have the fic lost-distance is suggesting. I'm not going to add directories willy-nilly until I have an idea what teh effect will be. Any suggestions?

Thanks in advance.
Matt.

"Ninjas aren't dangerous. They're more afraid of you than you are of them." - The Tick.
Top
wulff
n00b
n00b
Posts: 19
Joined: Sun Jan 23, 2005 1:07 pm

  • Quote

Post by wulff » Sun Jan 23, 2005 1:29 pm

Hey, I'm a newb using kernel 2.4.28-gentoo-r5.

Just trying to update my system, and I'm having the same problem. I've been able to solve some other issues myself, because portage will usually give me some clue where to look for a solution, or what package to install. This problem has me perplexed, and I don't really understand the solutions listed here.

Will one of these solutions leave me without the ability to use sound when I finally do get kde up and running?

forgot to mention portage is trying to install alsa-driver-1.0.8rc1 and I get nearly identical output to what's been shown.
Top
Post Reply

34 posts
  • Previous
  • 1
  • 2

Return to “Gentoo on PPC”

Jump to
  • Assistance
  • ↳   News & Announcements
  • ↳   Frequently Asked Questions
  • ↳   Installing Gentoo
  • ↳   Multimedia
  • ↳   Desktop Environments
  • ↳   Networking & Security
  • ↳   Kernel & Hardware
  • ↳   Portage & Programming
  • ↳   Gamers & Players
  • ↳   Other Things Gentoo
  • ↳   Unsupported Software
  • Discussion & Documentation
  • ↳   Documentation, Tips & Tricks
  • ↳   Gentoo Chat
  • ↳   Gentoo Forums Feedback
  • ↳   Duplicate Threads
  • International Gentoo Users
  • ↳   中文 (Chinese)
  • ↳   Dutch
  • ↳   Finnish
  • ↳   French
  • ↳   Deutsches Forum (German)
  • ↳   Diskussionsforum
  • ↳   Deutsche Dokumentation
  • ↳   Greek
  • ↳   Forum italiano (Italian)
  • ↳   Forum di discussione italiano
  • ↳   Risorse italiane (documentazione e tools)
  • ↳   Polskie forum (Polish)
  • ↳   Instalacja i sprzęt
  • ↳   Polish OTW
  • ↳   Portuguese
  • ↳   Documentação, Ferramentas e Dicas
  • ↳   Russian
  • ↳   Scandinavian
  • ↳   Spanish
  • ↳   Other Languages
  • Architectures & Platforms
  • ↳   Gentoo on ARM
  • ↳   Gentoo on PPC
  • ↳   Gentoo on Sparc
  • ↳   Gentoo on Alternative Architectures
  • ↳   Gentoo on AMD64
  • ↳   Gentoo for Mac OS X (Portage for Mac OS X)
  • Board index
  • All times are UTC
  • Delete cookies

© 2001–2026 Gentoo Foundation, Inc.

Powered by phpBB® Forum Software © phpBB Limited

Privacy Policy

 

 

magic