Hi, all:
I'm using centos 6.2-x86_64, the built-in kernel version is 2.6.32-220.el6.x86_64.
Now I compiled kernel of version of linux-2.6.32-220.23.1.el6.x86_64, which get from kernel-2.6.32-220.23.1.el6.src.rpm.
I have put vmlinuz and initramfs into /boot directory, as follow:
[kdev@panda boot]$ ll /boot/vmlinuz-2.6.32-* ./initramfs-2.6.32-* -rwxr-xr-x. 1 root root 3938288 12月 7 2011 /boot/vmlinuz-2.6.32-220.el6.x86_64 -rw-r--r--. 1 root root 3952816 12月 8 19:23 /boot/vmlinuz-2.6.32-kdev-v1 -rw-r--r--. 1 root root 15888573 5月 26 2012 ./initramfs-2.6.32-220.el6.x86_64.img -rw-r--r--. 1 root root 15824301 12月 8 20:17 ./initramfs-2.6.32-kdev-v1
and modified grub.conf like this: #boot=/dev/sdb default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS62 (2.6.32-220.el6.x86_64) root (hd0,0) kernel /vmlinuz-2.6.32-220.el6.x86_64 ro root=UUID=f09cc6eb-99fa-4c90-a1a5-ad15277e8331 rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD quiet SYSFONT=latarcyrheb-sun16 rhgb crashkernel=auto KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM initrd /initramfs-2.6.32-220.el6.x86_64.img
title CentOS62 (2.6.32-kdev-v1) root (hd0,0) kernel /vmlinuz-2.6.32-kdev-v1 ro root=UUID=f09cc6eb-99fa-4c90-a1a5-ad15277e8331 rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD quiet SYSFONT=latarcyrheb-sun16 rhgb crashkernel=auto KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM initrd /initramfs-2.6.32-kdev-v1.img
what i do is just copy the original section which beginning with title, and then modified it with different version_string. But at last, after selecting the kdev-v1 item from grub's menu, i got a black screen with a cursor blinking in the top-left, and paused there.
If i select the original kernel, namely 2.6.32-220.el6.x86_64, all thing is correct. Is the GRUB gets wrong?? My machine is : motherboard: MSI G41M-P26 cpu: Intel Celeron(R) CPU E3400
Thanks ~~!!
At 2012-12-09 00:09:24,"Kai Schaetzl" maillists@conactive.com wrote:
Yihect wrote on Sat, 8 Dec 2012 21:31:54 +0800 (CST):
initrd /initramfs-2.6.32-kdev-v1.img
compare!
Oh, yeah, that's my mistake, a small but deadly one. Thanks~~ Kai!
By the way, in default, the initramfs image made using mkinitrd cmd is too big to put into my /boot partition. I have to changed /etc/dracut.conf file to build initramfs only to boot my current hardware.
And in other hand, I found if I use the big one in my kvm vm, it can't work again, just show me a black screen with one blinding cursor in top-left corner. But if use the size-reduced one, it works well. So my question is why, why the big initramfs can't work. Any suggestions??
Kai