Re: USB-serial adapter suggestions needed

On Mon, Jan 08, 2024 at 08:27:19PM -0800, Mark Millard wrote:
> 
> So all your RPi2B's are v1.1 and so must be used as armv7.
> Good to know.
> 
> 
> > I've added the config.txt files to the netmap at
> > http://www.zefox.net/~fbsd/netmap
> 
> Thanks much.
> 
> If/when an experiment uses any adjusted/replaced config.txt ,
> please be specific about the variation at the time. That
> includes if/when you make www.zefox.org (an aarch64) use
> the standard config.txt for aarch64 with force_mac_address
> added, instead of it being partially based on the armv7
> config.txt .
> 
> One thing still missing for the reporting of the specific
> recent experiment is: what was the powerd status of
> nemesis.zefox.com ? Always indicate the powerd status for
> the RPi*'s at both ends of the serial line involved in the
> failure (GIO end and tip end, making clear the exact
> association).
> 

At that time nemesis.zefox.com was running powerd, enabled
in /etc/rc.conf. Now that line is commented out on all hosts.
It might be relevant that on www.zefox.org, the terminal
server to nemesis, powerd was run manually using 
powerd -a adp, not via an entry in /etc/rc.conf . The two
appear similar, but perhaps not identical for the Pi .

For now all hosts run with powerd off in an attempt to 
re-establish baseline behavior. 

Could Apache or something like it be configured to allow 
live, remote examination of the hosts in the tests? Making
config or static log files accessible seems fairly easy,
dynamic status looks more difficult. At this point my
own reporting errors/omissions are a significant hazard 
to any investigation. 

Thanks for all your help!

bob prohaska