Chrome OS won't boot!

200 views
Skip to first unread message

Caleb Xu

unread,
Jan 26, 2013, 12:11:44 PM1/26/13
to chromium-...@chromium.org
Hello everyone,

First and foremost, I am using the approach of burning a Hexxeh build to a flash drive, then applying to hard drive partitions with Minitool Parititon Maker/other tools that can read the partition table (unlike GParted). I'm doing this with Windows already installed and in use for about four years, so the "easy installation" method is not useful for me, as I don't want to lose the whole drive. I've managed to put all the files in place, and now, the only issue is the boot sequence. Right now, when booting with GRUB4DOS (chainloaded from default Windows bootloader thanks to grldr.mbr to allow dual-booting with Windows), the last error message I see before the PC hangs is:

Code:
[<timecode>] ramoops: request mem region failed
With a bit of research, I've found out what ramoops does, but I still have no knowledge about what to do.

For reference, the ROOT-A partition on my computer is /dev/sda7 and the STATE partition is /dev/sda6. My menu.lst for GRUB4DOS is below to show the parameters I'm giving. I have modified chromeos_startup under ROOT-A/sbin to point towards /dev/sda6 rather than /dev/sda1.

Code:
timeout 0

title Chromium OS
root (hd0,7)
kernel /boot/vmlinuz quiet console=tty2 init=/sbin/init boot=local rootwait ro noresume noswap noinitrd root=LABEL=ROOT-A i915.modeset=1 cros_legacy BOOT_IMAGE=vmlinuz
boot
Thanks in advance for any help I may receive.

Isky Hassan

unread,
Jun 11, 2013, 4:39:29 PM6/11/13
to chromium-...@chromium.org
I haven't gotten my dual boot with Win7 working either, but looking at your menu.lst file, I believe it should say <root (hd0,6)> if your ROOT-A is in /dev/sda7, since the numbering starts from 0, not 1.
Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages