Upgrading from Axis 2.3.1
cnc@cnc:~$ dmesg
[12133.814670] I-pipe: head domain RTAI registered.
[12133.814673] RTAI[hal]: compiled with gcc version 4.7.2 (Debian 4.7.2-5) .
[12133.814749] RTAI[hal]: mounted (IPIPE-NOTHREADS, IMMEDIATE (INTERNAL IRQs DISPATCHED), ISOL_CPUS_MASK: 0).
[12133.814751] SYSINFO: CPUs 8, LINUX APIC IRQ 2312, TIM_FREQ 6235080, CLK_FREQ 3592032000, CPU_FREQ 3592032000
[12133.814752] RTAI_APIC_TIMER_IPI: RTAI DEFINED 2314, VECTOR 2314; LINUX_APIC_TIMER_IPI: RTAI DEFINED 2312, VECTOR 2312
[12133.814754] TIMER NAME: lapic; VARIOUSLY FOUND APIC FREQs: 6235080, 6235080, 6132750
[12133.817628] RTAI[malloc]: global heap size = 2097152 bytes, <BSD>.
[12133.817649] , <uses LINUX SYSCALLs>, kstacks pool size = 524288 bytes.
[12133.817652] RTAI[sched]: hard timer type/freq = APIC/6235080(Hz); default timing: oneshot; linear timed lists.
[12133.817653] RTAI[sched]: Linux timer freq = 250 (Hz), TimeBase freq = 3592032000 hz.
[12133.817654] RTAI[sched]: timer setup = 999 ns, resched latency = 2943 ns.
[12133.821057] RTAI[math]: loaded.
[12149.653088] MOTENC: ERROR, unknown card detected
[12154.518172] RTAI[math]: unloaded.
[12154.518987] SCHED releases registered named ALIEN PEDV$D
[12154.520330] RTAI[malloc]: unloaded.
[12154.617575] RTAI[sched]: unloaded (forced hard/soft/hard transitions: traps 0, syscalls 0).
[12154.618407] I-pipe: head domain RTAI unregistered.
[12154.618491] RTAI[hal]: unmounted.
cnc@cnc:~$
Please Log in or Create an account to join the conversation.
It looks like the version with my changes has finished compiling, if you update now you should get a bit more info about what is going on (and the driver might even work)
Please Log in or Create an account to join the conversation.
cheers
Please Log in or Create an account to join the conversation.
To explain what I have done, I have made it so that when it finds an unknown card type it tells us what it found, and (at the moment) it assumes a Motenc-lite and carries on regardless....
Please Log in or Create an account to join the conversation.
It looks like the version with my changes has
finished compiling, if you update now ...
But note the buildbot had a problem (purple color):
retry
compile
exception
slave
lost
And no debs (including your commit 0044b8caf) will be made
until the buildbot offline slave is revived
Ref: buildbot.linuxcnc.org/buildbot/grid
Ref: current wheezy debs for rtai,i386:
buildbot.linuxcnc.org/dists/wheezy/master-rt/binary-i386/
Please Log in or Create an account to join the conversation.
But note the buildbot had a problem (purple color):It looks like the version with my changes has
finished compiling, if you update now ...
And no debs (including your commit 0044b8caf) will be made
I hadn't realised that the failure in a different OS / Realtime would prevent debs being made.
And as far as I can see this is nothing to do with my changes?
Hopefully things will be back in order by monday.
Please Log in or Create an account to join the conversation.
I hadn't realised that the failure in a different OS / Realtime would prevent debs being made.
i think the reasoning is we expect any commit to 1) successfully
build a deb on all supported platforms and 2) pass runtests on all supported platforms before making the commit changes available
as a deb to any supported platform.
The criteria apply to both normal and 'scratch' debs. 'Scratch' debs disappear
after some time or space limitation occurs.
correct (slave lost seems to happen now and then -- no idea why)And as far as I can see this is nothing to do with my changes?
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
I have taken a job at another company so I no longer have access to that set of hardware. thanks for your help, though-
Please Log in or Create an account to join the conversation.
Andy-
I have taken a job at another company
I hope that isn't because you were fired for taking too long to get the Motenc working?
Please Log in or Create an account to join the conversation.