Jump to content
janek202

Kext Wizard - Easy to use Kext Installer and more

269 posts in this topic

Recommended Posts

KW 3.7.11

 

"save list of loaded kexts into txt file" doesn't save a file! 

 

The "Save As" box opens, I put in a name, choose a location, click "Save" and no file is found. 

Share this post


Link to post
Share on other sites
Advertisement

Where a new version for Yosemite?And fix AppleKextExcludeList.kext

Problem in GenericUSBXHCI!!!!!

Thanks in advanced.

Look at this site:   http://pjalm.com/forums/index.php?topic=7.0  ,DSDT already with the patch for USB 3.0 ports. You will not need this "generic" kext in order to enable the doors. 
 
I applied the patch from this site in my DSDT, and ready never used the kext "GenericUSBXHCI". 
 
I tested both the Mavericks as in Yosemite, and works without problems.

Share this post


Link to post
Share on other sites

Thanks this is awesome! :thumbsup_anim:

Share this post


Link to post
Share on other sites

 

Look at this site:   http://pjalm.com/forums/index.php?topic=7.0  ,DSDT already with the patch for USB 3.0 ports. You will not need this "generic" kext in order to enable the doors. 
 
I applied the patch from this site in my DSDT, and ready never used the kext "GenericUSBXHCI". 
 
I tested both the Mavericks as in Yosemite, and works without problems.

 

Which patch is it exactly?

Fix EHC1 or Fix EHC2 or Fix XHC1 or something else?

Share this post


Link to post
Share on other sites

I have a strange issue with KextWizard:

 

All of the following occurred on a clean install of Mavericks 10.9.4 (AppStore version) and again after a repeated clean install.

 

The first time I ran KextWizard (unfortunately I did not get a screen grab), under the "Target Disk" dropdown menu I had the option to select disks labelled "Mavericks" and "Windows7" (my labels).  I ran the wizard having selected the Mavericks disk but unfortunately I do not know whether this worked as I believe there was an issue with the Kext I was working on.

 

When I rebooted and came back to KextWizard I found that the disks listed under "Target Disk" had changed to "Item 2" & "Item 3" as shown in the image below:

 

attachicon.gif20140805_005642.jpg

 

I tried a few reboots and downloading the application again but I was not offered the option/label "Mavericks" again.

 

I persevered and attempted to select "item 2" in case the issue was only the label and not the actual disk selection but all options were greyed out, as shown in the picture below:

 

attachicon.gif20140805_020133.jpg

 

The same thing happened when I selected "item 3", all options greyed out, as shown below:

 

attachicon.gif20140805_020202.jpg

 

Next I tried not selecting either "Target Disk" and instead leaving the dropdown selection on "choose".  This allowed me to select the options under Extra and S/L/E.

 

When I selected options under Extra and clicked Execute I was prompted to enter my username and password, as shown in the picture below:

 

attachicon.gif20140805_015714.jpg

 

After this had processed I got the following error message:

 

attachicon.gif20140805_015731.jpg

 

I followed the same procedure, leaving the "Target Disk" selection as "Choose" but this time selected options under S/L/E. I was again prompted for my username and password, as shown below:

 

attachicon.gif20140805_015851.jpg

 

this time, I received as acknowledgement that the tasks were finished, as below.

 

attachicon.gif20140805_015904.jpg

 

Other than the, rather unreliable, "Done" screen I have no way of determining whether or not KextWizard is seeing my Mavericks partitions, let alone whether it is making any changes.

 

Does anyone have any idea what's going on? Is this a problem others have encountered?

 

 

It's the same for me...  Impossible to use kext wizard... I don't know why---

Share this post


Link to post
Share on other sites

Hello Janek202

 

Great App! I've been using her for years, with the recent OS X El Capitan changes some things are now broken like Repair Permission. Also would you be willing to add the option for installing Kext Extensions into /Library/Extensions/ along with /System/Library/Extensions/ and Extra and Extensions.mkext on Desktop? Kext Wizard would then be able to do-it-all, you could even add the option to install Kexts into /EFI/clover/kexts/10.x/ folders if you wanted to just go completely overboard.  :w00t:

 

Obviously this can all be achieved manually with terminal but your Apps a heck-of-allot easier!

 

Gratitude,

 

Robert aka Mrengles

Share this post


Link to post
Share on other sites

 

you could even add the option to install Kexts into /EFI/clover/kexts/10.x/ folders

 

But what on earth is so hard about copy/paste?

Share this post


Link to post
Share on other sites

Nothing wrong with copy and past... If you would have quoted/read my posted correctly you would have seen that.

 

...you could even add the option to install Kexts into /EFI/clover/kexts/10.x/ folders if you wanted to just go completely overboard.  :w00t:

 

I can quote parts of post and make people look like an idiot too.

 

 

... would you be willing to add the option for installing Kext Extensions into /Library/Extensions/ along with /System/Library/Extensions/

 

But what on earth is so hard about copy/paste?

 

I guess if you want more specifics about the process, the hidden EFI portion needs to be mounted every time you want to make changes. An updated Kext Wizard, could do that, and install into the right Clover location by getting into from the current running OS.

 

Have a great day!

 

Mrengles

Share this post


Link to post
Share on other sites

Hmmm. O....K. :surprised:

At no point did i try to "make you look like an idiot"

 

Kexts to clover folder need no installation, so no need to use any automated app to do this. EFI is "hidden" for good reason, why people always find this to be problematic i do not know.

Share this post


Link to post
Share on other sites

Hmmm. O....K. :surprised:

At no point did i try to "make you look like an idiot"

 

Kexts to clover folder need no installation, so no need to use any automated app to do this. EFI is "hidden" for good reason, why people always find this to be problematic i do not know.

 

I don't know either... No need for Kext Wizard either its just saves steps and makes life easier. Do you use an app or Terminal to mount your "hidden" EFI partition? Well if Kext Wizard was updated to install Extensions into the Clover kext folders you wouldn't need to do either. Again it would just make managing Extension with Kext Wizard MORE helpful.

 

A little tip for easy access to the EFI partitions. Add this to your ~/bash_profile

# Mount hidden EFI partitions
alias mountEFI0='mkdir /Volumes/efi0 && sudo mount -t msdos /dev/disk0s1 /Volumes/efi0'
alias mountEFI1='mkdir /Volumes/efi1 && sudo mount -t msdos /dev/disk1s1 /Volumes/efi1'
alias mountEFI2='mkdir /Volumes/efi2 && sudo mount -t msdos /dev/disk2s1 /Volumes/efi2'
alias mountEFI3='mkdir /Volumes/efi3 && sudo mount -t msdos /dev/disk3s1 /Volumes/efi3'
alias mountEFI4='mkdir /Volumes/efi4 && sudo mount -t msdos /dev/disk4s1 /Volumes/efi4'
alias mountEFI5='mkdir /Volumes/efi5 && sudo mount -t msdos /dev/disk5s1 /Volumes/efi5'
Edited by Mrengles

Share this post


Link to post
Share on other sites

 

I don't know either... No need for Kext Wizard either its just saves steps and makes life easier. Do you use an app or Terminal to mount your "hidden" EFI partition? Well if Kext Wizard was updated to install Extensions into the Clover kext folders you wouldn't need to do either. Again it would just make managing Extension with Kext Wizard MORE helpful.

 

A little tip for easy access to the EFI partitions. Add this to your ~/bash_profile

# Mount hidden EFI partitions
alias mountEFI0='mkdir /Volumes/efi0 && sudo mount -t msdos /dev/disk0s1 /Volumes/efi0'
alias mountEFI1='mkdir /Volumes/efi1 && sudo mount -t msdos /dev/disk1s1 /Volumes/efi1'
alias mountEFI2='mkdir /Volumes/efi2 && sudo mount -t msdos /dev/disk2s1 /Volumes/efi2'
alias mountEFI3='mkdir /Volumes/efi3 && sudo mount -t msdos /dev/disk3s1 /Volumes/efi3'
alias mountEFI4='mkdir /Volumes/efi4 && sudo mount -t msdos /dev/disk4s1 /Volumes/efi4'
alias mountEFI5='mkdir /Volumes/efi5 && sudo mount -t msdos /dev/disk5s1 /Volumes/efi5'

 

I see your point about updating Kext Wizard.  If I am going to keep it sitting in my dock, it makes sense for it to be able to work well with the newest OS.  Clover configurator will also mount the EFI partition but I choose to have my EFI partition mounted at all times.  Therefore, I use the Clover prefpane to mount the EFI partition.  The command to mount the EFI partition is put into the NVRAM.plist.

 

post-270804-0-43817400-1441392257_thumb.png

Share this post


Link to post
Share on other sites

Actually its easier to just use 'diskutil mount /dev/diskXs1' where X is the disk number.

 

One simple command :D

 

Well thats even easier. Thanks PJALM!

Share this post


Link to post
Share on other sites

Actually its easier to just use 'diskutil mount /dev/diskXs1' where X is the disk number.

 

One simple command :D

Even easier to use 'diskutil mount EFI' if your partition is labeled EFI.  You can also omit the /dev/ part as well ie. 'diskutil mount disk1s1' works fine.

 

the diskutil command is wonderful.  Before discovering it I used to do 'mkdir /Volumes/EFI ; sudo mount -t msdos /dev/disk1s1'. 

Share this post


Link to post
Share on other sites

Hope somebody can halp me, i have a Lenovo yoga 2 "13" i just int Mac OS X 10.11.6 on it, i need some kext too it, and do i have to boot from usb?
 

13-inch 1,920 x 1,080 touchscreen Full HD
1.9GHz Intel Core i3 4030U
4GB DDR3 SDRAM 1600MHz
1792MB (shared) Intel HD Graphics 4400
802.11b/g/n wireless, Bluetooth 4.0

Share this post


Link to post
Share on other sites

Thanks for a great contribution to the OSX86 universe, it certainly has a lot more options than most other kext helpers out there. Well done.

Share this post


Link to post
Share on other sites

Yes. I used "touch" command, so system takes care of rebuilding cache, instead of rebuilding it manually. At least it should work like that.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By tlefko
      Description
      This esentially an ultra-simplistic version that is stable without the use of a deploy or complicated file installations and copies. Highly recommend using DW1560 wifi card, killer wifi isn't supported. This does include a copy of Clover, which of course I take no credit for. I am only responsible for minor changes in files and plists, as well as placement and instructions throughout the guide (as well as the work used from previous projects). Many files and ideas are sourced from @maz-1, @syscl, and my previous guides Granted, many files are similar or the same but there is significantly less of them and/or they are predeployed into spots where they will work just as well, even if not as efficient on bootup. Esentially, this guide is designed to provide a perfectly working setup with little knowledge of the topic and without optimization (because often they can break things). Most patches on the main plist use patches implemented by him as well. ****This guide does work excellently however and will provide you with a near perfect setup for Catalina for your XPS 9350, and is currently my daily driver as I struggled using the referenced users files as well.
      Styling
      This guide is designed to be literally as thorough as possible to appeal to those who really don't understand many of the things in @maz-1's guide or some of the other users as they assume you would already understand this information. It does not cover complex topics like undervolting etc etc Notes
      Never tested USB C except for charging, works great no issues with sleep, wakeup. power management is defaulted as I found with @maz-1 it had issues when on battery switching from AC USB devices eject on sleep (not really an issue) Haven't implemented a Bluetooth solution into this yet, as I don't really use it -- will be added ASAP (I believe KILLER WIFI will NOT work, must use one of the supported chipsets (DW1560 is excellent) BIOS Setup
      Set all SATA operation as AHCI Disable Secure Boot, Fast Boot For Coil Whine improvement disable C-States Enable UEFI Booting Recommended: Clean Install (Preinstall steps)
      Format a USB (16GB) as Journaled and then proceed to download the latest Catalina Installer Patcher Application Download the latest Catalina installer from within the Patcher App, and select to download a new copy and install to your USB device Download the clover configurator application and mount the EFI of the USB partition, then copy the contents of the Files linked above to the EFI Folder within the EFI partition. ** This is because the App Store installers will often not download a full installer, just an truncated version that downloads the installer files from the interent while installing. Thus, they're not bootable from a USB as they're not complete. That is why you should use this method to make sure the installer is usable for bootable media.
      Install Steps
      Simply use F12 to boot from the USB device, and select the USB Device and then boot from the Install mac OS partition. I have defaulted the installer to boot into verbose mode so I can easily see the errors you guys are seeing if you encounter them. If everything goes well, you can disable these from the boot arguments selection of Clover Configurator Boot into the USB Device, and follow the steps to format your SSD from the installer to install Mac OS Catalina. NOTE THE TRACKPAD WILL NOT FUNCTION AT THIS POINT, BUT THE TOUCHSCREEN WILL. This is caused by the way the installer handles Kext loading but because the touchscreen is being loaded via usb and the keyboard in a different method (which I can explain in detail if you'd like, the install will be possible. Do not be alarmed if the installer takes a long time to boot into, this is expected Once you have done this step, use F12 to select the USB and boot into the installer from the SSD in the options menu. (you cannot boot natively yet as the EFI isn't copied into the SSD yet. Setup computer as normal, touchpad, brightness, etc, should all be functioning at this point. Same with wifi. Then, you should using Clover configurator copy the contents of the USB EFI into the EFI folder of your SSD EFI partition (in the folder) Now we will add this as a native boot option. Setup computer as normal, touchpad, brightness, etc, should all be functioning at this point. Same with wifi. Then, you should using Clover configurator copy the contents of the USB EFI into the EFI folder of your SSD EFI partition (in the folder) Now will we add this as a boot entry so you can always boot from this natively without the USB. Boot Entry Setup
      Boot into the BIOS of the computer, then navigate to the Boot setup (or entries (not sure what it is called exactly, but it will be a list of the options your computer selects to boot) Click add new, and make sure the USB isn't plugged in. Select the only option that is avaiable, and in FS0 navigate to Boot/BOOTx64. Add this as an entry, then select this as whatever priority you would like. Credits
      Credit Hackintosher.com for basic patches (although @syscl) covered some Credit to @Rehabman Credit to @syscl Kexts, and his contributers (@maz-1) Messages and Facetime
      Using Clover Configuator generate your own Serials, Board Numbers, MLB There are various guides online to do this and as default they're set to essentially Null (Fakeserial) This is fairly straightforward and there is lots of documentation, just don't open these apps until you've done this properly. Finished!
      Congratulations, there really aren't any more steps that are required. Feel free to contact me with any questions. Files can be downloaded here, and issues and help requests can be said here or opened into the GitHub page. Please @ me for a faster response on this page, as I am not that attentive, also, feel free to PM me.  Github: https://github.com/tlefko/XPS13-9350-Catalina Thanks for reading! Files.zip
    • By ayeshch
      Me (and many other people) experience eye-ache from new Macbooks (and windows machines).
       
      I have spent two years of trial-and-error and found that installing macOS Mavericks on my MacBook (pro 13 late 2013, Intel Iris 1536 MB) resolves the issue of eye ache completely. (it is believed that newer systems use harsher version of temporal dithering that causes of a certain group of indivisuals eye aches).

      I cannot stay at Mavericks because of software support and security issues, so the only thing is an issue now:

      How can I take drivers from Mavericks and install them on Catalina? (I tried replacing .kext in /System/Library/Extensions with old files but it didn't work).

      It would be so great if possible!

      Thank you
    • By agrafuese
      Hello, I hope I am posting in the right place...
       
      I am having issues with VoodooInput. It loads fine, no errors or KPs, but movement is erratic. It seems when I am moving the cursor with my index finger and then try to click with my thumb, the cursor will shoot to the bottom of the screen, causing erroneous clicks and a lot of headaches. Sometimes it shoots to the top instead. Sometimes it performs as expected. It's unpredictable. 
       
      I have used VoodooI2C + VoodooI2CHID instead, and they work perfectly fine, but unfortunately they cause KPs. Plus, I like that VoodooInput is a singular kext. This is why I am trying to see if there's any way to fix this issue.
       
      Please see signature for my specs.
       
      Thank you.
    • By tlac
      Simple steps to create macOS Installer for Vmware on Linux or Windows
       
      This guide describes how you can create a Vmware image (vmdk) for installing macOS in Vmware. Most tutorials about this topic require an ISO installer file that was typically created in macOS or you have to download some preinstalled image file from unknown source. None of them are ideal. But if you follow the steps below, you will not need to access macOS and will use official and trusted sources.
       
      First of all download gibMacOS from here and set up
      https://github.com/corpnewt/gibMacOS
        Run the script to download the full macOS installer:
      on Linux: gibMacOS.command on Windows: gibMacOS.bat  
      Install qemu-img converter

      on Linux (Debian or Ubuntu):
      install qemu-tools package

      on Windows use this installer:
      https://qemu.weilnetz.de/w64/
      when you run the installer, it is enough to select the "tools" and "dll library".
       
      Convert the downloaded BaseSystem.dmg to Vmware image
      run the following commmand in that directory where BaseSystem.dmg was downloaded (somewhere here: gibMacOS-master/macOS Downloads/publicrelease/061-44387 - 10.15.3 macOS Catalina)
      on Linux:
      qemu-img convert -O vmdk -o compat6 BaseSystem.dmg recovery.vmdk on Windows:
      c:\"Program Files"\qemu\qemu-img convert -O vmdk -o compat6 BaseSystem.dmg recovery.vmdk  
      Use the previously created image to install macOS in Vmware
       
      I assume you have a patched and working Vmware already. If not, find another guide but in nutshell:
      - confirm the VT-x is supported on your Intel machine (if you are on AMD you may not able to virtualize macOS or you need to do more work)
      - install VMware Workstation or VMware Workstation Player (free for non-commercial use)
      - use an unlocker to patch the Vmware to support macOS guest
       currently this works well: https://github.com/BDisp/unlocker/
       
      So when you are here you have a patched Vmware and a Vmware image (recovery.vmdk).
      Run Vmware and create a new virtual machine by choosing macOS guest. But add another hard disk as well with selecting to use an existing virtual disk. Browse the recovery.vmdk. You will get a warning about the image is not in the latest format but choose to keep the existing format.
      After you installed the macOS, install the vmware tools as well.
       
      Tested on Windows 10 with macOS Catalina 10.15.3 in Vmware 15.5 Player
       
      Comments are welcome.
       
×