21 Jun
2020
21 Jun
'20
2:36 a.m.
Anno domini 2020 Sun, 21 Jun 04:39:42 -0400
Gene Heskett scripsit:
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On Sunday 21 June 2020 04:11:05 deloptes wrote:
Hi Gene!
Just this week I tried to get arm64 of devuan running on a RPi3B. While almost everything
worked and it booted really fast (~ 5 sec. from powerup to userland) I was not quite
satisfied. To be more precise, the official 5.XX kernel did not boot, the official
hardware support for the vidocore is broken etc., so I think arm64 not working is not a
devuan/debian issue but also present upstream. The BSDs work on the PI4, too, but with the
same problems. The armhf/lf work like a charm. Now I'm running the same version of
devuan armlf for RPI1 on all of my RPIs, that means only keeping one image up to date.
Looks like RPI is entering the same problematic field like C64 vs. C128 :)
Oh, the last RTAI patch I saw was for kernel 3.XX, I think, and nothing since then. Worked
fine. RT-PREEMPT is pestilence on my systems (not only RPi)
Nik
Gene Heskett wrote:
The debian version of u-boot is not compatible with the pi's boot loader
for armhf. Never has been to my knowledge.
The one time I tried the netinstall, which installs grub and an arm64
kernel, it booted nicely but networking was broken.
Basicly if you want debian on a pi you must use the raspbian flavor, it
Just Works, with the usual putzing with networking of course if running
a host file based network which I am. Which version of tde?
The PB and the DEV (14.1) on raspbian and debian
I rather like its ability to manage multiple
workspaces, and my
current gui on the rpi4, LXDE, does a poor job of that, not
remembering a hard to configure 4 pane setup over a reboot, its
easier to ssh -Y into it several times when building LinuxCNC .deb's
from scratch. From other machines with more comfortable seating. I
use R14.0.8 on two machines here, but not on the rpi4. It is a hair
hard on latency's though, a point where the pi's can use all the
help they can get since there is not a port of RTAI to the armhf's.
I don't have CNC and can't comment. The kernel is an issue as the
debian kernel did not work (buster) - I am not sure if it now works
though.
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-users-unsubscribe(a)lists.pearsoncomputing.net For additional
commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net Read
list messages on the web archive:
http://trinity-users.pearsoncomputing.net/ Please remember not to
top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Cheers, Gene Heskett