[Techtalk] what the heck does this mean!!

[Miriam English]

Hi Carla,

My first thought is the menu.lst entry that tries to start 64 Studio may 
not be jumping to the right place and crashing. If you want to post the 
relevant lines here (or even the whole menu.lst) I'll see if another set 
of eyes can pick up something wrong. I used to run 64 Studio on a 
partition on my machine and still have all my old menu.lst files.

Cheers,

	- Miriam

Carla Schroder wrote:
> http://bratgrrl.com/wtf.jpg
> 
> Scenario:
> 
> I installed a new motherboard. There are two SATA drives. I have 64 Studio on 
> sda1. The machine starts fine, I can get into the BIOS menu, and it 
> recognizes all the drives and the correct memory. So far so good.
> 
> It goes to the GRUB menu, and then the screen in the photo appears.
> 
> Kubuntu is on sdb1 and boots normally from the same GRUB menu. I used Kubuntu 
> to check the logs on sda1 and they don't show a thing-- they're empty.
> 
> /boot/grub/menu.lst is on sda1.
> 
> I checked all the menu.lst settings and they are correct-- correct initrd, 
> vmlinuz, everything. The partition seems to be healthy, the boot menu is 
> being read and i had no trouble mounting and reading it in Kubuntu. 
> 
> What the heck is all this and what can I do about it? Is there some secret 
> message in all that gobbledegook to tell me how to fix this?
> 
> I have only one 64 Studio kernel so I can't check if it's some kernel 
> weirdness. Only the mobo and the RAM are new.
> 
> thanks,
> Carla

-- 
If you don't have any failures then you're not trying hard enough.
  - Dr. Charles Elachi, director of NASA's Jet Propulsion Laboratory
-----
Website: http://miriam-english.org
Blog: http://miriam_e.livejournal.com