Kernel 2.6.5 one-time boots and a Q about System.map

[Stormmind]

I've searched but haven't found anything similar. I'm doing a clean install
on a PPro 200Mgh box using 2004 universal-cd. Everything seemed to be
going fine, I compiled 2.6.5 and placed all of it under boot and rebooted.
All seemed fine even now, 2.6.5 booted, gentoo started, but eth1 and eth0
swapped places, but I knew why and fixed it and rebooted again. This time
the kernel failed to boot. Grub found it and started it, then nothing happened
for a second and then the box restarted. I checked grub.conf but it seemed
fine, recompiled it a couple of times, but it still wouldn't boot. I then emerged
and compiled 2.4 sources but after placing it all in boot, I decided to try to
load 2.6 anyway and lo - it booted! But next time I rebooted it failed again!
I tryed booting 2.4 and it booted fine even after rebooting =)

I am baffled and don't know where to look. The weird thing is that it boots
fine once, but doesn't want to boot anymore after that. Maybe I forgot to
set "boot more than once"-flag somewhere? =P

Any help would be greatly appreciated!

Oh yes, and about System.map. Do you have to use different System.maps
for different kernels? 2.4 seems to boot fine with a 2.6 system.map and
since you don't write it in grub, I guess it doesn't matter. But it seems
fishy to me. What's a system.map anyway?

// Storm

[kopfsalat]

Don't know much about grub. Maybe you should try out Lilo to see if it is really a problem with grub.

Could be a dying harddisk or some strange kernel misconfiguration. Watch out for i/o errors or other warnings with

[Stormmind]

You didn't actually read my post, did you? My grub is fine as it actually tryes
to load the kernel. Also, if I use 2.4 kernel, it boots fine, nothing is wrong.
But 2.6 REBOOTS without even starting to load! It means it doesn't even
look for any harddrives! It doesn't give any output at all, just reboots!
So I can't really check dmesg or systemlogs, can I? =/

I agree it could be a misconfiguration, but the weird thing that it managed
to boot fine at least ONCE! Actually twice, after I tweaked around. But as soon
as I reboot, it fails again! In case it can be interesting, here's a link to my config.

Well, thanks for the reply!

Cheers!