Juergen ,
Thanks for that information,that makes things
clear.
There was one thing i forgot to mention yesterday
though ,which was the installation screen displayed a
message saying ' Installation partially failed ' and
look in the /tmp/install_log for details( Installation
did continue though succesfully and prompted for a
reboot too )
Today i was able to capture this file and am attaching
the same, if you look at the beginning of the file you
will find that there seem to be errors while
installing the package ,also pls look at the end of
the file
Could that be the root cause as to why the archive is
not built correctly and hence on reboot 'error 28' msg
is showing up ??
Btw I am using Solaris 10 8/07 as the installation OS
and upper memory ~ 2 GB
I did take a look at the src code as well and i think
i should be clera on both the bugs listed below
Pls advise
Thanks
Som
--- Juergen Keil <[EMAIL PROTECTED]> wrote:
>
> > Juergen,
> > Im not sure i understand when u say it
> > should contain both 32 and 64-bit drivers
>
> The compressed cpio driver package in
> \DU\sol_210\i86pc\Product\driver.Z
> should contain both 32- and 64-bit drivers.
>
> > ..i.e should
> > both the drivers be compressed and stored in
> > Tools\boot\ and Tools\boot\amd64 resply?
>
> No. Only the 32-bit driver module.
> (and only for Solaris 10 x86 FCS and older).
>
>
> The \DU\sol_210\i86pc\Tools\boot\ stuff is
> used by the old "boot.bin" boot code, which was
> used by Solaris 10 x86 (FCS) and older.
> The boot code that started with this screen:
>
>
> SunOS Secondary Boot version 4.02
>
>
> Solaris Booting System
>
> Running Configuration Assistant....
>
> ...
>
> Press ESCape to interrupt autoboot in 4 seconds.
>
>
>
> After pressing the ESC key the "Solaris Device
> Configuration
> Assistant" starts; there you can use the "F4 Add
> Driver"
> function key to load additional drivers from an "ITU
> driver
> diskette".
>
> The old boot.bin boot code never supported booting
> the installation kernel as a 64-bit kernel, so it
> was
> sufficient to only have a 32-bit kernel module in
> ...\Tools\boot\
>
> AFAIK, the uncompressed 32-bit driver kernel module
> from
> ...\Tools\boot\ was somehow magically added to the
> read-only ufs root filesystem on the installation CD
> on the fly, together with the necessary driver
> binding
> entries in etc/driver_aliases. I think this was
> done
> using some hooks / extension in the ufs filesystem
> code
> in the old boot code, in boot.bin.
>
>
> For the new GRUB based boot code, ...\Tools\boot\
> isn't needed at all. I guess I could add something
> to my ITU build scripts to remove
> DU/sol_211/i86pc/Tools/Boot,
> because an OpenSolaris ITU doesn't need it any more.
>
> > Is there a
> > standard procedure for this kind of problem where
> we
> > want both 32 and 64-bit versions of the same
> driver to
> > coexist on the same package? (A sample reference
> would
> > be great)
> > Thing is my installation seems to have proceeded
> > succesfully to 100% and eventually it did prompt
> me
> > for a reboot which i did.Subsequently the
> installed OS
> > on my LUN shows up on the GRUB menu ,but upon
> > selection i get error message saying
> >
> > 'Error 28: Unable to fit selected image into
> memory '
> > ( i get same problem even when i choose fail-safe
> > option on the GRUB menu)
>
> That is, you do have Solaris installed on an iSCSI
> disk? And GRUB and the GRUB menu is loaded via
> iSCSI?
>
> How does the PC boot from iSCSI into GRUB? Does the
> iSCSI controller add a BIOS boot device "C:" that is
> used to load GRUB, and that is used by GRUB to load
> the Solaris kernel and boot archive from your iSCSI
> LUN?
>
>
> Possible problems are:
>
> - Your system does not have enough "upper memory" to
>
> load the boot archive from iSCSI, that is, it is
> really running out of memory.
>
> See Bug ID: 6522857
>
>
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6522857
>
> Check how much "upper memory" is reported on the
> initial GRUB screen.
>
>
> - Your iSCSI hardware's PC BOOT support might report
> read
> errors, which do confuse old GRUBs.
>
> See Bug ID: 6387379
>
>
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6387379
>
> This one is fixed in recent versions of
> opensolaris;
> but I'm not sure of the fix was backported to
> Solaris 10.
>
>
> - the kernel and/or boot_archive file on the iSCSI
> root fs LUN are
> indeed corrupted somehow, GRUB tries to load and
> uncompress the
> corrupted data, and this might indeed overflow the
> available
> memory, before GRUB notices that the kernel and/or
> boot_archive
> data is corrupted. IIRC, current OpenSolaris
> GRUBs does verify
> the CRC checksum included in the gzip compressed
> boot_archive
> file, but older GRUBs might ignore the CRC
> checksums.
>
>
>
> > So somehow i cant help get the feeling that this
> might
> > be a packaging issue..i.e it did not get the
> 64-bit
> > driver??
> >
> > Any ideas ..pls help
> >
> > Thanks
> > Som
> >
> >
> >
> >
> > --- Juergen Keil <[EMAIL PROTECTED]> wrote:
> >
> > >
> > > > In regards to the same , i have a basic
> question
> > > > regarding the packaging of both 32/64bit
> driver on
> > > the
> > > > same floppy , in the 'build' script(under the
> \ni\
> > > > folder in itu.tar.bz2 ) do i need to create
> 2
> > > > compressed archives of my drivers - one for 32
> and
> > > one
> > > > for 64-bit just like the ni/dp380 driver
> packages
> > > as
> > > > shown below: ?
> > > >
> > > > compress < ni > $dest/Tools/Boot/ni/ni
> > > > cp ni.itu $dest/Tools/Boot/ni
> > > >
> > > > compress < dp8390 >
> $dest/Tools/Boot/dp8390/dp8390
> > > > cp dp8390.itu $dest/Tools/Boot/dp8390
> > >
> > >
> > > No. IIRC, the compressed 32-bit drivers in
> > > Tools/Boot/...
> > > were used by Solaris 10 x86 (pre-GRUB) and
> Solaris 9
> > > x86
> > > or older.
> > >
> > > For S10 x86 (post-GRUB), the installable driver
> > > package is
> > > important and should contain both 32- and 64-bit
> > > drivers.
> > >
>
=== message truncated ===
____________________________________________________________________________________
Looking for last minute shopping deals?
Find them fast with Yahoo! Search.
http://tools.search.yahoo.com/newsearch/category.php?category=shopping
_______________________________________________
driver-discuss mailing list
driver-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/driver-discuss
