Re: Debugging Multia boot problems: take one
Steve Langasek wrote:
>On Fri, Feb 17, 2006 at 05:30:17PM -0500, Jay Estabrook wrote:
>>On Fri, Feb 17, 2006 at 01:37:15PM -0800, Steve Langasek wrote:
>>>Yes, MOP != dhcp. You'll need to configure SRM to use dhcp as the boot
>>>protocol; IIRC the option is something like "set ewa0_protocol bootp", but
>>>you may want to check an SRM manual to confirm this (or poke at the
>>>variables in SRM until you find the right one, like I did :).
>>VERY close, Steve; it should be:
>> >>> set ewa0_protocols bootp # note the "s
Ahh, that makes all the difference. Someone should change the SRM
How-to, because that has "protocol", I just checked again to make sure.
And that didn't work. Now I get a whole different response from SRM, it
starts the bootp process, gives lots of messages, gets an IP number from
the server, etc. And, also, my intel box is now showing the request and
answer in the logs.
Unfortunately, the boot.img I got from debian doesn't seem to work
either. It is downloading it, but then it quits with "bootstrap failure"
and trys again. You're right, I don't have to tell it which file, dhcp
does that okay. So I think the problem must be the boot.img.
Is there another one I could download -- looking at the debian
site, there didn't seem to be any older ones. I also tried to do "boot
ewa0 -fi srm.exe" and it can't boot that either, but the srm.exe is just
the one from the firmware upgrade floppy, probably not bootable. The
howto gives a url to download bootable srm upgrades, but that url is
dead. Anyone know where to get them?
I guess I can try building a new boot.img if there isn't one
available. Hmm, looking at Jay's post again, I see that needs to be done
during a kernel build, which won't work, since I have no room on my
multia for the source. Maybe I can do an nfs mount and do it.