<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, May 23, 2013 at 3:38 PM, Giridhara RP (grp) <span dir="ltr"><<a href="mailto:grp@cisco.com" target="_blank">grp@cisco.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I did not see any file (vmlinuz-<version>.x86_64) under /boot. I was only looking at bzImage found under <arch>/boot/ . Am I missing something?<br>
</blockquote><div><br></div><div>Can you look at the 'running' kernel's config to see if it's indeed the one you compiled (provided you enabled support for it during building - see /proc/config.gz)? Eg something like 'CONFIG_X86_64=y' is set.<br>
<br>Is the machine you're building on 64-bit or 32-bit? I hope you used a 64bit compiler for building your kernel.</div><div><br></div><div>HTH,<br></div><div>-mandeep<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
<br>
[root@grpRHEL2 linux-2.6.32.60]# pwd<br>
/root/lin_2/linux-2.6.32.60<br>
[root@grpRHEL2 linux-2.6.32.60]# find . | grep -i vmlinuz<br>
[root@grpRHEL2 linux-2.6.32.60]#<br>
[root@grpRHEL2 linux-2.6.32.60]#<br>
<div class="im">[root@grpRHEL2 linux-2.6.32.60]# file vmlinux<br>
</div><div class="im">vmlinux: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, not stripped<br>
<br>
</div>[root@grpRHEL2 linux-2.6.32.60]# file vmlinux.o<br>
<div class="im">vmlinux.o: ELF 64-bit LSB relocatable, x86-64, version 1 (SYSV), not stripped<br>
<br>
</div>[root@grpRHEL2 linux-2.6.32.60]# file arch/x86/boot/bzImage<br>
arch/x86/boot/bzImage: Linux kernel x86 boot executable bzImage, version 2.6.32.60 (root@grpRHEL2) #1 SM, RO-rootFS, swap_dev 0x3, Normal VGA<br>
[root@grpRHEL2 linux-2.6.32.60]# file arch/x86_64/boot/bzImage<br>
arch/x86_64/boot/bzImage: symbolic link to `../../x86/boot/bzImage'<br>
<div class="im"><br>
-----Original Message-----<br>
From: amit mehta [mailto:<a href="mailto:gmate.amit@gmail.com">gmate.amit@gmail.com</a>]<br>
</div><div class="im">Sent: Thursday, May 23, 2013 3:31 PM<br>
To: Giridhara RP (grp)<br>
Cc: <a href="mailto:kernelnewbies@kernelnewbies.org">kernelnewbies@kernelnewbies.org</a><br>
Subject: Re: Kernel 64bit<br>
<br>
</div><div class=""><div class="h5">On Thu, May 23, 2013 at 2:45 PM, Giridhara RP (grp) <<a href="mailto:grp@cisco.com">grp@cisco.com</a>> wrote:<br>
> Looks like I copied wrong output in my previous email. Here is the output. Also, what should I do with 'grub'?<br>
><br>
> 5. After boot 'uname -a' , shows this.<br>
> Linux 2.6.32-60 #1 SMP Mon Mar 25 16:20:30 IST 2013 i686 GNU/Linux<br>
<br>
Generally, After building a new kernel, I issue 'update-grub' command on my ubuntu box to add proper entries for the newly built kernel in the grub configuration file, but I think 'make install' will take care of this as well. However, as you've confirmed that you've successfully booted from the newly built kernel, which is still being reported as a 32 bit kernel, therefore we can safely reject the case of incorrect and or missing grub entry.<br>
<br>
Do you see compressed x86_64 bit kernel image(vmlinuz-<version>.x86_64) under /boot ?<br>
_______________________________________________<br>
Kernelnewbies mailing list<br>
<a href="mailto:Kernelnewbies@kernelnewbies.org">Kernelnewbies@kernelnewbies.org</a><br>
<a href="http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" target="_blank">http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies</a><br>
</div></div></blockquote></div><br></div></div>