> Some modern disks use the "UASP" protocol in preference to the
>> traditional bulk-only mass storage protocol supported by the Plan
>> 9 usbdisk driver...
>
> Richards that patch makes other devices to not work, have you tested
> it after compiling all usb and kernel?
No, it was an experiment
> Some modern disks use the "UASP" protocol in preference to the
> traditional bulk-only mass storage protocol supported by the Plan
> 9 usbdisk driver. Even if the disk also supports bulk-only, the
> existing driver won't try to pick an alternate configuration to
> force the disk to fall back to
On Thu, Jun 17, 2021 at 04:05:15PM +0100, Steve Simon wrote:
> I must appologise, though I sent a reply at the time, an out of date x509
> certificate meant the email never reached my ISP.
Hi Steve, thanks anyway.
> What I tried to say was...
>
> > I wonder if the abaco problem you are seeing
I must appologise, though I sent a reply at the time, an out of date x509
certificate meant the email never reached my ISP.
What I tried to say was...
> I wonder if the abaco problem you are seeing is the global move to
> stronger TLS algorithms. I have backported libcrypt from 9front which
>
Now all is making sense. The tricky part will be configuring it at
boot time to make it the root file system...
Thanks a lot to both of you for the help, specially to you Richard.
Regards,
adr.
--
9fans: 9fans
Permalink:
> It may be easy to jump to the conclusion "9front can do X, plan 9 can't",
> but sometimes the situation is "9front does it this way, plan 9 does it that
> way".
yep, and sometimes 9front does it some way, while 4e doesn't do it in any way.
and sometimes 4e does it some way and 9front doesn't do
FWIW, here's an excerpt from my /cfg/sysname/termrc which i use to
start an extra fossil. The disk is a large (10TB from memory) WD Elements
connected to one of the USB2 ports. I don't yet start the venti
automatically because i keep remaking it to try different
configurations, but it runs fine.
I said:
> But despite the message you won't see it in /dev/sdU9.0 when starting usb/disk
I remember now: just do 'usb/disk -m /dev' to get the sdUX.Y mounted where you
want.
adr said:
>now the sd disk appears in /dev, but I can't set up the
>plan9 partitions:
> ...
>Thanks anyway.
If you're
On Fri, Jun 11, 2021 at 05:26:46PM +0100, Richard Miller wrote:
> > No luck!, although the end points appear now after manually executing
> > usb/disk.
> > ...
> > disk: logical block size 512, # blocks 7814037167
> > usb/disk: fsadd sdU9.0
>
> Once you've reached that point, it looks like the
> No luck!, although the end points appear now after manually executing
> usb/disk.
> ...
> disk: logical block size 512, # blocks 7814037167
> usb/disk: fsadd sdU9.0
Once you've reached that point, it looks like the driver is handling the disk
ok.
But despite the message you won't see it in
> > Some modern disks use the "UASP"
> > protocol in preference to the traditional bulk-only mass storage protocol
> > supported by the Plan 9 usbdisk driver. Even if the disk also supports
> > bulk-only, the existing driver won't try to pick an alternate configuration
> > to force the disk to
> I can connect to github too, and some other places. But if you surf the web
> you'll end up with this error. Just a few If you want to do a test:
>
> https://developer.arm.com
> https://wikipedia.org
> https://marc.info
> https://www.perseus.tufts.edu
> http://mars.jpl.nasa.gov
Thanks, I did a
> The usb subsystem is known to be pretty rudimentary, and indeed with respect
> to power management /sys/src/cmd/usb/usbd/usbd.c:/^portattach is headed by
> this comment:
> * BUG: does not consider max. power avail.
>
> Having said that, "It is impossible to use any usb disk" is possibly an
>
> Below is a patch ...
Something in the 9fans pathway has expanded the tabs in my patch into
8 spaces. Irritating. If you want to apply the patch, it will probably
be necessary to turn them back into tabs.
--
9fans: 9fans
Permalink:
To be pedantic, the troubles you describe are not strictly "9pi image problems",
you will likely find that 4e Plan 9 on any architecture will behave the same.
The usb subsystem is known to be pretty rudimentary, and indeed with respect
to power management /sys/src/cmd/usb/usbd/usbd.c:/^portattach
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
16 matches
Mail list logo
