coverup Posted February 4, 2004 Report Share Posted February 4, 2004 I know, this was covered many times.... just want to check if I got it right.... Ok, I got rpmdrake to install the latest enterprise kernel (2.4.22-26mdkenterprise), and now my /boot looks as -rw-r--r-- 1 root root 512 Feb 4 2004 boot.0300 lrwxrwxrwx 1 root root 29 Feb 4 07:49 config -> config-2.4.22-10mdkenterprise -rw-r--r-- 1 root root 52049 Sep 18 20:43 config-2.4.22-10mdk -rw-r--r-- 1 root root 51651 Sep 18 20:00 config-2.4.22-10mdkenterprise -rw-r--r-- 1 root root 51819 Jan 8 02:20 config-2.4.22-26mdkenterprise -rw-r--r-- 1 root root 5032 Sep 19 00:46 diag1.img -rw-r--r-- 1 root root 16796 Sep 19 00:46 diag2.img drwxr-xr-x 2 root root 4096 Feb 4 2004 grub/ -rw-r--r-- 1 root root 311158 Feb 4 2004 initrd-2.4.22-10mdkenterprise.img -rw-r--r-- 1 root root 308053 Feb 4 2004 initrd-2.4.22-10mdk.img -rw-r--r-- 1 root root 95299 Feb 4 07:54 initrd-2.4.22-26mdkenterprise.img lrwxrwxrwx 1 root root 33 Feb 4 07:54 initrd-enterprise.img -> initrd-2.4.22-26mdkenterprise.img lrwxrwxrwx 1 root root 23 Feb 4 2004 initrd.img -> initrd-2.4.22-10mdk.img lrwxrwxrwx 1 root root 37 Feb 4 07:50 kernel.h -> /boot/kernel.h-2.4.22-10mdkenterprise -rw-r--r-- 1 root root 537 Feb 4 05:40 kernel.h-2.4.22-10mdkenterprise -rw------- 1 root root 267776 Feb 4 07:54 map lrwxrwxrwx 1 root root 15 Feb 4 2004 message -> message-graphic -rw-r--r-- 1 root root 164755 Feb 4 2004 message-graphic -rw-r--r-- 1 root root 132 Feb 4 2004 message-text lrwxrwxrwx 1 root root 33 Feb 4 05:39 System.map -> System.map-2.4.22-10mdkenterprise -rw-r--r-- 1 root root 625045 Sep 18 20:43 System.map-2.4.22-10mdk -rw-r--r-- 1 root root 621280 Sep 18 20:00 System.map-2.4.22-10mdkenterprise -rw-r--r-- 1 root root 613565 Jan 8 02:20 System.map-2.4.22-26mdkenterprise -rw-r--r-- 1 root root 256 Feb 4 2004 us.klt lrwxrwxrwx 1 root root 20 Feb 4 2004 vmlinuz -> vmlinuz-2.4.22-10mdk -rw-r--r-- 1 root root 1343803 Sep 18 20:43 vmlinuz-2.4.22-10mdk -rw-r--r-- 1 root root 1375674 Sep 18 20:00 vmlinuz-2.4.22-10mdkenterprise -rw-r--r-- 1 root root 1354625 Jan 8 02:20 vmlinuz-2.4.22-26mdkenterprise lrwxrwxrwx 1 root root 30 Feb 4 07:54 vmlinuz-enterprise -> vmlinuz-2.4.22-26mdkenterprise I am worried that (1) System.map is still linked to System.map-2.4.22-10mdkenterprise, and not to System.map-2.4.22-26mdkenterprise; (2) kernel.h is linked to /boot/kernel.h-2.4.22-10mdkenterprise, and there is no equivalent file for kernel 2.4.22-26; (3) config -> config-2.4.22-10mdkenterprise, not config-2.4.22-26mdkenterprise; Also, in lilo.conf I now have two entries for 2.4.22-26mdkenterprise, and no entry for 2.4.22-10mdkenterprise boot=/dev/hda map=/boot/map vga=normal default="linux-enterpris" keytable=/boot/us.klt prompt nowarn timeout=100 message=/boot/message menu-scheme=wb:bw:wb:bw image=/boot/vmlinuz-enterprise label="linux-enterpris" root=/dev/hda5 initrd=/boot/initrd-enterprise.img append="nolapic devfs=mount hdc=ide-scsi acpi=off splash=silent" read-only image=/boot/vmlinuz label="linux" root=/dev/hda5 initrd=/boot/initrd.img append="noapic devfs=mount hdc=ide-scsi acpi=ht splash=silent" vga=788 read-only image=/boot/vmlinuz label="linux-nonfb" root=/dev/hda5 initrd=/boot/initrd.img append="noapic devfs=mount hdc=ide-scsi acpi=ht" read-only image=/boot/vmlinuz label="failsafe" root=/dev/hda5 initrd=/boot/initrd.img append="failsafe noapic devfs=nomount hdc=ide-scsi acpi=ht" read-only other=/dev/hda1 label="windows" table=/dev/hda image=/boot/vmlinuz-2.4.22-26mdkenterprise label=2422-26ent root=/dev/hda5 read-only optional vga=normal append=" nolapic devfs=mount hdc=ide-scsi acpi=off splash=silent" initrd=/boot/initrd-2.4.22-26mdkenterprise.img I'm saying that cause both the first and the last entries point to initrd-2.4.22-26mdkenterprise.img... Do I leave it as as, or should I do any editing? your advise is desperately needed.... Quote Link to comment Share on other sites More sharing options...
liquidzoo Posted February 4, 2004 Report Share Posted February 4, 2004 It wouldn't hurt anything to remove the System.map, kernel.h, and config symlinks and remap them to the correct files using ln -s <source file> <dest file> As for your lilo entry, there is an entry for both kernels if you look closely image=/boot/vmlinuz-enterprise label="linux-enterpris" root=/dev/hda5 initrd=/boot/initrd-enterprise.img append="nolapic devfs=mount hdc=ide-scsi acpi=off splash=silent" read-only image=/boot/vmlinuz label="linux" root=/dev/hda5 initrd=/boot/initrd.img append="noapic devfs=mount hdc=ide-scsi acpi=ht splash=silent" vga=788 read-only Which, if you look closely at your vmlinuz symlinks: lrwxrwxrwx 1 root root 20 Feb 4 2004 vmlinuz -> vmlinuz-2.4.22-10mdk-rw-r--r-- 1 root root 1343803 Sep 18 20:43 vmlinuz-2.4.22-10mdk -rw-r--r-- 1 root root 1375674 Sep 18 20:00 vmlinuz-2.4.22-10mdkenterprise -rw-r--r-- 1 root root 1354625 Jan 8 02:20 vmlinuz-2.4.22-26mdkenterprise lrwxrwxrwx 1 root root 30 Feb 4 07:54 vmlinuz-enterprise -> vmlinuz-2.4.22-26mdkenterprise and your initrd symlinks: -rw-r--r-- 1 root root 311158 Feb 4 2004 initrd-2.4.22-10mdkenterprise.img-rw-r--r-- 1 root root 308053 Feb 4 2004 initrd-2.4.22-10mdk.img -rw-r--r-- 1 root root 95299 Feb 4 07:54 initrd-2.4.22-26mdkenterprise.img lrwxrwxrwx 1 root root 33 Feb 4 07:54 initrd-enterprise.img -> initrd-2.4.22-26mdkenterprise.img lrwxrwxrwx 1 root root 23 Feb 4 2004 initrd.img -> initrd-2.4.22-10mdk.img You will see that vmlinuz and initrd.img both point to your default kernel, while vmlinuz-enterprise and initrd-enterprise.img both point to your new kernel. Be sure that if you do re-do your symlinks, you run lilo again before you reboot. When you do, you will see 2 entries at the top of your lilo screen. The first will boot into the new kernel, while the second will boot into the default kernel. By the way, a little OT here, but what is the benefit of the enterprise kernel over the default kernel-2.4.22-10mdk? Quote Link to comment Share on other sites More sharing options...
coverup Posted February 4, 2004 Author Report Share Posted February 4, 2004 The enterprise kernel was chosen by the MDK installer - I have 1Gig of RAM, and someone suggested that in that case the installer picks this kernel as default... As for my question, I was expecting that after upgrade, I would have an option to boot into the old *enterprise* kernel as well, and this option has been re-written, so I have now two entries for the new enterprise kernel and one entry for the standard old kernel (the one you pointed out)... Meantime, I went for it as is... just ran lilo -v, and shutdown now works with "acpi=on no apic nolapic". Well, it sort of works - no suspend/resume, and no battery meter but poweroff now works after I exit X... Quote Link to comment Share on other sites More sharing options...
ryanjensen Posted February 4, 2004 Report Share Posted February 4, 2004 To be able to boot into your old *enterprise kernel, simply add this to the end of your lilo.conf file image=/boot/vmlinuz-2.4.22-10mdkenterprise label=2422-10ent root=/dev/hda5 read-only optional vga=normal append=" nolapic devfs=mount hdc=ide-scsi acpi=off splash=silent" initrd=/boot/initrd-2.4.22-10mdkenterprise.img then run lilo as root. Ryan Quote Link to comment Share on other sites More sharing options...
Counterspy Posted February 5, 2004 Report Share Posted February 5, 2004 It is the case that the Enterprise Kernel is chosen by default to handle 1 Gb.+ of main memory. This happened with both 9.1 and 9.2 for me. Counterspy Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.