Re: Jumpstart x86 - not accepting -B insall_media=<NFS MOUNT>

"RobH" <robheilman@xxxxxxxxx> writes:

cd /var/miniroot
/boot/solaris/bin/root_archive unpack ./x86.miniroot ./unpacked
pkgadd -d . -R /var/miniroot/unpacked YUKONXsol
/boot/solaris/bin/root_archive pack ./x86.miniroot ./unpacked

Can you verify that the proper driver aliases do exist in the
miniroot?

(You said that ifconfig on yukon0 worked?)

I have the YUKON device set in the BIOS as the primary boot option.
Only thing I can think of is that the chipset is dual ported and
perhaps the installer is seeing it differently than the bois sees it.
I have dual the dual port option in the yukonx.conf file turned off as
it is by default.

Is there a command available in the miniroot that will determine what
it thought was the boot device? I assume that it is determine by
compairing the PCI ID's since that would remain static through all
"run-levels".

I have no idea; it does print the ethernet pathname early but it
does not list the boot device (the kernel "boots" from ramdisk)

FYI - I can get one of these blades up and running using a emulated USB
CDROM but it is painfully slow. (ISO, through SAMBA, emulated ATAPI
CDROM over USB - "feature" of my remote IP console) Can I collect more
info on the hardware from the installed machine to help diagnose the
jumpstart issue? If so, please let me know what you would like to see.

The information is printed by the command:

/sbin/netstrategy which will print something like:

ufs nge0 dhcp

Also check the netdev_path[] kernel variable; it should contain the
network device path which the kernel should map to the interface name.

Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.
.