Yes and I haven't been able to get the mailer to work like it should so that my name shows.
Boy am I in real trouble now. I down loaded the binary. Thinking that if I made any goofs I went to /usr/realtime-2.6.15-magma/modules and changed permissions on rtai_smi.ko and renamed it rtai_smi1.ko so if the one I down loaded and intended to replace the first file with didn't work I would have the original file intact. However, in the process all the files in /usr/realtime-2.6.15-magma/modules got wiped out and I couldn't get Ubuntu to shut down or reboot! So I installed another drive reloaded EMC2 on it from the CD and thought that I could move my /usr/realtime-2.6.15-magma/modules over from the newly installed ubuntu to the original hard drive. However, Ubuntu doesn't even recognize my 2nd hard drive as though it isn't present. At least I still have my ini and hal files saved on the usb memory stick that was in place. So eventually I'll be able to recover that work. However now I must figure out how to get the new rtai_smi.ko over to where it's got to go without wiping out the whole directory. Would renaming the rtai.smi.ko file be the cause of losing the system? If so how can I safely move the replacement binary file in to the module directory? Gene Heskett wrote: > On Saturday 10 March 2007, Jack Ensor wrote: > > And your mailer is broken Jack, no way to tell who wrote what here. > > >> It looks like I have a problem with smi (system maintenance interrupts) >> increasing the latency and causing the realtime errors. Referencing EMC >> Documentation Wiki - FixingDapperSMIIssues they give these instructions: >> >> ******** >> 3. Changing smi-module.c >> >> First you need to get the sources for the dapper version of RTAI: >> >> to get the sources for the dapper version you need to >> apt-get source rtai-3.3 >> >> Find the smi-module.c inside rtai/base/arch/i386/calibration, and change >> the following line: >> #define CONFIG_RTAI_HW_SMI_ALL 1 >> >> Once that is changed, you can compile the module and replace the version >> already installed. >> >> 4. Compiling the new module >> >> Unless you want to use the existing build process (which means you need >> to put the rtai sources in /usr/src/modules/rtai-3.3/ and use make-kpkg >> to build the modules) use the following Makefile: >> >> Makefile >> >> UNAME := $(shell uname -r) >> KERNEL26 := 2.6 >> KERNELVERSION := $(findstring $(KERNEL26),$(UNAME)) >> >> obj-m := rtai_smi.o >> rtai_smi-objs := smi-module.o >> >> INCLUDE := -I/usr/include/asm/mach-default/ >> KDIR := /lib/modules/$(shell uname -r)/build >> PWD := $(shell pwd) >> >> all:: >> $(MAKE) -C $(KDIR) $(INCLUDE) SUBDIRS=$(PWD) modules >> >> Simply run make, and the new module should be built. (Alternative: grab >> the binary from [[here]]). >> > There is no link for^^^^^ > > >> 5. Installing the new module >> >> Installing means simply copying the new binary module over the old >> version, located at: /usr/realtime-2.6.15-magma/modules/rtai_smi.ko >> *********** >> >> My question is do they simply mean down load the binary file and then >> copy it over /usr/realtime-2.6.15-magma/modules/rtai_smi.ko ? >> >> Do I still have to do step 4? >> > > Probably not, but if you download the binary, you may have to set its > perms to match the one you are over-writing, do it before the overwrite. > > >> Jack Ensor >> > > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
