|
|
Nido
|
Hello,
After a very long gap of 6 years,I'm back working on Linux machines.. the first task I got is to compile and run 2.6.31.x.
I followed the steps mentioned in the README file in kernel source and also took referrence to some of the sites.
I am able to compile the kernel and is under /boot.
I can see files: vmlinuz-2.6.31.5, System.map-2.6.31.5,initrd-2.6.31.5.img under /boot and corresponding entries in /boot/grub/grub.conf as updated by install.sh under ../arch/x86/boot
Here is my problem:Kernel boot hangs at boot after initrd message (before decompressing kernel).
Is my problem similar to what is in the below url :https://bugzilla.redhat.com/show_bug.cgi?id=144050
I'm running RHEL AS release 4 (Nahant Update 4)2.6.9-42.ELsmp.
Please let me know how to fix it.
Thanks as always!!
|
|
|
Note: If you are the author of this question and wish to assign points to any of the answers, please login first.For more information on assigning points ,click
here
|
|
|
Sort Answers By:
Date or Points
|
|
Goran Koruga
|
|
Nov 5, 2009 06:17:23 GMT
4 pts
|
|
Hello.
Do you see "BIOS EBDA" or "Linux version 2.6.x.y" line after that? Do you perhaps use "quiet" boot option?
Regards,
Goran |
|
|
Nido
|
|
Nov 5, 2009 06:31:14 GMT
N/A: Question Author
|
|
>>Do you see "BIOS EBDA" or "Linux version 2.6.x.y" line after that? Do you perhaps use "quiet" boot option?
Thanks for quicker reply.
It hangs just after initrd before decompressing kernel and don't show any message.
btw: I've loaded RHEL on VMware Machines, and checked on one of my HP and IBM Machines both shows same result :-(
-P.Naidu |
|
|
Goran Koruga
|
|
Nov 5, 2009 07:02:13 GMT
3 pts
|
|
Hi.
Then you should recheck your kernel config - those are the first things that should be printed and they occur very early in the boot.
Curious - did you forget to include support for VGA console or somesuch? Or maybe left it modularized.
Maybe you should start with RH's kernel config and tweak it when you know it works.
Regards,
Goran |
|
|
Nido
|
|
Nov 5, 2009 07:27:01 GMT
N/A: Question Author
|
|
Hi Again,
>>>Curious - did you forget to include support for VGA console or somesuch? Or maybe left it modularized.
Would vga console config affect after initrd and just before decompressing kernel ?
>>>Maybe you should start with RH's kernel config and tweak it when you know it works.
Treat me as newbie...give me some clue which settings can be checked.
Thanks, P.Naidu |
|
|
Goran Koruga
|
|
Nov 5, 2009 08:55:50 GMT
3 pts
|
|
Hi.
VGA console could affect it, because when not set (and if no other options of the same kind are enabled), display would not be available so you will not see anything.
I recommend to start with RH's kernel config, you can find it in /boot. Copy it to your kernel source dir as .config (might want to save current one), and then you can get asked about new options with:
make oldconfig
Regards,
Goran |
|
|
Nido
|
|
Nov 5, 2009 09:02:53 GMT
N/A: Question Author
|
|
Goran,
Thanks again. I'll check to run `make oldonfig` today and will get back to you.
Thanks Again, P.Naidu |
|
Matti Kurkela
|
|
Nov 5, 2009 09:11:32 GMT
4 pts
|
|
The 2.6.31.5 kernel will print a message before EDD probe (in linux-2.6.31.5/arch/x86/boot/edd.c):
if (!be_quiet)
printf("Probing EDD (edd=off to disable)... ");
If you cannot see this message, your problem is probably unrelated. For example, if your hardware is a Proliant server, the console functions may have been switched to ILO2 Virtual Serial Port, so nothing will appear on the screen. (Please describe the hardware you're running.)
Please attach your kernel configuration file for analysis.
The "kernel" line(s) of your /boot/grub/grub.conf might be important too.
MK |
|
|
Nido
|
|
Nov 5, 2009 10:08:39 GMT
N/A: Question Author
|
|
Hi,
One of the machines is IBM Desktop (Intel 440bx chipset)having VMware running RHEL 4U4.
I have another laptop HP dv6000 running VMware having the same issue.
/boot/grub/grub.conf :
#boot=/dev/sda
default=1
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Red Hat Enterprise Linux AS (2.6.31.5)
root (hd0,0)
kernel /vmlinuz-2.6.31.5 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.31.5.img
title Red Hat Enterprise Linux AS (2.6.9-42.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-42.ELsmp ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.9-42.ELsmp.img
title Red Hat Enterprise Linux AS-up (2.6.9-42.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-42.EL ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.9-42.EL.img
Thanks for your help.
P.Naidu |
|
|
Goran Koruga
|
|
Nov 5, 2009 10:17:53 GMT
4 pts
|
|
Hi.
I asked you about quiet option initially and you do have it - remove that crap.
I hate this idiotic default in modern distributions.
Regards,
Goran |
|
|
Matti Kurkela
|
|
Nov 5, 2009 10:56:20 GMT
5 pts
|
|
Yes. Remove the "rhgb" and "quiet" options - they offer a cool-looking start-up display when everything goes well, but when you have problems, they just hide the information that might be essential in solving the problem.
MK |
|
|
Nido
|
|
Nov 6, 2009 03:06:07 GMT
N/A: Question Author
|
|
Hello Goran/MK,
I removed rhgb and quite options while booting new kernel image manually from grub menu.
Here is the message, I'm getting when removing rhgb and quite option:
It decompresses kernel and shows:
edd=off to disable OK
booting kernel
It hangs forever while showing "booting kernel",
Also I tried changing options while make build using 'make oldconfig' but no luck yet.
Thanks, P.Naidu |
|
|
Viktor Balogh
|
|
Nov 6, 2009 14:01:06 GMT
3 pts
|
|
|
Be sure to include everything essential directly into your newly created kernel, do not compile these to modules! So things might here missing, e.g.: driver for the disk controller, driver for the root fs type... |
|
|
Viktor Balogh
|
|
Nov 6, 2009 14:03:57 GMT
2 pts
|
|
Did you generate the initial ramdisk? I don't know Red Hat, but in SuSE after kernel compiling I need to
# cd /boot
# mkinitrd -k vmlinuz -i initrd -M /boot/System.map |
|
|
Pnaidu
|
|
Nov 9, 2009 13:02:45 GMT
Unassigned
|
|
Viktor,
>>>>Did you generate the initial ramdisk? I don't know Red Hat, but in SuSE after kernel compiling I need to .
As I know , you need not have to manually run mkinitrd for 2.6.x kernel ; but its stillvalid in 2.4.x kernel.
I tried compiling 2.6.29 kernel and got the same problem , Is it because of VMware?? There is something common which is creating same situation with different kernel images.
Your views please...
Thanks as always, P.Naidu |
|
|
Goran Koruga
|
|
Nov 9, 2009 13:47:47 GMT
Unassigned
|
|
Hi.
Does the same thing happen if you use RH kernel config?
This would suggest somethig with CPU options to me.
Regards,
Goran |
|
Printable version
