From: Jacob Adams <tookmund@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Newcomer with Raspberry pi 1
Date: Tue, 19 May 2020 22:03:19 -0400 [thread overview]
Message-ID: <79640741-5AA2-4702-94D5-BE7D34501E18@gmail.com> (raw)
In-Reply-To: <drnDnPnru516cwEyFCry7-PdMJrrjriIkm7t_193u9FY1aGhlMRFAFsxjVatD5i9mb1_iAay1FtsMiaUrlV11A==@protonmail.ch>
I have a B+ lying around so I tried the latest image and got the same error. However, I created a new image with the latest 9front and had no issues on my B+.
So I guess you’ll need to compile from another machine or wait for new images. Or perhaps try an old image and then update using the instructions on the website?
Jacob
> On May 18, 2020, at 18:36, Txus Ordorika <txusinho@protonmail.ch> wrote:
>
> Hello!
>
> Nice to meet y'all. A newcomer here.
>
> I have a spare raspberry pi 1 at home, and I decided to use it with 9front. I see there are some precompiled images at download secion, so I tried [1]. This image leads to a couple of suicides, and the system gets unresponsive before I can do anything. Is there something I could do to avoid that?
>
> The screenshot [2] shows the error. I'm posting this as described in section 8.2.9.1 from the manual.
>
> Manual recommends to cross compile a image, but I assume that must be done from 9plan, right?
>
> Thanks for your time
>
> [1] http://9front.org/iso/9front-7408.1d345066125a.pi.img.gz
> [2] https://ttm.sh/QDa.jpeg
> --
> Txus Ordorika
>
> "During times of universal deceit, telling the truth becomes a revolutionary act."
> -George Orwell-
>
>
next prev parent reply other threads:[~2020-05-20 2:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 22:36 Txus Ordorika
2020-05-20 2:03 ` Jacob Adams [this message]
2020-05-20 5:28 ` [9front] " Txus Ordorika
2020-05-20 5:37 ` cinap_lenrek
2020-06-01 13:15 ` Txus Ordorika
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=79640741-5AA2-4702-94D5-BE7D34501E18@gmail.com \
--to=tookmund@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).