Re: LOM to OK Prompt

On Apr 6, 11:57 am, Helmut Kreft <kr...@xxxxxxxxx> wrote:
On Fri, 4 Apr 2008 16:25:05 -0700 (PDT), swun2...@xxxxxxxxx wrote:
I am using Hyper terminal from Windows XP.

The quality choice of tools for the job at hand.

Do you meant type 'console' first, then 'poweron' at the LOM> prompt?
because if I type 'poweron', the LOM will start auto boot.

Well the availability of the console depends on the computer beeing
powered on, not just the small management unit that runs the LOM.
Therefore poweron should be the first command to be issued. Then
two things may happen, and I don't remember which:
1.) You will stay in the LOM. This can easily be determined by observing
if there still is a lom> prompt and nothing particular happens.
Issue the console command then.
2.) You are dropped directly to the machines console. The lom> prompt
is gone and lots of interesting things suddenly happen. The machine
tells you it's maker, type, memory, then initializes memory and
tries to boot something.

If you have reached the console you may want to send a break when
the machines checks its memory. Some will refuse to boot if breaked
there, but not yours.

When the booting process started, I press Ctl-C/breaks, but nothing
happened until the Hypertermial become 'Not Response'.... then I need
to reluctantly kill the Hyperterminal in XP.

In theory this should work. Though you probably want to limit any
frantic keypressing to Ctrl-Break. Break is in the upper right corner
of your Keyboard. The key has "pause" and "break" written on it.
But I have to admit, I only know about the theory and never ever
tried to use Hyperterm.

I pressed Ctrl-Pause/Breaks, and the system comes to the Linux boot
prompt:
lom>poweron
lom>
LOM event: power on

Netra t1 (UltraSPARC-IIi 440MHz), No Keyboard
OpenBoot 3.10.25 ME, 512 MB memory installed, Serial #14236338.
Ethernet address 8:0:20:d9:3a:b2, Host ID: 80d93ab2.

Boot device: disk0:a File and args:
SILO Version 1.4.13
boot: boot:

I still not able to get to the OK prompt from there.

Thanks
Sam
Helmut

--
Almost everything in life is easier to get into than out of.
(Agnes' Law)

.

Relevant Pages

  • Re: LOM to OK Prompt
    ... the LOM will start auto boot. ... not just the small management unit that runs the LOM. ... Therefore poweron should be the first command to be issued. ... Issue the console command then. ...
    (comp.unix.solaris)
  • Solaris 10u3 jumpstart fails with 38e00
    ... here's the LOM output: ... Boot device: sec-disk File and args: ... Swapping out the drives from a D130 makes no difference, ... tftpboot entries as the Linux tutorials. ...
    (comp.unix.solaris)
  • Re: Solaris 10u3 jumpstart fails with 38e00
    ... I've tried setting up a Jumpstart server using Linux and also ... LOM output: ... Boot device: sec-disk File and args: Drive not ready ... ok boot net - install ...
    (comp.unix.solaris)
  • Re: No OK Prom on Netra T1 (105)
    ... -- What to do if break or the console has been switched off in the nvram. ... typing "break" at the LOM> prom ... to get a LOM> prompt, and then type "break" to get the desired OK prompt. ... No POST or boot ...
    (SunManagers)
  • Re: Troubleshooting a Netra X1
    ... No need to physically push the power ... button as you can remotely manage the system via LOM. ... If you get that far, you can boot off a CDROM by doing 'boot cdrom', or ... If you truly have the OBP prompt, then you should be able to boot up. ...
    (comp.unix.solaris)