Simpler Navigation for Servers and Operating Systems
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
General
cancel
Showing results for 
Search instead for 
Did you mean: 

Problem in installtion RHEL 4 on ML570 G4

mohammad_h
Occasional Visitor

Problem in installtion RHEL 4 on ML570 G4

Hi all,
I installed RHEL 4 AS on ML570 G4 server (3250M RAM, 4 processors), during the installation process every thing went smoothly and I faced no errors. But when I reboot the machine to do post configuration using the SMP kernel, system reached "Uncompressing kernel OK" and hanged up, nothing but the flushing cursor. When I used the Uni-processor, system boots but cat /proc/cpuinfo reveals one processor!!!
How can I boot the system using the SMP kernel???
4 REPLIES
Stuart Browne
Honored Contributor

Re: Problem in installtion RHEL 4 on ML570 G4

Which update, and what kernel revision?

If you can boot up on the uni-processor, can you 'up2date' to get the newer kernel? Do they work?
One long-haired git at your service...
mohammad_h
Occasional Visitor

Re: Problem in installtion RHEL 4 on ML570 G4

Version 4 AS without update and I re-install the system with RHEL ES version 4 with kernel 2.6.9-EL and also the kernel 2.6.9-ELsmp did the same thing... Is there any kernel parameters we have to pass it to the anaconda??
Stuart Browne
Honored Contributor

Re: Problem in installtion RHEL 4 on ML570 G4

Any particular reason you're using the original release, and not one of the updates?

I'm guessing the issue would be resolved with one of the newer kernel releases (It's at something like 2.6.9-55.EL).

And, no. I'm not aware of any boot-strings you could pass.
One long-haired git at your service...
mohammad_h
Occasional Visitor

Re: Problem in installtion RHEL 4 on ML570 G4

Hi Sturat,
Thanx for help but it was a booting-string issue.
"linux acpi=off nolapic dd"

That was the magic combination

Regards
Mohammad