[Bdi4emc-help] quickstep

Mon Sep 22 22:20:38 CEST 2008

On Monday 22 September 2008, David Szakovits wrote:
>    hi,
>    thanks, the files seemed to be under /usr/realtime....  so i copied
>    them under /lib as you suggested.
>    this helped but there appears to be a problem with the parport address
>    now.   maybe you know how to fix this?  also tried to answer your
>    questions

>    i had trouble compiling in the drivers/vital directory, but i felt i
>    could safely comment this out and so i did.
> Can you remember what errors occurred with the Vital driver ?
>
>    it starts out not finding "pci/pci.h" and then a bunch of undefined
>    macros and variables.

OK - Sounds like an include path needs tweaking for 2.6.24, but to be honest, 
all of the PCI drivers need overhauling in order to work with future kernels.

> To resolve the deprecated char warnings requires a couple of hours of
> tiresome, repetative search/replace - Maybe I'll make a start this evening.
>
>    do you just declare these "char **"  as "const char** " or is there a
>    better equivalent declaration that doesn't require const?

Yup, a case of going though the code adding const in assorted places - Nearly 
done here and will update CVS shortly.

> If you still get errors regarding the above symbols, could you
> check /boot/config-2.6.24-16-rtai and tell me if CONFIG_MODVERSION=y.
>
>    actually it is the plural CONFIG_MOVERSIONS=y and it is set equal to

Well.... CONFIG_MODVERSIONS - Not that it really matters too much as you found 
it ;-)

<snip>
> FATAL: Error inserting quickstep
> (/lib/modules/2.6.24-16-rtai/extra/quickstep.k o): Operation not permitted
> can't install quickstep
<snip>
> [363100.527781] emcmot: No parport found at 0x378
> [363100.527795] can't initialize motion hardware
<snip>
>    i notice this has something to do with the parport address.   i
>    checked in /proc/ioports and it is not there either.   i suspect this
>    is a problem to do with the use of the emc2 ubuntu as a starting
>    point.  i know nothing at all about this but i have previously noted
>    that the parport does not show up in /proc/ioports on emc2 machines.

Can you do a `lsmod`, remove any h/a modules by the name of probe_parport if 
present and then follow it with `modprobe parport && modprobe parport_pc`. 
Check the output from `lsmod` to confirm parport & parport_pc are loaded, 
then /proc/ioports *should* report addresses correctly.

If the above steps succeed and EMC runs, perhaps send a bug report for broken 
printer support to who ever is reponsible for that custom distro is in order.

>    i suppose i could start over with a different installation CD.   i
>    thought i could save some work installing rtai but maybe not.   i ran
>    into this sort of thing before when i wanted to run emc1 and emc2 on
>    the same OS.  i always gave up.

You want to see the hoops I have to jump through - But then I don't limit 
myself to a single distro, kernel, or architecture...

Regards, Paul.