Jump to content

Search the Community: Showing results for tags 'cache'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • InsanelyMac Lounge
    • Front Page News and Rumors
    • Reader News and Reviews
    • Forum Information and Feedback
  • OSx86 Project
    • New Releases and Updates
    • New Users Lounge
    • Developers Corner
    • Tutorials (The Genius Bar)
    • Technical FAQ
    • Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • Desktops
    • Notebooks
    • Netbooks
    • Tablets
    • MacMod of the Month
    • Multi-booting and Virtualisation
  • International
    • Your Language
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Русский
  • Apple World
    • Mac OS X
    • Apple Computers and Hardware
    • iOS Devices
    • Mac Applications
    • Mac Programming and Development
    • iOS Programming and Development
    • Mac Gaming
    • Mac Accessories
  • Discuss and Learn
    • Windows Discussion
    • *nix
    • Apple Opinions and Discussion
    • The Great Debates
    • Internet(s), Servers, and Networks
    • Buying Thoughts, Reviews, and Recommendations
    • Mods and Overclocking
    • The Big Issues [Real Life]
  • Everything Else
    • Creativity
    • Thunderdome (Random Stuff)
    • Laughs
    • The Marketplace


  • Kexts
    • Graphics Cards
    • Audio
    • LAN and Wireless
    • Other
  • Kernels
  • Bootloaders
  • DSDTs
    • Patches
  • Pandora
  • Apps
  • Miscellaneous
  • Customization

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start




Website URL







Found 7 results

  1. BEFORE TRYING THIS, DO THE OBVIOUS SOLUTION! REPLACE YOUR OPTIOFIX EFI FILE WITH VERSION 2, OR WITH VERSION 1. ONLY PROCEED IF DOING THIS DOES NOT WORK. Alright, so my first attempt at helping people that isn’t in a private discord. Hope this goes well. No one has posted this as a direct solution to someone asking for help with this error, so I thought I’d be the one to share it.

 I encountered this problem when I rebooted after making some minor changes and discovered I couldn’t boot back into the disk. All over the web, people keep suggesting clover-side tweaks and replacing kexts, and while they may solve the problem for some, absolutely nothing was working for me (and a few others), even when booting with no kernel cache at all. No boot flags worked, no .efi files would solve it. 

Holding spacebar in clover, no change. So, the solution ended up being system side, and not clover related. You needed to delete your prelinked kernel from the HDD and rebuild it. 

To do this, you just have to be able to get to your recovery drive or use an install USB that’ll give you access to the disk. Clover got me into my recovery drive just fine, another hint that it wasn’t related to clover - but regardless, whatever works for you. After you’re in a terminal, type the following commands.

 Df -h This will list all of your volumes, make sure you’re targeting your installation drive.

 If your volume has a space in the name, such as "Mac OS HS", you'll need to format it as such: "Mac\ OS\ HS" - This is simply how the command line associates spaces. touch /Volumes/[NAME HERE]/System/Library/Extensions && kextcache -u /Volumes/[NAME HERE]

 In my case, I replaced [NAME HERE] with my installation drive - "macOS\ 10.13". Chances are, this command will give you the error "Child process [directory] has exited due to signal 10" The line immediately after that will give you another bit of extremely important information that you need to take note of. "Error 107 rebuilding /System/Library/PrelinkedKernels/prelinkedkernel" That directory is what we're going to be targeting to fix our system. So, time to nuke it. rm -rf [location to /prelinkedkernel/prelinkedkernel] MAKE SURE YOU DOUBLE CHECK IT IS EXACTLY WHAT WAS OUTPUT WHEN YOU TRIED THE COMMAND ABOVE.

 IMPORTANT: YOU MAY RECEIVE A READ ONLY ERROR! DO NOT PANIC. I've done this on multiple machines and it really is hit or miss whether or not this will appear. Regardless, the solution is simple. The following code tag only applies to if you encounter this issue. Fsck mount -uw / RE-ENTER THE FOLLOWING COMMAND! You need a more specific location now. rm -rf /Volumes/[NAME]/System/Library/PrelinkedKernels/prelinkedkernel touch /Volumes/[NAME]/System/Library/Extensions && kextcache -u /Volumes/[Name] Now you should be receiving "/Volumes/[NAME] locked; waiting for lock." This is a good thing. Wait a few seconds, you'll receive "Lock acquired; proceeding." After that, you'll be back at -bash-3.2#, and it will appear as if nothing happened. Again, this is expected. For people who didn't have to use the Fsck command, simply type the following and receive the usual "Waiting for lock; Lock received" response. touch /Volumes/[NAMEHERE]/System/Library/Extensions && kextcache -u /Volumes/[NAME HERE] Now, use your up arrow on the keyboard to re-enter this command. If nothing happens, you're golden. If it detects kexts with invalid signatures, that's still okay - but for future reference, don't go the ##### approach/philosophy of installing kexts to your system drive. Take this as a warning. Go ahead and reboot, and start your installation just like normal. You'll now get past the 0x1 error. Congratulations! If you get hung up anywhere, go back to clover and add “-f” to the boot flags, then boot again. You should make it back to your desktop with no damage whatsoever.

 Like nothing ever happened! Now, as for what causes this, I honestly have no idea. All I know is when you have a working system, make some kind of modication/tweak/installation that HS doesn't agree with, you can possibly get this error on some systems. It's rare, but exists, and unfortunately this is the only way I've been able to get past it. It's not too much work, so don't be too intimidated. You'll have your system back in no time. If you'd like some personalized 1-on-1 support, read my signature and contact me that way. I'm more than happy to help, or at the very least take some time out of my day to analyze your issue and give my thoughts. Thanks for reading my first guide, I'm hoping to publish some more fixes to make High Sierra as painless as possible for every user.
  2. Hi, on my gear (i7-3770 16GB GA-Z77X-UD3H GTX 760 2GB) Web Driver works only 1-3 reboots after instalation. After this I`m geting black screen in middle of loading. I can login remotly to my machine when screen is black. After rebuilding cache manualy or with kext Utility screen work again! I have MacOS Sierra 10.12.6 with all updates nVidia Web Driver 378.05.05.25f04 installad Lilu.kext and NvidiaGraphicsFixup.kext On macos default driver I`m getting same results. Latest Clovers is my boot loader. How I can fix this up permanently ?
  3. This tool allows the rebuild of the kext cache of Mountain Lion in both locations S / L / E and E / E. From a Mailor's guide and modified by myself with the controls provided by Fiox89. Is ready to use! Enjoy! Good Hack! PS extract before use. Is in zip package. To repair permissions use Disk Utility. kextcache.sh.zip
  4. I will send 10$ via paypal to the one who solves this problem for me! This has been bugging me for too long now! (Thats ok as long as i don't advertise it in the title, right?) Don't get intimidated if you're not into video editing, this is probably a problem unrelated to FCPX! So, i just installed a Final Cut Pro X on my Hackintosh with Yosemite (10.10.5). However, the program won't generate any thumbnails for the videos. I have to skim the clips to get a preview of the content. After further investigation i discovered that neither did i get any audio waveforms, and the program used the original video files instead of the optimised ones, even though the transcoding had been successful. When taking a look at all my libraries, i saw that none of them had written any cached files (which contains the exact files I'm missing in my library). Now, this could of course be a fault in the program itself, but i don't think so. I have the EXACT same problems in iMovie and earlier versions of FCPX. I think this means that there has to be something wrong outside the program itself. My FCPX (all versions + iMovie) can't run with the NVIDIA web drivers, so I'm using the OS X Default Graphics Driver. It seems unlikely that these problems are related, but i might as well mention it! My configuration: Processor Intel i7 3820 @ 4,3ghz Primary Harddrive Samsung SSD 512GB (also containing Windows 10) Graphics Card Nvidia GTX 660 Ti (running OS X default driver) Motherboard Asus P9X79 PRO RAM 16gb Audio Card Focusrite Scarlett 8i6 Bootloader Chimera OS OS X Yosemite 10.10.5
  5. Vi posto la guida, creata da Mailor del forum hwupgrade e modificata da me per la necessità di automatizzare il più possibile la ricostruzione la cache dei kext nella cartella S/L/E e nella cartella E/E ( ma è applicabile, credo, per tutti i comandi eseguibili dal terminale ). Otterremo quindi una sorta di Kext wizard per Mountain Lion che ricostruisce la cache. Per riparare i permessi utilizzate Disk Utility. da terminale, non da root, digita vim kextcache.sh ( abbiamo già creato il file con nome cachekext ) ti si aprirà vim, un programma che scrive formati binari di testo senza cavolate particolari (header rtf etc). i comandi per usarlo sono da tastiera, e corripondono alla pressione dei tasti: i : attiva l'inserimento del testo. scrivendo, editerai di fatto il file kextcache.sh (che inizialmente sarà vuoto) <esc> : se pigi esc esci dalla modalità di inserimento testo :w (duepunti w) salva il file editato (dopo aver premuto esc) :q (duepunti q) esce :wq salva ed esce detto questo, dopo aver dato il comando da terminale, con vim davati premi i scrivi #!/bin/bash sudo kextcache -v 1 -a i386 -a x86_64 -m /System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext /System/Library/Extensions sudo kextcache -v 1 -a i386 -a x86_64 -m /Extra/Extensions.mkext /Extra/Extensions osascript -e 'tell application "Terminal" to quit' & premi esc digita :wq ora sarai tornato alla console. digita chmod +x kextcache.sh, così che diventi un file eseguibile. ora la situazione è questa: il tuo utente è proprietario di un file che risiede nella tua home. questo file è uno script bash che esegue i comandi che hai indicato. Associa il file appena creato all'applicazione terminale e cliccando due volte eseguira il programma e vi chiederà solamente la password! spero di non aver dimenticato nulla. Vi posto anche il tool già pronto per essere utilizzato. E da estrarre perché zippato. PS Per farlo partire senza associarlo basta digitare sempre da terminale ./kextcache.sh kextcache.sh.zip
  6. Cache Kext Ho potuto constatare che il comando da terminale sudo kextcache -v 1 -a i386 -a x86_64 -m /System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext /System/Library/Extensions funzionante da Lion fino a El Capitan o Yosemite, non funziona piu. Su Sierra è stato sostituito da quale comando? Grazie Riparazione permessi Diskutil repairpermissions è stato rimosso in Sierra come il comando in Utility Disco. come si riparano i permessi da terminale? sudo chown -R root:wheeel / ; sudo chmod -R 755 / questi comandi sono validi per l'intero disco? sostituiscono repairpermissions o la vecchia versione di Utility Disco ? Grazie
  7. Hello, I had a working hackintosh with Yosemite dp5 until earlier when I rebooted the system (Clover updated to 2818) and couldn't boot anymore. After selecting the boot option in Clover it restarts after 1 or 2 seconds. I tried booting in verbose and without caches. Does anyone know what to do?