Re: Booting an LDOM (can't find kernel)

[alexmcwhirter@triadic.us]

On 2016-07-26 18:56, John Paul Adrian Glaubitz wrote:

 

Just try with "console=ttyS0". systemd reads this parameter from the kernel command line and sets up the proper getty.

 

The systemd documentation has lots of information on that.

On Jul 26, 2016, at 11:37 PM, alexmcwhirter@triadic.us wrote:

That's exactly what i put in my silo.conf. For whatever reason it's not doing it on my t5210, but when logind eventually spawns a console prompt it will come up on ttyS0. The rest of the systemd / initramfs message output does not show up on ttyS0 however. This still works for me, because my box isn't panicing before logind is brought up, but in this specific case where it is panicing before logind is brought up it kind of leaves you in the dark.

You can see getty behaving differently on sun4v, for example...

On Sun4U, Getty's output looks like this on boot...

[  OK  ] Started Serial Getty on ttyS0.
[  OK  ] Reached target Login Prompts.

On Sun4V however, it looks like this...

[  OK  ] Started Getty on tty5.
[  OK  ] Started Getty on tty4.
[  OK  ] Started Getty on tty1.
[  OK  ] Started Getty on tty2.
[  OK  ] Started Getty on tty3.
[  OK  ] Started Getty on tty6.
[  OK  ] Started getty on tty2-tty6 if dbus and logind are not available.
[  OK  ] Reached target Login Prompts.

It appears that getty is treating the sun4v console like a graphical console, unlike sun4u (sun su / sun zilog) where it sees it as a serial console.