On 11/9/22 21:27, Rod Webster wrote:
Alec, the RT8169 hardware may be ok but the same driver is used for a host
of other hardware and it does not work as well. The RT8168-dkms driver
covers some of them and can be used to replace the RT8169.
https://packages.debian.org/buster/r8168-dkms. Read the notes on the repo
page
I had the RT8168 driver working once perfectly with a RT8111 on Bullseye
but could never do it again on a reinstall. It seems too many devices are
being supported by the one driver and performance suffers.
I think this is a real issue because the average new user should not be
expected to compile the kernel and it severely limits the available
hardware that will work with linuxcnc. For all its faults, Bookworm will be
the easiest path for users when 2.9 releases in the absence of buildbot
images. You can't install the bookworm packages on Bullseye. I tried...
So did I, but my buildbot's problem was the version of python 3 shipped
with bullseye. Too new. Wash rinse & repeat for bookworm I expect. Then
again, my test machine is the rpi4 running my Sheldon lathe. I thought
at the time that should have been an easy .configure script fix, but its
been a year now and no one has announced success. And I can't make a
camera work on buster for 2 consecutive buildbot versions. debian seems
bound to cripple us back to text screens, as everytime I update I get 10
or more gfx related libraries updated and something else doesn't work on
bullseye. which this machine is running.
Bullseye currently requires lcnc to be installed from source.... so not a
good candidate if it can be avoided. Bullseye (kernel 5.10) is not immune
from the error finishing read but I suspect the very first versions are
OK. Maybe your 5.4 kernel is OK. Note that predates support for the Realtek
8125 2.5 gb NIC used in the Odroid and an increasing number of SFF PC's
(support was added in 5.9) So maybe that's when they reworked it.
I've never had any delays with bookworm booting. Its pretty speedy here...
Rod Webster
*1300 896 832*
+61 435 765 611
Vehicle Modifications Network
www.vehiclemods.net.au
On Thu, 10 Nov 2022 at 11:24, Alec Ari via Emc-developers <
emc-developers@lists.sourceforge.net> wrote:
Rod,
RTAI Debian packages exist for Bullseye, I packaged them myself. RTAI will
never and has never been deployed in upstream Debian. I have an r8169 NIC
and don't have any issues with network latency. 5.4 kernel debs would also
work for Bookworm but it takes 5+ minutes to reach my desktop screen after
booting Bookworm on my 4+ GHz 8-core/16-thread Ryzen CPU so I'm steering
clear of it. Bookworm is a total joke right now, I ran sid for years and
never had a problem, now both testing/Bookworm and unstable/sid are
absolute turds.
Is this using the RTAI helper package and the uspace build, or some other
sorcery?
Andy,
For LinuxCNC, a 5.4 RTAI+PREEMPT_RT kernel would work, in theory, with a
LinuxCNC RTAI+uspace build, but currently having issues compiling RTAI's
mailbox (mbx) module against the RTAI+PREEMPT_RT kernel due to "pointer
type stuff." Need someone with more basic knowledge of C to fix problem.
Alec
On Wednesday, November 9, 2022 at 06:11:33 PM CST, Rod Webster <
r...@vehiclemods.net.au> wrote:
It's not useful to have RTAI in Bullseye as we don't have any debs for that
platform. It needs to target Bookworm so it is deployed to the Debian
repos.
Also, on the topic of kernels, there is a significant issue with the 5.x
and 6.x kernels in Debian which have excessive network latency
mostly/possibly only with Realtek NIC's) .
This causes an "Error finishing read" on Mesa ethernet devices which
disables communications to the board. Some of the NIC drivers in Debian are
15-30% slower than the original Realtek drivers according to some external
sources.
Some users have found that compiling the 6.1 PREEMPT_RT kernel resolves the
issue.
Sometimes using a NIC different driver fixes it but rarely.
Forum Ref:
https://forum.linuxcnc.org/27-driver-boards/46911-mesa-hm2-hm2-7i96s-0-error-finishing-read?start=110
<
https://forum.linuxcnc.org/27-driver-boards/46911-mesa-hm2-hm2-7i96s-0-error-finishing-read?start=110
So this issue now rules out all of the popular USFF
I am attempting to build deb files of this kernel today, but it's too
early to say if it will succeed or if I can even install them.
If a resolution is found, consideration should also be given to shipping a
PREEMPT_RT kernel deb with 2.9.
Rod Webster
*1300 896 832*
+61 435 765 611
Vehicle Modifications Network
www.vehiclemods.net.au
On Thu, 10 Nov 2022 at 07:55, andy pugh <bodge...@gmail.com> wrote:
On Wed, 9 Nov 2022 at 21:38, Alec Ari via Emc-developers <
emc-developers@lists.sourceforge.net> wrote:
Since there's been great progress with RTAI developments, can RTAI
Debian
package support for Bullseye be a milestone before 2.9.0 makes it's
initial
stable release?
I would like to see that, yes.
I was hoping to have PREEMPT_RT and RTAI work together with the 5.4
kernel
so one LinuxCNC package will work on all, but I don't think this is
going
to happen due to about ~5 lines of C code I don't understand. Making
5.4
RTAI-only kernel debs will be pretty easy once I have the Kconfig
changes
sorted out for Bullseye.
Is this using the RTAI helper package and the uspace build, or some other
sorcery?
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
