9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "adr via 9fans" <9fans@9fans.net>
To: 9fans@9fans.net
Subject: [9fans] Miller's 9pi image (rpi4) problems
Date: Thu, 10 Jun 2021 18:59:27 +0000	[thread overview]
Message-ID: <YMJhD8yRXYqw1Hvg@SDF.ORG> (raw)

First of all, hello to everyone.

I've been using 9front attracted by the aarch64 support, not so
much by the 64 bit words but by the registers at hand.

I got problems with cwfs: the name length limit hardcoded at
compile time, impossibility of disk usage statistics for the "other"
partition (in a file system which is going to crash when full...)
and some file corruption when halting in a usb disk still reading
from the buffer. I don't feel comfortable using an experimental fs
like hjfs.

I used Plan9 almost a decade ago. I remember using fossil+venti
and been quite happy (after some bug was discovered). I'm using
only arm computers now and is great to see the rpi4 supported, and
Richard Miller's image is almost a lab's distribution. So I renounced
to those precious free registers and gave it a try.

The biggest problem to me is the usb code.

First I'm using a kvm switch so there are a lot of attachments-detachments.
At a certain point it will end with "No slots available" and the
usb will became unusable. For me is a labyrinth, but I'm pretty sure
someone with more experience with the system could fix it.

There is something wrong with the code responsible of managing and
monitoring the power of the ports. This is going to be more
complicated. It is impossible to use any usb disk. I managed to
make one appear connecting it to one of the usb2 ports and powering
the usb disk externally before turning on the pi (the system crashed
several times when I powered the disk with the os running), but it
was useless:

usb/disk: startdevs: opening #0 /dev/usb/ep5.0
usb/disk: devmain: disk: endpoints not found
usb/disk: no unhandled devices found

The other issue important to me is with webfs:
webfs: tlsClient: fd out of range or not open

So no abaco for me, almost every page I try to load ends up with
this error. I installed a recent go and compiled opossum, but
at this point is unusable, at least for me.

I've had horrible usb related experiences with openbsd and netbsd
since the beginning of time, so it really surprised me the stability
of the 9front usb system.

Sorry I can only report this at the moment.

Regards,
adr.

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tc5dcd85d69518168-M542f01bc62388a7ac295c914
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

             reply	other threads:[~2021-06-10 18:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10 18:59 adr via 9fans [this message]
2021-06-11  9:05 ` Richard Miller
2021-06-11  9:14   ` Richard Miller
2021-06-11 14:38     ` adr via 9fans
2021-06-11 16:00       ` Richard Miller
2021-06-11 16:13       ` adr via 9fans
2021-06-11 16:26         ` Richard Miller
2021-06-11 17:57           ` adr via 9fans
2021-06-11 18:18             ` Richard Miller
2021-06-11 18:50               ` a
2021-06-11 19:10               ` hiro
2021-06-11 21:07               ` adr via 9fans
2021-06-13 17:22 ` [9fans] " adr via 9fans
2021-06-17 15:05 ` [9fans] " Steve Simon
2021-06-17 19:48   ` adr via 9fans
2021-06-19 11:41   ` adr via 9fans
2021-06-19 12:44     ` Richard Miller

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=YMJhD8yRXYqw1Hvg@SDF.ORG \
    --to=9fans@9fans.net \
    /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).