mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alex Dewar <alex.dewar@gmx.co.uk>
To: Emil Renner Berthing <kernel@esmil.dk>
Cc: Heiko Stuebner <heiko@sntech.de>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	"open list:ARM/Rockchip SoC..."
	<linux-rockchip@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Asus C101P Chromeboot fails to boot with Linux 5.2
Date: Fri, 12 Jul 2019 17:27:22 +0100	[thread overview]
Message-ID: <862e98f3-8a89-a05e-1e85-e6f6004da32b@gmx.co.uk> (raw)
In-Reply-To: <CANBLGcyO5wAHgSVjYFB+hcp+SzaKY9d0QJm-hxqnSYbZ4Yv97g@mail.gmail.com>

Hi Emil,

I've tried booting with: audit=0 console=tty0 console=ttyS2,115200n8
earlyprintk=ttyS2,115200n8 init=/sbin/init root=PARTUUID=%U/PARTNROFF=1
rootwait rw noinitrd

Now I don't get the audit messages, but no other message is displayed
either. It just alternates between a flashing cursor and a multicoloured
square in the middle of the screen. The system isn't totally
unresponsive though. If I press the power button it still shuts down
properly.

I've just tested it again and confirmed that it does boot with the
v5.1.11 kernel.

Best,
Alex

  reply	other threads:[~2019-07-12 16:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-12 15:00 Alex Dewar
2019-07-12 15:44 ` Emil Renner Berthing
2019-07-12 16:27   ` Alex Dewar [this message]
2019-07-12 22:07     ` Alex Dewar
2019-07-13 11:38       ` [REGRESSION] Xorg segfaults on Asus Chromebook CP101 with Linux v5.2 (was Asus C101P Chromeboot fails to boot with Linux 5.2) Alex Dewar
2019-07-13 14:47         ` Greg Kroah-Hartman
2019-07-13 15:17         ` Heiko Stuebner
2019-07-13 16:43           ` Alex Dewar
2019-07-13 22:58             ` Ezequiel Garcia

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=862e98f3-8a89-a05e-1e85-e6f6004da32b@gmx.co.uk \
    --to=alex.dewar@gmx.co.uk \
    --cc=heiko@sntech.de \
    --cc=kernel@esmil.dk \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®