Re: Booting an LDOM (can't find kernel)
Hello.
On 07/27/2016 02:26 AM, alexmcwhirter@triadic.us wrote:
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
<mailto: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.
There is an "issue". In order to let the kernel use the ldom console you
need to pass 'console=ttyHV0' (or do not pass any 'console=' at all),
not 'console=ttyS0'. But the file corresponding to this device is still
/dev/ttyS0.
Please, have a look at this thread:
http://marc.info/?l=linux-sparc&m=128984904112418&w=2
In particular, these steps should bring you the shell's prompt on the
ldom console:
telnet 127.0.0.1 5020
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
Connecting to console "skholman-test4" in group "skholman-test4" ....
Press ~? for control options ..
#. ?
{0} ok boot disk bla
Boot device: /virtual-devices@100/channel-devices@200/disk@0 File and
args: bla
SILO Version 1.4.14
Your imagename `bla' and arguments `' have either wrong syntax,
or describe a label which is not present in silo.conf
Type `help' at the boot: prompt if you need it and then try again.
boot: Linux console=ttyHV0 init=/bin/sh
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
/bin/sh: 0: can't access tty; job control turned off
# ls -l /dev/ttyS0
crw------- 1 root root 4, 64 Jul 27 05:23 /dev/ttyS0
# echo Hello > /dev/ttyS0
Hello
#
So my take is that if one setups systemd to always start a getty on
/dev/ttyS0, the login prompt will be shown on the ldom console when
Debian is booted with or without 'console=ttyHV0' on the cmdline.
Thanks.
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.
Reply to: