I tried building a new kernel with your patch and loaded nfe0 instead of the old rl0 I’m currently using. Well only the network. On Thu, Dec 27, at What do you need me to do, in order to get some usable info about what is going on? The ftp transfer stops, I’m unable to ping from the server and browsing the web from the machine also does not work. Search everywhere only in this topic Advanced Search Problem with nfe stability and throughput. Renewal of nfe driver package.
|Date Added:||16 January 2012|
|File Size:||17.91 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Reserved 0x bytes for rid 0x10 type 3 at 0xdfffc nfe0: 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.
Please don’t give up and lets try nf still guessing combinations.
Thanks a lot to Pyun YongHyeon. Things seemed to still be running, but ping to another local machine was sloooow.
Don’t worry about that. My network config is giving me problems. These modifications were made by Pyun YongHyeon. It would work on a greater variety of motherboards. On Sun, Dec 23, at I guess ukphy 4 is not right phy driver for the hardware as it could result in non-working driver.
Most vendors provides datasheet for their PHY even though they don’t want to reveal their ethernet controller datasheet. So I decided to beat it up with a torrent download: Added freensd for vlan hardware tagging capability.
Using 8 MSI messages miibus0: Please revert previous patch and apply the following one. It came up nicely with the following entries in dmesg: On Fri, Jan 18, at Also I noticed that both nfe0 and ohci1 both lists irq 23, but I don’t know if that is a problem: The M2N-VM machine stopped responding to ping, ssh, ftp.
How about using media type ‘auto’? I still have no idea why it doesn’t work on some hardwares. The ftp transfer stops, I’m unable to ping from the server and browsing the web from the machine also does not work.
FreeBSD and the nfe driver – DaemonForums
These are obtained from the HEAD branch. I have no idea why hardware vendors don’t like to release their datasheet for their PHY. So is there anything else I can do to help nailing this one? And it does not panic system anymore when it mfe to detect PHYs.
Index of /~mkgray/afs/bar/afs/sipb.mit.edu/project/freebsd/head/sys/dev/nfe
Fixed several problems on driver attachment. This was made by Michael Eisele. When I get home, I’ll try stressing the network some, to see how badly it misbehaves. These patches are needed to run nfe device driver. On Thu, Jan 17, at Would you show me the ukphy 4 output of verbosed boot message?
FreeBSD Manual Pages
I tried building a new kernel with your patch and loaded nfe0 instead of the old rl0 I’m currently using. Things came up just fine. On Wed, Jan 16, at Rreebsd have to check chip name and model number of PHY used on your motherboard and then apply the corresponding patch into kernel source code.