Hello Kamran,

> 3) I am trying to write the boot roms. I have RTL8139 cards (from Planet
> company). the pci id is 10ec for these cards. I have downloaded
10ec:8139 probably. That board is officially supported by etherboot,
since ages I believe. I had one before my 8169 arrived, and it did
it's job properly.

> eb-x.y.z.lzrom from the rom-o-matic site. I have written that image on a
> boot-rom and placed that rom on this card. But when I try to boot from
> the network card it does not. It doesn't even detect the card at all and
> goes directly to floppy drive asking for boot floppy. I have tested this
> on two computers.

Have you tested booting from a floppy with a .lzdsk image from
rom-o-matic?


>         a) a P-1 having an intel mother board which has proven to be a breeze
> [...]
> know what it is!) but no responce. The card doesn't get detected at all.

>         b) A P-1 VX-PRO 2 mother board which has already given me many problems
> [...]
> doesn't get detected and again the computer asks for a boot floppy.

> I have tried instructions on the rom-o-matic page to test the rom images
> first but that method does not work. I have downloaded and compiled
> etherboot package so that I can get boot1a.bin file to attach with the
> rom image but in short that method didn't work at least for the past two
> days.

I don't know of a boot1a.bin file method to test images. My first step
would have been to get a boot floppy as described above. If that does
not work, I'd try another version of etherboot (just to be sure)...
and finally dump that specific piece of hardware. If it *does* boot
from floppy, you should watch out for some piece of diagnostic
software that allows you to enable the boot rom socket on the card
(and probably also allows selection of the ROM address as well) -
www.realtek.com.tw could have software for you.

If that still does not help, please post this question on the
etherboot-users list, as it probably gets specific and people
around there will be more experienced to stuff like that. However, not
having enabled the boot prom socket seems to be something happening
quite often - just inserting does not always help.

What about the network boot option in one of your computers... hmmm...
there is something like an int18 or int19 option in etherboot having
to do with that. I think if using one of those options, the eprom will
be activated as soon as it is scanned, while in second case it would
only be activated by a bios knowing about "network booting". YMMV.

HTH,
 Anselm Martin Hoffmeister
 Stockholm Projekt Computer-Service
 <[EMAIL PROTECTED]>



-------------------------------------------------------
This SF.NET email is sponsored by: eBay
Great deals on office technology -- on eBay now! Click here:
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Reply via email to