Help with SMI on 2.4.7

Hi all, I've trying to get the SMI disabled but no luck at all. I've followed the steps in the wiki but I always get errors saying "Intel chipset not found" as well as "rtai_smi.ko not found". the module IS located at /usr/realtime-2.6.32-122-rtai/modules/rtai_smi.ko I've updated BOTH items in the rtapi.conf file as per the instructions. here's what I get. on latency tests the intel MB with a 3.4 GHz cpu do great times untill the time hits 32 seconds then it jumps from about Max Jitter (ns) 5000 to 500,000 exactly at 32 seconds every time

Here's the directory listing

/usr/realtime-2.6.32-122-rtai/modules$ ls
emc2 rtai_hal.ko rtai_mup.ko rtai_tasklets.ko
latency_rt.ko rtai_ksched.ko rtai_rtdm.ko rtai_tbx.ko
Module.symvers rtai_lxrt.ko rtai_sched.ko rtai_up.ko
preempt_rt.ko rtai_math.ko rtai_sem.ko rtai_usi.ko
rtai_bits.ko rtai_mbx.ko rtai_serial.ko rtai_wd.ko
rtai_calibrate.ko rtai_mq.ko rtai_smi.ko switches_rt.ko
rtai_fifos.ko rtai_msg.ko rtai_smp.ko


desktop:/usr/realtime-2.6.32-122-rtai/modules$ sudo insmod rtai_smi.ko
insmod: error inserting 'rtai_smi.ko': -1 No such device

I'm stumped, could this module be compiled for a different kernel? setsmi doesnt work either.
Thanks in advance for any help, I really want to get this figured out so I can move forward on the rest of the conversion to CNC for my mill.

Have you looked here...

www.linuxcnc.org/index.php/english/compo...ew&catid=18&id=16238

Rick G

Hi

I tried to post the same link as Rick this morning, but lost my connection.

The crux of the previous thread is that the smi fix only seems to work at all for particular chipset(s) even if you have an Intel MB.
The errors you got where what I got trying to load it with a machine with a new Intel MB.

If you can determine what chipsets you have on your MB ( I suspect from the CPU speed it is a newish one) I'll try to do some digging.
82801DB was the chip which caused SMI problems and responded to the fix, but I am not sure which other, if any, chips are targeted by the module.

regards

Thanks for the reply's. Yes I did read the posts mentioned above. I've been working on it for 3 days. I wanted to try everything I could prior to posting for help. Here's the numbers from lspci.
Intel 82Q963/Q965
Intel 82801H
The PC is a lenovo M55p 8808-VJN with a ATI Radeon 9200 in the PCI slot and onboard disabled.

Thanks again
Craig

Hi

OK checked the code of smi-module.c from the rtai-source package and this is the chipset table

Your specific chipset 82801H is not listed, thus presumably why the module will not load.

The module might not work with it anyway, don't know what changes were made to the chip between EB and H.

If you do a lspci -vv and post the print out as a txt file in an attachment, I will try to edit the module code to accept your chipset try to compile a new module and we can see where we get from there.

regards

Thank you so much, I will post lspci -vv as soon as my ISP gets the fiberoptic cable repaired that got cut with a excavator. I'm using my phone to post until its repaired at approx 3:30 pm central time.

Ok they got it fixed pretty quick, here's what lspci -vv shows.

root_lspci.txt is attached.

Thanks again

Sorry, I messed the last post up. here's the correct file.

root_lspci.txt

Hi,

Will not be able to try this until tomorrow, will let you know when I have.

regards

Hi

Your lspci print shows that the chip comes under the ICH8 umbrella

Intel Corporation 82801H (ICH8 Family)

There are 7 other ICH8 sub types defined in pci_ids.h now, so I have included them into the table in smi-module.c

This compiles fine with the magma sources I already have installed and I have attached the resulting rtai-smi.ko module
(remove the .txt from the download and replace with .ko the forum only accepts certain types of upload)

Disclaimer
This module is not warranted safe or of use for anything.

I cannot test it, because I do not have a suitable MB, other than it appears to have been successfully compiled as a module for the 2.6.32-122 kernel.

Best case scenario is that it will recognise your chipset and work.

Neutral outcome, it will not load or it will load and will not recognise your chipset.

Worst case scenario, it will load, but the registers it alters are different in your machine to the ICH8_4 chipset it apparently worked with previously and it will cause damage or render it a 'brick'.

The choice as to whether to try it is yours alone.

regards