Hi Dave,
On 12/04/2017 01:43 PM, John David Anglin wrote:
On 2017-12-04, at 6:51 AM, Frank Scheiner wrote:
But after installing v4.14.x and then trying to boot it, my rp3440
seemed to have locked up after the following messages:
```
[ 28.618056] io scheduler deadline registered
[ 28.618308] io scheduler cfq registered (default)
[ 28.618481] io scheduler mq-deadline registered
[ 28.623261] PDC Stable Storage facility v0.30
[ 28.671368] STI GSC/PCI core graphics driver Version 0.9b
[ 28.671984] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 28.708902] 0000:e0:01.1: ttyS0 at MMIO 0xfffffffff4050000 (irq =
73, base_baud = 115200) is a 16550A
[ 28.731145] 0000:e0:01.1: ttyS1 at MMIO 0xfffffffff4050010 (irq =
73, base_baud = 115200) is a 16550A
[ 28.731499] console ttyS1] enabled
[ 28.732307] bootconsole [ttyB0] disabled
I believe you need to change console to ttyS0 with v4.14.x.
Yes that solved it (see the bottom part of my earlier mail :-)), but
was unexpected, as in the past the console used by the iLO MP of the
rp3440 was always ttyS1.
Possibly, console argument is no longer needed
on command line.
I believe it is needed to configure the console in any case. Without
"console=" argument palo will add what is configured the default for a
system type:
from `/usr/share/doc/palo/README.gz`
```
[...]
1. HP machines can use either a serial or a graphics boot console.
Palo now figures out which one you are using and adds the
appropriate "console=" to the end of the boot command line. It is
only added if you don't already have "console=" in your boot
command line.
[...]
```
...(e.g. ttyS1 for rp3440 since [1]) and if you manually delete the
console argument when interacting with IPL to really get rid of it,
the console output stops after the kernel disables ttyB0:
```
[...]
[ 0.001572] Console: colour dummy device 160x64
[ 0.002947] console [tty0] enabled
[ 0.003082] bootconsole [ttyB0] disabled