booting my kernel with GRUB

Question about which tools to use, bugs, the best way to implement a function, etc should go here. Don't forget to see if your question is answered in the wiki first! When in doubt post here.
Post Reply
xxchrisxx

booting my kernel with GRUB

Post by xxchrisxx »

I've decided to give GRUB a try but i'm having a few problems.
I did the following:

cat stage1 stage2 > boot
cat boot >/dev/fd0

I compiled my kernel and did:

cat kernel.bin >>/dev/fd0

When it booted it said "Verifying DMI Pool Data......" then just hangs there. It Doesn't seem to read much off the floppy. Worse part is I just tryed to boot back into NetBSD and the PC just reboots and reboots and reboots.... :(

What have I done wrong ?

* url to the kernel source: http://osdev.neopages.net/downloads/tut ... l_grub.zip
User avatar
Solar
Member
Member
Posts: 7615
Joined: Thu Nov 16, 2006 12:01 pm
Location: Germany
Contact:

Re:booting my kernel with GRUB

Post by Solar »

Errors in your kernel can be ruled out, since they wouldn't make your PC reboot after you removed the boot (floppy) disk. (You did remove it, yes?)

So I'd daresay you hit /dev/hd0 instead of /dev/fd0 at some point of the procedure, resulting in a non-functional /dev/fd0 and a mangled /dev/hd0 bootsector.
Every good solution is obvious once you've found it.
User avatar
Pype.Clicker
Member
Member
Posts: 5964
Joined: Wed Oct 18, 2006 2:31 am
Location: In a galaxy, far, far away
Contact:

Re:booting my kernel with GRUB

Post by Pype.Clicker »

what seems weird to me is that 'append to floppy' command ...
doing "cat kernel >>boot" would make sense as the filesystem know how big "boot" was and where appended bytes should go, but on a physical device, i hardly see how it could work ...

And concerning your NetBSD, the best thing to do is probably to get a boot floppy for it (i mean a NetBSD boot floppy) which could have "run the installed system" or something ...

Or maybe trying to boot it with a clean GRUB disk with manually provided commands ...

with little chance, only the bootloader of your harddisk was damaged and the system itself is still available.
Post Reply