Alex recently wrote, in response to discussion about a system with more than 1G of ram not loading RTAI >>> >> >>> >> > This was a known bug on the older system, like last year. I thought >> > they got that fixed! >> > Not so, or is Mario using an old version of Ubuntu? >> > > We "fixed" that on 6.06 dapper by not allowing the system to see more than > 1G of ram. > By the time haryd came up, the rtai people were aware of a solution, yet it > wasn't part of rtai-3.6 which I used initially for the LiveCD. They fixed > the issue for 3.6.1 which is now part of the linuxcnc repository. So if you > have your updates installed, then it's definately fixed. > I can't remember if I rebuilt the LiveCD to include rtai-3.6.1, but probably > I didn't. > > Regards, > Alex > I ran into this issue with the 8.04 LiveCD back in May and had a brief email exchange about it with Jeff Epler (because I wanted to speak of other things with him).
Armed with Jeff's response about the memory constraint that was imposed in the 6.06 LiveCD and the rtai fix y'all had been anticipating would be released in time for the 8.04-LiveCD build, I went looking for an easy way to determine what version of RTAI was actually running on my machine. To save others the time it took me to do this (of course I may just be the slow kid in the class and the rest of you already know the answer), there is a utility called rtai-config that can provide the answer when invoked with the --version option. Unfortunately, the location of this utility seems to be dependent on the kernel version because of the way the rtai extensions are built. On my machine, it's in the /usr/realtime-2.6.24-16-rtai/bin directory and currently it returns the answer 3.6.1, confirming Alex's comment that "...if you have your updates installed, then it's definitely fixed." I'll see if I can find an appropriate place to add this tidbit to the wiki. Regards, Kent PS - mentioning the wiki reminds me to take a moment to rant that we all should be explicitly date/time stamping our contributions and specifying their effectivity (e.g., the software versions to which they apply) so subsequent readers have a clue whether the information they are looking at is relevant to their problem. As EMC/EMC2 and the wiki both evolve over time it gets harder and harder to know what's hot and what's merely historically interesting. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
