29 Jul
2004
29 Jul
'04
3:20 p.m.
Hi,
I wonder if anyone has a pointer to any web instructions on how to
replace an Alsa driver that has gotten broken in a new kernel release.
My ATIIXP sound chip has worked fine for months but suddenly it's broken
in a number of 2.6.7 kernels as well as 2.6.8-rc2. It appears that a
broken driver was released without testing, if I understand the Alsa Bug
Tracker correctly. Now there are comments about replacing the driver in
the kernel with the driver from CVS. I don't know how to do this.
Sorry for bringing this issue here but I'm hoping to get a simple
answer before I go join yet another mailing list for a one time event.
Thanks in advance,
Mark
29 Jul
29 Jul
3:50 p.m.
On Thu, Jul 29, 2004 at 10:05:30AM -0700, Mark Knecht wrote:
Hi,
I wonder if anyone has a pointer to any web instructions on how to
replace an Alsa driver that has gotten broken in a new kernel release.
My ATIIXP sound chip has worked fine for months but suddenly it's broken
in a number of 2.6.7 kernels as well as 2.6.8-rc2. It appears that a
broken driver was released without testing, if I understand the Alsa Bug
Tracker correctly. Now there are comments about replacing the driver in
the kernel with the driver from CVS. I don't know how to do this.
Sorry for bringing this issue here but I'm hoping to get a simple
answer before I go join yet another mailing list for a one time event.
In the kernel config, enable 'Sound card support' but disable ALSA, then
download the alsa-driver package from alsa-project.org and compile and
install it seperately.
cheers,
Christian
--
"Somewhere in Texas... a village is missing its idiot."
4:13 p.m.
Christian Henz wrote:
On Thu, Jul 29, 2004 at 10:05:30AM -0700, Mark Knecht
wrote:
Christian,
Thanks, but this would seem to build Alsa CVS, but not just replace
an existing driver within the kernel that I'm running. (This was the
instruction given within a bug report on the Alsa site for the problem
I'm having.) Not sure how Gentoo is going to feel about this, but I'll
consider it. Thanks.
This is not the same as what I found on the Alsa web site from
Jaroslav, which seems to say I should download CVS, then move a driver :
<SNIP>
Updating ALSA Kernel drivers
12/09/03
Hi,
I wonder if anyone has a pointer to any web instructions on how to
replace an Alsa driver that has gotten broken in a new kernel release.
My ATIIXP sound chip has worked fine for months but suddenly it's broken
in a number of 2.6.7 kernels as well as 2.6.8-rc2. It appears that a
broken driver was released without testing, if I understand the Alsa Bug
Tracker correctly. Now there are comments about replacing the driver in
the kernel with the driver from CVS. I don't know how to do this.
Sorry for bringing this issue here but I'm hoping to get a simple
answer before I go join yet another mailing list for a one time event.
In the kernel config, enable 'Sound card support' but disable ALSA, then
download the alsa-driver package from alsa-project.org and compile and
install it seperately.
cheers,
Christian
Some queries about the latest 2.6 kernels...
I presume the "alsa" part that comes with a 2.6 kernel is only
the equiv of the alsa-driver package so do I still need to get
alsa-lib and alsa-utils from somewhere else ?
Yes, from our main site - http://www.alsa-project.org .
If so, then do I have to determine which particular
version is
in the kernel and then source the same versioned lib/utils packages ?
Version is available in linux/include/sound/version.h
What is the difference between /usr/include/sound/*
and
/usr/src/linux/include/sound/* and where might ""
be that some packages need for compiling ?
ALSA library has a copy of kernel header files and it is backwards
compatible with ALSA code 0.9 final (which is also in the 2.6 kernel
tree). In other words, you can use 1.0 packages without any problems.
Is there some sane method to intergrate ALSA from CVS
into whatever
is the latest 2.6 kernel source tree... how ?
ftp://ftp.alsa-project.org/pub/kernel-patches .
or (use BitKeeper):
bk pull http://linux-sound.bkbits.net/linux-sound
or
simply copy files from the ALSA's alsa-kernel CVS module to relevant
locations in the 2.6 kernel tree.
Jaroslav
-----
Jaroslav Kysela
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs
<SNIP>
Thanks,
Mark
5:21 p.m.
On Thu, Jul 29, 2004 at 10:57:22AM -0700, Mark Knecht wrote:
Christian Henz wrote:
I'm a bit out of the loop lately, but this bit got me when I tried to do
this with 2.6.x ... I wasn't easily able to figure out what the
"relevant locations" should be. Has this been explained since Jaroslav
sent that mail?
-Eric Rz.
On Thu, Jul 29, 2004 at 10:05:30AM -0700, Mark
Knecht wrote:
>Hi,
ftp://ftp.alsa-project.org/pub/kernel-patches .
or (use BitKeeper):
bk pull http://linux-sound.bkbits.net/linux-sound
or
simply copy files from the ALSA's alsa-kernel CVS module to relevant
locations in the 2.6 kernel tree.
5:38 p.m.
On Thu, Jul 29, 2004 at 10:57:22AM -0700, Mark Knecht wrote:
Christian,
Thanks, but this would seem to build Alsa CVS, but not just replace
an existing driver within the kernel that I'm running. (This was the
instruction given within a bug report on the Alsa site for the problem
I'm having.) Not sure how Gentoo is going to feel about this, but I'll
consider it. Thanks.
Not just CVS, you can use any alsa-driver release. I remember
doing this when the in-kernel ALSA was still lagging behind the standalone
releases and it worked just fine, and it is actually much more straightforward
than patching the kernel to use a different version of alsa. After disabling
ALSA in the kernel config, you build alsa-driver seperately, just like one
does with any driver that isn't included in the kernel.
This is not the same as what I found on the Alsa
web site from
Jaroslav, which seems to say I should download CVS, then move a driver :
Yes, that way you actually patch the kernel tree with a different alsa-driver
release, but the results are more or less the same, only with more effort
(and even more effort if you just want to modify that one driver of yours).
cheers,
Christian
--
"Somewhere in Texas... a village is missing its idiot."
5:35 p.m.
On Thursday 29 July 2004 01:05 pm, Mark Knecht wrote:
Hi,
I wonder if anyone has a pointer to any web instructions on how to
replace an Alsa driver that has gotten broken in a new kernel release.
My ATIIXP sound chip has worked fine for months but suddenly it's broken
in a number of 2.6.7 kernels as well as 2.6.8-rc2. It appears that a
broken driver was released without testing, if I understand the Alsa Bug
Tracker correctly. Now there are comments about replacing the driver in
the kernel with the driver from CVS. I don't know how to do this.
Sorry for bringing this issue here but I'm hoping to get a simple
answer before I go join yet another mailing list for a one time event.
Have you eliminated the possibility that the module options changed?
Updating the driver is pretty straightforward, but what you have to do depends
on what your options are. By that I mean your distro should have sources to
build a package. It saves a little bit of aggravation over upgrading from
tarball (not much, but some).
In a nutshell, you turn off everything under Sound in the kernel cfg except
the very top level module, then build/install the ALSA drivers from the
not-the-kernel-sources. Once thats done you have to configure the module
loading and init script for the specifics.
Thanks in advance,
Mark
30 Jul
30 Jul
6:07 p.m.
Mark Knecht schrieb:
Hi,
I wonder if anyone has a pointer to any web instructions on how to
replace an Alsa driver that has gotten broken in a new kernel release.
My ATIIXP sound chip has worked fine for months but suddenly it's
broken in a number of 2.6.7 kernels as well as 2.6.8-rc2. It appears
that a broken driver was released without testing, if I understand the
Alsa Bug Tracker correctly. Now there are comments about replacing the
driver in the kernel with the driver from CVS. I don't know how to do
this.
This is how I replace the alsa stuff in the kernel source:
1. checkout the "alsa-kernel" module from the alsa-project cvs. Go to
http://alsa-project.org/download.php for instructions.
2. cd into the kernel tld
3. move the sound/oss dir to some safe location
4. remove the "sound" directory
5. copy the checked out "alsa-kernel" dir into the kernel tld and rename
it "sound"
6. remove "sound/oss" directory
7. move the "oss" dir from step 3 back into the "sound" dir
8. remove include/sound
9. move sound/include dir into the include dir.
10. unless I missed something you can now build and install kernel as usual.
hth
6:41 p.m.
On Fri, 2004-07-30 at 15:53, Stefan Scheffler wrote:
Mark Knecht schrieb:
This is way more complicated than necessary. You do not need to
recompile or reinstall the kernel to update your ALSA modules.
1. Compile the kernel with these settings:
CONFIG_SOUND=y
# CONFIG_SND is not set
# CONFIG_SOUND_PRIME is not set
For menuconfig users that's Sound card support -> Y, ALSA and OSS
support both N.
2. Check out ALSA cvs sources, using 'cvs co .', once your CVSROOT is
set correctly.
3. Run './build prep'. This generates the ./configure scripts.
4. cd to alsa-driver
5. Run ./configure --with-cards=atiixp, make, make install.
That is all. You do not have to touch your kernel source tree at all.
Lee
Hi,
I wonder if anyone has a pointer to any web instructions on how to
replace an Alsa driver that has gotten broken in a new kernel release.
My ATIIXP sound chip has worked fine for months but suddenly it's
broken in a number of 2.6.7 kernels as well as 2.6.8-rc2. It appears
that a broken driver was released without testing, if I understand the
Alsa Bug Tracker correctly. Now there are comments about replacing the
driver in the kernel with the driver from CVS. I don't know how to do
this.
This is how I replace the alsa stuff in the kernel source:
1. checkout the "alsa-kernel" module from the alsa-project cvs. Go to
http://alsa-project.org/download.php for instructions.
2. cd into the kernel tld
3. move the sound/oss dir to some safe location
4. remove the "sound" directory
5. copy the checked out "alsa-kernel" dir into the kernel tld and rename
it "sound"
6. remove "sound/oss" directory
7. move the "oss" dir from step 3 back into the "sound" dir
8. remove include/sound
9. move sound/include dir into the include dir.
10. unless I missed something you can now build and install kernel as usual.
7:03 p.m.
Lee Revell schrieb:
On Fri, 2004-07-30 at 15:53, Stefan Scheffler wrote:
This is way more complicated than necessary.
I like it complicated. :P
You do not need to
recompile or reinstall the kernel to update your ALSA module's.
I prefer to have most stuff I regulary use or that doesn't change often,
compiled into the kernel. Thats not possible when using alsa-driver.
7468
days inactive
7469
days old
linux-audio-user@lists.linuxaudio.org
8 comments
6 participants
participants (6)
-
Christian Henz -
Eric Dantan Rzewnicki -
John Check -
Lee Revell -
Mark Knecht -
Stefan Scheffler