kernel boot confusion
Hello, How is this possible? Okay, I copied /usr/src/linux-2.6.11.4-21.7 to /usr/src/linux-2.6.11.4-21.7.custom, ran "make menuconfig" (made my changes here so could use the new ATTO SCSI card) from the *custom directory, saved it, ran "make", then " make modules_install", created all the images and soft links under boot (below), edited lilo.conf and ran "lilo", rebooted, lilo says it is going to boot the new kernel, but instead of seeing my new kernel being loaded it says the default kernel is loaded; uname -r 2.6.11.4-21.7-default. However, that can't be possible because I now have access to my the tape drive attached to the ATTO SCSI card which I never had access to before when booting the other kernels. I have included relevant info below. Any ideas on what happened? I was hoping the kernel would be, 2.6.11.4-21.7-bigsmp.custom. Many thanks in advance. /etc/lilo.conf default = Linux-atto timeout = 80 message = /boot/message lba32 read-only prompt boot = /dev/hda change-rules reset disk = /dev/hda bios = 0x80 disk = /dev/sda bios = 0x81 image =/boot/vmlinuzatto ###Don't change this comment - YaST2 identifier: Original name: linuxatto### label = Linux-atto initrd = /boot/initrdatto root = /dev/hda2 append = "selinux=0 splash=silent " vga=0x317 image = /boot/vmlinuz ###Don't change this comment - YaST2 identifier: Original name: linux### label = Linux initrd = /boot/initrd root = /dev/hda2 append = "selinux=0 splash=silent " vga = 0x317 <snip> # ls -l /boot total 12237 drwxr-xr-x 4 root root 1024 Jul 11 15:48 . drwxr-xr-x 19 root root 4096 Jul 11 08:50 .. -rw-r--r-- 1 root root 120 Jun 2 13:47 README.vmlinux-2.6.11.4-21.7-bigsmp.gz lrwxrwxrwx 1 root root 44 Jul 8 17:42 System.map -> /boot/System.map-2.6.11.4-21.7-bigsmp.custom -rw-r--r-- 1 root root 741878 Jul 8 17:42 System.map-2.6.11.4-21.7-bigsmp.custom -rw-r--r-- 1 root root 729178 Jun 2 13:29 System.map-2.6.11.4-21.7-bigsmp.old -rw-r--r-- 1 root root 487561 Jun 2 13:03 System.map-2.6.11.4-21.7-um -rw-r--r-- 1 root root 512 Feb 4 19:19 backup_mbr lrwxrwxrwx 1 root root 1 Jul 7 07:26 boot -> . -rw-r--r-- 1 root root 512 Feb 4 19:19 boot.0300 -rw-r--r-- 1 root root 59669 Jun 2 13:47 config-2.6.11.4-21.7-bigsmp -rw-r--r-- 1 root root 18399 Jun 2 13:09 config-2.6.11.4-21.7-um drwxr-xr-x 2 root root 1024 Jul 7 07:26 grub lrwxrwxrwx 1 root root 27 Jul 7 15:46 initrd -> initrd-2.6.11.4-21.7-bigsmp -rw-r--r-- 1 root root 1587237 Jul 7 15:46 initrd-2.6.11.4-21.7-bigsmp -rw-r--r-- 1 root root 1487283 Jul 11 15:31 initrd-2.6.11.4-21.7-bigsmp.custom -rw-r--r-- 1 root root 1285487 Jul 7 15:47 initrd-2.6.11.4-21.7-um lrwxrwxrwx 1 root root 23 Jul 7 15:47 initrd-um -> initrd-2.6.11.4-21.7-um lrwxrwxrwx 1 root root 34 Jul 11 15:45 initrdatto -> initrd-2.6.11.4-21.7-bigsmp.custom -rwxr-xr-x 1 root root 2420024 Jun 2 13:09 linux-2.6.11.4-21.7-um lrwxrwxrwx 1 root root 22 Jul 7 15:47 linux-um -> linux-2.6.11.4-21.7-um lrwxrwxrwx 1 root root 21 Jul 7 07:44 linux-um.previous -> linux-2.6.11.4-20a-um drwx------ 2 root root 12288 Feb 4 19:12 lost+found -rw------- 1 root root 247808 Jul 11 15:48 map -rw-r--r-- 1 root root 94388 Mar 19 11:45 memtest.bin -rw-r--r-- 1 root root 133632 Jul 7 15:59 message -rw-r--r-- 1 root root 68171 Jun 2 13:49 symvers-2.6.11.4-21.7-i386-bigsmp.gz -rw-r--r-- 1 root root 20 Jun 2 13:09 symvers-2.6.11.4-21.7-um-um.gz lrwxrwxrwx 1 root root 28 Jul 7 15:46 vmlinuz -> vmlinuz-2.6.11.4-21.7-bigsmp -rw-r--r-- 1 root root 1555940 Jun 2 13:29 vmlinuz-2.6.11.4-21.7-bigsmp -rw-r--r-- 1 root root 1517778 Jul 8 17:44 vmlinuz-2.6.11.4-21.7-bigsmp.custom lrwxrwxrwx 1 root root 41 Jul 8 17:54 vmlinuzatto -> /boot/vmlinuz-2.6.11.4-21.7-bigsmp.custom ls -l /usr/src total 16156 drwxr-xr-x 11 root root 4096 Jul 8 15:55 . drwxr-xr-x 13 root root 4096 Jul 7 07:39 .. drwxr-xr-x 23 root root 4096 Jul 7 07:29 dicts -rwxr-xr-x 1 root root 16517969 Mar 2 15:49 jre-1_5_0_01-linux-i586.bin drwxr-xr-x 25 root root 4096 Jul 7 07:34 kernel-modules drwxr-xr-x 3 root root 20 Jul 7 15:30 linux-2.6.11.4-20a drwxr-xr-x 19 root root 4096 Jul 7 20:50 linux-2.6.11.4-21.7 drwxr-xr-x 3 root root 17 Jun 2 13:09 linux-2.6.11.4-21.7-obj drwxr-xr-x 20 root root 4096 Jul 8 16:45 linux-2.6.11.4-21.7.custom drwxr-xr-x 3 root root 20 Jul 7 07:34 linux-2.6.8-24 lrwxrwxrwx 1 root root 23 Jul 7 15:30 linux-obj -> linux-2.6.11.4-21.7-obj drwxr-xr-x 7 root root 67 Mar 23 13:34 packages # ls -l /lib/modules/ total 28 drwxr-xr-x 12 root root 4096 Jul 11 12:19 . drwxr-xr-x 13 root root 4096 Jul 7 15:30 .. drwxr-xr-x 4 root root 31 Jul 7 15:46 2.6.11.4-20a-bigsmp drwxr-xr-x 4 root root 4096 Jul 7 15:46 2.6.11.4-21.7-bigsmp drwxr-xr-x 4 root root 4096 Jul 11 12:19 2.6.11.4-21.7-bigsmp.custom drwxr-xr-x 3 root root 4096 Jul 8 17:36 2.6.11.4-21.7-default drwxr-xr-x 4 root root 4096 Jul 7 15:47 2.6.11.4-21.7-um drwxr-xr-x 2 root root 6 Jun 2 13:49 2.6.11.4-override-bigsmp drwxr-xr-x 2 root root 6 Jun 2 13:09 2.6.11.4-override-um drwxr-xr-x 4 root root 31 Jul 7 07:44 2.6.8-24-bigsmp drwxr-xr-x 3 root root 33 Jun 2 13:09 precompiled drwxr-xr-x 3 root root 35 Jun 2 13:09 scripts ~James
On Monday 11 July 2005 4:36 pm, James D. Parra wrote:
Hello,
How is this possible?
Okay, I copied /usr/src/linux-2.6.11.4-21.7 to /usr/src/linux-2.6.11.4-21.7.custom, ran "make menuconfig" (made my changes here so could use the new ATTO SCSI card) from the *custom directory, saved it, ran "make", then " make modules_install", created all the images and soft links under boot (below), edited lilo.conf and ran "lilo", rebooted, lilo says it is going to boot the new kernel, but instead of seeing my new kernel being loaded it says the default kernel is loaded; uname -r 2.6.11.4-21.7-default. However, that can't be possible because I now have access to my the tape drive attached to the ATTO SCSI card which I never had access to before when booting the other kernels. I have included relevant info below. Any ideas on what happened? I was hoping the kernel would be, 2.6.11.4-21.7-bigsmp.custom.
Maybe you forgot to run mkinitrd ? after make install and before lilo, you should run a command like mkinitrd -k vmlinuz-2.6.11.12-20050624110612-default -i initrd-2.6.11.12-20050624110612-default I normally have to do this when I compile from SuSE's KOTD. -- Osho
On Tuesday 12 July 2005 01:36, James D. Parra wrote:
Hello,
How is this possible?
Okay, I copied /usr/src/linux-2.6.11.4-21.7 to /usr/src/linux-2.6.11.4-21.7.custom, ran "make menuconfig" (made my changes here so could use the new ATTO SCSI card) from the *custom directory, saved it, ran "make", then " make modules_install", created all the images and soft links under boot (below), edited lilo.conf and ran "lilo", rebooted, lilo says it is going to boot the new kernel, but instead of seeing my new kernel being loaded it says the default kernel is loaded; uname -r 2.6.11.4-21.7-default. However, that can't be possible because I now have access to my the tape drive attached to the ATTO SCSI card which I never had access to before when booting the other kernels. I have included relevant info below. Any ideas on what happened? I was hoping the kernel would be, 2.6.11.4-21.7-bigsmp.custom.
Well, think about this a little. The kernel you got in the installation wasn't "default" it was "bigsmp". I don't know where you got the modules directory bigsmp.custom from, but it doesn't look like it was generated by the compile, judging by the dates on the directories The name of the kernel (the uname name, not the file name) is not taken from the name of the source directory, it's created by the Makefile in your source directory. The short story is: if you want to have a text tagged on to the kernel name, such as "atto" or "custom", you can create a file in the source directory called "localversion", containing the text you want to use The "default" name you got is just that, the default name. It doesn't mean you're using the same kernel as before, because you never had the -default kernel installed
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2005-07-11 at 16:36 -0700, James D. Parra wrote:
/usr/src/linux-2.6.11.4-21.7.custom, ran "make menuconfig" (made my changes here so could use the new ATTO SCSI card) from the *custom directory, saved ... kernel being loaded it says the default kernel is loaded; uname -r 2.6.11.4-21.7-default. However, that can't be possible because I now have access to my the tape drive attached to the ATTO SCSI card which I never had access to before when booting the other kernels. I have included relevant info below. Any ideas on what happened? I was hoping the kernel would be, 2.6.11.4-21.7-bigsmp.custom.
The kernel name does not depend on the name of the directory, but on the name you tell the kernel it has in its configuration file (var CONFIG_LOCALVERSION, accesible in the menu). And watch, your "/lib/modules/2.6.11.4-21.7-default" or "...-bigsmp." is now contaminated. You should get it again from the rpm. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFC0wxrtTMYHG2NR9URAsCwAJsGssbuC7RfDLjtD+ULurZ/ZQtIzACcDc5N TcjQeyxZnSgLyPvg+ylIJKo= =Bbdt -----END PGP SIGNATURE-----
participants (4)
-
Anders Johansson
-
Carlos E. R.
-
James D. Parra
-
Osho GG