9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Jacob Moody <moody@mail.posixcafe.org>
To: 9front@9front.org
Subject: Re: [9front] Used to boot to rio, doesn't anymore
Date: Fri, 26 Aug 2022 11:27:32 -0600	[thread overview]
Message-ID: <1466493e-8ac5-16a9-b4cc-96b45ff5c086@posixcafe.org> (raw)
In-Reply-To: <20220826165443.GA348404@tilde.team>

On 8/26/22 10:54, wakyct@tilde.team wrote:
> On Fri, Aug 26, 2022 at 10:25:41AM -0600, Jacob Moody wrote:
>> There is not enough information here.
>> Are you booting a terminal kernel? Did
>> you update between the last time it worked and
>> now?
> Yes, terminal kernel (an unmodified 386 install). I haven't updated (don't know how to yet). 
> I did recompile the kernel once following http://fqa.9front.org/fqa7.html#7.2.5. However 
> everything booted normally several times after that. 

If this is consistent, and none of the software changed, then surely something with the
hardware has changed. Iterating through the list of boot parameters outlined here:


May help you pin down what is causing the issue. You can go through one by one
and start turning stuff off to see what is hanging. My gut is saying something
is funky with your network card so perhaps start with *noetherprobe=.

In order to enter these boot parameters, when you boot in to 9front just
start hitting any key and that should throw you in to the boot loader prompt.
There you can type these boot parameters out, then when you're done you can
type 'boot' to actually get the kernel started. You will know you missed it
if you see the memory sizes show.

For disabling ethernet, the session will look something like:

> *noetherprobe=
> boot
Plan 9 ...

-- moody

  reply	other threads:[~2022-08-26 17:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-26  8:23 wakyct
2022-08-26 16:05 ` wakyct
2022-08-26 16:25   ` Jacob Moody
2022-08-26 16:54     ` wakyct
2022-08-26 17:27       ` Jacob Moody [this message]
2022-08-26 19:08         ` Steve Simon
2022-09-03  2:29           ` wakyct

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:

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

  git send-email \
    --in-reply-to=1466493e-8ac5-16a9-b4cc-96b45ff5c086@posixcafe.org \
    --to=moody@mail.posixcafe.org \
    --cc=9front@9front.org \


* 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;
as well as URLs for NNTP newsgroup(s).