From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 7589 invoked from network); 26 Aug 2022 19:12:24 -0000 Received: from 9front.inri.net (168.235.81.73) by inbox.vuxu.org with ESMTPUTF8; 26 Aug 2022 19:12:24 -0000 Received: from mx1.mythic-beasts.com ([46.235.224.141]) by 9front; Fri Aug 26 15:08:52 -0400 2022 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=quintile.net; s=mythic-beasts-k1; h=To:Date:Subject:From; bh=WLzGaAorBXWDttMGy8Xo/DtkJYCmVISDdkXtGUqXtcw=; b=IF4FRXk6rGlH8al7OyUN7PmlE5 X7X0VEDWQGUThyz5rL4rSBiNybmkC/Ct3JT2JV60YmCapCP8HM4IwXdy/B8Tsuv1RvRxp9UTbcTvZ lS3PpZkDAmzqRY/8jrKSBAOZwXU4fWCMFn8hOw9p7JyYG8HJCgoYu11iMfjajbU+MEVlqZ8sMKSW/ 1ju4hAZeDp8HaEIfX2k0jM9lebCRCm1SGSqvNKB32acXZiBXzCpVYC9ADf04mSJab1vHIvHlcu3JR CtiQP7RDi0kN7HkffNizIYxvaFFf8E34oAPCi3Rt6NjlysYpfK9Seg8u5zi6Sr0VX9Ft+qeph3001 i0OpH1fw==; Received: from [85.255.235.65] (port=36539 helo=smtpclient.apple) by mailhub-cam-d.mythic-beasts.com with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1oRehG-0010rE-Q4 for 9front@9front.org; Fri, 26 Aug 2022 20:08:51 +0100 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: Steve Simon Mime-Version: 1.0 (1.0) Date: Fri, 26 Aug 2022 21:08:46 +0200 Message-Id: <1AA32E1A-C426-4018-BD83-BBCC12E33948@quintile.net> References: <1466493e-8ac5-16a9-b4cc-96b45ff5c086@posixcafe.org> In-Reply-To: <1466493e-8ac5-16a9-b4cc-96b45ff5c086@posixcafe.org> To: 9front@9front.org X-Mailer: iPhone Mail (19G71) X-BlackCat-Spam-Score: 4 List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: social extension software Subject: Re: [9front] Used to boot to rio, doesn't anymore Reply-To: 9front@9front.org Precedence: bulk timesync will block if it cannot get a reference time. lock it to the bios c= lock 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 m= aybe it comes up later in the bootup sequence? -Steve > On 26 Aug 2022, at 19:30, Jacob Moody wrote: >=20 > =EF=BB=BFOn 8/26/22 10:54, wakyct@tilde.team wrote: >>> On Fri, Aug 26, 2022 at 10:25:41AM -0600, Jacob Moody wrote: >>>=20 >>> There is not enough information here. >>> Are you booting a terminal kernel? Did >>> you update between the last time it worked and >>> now? >>=20 >> Yes, terminal kernel (an unmodified 386 install). I haven't updated (don'= t know how to yet).=20 >>=20 >> I did recompile the kernel once following http://fqa.9front.org/fqa7.html= #7.2.5. However=20 >> everything booted normally several times after that.=20 >=20 > If this is consistent, and none of the software changed, then surely somet= hing with the > hardware has changed. Iterating through the list of boot parameters outlin= ed here: >=20 > http://fqa.9front.org/fqa9.html#9.5.2 >=20 > 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 somet= hing > is funky with your network card so perhaps start with *noetherprobe=3D. >=20 > 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 prom= pt. > There you can type these boot parameters out, then when you're done you ca= n > type 'boot' to actually get the kernel started. You will know you missed i= t > if you see the memory sizes show. >=20 > For disabling ethernet, the session will look something like: >=20 >> *noetherprobe=3D >> boot > Plan 9 ... >=20 >=20 > -- moody