On Sun, May 01, 2005 at 06:11:42AM -0700, cisco4ng wrote:
> All,
>
> I have a Nokia IP650 and I install IPSO 3.5FCS14 at bootmanager from
> scratch. Later on, I install IPSO 3.7.1build004 with the following
> command: "/etc/newimage -k -R -b -l ipso.tgz". By the way ipso.tgz is IPSO
> 3.7.1build 004.
>
> My understanding is that the option "-b" will force a bootmanager upgrade
> on the box as well. However, I am still getting this warning:
Yep it should.
>
> May 1 00:29:04 LAX-Hollywood [LOG_NOTICE] kernel: sio0: type 16550A
> May 1 00:29:05 LAX-Hollywood [LOG_WARNING] kernel: Bootmgr version is older
> than running kernel
> May 1 00:29:05 LAX-Hollywood [LOG_WARNING] kernel: Current: Bootmgr
> Revision: 3.3,base kernel=3.5-FCS14 01.11.2003-012500
> May 1 00:29:05 LAX-Hollywood [LOG_WARNING] kernel: Latest : NOKIA IPSO
> BOOTMGR VERSION=3.7.1-BUILD004 11.06.2003-010000
> May 1 00:29:06 LAX-Hollywood [LOG_WARNING] kernel: You may want to upgrade
> your bootmgr using /etc/upgrade_bootmgr.
>
So for curious reasons, it didn't actually upgrade your bootmgr. Did
newimage say after it had installed the OS:
Checking if bootmgr upgrade is needed...
Forcing upgrade of bootmgr as instructed.
Upgrading bootmgr....
Or something similar - not having a 3.5box around I'm using the 3.7.1Build13
code, and the wording may have changed...
I've not exactly used the above command in that I've not used the -k option,
but other than that mine has worked fine with any version of newimage that
*has* the -b opt :>
[snip]
> This box is running NG Feature Pack 3. The firewall hung really bad couple
> days ago (with
> barely little traffics) and I suspect it has to do with the old bootmanager
> that is not compatible
> with IPSO 3.7.1build004. To bring it back online, I had to turn off/on the
> power supply, boot
> into single user mode, run "fsck -y" about 8 times. After that, I have to
> run:
>
> "echo y | /etc/upgrade_bootmgr wd1 /var/admin/nkipflash-371.bin"
>
> By the way, Nokia TAC has been useless as always. They said that the "-b"
> is supposed to force the upgrade of bootmanager but it didn't and they
> don't know why.
>
> Has anyone seen this before?
>
No, fortunately. It could well be a bug in the newimage script in (perhaps
just that revision) of 3.5. It could also that for whatever reason the (3.5)
newimage command couldn't find the bootmgr image in the place it expected,
though it should have given some kind of error about that.
Smaff
--
You happen to be here, now.
=================================================
To set vacation, Out-Of-Office, or away messages,
send an email to [EMAIL PROTECTED]
in the BODY of the email add:
set fw-1-mailinglist nomail
=================================================
To unsubscribe from this mailing list,
please see the instructions at
http://www.checkpoint.com/services/mailing.html
=================================================
If you have any questions on how to change your
subscription options, email
[EMAIL PROTECTED]
=================================================
