[PlanetCCRMA] alsa-driver upgrade -- synaptic and planetccrma-core

Wed Dec 22 13:55:02 2004

This is a multi-part message in MIME format.
--------------080906090402030406050605
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

fonse006 wrote:

>>===== Original Message From Brad Fuller <brad@sonaural.com> =====
>>Why, when in synaptic, when I select alsa-driver 1.0.6 to be upgraded
>>synaptic replies:
>>
>>To be removed:
>>   planetccrma-core
>>
>>I'm using the 2.6.7-1.437.1.11.rhfc2.ccrma kernel from planetedge
>>
>>Looking in the planetccrma changelog, I take it that there is some link,
>>or some stub or something builtin to this core connecting it with ALSA
>>1.0.5? Is that right? How does this actually work?
>>Is there a map of core's built, or a diagram of the architecture of
>>these builds? (Frankly Fernando, I don't know how you keep this all
>>straight. Kudos to you! You definitely have a remarkable skill)
>>
>>any clues for the clueless would be appreciated!
>>
>>brad
>>
>>--
>>
>>    
>>
>I am not that great at describing this but here goes.  First thing first, alsa 
>is part of the kernel.  Specifically, alsa is a set of kernel modules that are 
>compiled against a specific kernel tree.  Rpm is a package management system 
>that packages precompiled binary object files along with a list of 
>dependencies.  If your system does not meet all of the dependencies then rpm 
>will not let you install the file.  Apt-get is a program that keeps track of 
>repositories of pre packaged binaries (In planet ccrma's case rpm is the 
>package management, there are several other systems for linux).  Anyway, what 
>happens when you try to upgrade to the newer alsa is apt, through invoking 
>rpm, checks the to see that you have the required files on your computer.  If 
>you do it downloads them and invokes rpm --install which as I am sure you can 
>guess, installs the package.  If you do not meet the dependencies then apt 
>tries to see if it can find the required package or packages in its list of 
>repositories.  If it can, it will tell you that you need to update various 
>packages, if not then, hmmmm I am not really sure what happens then, but I 
>assume it tells you that you cannot upgrade.  
>>From my perspective there are two options that you can take (that will not be 
>more trouble than they are worth).  First and easiest, install the kernel 
>version and other files that go with the new alsa.  I would suggest that if 
>you go this route do not check upgrade on the packages, check install just in 
>case your system does not boot with the new core.  Second and not much harder, 
>download and install the src rpm for your kernel, then the source for the alsa 
>version you want and follow the directions on the alsa website to compile the 
>alsa modules against your kernel version, install the new version remove the 
>old and your set.
>I hope that helps you out.
>
>Adam
>  
>
Thanks Adam. I know how apt/synaptic/yum and rpm work. I was wondering 
what the relationship of ALSA and the kernel is -- sorry I wasn't clear 
on that.  I need to re-read my emails!

>Where is that upgrade coming from 
>
ccrma

>(BTW, thanks to fonse006 for the
>explanation). You can do an "apt-cache policy alsa-driver" to see which
>package is selected and why. 
>  
>
Ok. As I think I mentioned: I have 1.0.5a-1.cvs.rhfc2.ccrma installed 
with 1.0.6a.... as a candidate

>The planetccrma-core packages are empty. They just make sure you have a
>coherent set of packages installed for the kernel and alsa through
>requirements. Do a "rpm -q --requires planetccrma-core" to see what I
>mean). 
>
Got it.
Ok, so I still don't understand the alsa module issue as far as the 
kernel (which is probably a better question on the ALSA list and for me 
to do some reading on the ALSA site, I admit.... but)
There is the kernel-module-alsa which has the same versioning of the 
kernel AND which states is equal to the version of alsa installed (which 
I take it as not actually equal to, but is the actual version of the 
alsa kernal module installed and integrated (still unsure of this) with 
the kernel.)

# rpm -q --requires planetccrma-core
kernel-2.6.7-1.437.1.11.rhfc2.ccrma-i686
kernel-module-alsa-kernel-2.6.7-1.437.1.11.rhfc2.ccrma-i686 = 
1.0.5a-1.cvs.rhfc2.ccrma
<....more... alsa... module... listing>

Is this kernel module actually compiled in with the kernel -- making it 
an integral part of the kernel?
And, the other alsa modules *not* in the kernel but are dependent on 
this kernel module (thus, why it is the same version.).

If this is all true, then it would appear to me that I would have to 
first update an appropriate kernel  and one that would incorporate the 
alsa kernel module.

#apt-get install kernel

results in many kernels. How would one know what is the latest that 
supports the latest alsa? I'm sure there is a command for this too. I am 
happy that I remembered the one above! :-)

brad

--------------080906090402030406050605
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
fonse006 wrote:
<blockquote cite="mid41C939E0@wm6.csusm.edu" type="cite">
  <blockquote type="cite">
    <pre wrap="">===== Original Message From Brad Fuller <a class="moz-txt-link-rfc2396E" href="mailto:brad@sonaural.com">&lt;brad@sonaural.com&gt;</a> =====
Why, when in synaptic, when I select alsa-driver 1.0.6 to be upgraded
synaptic replies:

To be removed:
   planetccrma-core

I'm using the 2.6.7-1.437.1.11.rhfc2.ccrma kernel from planetedge

Looking in the planetccrma changelog, I take it that there is some link,
or some stub or something builtin to this core connecting it with ALSA
1.0.5? Is that right? How does this actually work?
Is there a map of core's built, or a diagram of the architecture of
these builds? (Frankly Fernando, I don't know how you keep this all
straight. Kudos to you! You definitely have a remarkable skill)

any clues for the clueless would be appreciated!

brad

--

    </pre>
  </blockquote>
  <pre wrap=""><!---->I am not that great at describing this but here goes.  First thing first, alsa 
is part of the kernel.  Specifically, alsa is a set of kernel modules that are 
compiled against a specific kernel tree.  Rpm is a package management system 
that packages precompiled binary object files along with a list of 
dependencies.  If your system does not meet all of the dependencies then rpm 
will not let you install the file.  Apt-get is a program that keeps track of 
repositories of pre packaged binaries (In planet ccrma's case rpm is the 
package management, there are several other systems for linux).  Anyway, what 
happens when you try to upgrade to the newer alsa is apt, through invoking 
rpm, checks the to see that you have the required files on your computer.  If 
you do it downloads them and invokes rpm --install which as I am sure you can 
guess, installs the package.  If you do not meet the dependencies then apt 
tries to see if it can find the required package or packages in its list of 
repositories.  If it can, it will tell you that you need to update various 
packages, if not then, hmmmm I am not really sure what happens then, but I 
assume it tells you that you cannot upgrade.  
&gt;From my perspective there are two options that you can take (that will not be 
more trouble than they are worth).  First and easiest, install the kernel 
version and other files that go with the new alsa.  I would suggest that if 
you go this route do not check upgrade on the packages, check install just in 
case your system does not boot with the new core.  Second and not much harder, 
download and install the src rpm for your kernel, then the source for the alsa 
version you want and follow the directions on the alsa website to compile the 
alsa modules against your kernel version, install the new version remove the 
old and your set.
I hope that helps you out.

Adam
 </pre>
</blockquote>
Thanks Adam. I know how apt/synaptic/yum and rpm work. I was wondering
what the relationship of ALSA and the kernel is -- sorry I wasn't clear
on that.&nbsp; I need to re-read my emails! 
 
<blockquote type="cite">
 <pre wrap="">Where is that upgrade coming from </pre>
</blockquote>
ccrma 
 
<blockquote type="cite">
 <pre wrap="">(BTW, thanks to fonse006 for the
explanation). You can do an "apt-cache policy alsa-driver" to see which
package is selected and why. 
 </pre>
</blockquote>
Ok. As I think I mentioned: I have 1.0.5a-1.cvs.rhfc2.ccrma installed
with 1.0.6a.... as a candidate 
 
<blockquote type="cite">
 <pre wrap="">The planetccrma-core packages are empty. They just make sure you have a
coherent set of packages installed for the kernel and alsa through
requirements. Do a "rpm -q --requires planetccrma-core" to see what I
mean). </pre>
</blockquote>
Got it. 
Ok, so I still don't understand the alsa module issue as far as the
kernel (which is probably a better question on the ALSA list and for me
to do some reading on the ALSA site, I admit.... but) 
There is the kernel-module-alsa which has the same versioning of the
kernel AND which states is equal to the version of alsa installed
(which I take it as not actually equal to, but is the actual version of
the alsa kernal module installed and integrated (still unsure of this)
with the kernel.) 
 
# rpm -q --requires planetccrma-core 
kernel-2.6.7-1.437.1.11.rhfc2.ccrma-i686 
kernel-module-alsa-kernel-2.6.7-1.437.1.11.rhfc2.ccrma-i686 =
1.0.5a-1.cvs.rhfc2.ccrma 
&lt;....more... alsa... module... listing&gt; 
 
Is this kernel module actually compiled in with the kernel -- making it
an integral part of the kernel? 
And, the other alsa modules *not* in the kernel but are dependent on
this kernel module (thus, why it is the same version.). 
 
If this is all true, then it would appear to me that I would have to
first update an appropriate kernel&nbsp; and one that would incorporate the
alsa kernel module. 
 
#apt-get install kernel 
 
results in many kernels. How would one know what is the latest that
supports the latest alsa? I'm sure there is a command for this too. I
am happy that I remembered the one above! :-) 
 
brad 
</body>
</html>

--------------080906090402030406050605--