[PlanetCCRMA] FC2 "experimental" kernel install dependency error
Brad Fuller
brad@sonaural.com
Thu Nov 4 12:00:04 2004
This is a multi-part message in MIME format.
--------------060703060002060809020400
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Brad Fuller wrote:
> Ok, I got the kernel 2.6.7-1.437.1.11.rhfc2.ccrma loaded.
> Unfortunately, Xwindows didn't start up. I had to change the
> nvidia6111 driver to the older one -- and then X started up. Why would
> this be? I was going to install 6111 again -- the nvidia installer
> said it was already installed (thought maybe there was some
> interaction between this kernel and nvidia6111.)
>
> Anyone come across this?
>
> brad
>
I take that back about the kernel. I did load it successfully (at least
the logs don't say there are problems) but:
# cat /proc/sys/kernel/lowlatency
replies:
cat: /proc/sys/kernel/lowlatency: No such file or directory
so, jackstart doesn't start. of course.
Note that this is NOT from the experimental repos. Perhaps I should try
these, Fernando? You did mention below that these have had more
success. Still...I do wonder why I don't have lowlatency.
Any ideas where to look?
(I do have "kernel.lowlatency=1" in /etc/sysctl.conf)
brad
> Fernando Pablo Lopez-Lezcano wrote:
>
>>On Wed, 2004-11-03 at 22:43, Brad Fuller wrote:
>>
>>
>>>Tried to install the new FC2 ccrma kernel:
>>>
>>># apt-get install planetccrma-core
>>>
>>>but received a conflict that
>>>
>>>
>>>
>>>>file /usr/lib/libasound.so.2.0.0 from install of
>>>>
>>>>
>>>alsa-lib-1.0.5-1.cvs.rhfc2.ccrma conflicts with file from package
>>>libasound2.1.0.6-16.rhfc2.at
>>>
>>>
>>
>>That's a conflict caused by unfortunate non-standard naming of the alsa
>>library packages at atrpms. I should (will in the next release) include
>>an "Obsoletes:" clause for them, but the proper fix will be for atrpms
>>to return to the "standard" naming of those packages ("standard" as in
>>"what all others do, including the base redhat/fedora distribution").
>>
>>
>>
>>>A LOT of packages depend on the libasound2.10.06. Any way to get
>>>around this?
>>>
>>>
>>
>>You can either install the planetccrma-core critical components one by
>>one, or get rid of the libasound2 packages and replace them by the
>>equivalent alsa-lib packages (BTW, is there an explicit dependency on
>>libasound2?, there should not be one, try "rpm -q --whatrequires
>>libasound2").
>>
>>For the first option, do an "apt-get install kernel" and you will see
>>the choices you have. The most conservative one for fc2 will be
>>kernel#2.6.7-1.437.1.ll.rhfc2.ccrma (that is the one "required" by
>>planetccrma-core), there are other more experimental kernels in the
>>"planetedge" repository. Those have better low latency performance but
>>are riskier to run[*].
>>
>>I posted this a while ago:
>>
>>
>>>The best kernels I currently have for 2.6 are in the "experimental"
>>>repository, they have to be installed explicitly (not through a meta
>>>package), and they are only advertised in the mailing list.
>>>
>>>Check this post for information on current latest bleeding edge
>>>kernel:
>>>http://ccrma-mail.stanford.edu/pipermail/planetccrma/2004-August/005879.html
>>>And follow the link inside for more details...
>>>
>>>Remember that before trying the apt-get install xxx. you have to add
>>>another line to the /etc/apt/sources.list (same as the planetcore
>>>line, but replacing planetcore with planetedge), and do an apt-get
>>>update.
>>>
>>>
>>
>>If you install either (edge or conservative), you also have available a
>>newer alsa than the one included in the kernel itself, for that do an:
>>
>>apt-get install kernel-module-alsa
>>
>>and again you will get choices. Explicitly install the one that matches
>>the kernel you just installed.
>>
>>-- Fernando
>>
>>[*] I was hoping that by now the experimental voluntary-preempt patches
>>for very good low latency performance would have stabilized a lot, but
>>another approach was taken by Ingo Molnar and we now have a very new
>>"realtime-preempt" patch that promises to be even better. Regretfully it
>>is still quite unstable. I'm trying it out regularly and trying to
>>follow its development but I have not posted experimental packages yet
>>(let me know if any on the list needs to be a guinea pig).
>>
>>
>>_______________________________________________
>>PlanetCCRMA mailing list
>>PlanetCCRMA@ccrma.stanford.edu
>>http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma
>>
>>
>>
>>
--------------060703060002060809020400
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">
Brad Fuller wrote:
<blockquote cite="mid418A81BA.8070802@sonaural.com" type="cite">
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<font size="-1"><font face="Helvetica, Arial, sans-serif">Ok, I got
the
kernel 2.6.7-1.437.1.11.rhfc2.ccrma loaded. Unfortunately, Xwindows
didn't start up. I had to change the nvidia6111 driver to the older one
-- and then X started up. Why would this be? I was going to install
6111 again -- the nvidia installer said it was already installed
(thought maybe there was some interaction between this kernel and
nvidia6111.)<br>
<br>
Anyone come across this?<br>
<br>
brad<br>
</font></font><br>
</blockquote>
I take that back about the kernel. I did load it successfully (at least
the logs don't say there are problems) but:<br>
<br>
# cat /proc/sys/kernel/lowlatency <br>
<br>
replies:<br>
<br>
cat: /proc/sys/kernel/lowlatency: No such file or directory<br>
<br>
so, jackstart doesn't start. of course.<br>
<br>
Note that this is NOT from the experimental repos. Perhaps I should try
these, Fernando? You did mention below that these have had more
success. Still...I do wonder why I don't have lowlatency.<br>
<br>
Any ideas where to look?<br>
<br>
(I do have "kernel.lowlatency=1" in /etc/sysctl.conf)<br>
<br>
brad<br>
<br>
<blockquote cite="mid418A81BA.8070802@sonaural.com" type="cite">Fernando
Pablo Lopez-Lezcano wrote:
<blockquote cite="mid1099590392.1753.20.camel@cmn37.stanford.edu"
type="cite">
<pre wrap="">On Wed, 2004-11-03 at 22:43, Brad Fuller wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Tried to install the new FC2 ccrma kernel:
# apt-get install planetccrma-core
but received a conflict that
</pre>
<blockquote type="cite">
<pre wrap="">file /usr/lib/libasound.so.2.0.0 from install of
</pre>
</blockquote>
<pre wrap="">alsa-lib-1.0.5-1.cvs.rhfc2.ccrma conflicts with file from package
libasound2.1.0.6-16.rhfc2.at
</pre>
</blockquote>
<pre wrap=""><!---->
That's a conflict caused by unfortunate non-standard naming of the alsa
library packages at atrpms. I should (will in the next release) include
an "Obsoletes:" clause for them, but the proper fix will be for atrpms
to return to the "standard" naming of those packages ("standard" as in
"what all others do, including the base redhat/fedora distribution").
</pre>
<blockquote type="cite">
<pre wrap="">A LOT of packages depend on the libasound2.10.06. Any way to get
around this?
</pre>
</blockquote>
<pre wrap=""><!---->
You can either install the planetccrma-core critical components one by
one, or get rid of the libasound2 packages and replace them by the
equivalent alsa-lib packages (BTW, is there an explicit dependency on
libasound2?, there should not be one, try "rpm -q --whatrequires
libasound2").
For the first option, do an "apt-get install kernel" and you will see
the choices you have. The most conservative one for fc2 will be
kernel#2.6.7-1.437.1.ll.rhfc2.ccrma (that is the one "required" by
planetccrma-core), there are other more experimental kernels in the
"planetedge" repository. Those have better low latency performance but
are riskier to run[*].
I posted this a while ago:
</pre>
<blockquote type="cite">
<pre wrap="">The best kernels I currently have for 2.6 are in the "experimental"
repository, they have to be installed explicitly (not through a meta
package), and they are only advertised in the mailing list.
Check this post for information on current latest bleeding edge
kernel:
<a class="moz-txt-link-freetext"
href="http://ccrma-mail.stanford.edu/pipermail/planetccrma/2004-August/005879.html">http://ccrma-mail.stanford.edu/pipermail/planetccrma/2004-August/005879.html</a>
And follow the link inside for more details...
Remember that before trying the apt-get install xxx. you have to add
another line to the /etc/apt/sources.list (same as the planetcore
line, but replacing planetcore with planetedge), and do an apt-get
update.
</pre>
</blockquote>
<pre wrap=""><!---->
If you install either (edge or conservative), you also have available a
newer alsa than the one included in the kernel itself, for that do an:
apt-get install kernel-module-alsa
and again you will get choices. Explicitly install the one that matches
the kernel you just installed.
-- Fernando
[*] I was hoping that by now the experimental voluntary-preempt patches
for very good low latency performance would have stabilized a lot, but
another approach was taken by Ingo Molnar and we now have a very new
"realtime-preempt" patch that promises to be even better. Regretfully it
is still quite unstable. I'm trying it out regularly and trying to
follow its development but I have not posted experimental packages yet
(let me know if any on the list needs to be a guinea pig).
_______________________________________________
PlanetCCRMA mailing list
<a class="moz-txt-link-abbreviated"
href="mailto:PlanetCCRMA@ccrma.stanford.edu">PlanetCCRMA@ccrma.stanford.edu</a>
<a class="moz-txt-link-freetext"
href="http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma">http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma</a>
</pre>
</blockquote>
</blockquote>
</body>
</html>
--------------060703060002060809020400--