Jump to content

Hervé

Administrators
  • Posts

    10041
  • Joined

  • Last visited

  • Days Won

    563

Posts posted by Hervé

  1. Yes, you will always be prompted for that BIOS system password. Like you, I initially thought that was odd, but that's the way it works I'm afraid...

     

    So you don't seem to have Sleep functionality working... How about when you simply close the lid?

     

    Did you install the ACPI (CoolBook) fix in EDP at system build? That will install AppleACPIPlatform kext v1.3.5 in /E/E and you should then delete the kext of similar name (v2.0 in all likelyhood) from /S/L/E. Remember to re-run myFix (full) afterwards.

  2. No, there's no need to redo a System Build after changing BIOS and/or hibernate settings and order does not matter at all. You probably don't need SleepEnabler kext, so if you have it in /E/E, delete it and re-run myFix (full).

     

    You can update safely to SL 10.6.8. Use the Combo update but redo the EDP system build before you reboot.

  3. First of all, make sure your BIOS is configured as per recommended settings in the dedicated thread. Then, make sure your Hibernate Mode is set to 0.

     

    Once EDP System Build is done, you should have no problem whatsoever.

     

    Intel 3945 is actually present in DSDT table. Don't hesitate to decompile, modify your text table source and recompile it to reflect true wireless card. This is just cosmetic...

  4. We've got an open list of supported/unsupported cards & dongles in R&D -> Network section: https://osxlatitude.com/index.php?/topic/2120-wireless-cards-inventory/

     

    I'd also invite you to consult the wiki pages of InsanelyMac that covers supported HW components per OS X version quite well. Of course, this is only as good as contributors make it, but we do try and contribute there too! http://wiki.osx86project.org/wiki/index.php/Main_Page

    There's a substantial list for 10.8.2: http://wiki.osx86project.org/wiki/index.php/HCL_10.8.2#Wireless

     

    In all cases, I can only recommend to check the chip manufacturer's site and check for OS X support. There aren't that many: Broadcom, Atheros, Ralink are the main ones... For instance, if you're looking at Ralink-based card or dongles, look here: http://www.mediatek.com/_en/07_downloads/01_windows.php?sn=502

     

    If you want to look at Realtek, same thing, consult their web site and look up each family of wireless NICs. For instance: http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=21&PFid=48&Level=5&Conn=4&DownTypeID=3&GetDown=false&Downloads=true

     

    Then you can easily do a search on the net for chip # and see what pops up. That should give you some indications of potential cards or dongles.

     

    The main conclusion is that you have to do some homework, as always...

  5. Which OS X version are you using?

     

    This kind of connection issue was reported with 10.8.4 for cards that are not supported OOB but require a patched kext (eg: DW1395). I have that exact same card and it works OOB on clear/WEP/AES networks throughout the whole 10.6 to 10.9 Mac OS X range.

     

    Check that you don't have a wireless kext lying around in /E/E. You could also remove all wireless reference from Network System Preferences panel and restart.

  6. In System Preferences you can override keys.

     

    Or simply use Logitech keyboard layouts provided in Ukeleke dmg image. Copy them to /Library/Keyboard Layouts, then select Logitech from Input tab of Language Pref Pane to activate.

  7. Again, Intel cards are not supported and never will be until Apple decide to use them in their Macs (so it could be a very very long wait!).

     

    EDP will only display wifi cards for those modeld that actually require kexts! Bear in mind that many cards are natively supported because Apple use similar hardware in their own products (eg: DW1390, DW1490, Atheros AR5B91, etc.). As such, these models do not require any additional kexts and, quite naturally, EDP will not display anything for those...

  8. There's no EDP entry for that model because we have not made one up yet. Usually, that means we've had no-one with that model to feed us with his/her /Extra contents once OS X was fully installed and running on the machine.

     

    EDP system builds and bootpacks don't fall up the sky; they're the result of actual successful installations and testing.

     

    This implies 2 important things:

    1. you should not make an EDP System Build for a listed system that does not match your own hardware (unless you've been advised to do so or it is confirmed to work)
    2. get OS X running on your model and feed us your /Extra folder once finished. That'll be your brick to the house.
    • Like 1
  9. As far as I know, D830s have ALPS trackpad, not Synaptics. Scrolling works Ok with severak PS2 kextpacks. By default, EDP installs the ANV-SLice which does provide heavy-finger scrolling (you need to very light finger for regular mouse moves...).

     

    Our D Series are one of the best mastered family of laptops as far as Hackintoshing is concerned; so, yes, our OSXL install procedure + EDP is well adapted to these systems (and has been for quite some time). There is also a dedicated thread in the D830 section re: BIOS settings.

     

    If you want to play around with native SpeedStep and improvement GPU management, read-up the article about fine-tuning with FakeSMC in the Articles section of the web site.

  10. Cham Wizard does nothing to kext cache. It simply allows you to update your bootloader or choose a specific version, adjust your boot plist parameters, select a given SMBIOS plist or select your Chameleon modules.

     

    Kext cache is something totally different and tools like Kext Wizard and myHack can help to rebuild it. If you use myHack, then you should always use myFix to rebuild your cache. Why? Because the kexts you have in /E/E need to be reflected in the PlugIns of the myHack kext placed in /S/L/E. Naturally, that has a direct impact on kext cache if you do any modification to kexts.

     

    Good to hear your down to a proper boot time now. As an order of comparison, my boot time on my D630 nVidia with ML went from 1min to 20seconds once I sorted out a kext cache issue! So it's very much worth to get kext cache in order.

     

    I'd keep that original ACPIPlatform kext away as it's often found to slow down shutdowns and restarts, but no harm trying again with that kext back in /S/L/E. You'll soon find out if it makes a difference or not.

     

    You could also probably check all those empty cases between C States and C4, especially the Drop SSDT if you have your own tables (like DSDT).

  11. You can use EDP to set that up when you do your system build: it's the "emulated SpeedStep" option of the CPU&Power tab. Set it to ON.

     

    In your case, if you prefer the manual method, since you appear to already have the PState kext already installed in /E/E, just copy the PStateMenu plist from /Extra/Storage/LaunchAgents to /Library/LauchAgents...

     

    Brave man! You're running on conservative mode?

  12. Mmm, a 3min boot is more likely the consequence of something wrong (incorrect boot settings, lack of kext cache) rather than a lack of SSD trim.

     

    For instance, on my D630, keeping USBBusFix set to Yes on a previous Lion partition caused a good 1-2min wait after the Chameleon background screen appeared and before the gray Apple logo appeared with the spinning wheel. Add lack of kext cache to that and that could easily exceeds 3mins boot time!

  13. Video card reported as 8400M GS is long known and the way to change this through simple DSDT text edit has been mentioned many times before. Nothing new here...

     

    You should have no problem whatsoever installing SL,Lion or ML on your WUXGA D830 with NVS 140M. It's totally supported with our OSXL process + specific bootpack.

×
×
  • Create New...