Jump to content

Hervé

Administrators
  • Posts

    10026
  • Joined

  • Last visited

  • Days Won

    561

Everything posted by Hervé

  1. I would have expected you to have a battery profile in addition to your mains profile. -> E.g., on battery: pc21:~ admin$ sudo pmset -g Active Profiles: Battery Power -1* AC Power -1 Currently in use: hibernatemode 0 displaysleep 15 lidwake 1 acwake 0 halfdim 1 sleep 20 ttyskeepawake 1 disksleep 10 hibernatefile /var/vm/sleepimage ring 0 pc21:~ admin$ -> E.g., on mains: pc21:~ admin$ sudo pmset -g Active Profiles: Battery Power -1 AC Power -1* Currently in use: womp 1 autorestart 0 halfdim 1 hibernatefile /var/vm/sleepimage ring 1 networkoversleep 0 disksleep 10 sleep 30 hibernatemode 0 ttyskeepawake 1 displaysleep 20 acwake 0 lidwake 1 pc21:~ admin$ I'm inclined to think that your battery manager is not working properly... Which kext are you using?
  2. The late xxxx/ForceWake message is related to sleep image file. You need to do 2 things: 1) disable hibernation (in Terminal, type sudo pmset hibernatemode 0) 2) delete sleep image file found in /var/vm (in Terminal, type sudo rm -f /var/vm/sleepimage) If required, boot in safe mode (-x Chameleon boot flag).
  3. Don't worry, there's no reason why issues would suddenly pop up thereafter.
  4. EDP does not support Yosemite yet.
  5. nVidia description is just a text description in the DSDT. It's easily changed. Theprocedure has been described in an article on DSDT patching in the Articles page of the web site. Have a look at it. BIOS versions have been mentioned in the dedicated pinned thread on the matter. For the rest, I guess your /Extra is not properly set/tuned. There is no need for the VBIOS option and GE should be set to Yes.
  6. Seems you don't have graphics acceleration. We need better details than that for your specs: open up Terminal app and enter lspci -nn command (needs lspcidrv kext install as a pre-requisite). Then post the resulting info.
  7. 'never experienced such thing; silly rumours or quick conclusions as far as I'm concerned.
  8. That old ISO should be considered totally obsolete these days. If you have no means to create a myHack installer, then download and burn Nawcom's ModCD and boot your bought copy of 10.6.3. That should get you there to start with. DW1390 works natively, so you should have no problem whatsoever with that wireless card. If you have no Ethernet, then download the appropriate bootpack on a USB key from a Windows PC, then copy from that USB key to your Hackintoshed D620 to get whatever might be missing (DSDT, plists, kexts). If you can only boot with the old ISO, you can still subsequently make a myHack USB installer by separately downloading myHack + the D620 bootpack on a USB key; you'll just have to run myHack using the bootpack and your bought 10.6.3 media.
  9. Yosemite is only at DP1 and not fully finished; its hardly been out 2 weeks to dat… Wait until GM before you consider it. There are lots of things that are not supported yet. This being said, ML, Mavericks and Yosemite can only work on the nVidia-based D830 so make sure you have that model. You should not have encountered any problems updating to ML 10.8.5 from 10.8.4 on such model, whether you updated through Apple Menu or through Combo update. Something wrong must have been done, unless of course it's the GMA X3100 model that you have. If indeed it were the X3100-based D830, you can only install ML at best and every time you update, you have to re-run MLPF hack. Do not bother with Mavericks or beyond on the X3100 model, there is no graphics support. PS: it's very common to obtain a "installation failed" with ML, whether at initial install, after update or even with other application installation. It appears to be cache related but can be considered a false negative and everything is in fact Ok. It's been mentioned several times before.
  10. I don't use myHack, no, it's a Clover-based temporary installation. In fact, I boot Clover off the USB installer key then select the Yosemite partition that I created on my SSD that has existing Chameleon ML + Mavericks partitions (I did not want to break those Chameleon installations). As such, my kexts reside on the USB key, in the /EFI/CLOVER/kexts/10.10 folder, not in the /S/L/E folder of the actual Yosemite partition. In that respect, the 10.10 installation on the SSD is 100% vanilla. The purpose of lspcidrv kext is to support the lspci Terminal command (to list PCI devices) and the Bluetooth kext is just a patch of the vanilla kext that includes PCI details of the Dell DW350/DW360 BT devices; it allows to turn Bluetooth On and Off through the Finder's bar BT icon.
  11. VoodooBattery working Ok on my D630 Yosemite installation. I'm using this version (in case there are several): VoodooBattery.kext.zip The only kexts I use are: AppleACPIPS2Nub.kext AppleHDADisabler.kext ApplePS2Controller.kext BCM5722D.kext FakeSMC.kext Patched_10.7_AppleRTC.kext VoodooBattery.kext VoodooHDA.kext and more specifically, but not essentials: lspcidrv.kext CSRBluetoothHostControllerUSBTransport.kext
  12. Keyboard remapping has been mentioned before and tools such as Ukelele (which includes pre-defined Logitech layouts) or DoubleCommand were recommended. You can do a search on the forum for that.
  13. Until you suss out which graphics you have, you'll probably never go anywhere clear. Open up Terminal and type the lspci -nn command (needs lspcidrv kext installed).
  14. No guide means noone here had one to test/install OS X. Time for you to take up the job...
  15. Yup, there's no KP at all, only graphics not initializing...
  16. Got the laptop back for a couple of days. Volume adjustment fixed by setting VoodooHDA Info plist "fix" parameters to true: <key>VoodooHDAEnableHalfMicVolumeFix</key> <true/> <key>VoodooHDAEnableHalfVolumeFix</key> <true/> <key>VoodooHDAEnableMuteFix</key> <true/> <key>VoodooHDAEnableVolumeChangeFix</key> <true/> fn-F6 / fn-F7 volume down/up buttons now operate properly, as is audio icon volume bar or audio pref pane. Got to test the DisplayPort output and it appeared to natively work Ok (extended/mirror modes): Initial post & boot pack updated accordingly.
  17. 1st of all, you would need to post the full specs of your system. 2ndly, the D830 pack may not suit your system, most specifically because a DSDT table is by nature very model specific. You can refer to the D Series X3100-based ML with full QE/CI guides to try and make your own ML installation with full graphics installation. But you would really need to adapt any kext pack you grabbed from an existing D model...
  18. Patel posted a guide for nVidia-based E6410 a long time ago; did you use it? @Blubaze94, I suggest you try and follow that guide for your E6510; it's in the Supported Models with Guide section...
  19. Intel wireless cards are not supported... Patel's E6410 nVidia guide details the process to follow for Mavericks. The only difference is that he had a lower res screen. However, that usually isn't an issue with nVidia GPUs. Did you use that guide at all?
  20. Having done it several times on a D830 nVidia, I can also confirm that updates can be made directly from AppleMenu/AppStore or via Combo Updates; these work fine whether you run ML or Mav. ML and/or Mav updates are no problem on Hackintoshes. For upgrades, Bronxteck explained it all -> re-install over your existing ML installation to keep your setup and files or do a brand new installation erasing the existing ML partition. You may not have a fully tuned installation which could explain the issues you encountered.
  21. Then, your graphics are not initialising properly. NVS 3100M is based on GT218 GPU, which I believe to be same family as GPUs fitted to GeForce G210 desktop cards (cards that are supported OOB). You probably need to actually choose in BIOS between the built-in Intel or on-board nVidia...
  22. Tested Ok in Yosemite 10.10 DP1. Same method as described above, patching CellPhoneHelper.kext from 10.10.
  23. AGP graphics card? I don't even know if that is supported... -> Give Nawcom's ModCD a try!
  24. Well, that's just cosmetic; the computer might actually still run at lower speed...
  25. You'll have to check if the M4600 can take those (something outwith the scope of this forum you'll understand). For wireless, please refer to the dedicated thread re: supported/unsupported cards in R&D->Wireless subsection.
×
×
  • Create New...