Oh, one more thing; DO NOT SELECT RTAI in the installer just yet. I have the
infrastructure there but no image yet so the script will fail right now. Please
choose PREEMPT_RT. I will let everybody know about RTAI support when it's done.
Alec
___
Emc-
Hello everybody,
I finally have the Gentoo image uploaded and it's installer updated.
Instructions:
https://openlunchbox.com/mw19/index.php/HOWTO:_Gentoo_for_LinuxCNC
If you wish to install it from a Debian system, you can skip the SystemRescue
steps and start here:
https://openlunchbox.com/m
Hello,
RTAI has been updated to 5.4.290 (latest 5.4 kernel as of this writing) and I
have already packaged kernel debs here:
https://github.com/NTULINUX/RTAI/releases/tag/v5.3.3
I will also be building LinuxCNC deb packages today that are built against the
5.4.290 kernel.
A huge shout-out to
On Monday, January 20, 2025 at 06:20:33 PM CST, Steffen Möller via
Emc-developers wrote:
>Is there any scenario for which both real-time flavors would be installed at
>the same time?
Definitely not. LinuxCNC needs to be built differently for RTAI, and you cannot
run PREEMPT_RT and RTAI at t
The issue is that linuxcnc and linuxcnc-rt would be the same as linuxcnc
doesn't get built differently, whether you're using POSIX rt threads, or POSIX
non-rt threads. I think it should be `linuxcnc` and `linuxcnc-rtai`. linuxcnc's
binaries only change if using RTAI.
Alec
On Friday, January
Hi Gene,
Gentoo itself supports many architectures (officially; amd64x86alpha
armarm64hppamipsppcppc64riscvsparc) however the
image I built is specific to AMD64 platforms.
I made a thread here but got no replies, so I'm not sure what benefit it would
be if
Hello everyone,
As some of you may know, I've been working on a Gentoo image for LinuxCNC that
installs and boots off USB, SATA/AHCI, and NVMe devices.
The only problem right now is that it is going to take some time to get qtpyvcp
working with it, however LinuxCNC itself and FlexGUI work perfe
I have no idea what's going on here but maybe using fakeroot can help?
Alec
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
Thanks to TurBoss, I fixed that problem by adding
PYTHONPATH="/usr/lib/python3/dist-packages" to /etc/env.d/99linuxcnc (system
environment variable) to the ebuild. LinuxCNC's latency-test works now, however
when trying to start sim axis, I get:
count= and names= are mutually exclusive
and2: rta
I see the light at the end of the tunnel, the sim lathe does indeed work!
Alec
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
Hello,
I'm having trouble getting LinuxCNC going again on Gentoo. It's been a year
since I had everything working, made some updates and now it's broken. I'm
using the latest 2.9 checkout.
1st problem:
When trying to start the sim axis, I get:
ModuleNotFoundError: No module named 'linuxcnc'
One more thing I should note, this is not a run-in-place environment. I am
working on updating the LinuxCNC Gentoo ebuild package, so this is a global
system install.
Alec
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://l
I paid my respects to the RTAI mailing list:
https://www.freelists.org/post/rtai/In-Memoriam-Prof-Paolo-Mantegazza,5
I will do the best I can to keep RTAI alive for LinuxCNC but without anymore
development on the mainline branch, there won't be much to do. I've already
fixed all the issues I coul
https://github.com/LinuxCNC/linuxcnc/compare/master...NTULINUX:linuxcnc:ntulinux/2.9-musl
LinuxCNC builds on musl now!
Thanks to BsAtHome and those from the musl community for all their input and
patches! I couldn't have done this myself.
Alec
___
E
Adding:
to:
src/libnml/buffer/tcpmem.cc
Fixed the build of tcpmem as well. Getting much closer now. I added some
comments to the issue that should definitely help fix the `basename` ones and
`pthread_attr_setaffinity_np`
We're practically almost done here.
Alec
__
Adding:
#include
to:
src/hal/user_comps/xhc-whb04b-6/usb.h
Fixed all of the `timeval` errors, so we are closer! Credit goes to BsAtHome.
Alec
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/
Hello everyone,
I opened up a bug report for LinuxCNC in respect to building it on a musl C
library based system instead of glibc. glibc is known for many security
vulnerabilities and code complexity, however I understand it is the default C
library for Debian.
With several Linux distributions
I keep getting timeouts and "site cannot be reached" errors, either the forums
take me 30 seconds to load or it breaks completely. Is it getting DDoS'd or
something? It's been really messed up the past few days.
Thanks,
Alec
___
Emc-developers maili
Hey everyone,
I haven't been following this thread too closely but I am curious... Can I see
a screenshot of the new proposed AXIS interface?
Thanks!
Alec
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge
As a Gentoo user, I only have one thing to say:
Don't expect external projects (i.e. not Gentoo) to revolve around your system.
LinuxCNC's main distribution that they support is Debian which has a default
shell of GNU Bash.
Alec
___
Emc-developers m
Andy,
A few people tested out your RTAI debs and ran into issues such as the infamous
"CANNOT FIND MAILBOX" error. I was able to figure out the root source of the
issue; your rtai-modules package does not match the 5.4.258 kernel you built.
I re-built the rtai-modules package for 5.4.258 which
Hello,
I know there's been some issues with getting around building documentation for
those that don't need it, so I did develop a brutal hack to make them go away.
This is not meant to be used as-is but rather be modified so it can fit cleanly
in the tree:
https://github.com/NTULINUX/linuxcnc
I haven't been following the docs issue too closely but this is all dead code
from what I gather:
debian/configure:
while test $# -ne 0; do
case "$1" in
noauto) BUILD_AUTO=false ;;
rtai) BUILD_RTAI=true ;;
rtai=*) BUILD_RTAI=true; RTAI_DEV=${1#rtai=} ;;
xenomai) BUILD_XENOMAI
Updated results:
Runtest: 259 tests run, 256 successful, 3 failed + 0 expected, 1 skipped
Failed:
/home/ntu/linuxcnc/tests/pyhal
/home/ntu/linuxcnc/tests/realtime-math
/home/ntu/linuxcnc/tests/symbols.0
realtime-math failed only because:
+ set -xe
+ halcompile --install r
He shoots HE SCORES!!!
SUBDIRS was being used again when it shouldn't be, I didn't remove all the
instances I guess. M= is the way to go, and I fixed the tests.
Commit:
https://github.com/NTULINUX/linuxcnc-rtai-gnu11/commit/867ac21bfa2138988d1fd800126be23cb3d4cb60
CHEERS!
Alec
_
Error for personalities_mod:
cat /home/ntu/linuxcnc/tests/halcompile/personalities_mod/stderr
+ set -e
+ halcompile --personalities=2 --install lincurve_test.comp
mkdir: cannot create directory '.tmp_41640': Permission denied
blah blah blah
mkdir: cannot create directory ‘.tmp_41846’: Permission d
Accidentally sent this directly to Andy instead of the mailing list..
Yes, SUBDIRS was deprecated a long time ago and then eventually removed, in
favor of M. The fix I made before was so 5.4 builds would work, however that
was only for the classic ./configure ; make method. Using M=$(PWD) doesn'
I thought my local changes to prevent docs from building if `no-docs` is set
was the reason for this breakage, but I reverted my doc changes and I still get
this error:
# `.../doc/linuxcnc`) because that's where the
# `linuxcnc` launcher script looks for them, and that's
# inconvenient to change
By using BASEPWD, there's some magic I don't quite understand but here it is:
ifeq ($(BASEPWD),)
BASEPWD := $(shell pwd)
export BASEPWD
include Makefile.inc
else
include $(BASEPWD)/Makefile.inc
endif
M=$(PWD)/src needs to be set if you're building LinuxCNC kernel modules from
the top directory o
The problem has to do with Kbuild, and I think I just found the right magic.
uspace doesn't use the M= value at all nor builds any kernel modules.
M=$(BASEPWD) seems to satisfy both ./configure builds and Debian packages.
Commit:
https://github.com/NTULINUX/linuxcnc-rtai-gnu11/commit/e8ece4358c
I mostly figured this out, both the docs issue and the module building issue.
As for docs, the `nodocs` option is completely ignored. When I fixed that, I
get:
# some clean-up
rm -f
/home/ntu/linuxcnc/debian/tmp/usr/share/doc/linuxcnc/examples/sample-configs/*/*position*.txt
make[1]: Leaving di
One thing to try, revert 3ee51e306bbe93d424dcdcc8429feaf0b9d6ef02
Thanks for the command lines, will dig soon.
Alec
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
What on the command line do you pass to trigger building LinuxCNC against RTAI?
I'll need the full ./debian/configure stuff and the dpkg-buildpackage strings
and whatever else is required. Treat me like I'm a total Debian noob :)
Alec
___
Emc-develop
I have hardly any experience writing Debian packages, and the ones for LinuxCNC
are quite complicated. I will try building your tree on my Debian system soon
and see if I can help at all. I hope someone else can chime in.
Alec
___
Emc-developers mail
I have no idea where your problem might be coming from but I'm guessing it
might be missing the "M" argument.
i.e.
$(PYTHON) modsilent.py $(MAKE) KBUILD_EXTRA_SYMBOLS=$(moduledir)/Module.symvers
-C $(KERNELDIR) M=$(PWD) CC=$(CC) V=$(BUILD_VERBOSE) modules
For the record, I have been able to bu
Hey, I ironed out the last few bugs with the gnu11-libm-kbuild branch.
Andy, when you start on RTAI again, use that branch as your starting point. I
already reverted LinuxCNC commit 3d926d87f14ada9dea313c2989ee8f24f0e54e0c
locally and it builds fine.
100% Kbuild is the way to go if it works.
A
I haven't tested this on real CNC hardware, just the sim axis, but I made an
attempt to move the musl libm library into Kbuild. This is so the harmless
undefined symbols in modules during the RTAI build (not LinuxCNC) are gone.
Originally, RTAI's build system would build musl's libm math library
Whelp, pull request submitted. Just be sure to test the math!
https://github.com/LinuxCNC/linuxcnc/pull/2685
The 2.9 branch will be broken with newer RTAI without this, so if it works in
master I'd cherry-pick it.
Alec
___
Emc-developers mailing lis
I can't tell because my C skills are pretty bad but looking at fmax and fmin,
I'm worried that the X and Y axis might be flipped for example:
LinuxCNC from rtapi_math.h:
extern __inline double fmax(double __y, double __x) {
return __y > __x || __builtin_isnan(__x) ? __y : __x;
}
extern __in
I can make a pull request, I'm pretty sure the appropriate fix is indeed the
correct fix. I think it'd be important to test the implementations of atan,
asin, acos, fmax and fmin to make sure all is well. LinuxCNC will report errors
if any of the math is wrong, yes? Say for example the accuracy
I don't exactly know why switching to GNU11 causes this issue, maybe the GNU11
standard already defines these, but I removed LinuxCNC's definitions of the
following functions:
atan
asin
acos
fmax
fmin
from rtapi_math.h
and had to remove -Werror=frame-larger-than=2560 from LinuxCNC's Makefile a
Oh crap, I'm seeing these too. This might be because of the gnu11 changes but
I'll have to look into this more. Yes, trig errors everywhere.
Alec
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/
Not a problem, I will build RTAI 5.4.256 kernel packages and rtai-modules with
the `gnu11` branch. Just be sure to revert the gnu89 commit for limit_axis when
testing the debs. I'm not sure when I'll exactly get around to this but I got
it.
Alec
___
I would do a `make mrproper` and follow these steps for the kernel build:
https://github.com/NTULINUX/RTAI/blob/gnu11/README.INSTALL
Then skip to line 92, Creating RTAI Debian packages
That's a really odd problem that I've never before. I was able to build RTAI
kernel and module packages on Deb
Yes, use the gnu11 branch in my RTAI tree and pick either 4.19.294 or or 5.4.256
As an additional layer of testing, revert the C89 commit in LinuxCNC to make
sure GNU11 `for` loops actually work as intended:
https://github.com/LinuxCNC/linuxcnc/commit/3d926d87f14ada9dea313c2989ee8f24f0e54e0c
If
Hi all,
Rene said I should switch RTAI to GNU11:
https://github.com/LinuxCNC/linuxcnc/commit/3d926d87f14ada9dea313c2989ee8f24f0e54e0c#commitcomment-128557906
I suppose the above commit could be reverted.
Would anyone be able to test LinuxCNC against the changes I'll be making to
RTAI? I can on
Moving forward, I can merge that C11 patch into RTAI so we don't have to worry
about C89/gnu89 anymore and you can just code how you please :-)
I haven't noticed any regressions with the little testing I did but there could
be something down road. I guess it depends on how often/how much C11 cod
I don't know if this code is right, I just copied and pasted the 32 versions
and made 64 versions where required.
https://github.com/LinuxCNC/linuxcnc/pull/2650
Undefined symbols are gone, please review before merging!
Alec
___
Emc-developers mailin
So, there are two ways of building kernel modules with GNU11 instead of gnu89
or C99.
1.) Do it in RTAI:
https://github.com/NTULINUX/RTAI/commit/a649bbb40fad9299ba31285276d9204df2f222d9
2.) Do it in LinuxCNC:
https://github.com/NTULINUX/linuxcnc/commit/a76b69f7e66f7a3831be655ea3dde4590502a175
mpatible kernel. When do we accept that RTAI is really yesterday's
technology? Where is the port to Xenomai 4?
Rod Webster
*1300 896 832*
+61 435 765 611
Vehicle Modifications Network
www.vehiclemods.net.au
On Wed, 20 Sept 2023 at 18:27, andy pugh wrote:
> On Wed, 20 Sept 2023 at 01:
See the links I posted, they link to the lines in the kernel Makefile, that's
where the gnu89 is coming from.
Seriously though, the proper way to fix this is to not use c11/gnu11 with 4.19
or 5.4 kernel sources. It probably won't even work and shouldn't be tried. 4.19
and 5.4 use gnu89.
https:
The kernel switched to GNU11 with 5.18. RTAI is still 4.19 and 5.4, meaning all
kernel space needs to be gnu89:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/Makefile?h=linux-4.19.y&id=dd5638bc06a6bf3f5ca1a134960911dc49484386#n375
https://git.kernel.org/pub/scm/linux/kern
Upon make:
Reading 205/205 dependency files
Done reading dependencies
MAKEFLAGS="" \
/usr/bin/python3.11 modsilent.py make
KBUILD_EXTRA_SYMBOLS=/usr/realtime-4.19.294-rtai-amd64/modules/Module.symvers
-C /usr/src/linux-headers-4.19.294-rtai-amd64 M=/home/ntu/linuxcnc/src CC=gcc
V=0 modules
make
Meant to say, if you set CONFIG_FRAME_WARN to 0, the last error I posted should
go away.
Alec
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
What's really odd is that src/objects/hal/components/raster.c:14:10: fatal
error: stdlib.h: No such file or directory
stdlib.h is part of the C library, it shouldn't be looking for stdlib.h in
kernel space, at all, ever.
Alec
___
Emc-developers mail
Thank you!!
Alec
On Wednesday, June 7, 2023 at 11:38:14 PM UTC, Sebastian Kuzminsky
wrote:
On 6/7/23 14:29, Alec Ari via Emc-developers wrote:
> 2.9 branch is still missing any recent Clang fixes, just throwing that out
> there as a reminder.
>
> https://github.com/Linux
2.9 branch is still missing any recent Clang fixes, just throwing that out
there as a reminder.
https://github.com/LinuxCNC/linuxcnc/pull/2214/commits
Alec
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge
I fixed the Gentoo package for now to fix the Clang 16 error, sed oneliner:
's#-Wl,--version-script,objects/\$\*.ver ##'
Just temporary until it gets fixed the right way.
ebuild:
https://github.com/NTULINUX/ntu_overlay/tree/main/sci-electronics/linuxcnc
Alec
_
Just my two cents, I use Gentoo for everything. When dealing with ARM64 boards
I start with a fully custom kernel and U-Boot image, and do the root filesystem
myself. I steer away from Debian due to poor performance. Gentoo isn't as
user-friendly so that's the trade off.
At least for AMD64 plat
.
https://github.com/LinuxCNC/linuxcnc/issues/2509
as a workaround you can just remove the version script, it isnt actually
needed.
Rene
On 26.05.23 02:50, Alec Ari via Emc-developers wrote:
> Yes but it's been awhile, I've actually done some U-Boot development in the
> past. This p
Oh, I see, I read the Github issue you posted:
https://apt.llvm.org/
Heh, that's pretty cool!
Alec
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
Yes but it's been awhile, I've actually done some U-Boot development in the
past. This problem with the linker is not kernel related though.
Alec
On Friday, May 26, 2023 at 12:00:10 AM UTC, gene heskett
wrote:
On 5/25/23 19:13, Alec Ari via Emc-developers wrote:
> 16.
wrote:
> On 26. May 2023, at 00:11, Alec Ari via Emc-developers
> wrote:
>
> Right, that's why I'm here. I don't know what's going on and need help. This
> is the last step then my Gentoo work is done and I can publish everything.
> LinuxCNC compiled be
and LLD than before.
Alec
On Thursday, May 25, 2023 at 10:50:44 AM UTC, renehopf--- via Emc-developers
wrote:
clang should work fine, there is a github ci job compiling with clang.
On 25.05.23 12:04, Alec Ari via Emc-developers
wrote:
> Hello,
>
> I think this might be becau
Hello,
I think this might be because I'm using Clang+LLD 16 but I'm not sure.. These
look like syntax errors, not an environment/cache issue.
Alec
> ld.lld: error: objects/enum.ver:4: ; expected, but got
> > > > @;
> > > > ^
> clang-16: error: linker command failed with exit code 1 (use -v to
Hi everyone,
I have built the Gentoo image for LinuxCNC, real-time kernel and all with
WiFi+wired ethernet support for many of the common USB NICs but now running
into trouble building LinuxCNC itself:
`make -j17`:
config.status: creating ../scripts/setup_designer
1 warning generated.
Creating
Just a heads up, Clang fixes still missing in 2.9..
Alec
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
Currently, the fixes for Clang are only in master, can these be merged into 2.9?
TIA,
Alec
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
Will give it a shot soon! Thanks!
On Friday, January 13, 2023 at 08:40:41 AM UTC, Sebastian Kuzminsky
wrote:
Does this work around the problem?
https://github.com/LinuxCNC/linuxcnc/issues/2264#issuecomment-1380954324
--
Sebastian Kuzminsky
___
Running Gentoo, just trying to get the sim axis window working again (not a
real-time kernel, just quick test)
ntu@ntu ~ $ linuxcnc
LINUXCNC - 2.10.0~pre0
Machine configuration directory is '/home/ntu/linuxcnc/configs/sim.axis'
Machine configuration file is 'axis.ini'
Starting LinuxCNC...
linuxcn
Yes it is! uvcvideo! Thanks!
Alec
On Sunday, January 8, 2023 at 06:12:33 PM UTC, gene heskett
wrote:
On 1/8/23 01:42, Alec Ari via Emc-developers wrote:
> Oh hey! Speaking of cameras, I'm working on a Gentoo image for LinuxCNC, it's
> like 90% of the way there, I have
Oh hey! Speaking of cameras, I'm working on a Gentoo image for LinuxCNC, it's
like 90% of the way there, I have an installer and everything, just need to
test it on CNC hardware.. Are the cameras you guys use for camview fall under
UVC (USB_VIDEO_CLASS / uvcvideo) or something else? Trying to av
Both of these files are different, all authors are arguably correct. Paolo
doesn't work on LinuxCNC, he didn't write the one in LinuxCNC. The LinuxCNC one
is based off other work, and Paolo's as well.
My vote is on not a bug, not an issue.
Alec
On Monday, December 5, 2022 at 08:37:28 AM CS
Subject
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
6:12:08 PM CST, andy pugh
wrote:
On Wed, 23 Nov 2022 at 21:10, Alec Ari via Emc-developers
wrote:
>
> Ok, with that being said, we should stop saying RTAI cannot/will not be
> tested. I keep reading that among/amongst the mailing list.
No, I for one remain keen on retaining RTAI s
Ok, with that being said, we should stop saying RTAI cannot/will not be tested.
I keep reading that among/amongst the mailing list.
Alec
On Wednesday, November 23, 2022 at 02:44:43 PM CST, Sebastian Kuzminsky
wrote:
On 11/23/22 12:19, Alec Ari via Emc-developers wrote:
> OK, so t
OK, so that should work with the Github CI/CD too then, right?
Alec
On Wednesday, November 23, 2022 at 10:45:58 AM CST, Sebastian Kuzminsky
wrote:
On 11/23/22 09:02, Alec Ari via Emc-developers wrote:
> With CI/CD, can't you have it do a `runtests` in a run-in-place
> env
With CI/CD, can't you have it do a `runtests` in a run-in-place environment? I
could also write a simple RTAI test program (even more simple than the
testsuite/built-in latency test) that'll just load and exit.
Alec
On Wednesday, November 23, 2022 at 04:38:42 AM CST, Jérémie Tarot
wrote:
RTAI kernel 5.4 Debian packages are up!
https://github.com/NTULINUX/RTAI/releases/tag/v5.3.3-delta
If these check out OK for you guys, I'll mark it as stable and merge this into
my `master` branch.
Alec
___
Emc-developers mailing list
Emc-developers
I can make sure RTAI works with LinuxCNC myself, no need for Seb's stuff or
anyone's VMs for that matter. Adding back in RTAI support though to the
LinuxCNC Debian configure script would be helpful. I started on it but it's not
finished.
https://github.com/LinuxCNC/linuxcnc/issues/2052
In case
I don't mind building LinuxCNC RTAI packages but the problem is actually a
license problem. LinuxCNC keeps complaining after the ./configure about how
it's a non-distributable build, but that flag has to be set due to the readline
GPL-v2/LGPL starting with Debian Bullseye, otherwise the configur
It'd be nice if people got off their high horse and just shared the keys with
you. I don't know what's going on anymore with LinuxCNC.
Alec
On Friday, November 11, 2022 at 07:07:40 PM CST, andy pugh
wrote:
I can't do it.
Previously the buildbot was integral to the process, but the bu
I'll be happy to maintain Bookworm RTAI Debian packages too.
Alec
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
difications 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 up
t.au
On Thu, 10 Nov 2022 at 07:55, andy pugh 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
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 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 t
POSIX threads and RTAI on the
same kernel removing the need to reboot. Not really a LinuxCNC question though,
please no ban.
Alec
- Forwarded Message -
From: Alec Ari
To: Rtai
Sent: Sunday, November 6, 2022 at 07:01:45 PM CST
Subject: Attempt at RTAI and PREEMPT_RT (same kernel)
Hello
I could build a Gentoo image with PREEMPT_RT and hardware 3D acceleration with
LinuxCNC using this:
https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git/log/?h=linux-6.1.y-rt&qt=grep&q=rk3328
Coupled with a bleeding edge X.org stack (mesa etc) with all the codecs.
The RK3328 us
Rainer,
Thank you so much! I will add back in the ACPI power states for software
shutdown capability and then roll out the 5.4 kernels. The crashing bug was
actually fixed by Jepler, excessively unloading and reloading RTAI would cause
crashes. Glad my FPU changes work on Intel!
Alec
On
Hi everyone,
I'll be working on kernel 5.4 RTAI packages for Debian Bullseye soon, just want
to test these changes on different hardware before it rolls out. Please test
rebooting and shutdown. I removed ACPI power states, this should improve
performance but may require holding power button dow
the 4.19 debs would be just a final test before I
roll out RTAI kernel 5.4 packages.
Alec
On Saturday, October 29, 2022 at 10:59:40 AM CDT, andy pugh
wrote:
On Sat, 29 Oct 2022 at 08:02, Alec Ari via Emc-developers
wrote:
> Hi everyone,
>
> So I'm trying to
Hi everyone,
So I'm trying to host LinuxCNC + RTAI packages for Bullseye but I have to use
--enable-non-distributable=yes and there is no libreadline-gplv2-dev package in
Bullseye. Is it really an issue to post a LGPL/GPL mixed package? Who would
actually be upset by a conflicting GPL/LGPL lice
le to load modules (i.e. before udev
is loaded but you want kernel modesetting) but if you're not a kernel hacker,
really no need.
Probably too much info but now you know!
Alec
On Monday, October 24, 2022 at 10:43:52 PM UTC, Jon Elson
wrote:
On 10/24/22 15:28, Alec Ari via Emc-
Jon,
You can actually grab the sid 6.0 kernel and drop it on Bullseye and perhaps
even Buster:
https://packages.debian.org/sid/linux-image-6.0.0-2-amd64
Firmware:
https://packages.debian.org/sid/firmware-misc-nonfree
Install:
sudo dpkg -i linux-image-6.0.0-2-amd64_6.0.3-1_amd64.deb
sudo dpkg
Warnings for 5.4 kernel, note: [-Wvla]
Reading 0/204 dependency files
Done reading dependencies
Reading 0/204 dependency files
Done reading dependencies
In file included from hal/utils/halcmd_commands.cc:40:
hal/utils/halcmd_commands.cc: In function ‘int do_loadrt_cmd(char*, char**)’:
./config.h:4
To clarify, you still need to use M instead of SUBDIRS, but the "FATAL: parse
error in symbol dump file" was 100% PEBKAC lol.
Alec
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-de
Scratch that, I did a dumb thing with my build system. LinuxCNC works with RTAI
5.4 now, screenshot attached.
WOOO!
Alec___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
All the LinuxCNC kernel modules build now against 5.4 albeit with several VLA
(variable length array) warnings and this fatal error at the very end:
MODPOST 185 modules
FATAL: parse error in symbol dump file
make[2]: *** [scripts/Makefile.modpost:95: __modpost] Error 1
make[1]: *** [Makefile:16
Found the problem:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/Makefile?h=v5.4.219&id=7e35b42591c058b91282f95ce3b2cf0c05ffe93d
Fix:
diff --git a/src/Makefile b/src/Makefile
index 96eba38334..047419d4bc 100644
--- a/src/Makefile
+++ b/src/Makefile
@@ -537,8 +537,8 @@ i
This error:
> cp Module.symvers *.ko ../rtlib/
> cp: cannot stat 'Module.symvers': No such file or directory
Is a red herring. Fix:
diff --git a/src/Makefile b/src/Makefile
index 96eba38334..374b4bf35d 100644
--- a/src/Makefile
+++ b/src/Makefile
@@ -538,7 +538,7 @@ ifeq ($(BUILD_SYS),kbuild)
mo
1 - 100 of 333 matches
Mail list logo
