bcm5722d

[Thund3rbolt]

Anyone else having an issue with the wired lan using this driver? It's disconnecting for me under heavy load. If I transfer say 10 GB or more it never completes and I have to reboot to get it working again.

 

Issue reported here: https://github.com/a...5722D/issues/11

 

and here: http://www.osx86.net...&id=3074&page=1

 

solution: Went back to using AppleBCM5751Ethernet. Copy IONetworkingfamily.kext (Version 1.10) and AppleBCM5751Ethernet.kext ( Version 2.10d21 Copyright Apple) to /Extra/Extensions then delete BCM5722d.kext and re-run Myfix.

[Hervé]

Will try. I have that BCM5722d kext installed, but never actually use the wired Ethernet, just Wifi.

[Thund3rbolt]

Let me now if you have any success using lion if you can Herve. I think in light of this problem we should do away with that driver until a new version can be released.

[JDubU]

Does AppleBCM5751Ethernet.kext still work after waking from sleep?

BCM5722d.kext causes the wired network adapter to stay asleep -- a reboot being required to bring it back to life.

[Hervé]

I'm typing this having switched off Wifi, plugged in the Ethernet, put the laptop to sleep by closing the lid and waking it by opening the lid.

 

So the answer is: Yes

 

The loaded kext is that provided by the myHack library:

[JDubU]

Very interesting!

 

I thought that this was a known problem with the BCM5722d kext. I know that Seb reported that his did not work after waking from sleep and a Google search has others (on other forums) reporting it as well (for example: http://www.osx86.net/downloads.php?do=file&id=3074&page=2).

 

My EDP install and BIOS settings are the same as yours (I used your setting based on our discussion in: https://osxlatitude.com/index.php?/topic/1827-slow-shutdown/page__st__20).

 

Any ideas on why yours does not have the problem? Did you do something special to make it work?

[Hervé]

Nothing specific ever done; it just works, so never had reason to think about it. I still have to test this reported disconnection issue under high traffic though...

 

I'll put a copy of my Chameleon boot plist + SMBIOS details later on, in case the answer lies somewhere in there; doubt it though...

[Hervé]

Here they are:

 

 

And running Chameleon 2.1svn regularly updated (up to r2063 at the moment):

 

[JDubU]

Thanks Hervé!

 

There were several differences.

 

org.hameleon.boot.plist:

In my "CPU" section no items at all were checked.

My "USB bus fix" was checked.

 

SMBIOS:

My model was set to MacBook3,1 instead of MacBookPro3,1.

 

I changed the above features to match yours and I also updated to the latest svn release of Chamelion (r2069).

After restarting:

 

"Network" system preferences pane shows WiFi(connected), Ethernet(connected) and Firewire(not connected). Before the changes, it also listed Bluetooth (not connected). The Bluetooth Icon appears in the menu bar but now does not show in system preferences.

 

Closing the lid to put the computer to sleep and then opening it again to wake it up, Network pane now shows WiFi(connected), Ethernet(not connected), Firewire(not connected).

 

So it did not fix the Ethernet wakeup problem.

I wonder if there are Ethernet hardware differences between our two D630's?

[Hervé]

I would not worry too much about not seeing any BT items in the Network Pref Pane, unless you use PAN or DUN with a bluetooth. device. In fact, these 2 may require to be added manually -> Press "+" button and see what's offered in the list of interfaces.

 

In the System Preferences however, you should see the BT icon. The other way to open the BT Pref Pane is to click on the menu bar icon and select "Open Bluetooth preferences...".

 

Re: on-board Ethernet, I'd expect the same HW on all D630: