Jump to content

kode54

kode54

Member Since 20 Jul 2011
Offline Last Active Private
-----

Posts I've Made

In Topic: Airport - PCIe Half Mini

Today, 03:00 AM

It's not an Atheros card. It's this card, which is most definitely Broadcom:

 

http://www.amazon.co...0?ie=UTF8&psc=1

 

IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/RP05@1C,4/IOPP/ARPT@0

 

compatible = <"pci1a3b,2123", "pci14e4,43b1", "pciclass,028000", "ARPT">

 

IOName = "pci14e4,43b1"

In Topic: Airport - PCIe Half Mini

Yesterday, 09:51 AM

  1. 1. Description of WiFi problem

WiFi card does not appear, and according to IOReg, still lists its original compatibility field, after applying SSDT patch with Clover.

 

  1. 2. OS X version/motherboard model/BIOS version/processor/graphics

10.9.5 13F18 / MSI Z77A-GD65 / is this really necessary? / Core i5 3570K / Radeon R9 270X

 

  1. 3. Procedure/Guide Used

Your SSDT guide. Opened 43xx patch, edited the RP04 to RP05, the PCI root ID that contains my card.

  1. 4. Copy of IOReg/IORegistryExplorer_v2.1.zip (View Raw)

http://cl.ly/3T2y3N1L0S1g

 

  1. Console/All Messages/kernel airport - select/Save Selection As:
  2.  
  3. Not sure what this means, as there is no "kernel airport" selection under All Messages, nor anything else. My kernel log is filling up with mdworker messages about Import: Bad path:, which is unrelated to this.
  4.  
  5. DPCIManager/Status
  6.  
  7. https://www.dropbox....21 02.45.07.png
  8.  
  9. System Information/Hardware/Network/WiFi

https://www.dropbox....21 02.47.00.png

  1.  
  2. Clover (if installed)
  3.  
  4. 1. EFI/Clover/config.plist

http://cl.ly/3u0A0E3R2d04

  1. 2. EFI/Clover/misc/debug.log (Set config.plist/Boot/Log/true)
  2.  
  3. http://cl.ly/0A3Z0v0X2i1h
  4.  
  5. EFI/Clover/ACPI/Patched/dsdt.aml
  6.  
  7. Didn't touch this file. There is no dsdt.aml in my Clover configuration.
  8.  
  9. EFI/Clover/ACPI/Patched/ssdt.aml (if WiFi edited)

http://cl.ly/2x0p3a2c3C2i

In Topic: Airport - PCIe Half Mini

18 August 2014 - 07:54 AM

WiFi only, need USB for BT.

 

Why yes, I do believe that is what the included cable is for.

In Topic: AppleIntelE1000e.kext for 10.8/10.7/10.6/10.5

13 August 2014 - 05:13 AM

I forgot about PlistBuddy. Yeah, that'll do it much quicker and easier.

In Topic: AppleIntelE1000e.kext for 10.8/10.7/10.6/10.5

13 August 2014 - 04:48 AM

sudo kextunload /System/Library/Extensions/IONetworkingFamily.kext/Contents/PlugIns/AppleIntelE1000e.kext

 

sudo vi /System/Library/Extensions/IONetworkingFamily.kext/Contents/PlugIns/AppleIntelE1000e.kext/Contents/Info.plist

 

Type:

 

/NETIF_F_TSO<Enter>

 

to find the relevant setting. Change the associated <true/> to <false/>, by moving the cursor to the /, pressing the i key to switch to insert mode, backspace the word, and type in false. Then press Escape, then :wq to write out the file and quit.

 

Then you can reload it with:

 

sudo kextload /System/Library/Extensions/IONetworkingFamily.kext/Contents/PlugIns/AppleIntelE1000e.kext

 
You're welcome to copy the plist out and make the change with Xcode, but I think that goes a little overboard. Nano -w is also fine, if you already know your way around search, edit, and save with that.
 
As mentioned above, this feature will probably be disabled by default in future releases.
 
Further disputing the usefulness of TSO, when it's already proven to be quite buggy. The fact that it's enabled by default on Windows for some newer chipsets does not mean that it suddenly works properly on older chipsets. Or even that it has been fully tested on newer hardware. Intel probably likes to use their install base as a testbed, then cleans up the mess with later driver releases. You're welcome to argue this, but perhaps for now, you could put a notice in the OP to disable this option if TX unit hangs are encountered, and for future versions, enable it at your own risk.
 
You may also opt to make the edit and reboot instead of using the kextunload/kextload cycle, but I've found that a reboot is not entirely necessary to fix the hardware hang issue, now that I've already had to experience it a few times from attempting to back up over 40GB of data over even just a 100Mbps link. Since making this configuration change, I have been able to back up over 1TB of data over the same link without any errors.
© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy