Hi all, I saw the discussion on chat two nights ago about building an SMP kernel with rtai. I tried to give it a shot to use with the Intel Atom 330, and got to an error which I do not know how to resolve. I found these pages as references:
http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?Debian_Lenny_Compile_RTAI http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?RtaiSteps http://wiki.linuxcnc.org/cgi-bin/emcinfo.pl?BuildingUbuntuPackages And as I ran into problems, cobbled what I could from each of them. Currently I am running from Ubuntu 8.04 with the 2.6.26-generic kernel (no rtai at this point). I was basically able to get all of the steps for building on Debian Lenny to work down through 'make menuconfig' except that the CFLAGS_KERNEL value was not recognized. I used the source for kernel version 2.6.22 because it was the latest version having a patch file from rtai. I wasn't sure whether 2.6.24 needed a patch file or not, so just to get the procedure down I decided to go with the latest version that did have a patch. I also chose the "core2" as the processor family in make menuconfig. The script make-kpkg did not exist on my system, so I went to the rtai-steps documentation and was able to do a "make all", "make modules", "make bzImage" and "make modules install" (see below). mkinitrd was not found but I saw that it has been replaced with mkinitramfs, which did appear to run properly. I then copied the necessary files to /boot and edited /boot/grub/menu.lst to add a selection for the new kernel. The kernel starts to boot but first gives a warning "/lib/modules/2.6.22 no such file or directory", followed by a fatal error, /lib/modules/2.6.22/modules.dep.temp could not open for writing. I went and checked for /lib/modules/2.6.22 and found that it did in fact not exist. After rechecking the documentation I finally realized that there was a problem in the print out I was working from, in that the "_" was not printed for "make modules_install", but "make modules install" ran without error. I ran the correct command and sure enough it did create what looks like a valid /lib/modules/2.6.22 folder with contents similar to those for the other installed kernels. I rebooted, and selected the new kernel, but am still getting that same error. The file permissions look the same, etc. Would any kernel guru out there happen to know why it might not be able to find or write to the /lib/modules/2.6.22 folder or files in those folders? There is no file modules.dep.temp, but there is modules.dep, which is consistent with the files associated with the other kernels. Regards, Eric ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
