I think you are on the right track, Seen a similar case with pxelinux. Add a -solaris option to that line
I.e. append -solaris multiboot-solaris-10u7-x86 kernel/unix -B install_media=$ip_addr........ The installer does not pass the dhcp info to the solaris installer. Hence the server boots from the network and then falls off the network in the solaris installer portion. Sent from mobile device On Nov 4, 2009, at 11:45 AM, Rick Miller <vmiller at verisign.com> wrote: What is the menu.lst entry on the linux tftp server for this solaris host? There is a install_debug flag you can pass to it as well. Sent from mobile device There is no menu.lst. The boot loader was written in-house (not my choice), and I believe it is loosely based on Syslinux. However, the boot loader is calling up the inetboot from the Solaris 10 ISO should be passing it multiple values, including install_media, install_config, etc... Here is the relevant portion of the boot options... append: multiboot-solaris-10u7-x86 kernel/unix -B install_media=$ip_addr:$dir,install_config=$ip_addr:$dir,sysid_config=$ip_addr:$dir,install_boot=$ip_addr:$dir - install nowin --- x86.miniroot multiboot-solaris-10u7-x86 is the inetboot file from the s10u7 ISO. $ip_addr is the IP address to the install server and $dir is the NFS exported directory to look in. The portion When the OS errors and I run /sbin/getbootargs, all I see is '- install nowin'. So, it doesn't display all the -B boot args. Therefore, I am assuming that the -B boot args should get passed to inetboot and ignore everything following the first '-'. Is this a correct assumption and if so, how do I determine if the inetboot is really interpreting those? Am I on the right trail or am I completely off base here? -- This message posted from opensolaris.org _______________________________________________ install-discuss mailing list install-discuss at opensolaris.org http://mail.opensolaris.org/mailman/listinfo/install-discuss
