Aquileo | Recent changes to bugshttps://sourceforge.net/p/etherboot/bugs/2008-05-08T23:56:10ZRecent changes to bugsAquileo | set / config command does not work2008-05-08T23:56:10Z2008-05-08T23:56:10ZSwTesterhttps://sourceforge.net/u/swtester/https://sourceforge.netf8df2a60261d67a47defdfa7914b745769c5cdf6<div class="markdown_content"><p>Hello, I would like to boot the workstation using iSCSI. Unfortunately it seems that gPXE 0.9.3 Image Generator (ROM-o-matic.net) does not create working ROM image as I can't set / config any parameters (No non-volatile option storage available). Tested on various network cards / various workstations with the same result. :-( </p></div>Aquileo | DHCP issues2007-12-09T00:11:24Z2007-12-09T00:11:24ZAnonymoushttps://sourceforge.net/u/userid-None/https://sourceforge.net5dff24a0422c84b401428de4dcccfa2f42ef6864<div class="markdown_content"><p>I'm having an issue with the most current gpxe source.</p>
<p>I use vmware server for iscsi boot testing. I have been building either the e1000.rom or undi.pxe. Using gpxe source from about 4 weeks ago works fine. In the current source if i build either e1000.rom or undi.pxe it loads up fine but times out after a short period with "Connection timed out (0x4c106035)"</p>
<p>Below is an output of the log file from the DHCP Turbo server. The same entries appear when using either rom or pxe.</p>
<p>Some help with this would be great. Thanks, Rob</p>
<p>verbose: Sun Dec 09 11:28:56 2007 The frontend received packet: 01-01-06-00-29-6F-A2-14-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-0C-29-6F-A2-14-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-63-82-53-63-61-11-00-56-4D-2A-1D-7A-C0-7C-45-BA-F4-3D-61-65-6F-A2-14-3D-07-00-00-0C-29-6F-A2-14-AF-22-B1-05-01-80-86-10-0F-13-01-01-17-01-01-15-01-01-11-01-01-12-01-01-18-01-01-19-01-01-21-01-01-10-01-01-32-04-C0-A8-0A-35-36-04-C0-A8-0A-01-5E-03-01-02-01-5D-02-00-00-3C-20-50-58-45-43-6C-69-65-6E-74-3A-41-72-63-68-3A-30-30-30-30-30-3A-55-4E-44-49-3A-30-30-32-30-30-31-39-02-05-DC-37-0D-01-03-06-07-0C-0F-11-2B-3C-42-43-AF-CB-35-01-01-FF.<br />
debug: Sun Dec 09 11:28:56 2007 Ignoring duplicate discover from device 00-00-0C-29-6F-A2-14.<br />
debug: Sun Dec 09 11:28:56 2007 The server is dropping a datagram.<br />
verbose: Sun Dec 09 11:28:56 2007 The frontend received packet: 01-01-06-00-29-6F-A2-14-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-0C-29-6F-A2-14-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-63-82-53-63-61-11-00-56-4D-2A-1D-7A-C0-7C-45-BA-F4-3D-61-65-6F-A2-14-3D-07-00-00-0C-29-6F-A2-14-AF-22-B1-05-01-80-86-10-0F-13-01-01-17-01-01-15-01-01-11-01-01-12-01-01-18-01-01-19-01-01-21-01-01-10-01-01-32-04-C0-A8-0A-35-36-04-C0-A8-0A-01-5E-03-01-02-01-5D-02-00-00-3C-20-50-58-45-43-6C-69-65-6E-74-3A-41-72-63-68-3A-30-30-30-30-30-3A-55-4E-44-49-3A-30-30-32-30-30-31-39-02-05-DC-37-0D-01-03-06-07-0C-0F-11-2B-3C-42-43-AF-CB-35-01-01-FF.<br />
debug: Sun Dec 09 11:28:56 2007 Ignoring duplicate discover from device 00-00-0C-29-6F-A2-14.<br />
debug: Sun Dec 09 11:28:56 2007 The server is dropping a datagram.</p></div>Aquileo | cxz2007-11-19T20:33:21Z2007-11-19T20:33:21ZAnonymoushttps://sourceforge.net/u/userid-None/https://sourceforge.net4cbdf47a4b419ad63ecd20d938083cd73306606d<div class="markdown_content"><p>czxczxcz</p></div>Aquileo | p910nd sometimes hangs after connection2007-07-24T06:08:47Z2007-07-24T06:08:47ZAnonymoushttps://sourceforge.net/u/userid-None/https://sourceforge.netdc755ef7ff2f3a30024aaee85ef8c2624a53a1dc<div class="markdown_content"><p>p910nd version 0.9<br />
Log says connection established, then the program stops accepting TCP traffic and locks up. Debugging shows that the "f" variable is uninitialized. Initializing f to NULL fixes the problem for me. I'd suggest in server() set f to NULL in the loop just before the while() testing for connection, then fclose(f) after printing that connection. That survives printer disconnection/reconnection better than leaving the file open. -- n2rjt@yahoo.com</p></div>Aquileo | compile time error when using DHCP_USER_CLASS2007-04-01T17:02:40Z2007-04-01T17:02:40ZAnonymoushttps://sourceforge.net/u/userid-None/https://sourceforge.net6cb6a33f95a7fb96dfec1da2de74658594706540<div class="markdown_content"><p>from: georg@ziborski.net</p>
<p>cc -DASK_BOOT=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_FLOPPY -DBOOT_THIRD=BOOT_DISK -DBOOT_INDEX=0 -DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"THINCLI\" -DDHCP_USER_CLASS_LEN=7 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DELF_IMAGE -DPXE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -DCONFIG_ISA -Os -ffreestanding -Wall -W -Wno-format -DPCBIOS -fstrength-reduce -fomit-frame-pointer -march=i386 -falign-jumps=1 -falign-loops=1 -falign-functions=1 -mcpu=i386 -DVERSION_MAJOR=5 -DVERSION_MINOR=4 -DVERSION=\"5.4.3\" -I include -I arch/i386/include -DARCH=i386 -o bin/nic.o -c core/nic.c<br />
core/nic.c:107: warning: initialization makes integer from pointer without a cast<br />
core/nic.c:107: initializer element is not computable at load time<br />
core/nic.c:107: (near initialization for `dhcpdiscover[24]')<br />
core/nic.c:165: warning: initialization makes integer from pointer without a cast<br />
core/nic.c:165: initializer element is not computable at load time<br />
core/nic.c:165: (near initialization for `dhcprequest[36]')<br />
make: *** [bin/nic.o] Error 1<br />
make: Leaving directory `/tmp/ROMwJ72lZ'</p></div>Aquileo | Fix for e1000-82541pi2007-02-23T13:55:47Z2007-02-23T13:55:47ZXavier Hiennehttps://sourceforge.net/u/xhienne/https://sourceforge.nete3f039f4eec73651ba3a2bfd8c82ac26a5444dcb<div class="markdown_content"><p>Hello,</p>
<p>A colleague of mine used rom-o-matic.net to get a zpxe image for his Intel PRO/1000 GT Desktop network card (based on 82541pi chip). The zpxe image was not working, displaying an error message like "Bad MAC type".</p>
<p>It looked like to me that 82541pi support was incomplete : 82541pi appears in the rom-o-matic/etherboot device list but the e1000_set_mac_type function fails to detect it (code not implemented) and returns -E1000_ERR_MAC_TYPE.</p>
<p>Here is a patch that solved the problem.</p></div>Aquileo | DOUT2006-08-09T11:17:09Z2006-08-09T11:17:09ZAnonymoushttps://sourceforge.net/u/userid-None/https://sourceforge.net3576e3a57e2018c74cfe2836d601c8ef9f62b8bf<div class="markdown_content"><p>DL10038D NOT SUPPORTIN RTL8139 DIRVER</p></div>Aquileo | mknbi fix for compilation with gcc42006-05-19T10:41:21Z2006-05-19T10:41:21ZAnonymoushttps://sourceforge.net/u/userid-None/https://sourceforge.net29ece9ebbae829af77c1208d0fdf2476239de1b4<div class="markdown_content"><p>mknbi-1.4.4 has conflicting declaration of a variable <br />
as extern in header and static in source file.<br />
The doesn't work with gcc4 and I cannot imagine how <br />
it was supposed to work earlier (probably gcc <br />
ignoring the static...).</p>
<p>I think the rather trivial patch does no harm, but <br />
please judge for yourself.</p>
<p>Greetings,</p>
<p>Thomas.</p>
<p>PS: If you have questions, please contact me at <br />
thomas-forum@orgis.org</p></div>Aquileo | driver for ENL832-TX-ICNT2006-05-03T19:39:54Z2006-05-03T19:39:54ZEduardo Soareshttps://sourceforge.net/u/edurbs/https://sourceforge.net93c10f12448bdbaacadc7eaf815b5d840668b0ab<div class="markdown_content"><p>I need this driver to use with LTSP.<br />
There is no driver for ENV-TX-ICNT on rom-o-matic.net <br />
I downloaded the source of etherboot but not know C and<br />
I cant make the driver.<br />
I guess the sundance driver can be used.<br />
The vendor is 0x13f0 and card is 0x0200 (the sundance<br />
driver is 0x0201)<br />
The link for more information about the card is<br />
<a href="http://www.encore-usa.com/product.php?id=5&lang" rel="nofollow">http://www.encore-usa.com/product.php?id=5&lang</a><br />
There is an attach with the source of the driver that<br />
came with the card.</p></div>Aquileo | NEWS: Suggestions for the etherboot User Manual2005-11-21T22:46:18Z2005-11-21T22:46:18ZBorg Number Onehttps://sourceforge.net/u/userid-602797/https://sourceforge.net0792f28c489b23edd7208625542600c22a0d8625<div class="markdown_content"><p>Dear Reader.</p>
<p>Because I have some news/suggestions for the etherboot<br />
users manual, I wrote to the primary author: Ken Yap.</p>
<p>Here is the answer:</p>
<p>Hello Borg,</p>
<p>Thanks for you contribution. I am not involved in<br />
Etherboot anymore but<br />
I'm sure that if you posted your contribution to the<br />
Sourceforge web<br />
site, under the Bug Tracker forum, it will be picked up and<br />
incorporated into future versions.</p>
<p>You could also email your comments to the Etherboot<br />
user list.</p>
<p>Cheers, Ken</p>
<p>--- "Borg No. One" <borg_no.one@gmx.net> wrote:</p>
<p>> Hi.<br />
><br />
> Reffering to this:<br />
><br />
><br />
<a href="http://etherboot.sourceforge.net/doc/html/userman/x302.html">http://etherboot.sourceforge.net/doc/html/userman/x302.html</a><br />
><br />
> --><br />
> Hardware issues<br />
> ---------------<br />
> Finally some recent motherboard have flash BIOSes<br />
which contain space<br />
> where<br />
> an extension BIOS such as Etherboot can be inserted.<br />
> The Phoenix Award BIOSes can be modified using a<br />
program called<br />
> cbrom.exe.<br />
> Or do a Web search for it. No success has been<br />
reported for AMI<br />
> BIOSes.<br />
> Dirk von Suchodoletz maintains a list of successes<br />
and failures here.<br />
><br />
><br />
> ...and further "ethorboot<-->BIOS" related stuff,<br />
> I would like to inform you, that I am able to even modify<br />
> + new AMIBIOS8 files<br />
> + Award Medallion BIOS<br />
> + Phoenix Award BIOS.<br />
> + ...<br />
><br />
><br />
> It would be great if you could mention<br />
> + my homepage: "http://bnobtc.pix-art.com"<br />
> + my service to help other users who want to add<br />
etherboot roms to<br />
> different<br />
> and new BIOS-FLASHRoms.</p>
<p>In conclusion:</p>
<p>It would be great, if following (or similar phrases)...:</p>
<p>"If you have troubles to add etherboot ROMs to new<br />
Award / AMI / Phoenix BIOS files,<br />
then just check the BNOBTC - [ BIOS Tool Collection ]<br />
or ask the author to get help in adding an etherboot<br />
ROM to your BIOS file.<br />
<a href="http://bnobtc.pix-art.com" rel="nofollow">http://bnobtc.pix-art.com</a>"</p>
<p>...could be added here:<br />
<a href="http://etherboot.sourceforge.net/doc/html/userman/x302.html">http://etherboot.sourceforge.net/doc/html/userman/x302.html</a></p></div>