<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body text="#000000" bgcolor="#ffffff">
<tt>Marcin Kosieradzki wrote:</tt>
<blockquote type="cite" cite="mid:8c161bfb0911190254i5ea5edc7m71cb012535c61c68@mail.gmail.com">
<title>Re: [gPXE] gPXE,nc380t (bcm5706 / bnx2) sanboot iscsi
connectivity and BIOS issues</title>
<!-- Converted from text/plain format -->
<p><tt><font size="2">On the machine with an old revision S5000PSL
(with builtin VGA) (the<br>
one I was describing in previous email): if I didn't<br>
press ctrl+B there was a "Press F2 to enter SETUP" message displayed and<br>
sometimes after pressing F2 it was changing into "Entering SETUP", but<br>
nothing happened.<br>
</font></tt></p>
</blockquote>
<tt>There are two Control-B prompts from gPXE, one during POST and
another when it's gPXE's turn to boot. In general, it's best to avoid
the POST-time prompt, since gPXE will get going before POST has
completed, and we've seen scenarios where the memory map is
incomplete. Also, other devices might not have initialized, such as a
RAID controller providing an INT 0x13 hook for HDD access.<br>
</tt>
<blockquote type="cite" cite="mid:8c161bfb0911190254i5ea5edc7m71cb012535c61c68@mail.gmail.com">
<p><tt><font size="2">On the machine with a newer revision S5000PSL
(with builtin VGA),<br>
after not pressing ctrl+B in gpxe there was<br>
initialization message of second chipset on my NC380T (which I didn't<br>
turn off) displayed,<br>
something like "Press F1 to skip iSCSI". And then "Press F2 to enter
SETUP"....<br>
</font></tt></p>
</blockquote>
<tt>It's possible to run out of option ROM space by having too many
option ROMs. Removing cards or possibly disabling them in BIOS setup
might help.<br>
</tt>
<blockquote type="cite" cite="mid:8c161bfb0911190254i5ea5edc7m71cb012535c61c68@mail.gmail.com">
<p><tt><font size="2">On the third machine with an old recision
S5000VSA (with PCI VGA card<br>
and builtin VGA card disabled):<br>
If I pressed ctrl+B machine was immediately rebooted.<br>
If I didn't there was "press F2 to enter setup" and machine was<br>
rebooted after few seconds.<br>
</font></tt></p>
</blockquote>
<tt>I've seen a gPXE ROM recently rebooting a particular model I have
here, much as you've described. I'll try to find the time to look into
it.<br>
</tt>
<blockquote type="cite" cite="mid:8c161bfb0911190254i5ea5edc7m71cb012535c61c68@mail.gmail.com">
<p><tt><font size="2">I'm planning to buy Intel PRO/1000 ET NIC, put
it in lower number<br>
PCI-e port, boot OS from iSCSI, disable mba on<br>
both chipsets on NC380T and then continue to solve first issue, but<br>
this time probably running gPXE from USB stick.</font></tt></p>
</blockquote>
<tt>Note that recently I tried to SAN-boot an HP ProLiant ML370 G5
computer, but the Windows had a Blue Screen of Death. Quite familiar
with SAN-booting, this suggests to me that the Windows NIC drivers
might not be capable of completing the SAN-boot; perhaps they rely on
user-land components or perhaps there's a filter driver that needs to
be found and enabled at boot-time. I don't know if this relates to
your situation at all, but wanted to share.<br>
<br>
Good luck!<br>
<br>
- Shao Miller<br>
</tt>
</body>
</html>