PCLinuxOS-Forums
News: ...FLASH!!! ...New PCLinuxOS Testing board now open. Register today! Be an active contributor to the PCLinuxOS future! ... Read all about it now, on THIS forum!!!..
 
*
Welcome, Guest. Please login or register. May 27, 2012, 07:56:08 PM


Login with username, password and session length


Pages: [1]   Go Down
  Print  
Author Topic: [SOLVED] GRUB questions prior to updating my Kernel  (Read 816 times)
BMaytum
Full Member
***
Offline Offline

Posts: 52



« on: November 11, 2011, 08:06:02 PM »

My PCLOS is up-to-date via Synaptic (today I ran "aptupdate") EXCEPT currently my PCLOS is using old kernel-2.6.33.7-pclos4.bfs.  Texstar has mentioned in several forum posts that we should update to a new kernel (stating that old kernels may soon have compatibility issues with updated PCLOS components). So I'd like to update to kernel-2.6.38.8-pclos3.bfs, but before I do so, I'm wondering if that kernel upgrade will automatically also update my GRUB "menu.lst" file?  And if not, what pre-Kernel Update steps and what post-Kernel Update steps must I take to ensure I'll still be able to dual-boot this PC?

For info, here's my current "menu.lst" file:
Code:
[root@localhost ~]# cat /boot/grub/menu.lst
# This GRUB menu.lst was autogenerated 9/20/2010 when BDM upgraded PCLOS2010.07 to newer kernel 2.6.33.7-pclos4.bfs
#  BDM modified line "default 0" to "default 3" to make Windows XP the Default OS to boot after timeout 10 secs.
timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,4)/boot/gfxmenu
# default 0
default 3

title linux
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux root=LABEL=PCL-root vmalloc=256M resume=LABEL=PCL-swap splash=silent vga=788
initrd (hd0,4)/boot/initrd.img

title linux-nonfb
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=LABEL=PCL-root vmalloc=256M resume=LABEL=PCL-swap
initrd (hd0,4)/boot/initrd.img

title failsafe
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=failsafe root=LABEL=PCL-root failsafe vmalloc=256M
initrd (hd0,4)/boot/initrd.img

title windows
rootnoverify (hd1,0)
map (0x81) (0x80)
map (0x80) (0x81)
makeactive
chainloader +1

title 2.6.33.5-pclos1.bfs
kernel (hd0,4)/boot/vmlinuz-2.6.33.5-pclos1.bfs BOOT_IMAGE=2.6.33.5-pclos1.bfs root=LABEL=PCL-root vmalloc=256M resume=LABEL=PCL-swap splash=silent vga=788
initrd (hd0,4)/boot/initrd-2.6.33.5-pclos1.bfs.img

title 2.6.33.7-pclos4.bfs
kernel (hd0,4)/boot/vmlinuz-2.6.33.7-pclos4.bfs BOOT_IMAGE=2.6.33.7-pclos4.bfs root=LABEL=PCL-root vmalloc=256M resume=LABEL=PCL-swap splash=silent vga=788
initrd (hd0,4)/boot/initrd-2.6.33.7-pclos4.bfs.img

You'll note that WindowsXP is the default operating system for booting this PC - I want to retain (or restore) that behavior when the new Kernel is installed.

My GRUB expertise is novice, I struggled a lot with GRUB last year (see http://www.pclinuxos.com/forum/index.php/topic,79699.0.html) even with knowledgable & patient help from Old-Polack and kjpetrie.  Hence I seek advice about what I need to do before (and/or after) I update to the new Kernel.
Logged

Asus P5N32-E SLI, C2D E8400 w/ Zalman CNPS9500AT HSF, 4GB DDR2, Asus ENGTX580 1536MB Vidcard, ThermalTake 750W Modular PSU, Samsung SATA DVD, WD 320GB SATA-II,  Win7 Pro x64.
Asus P4PE, 2.4GHz P4, 2GB RAM, Asus EN6800GT/256MB Vidcard, 250&120GB HDDs, dual-boot WinXPSP3 & PCLOS2012.2
Old-Polack
Administrator
Hero Member
*****
Online Online

Posts: 9697


----IOFLU----


« Reply #1 on: November 11, 2011, 11:06:47 PM »

BMaytum:

When you install a new kernel, the links used by grub are recreated pointing to the newest kernel, so there is nothing that need to be done in your menu.lst. Your default boot option in the grub menu will automatically boot to the newest kernel installed.
Logged

Old-Polack

Of what use be there for joy, if not for the sharing thereof?



Lest we forget...
BMaytum
Full Member
***
Offline Offline

Posts: 52



« Reply #2 on: November 12, 2011, 02:08:51 AM »

Thanks (yet again) Old-Polack!  Based on your assurances above, I used Synaptic to install the new kernel-2.6.38.8-pclos3.bfs (version 1-1pclos2011) & it's associated kernel-devel-2.6.38.3-pclos3.bfs kernel headers, and yes choosing linux from the boot menu does indeed boot that new kernel.  Afterwards I also used Synaptic to uninstall kernel-2.6.33.5-pclos1.bfs & it's associated kernel-devel headers (that version may have been the base kernel from my initial install from LiveCD (PCLOS2010.7? I forget....), just to reclaim aprox 56MB diskspace on my / partition.  My current Grub menu list file now has these entries:
Code:
[root@localhost ~]# cat /boot/grub/menu.lst
timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,4)/boot/gfxmenu
default 3

title linux
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux root=LABEL=PCL-root vmalloc=256M resume=LABEL=PCL-swap splash=silent vga=788
initrd (hd0,4)/boot/initrd.img

title linux-nonfb
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=LABEL=PCL-root vmalloc=256M resume=LABEL=PCL-swap
initrd (hd0,4)/boot/initrd.img

title failsafe
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=failsafe root=LABEL=PCL-root failsafe vmalloc=256M
initrd (hd0,4)/boot/initrd.img

title windows
rootnoverify (hd1,0)
map (0x81) (0x80)
map (0x80) (0x81)
makeactive
chainloader +1

title 2.6.33.7-pclos4.bfs
kernel (hd0,4)/boot/vmlinuz-2.6.33.7-pclos4.bfs BOOT_IMAGE=2.6.33.7-pclos4.bfs root=LABEL=PCL-root vmalloc=256M resume=LABEL=PCL-swap splash=silent vga=788
initrd (hd0,4)/boot/initrd-2.6.33.7-pclos4.bfs.img

title 2.6.38.8-pclos3.bfs
kernel (hd0,4)/boot/vmlinuz-2.6.38.8-pclos3.bfs BOOT_IMAGE=2.6.38.8-pclos3.bfs root=LABEL=PCL-root vmalloc=256M resume=LABEL=PCL-swap splash=silent vga=788
initrd (hd0,4)/boot/initrd-2.6.38.8-pclos3.bfs.img

This menu file retained WindowsXP as the the default operating system ("default 3"), and all working fine.

I've marked this thread as [Solved]. Thanks O-P.
Logged

Asus P5N32-E SLI, C2D E8400 w/ Zalman CNPS9500AT HSF, 4GB DDR2, Asus ENGTX580 1536MB Vidcard, ThermalTake 750W Modular PSU, Samsung SATA DVD, WD 320GB SATA-II,  Win7 Pro x64.
Asus P4PE, 2.4GHz P4, 2GB RAM, Asus EN6800GT/256MB Vidcard, 250&120GB HDDs, dual-boot WinXPSP3 & PCLOS2012.2
Vortеx
Hero Member
*****
Offline Offline

Posts: 2010


Vorteks without the Secretary


« Reply #3 on: November 12, 2011, 08:40:29 AM »

I've marked this thread as [Solved].
No you haven't Tongue

You marked your last post only.
If you edit the title of the first post this should be done. Smiley
Logged
Pages: [1]   Go Up
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.16 | SMF © 2011, Simple Machines

Valid XHTML 1.0! Valid CSS! Dilber MC Theme by HarzeM