buzzingrobot
April 27th, 2012, 10:40 PM
12.04 64-bit is failing to install here off a CD. I am getting the same "You need to load the kernel first" error that I reported here:http://ubuntuforums.org/showthread.php?t=1964065 about Beta2.
Here's what happens: I insert the CD newly burned on a Mac, and hit reset. It boots into the CD and I see the "Try or Install" menu. Selecting either option, the drive spins up for about 15 seconds, goes quiet, and then I see this:
"error: couldn't read file"
"You need to load the kernel first...Press a key to continue"
If I press a key, it returns to the original "Try or Install" menu. If I don't, it returns by itself. At that point, pressing F-10 to boot, or any other key, has no effect. The machine appears to be locked up.
I have tried editing the Grub options. Nothing has an impact.
I have verified, on multiple CD's, that the iso burned correctly and that the kernels are, in fact, where grub thinks they are.
The install routines on CD's of other distributions work. Only Ubuntu 12.04 does this. Repeatedly.
Has anyone else seen this? Is there a fix? I followed through the beta cycle and now, when I want to do a clean install, it's frustrating to get this error over and over.
Here's what happens: I insert the CD newly burned on a Mac, and hit reset. It boots into the CD and I see the "Try or Install" menu. Selecting either option, the drive spins up for about 15 seconds, goes quiet, and then I see this:
"error: couldn't read file"
"You need to load the kernel first...Press a key to continue"
If I press a key, it returns to the original "Try or Install" menu. If I don't, it returns by itself. At that point, pressing F-10 to boot, or any other key, has no effect. The machine appears to be locked up.
I have tried editing the Grub options. Nothing has an impact.
I have verified, on multiple CD's, that the iso burned correctly and that the kernels are, in fact, where grub thinks they are.
The install routines on CD's of other distributions work. Only Ubuntu 12.04 does this. Repeatedly.
Has anyone else seen this? Is there a fix? I followed through the beta cycle and now, when I want to do a clean install, it's frustrating to get this error over and over.