Yep, I tested it again
For me:
'kernel .../multiboot kernel/unix -B ...' gives me an interactive
install where I have to choose 'Custom Jumpstart' from a menu.
'kernel .../multiboot kernel/unix - install -B ...' gives me an "Error
20" message about needing to load the multiboot kernel before any modules.
'kernel .../multiboot kernel/unix -v - install -B ...' gives the proper
behavior, albeit with verbose output from the kernel during boot.
I didn't try:
'kernel .../multiboot kernel/unix -v install -B ...' but I wouldn't be
surprised to see it give the menu also.
There's got to be abug somehwere in the argument processing. I haven't
unpacked the minitroot to debug further, but I did try to log a support
request (in order to open a bug) on SunSolve, only to find out that
there's something wrong with our contract. I'll have to straighten that
out on Monday.
-Kyle
Kyle McDonald wrote:
> Sean Alderman wrote:
>
>> Lori,
>> Thanks for the tip. I've discovered a message that explains everything...
>>
>> The Kernel is ignoring all the arguments. There is a message just before
>> the screen print of the Solaris Kernel blah blah (32 bit) etc. which shows
>> that the it is ignoring kernel arguments and lists all the grub arguments
>> after the kernel/unix part. Not sure why that would be, here again is my
>> grub menu.1st
>>
>>
>>
> Sean,
>
> I've just started to try to jumpstart u6 now also, and I'm not sure I'm
> seeing exactly what you are, but I'm also seeing things that are
> differrent from what I'm used to.
>
> I cloned my s10u5 menu.lst (which admittedly hasn't been tested in a
> while,) and edited it for u6 (mainly 's/u5/u6/g'). This left the kernel
> line like:
>
> kernel /Sol/s10/u6_X86/multiboot kernel/unix - install -B ...
>
> either GRUB or the multiboot program didn't like the '- install', and
> printed out warnings about how the 'multiboot kernel must be loaded
> before modules'. At the time I didn't know it was the '- install' that
> was making the problem, so I went and ran the following to see what kind
> of menu.lst it would make:
>
> ./add_install_client -d -e 00:01:02:03:04:05 -c 1.2.3.4:/ex/Inst -p
> 1.2.3.4:/ex/Inst/SysID/Def i86pc
>
> With the exception of the serial port parameters, the only difference in
> the menu.lst.000102030405 file and mine was the '- install'.
>
> I copied that menu.lst, added the serial console parameters, and it
> booted fine, but it prompts me with the same menu you are getting.
>
> I then added in '-v - install' hoping I coudl see more of what was going
> on. It worked - well it skipped the first menu and went striaght to
> 'Custom Jumpstart' anyway, it did stop and ask me about my terminal
> though. I'll have to figure that out next.
>
> I noticed in one of your menu.lst files you had the -v, but it was '-v
> install' not '-v - install'. Have you tried puting the ' - ' in there?
>
> I'm going to have to try it again now with the '-v' removed (which
> should make it identical to the hand-made menu.lst I started with but
> we'll see...)
>
>
>> The other slightly interesting thing I noticed is that when I modify the
>> /tftpboot/<mac>.menu.lst file - let's say to change the grub label - I boot
>> the target machine and it seems to be pulling the grub menu from somewhere
>> else, though it has all the right kernel arguments...it just doesn't reflect
>> my change to the label. Now please recall that I used all the scripts to
>> build the install server and install clients that are provided on the U6
>> media. So I'm slightly confused as to why the grub menu would not be
>> loading from the /tftpboot directory that the install server setup script
>> created.
>>
>>
>>
> That is strange, I don't know what could be causing that. Try hitting
> 'c' to get to the grub command prompt, and then use the configfile
> command to load the menu.lst you know is right (or the one you want to
> test.)
>
> For /tftpboot/test.menu.lst it would be:
>
> configfile (nd)/test.menu.lst
>
> I'll let you know if I stumble accross anything else.
>
> -Kyle
>
>
>> P.S. salderma = alderhos, this forum account uses my personal email the
>> other is for work.
>>
>>
>
> _______________________________________________
> install-discuss mailing list
> install-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/install-discuss
>
