Jump to content

Hervé

Administrators
  • Posts

    10041
  • Joined

  • Last visited

  • Days Won

    563

Posts posted by Hervé

  1. !!! WARNING !!!

     

    10.8.4 seems to break network connection for some Wireless setups. Several users have now reported problems with Broadcom-based cards. Bronxteck confirmed this and indicated that 10.8.4 can break connectivity to secured network. However, open or low-secured networks (WEP) retain ability to connect.

     

    I'll try and test things with DW1390 and DW1395 cards tonight.

     

    Atheros-based cards listed as "Airport Extreme" (i.e. as fitted to real-Macs) appear unaffected by the above issue.

     

    As such, update with caution and be ready to change to WEP or Open-encryption with MAC @-filtering...

  2. In that case, I can confirm that Atheros cards, as used in Apple Macs, appear unaffected by the 10.8.4 update. I switched from a Broadcom-based DW1395 'G' card to an ex-Apple Mac Atheros 9281 'N' card a couple of weeks ago in my D630 nVidia and no side affect to wifi after updating to 10.8.4.

  3. No, SMC 2.3f35 translates to 02030F00 0035.

     

    Correct, the Apple link does not list and specific SMC value for the MBP9,2; as such, you're gonna have to experiment with other SMC values and corresponding SMBIOS plist. Just make sure both match, i.e. SMC & SMBIOS plist that match the same Mac model. In your particular case, look for Ivy Bridge models: MBP9.1, MBP9.2, MPBRet10.1 or MBA5.2

  4. That's perfectly normal. T9300's Tjmax is 105°C, so you're well within the expected operating T°. My own T9300 runs at similar temperatures. I myself upgraded from a T7500 and you're right: the performance improvement is quite noticeable.

  5. D830 with T9300 C2D + nVidia chip + 4Go RAM + SSD all make for a very good Hackintosh platform. 'sounds like you did a good tuning for a D830 that should now run ML very smoothly. Enjoy that Hackintosh. 

  6. I'm really sorry, I thought the article mentioned the default SMC value and how/where to get different SMC values clearly enough...

     

    Looking at the SMC values mentioned in the article, I also thought the correspondance was obvious enough:

    [...]
    By default, FakeSMC is using SMC version 1.30f3 which is displayed in Data field as 01300F00 0003.

    [...]

    Mario and I tried the SMC version listed for the 15″ MacBookPro5,1 -> 1.33f8 (SMC 1.2). This translated to 6bytes Data 01330F00 0008.

    [...]

    NB: most of this derives from Prasys’ own work.

    [...]

    6bytes, eh?

    01 | 30 | 0F | 00 | 00 | 03 -> 1.30 f 3

    01 | 33 | 0F | 00 | 00 | 08 -> 1.33 f 8

     

    Now try and establish what could it be for 1.68f98 or 1.69f4 (hint hint).

     

    Remember: no matter what SMBIOS profile you choose or make, if you do not modify the default SMC value of FakeSMC.kext (which, I repeat, is 1.30f3), well that's what you'll always see in your System Profile...

  7. It would please me that you read the article properly!

    1. it clearly explains how to edit the FakeSMC plist
    2. it clearly explains what to do to determine the Mac model/SMBIOS/SMC that best matches your own Hack
    3. illustrations are provided

    How much more could one need???  <_>

     

    And, where did you get that SMC 1.30f3 corresponds to the MPB9,2 ?

  8. Yes, I guess you would.

     

    Pre-release 10.8.4 versions were known to break wifi but I don't have the details. We need to look into that. I was fortunate enough to purchase and install an Atheros 9281-based 802.11n Apple Mac card  in my D630n just a couple of weeks ago and that works OOB, regardless of the version. Consequently, I retained full wifi services after updating to 10.8.4.

  9. 10.8.4 pre-release versions were known to break Wifi, but until you say more about your own specs, there's little we can do or say.

     

    If you're not intending to use MLPF on that D630, don't even think of running ML; there's really no point at all. However, since you're able to install an earlier ML release properly, I recommend that you make a new SL or Lion USB installer from that ML installation. This will get rid of all the trouble you encountered with your virtual machine.

  10. You've installed ML with MLPF hack on a D630 with X3100 graphics. Did you read the McRumors thread at all? The MLPF hack does not support upgrading ML in the standard way, at least not without re-running MLPF!

     

    The procedure listed in the guides covered ML 10.8.0 to 10.8.3. You need to go back to the updated MLPF web site for the procedure that supports 10.8.4.

     

    You'll probably have to start all over again.

  11. I would suggest you redo an EDP system build after your update to 10.8.4. With the reintroduction of AppleACPIPlatorm v1.7 in /S/L/E folder, you're likely to experience kext cache issues. The EDP system rebuild should take care of this.

     

    If not, try to manually remove the offending kext from /S/L/E and re-run myFix (full).

  12. I can't remember if I coded MBP5,1 in that FakeSMC version, so check it! Disable PStateMenu to verify native SpeedStep operation. There's also a good chance that you can run without NullCPUPowerManagement (or maybe you do already), in which case, ensure your Chameleon boot plist has P & C States checked.

     

    Are you using a D830 or D630 nVidia DSDT?

  13. Updated my D630 nVidia 135M successfully using Combo Update 10.8.4.

    D630n_10.8.4.jpg

    On 1st reboot, I had no keyboard and noticed the CPU reported as a 1.2GHz C2D only. All was Ok after subsequent 2nd reboot. The update installs AppleACPIPlatform kext v1.7 in S/L/E. Like Bronxteck, I strongly recommend to delete that kext to only retain EDP's v1.3.5 in /E/E to avoid cache issues and rebuild permissions & caches with myFix.

     

    Nothing else to report. Looks pretty safe to update.

     

    EDIT: Oups! 'just realised I had updated my FakeSMC kext to v5.1.67 and made a mistake when modifying the SMC keys. That would explain the strange CPU speed report I was getting on occasion!

  14. The latest VoodooHDA does work on the D830, yes.

     

    Re: USB device disconnected after sleep, that is perfectly normal. When the computer goes to sleep, the USB ports are no longer powered; as such, all connected device get disconnected. The only way to somehow circumvent this is to enable "USB Wake" in the BIOS so that power is retained to USB ports when the computer is connected to the mains. That is however not effective when running on battery.

  15. I recommend the combination of 2 tools:

    1. Ukelele Logitech keyboard layouts for full keyboard mappings (just copy the appropriate Logitech layouts from within the app package to /Library/Keyboard layouts then select these new layouts to the list of input sources where they're automatically added)
    2. DoubleCommand for special keys assignation such as Windows key as Command key or PC-Style Home/End keys recognition

    Keyboard_layouts.jpg Languages_selection.jpg

    DoubleCommand.jpg

    • Like 1
×
×
  • Create New...