Intel LAN connection stops working

[kuroishi]

Ok here is my issue, i searched the forums and didn't see this reproduced.

 

My lan connection works like a peach for anywhere from a few minutes to a few hours. But soon as i really put the heat on for a torrent or a general download, it dies. No recovery possible it just stops and I have to reboot to get it to work again. Does anyone have any ideas? I'm using 10.5.2 iAtkos.

[Maciek Leja]

Similar thing is happening to me. I am running iDeneb 10.5.5 and my 2 onboard lans do not work at all but I installed a PCI Dynex card and it worked amazing for a few days and suddenly for two days it only works up to 30 min. and then I get a 169 address. Starts working again when I restart.

 

WTF!

[ivomu89]

Ok here is my issue, i searched the forums and didn't see this reproduced.

 

My lan connection works like a peach for anywhere from a few minutes to a few hours. But soon as i really put the heat on for a torrent or a general download, it dies. No recovery possible it just stops and I have to reboot to get it to work again. Does anyone have any ideas? I'm using 10.5.2 iAtkos.

 

HEEY,

 

I got the same problem too!! it can work for hours without any problems but then it stops when start downloading via usenet or when i download a torrent file with the program transmission..

 

I really wonder if you solved your problem and how?? I got Mac os x 10.5.6 leopard. My ethernet card is a realtek 8169, something like that.. If it is of any use for you.. If you got something, please HELP.

 

Thanks,

 

Ivo M from Holland

[solar984]

I am also having a similar problem. The problem seems to happen under load, or after a certain number of packets maybe..

 

I've been working on this for a while and haven't quite figured it out, but I do have a workaround.

If you boot with cpus=1 then the problem doesn't happen at all. This is better than nothing but I would like to figure out what's up.

 

I'm having this problem on 2 completely different computers both with almost fully stock retail 10.5.6 installs. Both systems are using Core 2 Duo processors. One system uses a VIA chipset and the other has an nForce. It happens with all network cards including the Realtek 8169 that works with no mods, the nForce LAN (tried several different drivers) and the ViaRhine LANs. One interesting bit is that I noticed that it only kills the NIC that you're using.. so for instance if you have an onboard LAN and a PCI card LAN, you can use the PCI card for a while, then when it gets hosed up you plug your network cable into the onboard one and that one will still work for a while, then that dies too.

 

Here is how to reproduce it every time:

 

Open terminal

Type: sudo ping -f ADDRESS

 

Replace ADDRESS with the IPv4 address of your router, for example 192.168.0.1 or whatever.

It will make dots for dropped packets. When it starts off it should only have 1-2 dots and you should see the cursor kinda flashing.. it prints a dot each time it sends a packet and deletes it each time it receives a reply. Wait about 2-3 minutes and it'll die and you'll just see a flood of dots. Type control-c to stop it.

 

I went through and started with a completely retail install and added only the basics to get the system to boot.

I have a 100% retail install except for these and the problem is still happening:

dsmos.kext (decrypt)

AppleVIAATA.kext (for hard drive support)

Natit.kext (video string injector)

 

I also was using these before but restoring them to vanilla versions had no effect:

Modded AppleACPIPlatform.kext (fixes reboot)

Modded AppleSMBIOS.kext (fixes system info and apps that check that stuff)

Modded AppleHDA.kext and HDAEnabler.kext (audio codec support)

 

I also tried the Voodoo Kernel 9.5.0 and while it worked great the problem is exactly the same.

 

I guess the problem may be some sort of multi core related thing, or perhaps cpus=1 has some other effects, like disabling the APIC or something like that (something people do for AMDs on linux).

 

For anyone wanting to use the workaround, edit the file /Library/Preferences/SystemConfiguration/com.apple.Boot.plist and find the section that looks like this:

 

<key>Kernel Flags</key>

<string></string>

 

Make it looks like this:

 

<key>Kernel Flags</key>

<string>cpus=1</string>

[solar984]

I've got some more information on this, but still no real solution, just another workaround.

 

The motherboard I'm using is: Biostar P4M900-M7 FE

 

If I use ViaRhine.kext with the onboard 100Mbit LAN it works (but really slowly probably because of the hacked driver) but under load with both cores the problem described above still happens.

If I use a RTL8169 based gigabit LAN (my preferred card) it works without any special drivers but dies under load.

If I use a 3Com 905C-TX (Broadcom, 100Mbit) it works without any special drivers too but dies under load.

 

One thing that works with no problem is the Apple USB Ethernet (the one sold for use with the MacBook Air, 30 dollars). I guess this problem may be related to PCI devices only? USB Ethernet works with both cores enabled and doesn't die under load but all the other internal network cards including the built in onboard one have the problem with 2 cores. Is there some problem with this specific board? Could the problem be in the AppleVIAATA.kext?

 

The USB Ethernet works but it's slow (100Mbit not 1000Mbit) and I would like to get to the bottom of this problem.

[falhart]

This solution did work for me.

 

edit the file /Library/Preferences/SystemConfiguration/com.apple.Boot.plist and find the section that looks like this:

 

<key>Kernel Flags</key>

<string></string>

 

Make it looks like this:

 

<key>Kernel Flags</key>

<string>cpus=1</string>

 

 

 

I have noticed that a few people have this problem.

 

Now while that is great and does work it only gives you one processor. I dont know if there is another solution for this or not but anyone with any input would be greatly appreciated.

 

This is the last thing i need to get working to have my machine fully functional and i have no idea how to resolve.

 

If someone with more advanced knowledge wants me to run some diagnostics or post some log files and i will happily do so. just let me know what and where to look and i will.

 

Thanks in advance!

[solar984]

In my earlier post I said the problem doesn't happen with the USB Ethernet, but it did eventually happen and I went back to the cpus=1 workaround. I noticed that after a week or two even that didn't always work. I replaced the motherboard with a Gigabyte EP45-UD3R and my problems went away.. the problem board was a cheap 50 dollar VIA based motherboard.. I don't recommend it.

[yioulas]

That's really weird because I have a single core Dell Inspiron 9300 and it still happens even with cpu=1. It's really frustating. Everything else works perfectly.

 

I am using a broadcom 440x lan card. I 've ordered a broadcom wifi card hoping that the problem will go away with wireless.

 

Please post here if you find any solutions. I have been trying to fix this for a week now. I tried using the old IONetworkingFamily.kext version 1.5.0. and the connection lasts longer before crashing. I heard that using the old kext disables wireless though.

 

I also tried playing with the MTU settings and setting the card to half-duplex after reading many posts. Again these just increased the time before the crash.

 

My motherboard is intel ICHx based.