On 11/2/2012 5:18 AM, Michael Haberler wrote:
> I added this:
>
> Verify initrd has been created
> ------------------------------
>
> The lucid dpkg & friends tools are very outdated, and fail to create
> an initramfs after the above 'dpkg -i *.deb' step.
>
> Depending on your installation, this might have happened or not.
> See if this has happened:
>
> $ ls -l /boot/initrd.img-3.2.21-xenomai+
>
> If this file does not exist, create it manually as root like so
>
> # update-initramfs -c -k 3.2.21-xenomai+
and then, still as root, one must update grub to include the newly
generated initrd.img-3.2.21-xenomai+ file
# update-grub
>
> Now reboot, and Xenomai should come up. Verify this by:
>
> $ dmesg |grep Xenomai
> [ 3.250972] I-pipe: head domain Xenomai registered.
> [ 3.340753] Xenomai: hal/i386 started.
> [ 3.410749] Xenomai: scheduling class idle registered.
> [ 3.511046] Xenomai: scheduling class rt registered.
> [ 3.664165] Xenomai: real-time nucleus v2.6.1 (Light Years Away) loaded.
> [ 3.830540] Xenomai: debug mode enabled.
> [ 3.891351] Xenomai: starting native API services.
> [ 4.030965] Xenomai: starting POSIX services.
> [ 4.240531] Xenomai: starting RTDM services.
>
Yep. Xenomai now boots and lives on my P4 box.
>
>
> NB: when building the kernel yourself like described in the README, you might
> be better off using a more recent distro than lucid; I had very nasty
> problems building 3.x kernels on lucid and now build them on my server which
> is Debian wheezy.
Lucid Lynx aka 10.04LTS reaches its official end-of-life in just 6
months time. The only reason we're still using it is the delay in RTAI
development. I see no reason not to ratchet up the requirements for a
build system for non-RTAI systems using Xenomai or the PREEMPT_RT patch.
As a bonus, one gets access to much newer builds of interesting
applications in the repositories without lifting a finger.
> It might be the CPU family is set to aggressively, I have:
>
> $ grep CONFIG_X86_MINIMUM_CPU_FAMILY /boot/config-*
> /boot/config-2.6.32-122-rtai:CONFIG_X86_MINIMUM_CPU_FAMILY=4
> /boot/config-2.6.32-32-generic:CONFIG_X86_MINIMUM_CPU_FAMILY=4
> /boot/config-2.6.38-10-generic:CONFIG_X86_MINIMUM_CPU_FAMILY=5
> /boot/config-2.6.38.8-xenomai+:CONFIG_X86_MINIMUM_CPU_FAMILY=5
> /boot/config-3.2.21-xenomai+:CONFIG_X86_MINIMUM_CPU_FAMILY=5
> /boot/config-3.4.13-rt-preempt-rt22+:CONFIG_X86_MINIMUM_CPU_FAMILY=5
>
> Stepping back to P4 might help if it still fails to boot with the correct
> initrd image.
If these family numbers are the same as the Intel x86 generation
numbers, then a P4 is already covered since Pentiums were a
5th-generation design (hence the "Pent" from the Greek for "five"). In
any case, I booted 3.2.21-xenomai+ successfully without mucking with the
CPU family number.
As an aside, there are two broken symbolic links in
linux-image-3.2.21-xenomai+_0.1_i386.deb
./lib/modules/3.2.21-xenomai+/build ->
/media/kernels/work-linuxcnc-3.2.21-xenomai-x86
./lib/modules/3.2.21-xenomai+/source ->
/media/kernels/work-linuxcnc-3.2.21-xenomai-x86
They weren't a problem---dpkg simply flagged and deleted them---but they
shouldn't be there.
> - Michael
Thanks again, Michael, for your efforts.
Regards,
Kent
------------------------------------------------------------------------------
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
