From: Romano <unobe@cpan.org>
To: 9front@9front.org,hiro <23hiro@gmail.com>
Subject: Re: [9front] rpi4 shoots to 100% load and is unresponsive
Date: Thu, 07 May 2020 19:47:40 +0000 [thread overview]
Message-ID: <E9ABF4F4-EFC1-4E32-8275-84C8CCDBCD0E@cpan.org> (raw)
In-Reply-To: <CAFSF3XMb4Fz1TQVs-4ovDm9sRawK+zerdPpeNsfKXFWitfQaKw@mail.gmail.com>
Thank you, hiro.
The firmware I updated using rpi-eeprom just last week on raspbian, but my understanding of the boot process is that doesn't matter--what's on /n/pidos does. For /n/pidos, I used the files on the iso image on 9front and just an updated rpi4 kernel: that craps out with the 100% load. I also pulled the latest files using mk under /sys/src/boot/bcm, which appears to be tracking the master, not stable, branch in the raspberrypi firmware repo. I copied those files to /n/pidos and still had issues.
It's odd because clearly not everything is going awry, since 'stats' still shows updates.
Did I answer your question, or am I misunderstanding how the firmware works?
On May 7, 2020 7:25:57 PM UTC, hiro <23hiro@gmail.com> wrote:
>that kinda supports kenji's experiences, too. he was having general
>stability issues that this reminds me of.
>
>how's your firmware dated?
>
>when i installed 9front on rpi4 i might have been lucky bec. of the
>firmware that i picked - i didn't use the one from the release. that
>one was not working at all for me.
>
>but sadly i only ran it for a few minutes, and i didn't stress test
>anything.
next prev parent reply other threads:[~2020-05-07 19:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 18:46 Romano
2020-05-07 19:25 ` [9front] " hiro
2020-05-07 19:47 ` Romano [this message]
2020-05-07 19:54 ` cinap_lenrek
2020-05-07 20:06 ` Romano
2020-05-07 20:45 ` Romano
2020-05-07 21:03 ` cinap_lenrek
2020-05-07 21:11 ` cinap_lenrek
2020-05-07 21:29 ` cinap_lenrek
2020-05-07 22:02 ` Romano
2020-05-08 4:44 ` kokamoto
2020-05-08 5:57 ` kokamoto
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=E9ABF4F4-EFC1-4E32-8275-84C8CCDBCD0E@cpan.org \
--to=unobe@cpan.org \
--cc=23hiro@gmail.com \
--cc=9front@9front.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;
as well as URLs for NNTP newsgroup(s).