Path: csiph.com!news.mixmin.net!aioe.org!news.servidellagleba.it!bofh.it!news.nic.it!robomod
From: Matthias Luescher <lueschem@gmail.com>
Newsgroups: linux.debian.bugs.dist,linux.debian.kernel
Subject: Bug#884601: "console=ttyAMA0,115200" --> "console=tty0"
Date: Wed, 27 Dec 2017 17:10:01 +0100
Message-ID: <v1mrf-3SW-15@gated-at.bofh.it>
References: <uXHXj-1IM-5@gated-at.bofh.it>
Old-Return-Path: <debbugs@buxtehude.debian.org>
Reply-To: Matthias Luescher <lueschem@gmail.com>, 884601@bugs.debian.org
Resent-To: debian-bugs-dist@lists.debian.org
Resent-Cc: Debian Kernel Team <debian-kernel@lists.debian.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="089e0829d268ef34fa0561547d3c"
Approved: robomod@news.nic.it
Lines: 49
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.bugs.dist:871375 linux.debian.kernel:59780

--089e0829d268ef34fa0561547d3c
Content-Type: text/plain; charset="UTF-8"

Hi

I just faced a similar issue with the arm64 kernel
(linux-image-4.14.0-0.bpo.2-arm64). It booted fine with the 4.13 based
kernel but it failed after the upgrade to the above mentioned kernel. Since
I wanted to debug the stuff I took a closer look at the cmdline.txt file:
There I found the config "console=ttyAMA0,115200". This looked wrong to me
since ttyAMA0 is the bluetooth device on the Raspberry Pi 3. Therefore I
changed it to "console=tty0" and all of a sudden my system booted again
with the 4.14 kernel.

Another remark: My setup also worked with the 4.14 kernel combined with the
device tree binary from the 4.13 kernel. However, I do not like this hack.

My full setup is here: https://github.com/lueschem/edi-pi

Good luck
Matthias

--089e0829d268ef34fa0561547d3c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi<div><br></div><div>I just faced a similar issue with th=
e arm64 kernel (linux-image-4.14.0-0.bpo.2-arm64). It booted fine with the =
4.13 based kernel but it failed after the upgrade to the above mentioned ke=
rnel. Since I wanted to debug the stuff I took a closer look at the cmdline=
.txt file: There I found the config &quot;<span style=3D"color:rgb(0,0,0);w=
hite-space:pre-wrap">console=3DttyAMA0,115200&quot;. This looked wrong to m=
e since ttyAMA0 is the bluetooth device on the Raspberry Pi 3. Therefore I =
changed it to &quot;console=3Dtty0&quot; and all of a sudden my system boot=
ed again with the 4.14 kernel.</span></div><div><span style=3D"color:rgb(0,=
0,0);white-space:pre-wrap"><br></span></div><div><span style=3D"color:rgb(0=
,0,0);white-space:pre-wrap">Another remark: My setup also worked with the 4=
.14 kernel combined with the device tree binary from the 4.13 kernel. Howev=
er, I do not like this hack.</span></div><div><span style=3D"color:rgb(0,0,=
0);white-space:pre-wrap"><br></span></div><div><span style=3D"color:rgb(0,0=
,0);white-space:pre-wrap">My full setup is here: </span><font color=3D"#000=
000"><span style=3D"white-space:pre-wrap"><a href=3D"https://github.com/lue=
schem/edi-pi">https://github.com/lueschem/edi-pi</a></span></font></div><di=
v><font color=3D"#000000"><span style=3D"white-space:pre-wrap"><br></span><=
/font></div><div><font color=3D"#000000"><span style=3D"white-space:pre-wra=
p">Good luck</span></font></div><div><font color=3D"#000000"><span style=3D=
"white-space:pre-wrap">Matthias</span></font></div></div>

--089e0829d268ef34fa0561547d3c--