smi_module compilation problem

Hello,

I am trying to disable the smi on my computer and I got an error when I follow the wiki SMIfix page.

In fact, I have chosen to use the little makefile to compile smi_module.ko but it cannot find the rtai_wrapper.h file which is situated in the include diretory. I am not friendly with "make modules" but even if i add the exact path on INCLUDE variable, it doesn't work.

This is the exact message error :

antoine@pc-desktop:/usr/src/modules/rtai-3.8.1/base/arch/i386/calibration$ sudo make all
[sudo] password for antoine:
make -C /lib/modules/2.6.32-122-rtai/build -I/usr/include/asm/mach-default/ SUBDIRS=/usr/src/modules/rtai-3.8.1/base/arch/i386/calibration modules
make[1]: entrant dans le répertoire « /usr/src/linux-headers-2.6.32-122-rtai »
CC [M] /usr/src/modules/rtai-3.8.1/base/arch/i386/calibration/smi-module.o
/usr/src/modules/rtai-3.8.1/base/arch/i386/calibration/smi-module.c:32:27: error: rtai_wrappers.h: Aucun fichier ou dossier de ce type
/usr/src/modules/rtai-3.8.1/base/arch/i386/calibration/smi-module.c:142: error: expected ‘)’ before ‘ulong’
make[2]: *** [/usr/src/modules/rtai-3.8.1/base/arch/i386/calibration/smi-module.o] Erreur 1
make[1]: *** [_module_/usr/src/modules/rtai-3.8.1/base/arch/i386/calibration] Erreur 2
make[1]: quittant le répertoire « /usr/src/linux-headers-2.6.32-122-rtai »
make: *** [all] Erreur 2

Could you help me on this point ?

Thank you !

Anyone ?

Ok, so if I want to compile entirely rtai with SMI disabled. Which version of it I need to download ? I am using EMC from the liveCD install ( v10.04 )

I am very surprised because when I get the last version of rtai (3.8 ), I don't find the HAL patch for my kernel ( 2.6.32 ). Do you know which combination ( linux - rtai version ) I need to use ?

Thank you !

If I have this message in my dmesg, does it mean that SMI is already disabled ?

[ 1312.575077] SMI configuration has been reset, saved mask used = 1.
[ 1319.369192] RTAI: Intel chipset found, enabling SMI workaround.
[ 1319.369209] SMI configuration has been cleared, mask used = 1 (saved mask setting 1).

Some time later, I have :

[ 1321.354697] RTAPI: ERROR: Unexpected realtime delay on task 1
[ 1321.354703] This Message will only display once per session.
[ 1321.354705] Run the Latency Test and resolve before continuing.
[ 1321.355357] 1580: ERROR: Unexpected realtime delay: check dmesg for details.
[ 1321.355368]
[ 1321.355370] In recent history there were
[ 1321.355373] 2997675, 3023565, 2974980, 3021435, and 3000683
[ 1321.355376] elapsed clocks between calls to the motion controller.
[ 1321.355398] This time, there were 3603007 which is so anomalously
[ 1321.355403] large that it probably signifies a problem with your
[ 1321.355407] realtime configuration. For the rest of this run of
[ 1321.355411] EMC, this message will be suppressed.

Does it mean that i have a big latency problem ?

Okay,

Does anyone could explain how to disable SMI on the last EMC liveCD version ( Lynx ).

With the Makefile given on the wiki, I got the error described below.
When I try to compile all the rtai sources, I got a compatibility problem when I apply the HAL patch on the kernel.

I have also tried a little software called smictrl ( www.rts.uni-hannover.de/rtaddon/ ) which I succeeded to compile. But I don't know which value I need to apply to the SMI register and even if it is enough to reduce the periodic latency.

Plz, help me.

So finally, if someone is interested in this topic. I have found the solution to my problem :

In fact rtai_smi.ko is already compiled in Ubuntu RTAI 10.04 and is situated in :

/usr/realtime-2.6.32-122-rtai/modules/rtai_smi.ko

So, you just have to execute : sudo insmod /usr/realtime-2.6.32-122-rtai/modules/rtai_smi.ko

In my case, it solved latency problem when no graphical task is running
Before : Max Jitter 1ms & 25us : about 100000us
After : Max Jitter 1ms : 5661 | 25us : 9813

When I run glxgear I come back to my old shitty results....Help me...

Have you looked here...
wiki.linuxcnc.org/emcinfo.pl?TroubleShooting

If you have not already you may want to experiment with a different video driver.

Rick G