On Tue, Jun 28, 2011 at 2:07 PM, Ponkumaran Annadurai <aspkumaran@gmail.com> wrote:
On Tue, Jun 28, 2011 at 1:13 PM, Daniel Baluta <daniel.baluta@gmail.com> wrote:
Have you tried to setup some sort of cross-compilation environment? Could you check CROSS_COMPILE env variable?
Yes, I have given yes for that option during configuration
OK, then that's your problem. CROSS_COMPILE is a string pointing to your cross compiler prefix.
thanks, Daniel.
Yes, It worked. Thank you sir. But I couldn't understand the reason. Can you explain this to me?
Please keep kernelnewbies to CC:, so that other can read about this problem if they hit it. The reason for which it didn't work is that you haven't set a valid cross-compiler prefix in CROSS_COMPILE When you set a cross-compiler prefix, the value stored in CROSS_COMPILE is concatenated with the name of each tool used to compile your kernel. For example, objdump will be used as ${CROSS_COMPILE}objdump. You set CROSS_COMPILE=Y, and the tool to be used is now named Yobjdump, which obviously doesn't exist. Valid values for CROSS_COMPILE look like this: CROSS_COMPILE= mips64-octeon-linux-gnu-. Hope that things are now more clear. thanks, Daniel
On Tue, Jun 28, 2011 at 4:59 PM, Daniel Baluta <daniel.baluta@gmail.com>wrote:
On Tue, Jun 28, 2011 at 2:07 PM, Ponkumaran Annadurai <aspkumaran@gmail.com> wrote:
On Tue, Jun 28, 2011 at 1:13 PM, Daniel Baluta <daniel.baluta@gmail.com> wrote:
Have you tried to setup some sort of cross-compilation environment? Could you check CROSS_COMPILE env variable?
Yes, I have given yes for that option during configuration
OK, then that's your problem. CROSS_COMPILE is a string pointing to your cross compiler prefix.
thanks, Daniel.
Yes, It worked. Thank you sir. But I couldn't understand the reason. Can
you
explain this to me?
Please keep kernelnewbies to CC:, so that other can read about this problem if they hit it.
The reason for which it didn't work is that you haven't set a valid cross-compiler prefix in CROSS_COMPILE
When you set a cross-compiler prefix, the value stored in CROSS_COMPILE is concatenated with the name of each tool used to compile your kernel.
For example, objdump will be used as ${CROSS_COMPILE}objdump. You set CROSS_COMPILE=Y, and the tool to be used is now named Yobjdump, which obviously doesn't exist.
Valid values for CROSS_COMPILE look like this: CROSS_COMPILE= mips64-octeon-linux-gnu-.
Hope that things are now more clear.
thanks, Daniel
Yes, they are clear. Thank you sir. -- regards, kumaran
I got struck in making initrd file, I got the following error root@rocker:/boot# mkinitramfs -o initrd.img-2.6.39.1 2.6.39.1Y W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module r8169 can you suggest me the proper ways to compile a kernel? -- thanks, kumaran
On Tue, Jun 28, 2011 at 8:39 PM, Ponkumaran Annadurai <aspkumaran@gmail.com> wrote:
I got struck in making initrd file, I got the following error
root@rocker:/boot# mkinitramfs -o initrd.img-2.6.39.1 2.6.39.1Y
2.6.39.1Y? - shouldn't it be 2.6.39.1. These days I cooked a script to compile the kernel. Perhaps it helps. KERNEL_DIR=/home/daniel/src/linux KERNEL_VER=3.0.0-rc4 cd $KERNEL_DIR #build kernel and images make bzImage make modules make modules_install #copy newly created image to /boot cp $KERNEL_DIR/arch/x86/boot/bzImage /boot/vmlinuz-$KERNEL_VER cp $KERNEL_DIR/.config /boot/config-$KERNEL_VER cp $KERNEL_DIR/System.map /boot/System.map-$KERNEL_VER #setup initrd image cd /boot mkinitramfs -o initrd.img-$KERNEL_VER $KERNEL_VER thanks, Daniel.
On Wed, Jun 29, 2011 at 01:08, Daniel Baluta <daniel.baluta@gmail.com> wrote:
On Tue, Jun 28, 2011 at 8:39 PM, Ponkumaran Annadurai <aspkumaran@gmail.com> wrote:
I got struck in making initrd file, I got the following error
root@rocker:/boot# mkinitramfs -o initrd.img-2.6.39.1 2.6.39.1Y
2.6.39.1Y? - shouldn't it be 2.6.39.1.
Daniel, I guess Ponkumaran did something (wrong) with extra version...what do you think? -- regards, Mulyadi Santosa Freelance Linux trainer and consultant blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com
On Wed, Jun 29, 2011 at 9:28 AM, Mulyadi Santosa <mulyadi.santosa@gmail.com> wrote:
On Wed, Jun 29, 2011 at 01:08, Daniel Baluta <daniel.baluta@gmail.com> wrote:
On Tue, Jun 28, 2011 at 8:39 PM, Ponkumaran Annadurai <aspkumaran@gmail.com> wrote:
I got struck in making initrd file, I got the following error
root@rocker:/boot# mkinitramfs -o initrd.img-2.6.39.1 2.6.39.1Y
2.6.39.1Y? - shouldn't it be 2.6.39.1.
Daniel, I guess Ponkumaran did something (wrong) with extra version...what do you think?
Mulyadi, I don't see how he could have changed EXTRA_VERSION from Makefile. Ponkumaran, could you try running: # mkinitramfs -o initrd.img-2.6.39.1 2.6.39.1 thanks, Daniel.
On Wed, Jun 29, 2011 at 12:42 PM, Daniel Baluta <daniel.baluta@gmail.com>wrote:
I got struck in making initrd file, I got the following error
root@rocker:/boot# mkinitramfs -o initrd.img-2.6.39.1 2.6.39.1Y
2.6.39.1Y? - shouldn't it be 2.6.39.1.
Daniel, I guess Ponkumaran did something (wrong) with extra version...what do you think?
Mulyadi, I don't see how he could have changed EXTRA_VERSION from Makefile.
No, I didn do anything in the Makefile
Ponkumaran, could you try running: # mkinitramfs -o initrd.img-2.6.39.1 2.6.39.1
I tried this one first but I was prompted that the folder 2.6.39.1 is not found in /lib/modules. Then I found a folder named 2.6.39.1Y thats why I used this name. But now I guess that this Y is given by me during configuration in the place for local version option. Is that any problem with that?
thanks, Daniel.
-- thanks, kumaran
On Wed, Jun 29, 2011 at 4:37 PM, Ponkumaran Annadurai <aspkumaran@gmail.com> wrote:
On Wed, Jun 29, 2011 at 12:42 PM, Daniel Baluta <daniel.baluta@gmail.com> wrote:
I got struck in making initrd file, I got the following error
root@rocker:/boot# mkinitramfs -o initrd.img-2.6.39.1 2.6.39.1Y
2.6.39.1Y? - shouldn't it be 2.6.39.1.
Daniel, I guess Ponkumaran did something (wrong) with extra version...what do you think?
Mulyadi, I don't see how he could have changed EXTRA_VERSION from Makefile.
No, I didn do anything in the Makefile
Ponkumaran, could you try running: # mkinitramfs -o initrd.img-2.6.39.1 2.6.39.1
I tried this one first but I was prompted that the folder 2.6.39.1 is not found in /lib/modules. Then I found a folder named 2.6.39.1Y thats why I used this name. But now I guess that this Y is given by me during configuration in the place for local version option. Is that any problem with that?
I don't know :). I would recommend you to start a fresh install. It's obvious that you've did something wrong in the first time. Compiling the kernel should be fairly easy. thanks, Daniel.
On Tue, Jun 28, 2011 at 18:29, Daniel Baluta <daniel.baluta@gmail.com> wrote:
Please keep kernelnewbies to CC:, so that other can read about this problem if they hit it.
The reason for which it didn't work is that you haven't set a valid cross-compiler prefix in CROSS_COMPILE
When you set a cross-compiler prefix, the value stored in CROSS_COMPILE is concatenated with the name of each tool used to compile your kernel.
For example, objdump will be used as ${CROSS_COMPILE}objdump. You set CROSS_COMPILE=Y, and the tool to be used is now named Yobjdump, which obviously doesn't exist.
Great job man!!! Your explanation also clearly explain to me how this option works. Thanks! -- regards, Mulyadi Santosa Freelance Linux trainer and consultant blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com
participants (3)
-
Daniel Baluta -
Mulyadi Santosa -
Ponkumaran Annadurai