etherboot-developers Mailing List for Etherboot (Page 280)
Brought to you by:
marty_connor,
stefanhajnoczi
Menu
▾
▴
etherboot-developers — Discussion of developer issues
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
(10) |
Sep
(3) |
Oct
(10) |
Nov
(47) |
Dec
(20) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(41) |
Feb
(107) |
Mar
(76) |
Apr
(103) |
May
(66) |
Jun
(72) |
Jul
(27) |
Aug
(31) |
Sep
(33) |
Oct
(18) |
Nov
(33) |
Dec
(67) |
| 2002 |
Jan
(25) |
Feb
(62) |
Mar
(79) |
Apr
(74) |
May
(67) |
Jun
(104) |
Jul
(155) |
Aug
(234) |
Sep
(87) |
Oct
(93) |
Nov
(54) |
Dec
(114) |
| 2003 |
Jan
(146) |
Feb
(104) |
Mar
(117) |
Apr
(189) |
May
(96) |
Jun
(40) |
Jul
(133) |
Aug
(136) |
Sep
(113) |
Oct
(142) |
Nov
(99) |
Dec
(185) |
| 2004 |
Jan
(233) |
Feb
(151) |
Mar
(109) |
Apr
(96) |
May
(200) |
Jun
(175) |
Jul
(162) |
Aug
(118) |
Sep
(107) |
Oct
(77) |
Nov
(121) |
Dec
(114) |
| 2005 |
Jan
(201) |
Feb
(271) |
Mar
(113) |
Apr
(119) |
May
(69) |
Jun
(46) |
Jul
(21) |
Aug
(37) |
Sep
(13) |
Oct
(4) |
Nov
(19) |
Dec
(46) |
| 2006 |
Jan
(10) |
Feb
(18) |
Mar
(85) |
Apr
(2) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(10) |
Jul
(20) |
Aug
(9) |
Sep
(11) |
Oct
(4) |
Nov
(1) |
Dec
(40) |
| 2008 |
Jan
(19) |
Feb
(8) |
Mar
(37) |
Apr
(28) |
May
(38) |
Jun
(63) |
Jul
(31) |
Aug
(22) |
Sep
(37) |
Oct
(38) |
Nov
(49) |
Dec
(24) |
| 2009 |
Jan
(48) |
Feb
(51) |
Mar
(80) |
Apr
(55) |
May
(34) |
Jun
(57) |
Jul
(20) |
Aug
(83) |
Sep
(17) |
Oct
(81) |
Nov
(53) |
Dec
(40) |
| 2010 |
Jan
(55) |
Feb
(28) |
Mar
(36) |
Apr
(7) |
May
|
Jun
|
Jul
(7) |
Aug
|
Sep
|
Oct
(1) |
Nov
(3) |
Dec
|
| 2011 |
Jan
(1) |
Feb
|
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(6) |
Oct
|
Nov
(10) |
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Marty C. <md...@th...> - 2001-04-21 22:33:10
|
Greetings fans of Network Booting, I have updated http://rom-o-matic.net/ with a new test version of Etherboot which has a rewritten Tulip driver and incorporates a recent patch to the loader.S code which may help people whose BIOSes were not recognizing their ROMs in earlier development releases. We are now very close to the release of the next production release of Etherboot, version 5.0. So now would be a great time to test the latest production release. Using http://rom-o-matic.net/ you can build a customised Etherboot image in about 5 seconds. For example, to create a floppy bootable image for a tulip or clone card, just select "tulip" from the "NIC/ROM Type" menu, and "Floppy Bootable ROM Image" from the "Output Format" menu, and press "Get ROM". Save the image to disk when prompted. If should be called something like "eb-4.7.24-mc2-tulip.lzdsk". (MIE/Windows users, please read the note on the site about how to work around an MIE bug when downloading images). Now copy your image to a blank formatted floppy with: cat eb-4.7.24-mc2-tulip.lzdsk > /dev/fd0 and try booting a machine with it. If you're using DOS/Windows you can use the RAWRITE program to write the floppy image to a floppy. RAWRITE is usually on Linux installation CDs as well as at the usual Linux distribution sites like Red Hat and Debian's ftp sites. Many Thanks to all the people who have given us (and will give us) feedback on the development versions of Etherboot. Your reward will be a solid new production release. --- Try: http://rom-o-matic.net/ to make Etherboot images instantly. Name: Marty Connor US Mail: Entity Cyber, Inc.; P.O. Box 391827; Cambridge, MA 02139; USA Voice: (617) 491-6935, Fax: (617) 491-7046 Email: md...@th... Web: http://www.thinguin.org/ |
|
From: Ken Y. <ke...@nl...> - 2001-04-21 14:51:37
|
BTW, for those of you who are not aware of it, there is an area on the Etherboot web site that can be used to submit user-written documentation, it's under DocManager from http://sourceforge.net/projects/etherboot So if you have a short how-to on some topic, like flashing BIOSes, or even a long document on something Etherboot related, like how you got it to work on your 1 THz NIC, here is the place to upload it, preferably as HTML. (I'm not sure if you have to register as a Sourceforge user first, but user registration is free anyway.) |
|
From: Ken Y. <ke...@nl...> - 2001-04-20 00:33:43
|
|>Perhaps you might like to analyse why it works and |is there a way to debug etherboot and/or with file is to edit for a |printf? | |>what it tells you about what the BIOS is expecting. |hmm... |there is a USB-bug in this BIOS-Vers. The networkhardware don't works |when USB is enebeld (on Windows and Linux) ?!?! You have to work out, possibly with the help of documentation from the BIOS manufacturer, what mechanism is used to give control to the extension BIOS. From the symptoms, it appears the BIOS is not PnP compliant but it does call the ROM at the +3 entry point when it detects the BIOS, which is legacy (ISA) ROM behaviour. However the BIOS does not appear to boot by calling INT 0x19 after all devices have initialised so even though Etherboot has hooked that interrupt, it isn't getting called. It must have its own startup mechanism. The fact that the USB device seems to disrupt the network booting points to this also. So you have to get more documentation from the mfr and study it. In summary, it's not Etherboot you have to debug, it's the mfr's BIOS. |
|
From: Volker S. <Vol...@da...> - 2001-04-19 08:06:40
|
>Yes, but it's working by accident and the bug will not be propagated >into future versions. it`s a misunderstanding, but i have no more time now >Perhaps you might like to analyse why it works and is there a way to debug etherboot and/or with file is to edit for a printf? >what it tells you about what the BIOS is expecting. hmm... there is a USB-bug in this BIOS-Vers. The networkhardware don't works when USB is enebeld (on Windows and Linux) ?!?! cu volker |
|
From: Ken Y. <ke...@nl...> - 2001-04-19 06:53:40
|
|...but this is not my problem now because ver. 4.7.23 is working. |but it's more important to run with the 82559er Yes, but it's working by accident and the bug will not be propagated into future versions. Perhaps you might like to analyse why it works and what it tells you about what the BIOS is expecting. |
|
From: Volker S. <Vol...@da...> - 2001-04-19 06:49:59
|
>Oh well, this BIOS is too strange for me to deal with now. Ask your >supplier how to boot network cards with this BIOS and if they have any >sample ROM images you can get and look at with src/disrom.pl. auah... ...but this is not my problem now because ver. 4.7.23 is working. but it's more important to run with the 82559er cu volker |
|
From: Ken Y. <ke...@nl...> - 2001-04-19 05:49:12
|
|What Etherboot version did you try? Always mention the version you are |using. Some changes were introduced in 4.7.22: | |+ Peter Kögel contributed patches to the SiS900 driver to make it work |for the SiS640e/SiS730s. | |If you haven't tried this let us know if 4.7.24 works for the 630s. In fact, looking at sis900.c, Peter Kögel made the changes to handle the 630e (although tested on the 730s, he says) and the 640e in the LOG is a typo (my fat fingers). So I think that the most recent version of the driver probably already does what you want. |
|
From: Ken Y. <ke...@nl...> - 2001-04-19 02:19:35
|
|The chipset sis630e built-in a different sis900 with the standalone |sis900 ethernet chip. The driver from linux 2.2 will not work with it, |only the new linux 2.4.x sis900 driver works with the sis630e . This |also leads to the etherboot sis900 driver that Marty wrote's which is |based on the linux 2.2 driver. I haven't go through the driver souce |yet, but I guess the eeprom is a little different from the standalone |sis900 chip. If anyone is interested to find out please go ahead! I |think we only need a slight modification with comparison with the |difference of the linux 2.2 driver and the linux 2.4 driver and apply |those changes to the etherboot driver. The new driver is backward |compatible, so it is OK. The sis630e chip is also known as "GFXcel 133" What Etherboot version did you try? Always mention the version you are using. Some changes were introduced in 4.7.22: + Peter Kögel contributed patches to the SiS900 driver to make it work for the SiS640e/SiS730s. If you haven't tried this let us know if 4.7.24 works for the 630s. |
|
From: David C. <dav...@rc...> - 2001-04-19 02:14:03
|
Dear all, The chipset sis630e built-in a different sis900 with the standalone sis900 ethernet chip. The driver from linux 2.2 will not work with it, only the new linux 2.4.x sis900 driver works with the sis630e . This also leads to the etherboot sis900 driver that Marty wrote's which is based on the linux 2.2 driver. I haven't go through the driver souce yet, but I guess the eeprom is a little different from the standalone sis900 chip. If anyone is interested to find out please go ahead! I think we only need a slight modification with comparison with the difference of the linux 2.2 driver and the linux 2.4 driver and apply those changes to the etherboot driver. The new driver is backward compatible, so it is OK. The sis630e chip is also known as "GFXcel 133" . regards, David |
|
From: Ken Y. <ke...@nl...> - 2001-04-18 14:30:24
|
>ok, i have set RLOADER,PRLOADER...PRZLOADER=3D bin/rzloader on vers. >4.7.24 > >BIOS says: "no system found" Oh well, this BIOS is too strange for me to deal with now. Ask your supplier how to boot network cards with this BIOS and if they have any sample ROM images you can get and look at with src/disrom.pl. |
|
From: Volker S. <Vol...@da...> - 2001-04-18 07:59:47
|
>What you probably have to do is use rzloader.bin with the ROM image, >instead of przloader.bin. This means editing the Makefile rule specially >for this target, because the default for PCI NICs is to prepend >przloader.bin. ok, i have set RLOADER,PRLOADER...PRZLOADER=3D bin/rzloader on vers. 4.7.24 BIOS says: "no system found" cu volker _______________________________________________ |
|
From: Ken Y. <ke...@nl...> - 2001-04-18 00:23:09
|
|>1. You have a PnP conformant BIOS but you did not select the network |>device as a bootable device.=20 | |the BIOS from the MachZ is special for embedded computers and there is |no option for netboot |because there are options for flashboot, romboot, ramdiskboot.... Ah that's probably why it's not detected then. Probably the BIOS uses the legacy ROM method of getting control even though it's a PCI NIC. |after flashing i set a window with a min size of 16kbyte on the begin of |the etherboot-image in the flash and |than i set the window to a harwareadresse were the BIOS can find the |BIOS-extensions ( D800 ) | |at last is set the bootsuccsession but i haven't a other device and |that's it | |>2. You do not have a PnP conformant BIOS. |i don't know What you probably have to do is use rzloader.bin with the ROM image, instead of przloader.bin. This means editing the Makefile rule specially for this target, because the default for PCI NICs is to prepend przloader.bin. |
|
From: Volker S. <Vol...@da...> - 2001-04-17 08:23:57
|
-----Urspr=FCngliche Nachricht----- Von: Ken Yap [mailto:ke...@nl...] Gesendet: Freitag, 13. April 2001 13:19 An: eth...@li... Betreff: Re: AW: [Etherboot-developers] etherboot Ver. 4.7.23=20 >I think for the eepro100, it's one of the following reasons: >1. You have a PnP conformant BIOS but you did not select the network >device as a bootable device.=20 the BIOS from the MachZ is special for embedded computers and there is no option for netboot because there are options for flashboot, romboot, ramdiskboot.... after flashing i set a window with a min size of 16kbyte on the begin of the etherboot-image in the flash and than i set the window to a harwareadresse were the BIOS can find the BIOS-extensions ( D800 ) at last is set the bootsuccsession but i haven't a other device and that's it >2. You do not have a PnP conformant BIOS. i don't know >The 82559er bug is a different issue not yet understood. My guess is a >media selection issue. the software init. the hardware right but the hardware don't work and i think etherboot can't see that (init is ok) and send for ever a request. cu volker ______________________________________________ Etherboot-developers mailing list Eth...@li... http://lists.sourceforge.net/lists/listinfo/etherboot-developers |
|
From: Ken Y. <ke...@nl...> - 2001-04-17 00:09:59
|
>Some DHCP servers have manual IP assignment configurations with client's >MAC >+address, but others have been configured as dynamic assignment scheme. >So, if >+there are any DHCP client, they can get one IP. > >This is useful when there are many mobile clients, but make it useless >several >+net-booted clients with manual MAC-based assign strategy. Because there >are >+"filename" directive for there own OS kernel image and other boot >related >+options, if they contact dynamic assignment DHCP server firstly, they >can't >+boot properly. Etherboot already has the facility you are looking for, since 4.7.1x or thereabouts. It consists of two parts: Firstly all DHCPDISCOVER packets from Etherboot go out with the tag Vendor Class Identifier (VCI is a tag defined in the DHCP RFC) of "Etherboot-x.y" where x.y is the version number. Secondly, if compiled with the conditional REQUIRE_VCI_ETHERBOOT, Etherboot will only accept replies with the encapsulated option of the tag VCI starting with "Etherboot". This is a compile time option because if it were the default, then Etherboot would not be able to boot on a plain setup. The first is to allow a suitably configured DHCP server (e.g. ISC DHCPD 3.0) to identify Etherboot clients and reply to only those, using conditional scoping. This prevents the server from offering leases to non-Etherboot clients. The second is so that when more than one DHCPOFFER comes in, only the one from the designated DHCP server will be accepted, offers from other DHCP servers, presumably for booting other clients, will be ignored. There are some short notes on this in RELNOTES, which need to migrate into the main documentation when I get some time. It would be nice if you could try the feature out, as I have not used it in production; I have only verified that the components work. |
|
From: Hyun-Joon C. <ta...@ne...> - 2001-04-16 06:36:28
|
SGVsbG8uDQoNCk15IG5hbWUgaXMgSHl1bi1Kb29uIENoYSwgYSBLb3JlYW4gZW1iZWRkZWQgTGlu dXggZW5naW5lZXIuDQoNCkknbSB3b3JraW5nIG9uIGRlcGxveWluZyBtdWx0aXBsZSBuZXQtYm9v dGVkIFNCQ3MgdG8gdGhlIElTUHMuIFRoZXkgYWxsIGhhdmUgYXQgbGVhc3QgQi1jbGFzcyBuZXR3 b3JrIGFuZCBydW4gbXVsdGlwbGUgREhDUCBzZXJ2ZXJzIHRvIG1ha2UgaXQgZWFzeSB0byBtYW5h Z2UgdGhlaXIgSVAgcG9vbC4NCg0KU29tZSBESENQIHNlcnZlcnMgaGF2ZSBtYW51YWwgSVAgYXNz aWdubWVudCBjb25maWd1cmF0aW9ucyB3aXRoIGNsaWVudCdzIE1BQyBhZGRyZXNzLCBidXQgb3Ro ZXJzIGhhdmUgYmVlbiBjb25maWd1cmVkIGFzIGR5bmFtaWMgYXNzaWdubWVudCBzY2hlbWUuIFNv LCBpZiB0aGVyZSBhcmUgYW55IERIQ1AgY2xpZW50LCB0aGV5IGNhbiBnZXQgb25lIElQLg0KDQpU aGlzIGlzIHVzZWZ1bCB3aGVuIHRoZXJlIGFyZSBtYW55IG1vYmlsZSBjbGllbnRzLCBidXQgbWFr ZSBpdCB1c2VsZXNzIHNldmVyYWwgbmV0LWJvb3RlZCBjbGllbnRzIHdpdGggbWFudWFsIE1BQy1i YXNlZCBhc3NpZ24gc3RyYXRlZ3kuIEJlY2F1c2UgdGhlcmUgYXJlICJmaWxlbmFtZSIgZGlyZWN0 aXZlIGZvciB0aGVyZSBvd24gT1Mga2VybmVsIGltYWdlIGFuZCBvdGhlciBib290IHJlbGF0ZWQg b3B0aW9ucywgaWYgdGhleSBjb250YWN0IGR5bmFtaWMgYXNzaWdubWVudCBESENQIHNlcnZlciBm aXJzdGx5LCB0aGV5IGNhbid0IGJvb3QgcHJvcGVybHkuDQoNClNvIEkgdGVzdGVkIHNldmVyYWwg cGh5c2ljYWwgYW5kIGxvZ2ljYWwgY29uZmlndXJhdGlvbiBvcHRpb25zIHRvIG1ha2UgdGhlbSBi b290IGluIGxhcmdlLXNjYWxlIG5ldHdvcmsgd2l0aCBtYW55IGRpZmZlcmVudCBESENQIHNlcnZl cnMuDQoNClRoZXNlIGFyZSBteSB0aGlua2luZ3MuDQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLQ0KMS4gVXNpbmcgVkxBTg0KLSBDaGFuZ2UgVkxBTiBjb25maWd1cmF0 aW9ucyBhZnRlciB0aGUgdGltZSBvZiBJUCBhc3NpZ25tZW50LiBUaWUgdGhlbSAtIFNCQ3MgYW5k IGRlZGljYXRlZCBESENQIHNlcnZlcnMgLSB1cCBmaXJzdGx5IGFuZCByZWxlYXNlIHRoZW0gdG8g aW50ZXJuZXQgYWZ0ZXIgYm9vdCBpcyBjb21wbGV0ZWQuDQotIE1vbml0b3Jpbmcgc2VydmVyIGlz IG5lZWRlZC4NCi0NCg0KMi4gVXNpbmcgdW51c2VkIERIQ1Agb3B0aW9ucw0KLSBEZWZpbmUgYW4g b3B0aW9uIGZvciBtYXRjaGluZyBrZXlzIGJldHdlZW4gY2x1c3RlcnMgb2YgY2xpZW50cyBhbmQg REhDUCBzZXJ2ZXJzLiBBcmUgdGhlcmUgYW55IG9wdGlvbnMgdXNlZCBmb3IgdGhpcyBwdXJwb3Nl PyBJIGNhbid0IGZpbmQuDQotIENoYW5nZSBpbiBldGhlcmJvb3QgaXMgbmVlZGVkLg0KLQ0KDQoz LiBVc2luZyBwcm9wcmlldGFyeSBwcm90b2NvbA0KLSBNYWtlIGN1c3RvbSBvciB1c2UgYWx0ZXJu YXRpdmUgcHJvdG9jb2xzLiBEb24ndCB1c2UgREhDUCBhdCBhbGwuDQotIEFsbW9zdCBub3QgYWNj ZXB0YWJsZS4NCi0gDQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0K DQpBbGwgY2FzZXMgYXJlIHVuZGVyIGFzc3VtcHRpb24gb2YgbWluaW11bSBjaGFuZ2Ugb2YgY3Vy cmVudCBESENQIGVudmlyb25tZW50IGluIHRoZSBuZXR3b3JrLiANCg0KSSdtIGNvbnNpZGVyaW5n IG5vLiAyIGFzIGEgc29sdXRpb24gYW5kIGhhdmUgdG8gc3RhcnQgcHJvZ3JhbW1pbmcgd2l0aGlu IHRoaXMgd2Vlay4gQW55IGlkZWFzIG9uIHRoaXMgc2l0dWF0aW9uPw0KDQpQbGVhc2UsIGFueW9u ZSBleHBlcmllbmNlZCBzaW1pbGFyIHRoaW5nLCBhZHZpY2UgdG8gbWUuDQoNClRoYW5rcyBpbiBh ZHZhbmNlLg0K |
|
From: <ebi...@ln...> - 2001-04-13 21:57:53
|
Marty Connor <md...@th...> writes: > On 4/12/01 1:44 PM Eric W. Biederman ebi...@ln... wrote: > >Marty Connor <md...@th...> writes: > >> Eric, this is excellent! We get a lot of requests from people about how > >> to flash a motherboard BIOS. This is a great tool! > > >Says Marty without running it... > > I should have been a little more precise. Your tool is an excellent > idea. You are correct that I have not run it yet. Of course I haven't > driven a BMW, but I hear they are excellent cars and the company that > makes them has a good reputation... Just giving you a hard time... :) > I appreciate and respect the art and science of BIOS flashing, and want > to help make it easier for people who are less skilled in the art, just > as > rom-o-matic.net makes it easier to make Etherboot ROMS. I want to help as well. But also to emphasize that because you can't count on the vendors to support the plugin roms in any particular fashion. And that cbrom make it look really easy. And it isn't always. So as well as how to do it for some specific motherboard boards a presentation of tricks you can try when the the rom doesn't want to work on your motherboard, should be useful. Simply knowing how to run cbrom isn't enough... > Hopefully these articles will help those who have asked about how to do > this. It is certainly a starting point. Eric |
|
From: Marty C. <md...@th...> - 2001-04-13 20:19:10
|
On 4/12/01 1:44 PM Eric W. Biederman ebi...@ln... wrote: >Marty Connor <md...@th...> writes: >> Eric, this is excellent! We get a lot of requests from people about how >> to flash a motherboard BIOS. This is a great tool! >Says Marty without running it... I should have been a little more precise. Your tool is an excellent idea. You are correct that I have not run it yet. Of course I haven't driven a BMW, but I hear they are excellent cars and the company that makes them has a good reputation... >Basically what I do is I get the bios flash utility and a bios update >from the motherboard vendor. At least on some versions of the award >bios they store their drivers to flash the rom in the new romimage itself. >Then once I have an image I know I can flash you can take my tool and >see with an award bios how all of the plugin roms are laid out. >Going further is an art. It is not longer a black art, but it is >still an art. Bioses are choosy about which plugin roms they run. If >the bios already has a PXE rom, replace it and imitate it as closely >as possible with etherboot. I appreciate and respect the art and science of BIOS flashing, and want to help make it easier for people who are less skilled in the art, just as rom-o-matic.net makes it easier to make Etherboot ROMS. I have found these two web pages which describe how to insert Etherboot code into an Award BIOS and flash it: http://www.riverdale.k12.or.us/linux/ltsp_bookpc_howto.html http://www.riverdale.k12.or.us/linux/ltsp_bookpc2_howto.html Hopefully these articles will help those who have asked about how to do this. --- Try: http://rom-o-matic.net/ to make Etherboot images instantly. Name: Marty Connor US Mail: Entity Cyber, Inc.; P.O. Box 391827; Cambridge, MA 02139; USA Voice: (617) 491-6935, Fax: (617) 491-7046 Email: md...@th... Web: http://www.thinguin.org/ |
|
From: Marty C. <md...@th...> - 2001-04-13 12:28:51
|
On 4/13/01 7:19 AM Ken Yap ke...@nl... wrote:
>It seems that, from a couple of reports, some people have non-conformant
>BIOSes. I will edit loader.S in the next version so that by defining
>NON_PNP_BIOS, they can use the INT19H mechanism to hook the boot entry
>point, i.e. the mechanism used by "legacy ROMs".
I was thinking of adding something to the rom-o-matic which would allow
people to swap the ID bytes as they created their rom, using the
"swapdevids.pl" program. The other experiment I was thinking of trying
was using a byte pattern of 02 00 02 which, when reversed is the same.
I'm not sure if the final byte is all that important.
>The 82559er bug is a different issue not yet understood. My guess is a
>media selection issue.
If I could find such a card, I'd be willing to check this out. I haven't
looked too hard at this driver, but without a test card, it's a little
difficult to debug.
---
Try: http://rom-o-matic.net/ to make Etherboot images instantly.
Name: Marty Connor
US Mail: Entity Cyber, Inc.; P.O. Box 391827; Cambridge, MA 02139; USA
Voice: (617) 491-6935, Fax: (617) 491-7046
Email: md...@th...
Web: http://www.thinguin.org/
|
|
From: Ken Y. <ke...@nl...> - 2001-04-13 11:19:15
|
>>In other words, please fill in this table: > > <4.7.23 4.7.23 4.7.24 >eepro100 no, no prompt yes,valid prompt no, no prompt >82559er no, no prompt no, valid prompt no, no prompt > >the eepro100 works with both drivers fine. >the 82559er print a valid prompt and wait for DHCPServer but the 82559er >makes no request and wait for ever. I think for the eepro100, it's one of the following reasons: 1. You have a PnP conformant BIOS but you did not select the network device as a bootable device. The bug in 4.7.23 bypasses the BIOS mechanism. When the BIOS is conformant, it will, in the first enumeration pass, detect the net device as a bootable device. In the second pass, it will attempt to boot from the detected devices in the order specified in the BIOS configuration, e.g. NET, A, C. If the net device is not specified in the configuration, then it will not be tried. 2. You do not have a PnP conformant BIOS. It seems that, from a couple of reports, some people have non-conformant BIOSes. I will edit loader.S in the next version so that by defining NON_PNP_BIOS, they can use the INT19H mechanism to hook the boot entry point, i.e. the mechanism used by "legacy ROMs". >I think i need this bug on my hardware and one more for the 82559er :-) The 82559er bug is a different issue not yet understood. My guess is a media selection issue. |
|
From: <ebi...@ln...> - 2001-04-12 17:45:09
|
Marty Connor <md...@th...> writes: > On 4/11/01 8:00 PM Eric W. Biederman ebi...@ln... wrote: > >Here is a cleaned up version of my award rom decoder, now that I have > >used this reverse engineering to get etherboot into the curdls > >motherboard. > >If someone wants they can build now take lharc and my program > >and build an opensource version of cbrom... > > Eric, this is excellent! We get a lot of requests from people about how > to flash a motherboard BIOS. This is a great tool! Says Marty without running it... > I would very much like to document BIOS flashing procedures for the > Etherboot documentation. Would anyone who knows how to do this please > send me mail? We are working on getting the Etherboot documentation into > Docbook XML, and this would be a really nice section. Basically what I do is I get the bios flash utility and a bios update from the motherboard vendor. At least on some versions of the award bios they store their drivers to flash the rom in the new romimage itself. Then once I have an image I know I can flash you can take my tool and see with an award bios how all of the plugin roms are laid out. Going further is an art. It is not longer a black art, but it is still an art. Bioses are choosy about which plugin roms they run. If the bios already has a PXE rom, replace it and imitate it as closely as possible with etherboot. Eric |
|
From: Marty C. <md...@th...> - 2001-04-12 17:34:50
|
On 4/11/01 8:00 PM Eric W. Biederman ebi...@ln... wrote:
>Here is a cleaned up version of my award rom decoder, now that I have
>used this reverse engineering to get etherboot into the curdls
>motherboard.
>If someone wants they can build now take lharc and my program
>and build an opensource version of cbrom...
Eric, this is excellent! We get a lot of requests from people about how
to flash a motherboard BIOS. This is a great tool!
I would very much like to document BIOS flashing procedures for the
Etherboot documentation. Would anyone who knows how to do this please
send me mail? We are working on getting the Etherboot documentation into
Docbook XML, and this would be a really nice section.
Best Regards,
Marty
---
Try: http://rom-o-matic.net/ to make Etherboot images instantly.
Name: Marty Connor
US Mail: Entity Cyber, Inc.; P.O. Box 391827; Cambridge, MA 02139; USA
Voice: (617) 491-6935, Fax: (617) 491-7046
Email: md...@th...
Web: http://www.thinguin.org/
|
|
From: <ebi...@ln...> - 2001-04-12 16:51:29
|
Ken Yap <ke...@nl...> writes: > >> What happens with 4.7.22? If that also crashes in the same way then it's > >> not a .23 problem per se but something else unresolved. I know this > >> doesn't help you much but it at least narrows down the problem. If .22 > >> works (the EEPRO100 driver didn't change in between) then I want to know > >> about it. > > > >4.7.22 does not crash. > >It is also not recognized on the Tyan S2510 motherboard with AMI BIOS. > >In other words: Etherboot 4.7.22 flashed on Intel Pro100+ card is not > >called from BIOS at boot time on this motherboard. > >Flashed eepro100 4.7.22 Etherboot is recognized and runs fine on Intel > >L440GX+ motherboard. > >Also, 4.7.23 runs fine on Tyan motherboard when run from a boot floppy. > > Grr, BIOS issues again. I wish there was an easy way to determine > conformance or not of a BIOS to the standard. :) One of the reasons why I'm working on linuxBIOS for a long term solution. Then if you have a real problem you read the source or recompile a new BIOS.... Eric |
|
From: <ebi...@ln...> - 2001-04-12 16:48:14
|
Ken Yap <ke...@nl...> writes: > |Here is a cleaned up version of my award rom decoder, now that I have > |used this reverse engineering to get etherboot into the curdls > |motherboard. > | > |If someone wants they can build now take lharc and my program > |and build an opensource version of cbrom... > > Thanks, I'll put that in contrib/. Any preferred name for it? Something like award_plugin_roms. My original working name of rom_strings isn't very accurate any more. It's a perl script that should do a pretty good job of listing roms. Eric |
|
From: Marty C. <md...@th...> - 2001-04-12 16:09:13
|
I have rewritten the Etherboot tulip driver to incorporate media
detection (and other) code from the Linux tulip driver. This should mean
that the Etherboot driver supports a lot more tulip and clone cards. I
have tested the driver with with the following cards:
DEC-21041A genuine DEC Tulip card
MX98715 Macronix Tulip Clone
ADMTEK0985 Linksys v4.1 LNE100TX
LC82C168 Netgear FA310TX
LC82C115 Linksys v2.0 LNE100TX
I have installed a test version of Etherboot on rom-o-matic.net that uses
this new tulip driver. The version with the new tulip driver is called
"4.7.24mc1" to differentiate it from the official 4.7.24 release. To get
a test image, just choose "tulip" as your NIC type. The new tulip driver
is the only change.
There are some things you should know:
- This driver is BIG. It started out as 800 lines of code, and is now
almost *2000* lines. I may be able to shorten it, but the Linux driver
tries to support over 140 cards and clones, so there is a lot of code
to deal with media detection and various ways of getting the MAC
address.
Consider this a first pass. I'm sure together we can improve it.
- The ROM images this driver produces are BIG. The .lzrom file is 32K.
The runtime size is over 40K. There could be some problems on machines
where the BIOS is borrowing some memory.
- I have burned working 32KB ROMs for 4 of the above cards, and they do
work.
You need to use at least a 27C256 (that's 256K *bits* or 32K bytes).
I'd recommend using Etherboot version 4.7.24 if you want to compile
this
yourself.
The source for the new tulip.c file is on http://www.thinguin.org for
those who want to check it out.
I suspect that we may have to make changes to save space because the
driver is so large, especially where people need a lot of Etherboot
options. There are things that can be done. Right now, I need people to
try the driver and see it if basically works.
The Linux tulip driver is one of the most amazing pieces of code I have
ever studied. My hat is off to Donald Becker and the people who maintain
it. It took me almost 5 continuous days of studying and coding to
understand it well enough to rewrite and incorporate the necessary
routines into Etherboot.
I consider this rewrite to be a starting point. I welcome (and hope)
that others will find ways to shrink the code (conditionally compiling a
lot of printfs, using 2 receive buffers instead of 4, etc.) and that we
will be able use lots of old DEC 21xxx and clone based cards for network
booting.
I'm going to take a long rest now.
Have fun, and thanks for testing this! Please send bug reports and
questions to the Etherboot-users and Etherboot-developers lists, as
appropriate. I'm way behind in answering my mail ;-)
Marty
---
Try: http://rom-o-matic.net/ to make Etherboot images instantly.
Name: Marty Connor
US Mail: Entity Cyber, Inc.; P.O. Box 391827; Cambridge, MA 02139; USA
Voice: (617) 491-6935, Fax: (617) 491-7046
Email: md...@th...
Web: http://www.thinguin.org/
|
|
From: Volker S. <Vol...@da...> - 2001-04-12 08:22:40
|
>Do you mean it works with both the eepro100 and the 82559er or that it >works with the eepro100 only. >In other words, please fill in this table: <4.7.23 4.7.23 4.7.24 eepro100 no, no prompt yes,valid prompt no, no prompt 82559er no, no prompt no, valid prompt no, no prompt the eepro100 works with both drivers fine. the 82559er print a valid prompt and wait for DHCPServer but the 82559er makes no request and wait for ever. >When you say it's the only version working, I take it you have also >tried 4.7.24? Because I have a report that 4.7.24 is very PnP comformant >now and fixed a serious bug in 4.7.23. I think i need this bug on my hardware and one more for the 82559er :-) _______________________________________________ Etherboot-developers mailing list Eth...@li... http://lists.sourceforge.net/lists/listinfo/etherboot-developers |
53 messages has been excluded from this view by a project administrator.
