Mailinglist Archive: opensuse (3996 mails)
| < Previous | Next > |
RE: [SLE] Novell kit 9.1 running 2.4 not 2.6??
- From: Vince Negri <vnegri@xxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 7 Sep 2004 09:53:48 +0100
- Message-id: <35C843B8EC93D511844500306E0029B3C9D521@ASL1>
> So why does the thing boot into 2.4.21, apparently from my hda2 9.0
slice??
Because your lilo.conf is pointing to
/boot/vmlinuz for both 9.0 and 9.1.
The /boot referred to in lilo.conf is *not* the /boot folder
that is in place when the system is booted, but the /boot
folder that is in place *at the moment lilo is run.* So that
/boot/vmlinuz gets parsed as the same kernel in all cases
Did you, perhaps, get a YOU kernel update for 9.0 recently? With
the lilo.conf you have, that would end up with all suse's booting
the same kernel.
To avoid a total descent into madness :) you either need to
a) switch to GRUB or
b) fix your lilo.conf.
For b), you would need to edit your fstab so that your 9.0 install
mounted hda1 (read-only) at some directory, say
/mnt/suse91, and then your lilo.conf would end with
image = /mnt/suse91/boot/vmlinuz
label = suse91
initrd = /mnt/suse91/boot/initrd
..etc..
Then re-running lilo from suse9.0 would fix everything.
I hope this makes sense!
However, you haven't said what bootloader setup you asked
for when installing 9.1. Did you tell yast not to install a
bootloader, because you intended all along to boot via
your original lilo setup?
> -----Original Message-----
> From: David T-G [SMTP:davidtg-suse-linux-e@xxxxxxxxxxxxxxx]
> Sent: Monday, September 06, 2004 3:50 PM
> To: SuSE Linux (English) list
> Cc: Vince Negri
> Subject: Re: [SLE] Novell kit 9.1 running 2.4 not 2.6??
>
> Vince, et al --
>
> ...and then Vince Negri said...
> %
> % I notice that you loaded 9.1 "onto the swap slice on
> % my basic e-Machines desktop (where I'm happily running 9.0 Pro) "
> % What kernel version is your 9.0 install at?
>
> It's 2.4. Oh, wait ... Hey, it's 2.4.21-238!
>
> OK, now I am very confused. I have lilo in my SuSE 9.0 hda2 root with an
> entry for 'suse91' pointing to hda1. To wit:
>
> #message = /boot/message
> timeout = 30
> prompt
> default = linux
> boot = /dev/hda
>
> image = /boot/vmlinuz
> ###Don't change this comment - YaST2 identifier: Original name:
> linux###
> label = linux
> initrd = /boot/initrd
> optional
> root = /dev/hda2
> vga = 0x31a
> append = "splash=verbose desktop hdc=ide-scsi hdclun=0 showopts"
>
> image = /boot/vmlinuz
> ###Don't change this comment - YaST2 identifier: Original name:
> single###
> label = single
> initrd = /boot/initrd
> optional
> root = /dev/hda2
> vga = 0x31a
> append = "splash=verbose desktop hdc=ide-scsi hdclun=0 showopts
> single"
>
> image = /boot/vmlinuz
> label = suse91
> initrd = /boot/initrd
> optional
> root = /dev/hda1
> vga = 0x31a
> append = "splash=verbose desktop hdc=ide-scsi hdclun=0 showopts"
>
> When I boot the 9.1 slice, df reports /dev/hda1 as / (my only mount) and
> yet I see 2.6 stuff in my /boot dir:
>
> davidtg@strumpet:~> df -kh /mnt/tmp
> Filesystem Size Used Avail Use% Mounted on
> /dev/hda1 2.1G 1.7G 374M 82% /mnt/tmp
> davidtg@strumpet:~> ls -goh /mnt/tmp/boot/
> total 5.2M
> -rw-r--r-- 1 104K Apr 6 22:14 Kerntypes-2.6.4-52-default
> -rw-r--r-- 1 712K Apr 6 22:08 System.map-2.6.4-52-default
> lrwxrwxrwx 1 1 Sep 6 07:55 boot -> .
> -rw-r--r-- 1 54K Apr 6 22:14 config-2.6.4-52-default
> drwxr-xr-x 2 360 Sep 6 07:55 grub
> lrwxrwxrwx 1 23 Sep 6 08:08 initrd -> initrd-2.6.4-52-default
> -rw-r--r-- 1 1.1M Sep 6 08:08 initrd-2.6.4-52-default
> -rw-r--r-- 1 82K Apr 6 13:29 message
> -rw-r--r-- 1 73K Apr 6 22:14
> modversions-2.6.4-52-i386-default.gz
> -rw-r--r-- 1 1.7M Apr 6 22:14 vmlinux-2.6.4-52-default.gz
> lrwxrwxrwx 1 24 Sep 6 07:59 vmlinuz ->
> vmlinuz-2.6.4-52-default
> -rw-r--r-- 1 1.5M Apr 6 22:08 vmlinuz-2.6.4-52-default
>
> So why does the thing boot into 2.4.21, apparently from my hda2 9.0
> slice??
>
>
> TIA again
>
> Scratching my head,
> :-D
> --
> David T-G
> davidtg@xxxxxxxxxxxxxxx
> http://justpickone.org/davidtg/ Shpx gur Pbzzhavpngvbaf Qrprapl Npg!
>
Legal Disclaimer: Any views expressed by the sender of this message are
not necessarily those of Application Solutions Ltd. Information in this
e-mail may be confidential and is for the use of the intended recipient
only, no mistake in transmission is intended to waive or compromise such
privilege. Please advise the sender if you receive this e-mail by mistake.
slice??
Because your lilo.conf is pointing to
/boot/vmlinuz for both 9.0 and 9.1.
The /boot referred to in lilo.conf is *not* the /boot folder
that is in place when the system is booted, but the /boot
folder that is in place *at the moment lilo is run.* So that
/boot/vmlinuz gets parsed as the same kernel in all cases
Did you, perhaps, get a YOU kernel update for 9.0 recently? With
the lilo.conf you have, that would end up with all suse's booting
the same kernel.
To avoid a total descent into madness :) you either need to
a) switch to GRUB or
b) fix your lilo.conf.
For b), you would need to edit your fstab so that your 9.0 install
mounted hda1 (read-only) at some directory, say
/mnt/suse91, and then your lilo.conf would end with
image = /mnt/suse91/boot/vmlinuz
label = suse91
initrd = /mnt/suse91/boot/initrd
..etc..
Then re-running lilo from suse9.0 would fix everything.
I hope this makes sense!
However, you haven't said what bootloader setup you asked
for when installing 9.1. Did you tell yast not to install a
bootloader, because you intended all along to boot via
your original lilo setup?
> -----Original Message-----
> From: David T-G [SMTP:davidtg-suse-linux-e@xxxxxxxxxxxxxxx]
> Sent: Monday, September 06, 2004 3:50 PM
> To: SuSE Linux (English) list
> Cc: Vince Negri
> Subject: Re: [SLE] Novell kit 9.1 running 2.4 not 2.6??
>
> Vince, et al --
>
> ...and then Vince Negri said...
> %
> % I notice that you loaded 9.1 "onto the swap slice on
> % my basic e-Machines desktop (where I'm happily running 9.0 Pro) "
> % What kernel version is your 9.0 install at?
>
> It's 2.4. Oh, wait ... Hey, it's 2.4.21-238!
>
> OK, now I am very confused. I have lilo in my SuSE 9.0 hda2 root with an
> entry for 'suse91' pointing to hda1. To wit:
>
> #message = /boot/message
> timeout = 30
> prompt
> default = linux
> boot = /dev/hda
>
> image = /boot/vmlinuz
> ###Don't change this comment - YaST2 identifier: Original name:
> linux###
> label = linux
> initrd = /boot/initrd
> optional
> root = /dev/hda2
> vga = 0x31a
> append = "splash=verbose desktop hdc=ide-scsi hdclun=0 showopts"
>
> image = /boot/vmlinuz
> ###Don't change this comment - YaST2 identifier: Original name:
> single###
> label = single
> initrd = /boot/initrd
> optional
> root = /dev/hda2
> vga = 0x31a
> append = "splash=verbose desktop hdc=ide-scsi hdclun=0 showopts
> single"
>
> image = /boot/vmlinuz
> label = suse91
> initrd = /boot/initrd
> optional
> root = /dev/hda1
> vga = 0x31a
> append = "splash=verbose desktop hdc=ide-scsi hdclun=0 showopts"
>
> When I boot the 9.1 slice, df reports /dev/hda1 as / (my only mount) and
> yet I see 2.6 stuff in my /boot dir:
>
> davidtg@strumpet:~> df -kh /mnt/tmp
> Filesystem Size Used Avail Use% Mounted on
> /dev/hda1 2.1G 1.7G 374M 82% /mnt/tmp
> davidtg@strumpet:~> ls -goh /mnt/tmp/boot/
> total 5.2M
> -rw-r--r-- 1 104K Apr 6 22:14 Kerntypes-2.6.4-52-default
> -rw-r--r-- 1 712K Apr 6 22:08 System.map-2.6.4-52-default
> lrwxrwxrwx 1 1 Sep 6 07:55 boot -> .
> -rw-r--r-- 1 54K Apr 6 22:14 config-2.6.4-52-default
> drwxr-xr-x 2 360 Sep 6 07:55 grub
> lrwxrwxrwx 1 23 Sep 6 08:08 initrd -> initrd-2.6.4-52-default
> -rw-r--r-- 1 1.1M Sep 6 08:08 initrd-2.6.4-52-default
> -rw-r--r-- 1 82K Apr 6 13:29 message
> -rw-r--r-- 1 73K Apr 6 22:14
> modversions-2.6.4-52-i386-default.gz
> -rw-r--r-- 1 1.7M Apr 6 22:14 vmlinux-2.6.4-52-default.gz
> lrwxrwxrwx 1 24 Sep 6 07:59 vmlinuz ->
> vmlinuz-2.6.4-52-default
> -rw-r--r-- 1 1.5M Apr 6 22:08 vmlinuz-2.6.4-52-default
>
> So why does the thing boot into 2.4.21, apparently from my hda2 9.0
> slice??
>
>
> TIA again
>
> Scratching my head,
> :-D
> --
> David T-G
> davidtg@xxxxxxxxxxxxxxx
> http://justpickone.org/davidtg/ Shpx gur Pbzzhavpngvbaf Qrprapl Npg!
>
Legal Disclaimer: Any views expressed by the sender of this message are
not necessarily those of Application Solutions Ltd. Information in this
e-mail may be confidential and is for the use of the intended recipient
only, no mistake in transmission is intended to waive or compromise such
privilege. Please advise the sender if you receive this e-mail by mistake.
| < Previous | Next > |