Jump to content

Hervé

Administrators
  • Posts

    10042
  • Joined

  • Last visited

  • Days Won

    563

Everything posted by Hervé

  1. Why don't you try to boot your USB installer without cache?
  2. Why did you opt for MacMini5,1 SMBIOS which is a Sandy Bridge platform (Core i5-2xxxM with HD3000 graphics) when you have a C2D platform with nVidia GeForce G210? I'd say that iMac10,1 SMBIOS would be much better (Core2Duo E7x00 with nVidia graphics). Give that a try. Could you post a zipped copy of your Clover EFI folder?
  3. Having swapped motherboards, you effectively have a D430 that happens to be in a D420 casing... Since it's a tad misleading and only likely to cause confusion, claiming or stating to run MLPF'ed ML 10.8.5 on a D420 is best avoided; as such, the title of your thread was renamed and I would invite you to do the same for your video title. Indeed, it's because of the EDP gradual decay (lack of developers and interest oblige) that I started to post full packs that do not rely on the tool. It would seem the VoodooHDA kext you're using that's not fat binary (i.e. 32+64bit compiled) but 64bit-only. The version included in the pack I posted is v2.8.1 and that's fat binary. You can easily check the architecture of your kext with lipo Terminal command. For instance: lipo -info /Extra/Extensions/VoodooHDA.kext/Contents/MacOS/VoodooHDA If it's fat-binary, the command will return something like: Architectures in the fat file: <file name> are: x86_64 i386 If it's 64bit-only, the command will return something like: Non-fat file: <file name> is architecture: x86_64 ` As a test, I've just rebuilt my D430 ML cache and do not have those VoodooHDA-related error messages. Use the version included in the pack... NB: I don't know if it's just the poor quality of the video but you don't appear to run ML with graphics acceleration on that D430. Make sure you (re)configure 32bit kernel mode in the Chameleon o.c.B.plist. I'm not going to bother updating any of those old MLPF threads but the best way to run ML on those platforms with natively-unsupported GPUs is to start with a vanilla 64bit installation (w/o graphics acceleration of course), followed by all ML updates, including the security ones. Once all updates have been installed, proceed with MLPF conversion in order to run the systems in 32bit kernel mode with graphics acceleration.
  4. I believe Jake has mentioned everything that could be looked at: 1) make sure LAN is not disabled 2) try enabling and/or disabling Legacy ROM option
  5. Then you have a problem with your BIOS settings...
  6. Go to System Preferences then Network... If there's no Ethernet listed, click on + button at bottom left corner and select Ethernet as interface to add.
  7. It should make no difference whether PXE is enabled or not (it's used to boot OS from LAN) but I never keep PXE on. The Mausi kext is clearly loaded, therefore check your Network Preference Panel. If the Ethernet still isn't there, you should now be able to manually add it.
  8. Then install it manually: copy the kext to /Library/Extensions repair permissions and rebuild your cache: sudo chmod -Rf 755 /L*/E* sudo chown -Rf 0:0 /L*/E* sudo touch -f /L*/E* sudo kextcache -Boot -U / If you obtain an error message "....77", repeat the touch + kextcache commands.
  9. http://www.insanelymac.com/forum/topic/304235-intelmausiethernetkext-for-intel-onboard-lan/ https://github.com/Mieze/IntelMausiEthernet
  10. Apple removed the built-in facility to have a Display icon on the Finder's bar (that's what the "menu line" is called) when Mountain Lion was introduced back in 2012. If you wish such a tool, you can refer to this old thread on the matter (I personally still recommend (and use) Display Menu app today)… Do think of using the forum Search facility. Re: HDMI audio, make sure to use: patched AppleHDA patched SNB framebuffer Everything is already available here.
  11. You've not bothered to apply any of the changes suggested in post #7.
  12. "I can not activate the the Monitor icon on home screen"... Sorry, I don't understand; what do you mean?
  13. Seems Ok. You say you're booting off an external USB disk. Did you try to boot with the internal HDD removed?
  14. Well, those offending kexts sure aren't in the cache or list of kexts to cache; otherwise, they would be listed in the warning about invalid signature. On that basis, we have to conclude that they are injected by Clover through the EFI/Clover/kexts/10.12 or EFI/Clover/kexts/Other folder. There can be no other explanation. 'might be a good idea to post a zipped copy of your full EFI folder...
  15. From Terminal, type the following commands. 1) to remove prelinked kernel (it should auto re-generate): sudo rm -f /System/Library/PrelinkedKernels/prelinkedkernel 2) to remove kext cache: sudo rm -Rf /System/Library/Caches/com.apple.kext.caches/* 2) to rebuild cache + prelinked kernel: sudo touch -f /S*/L*/E* sudo touch -f /L*/E* sudo kextcache -Boot -U / (or: sudo kextcache -system-prelinked-kernel) If you get an error message "... 77", re-type the touch + kextcache commands. Ignore any message "... 17".
  16. Then the offending kexts are still cached. Try and manually delete cache folders + prelinked kernel, then rebuild the cache.
  17. If you've rebuilt your cache and there are still traces of the offending kexts, try and locate them on the disk. From Terminal, type: sudo find / -name NullCPUPowerManagement.kext -print 2>/dev/null and repeat this for the VoodooPS2Controller kext. One question: this EFI folder you're looking at, is at at the root of your Sierra partition or in the mounted EFI partition? Make sure to look in the right place...
  18. @OliverZ: Apple has no native support for mobile Haswell iGPU; that's why all laptops based on mobile HD4200/HD4400/HD4600 iGPU must fake desktop HD4600 model (id 8086:0412). Of course, you could try MBP11,1 or MBP11,2 SMBIOS, but I had no graphics issue using MBA6,2 on my mobile HD4600-based E6440.
  19. When you fake desktop HD4600, I believe it's 0x80860412, not 0x04128086... Use latest CloverConfigurator and there'll be no doubts.
  20. No, you also need to rebuild your cache, otherwise it's as if the kexts were still present. Open up Terminal and use the following commands once kexts have been deleted: sudo touch -f /L*/E* sudo touch -f /S*/L*/E* sudo kextcache -Boot -U / If you use Clover, make sure the kexts are not in the EFI/Clover/kexts/10.12 or Other folder.
  21. Great! Would be useful for other users if you could provide the settings you used (Mac model, PCI ids, thresholds) and the various GPU core/Memory frequency steps you noticed... 162/???? MHz 202/1620 MHz 405/???? MHz 666/3010 MHz
  22. Confirmed to work on Precision M4400 with nVidia FX 770M and Precision M4800 with nVidia K2100M.
×
×
  • Create New...