Testers Needed for New RTAI Packages
- tommylight
- Away
- Moderator
Less
More
- Posts: 19190
- Thank you received: 6433
06 Jan 2020 04:34 #154122
by tommylight
Replied by tommylight on topic Testers Needed for New RTAI Packages
What does "xrandr" say ?
If that does not list your screen resolution, it most probably will not work. Been a long time since i messed with that.
If that does not list your screen resolution, it most probably will not work. Been a long time since i messed with that.
Please Log in or Create an account to join the conversation.
06 Jan 2020 04:48 #154124
by phillc54
Replied by phillc54 on topic Testers Needed for New RTAI Packages
xrandr shows 1024 x 768, 800 x 600 and 640 x 480
I think that is because it reverts back to the vesa driver because of not being able to run the frambuffer driver.
I think that is because it reverts back to the vesa driver because of not being able to run the frambuffer driver.
Please Log in or Create an account to join the conversation.
11 Jan 2020 15:59 #154624
by JohnnyCNC
I looked in Menu>Administration and I don't see that option. The closest thing I could find is this.
I am getting this error and I could find this/these in Synaptic.
I also saw this when debuild -uc -us finished running.
W: linuxcnc-uspace: executable-not-elf-or-script usr/share/linuxcnc/ncfiles/lathe/turning.ngc
W: linuxcnc-uspace: executable-not-elf-or-script usr/share/doc/linuxcnc/examples/sample-configs/sim/gmoccapy/lathe_configs/boring.ngc
W: linuxcnc-uspace: executable-not-elf-or-script usr/share/doc/linuxcnc/examples/sample-configs/nc_files/lathe/facing.ngc
W: linuxcnc-uspace: executable-not-elf-or-script usr/share/linuxcnc/ncfiles/lathe/chamfer.ngc
W: linuxcnc-uspace: executable-not-elf-or-script usr/share/doc/linuxcnc/examples/sample-configs/nc_files/lathe/radius.ngc
W: linuxcnc-uspace: dev-pkg-without-shlib-symlink usr/lib/libpyplugin.so.0 usr/lib/libpyplugin.so
W: linuxcnc-uspace: init.d-script-does-not-source-init-functions etc/init.d/realtime
W: linuxcnc-uspace: udev-rule-missing-subsystem lib/udev/rules.d/99-xhc.rules:2 vendor/product matching missing SUBSYSTEM specifier
W: linuxcnc-uspace-dev: syntax-error-in-debian-changelog line 8 "found start of entry where expected more change data or trailer"
W: linuxcnc-uspace-dev: priority-extra-is-replaced-by-priority-optional
W: linuxcnc-uspace-dev: manpage-has-errors-from-man usr/share/man/man3/hal_stream.3hal.gz 51: warning: macro 'They' not defined
Finished running lintian.
I was following the instructions for "Debian 10 LinuxCNC" at www.gnipsel.com/linuxcnc/uspace/debian10-emc.html
I may try Linux Mint 19.1 using a spare SSD I have and see how that goes.
Replied by JohnnyCNC on topic Testers Needed for New RTAI Packages
You have to enable "source code" repositories in the "software sources" from the main menu>administration.I did not successfully install 28. I got a bunch of dependency issues.
sudo dpkg --install linuxcnc_2.8.0.pre1.4891.gadf1eff73_amd64.deb
I looked in Menu>Administration and I don't see that option. The closest thing I could find is this.
I am getting this error and I could find this/these in Synaptic.
I also saw this when debuild -uc -us finished running.
W: linuxcnc-uspace: executable-not-elf-or-script usr/share/linuxcnc/ncfiles/lathe/turning.ngc
W: linuxcnc-uspace: executable-not-elf-or-script usr/share/doc/linuxcnc/examples/sample-configs/sim/gmoccapy/lathe_configs/boring.ngc
W: linuxcnc-uspace: executable-not-elf-or-script usr/share/doc/linuxcnc/examples/sample-configs/nc_files/lathe/facing.ngc
W: linuxcnc-uspace: executable-not-elf-or-script usr/share/linuxcnc/ncfiles/lathe/chamfer.ngc
W: linuxcnc-uspace: executable-not-elf-or-script usr/share/doc/linuxcnc/examples/sample-configs/nc_files/lathe/radius.ngc
W: linuxcnc-uspace: dev-pkg-without-shlib-symlink usr/lib/libpyplugin.so.0 usr/lib/libpyplugin.so
W: linuxcnc-uspace: init.d-script-does-not-source-init-functions etc/init.d/realtime
W: linuxcnc-uspace: udev-rule-missing-subsystem lib/udev/rules.d/99-xhc.rules:2 vendor/product matching missing SUBSYSTEM specifier
W: linuxcnc-uspace-dev: syntax-error-in-debian-changelog line 8 "found start of entry where expected more change data or trailer"
W: linuxcnc-uspace-dev: priority-extra-is-replaced-by-priority-optional
W: linuxcnc-uspace-dev: manpage-has-errors-from-man usr/share/man/man3/hal_stream.3hal.gz 51: warning: macro 'They' not defined
Finished running lintian.
I was following the instructions for "Debian 10 LinuxCNC" at www.gnipsel.com/linuxcnc/uspace/debian10-emc.html
I may try Linux Mint 19.1 using a spare SSD I have and see how that goes.
Attachments:
Please Log in or Create an account to join the conversation.
12 Jan 2020 00:52 - 12 Jan 2020 01:08 #154655
by JohnnyCNC
Replied by JohnnyCNC on topic Testers Needed for New RTAI Packages
I loaded Linux Mint 19.2, RTAI 4.14.148 and 2.8.0~Pre1
uname -a shows:
Linux X3CNC 4.14.148-rtai-amd64 #2 SMP PREEMPT Sat Nov 9 16:29:10 GMT 2019 x86_64 x86_64 x86_64 GNU/Linux
I am getting an error when starting LinuxCNC of "in 'estop-latch.1.ok-out' does not exist" so I tried to run halshow pins aand I get this:
john@X3CNC:~$ halshow
RTAPI: ERROR: could not open shared memory (No such file or directory)
HAL: ERROR: could not initialize RTAPI
halcmd: hal_init() failed: -22
NOTE: 'rtapi' kernel module must be loaded
Segmentation fault (core dumped)
john@X3CNC:~$
Does this indicate what I did wrong?
Thanks
John
uname -a shows:
Linux X3CNC 4.14.148-rtai-amd64 #2 SMP PREEMPT Sat Nov 9 16:29:10 GMT 2019 x86_64 x86_64 x86_64 GNU/Linux
I am getting an error when starting LinuxCNC of "in 'estop-latch.1.ok-out' does not exist" so I tried to run halshow pins aand I get this:
john@X3CNC:~$ halshow
RTAPI: ERROR: could not open shared memory (No such file or directory)
HAL: ERROR: could not initialize RTAPI
halcmd: hal_init() failed: -22
NOTE: 'rtapi' kernel module must be loaded
Segmentation fault (core dumped)
john@X3CNC:~$
Does this indicate what I did wrong?
Thanks
John
Last edit: 12 Jan 2020 01:08 by JohnnyCNC.
Please Log in or Create an account to join the conversation.
12 Jan 2020 17:18 - 12 Jan 2020 17:18 #154693
by andypugh
Replied by andypugh on topic Testers Needed for New RTAI Packages
To run halshow you need to be linked in to the running realtime.
So, with linuxCNC running:
halcmd -kf
loadusr halshow
Or, simpler
halcmd -kf
show pins
Or, even:
halcmd show pins
So, with linuxCNC running:
halcmd -kf
loadusr halshow
Or, simpler
halcmd -kf
show pins
Or, even:
halcmd show pins
Last edit: 12 Jan 2020 17:18 by andypugh.
Please Log in or Create an account to join the conversation.
12 Jan 2020 23:57 #154731
by JohnnyCNC
Replied by JohnnyCNC on topic Testers Needed for New RTAI Packages
I reloaded everything. I have good latency of 19100. But when I start LinuxCNC I get an error of:
insmod: ERROR: could not insert module /usr/realtime-4.14.148-rtai-amd65/modules/rtai_hal.ko: File exists 8456
Kernel message information:
/usr/lib/tcltk/linuxcnc/show_erros.tcl:
dmesg: read kernel buffer failed: Operation not permitted
dmesg requires root privlege on this system.
Now, what I think I am seeing in this. The error after the ERROR label and a secondary error of not being able to call dmesg to display the dmesg info.
I did a find and as it says "/usr/realtime-4.14.148-rtai-amd64/modules/rtai_hal.ko" does exist.
No what?
Thanks
John
insmod: ERROR: could not insert module /usr/realtime-4.14.148-rtai-amd65/modules/rtai_hal.ko: File exists 8456
Kernel message information:
/usr/lib/tcltk/linuxcnc/show_erros.tcl:
dmesg: read kernel buffer failed: Operation not permitted
dmesg requires root privlege on this system.
Now, what I think I am seeing in this. The error after the ERROR label and a secondary error of not being able to call dmesg to display the dmesg info.
I did a find and as it says "/usr/realtime-4.14.148-rtai-amd64/modules/rtai_hal.ko" does exist.
No what?
Thanks
John
Please Log in or Create an account to join the conversation.
13 Jan 2020 00:33 #154733
by andypugh
Replied by andypugh on topic Testers Needed for New RTAI Packages
Try sudo dmesg
Did you "sudo make setuid" after compiling LinuxCNC?
(Did you compile LinuxCNC?)
Did you "sudo make setuid" after compiling LinuxCNC?
(Did you compile LinuxCNC?)
Please Log in or Create an account to join the conversation.
13 Jan 2020 03:18 #154736
by JohnnyCNC
Replied by JohnnyCNC on topic Testers Needed for New RTAI Packages
I did not compile LinuxCNC. I used the files from www.linuxcnc.org/temp. I did have some success. I can now start LinuxCNC. I am now working on getting the .hal file for my P4S pendant converted. I'm sure there are still some issues with my LinuxCNC .hal & .ini files but at least I was able to start it and get a list of pin names.
Is there a list that shows the old and new pin names side by side?
One other thing I need to do is to get it to boot into the rtai kernel by default. I think there is a grub manager program for that.
Thanks
John
Is there a list that shows the old and new pin names side by side?
One other thing I need to do is to get it to boot into the rtai kernel by default. I think there is a grub manager program for that.
Thanks
John
Please Log in or Create an account to join the conversation.
- twoflowers
- Offline
- User is blocked
Less
More
- Posts: 120
- Thank you received: 32
13 Jan 2020 08:22 #154742
by twoflowers
Replied by twoflowers on topic Testers Needed for New RTAI Packages
Just remove all other kernels, leaving only the RTAI kernel.
Please Log in or Create an account to join the conversation.
13 Jan 2020 10:23 - 13 Jan 2020 10:24 #154748
by andypugh
The internet suggests that the commandwill configure grub to boot into the last-selected kernel.
(there are other suggestions, but that seems the simplest, if it works)
Replied by andypugh on topic Testers Needed for New RTAI Packages
One other thing I need to do is to get it to boot into the rtai kernel by default. I think there is a grub manager program for that.
The internet suggests that the command
sudo grub-set-default saved
(there are other suggestions, but that seems the simplest, if it works)
Last edit: 13 Jan 2020 10:24 by andypugh.
Please Log in or Create an account to join the conversation.
Time to create page: 0.162 seconds