Hi, I have an old IBM PL workstation with one of these ethernet cards (onboard eepro100 + bootrom that supports PXE). After trying for a few long hours of research I finally found how to solve the problem.
Basically you need to do this: go to http://www.rom-o-matic.com/5.1.3/ - THIS IS THE ONLY VERSION THAT WORKS FOR ME select the eepro100 card and ROM output format (I use .lzpxe) Press the Configure Button and select the following options: ALLOW_ONLY_ENCAPSULATED Ignore Etherboot-specific options that are not within the Etherboot encapsulated options field. This option should be enabled unless you have a legacy DHCP server configuration from the bad old days before the use of encapsulated Etherboot options. AND on the: DEFAULT_BOOTFILE: Define a default bootfile for the case where your DHCP server does not provide the information. Example: -DDEFAULT_BOOTFILE="tftp:///tftpboot/kernel"; If you do not specify this option, then DHCP offers that do not specify bootfiles will be ignored. section write the path to your kernel file (don't use /tftpboot/ if your thftpserver is started in secure mode: -s : eg: tftp:///lts/vmlinuz-2.4.9-ltsp-lpp-5) get the image and then set your dhcpd.conf file, smth like this: host ws00X { hardware ethernet 00:60:94:05:3F:E1; #the ARP address fixed-address 192.168.0.2; #local IP if substring (option vendor-class-identifier, 0, 9) = "PXEClient" { filename "/lts/eb-5.1.3-eepro100.lzpxe"; #the one you've got from rom-o-matic } else if substring (option vendor-class-identifier, 0, 9) = "Etherboot" { filename "/lts/vmlinuz-2.4.9-ltsp-lpp-5"; #neat kernel option vendor-encapsulated-options 3c:09:45:74:68:65:72:62:6f:6f:74:ff; ## as they are, they're not MAC related } } restart dhcpd and then it should work, when it boots it even posts a message like activating tftp lockup bug workaround:) Hope this will solve your problem, I've met a few people who had the same problem and it worked perfectly for them. For other problems related with the eepro100 card (there are some other bugs) you should visit Donald Becker's web page: http://www.scyld.com/network/ and download and compile utils that will help you solve those problems. I even thought of writing a little HOWTO about this little workaround to help other people not feel the frustration that I felt when I experienced this annoying problem. Should I? I don't know, maybe it's kind of insignifiant for the community. Best regards, Dragosh M. On Tue, 2003-02-11 at 17:58, Peter Pankonin wrote: > I have a client with a number of HP Vectra P2 350 boxes. I'm having trouble > finding a PXE boot ROM that works with the NIC. It appears to be a 82559 > chip. I've tried these: > > eb-5.0.8-82559er > eb-5.0.8-eepro100 > eb-5.1.5-82559er > eb-5.1.5-eepro100k > eb-5.1.5-eepro > > They either hang at "searching for server (DHCP)" or reboot the client halfway > through the boot process. > > I did find that an eb-5.0.5-eepro100 boot floppy works with this NIC. Does > anyone have any idea why the newer boot ROMs don't? I tried a 3c905 in the > box and it works fine. Thanks. -- I/O error while opening .signature file ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _____________________________________________________________________ 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
