On Tue, Apr 7, 2009 at 8:27 AM, Dave Phillips <dlphillips(a)woh.rr.com> wrote:
Mark Knecht wrote:
Is there any reason you really even need the
UUID stuff? Why not dump it?
Hi Mark,
I did try replacing the UUID stuff with direct disk specifications but
got no joy. As it happens, I decided this morning to uninstall the rt
kernel (the one that wouldn't load) and installed a different one
(2.6.24-23-rt). I copied its grub entry from /boot/grub/menu.lst on the
Intrepid partition to /boot/grub/menu.lst on my 64 Studio partition. I
rebooted, selected the new kernel from the grub menu, and voila, it loaded.
When I installed the new kernel I also searched the repo for everything
with 2.6.24-23-rt in its name. I installed some packages I'm sure I did
*not* install for the previous (non-loading) kernel.
So I have a bootable rt kernel for Ubuntu 8.10. Now I have to find the
best settings for Jack, I'm getting too many xruns.
Thanks to everyone who responded. The UUID problem was a reminder to me
that Linux changes constantly. It gets difficult to keep up sometimes, I
appreciate the help here.
Best,
dp
All very strange to me. No problems here on Gentoo with any of the RT
kernels I've tried so far. Note that I've not played with 2.6.29 as
I've seen notable folks like Fernando reporting some problems on the
rt-kernel list, and I just don't feel the need for a new kernel all
that often.
Going back to your original post it seems you never said what kernel
you were trying to boot and then having problems with. What kernel was
it?
Currently it seems you really didn't try to jump that far going from
2.6.24-18 to 2.6.24-23 which is likely why the booting part wasn't an
issue. Is that that your assessment?
Cheers,
Mark