Re: Location of Kernel modules
- From: Michael Schnell <mschnell_at_lumino_dot_de@xxxxxxxxxxx>
- Date: Wed, 24 May 2006 12:50:01 +0200
Thanks to all for help !
With doing "make install" three files were created:
# ls -l *16*
-rw-r--r-- 1 root root 807951 May 19 13:09 System.map-2.6.16-default
-rw-r--r-- 1 root root 1462219 May 24 11:08 initrd-2.6.16-default
-rw-r--r-- 1 root root 1497841 May 19 13:09 vmlinuz-2.6.16-default
"Make install" even created a new menu entry at the top of GRUBs menu.lst, pointing to /boot/vmlinuz-2.6.16-default and thus indeed creates a bootable system for the new system:
Now I get
# uname -r
2.6.16-default
"Make install" moreover modified the "vmlinux" symlink in /boot that originally pointed to vmlinuz-2.6.11.4-21.11-default to point to the newly created vmlinuz-2.6.16-default.
Thus the original menu entry "Suse" (that used "vmlinux") boots the same image as the newly created menu entry.
So I modified the original menu entry "Suse" to point to vmlinuz-2.6.11.4-21.11-default directly.
With that I get the same problem in the other direction, not this 2.6.11.4 Kernel tries to load the 2.6.16 modules and can't boot.
What can be done to have the option to boot different Kernel versions using GRUB ? IMHO, with 2.6 building a monolithic Kernel is not an option....
Thanks for any further hints,
-Michael
.
- Follow-Ups:
- Re: Location of Kernel modules
- From: Grant
- Re: Location of Kernel modules
- References:
- Location of Kernel modules
- From: Michael Schnell
- Re: Location of Kernel modules
- From: Michael Schnell
- Re: Location of Kernel modules
- From: Grant
- Location of Kernel modules
- Prev by Date: Re: Location of Kernel modules
- Next by Date: Re: Location of Kernel modules
- Previous by thread: Re: Location of Kernel modules
- Next by thread: Re: Location of Kernel modules
- Index(es):
Relevant Pages
|