it doesn't work. The switch I have shows it coming up 100 bt FDX, and
etherboot says it is up 100bt FDX, but etherboot keeps complaining about
timeouts .... anyone seen this? tcpdump shows that no packets are making
it out of the box.

Note these are TX Timeouts, not timeouts on DHCP responses. There is some
problem with xmitting.

And I still claim that this is the kind of thing that comes up with a
forked driver tree :-)

ron

===

Jumping to boot code
ROM segment 0x5000 length 0x0012 reloc 0x9400
clocks_per_tick = 379143
Etherboot 5.1.1 (GPL) ELF (Multiboot) for [SIS900]
Boot from (N)etwork or from (L)ocal? N
Found SIS900 at 0x2100, ROM address 0x0000
Probing...[SIS900]
sis900_probe: MAC addr 00:D0:09:63:38:CF at ioaddr 0x2100
sis900_probe: Vendor:0x1039 Device:0x0900
sis900_probe: SiS 900 Internal MII PHY transceiver found at address 1.
sis900_probe: Using SiS 900 Internal MII PHY as default
sis900_read_mode: Media Link On 100mbps full-duplex
Searching for server (DHCP)...
sis900_transmit: TX Timeout! Tx status 8000024E.
sis900_transmit: TX Timeout! Tx status 8000024E.
sis900_transmit: TX Timeout! Tx status 8000024E.
sis900_transmit: TX Timeout! Tx status 8000024E.
sis900_transmit: TX Timeout! Tx status 8000024E.




Reply via email to