Som,
> Juergen,
> Using the prototype file you suggested below,
> i created a new compressed archive and replaced the
> one in 'du/sol_10/i86pc/Product/' created by the
> earlier pkg_drv command using the 32-bit driver module
>
> Is that the way to go?
Sounds ok.
> DU diskette image did contain
> both the modules in the resp paths(/kernel/drv and
> /kernel/drv/amd64)
>
> I began installation ,my target was recognized
If you see that the installer offers a new disk target
that wasn't present when you didn't use the additional
drivers from the ITU media, the kernel appears to use
your new ITU driver just fine...
> and i
> selected the disk/partitions to create , Installation
> began,however now the progress bar is stuck at 3% at
> the point where it says
> '( Creating and checking filesystems) '
Hmm, which installation method did you choose?
The one that starts the X11 server (Interactive Installtion /
Desktop session)?
I'd try the "Interactive Installation (Console)" method
first, with kmdb loaded (edit the grub boot menu entry,
pass option "-k" to the kernel). The console installation
and kmdb allows you to see kernel panic messages
or other kernel error / warning messages.
Note also that the installation kernel is running without
swap space until the target disk for installation gets
partitioned and there is swap space on that disk (IIRC);
at the same time lots of stuff is installed to the root fs
ramdisk (JAVA & X11 server), which sometimes results in a
hung system, because the installation kernel is running out
of free pysical memory (systems with 512MB or less of
physical memory seem to be affected).
> Im guessing this must be the point where 64bit kernel
> is loaded ? How do i know for sure that it has picked
> the right module?
Hmm, you could try to boot the installation kernel with
kmdb, using kernel boot argument "-k", and when it hangs
break into the debugger using "F1-a" and poke around in
the kernel with the kernel debugger:
::modinfo
Should show that your ITU driver is loaded
::prtconf
Should show the device tree, including a node using your ITU device driver
::pstree
Process listing
... etc
> Thanks
> Som
>
>
> --- Juergen Keil <[EMAIL PROTECTED]> wrote:
>
> > Som,
> >
> > > 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?
> >
> > Yes, both 32- and 64-bit kernel modules should be
> > put into a
> > single package.
> >
> > The 64-bit driver will use it's own "amd64"
> > subdirectory for the
> > driver, so this doesn't conflict with the 32-bit
> > driver.
> >
> > The prototype file for the package should look
> > similar to this
> > (where I'm installing two kernel modules "ni" and
> > "dp8390"
> > to /kernel/drv/, both 32- and 64-bit):
> >
> > i pkginfo
> > i postinstall
> > i preremove
> > i copyright
> > d none /kernel ? ? ?
> > d none /kernel/drv ? ? ?
> > f none /kernel/drv/ni=ni 0755 root sys
> > f none /kernel/drv/dp8390=dp8390 0755 root sys
> > f none /kernel/drv/amd64/ni=amd64/ni 0755 root sys
> > f none /kernel/drv/amd64/dp8390=amd64/dp8390 0755
> > root sys
> >
> >
> >
> > The 32-bit Solaris kernel will pick up the 32-bit
> > driver
> > binary from /kernel/drv/{modulename}, and when you
> > boot
> > 64-bit, /kernel/drv/amd64/{modulename} will be used.
> >
> >
> > Not sure how to get the desired result with pkg_drv,
> > though...
> >
> >
>
>
>
>
________________________________________________________________________________
____
> 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
