Re: [Etherboot-developers] Boot Eprom
Brought to you by:
marty_connor,
stefanhajnoczi
|
From: Markus G. <ma...@gu...> - 2001-06-30 20:06:51
|
27512 is a 64kB EPROM. It should work fine with a 16kB image. It is backwards compatible with the 27256 (which is 32kB) and 27128 (which is 16kB), but if you configured your NIC for 16kB mode, it is not clear whether it will select the first, second, third or fourth 16kB segment (or maybe randomly pick one each time you access the ROM); thus, you might want to burn the same image into all four segments and then configure the NIC for 16kB. Alternatively, if you configured the NIC for 64kB mode, then you only need to burn the image into the first part of the EPROM and you leave everthing else blank. Many cards require that you enable the ROM using some card-specific utility. I am not sure, if this is the case for the two NICs that you use. Where did you download the images from? http://www.rom-o-matic/ ? There used to be a bug in very old PCI BIOSs that would refuse to recognize etherboot images. I am not sure if that is still the case (I think, at one time, there was discussion of putting a workaround into etherboot). Check the mailing list archive for more information. If you have one of these old and buggy BIOS version, then the archive might have instructions on how to modify etherboot to make things work. Markus BM wrote: > Have anybody know how programme eprom's? > > I have an Eprom Programmer & downloaded boot image file for my ethernet > cards.(3C905B-TX-NM & RTL8139). > > I write image file (16Kb) to Eprom 27C128 for 8139. > > But 8139 could'nt boot pc client.Also I write 29C512 for 3C905 but it > doesn't boot too.Is there any tricks for writing Eprom's?. > > I write the image file from adres 0000.Is it true? or is there another > thing so I don't know? > > Please help me if any one know this... -- Markus Gutschke Resonate, Inc. 3637 Fillmore Street #106 385 Moffett Park Drive San Francisco, CA 94123-1600 Sunnyvale, CA 94089 +1-415-567-8449 +1-408-548-5528 ma...@gu... mgu...@re... |