Networking lost when change in card utilized / lockup on D-Link Gigabit DGE-530T

[HaikuCPA]

Running R1/alpha 2 (Revision 36769) GCC 2 Hybrid Kernel May 8 2010 20:58:31, Architecture: Pentium 4 2.79 ghz with 2678 MB RAM, HP dx2000MT with non stock Network card added: D-Link DGE-530T 10/100/1000 Gigabit Adapter. (Native Card is shown as a "sysconnekt" in Haiku, which is a 10/100 - not being utilized.)

When I connect the network cable into the D-Link network card - a network connection only exists if I choose DHCP. If I change the connection to a static IP, I loose my connection. If I revert back to DHCP the useage bar on the left (memory or CPU usage goes almost to 100%, I can no longer use Haiku and am forced to pull the plug on the computer.

(Note - I also own a second similar looking machine ->HP D220 with 2.4 ghz and 759 MB Ram ->identical build information as above. However the native card in this machine is a Broadcom 440x, which I used initially without issue.

It will sound odd, but I also have a second card in the HPD220, however it is a Realtek 102TXA 10/100 card (equivalent bandwirth as native Broadcom Card). Upon switching the cable connection to the Realtek card from the Broadcom card, I lost networking from the Realtek card -> I could not ping the router.

Switching from DHCP to a static configuration didn't resolve the issue, and switching back to DHCP from a static setting is not a problem.

A network connection from this Realtek card was previously functional. When I plugged the cable back into the Broadcom card -> networking functioned properly from it.)

Unfortunately I haven't the programming skill to submit a patch. Its also difficult for me to tell what the real problem is, however, my guess is that there is an issue with Haiku being able to adjust its networking settings to changing circumstances on the fly - weather it be [from DHCP to static] or [device number] or [drivers utilized]. However, it also seems that either [gigabit networking] or [the driver for Dlink cards] are factors in this issue as well.

[anevilyak]

You may want to try a nightly image and see if this behavior still exists. There have been nearly 2000 changes since alpha 2 and the network stack in particular has seen a bunch of work in recent weeks.

[waddlesplash]

No reply in 8 years.

[nielx]

Remove milestone for tickets with status = closed and resolution != fixed