From: Steve Simon <firstname.lastname@example.org>
Subject: Re: [9front] Used to boot to rio, doesn't anymore
Date: Fri, 26 Aug 2022 21:08:46 +0200 [thread overview]
Message-ID: <1AA32E1A-C426-4018-BD83-BBCC12E33948@quintile.net> (raw)
timesync will block if it cannot get a reference time. lock it to the bios clock or get networking working before timesync is called.
i dont know where timesync gets its reference in 9 front default install but start by looking at why timesync is unhappy - maybe the network is dead or maybe it comes up later in the bootup sequence?
> On 26 Aug 2022, at 19:30, Jacob Moody <email@example.com> wrote:
> On 8/26/22 10:54, firstname.lastname@example.org 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
>> 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:
> Plan 9 ...
> -- moody
next prev parent reply other threads:[~2022-08-26 19:12 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
2022-08-26 19:08 ` Steve Simon [this message]
2022-09-03 2:29 ` wakyct
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 \
* 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).