Mike Payson wrote:
I've been trying to do an emerge -u world for about two weeks now. Every
time it get's to alsa-driver-1.0.8_rc1, it crashes. Here's the error
message I'm getting. Any ideas?
Thanks!
Mike
gcc -D__KERNEL__ -DMODULE=1
I've been trying to do an emerge -u world for about two weeks now. Every
time it get's to alsa-driver-1.0.8_rc1, it crashes. Here's the error
message I'm getting. Any ideas?
Thanks!
Mike
gcc -D__KERNEL__ -DMODULE=1
-I/var/tmp/portage/alsa-driver-1.0.8_rc1/work/alsa-driver-1.0.8rc1/include
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi list,
can anyone please tell me why alsa-driver depends on pfeifer-sources?
emerge -p alsa-driver
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[ebuild N] sys-kernel/pfeifer-sources-2.4.21.1_pre4
go to virtuals file and remove pfiefer-kelnel from the kernel line...
i had similar problem with ck-sources and alsa...
i mean this file :
/var/cache/edb/virtuals
|hi list,
|
|can anyone please tell me why alsa-driver depends on pfeifer-sources?
|
|emerge -p alsa-driver
|
|These are the packages
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
go to virtuals file and remove pfiefer-kelnel from the kernel line...
i had similar problem with ck-sources and alsa...
i mean this file :
/var/cache/edb/virtuals
mh...there was no pfeifer-sources entry in this file. i added pfeifer-sources
on
Hi,
Why is emerge telling my it wants to install alsa-driver 0.9.8 when I
have 1.0.0rc2 installed? It's strange that it's doing this only for the
driver file and not the rest of Alsa:
Wizard root # emerge -Up world
--upgradeonly implies --update... adding --update to options.
These are the
Because the driver is not unmasked. Just ignore emerge.
It really wants to downgrade since the unmasked version
is lower. I'm seeing it too every time I do a emerge -uD
world -p so I ignore it. You can fix it by editing the
ebuild and taking the ~x86 out of the KEYWORDS entry.
On Thu, 11
Because the driver is not unmasked. Just ignore emerge.
It really wants to downgrade since the unmasked version
is lower. I'm seeing it too every time I do a emerge -uD
world -p so I ignore it. You can fix it by editing the
ebuild and taking the ~x86 out of the KEYWORDS entry.
Brett,
Because the driver is not unmasked. Just ignore emerge.
It really wants to downgrade since the unmasked version
is lower. I'm seeing it too every time I do a emerge -uD
world -p so I ignore it. You can fix it by editing the
ebuild and taking the ~x86 out of the KEYWORDS entry.
If I remember correctly not all the alsa-1.0.x are masked
so they dont' show up as needing replacement.
Another thing we can do is emerge -UD world where U says
do not downgrade or it's not supposed to (I hadn't thought
of that before). Another option is emerge -i
alsa-driver-0.98.ebuild
Thanks. I'll go back and see what I have in the ebuilds.
I'll also check and see if I did a kernel update - I know
I did but not just when I did it.
On Thu, 11 Dec 2003 18:10:06 +0100
Patrick Börjesson [EMAIL PROTECTED] wrote:
Because the driver is not unmasked. Just ignore
emerge.
It
SNIP
Another thing we can do is emerge -UD world where U says
do not downgrade or it's not supposed to (I hadn't thought
of that before).
This is the command I use. If I use emerge -up world then emerge tells me
it's going to remove all of 1.0.0rc2 and install 0.9.8.
I've currently done
KEYWORDS=~x86 emerge alsa-driver
I think there is a little mistake in here, it should be:
ACCEPT_KEYWORDS=~x86 emerge alsa-driver
brgds, Marc
--
[EMAIL PROTECTED] mailing list
KEYWORDS=~x86 emerge alsa-driver
I think there is a little mistake in here, it should be:
ACCEPT_KEYWORDS=~x86 emerge alsa-driver
Yeap, you're of course right. =)
Patrick Börjesson
--
Public key ID: 4C5AB0BF
Public key available at wwwkeys.pgp.net
pgp0.pgp
Description: PGP
I missed that. The D says do dependencies so I would
assume it's going to merge stuff that alsa-driver depends
on. Someone else gave a good explanation of what is
happening.
I understand - I'm here but where is here? G.
On Thu, 11 Dec 2003 09:40:33 -0800
Mark Knecht [EMAIL PROTECTED]
KEYWORDS=~x86 emerge alsa-driver
I think there is a little mistake in here, it should be:
ACCEPT_KEYWORDS=~x86 emerge alsa-driver
brgds, Marc
Well, yes but no. I'm typing these emails on a Windows box and sometimes
mess up what I wrote in an email, but thanks for pointing that out.
I emerged alsa-driver again with ACCEPT_KEYWORDS=~x86 and it still wants to
downgrade in a emerge -uD world -p so should I create the
/etc/portage/portage.unmask file?
Thursday 11 December 2003 12:10, Patrick Börjesson wrote:
Alsa-driver-1.0.0_rc2 is ~x86, 0.9.8 is ordinary x86. They are
I emerged alsa-driver again with ACCEPT_KEYWORDS=~x86 and it still
wants to downgrade in a emerge -uD world -p so should I create the
/etc/portage/portage.unmask file?
Well... since you run without ~x86 ordinarily this is to be expected. If
you don't want to downgrade alsa-driver after you've
Something is royally messed up.
I've created the /etc/portage/package.unmask . I put media-sound/alsa-driver
and all the other alsa stuff a media-sound/alsa-driver or whatever the
package is in the file. The format was media-sound/alsa-driver or
media-libs/alsa-lib. I did this for driver,
I have alsa-driver version 0.9.2 installed. After running emerge world
-u my system wants to install 0.9.8 but as a new package and not as an
update to 0.9.2.
Is this a slotting issue?
--
Ian Truelsen
Email: [EMAIL PROTECTED]
AIM: ihtruelsen
Homepage: http://www.ihtruelsen.dyndns.org
--
No, you can't slot a driver like this. You use one or the other.
On Thursday 27 November 2003 13:44, you wrote:
I have alsa-driver version 0.9.2 installed. After running emerge world
-u my system wants to install 0.9.8 but as a new package and not as an
update to 0.9.2.
Is this a slotting
On Friday 28 November 2003 03:44, Ian Truelsen wrote:
I have alsa-driver version 0.9.2 installed. After running emerge world
-u my system wants to install 0.9.8 but as a new package and not as an
update to 0.9.2.
Is this a slotting issue?
Contrary to the other post, YES. From
Hi Mike,
I think the file you should look at should be
/usr/src/linux/include/asm/mach-default/irq_vector.h.
Actually this brings me to an interesting question. If your
/usr/include/asm does not have a mach-default directory, that sounds
like either of the following possibilities:
a. You are
You should build it within the kernel not as a separate ebuild.
In the sound section you can select alsa support.
True enough, but my experience with the 2.6 alsa was not good. I
have a card
(es1371) that works just fine with the OSS modules, but it's DOA
with 2.6 alsa
support.
On Wed, 24 Sep 2003, Mark Knecht wrote:
For kicks I emerged the development-sources. I assume this is the 2.6 kernel
you are talking about.
I have no real intention of building this kernel, but I wanted to look
around a bit. Alsa sound is an option when I run make xconfig, which is
good,
-Original Message-
From: Mark Knecht [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 24, 2003 11:00 AM
To: [EMAIL PROTECTED]
Subject: RE: [gentoo-user] alsa-driver
So, where is Alsa in this kernel?
Thanks,
Mark
Question to myself, is Alsa really *not* in the 2.6 kernel
On Wed, 24 Sep 2003, Mark Knecht wrote:
So, where is Alsa in this kernel?
Thanks,
Mark
Question to myself, is Alsa really *not* in the 2.6 kernel until I emerge
Alsa?
If so, how do I emerge Alsa for this kernel tree without upsetting my other
kernel trees? Just run emerge alsa-XXX
On Thu Sep 25, 2003 at 12:19:12AM +0800 or thereabouts, Lim Swee Tat wrote:
Hi Mike,
I think the file you should look at should be
/usr/src/linux/include/asm/mach-default/irq_vector.h.
Actually this brings me to an interesting question. If your
/usr/include/asm does not have a
Alsa is part of the 2.6 kernel. You don't need alsa-driver anymore,
although you do need alsa-utils for alsactl and alsamixer. Looking
through portage, as of the most recent ebuild, alsa-utils-0.9.6-r1 (~x86),
the init script is moved from alsa-driver to alsa-utils.
--
Marshal,
If Alsa is truly 'part of the kernel' then my question was, and still
is,
where is the source code in the kernel tree?
Out of morbid curiousity--
What's wrong with the drivers in linux-2.6.0-test*/sound?
-Heschi
--
[EMAIL PROTECTED] mailing list
On Wed, 24 Sep 2003, Mark Knecht wrote:
Alsa is part of the 2.6 kernel. You don't need alsa-driver anymore,
although you do need alsa-utils for alsactl and alsamixer. Looking
through portage, as of the most recent ebuild, alsa-utils-0.9.6-r1 (~x86),
the init script is moved from
Simple enough.
cd /usr/src/linux-beta/sound/
For some reason or other, sound is no longer in drivers.
Thanks. That was what I was missing. I looked and looked at that directory
and just didn't see it.
Thanks!
Now, this is then the directory I will patch with my hdsp updates under this
If Alsa is truly 'part of the kernel' then my question was, and still
is,
where is the source code in the kernel tree?
Out of morbid curiousity--
What's wrong with the drivers in linux-2.6.0-test*/sound?
-Heschi
Nothing except they are out of date. I just didn't see the directory
I have been trying to emerge the alsa-driver, but the emerge fails. The
error message is this:
ERROR: media-sound/alsa-driver-0.9.2 failed.
Function src_compile, Line 59, Exitcode 2
Parallel Make Failed.
Just wondering how I can correct this. I followed the alsa-driver howto
on the gentoo site,
On Tuesday 23 September 2003 03:00 pm, Michael Rasile wrote:
Parallel Make Failed
A semi-educated guess: Go to your /etc/make.conf and look for the
line: MAKEOPTS=-j2. Try changing that to: MAKEOPTS=-j1
And try the emerge again.
--
Regards, Ernie
100% Microsoft and Intel free
--
[EMAIL
On Tue Sep 23, 2003 at 02:20:36PM -0400 or thereabouts, Ernie Schroder wrote:
On Tuesday 23 September 2003 03:00 pm, Michael Rasile wrote:
Parallel Make Failed
A semi-educated guess: Go to your /etc/make.conf and look for the
line: MAKEOPTS=-j2. Try changing that to: MAKEOPTS=-j1
And try
Hi,
It sounds like you linked your /usr/src/linux/include/linux in
/usr/include/linux. The default /usr/include/linux in gentoo is usually
linux 2.4, and where irq_vector.h is missing appears to be only in linux
2.6.
Just do something really simple.
ln -sf
On Tuesday 23 September 2003 03:51 pm, Michael Rasile wrote:
On Tue Sep 23, 2003 at 02:20:36PM -0400 or thereabouts, Ernie
Schroder wrote:
On Tuesday 23 September 2003 03:00 pm, Michael Rasile wrote:
Parallel Make Failed
A semi-educated guess: Go to your /etc/make.conf and look for the
On Tuesday 23 September 2003 03:10 pm, Ernie Schroder wrote:
On Tuesday 23 September 2003 03:51 pm, Michael Rasile wrote:
On Tue Sep 23, 2003 at 02:20:36PM -0400 or thereabouts, Ernie
Schroder wrote:
On Tuesday 23 September 2003 03:00 pm, Michael Rasile wrote:
Parallel Make Failed
On Tue Sep 23, 2003 at 03:10:32PM -0400 or thereabouts, Ernie Schroder wrote:
On Tuesday 23 September 2003 03:51 pm, Michael Rasile wrote:
On Tue Sep 23, 2003 at 02:20:36PM -0400 or thereabouts, Ernie
Schroder wrote:
On Tuesday 23 September 2003 03:00 pm, Michael Rasile wrote:
Parallel
On Wed Sep 24, 2003 at 03:05:29AM +0800 or thereabouts, Lim Swee Tat wrote:
Hi,
It sounds like you linked your /usr/src/linux/include/linux in
/usr/include/linux. The default /usr/include/linux in gentoo is usually
linux 2.4, and where irq_vector.h is missing appears to be only in linux
If you run 2.6 why do you want to build alsa-driver?
Yuval Scharf
On Tue, 23 Sep 2003, Michael Rasile wrote:
On Tue Sep 23, 2003 at 03:10:32PM -0400 or thereabouts, Ernie Schroder wrote:
On Tuesday 23 September 2003 03:51 pm, Michael Rasile wrote:
On Tue Sep 23, 2003 at 02:20:36PM -0400
On Tue, 23 Sep 2003 23:37:48 +0300 (IDT)
Scharf Yuval [EMAIL PROTECTED] wrote:
If you run 2.6 why do you want to build alsa-driver?
Agreed, alsa-driver is only for 2.4 kernels. 2.5/2.6 have alsa drivers built
into the kernel tree.
--
Collins Richey - Denver Area
if you fill your heart with
If you run 2.6 why do you want to build alsa-driver?
Agreed, alsa-driver is only for 2.4 kernels. 2.5/2.6 have alsa
drivers built
into the kernel tree.
So teach me. The alsa revision shipped with 2.6 is out of date. How does one
get back up to date with what is being released by the
:-( Apparently you know more than me.
Yuval Scharf
On Tue, 23 Sep 2003, Mark Knecht wrote:
If you run 2.6 why do you want to build alsa-driver?
Agreed, alsa-driver is only for 2.4 kernels. 2.5/2.6 have alsa
drivers built
into the kernel tree.
So teach me. The alsa revision
On Tue, 23 Sep 2003 14:18:02 -0700
Mark Knecht [EMAIL PROTECTED] wrote:
If you run 2.6 why do you want to build alsa-driver?
Agreed, alsa-driver is only for 2.4 kernels. 2.5/2.6 have alsa
drivers built
into the kernel tree.
So teach me. The alsa revision shipped with 2.6 is
On Tue Sep 23, 2003 at 03:10:52PM -0600 or thereabouts, Collins Richey wrote:
On Tue, 23 Sep 2003 23:37:48 +0300 (IDT)
Scharf Yuval [EMAIL PROTECTED] wrote:
If you run 2.6 why do you want to build alsa-driver?
Agreed, alsa-driver is only for 2.4 kernels. 2.5/2.6 have alsa drivers built
You should build it within the kernel not as a separate ebuild.
In the sound section you can select alsa support.
Yuval Scharf
On Tue, 23 Sep 2003, Michael Rasile wrote:
On Tue Sep 23, 2003 at 03:10:52PM -0600 or thereabouts, Collins Richey wrote:
On Tue, 23 Sep 2003 23:37:48 +0300 (IDT)
:-( Apparently you know more than me.
Yuval Scharf
I doubt it!! My custom ebuild was provided to me by an Alsa developer since
they wanted me to test a sound card that at the time didn't work and I was
probably the only person around who had one. (RME HDSP 9652) This ebuild
patches the
How would I accomplish this with 2.6?
A good question. I would presume you need to subscribe to the
alsa-devel (sp.
?!) list. Google for that.
I know their answer. Patch the kernel.
I'm wondering what the Gentoo flow will do for me? If I don't build Alsa in
the kernel, will Gentoo not
On Wed, 24 Sep 2003 00:42:30 +0300 (IDT)
Scharf Yuval [EMAIL PROTECTED] wrote:
You should build it within the kernel not as a separate ebuild.
In the sound section you can select alsa support.
True enough, but my experience with the 2.6 alsa was not good. I have a card
(es1371) that works
Hi,
I don't know how to check things like masked packages yet, but there has
been a new alsa-driver package on CVS for a few weeks now. Is there and
ebuild for it? I'm not finding it yet.
If there is one, how would I get it? I'm using
emerge -p --deep world to look right now.
Thanks,
Mark
Hello,
Am Dienstag, 15. Juli 2003 19:59 schrieb Mark Knecht:
Hi,
I don't know how to check things like masked packages yet, but there has
been a new alsa-driver package on CVS for a few weeks now. Is there and
ebuild for it? I'm not finding it yet.
Yes, there is a ebuild for alsa-0.9.5 in
I think a ACCEPT_KEYWORDS=~86 emerge -p alsa-driver would do the trick.
You can always look in /usr/portage/category/package to see,
if there are
updates to packages you are interested in.
Michael,
Thanks very much. That does work and it is found. My tired brain is not
adjusting well to
~x86
-Heschi
I think a ACCEPT_KEYWORDS=~86 emerge -p alsa-driver would do the
trick.
On my test machine at work the proposed command:
ACCEPT_KEYWORDS=~86 emerge -p alsa-driver
--
[EMAIL PROTECTED] mailing list
arch corresponds to your particular operating architecture (x86, ppc,
alpha, etc)
arch - Stable packages
~arch - Unstable and testing packages
-arch - Packages known not to work on arch
On Tue, 2003-07-15 at 18:51, Mark Knecht wrote:
On Tue, 2003-07-15 at 15:46, Heschi Kreinick wrote:
~x86
Probably make.conf is the only place that really even mentions them. But
basically, in an ebuild is a list of KEYWORDS. Currently I believe the only
use of KEYWORDS is to define what architectures (sparc, x86, ppc, ...) a
package works on. In your make.profile, make.defaults sets ACCEPT_KEYWORDS
On Mon, 2003-06-09 at 19:06, Brett I. Holcomb wrote:
ebuild has some commands to allow unpacking the source, then compiling and
installing it. Check the Gentoo developer docs on the ebuild system.
Brett,
Thanks for the info. I'll go start looking.
I hope there's a way to do this using
Well, I haven't done any work with ebuilds other than use them and look at
them. I am going to try an ebuild for a program so I've been looking the
docs. If worst comes to worst you can take the existing ALSA ebuild, move it
to a local portage directory (that's explained in the docs), add
On Mon, 2003-06-09 at 19:30, Brett I. Holcomb wrote:
Well, I haven't done any work with ebuilds other than use them and look at
them. I am going to try an ebuild for a program so I've been looking the
docs. If worst comes to worst you can take the existing ALSA ebuild, move it
to a local
60 matches
Mail list logo
