Kernel version determination
My real question, I guess, is "where does
See my problem? It has utterly stumped me. Any suggestions on how I can get the machine into a coherent state?
<edit>
See the comments for the whole story. The machine in question is PXE booting first, and then booting the vmlinuz from the hard drive. Except it's not, and the PXE kernel is still active after "booting" the hard drive, and that causes all kinds of confusion.
When I take the LAN card out of the boot sequence, with the BIOS, and boot the machine, GRUB loads, and fails to boot (even after I corrected
... then the machine boots the right kernel just fine.
I think the copy of GRUB that's being started at boot time is not the copy of GRUB that's pointing at the
I'm open to all suggestions on diagnostic or recovery steps.
</edit>
<edit again>
I found this, which put me on the right track to solving the problem, which in my case was a simple as typing
Now, I need to fix my PXE server, because it's obviously laying down something quite wrong to blank PXE clients.
</edit>
Thanks for your time,
uname get its information from?". However, I think some background might be relevant for helping you see what's actually bugging me...host:~ # modprobe
modprobe: Can't open dependencies file /lib/modules/2.4.2-178-POS_IBM/modules.d
host:~ # ls /lib/modules
. .. 2.4.21-204-POS_IBM misc
host:~ # uname -rv
2.4.21-178-POS_IBM #1 Wed Jan 14 16:04:41 UTC 2004
host:~ # cat /boot/grub/menu.lst
timeout 0
title linux
kernel (hd0,1)/boot/vmlinuz root=/dev/hda2 acpi=off
host:~ # strings /boot/vmlinuz |grep 2.4.21
2.4.21-204-POS_IBM (root@f160) #1 Wed Sep 8 15:11:11 UTC 2004See my problem? It has utterly stumped me. Any suggestions on how I can get the machine into a coherent state?
<edit>
See the comments for the whole story. The machine in question is PXE booting first, and then booting the vmlinuz from the hard drive. Except it's not, and the PXE kernel is still active after "booting" the hard drive, and that causes all kinds of confusion.
When I take the LAN card out of the boot sequence, with the BIOS, and boot the machine, GRUB loads, and fails to boot (even after I corrected
/boot/grub/menu.lst to point at (hd0,2) and /dev/hda3), though if I manually type in ...GRUB> kernel (hd0,2)/boot/vmlinuz root=/dev/hda3 acpi=offGRUB> boot... then the machine boots the right kernel just fine.
I think the copy of GRUB that's being started at boot time is not the copy of GRUB that's pointing at the
menu.lst file that I've been tampering with.I'm open to all suggestions on diagnostic or recovery steps.
</edit>
<edit again>
I found this, which put me on the right track to solving the problem, which in my case was a simple as typing
grub-install /dev/hda after manually booting with the above GRUB commands.Now, I need to fix my PXE server, because it's obviously laying down something quite wrong to blank PXE clients.
</edit>
Thanks for your time,
