Groups > linux.debian.bugs.dist > #871375

Bug#884601: "console=ttyAMA0,115200" --> "console=tty0"

From	Matthias Luescher <lueschem@gmail.com>
Newsgroups	linux.debian.bugs.dist, linux.debian.kernel
Subject	Bug#884601: "console=ttyAMA0,115200" --> "console=tty0"
Date	2017-12-27 17:10 +0100
Message-ID	<v1mrf-3SW-15@gated-at.bofh.it> (permalink)
References	<uXHXj-1IM-5@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

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

Back to linux.debian.bugs.dist | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Bug#884601: "console=ttyAMA0,115200" --> "console=tty0" Matthias Luescher <lueschem@gmail.com> - 2017-12-27 17:10 +0100
  Bug#884601: "console=ttyAMA0,115200" --> "console=tty0" Michael Stapelberg <stapelberg@debian.org> - 2018-01-04 18:10 +0100
    Bug#884601: "console=ttyAMA0,115200" --> "console=tty0" Matthias Luescher <lueschem@gmail.com> - 2018-01-05 23:00 +0100

csiph-web