Here's an interesting twist.
I put in a 2nd PCI ethernet controller in the client which uses the Realtek chip/drivers. This is in addition to the onboard Marvell/sky2 ethernet controller.
Then I observe the following behavior:
- It will only PXE Boot from the onboard Marvell controller (sky2 driver)
- where it used to crash (see above) it actually loads the drivers for the Realtek controller
- if I move the ethernet plug from the Marvell to the Realtek controller, it re-establishes the ethernet connection
- and lo-and-behold, a successful boot.
Here is the term output on boot where it continues with the Realtek controller:
[] eth0: RTL8169sb/8110sb at 0xf8828000, [mac addr], XID 10000000 IRQ 17
Done.
[] NET: Registered protocol family 17
IP-Config: eth0 hardware address [mac addr] mtu 1500 DHCP RARP
[] r8169: eth0: link down
( ... then I move the ethernet plug from the Marvell to the Realtek PCI card... )
[] r8169: eth0: link up
( ... then some fast scrolling to the LTSP DHCP settings... and done!)
So it seems like it is definitely a problem somewhere with the Marvell controller and how it dies somewhere in the boot of the PXE boot image, but I have no idea how to fix this.
FYI - If I plug in a different ethernet cable to the Realtek controller, then it doesn't complete the PXE boot.
Any ideas????
Bookmarks