public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Kernel panic - not syncing: No working init found.
Date: Wed, 3 Jun 2020 12:28:33 -0500	[thread overview]
Message-ID: <9731225a-4718-4cb2-4153-2d3cd06deecc@gmail.com> (raw)
In-Reply-To: <CAP8WD_abkKPcGQSQokit7omXvLrvMQ8EFVxdCwXEHtAh2CysJw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 620 bytes --]

tedheadster wrote:
> Yes, you do need to capture the kernel output.
>
> The usual way is to hook up a serial cable to another computer and
> pipe the output to it. You interrupt the boot (usually by hitting
> <shift> or <tab> in GRUB), and then edit the kernel command line thus:
>
> console=tty1 console=ttyS0,115200n8
>
> If you can do that you can give us some debug output.
>
> - Matthew
>
>


Could she boot from some other media, mount the partitions to get to
dmesg and get it from that?  Or since it may not be mounting any
partitons, would that lead down the wrong path if it is outdated? 

Dale

:-)  :-) 

[-- Attachment #2: Type: text/html, Size: 1035 bytes --]

  reply	other threads:[~2020-06-03 17:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03 16:24 [gentoo-user] Kernel panic - not syncing: No working init found thelma
2020-06-03 16:31 ` Dale
2020-06-03 16:52   ` thelma
2020-06-03 16:57     ` tedheadster
2020-06-03 17:12       ` thelma
2020-06-03 17:15         ` tedheadster
2020-06-03 17:28           ` Dale [this message]
2020-06-03 17:51             ` Michael
2020-06-03 18:35             ` thelma
2020-06-03 18:10     ` J. Roeleveld
2020-06-03 18:06 ` J. Roeleveld
2020-06-03 18:38   ` thelma
2020-06-03 18:53     ` J. Roeleveld
2020-06-04  3:10 ` Adam Carter
2020-06-06  5:54   ` Adam Carter

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=9731225a-4718-4cb2-4153-2d3cd06deecc@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.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