Intel 82559ER network chip, 1209 ID, 82559, 1229 ID

[Guest]

I have a TRUELY headless system. No video output is EVER possible. There is
no video connector on the device.

It uses the Intel 82559ER network chip (which has an ID of 1209). I have
gotten several images to compelete FBA (according to the kernel debugger
output from the serial port) and it appears that the e100ent.sys driver is
installed. However, the driver will not start and I can not ping the system.

The product used to run Win NT and it used the e100ent.sys driver then. The
driver download from Intel has that driver in there, it also has
e100b325.sys.

I can get the same FBA image to work on a PC that has very similar hardware
(440BX chipset) and a NIC with the 82559 network chip (ID 1229). It works
fine, but uses the e100b325.sys driver.

Can anyone help me? I'm at my wit's end trying to get the driver to start on
my headless system.

Thanks,
Gary

 

[KM]

Gary,

Did you componentize the driver yourself or found INtel's component for XPe?
Did you test the driver on XP Pro first? Does it work there?

In any case, you may want to give it a little bit of debugging via an output to a text file.
Basically if you use command line utilities such as ipconfig, netsh and devcon, and output the results of those command tools to a
text file that you can further explore on another PC, it should give you some good hints on what's going on in your headless system.

Not to mention, you always have \windows\setupapi.log file to check why the driver is falling to start or etc.

 

[Guest]

Just in case anyone else comes looking at this post later... the real
problem turned out to be in the BIOS. The network chip was not set up
correctly. Once the BIOS vendor fixed some of the problems with the BIOS I
was able to ping by name and use remote desktop.

Thanks

 

[KM]

The rule#1 in XPe - components should work under XP Pro first
Obviously, this rule helps avoiding issues with BIOS.