From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Tue, 20 Feb 2007 08:23:02 +0100 From: "Eric Noulard" Subject: Re: [Xenomai-help] patching continues In-Reply-To: <45D9F759.7020006@domain.hid> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <45D9F759.7020006@domain.hid> List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: rolandtollenaar@domain.hid Cc: Xenomai-help@domain.hid 2007/2/19, Roland Tollenaar : > Hi all, > > I have gone through the kernel patching steps and all seems to go well. > Except... > > 1 > I don't seem to get an initrd from the make process and my system does > not have a mkinitrd on it. Is this normal? I get the vmlinux though > which I am very happy about :) I don't know how you did compile your kernel but if you "only" did: make YYYYconfig make make modules_install you won't get initrd from this. you need to do it yourself for example with /sbin/mkinitrd -v -f /what_ever_dir_is/boot/initrd-2.6.16-pipe.img 2.6.16-pipe which will create (OR REPLACE if it exists) your initrd file for kernel version 2.6.16-pipe Note that you still to update your lilo.conf / grub.conf file for adding your freshly compiled kernel. > > 2 > Then the make modules install generates the lib/modules/2.6.16-pipe > directory but it has only a very few modules. Not nearly as many as the > current kernel seems to have. It really depends on what you chose during make YYYYconfig step. you may try to diff the .config obtained for your currently running kernel with the one used for xenomai-patched kernel. > > Might anyone be able to give some hints as to what I could be doing wrong? What is wrong did you manage to boot? I don't if my answer are appropriate since I don't know exactly what step you did for compiling your kernel. May be you can tell us what you did exactly (command lines) and what you expected that does not work (missing files, kernel does not boot, no new kernel boot menu...) -- Erk