Not getting the initial Firmware prompt


 
Thread Tools Search this Thread
Operating Systems AIX Not getting the initial Firmware prompt
# 1  
Old 11-17-2005
Error Not getting the initial Firmware prompt

Hi All..

Well I have a prob. Last day I Installed AIX 5.3 on a P550, the installation went fine and I am able to login and perform my activities. But today I noticed one thing. Whenever I reboot the server, am not getting the initial firmware menu from where I could select the boot devices and SMS menu. The first display I get is the AIX login screen. Can anyone help me or tell me why am i not getting the initial display???

With Regards,

BALA
Login or Register to Ask a Question

Previous Thread | Next Thread

5 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Removing all characters up to initial '{'

Hi there, Im having a bit of difficulty with this one and I suspect its because of the character I want to match against maybe causing me a problem, but i wanted to remove everything up to (but not including) the first instance of '{' in a string so for example the string that I want to... (2 Replies)
Discussion started by: hcclnoodles
2 Replies

2. Solaris

Unable to move from rsc prompt to ok prompt

Hi, on sunfire v890 unable to move from rsc prompt to ok prompt, i have executed the command break. (9 Replies)
Discussion started by: manoj.solaris
9 Replies

3. UNIX for Dummies Questions & Answers

How to Change the % prompt to - prompt in UNIX?

how to Change the % prompt to - prompt in unix :wall: ---------- Post updated at 07:40 AM ---------- Previous update was at 07:38 AM ---------- How To display the last modification time of any file in unix ---------- Post updated at 07:40 AM ---------- Previous update was at 07:40 AM... (2 Replies)
Discussion started by: manjiri sawant
2 Replies

4. UNIX for Advanced & Expert Users

Initial RT Configuration

We are trying to set up a ticket request application on a Solaris 9 (SPARC) server. http://wiki.bestpractical.com/index.cgi?SolarisInstallGuide Apache has been configured and MySQL 4.1.12 was installed. http://www.sun.com/bigadmin/features/articles/req_track_1.html Now the issue is with... (1 Reply)
Discussion started by: chrs0302
1 Replies

5. Solaris

Initial RT Configuration

We are trying to set up a ticket request application on a Solaris 9 (SPARC) server. http://wiki.bestpractical.com/index.cgi?SolarisInstallGuide Apache has been configured and MySQL 4.1.12 was installed. http://www.sun.com/bigadmin/features/articles/req_track_1.html Now the issue is with... (0 Replies)
Discussion started by: chrs0302
0 Replies
Login or Register to Ask a Question
REBOOT(8)						      System Manager's Manual							 REBOOT(8)

NAME
reboot - stopping and restarting the system SYNOPSIS
/sbin/reboot [ -lqnhdarsfRD ] /sbin/halt [ -lqndars ] /sbin/fastboot [ -lqndarsRD ] DESCRIPTION
2.11BSD is started by placing it in memory at location zero and transferring to its entry point. Since the system is not reentrant, it is necessary to read it in from disk or tape each time it is to be boot strapped. Rebooting a running system: When the system is running and a reboot is desired, shutdown(8) is normally used to stop time sharing and put the system into single user mode. If there are no users then /sbin/reboot can be used without shutting the system down first. Reboot normally causes the disks to be synced and allows the system to perform other shutdown activities such as resynchronizing hardware time-of-day clocks. A multi-user reboot (as described below) is then initiated. This causes a system to be booted and an automatic disk check to be performed. If all this succeeds without incident, the system is then brought up for multi-user operation. Options to reboot are: -l Don't try to tell syslogd(8) what's about to happen. -q Reboot quickly and ungracefully, without shutting down running processes first. -n Don't sync before rebooting. This can be used if a disk or the processor is on fire. -h Don't reboot, simply halt the processor. -d Dump memory onto the dump device, usually part of swap, before rebooting. The dump is done in the same way as after a panic. -a Have the system booter ask for the name of the system to be booted, rather than immediately booting the default system (/unix). -r Mount the root file system as read only when the system reboots. This is not supported by the kernel in 2.11BSD. -s Don't enter multi-user mode after system has rebooted - stay in single user mode. -f Fast reboot. Omit the automatic file system consistency check when the system reboots and goes multi-user. This is accomplished by passing a fast reboot flag on to the rebooting kernel. This currently prevents the use of -f flag in conjunction with the -h (halt) flag. -D Set the autoconfig(8) debug flag. This is normally not used unless one is debugging the autoconfig program. -R Tells the kernel to use the compiled in root device. Normally the system uses the device from which it was booted as the root/swap/pipe/dump device. Reboot normally places a shutdown record in the login accounting file /usr/adm/wtmp. This is inhibited if the -q or -n options are present. Note that the -f (fast reboot) and -n (don't sync) options are contradictory; the request for a fast reboot is ignored in this case. Halt and fastboot are synonymous with ``reboot -h'' and ``reboot -f'', respectively. Power fail and crash recovery: Normally, the system will reboot itself at power-up or after crashes if the contents of low memory are intact. An automatic consistency check of the file systems will be performed, and unless this fails, the system will resume multi-user operations. SEE ALSO
autoconfig(8), sync(2), utmp(8), shutdown(8), syslogd(8) 3rd Berkeley Distribution May 24, 1996 REBOOT(8)