How to get very old 3c905b with iPXE to work?

[hegi]

Hi NiKiZe,
thank you for your reply.

(2017-09-11 21:38)NiKiZe Wrote:  I would suggest that you first build for example 10b79055.iso and test that (if PCIID is correct)
And when you have done that and confirmed it working you could start experimenting with rom burning.

OK, then we do it in these two steps.

What I want do to is to use the NIC to Boot the Box as a LTSP client. The filename is handed out by DHCP, the the kernel by TFTP.

(2017-09-11 21:38)NiKiZe Wrote:  Please provide the exact make command you used to build your rom.

Sure.
So I did "Generating iPXE build image version 9720f" as "Standard build" on rom-o-matic.eu as ".ISO bootable image", which then in turn is stored on an USB-Stick using dd. The embedded script was specified as follows, based on the web-examples:

Code:

#!ipxe

:retry_dhcp
dhcp && isset ${filename} || goto retry_dhcp
echo Booting from ${filename}
chain ${filename}

... this boots me nicely into my LTSP environment. - Good

However, the only changes from my previous failed ROM Attempt were:

• Advanced Build
• ROM binary (10b79055.rom)
• PCI-Vendor & Device ID 10b7:9055 (according to lspci)
• burning the binary using zprommer to an MX28F1000 EEPROM
• fitting the 3com NIC with the EEPROM
  

(2017-09-11 21:38)NiKiZe Wrote:  The error you get seems to come from libprefix.S, not sure how to debug that. but let's start with the basics above first.

...well I'm also not sure what to do or try .

Since the script is working as expected and there are no other config options on rom-o-matic besides the GIT revision, I see little hope to make this fly as planned.

For the time beeing I rule out the burned EEPROM Chip as source of failure, since it verifys "OK" and it is recognized by the NIC, since it shows an iPXE message upon startup.

Any further ideas?

Thank a lot

Stefan.