Updated install of machinekit -- new errors

[mugginsac]

I did sudo apt-get install machinekit. Now I get a bunch of new messages.

I am trying to figure out if I somehow screwed up my configs in the process of updating machinekit. Here is a link to my .ini file. Here is a link to my .hal file.

I have also attached a screen capture of the error/warning message that appeared on the axis screen.

cat /var/log/linuxcnc.log gives:

Feb 26 01:18:01 beaglebone msgd:0: startup pid=2670 flavor=rt-preempt rtlevel=1 usrlevel=1 halsize=524288 shm=Posix cc=gcc 6.3.0 20170516  version=v0.1~-----~01fe624
Feb 26 01:18:01 beaglebone msgd:0: ØMQ=4.2.1 czmq=4.0.2 protobuf=3.0.0 atomics=gcc intrinsics    libwebsockets=2.0.3
Feb 26 01:18:01 beaglebone msgd:0: configured: sha=01fe624
Feb 26 01:18:01 beaglebone msgd:0: built:      Feb 25 2019 07:42:47 sha=01fe624
Feb 26 01:18:01 beaglebone msgd:0: register_stuff: actual hostname as announced by avahi='beaglebone.local'
Feb 26 01:18:01 beaglebone msgd:0: zeroconf: registering: 'Log service on beaglebone.local pid 2670'
Feb 26 01:18:02 beaglebone msgd:0: zeroconf: registered 'Log service on beaglebone.local pid 2670' _machinekit._tcp 0 TXT "uuid=471405b7-f524-4f2a-9697-6061a9855992" "instance=5c216bac-3964-11e9-9408-7c669d58a259" "service=log" "dsn=ipc:///tmp/0.log.471405b7-f524-4f2a-9697-6061a9855992"
Feb 26 01:18:03 beaglebone msgd:0: hal_lib:2675:rt memmapped gpio port 2 to 0xb6fb1000, oe: 0xb6fb1134, set: 0xb6fb1194, clr: 0xb6fb1190
Feb 26 01:18:03 beaglebone msgd:0: hal_lib:2675:rt pin 9 maps to pin 2-5, mode 85
Feb 26 01:18:03 beaglebone msgd:0: hal_lib:2675:rt pin 10 maps to pin 2-4, mode 85
Feb 26 01:18:03 beaglebone msgd:0: hal_lib:2675:rt memmapped gpio port 0 to 0xb6faf000, oe: 0xb6faf134, set: 0xb6faf194, clr: 0xb6faf190
Feb 26 01:18:03 beaglebone msgd:0: hal_lib:2675:rt pin 14 maps to pin 0-26, mode 85
Feb 26 01:18:03 beaglebone msgd:0: hal_lib:2675:rt pin 18 maps to pin 2-1, mode 85
Feb 26 01:18:03 beaglebone msgd:0: hal_lib:2675:rt memmapped gpio port 1 to 0xb6fad000, oe: 0xb6fad134, set: 0xb6fad194, clr: 0xb6fad190
Feb 26 01:18:03 beaglebone msgd:0: hal_lib:2675:rt hpg_stepgen_init
Feb 26 01:18:09 beaglebone rtapi:0: unload: '' not loaded
Feb 26 01:18:09 beaglebone rtapi:0: unload: '' not loaded
Feb 26 01:18:09 beaglebone rtapi:0: unload: '' not loaded
Feb 26 01:18:09 beaglebone rtapi:0: unload: '' not loaded
Feb 26 01:18:09 beaglebone rtapi:0: unload: '' not loaded
Feb 26 01:18:09 beaglebone rtapi:0: unload: '' not loaded
Feb 26 01:18:09 beaglebone rtapi:0: unload: '' not loaded
Feb 26 01:18:09 beaglebone msgd:0: rtapi_app exit detected - scheduled shutdown
Feb 26 01:18:11 beaglebone msgd:0: msgd shutting down
Feb 26 01:18:11 beaglebone msgd:0: zeroconf: unregistering 'Log service on beaglebone.local pid 2670'
Feb 26 01:18:11 beaglebone msgd:0: log buffer hwm: 0% (8 msgs, 699 bytes out of 524288)
Feb 26 01:18:11 beaglebone msgd:0: normal shutdown - global segment detached

machinekit@beaglebone:~$ cat linuxcnc_debug.txt

2648
  PID TTY      STAT   TIME COMMAND
Stopping realtime threads
Unloading hal components

machinekit@beaglebone:~$ cat linuxcnc_print.txt
RUN_IN_PLACE=no
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/usr/bin
LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/usr/lib/linuxcnc
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/usr/share/linuxcnc/tcl/msgs
INIVAR=/usr/libexec/linuxcnc/inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.6
INIFILE=/home/machinekit/machinekit/configs/ARM.BeagleBone.Xylotex/Xylotex.ini
PARAMETER_FILE=pru-stepper.var
TASK=milltask
HALUI=halui
DISPLAY=axis
Starting Machinekit server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting Machinekit IO program: io
Starting HAL User Interface program: halui
Killing task linuxcncsvr, PID=2648
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments

[mugginsac]

Found the culprits. Three more calls to rtapi_print() affected by the change from RTAPI_MSG_ERR to RTAPI_MSG_ALL.

But I have seemingly created a bug in my config in the process of cleaning them up.

The axis screen appears for a fraction of a second and then disappears.

[Bas de Bruijn]

Did you “export DEBUG=5” before the /var/log/linuxcnc.log?

[Condit Alan]

Bas,

The answer would be yes and no. After I first ran it, and saw the new messages, I knew people would want to see it with debugging support in order to help, I ran it again after “export DEBUG=5”. In essence the new messages in /var/log/linuxcnc.log were identical and there weren’t any errors in the earlier stuff in the log. But, it wasn’t until shortly after I posted it that the significance hit me and that was when I started searching for where those new messages were coming from.

How long after a pull request is moved to master, will a “sudo apt-get install machinekit” get the updated files from a build? Or should I set up a cross build on my linux pc and build from source?

Alan

[Bas de Bruijn]

> On 26 Feb 2019, at 23:32, Condit Alan <mugg...@gmail.com> wrote:
>
> Bas,
>
> The answer would be yes and no. After I first ran it, and saw the new messages, I knew people would want to see it with debugging support in order to help, I ran it again after “export DEBUG=5”. In essence the new messages in /var/log/linuxcnc.log were identical and there weren’t any errors in the earlier stuff in the log. But, it wasn’t until shortly after I posted it that the significance hit me and that was when I started searching for where those new messages were coming from.
>
> How long after a pull request is moved to master, will a “sudo apt-get install machinekit” get the updated files from a build? Or should I set up a cross build on my linux pc and build from source?

I dont know specifics, but something like 1 to 2 hrs.

>
> Alan
>
>
>
>> On Feb 25, 2019, at 10:18 PM, Bas de Bruijn <b...@basdebruijn.com> wrote:
>>
>>
>>
>>> On 26 Feb 2019, at 06:32, mugginsac <mugg...@gmail.com> wrote:
>>>
>>> Found the culprits. Three more calls to rtapi_print() affected by the change from RTAPI_MSG_ERR to RTAPI_MSG_ALL.
>>> But I have seemingly created a bug in my config in the process of cleaning them up.
>>> The axis screen appears for a fraction of a second and then disappears.
>>
>> Did you “export DEBUG=5” before the /var/log/linuxcnc.log?
>

> --
> website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit
> ---
> You received this message because you are subscribed to the Google Groups "Machinekit" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+...@googlegroups.com.
> Visit this group at https://groups.google.com/group/machinekit.
> For more options, visit https://groups.google.com/d/optout.

[schoo...@gmail.com]

Just check the repo to see if there is a new package with the right git
Sha to match the commit

[Condit Alan]

What is the url for the repository?

> --
> website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit

> --- You received this message because you are subscribed to a topic in the Google Groups "Machinekit" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/machinekit/twyuwZByyoA/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to machinekit+...@googlegroups.com.

[Bas de Bruijn]

On 27 Feb 2019, at 18:53, Condit Alan <mugg...@gmail.com> wrote:

What is the url for the repository?

https://github.com/machinekit/machinekit

I think we’re talking about the packages :)

That one is here:

http://deb.machinekit.io/debian/pool/main/m/machinekit/

You received this message because you are subscribed to the Google Groups "Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+...@googlegroups.com.

[Alan Condit]

I searched through the .debs in the repository and didn’t find the sha for either of the last two pulls.

[ce...@tuta.io]

Hello,

just to be certain, you don't mean SHA of the puller commit, right? It's SHA of the merge commit. (Last one is http://deb.machinekit.io/debian/pool/main/m/machinekit/machinekit-posix_0.1.1551246384.gitdc0dd15-1~stretch_amd64.deb for example)

C.

Dne středa 27. února 2019 22:58:53 UTC+1 mugginsac napsal(a):

[Alan Condit]

I was looking for either, but I need the rtpreempt for arm.

[ce...@tuta.io]

Should be these:

http://deb.machinekit.io/debian/pool/main/m/machinekit/machinekit-rt-preempt_0.1.1551246384.gitdc0dd15-1~stretch_armhf.deb

http://deb.machinekit.io/debian/pool/main/m/machinekit/machinekit_0.1.1551246384.gitdc0dd15-1~stretch_armhf.deb

Cannot it be browser caching? Can you see them with apt?

C.

Dne čtvrtek 28. února 2019 0:11:09 UTC+1 mugginsac napsal(a):

[Condit Alan]

Cern,

Thanks, I have only done install or upgrades on the beaglebone black via “sudo apt-get install machinekit”.

So, I don’t even know how to get apt to install those particular versions.

I am more used to using synaptic on my linux pc.

I finally found them with my browser. I wasn’t looking for the second package.

I saw a notice about installing machinekit-hal and machinekit-cnc, I don’t know whether that has complicated issues also.

I tried install machinekit and got an error message

machinekit@beaglebone:~$ sudo apt-get install machinekit

Reading package lists... Done

Building dependency tree       

Reading state information... Done

Some packages could not be installed. This may mean that you have

requested an impossible situation or if you are using the unstable

distribution that some required packages have not yet been created

or been moved out of Incoming.

The following information may help to resolve the situation:

The following packages have unmet dependencies:

 machinekit : Depends: machinekit-rt-threads

              Depends: python-gst0.10 but it is not installable

E: Unable to correct problems, you have held broken packages.

I tried install machinekit-rt-preempt and got an error message

machinekit@beaglebone:~$ sudo apt-get install machinekit-rt-preempt

Reading package lists... Done

Building dependency tree       

Reading state information... Done

Some packages could not be installed. This may mean that you have

requested an impossible situation or if you are using the unstable

distribution that some required packages have not yet been created

or been moved out of Incoming.

The following information may help to resolve the situation:

The following packages have unmet dependencies:

 machinekit-rt-preempt : Depends: machinekit (= 0.1.1551246384.gitdc0dd15-1~stretch) but 0.1.1551000781.git82d727d-1~stretch is to be installed

E: Unable to correct problems, you have held broken packages.

So, then I tried install machinekit machinekit-rt-preempt

machinekit@beaglebone:~$ sudo apt-get install machinekit machinekit-rt-preempt

Reading package lists... Done

Building dependency tree       

Reading state information... Done

Some packages could not be installed. This may mean that you have

requested an impossible situation or if you are using the unstable

distribution that some required packages have not yet been created

or been moved out of Incoming.

The following information may help to resolve the situation:

The following packages have unmet dependencies:

 machinekit : Depends: python-gst0.10 but it is not installable

 machinekit-rt-preempt : Depends: machinekit (= 0.1.1551246384.gitdc0dd15-1~stretch) but 0.1.1551264903.git0634d7c-1~stretch is to be installed

E: Unable to correct problems, you have held broken packages.

Do I need to purge and start over? 

How do I get apt to show me the files that I need to use?

There used to be a way to download a particular .deb and install it. Is that still possible?

Alan

[schoo...@gmail.com]

Please say what you are installing on what.

You appear to be trying to install a Jessie package on Stretch, because Jessie is the only one with that version dependency.

So make sure your sources.list is correct and run apt update first

Yes for now, purge your packages and reinstall

I will check later that the packages contain what they should.

--
website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit
---

You received this message because you are subscribed to the Google Groups "Machinekit" group.

To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+...@googlegroups.com.

[schoo...@gmail.com]

OK

I have found the problem, an unintended corruption of the package name, causing an overwrite in the Packages text and
linking to the wrong package.

I have pushed a fix, but it needs to be tested, merged and in the meanwhile I may need to purge the repo or it will not correct

[schoo...@gmail.com]

Now hopefully fixed the problem and new packages in the repo

Purge your old packages, do an apt update and then install again.

[Condit Alan]

Schooner,

Sorry for not saying but yes, I was/am installing for Beaglebone Black on Stretch.
I was able to purge and re-install. The fixes are there and machinekit now appears to run properly (in house).

Now I have to take it back out to the shop and test on the X2 CNC minimill.

Now I also need to test my fixes on the BeBoPr-Bridge and CRAMPS machines
to verify no typos crept in or fix them if they did.

I think I have finally figured out the correct way to push corrections to “machinekit”,
but now they want us to only push to “machinekit-cnc” or “machinekit-hal”???? Oh, well,
live (hopefully) and keep on learning!!!

Thanks,
Alan

[mugginsac]

OK, I got machinekit loading on my BeBoPr-Bridge, my CRAMPS board and my Xylotex-DB25.

I posted another set of edits of the configs for the three of them. I posted them to machinekit-cnc this time.

Basically, I think the configs were what I posted previously to machinekit, but somehow either I missed some things

or they didn't get transferred from machinekit to machinekit-cnc. Either way they are there now (as soon as someone approves the pull request).

The Xylotex is running my X2 CNC-MiniMill and it now boots in a reasonable time. It also jogs nicely and homes correctly.

So, thank you Schooner, Bas, Charles, Cern and anyone else I forgot.

[Bas de Bruijn]

Glad you got it working.
PR is being tested and will be merged quickly
Bas