Recent changes to bugs

set / config command does not work

SwTester — Thu, 08 May 2008 23:56:10 -0000

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. :-(

DHCP issues

Anonymous — Sun, 09 Dec 2007 00:11:24 -0000

I'm having an issue with the most current gpxe source.

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)"

Below is an output of the log file from the DHCP Turbo server. The same entries appear when using either rom or pxe.

Some help with this would be great. Thanks, Rob

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.
debug: Sun Dec 09 11:28:56 2007 Ignoring duplicate discover from device 00-00-0C-29-6F-A2-14.
debug: Sun Dec 09 11:28:56 2007 The server is dropping a datagram.
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.
debug: Sun Dec 09 11:28:56 2007 Ignoring duplicate discover from device 00-00-0C-29-6F-A2-14.
debug: Sun Dec 09 11:28:56 2007 The server is dropping a datagram.

cxz

Anonymous — Mon, 19 Nov 2007 20:33:21 -0000

czxczxcz

p910nd sometimes hangs after connection

Anonymous — Tue, 24 Jul 2007 06:08:47 -0000

p910nd version 0.9
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

compile time error when using DHCP_USER_CLASS

Anonymous — Sun, 01 Apr 2007 17:02:40 -0000

from: georg@ziborski.net

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
core/nic.c:107: warning: initialization makes integer from pointer without a cast
core/nic.c:107: initializer element is not computable at load time
core/nic.c:107: (near initialization for `dhcpdiscover[24]')
core/nic.c:165: warning: initialization makes integer from pointer without a cast
core/nic.c:165: initializer element is not computable at load time
core/nic.c:165: (near initialization for `dhcprequest[36]')
make: *** [bin/nic.o] Error 1
make: Leaving directory `/tmp/ROMwJ72lZ'

Fix for e1000-82541pi

Xavier Hienne — Fri, 23 Feb 2007 13:55:47 -0000

Hello,

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".

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.

Here is a patch that solved the problem.

DOUT

Anonymous — Wed, 09 Aug 2006 11:17:09 -0000

DL10038D NOT SUPPORTIN RTL8139 DIRVER

mknbi fix for compilation with gcc4

Anonymous — Fri, 19 May 2006 10:41:21 -0000

mknbi-1.4.4 has conflicting declaration of a variable
as extern in header and static in source file.
The doesn't work with gcc4 and I cannot imagine how
it was supposed to work earlier (probably gcc
ignoring the static...).

I think the rather trivial patch does no harm, but
please judge for yourself.

Greetings,

Thomas.

PS: If you have questions, please contact me at
thomas-forum@orgis.org

driver for ENL832-TX-ICNT

Eduardo Soares — Wed, 03 May 2006 19:39:54 -0000

I need this driver to use with LTSP.
There is no driver for ENV-TX-ICNT on rom-o-matic.net
I downloaded the source of etherboot but not know C and
I cant make the driver.
I guess the sundance driver can be used.
The vendor is 0x13f0 and card is 0x0200 (the sundance
driver is 0x0201)
The link for more information about the card is
http://www.encore-usa.com/product.php?id=5&lang
There is an attach with the source of the driver that
came with the card.

NEWS: Suggestions for the etherboot User Manual

Borg Number One — Mon, 21 Nov 2005 22:46:18 -0000

Dear Reader.

Because I have some news/suggestions for the etherboot
users manual, I wrote to the primary author: Ken Yap.

Here is the answer:

Hello Borg,

Thanks for you contribution. I am not involved in
Etherboot anymore but
I'm sure that if you posted your contribution to the
Sourceforge web
site, under the Bug Tracker forum, it will be picked up and
incorporated into future versions.

You could also email your comments to the Etherboot
user list.

Cheers, Ken

--- "Borg No. One" <borg_no.one@gmx.net> wrote:

> Hi.
>
> Reffering to this:
>
>
http://etherboot.sourceforge.net/doc/html/userman/x302.html
>
> -->
> Hardware issues
> ---------------
> Finally some recent motherboard have flash BIOSes
which contain space
> where
> an extension BIOS such as Etherboot can be inserted.
> The Phoenix Award BIOSes can be modified using a
program called
> cbrom.exe.
> Or do a Web search for it. No success has been
reported for AMI
> BIOSes.
> Dirk von Suchodoletz maintains a list of successes
and failures here.
>
>
> ...and further "ethorboot<-->BIOS" related stuff,
> I would like to inform you, that I am able to even modify
> + new AMIBIOS8 files
> + Award Medallion BIOS
> + Phoenix Award BIOS.
> + ...
>
>
> It would be great if you could mention
> + my homepage: "http://bnobtc.pix-art.com"
> + my service to help other users who want to add
etherboot roms to
> different
> and new BIOS-FLASHRoms.

In conclusion:

It would be great, if following (or similar phrases)...:

"If you have troubles to add etherboot ROMs to new
Award / AMI / Phoenix BIOS files,
then just check the BNOBTC - [ BIOS Tool Collection ]
or ask the author to get help in adding an etherboot
ROM to your BIOS file.
http://bnobtc.pix-art.com"

...could be added here:
http://etherboot.sourceforge.net/doc/html/userman/x302.html