I still have no idea why it doesn’t work on some hardwares. It came up nicely with the following entries in dmesg: I guess ukphy 4 is not right phy driver for the hardware as it could result in non-working driver. What would be the next step for me to try in order to resolve this? The M2N-VM machine stopped responding to ping, ssh, ftp.
|Date Added:||17 January 2006|
|File Size:||36.3 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Is there any reason not using auto media type? Added two protections for possible watchdog timeouts; check for missing Tx completion interrupt and check for missed start Tx command. I tried pinging the machine and the result of that is that pings are OK and then usually a freebsf timeout follows and then another OK pings etc. These are obtained from the HEAD branch. These updates were made by Pyun YongHyeon yongari at freebsd dot org.
On Fri, Jan 18, at Added support for hardware checksum offloading capability. These patches are needed to run nfe device driver. So is there anything else I can do to help nailing this one?
You may need one of the following PHY patches to detect the link type correctly. You can insert a delay by typing the following command.
On Tue, Jan 22, at I didn’t even think atphy 4 can establish a valid link. Reserved 0x bytes for rid 0x10 type 3 at 0xdfffc nfe0: You can get the diff at the following URL.
I guess ukphy 4 is not right phy driver for the hardware as it could result in non-working driver. I guess the above issue is related with your manual media configuration such that nfe 4 thinks it established a full-duplex link with link partner but the resolved link is still half-duplex one.
Most vendors provides datasheet for their PHY even though they don’t want to reveal their ethernet controller datasheet. Note that this driver has a long standing bug that is is instability of manual half-duplex media selection on certain hardwares auto sensing media type should work for all cases, though.
Search everywhere only in this topic. These updates were made by Pyun YongHyeon.
freebsd-current – Problem with nfe stability and throughput
These updates were made by Peer Chen pchen at nvidia dot com. Downloads to the box are both slow and unstable. Please frreebsd give up and lets try possible still guessing combinations. It would work on a greater variety of motherboards.
Hi, Pyun YongHyeon wrote: OUI 0x, model 0x, rev.
FreeBSD nfe Network Device Driver
It now correctly handles missing PHY issues on nForce Thanks a lot to Pyun YongHyeon. Free forum by Nabble. Things came up just fine. What would be the next step for me to try in order to resolve this?
FreeBSD Manual Pages
In reply to this post by Chris Poulsen. What do you need me to do, in order to get some usable info about what is rfeebsd on? Please revert previous patch and apply the following one. These modifications were made by Pyun YongHyeon.