Hi Juergen,
      Thanks a ton for the help, yes all i had to do
was recompile my driver for 32-bit and specify that as
the kernel module for the pkg_drv command,then when i
selected option 5 , it detected/installed my driver to
miniroot and booted of it, was able to detect my
target drive too!!!
Only question now is ..how do i get both 32-bit and
64-bit modules onto the pkg? because the OS CD that i
am using is for x86-64? 

Thanks
Som

--- Juergen Keil <[EMAIL PROTECTED]> wrote:

> Hi Som,
> 
> >          Im attempting to install/boot  Solaris OS
> on
> > a SCSI target drive that would be discovered using
> my
> > iSCSI HBA driver.
> >  To do this, all i need to do (pls correct me if i
> am
> > wrong) is to create a driver update floppy and add
> the
> > driver updates(using option 5) in the installation
> > process at the beginning so my driver will be
> loaded
> > and my SCSI target/LUN will be reported as one of
> the
> > disks on which OS can be installed
> > 
> > Here is what i did for pkg_drv 
> > 
> > /opt/SUNWpkgd/bin/pkg_drv -i '"pci1234,5678"' -c
> scsi
> > -r 1.0 -d "My Dummy family of HBA Controllers" -D
> "My
> > iSCSI HBA" -t pci -V 'VERSION=0.1' mydriver 
> > 
> > 
> > (NOTE: using dummy values above) 
> > 
> > The package was succesfully created and using 'dd'
> i
> > got the /tmp/737/ITU.3(output diskette image) onto
> the
> > floppy .. is that enough?
> 
> "dd if={pcfs_image} of=/dev/rdiskette bs=18k" should
> be  
> enough, if that file contains an msdos fat
> filesystem image.
> 
> Try this as a sanity check for the ITU floppy image:
> 
>     # lofiadm -a /tmp/737/ITU.3 /dev/lofi/99
>     
>     # mount -r -F pcfs /dev/lofi/99 /mnt
>     
>     # ls -l /mnt
>     total 1
>     drwxrwxrwx   1 root     root         512 Feb  6 
> 2008 DU
> 
>     # ls -l /mnt/DU
>     total 3
>     -rwxrwxrwx   1 root     root           7 Feb  6 
> 2008 label.vol
>     drwxrwxrwx   1 root     root         512 Feb  6 
> 2008 sol_210
>     drwxrwxrwx   1 root     root         512 Feb  6 
> 2008 sol_211
>     
>     # ls -l /mnt/DU/sol_210
>     total 1
>     drwxrwxrwx   1 root     root         512 Feb  6 
> 2008 i86pc
>     
>     # ls -l /mnt/DU/sol_210/i86pc
>     total 5
>     drwxrwxrwx   1 root     root         512 Feb  6 
> 2008 Docs
>     drwxrwxrwx   1 root     root         512 Feb  6 
> 2008 Patches
>     drwxrwxrwx   1 root     root        1024 Feb  6 
> 2008 Product
>     drwxrwxrwx   1 root     root         512 Feb  6 
> 2008 Tools
>     
>     # ls -l /mnt/DU/sol_210/i86pc/Tools
>     total 9
>     drwxrwxrwx   1 root     root        1024 Feb  6 
> 2008 Boot
>     -rwxrwxrwx   1 root     root        3323 Feb  6 
> 2008 install.sh
>     
>     # ls -l /mnt/DU/sol_210/i86pc/Tools/install.sh 
>     -rwxrwxrwx   1 root     root        3323 Feb  6 
> 2008 
> /mnt/DU/sol_210/i86pc/Tools/install.sh
>    
>    
>    
> > Then i inserted the Solaris 10 CD ROM and
> proceeded
> > installation by choosing option 5 (which is to add
> > driver updates) . The installation program seems
> to
> > detect/read the floppy and i get a message saying 
> > 'Extracting software from floppy' 
> 
> Is there any indication that the driver package for
> your iscsi hardware
> is added to the system?
> 
> Does your iscsi driver package contain some kind of
> copyright file that
> is displayed at package installation time?  Do you
> see that copyright
> file displayed on the console when you use "option 5
> (add driver
> updates)" ?
> 
> 
> Did you make sure that your driver package contains
> both 32- and 64-bit
> kernel modules?  During installation a 32-bit kernel
> is running, so we
> need a 32-bit driver module.
> 
> 
> > But after the rest of the installation proceeds ,
> find
> > that my driver is not installed at all and
> therefore
> > NO hard disks are found
> > 
> > Any ideas pls as to what could be the problem?
> > 
> > Thanks
> > Som
> > 
> > 
> > --- Juergen Keil <[EMAIL PROTECTED]> wrote:
> > 
> > > 
> > > RamKishoreV wrote:
> > > 
> > > > Javen Wu <[EMAIL PROTECTED]> wrote: 
> > > > > You need ITU image. I assume you are working
> on
> > > X86. Please try the 
> > > > > below link:
> > > > >
> > >
> http://www.tools.de/opensource/solaris/itu/newboot/
> > > >
> > > > I looked into the ITU directory. It doesn't
> > > contain any scsi device
> > > > specific driver disks. Do we have to do
> anything
> > > different for scsi
> > > > specific driver disks. 
> > > 
> > > I don't think anything special is needed for
> scsi
> > > itu drivers.
> > > 
> > > We need a standard package that installs the new
> > > driver to the
> > > ramdisk root filesystem, and a postinstall
> script in
> > > the package
> > > that registers  the new driver with the kernel
> > > (add_drv ...).
> > > 
> > > scsi drivers do register themself in
> > > /etc/driver_classes, so you
> > > probably need to use the "-c scsi" option for
> > > add_drv...
> > > 
> > > 
> > > 
> > > One thing that might be broken (I havn't
> verified
> > > this yet): I think my
> > > "install.sh" ITU install script needs a small
> update
> > > for current
> > > opensolaris, now that the multiboot binary is
> gone
> > > and grub directly
> > > loads the kernel (the new directboot feature,
> added
> > > when xen / xvm was
> > > integrated).  I think this breaks the
> is_newboot()
> > > function that I'm
> > > using in "install.sh":
> > > 
> > > #
> > > # Detect a "newboot" target OS.
> > > #
> > > is_newboot() {
> > >         [ -f $basedir/platform/i86pc/multiboot ]
> ||
> > > return 1
> > >         [ -d $basedir/boot/grub ] || return 1
> > >         return 0
> > > }
> > > 
> > > 
> > > > I did not understand bef_name and
> real_modepath
> 
=== 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
[email protected]
http://mail.opensolaris.org/mailman/listinfo/driver-discuss

Reply via email to