vmunix.prev

[castro_2]

I have a problem with re-compile the kernel. How can I do to startup the machine with the old kernel (vmunix.prev)
Thanks.

[Helen French · Accepted solution]

You need to reboot the system, then interrupt the normal boot process, give boot command at console prompt and interact with ISL. Then at ISL prompt:
ISL > hpux boot disc(;0)/stand/vmunix.prev

[Allan Pincus]

1. Reboot the machine and interrupt the boot process by tapping the "esc" key.

2. At the PDC interface (often called "boot admin" menu) type:

boot pri isl

3. At the ISL> prompt type:

hpux /stand/vmunix.prev

That should do what you need.

- Allan

[S.K. Chan]

In BOOT_ADMIN prompt you would enter ..
bo pri isl
and once you get teh ISL prompt ..
ISL> hpux (;0)/stand/vmunix.prev
Do take a look also .. (DOCID=KBRC00008089) for greater detail ..
http://support1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000062908963

[Michael Elleby III_1]

Castro-

On power up of the system, interrupt the boot process when indicated...

1. Type in 'no pri' to tell the system to boot from the primary boot path.

2. When it asks you to interact with ISL, type in a 'Y' and press enter.

3. When presented with the ISL prompt, type in:
'hpux (;0)/stand/vmunix.prev' and press enter.

This should boot your system using the previous kernel..

Hopefully, you will have success.

Mike-

[steven Burgess_2]

Hi

Reboot the machine. Interupt the boot sequence

Interact with ipl 'Y'

ISL> hpux -is /stand/vmunix.old

Will boot the old kernel

HTH

Steve

[Anil C. Sedha]

Hi Castro,

You can do the following

Start the system

Press any key to abort the startup. Here cancel the boot process by pressing any key.

Enter ISL mode by using

boot -is

At ISL prompt enter

ISL> hpux -is /stand/vmunix.prev

This will resolve your problem. Don't forget to assign points to answers that you like best.

[doug hosking]

Responses above are useful for emergency recovery in situations like yours, but keep in mind that some commands may not behave correctly if you do this. (Commands that use nlist() calls to access /dev/kmem, etc. often assume that you have booted /stand/vmunix.
You may get odd results from them if you boot from vmunix.prev or something other than /stand/vmunix.) This isn't usually horrible, and is less of a problem than it once was because more commands are using the pstat family of system calls instead of nlist to collect their information now, but if you need to boot vmunix.prev you would be wise to reboot normally as soon as reasonably convenient after that to reduce the risk of this type of problem. The kmupdate manual page has some additional information that might be useful to you on newer HP-UX releases.