Re: Netra T5220

[Don NetBSD <netbsd-embedded%gmx.com@localhost>]

On 11/16/2018 2:53 PM, Sad Clouds wrote:
> On Fri, 16 Nov 2018 13:22:19 -0700
> Don NetBSD <netbsd-embedded%gmx.com@localhost> wrote:
>
> > So, it seems like there are a boat load of prompts -- "u-boot>",
> > "->", "ok" ...  And, nothing that seems to summarize ALL of
> > the pertinent environments in which you can be interacting with
> > the box.
>
> You're getting confused between various consoles. This is what I do to
> log in
>
> I have a Linux laptop connected to T5220 via serial cable
>
>
> Here I use 'cu' to initiate connection:
>
> # chmod 666 /dev/ttyUSB0
> # cu -l /dev/ttyUSB0

Fine, I use tip(1)...

> First login takes me to service processor console:
>
> SUNSP00212824CA7D login: root
> Password:
> Waiting for daemons to initialize...
>
> Daemons ready
>
> Sun(TM) Integrated Lights Out Manager
>
> Version 2.0.4.27.g
>
> Warning: password is set to factory default.

This is where we differ.  I get a U-Boot banner (actually, TWO of them)
followed by a "u-boot>" prompt.  If I issue the "boot" command at that
prompt, the service processor boots (lots of diagnostic output before
finally offering up the "->" prompt)

Once at the SP prompt, I can progress to a console, as below.  I just
have this "extra step" BEFORE the SP prompt is available.

And, am unsure of what I can do, there (e.g., I was able to reset
the password for the SP using commands from the "u-boot>" prompt)

> The following command takes me to system console. After I type 'y' and
> hit Enter key, Solaris login prompt appears:
>
> -> start /SP/console
> Are you sure you want to start /SP/console (y/n)? y
>
> Serial console started.  To stop, type #.
>
> t5220 console login:


> I don't know if your system is bootable and if it has Solaris running.
> If not, then download ISO, burn to DVD and try booting from that.

The system boots (5.10) -- if I want to go that far.  Right now, I want
to sort out how to get the box into a configuration that I can at least
document.  Then, figure out how I might want to CHANGE that to suit my
specific needs.

Starting at the "u-boot level" seems the most prudent...