On Sun, Apr 05, 2009 at 09:09:58AM -0400, Dave Phillips wrote: I notice you have two 'root' lines in above entry. I'm guessing you might try removing the first one. Otherwise, I would suggest going back to the old-style boot logic, at least for verification purposes. /boot/grub/menu.lst: root (hd0,0) /etc/fstab: /dev/sda1 / ext3 relatime,errors=remount-ro 0 1 Booting was never trivial. There is also now a grub/grub2 distinction to learn... HTH -- Joel Roth

Dave Phillips wrote: Hello Dave, I also don't see the problem. So this is when I go back to the basics. I used to have an IDE drive and a SCSI drive in the same box with GRUB only on the SCSI drive and selecting which kernel to boot off of which drive. When moving to Fedora 10, that became a problem because there wasn't enough time delay given to the SCSI drive for SCSI drive recognition during bootup, and so my GRUB files where never loaded and the system hung. The only solution was to pull out the IDE drive and just run with the SCSI drive. [Rant on. Fedora 10 bootup programmers take note, and also take note that you didn't find the floppy drive correctly during bootup either. You achieved a faster bootup time, but at the expense of failing to find drives. I am *not* happy with that trade-off. Rant off.] From what you've shown, it looks like you only have the 1 drive in your box, correct? In the /boot/grub/menu.lst file on the sda drive: The title line is no problem. (this is what I refer to as the "title" block description below.) The root line is no problem. The kernel line and the initrd line are not problems if you have those files where they are stated to be. I'd check your /dev/sda1 boot directory just to be certain that the specified vmlinuz and initrd files are there. On the kernel line, I have the option "rhgb" which I don't know what it means. Might try a boot with "rhgb" as an option. Rather than using the "splash" option on the kernel line, I use the "splashimage" GRUB command. I wouldn't expect it to be a problem for you, but you might want to try a boot without the "splash" option in the kernel line. My splashimage GRUB command looks like this: splashimage=(hd0,0)/boot/grub/splash.xpm.gz I don't use the "savedefault" or the "boot" parameters within the "title" block. You could try removing them. My primary suspect for your problem is the "savedefault" parameter, but I can't tell since you didn't show the "title" blocks for your other kernels. In the GRUB commands section outside of a "title" block (where I use the above splashimage command), I comment out the hiddenmenu command so that I can see all of the kernels I wish to boot. Also in the GRUB commands section I use the default command, rather than the "savedefault" option in a "title" block. I use: default=0 where 0 is the first "title" block, 1 is the next "title block, and so on. And it's a good idea to specify a timeout command in the GRUB command section. I'm using: timeout=4 to allow one 4 seconds to select which kernel you wish to boot before GRUB will take the default=x "title" block to boot. For what it's worth. Good luck. Stephen.

On Tue, Apr 7, 2009 at 8:27 AM, Dave Phillips <dlphillips(a)woh.rr.com> wrote: For the xrun issue, try stopping networkmanager, that has done wonders for me on ubuntu machines, and if you know how to set up a network connection without it running, all the better for your machine's performance.

Mark Knecht wrote: Hi Mark, The recap: I began by building and installing a 2.6.26 rt kernel. It wouldn't load, just aborted with the UUID error. I decided to install an Ubuntu-sanctified kernel, 2.6.24-18-rt, when it appeared in the repo. Alas, I got the same error when I tried to load that one. After much head-scratching, I gave up this morning and installed 2.6.24-23-rt, and it works. AFAICT maybe I missed installing a modules package ? But that doesn't explain why my home-brew kernel wouldn't load. Best, dp