Jump to content
janek202

Kext Wizard - Easy to use Kext Installer and more

272 posts in this topic

Recommended Posts

Not sure if this has been mentioned yet, but a built-in KEXT repository would be the bees knees. -_-

 

I'm not a web developer. Adding all kexts using mails and dropbox, means too much work.

I won't add every single kext manually into my dropbox. I don't know how to create site for that.

 

And I'm working on a new project. New wizard. More info soon.

Share this post


Link to post
Share on other sites
Advertisement
Not sure if this has been mentioned yet, but a built-in KEXT repository would be the bees knees. :(

 

-Stell

 

Uhhh... Wow. Do you have any idea how much work that would be? Might I suggest going over to kexts.com?

Share this post


Link to post
Share on other sites

Since Lion by default doesn't have a kernel cache, and Chameleon by default does not load a manually created kestcache, I think you should add an option in the maintenance section to add a "UseKernelCache" to the boot.plist if the user selects the option to create a kernel cache.

Share this post


Link to post
Share on other sites

Yes but that would load kexts only from S/L/E...

We need to create combo cache from both /E/E and S/L/E and use it at startup. Is it possible? How?

Share this post


Link to post
Share on other sites
Yes but that would load kexts only from S/L/E...

We need to create combo cache from both /E/E and S/L/E and use it at startup. Is it possible? How?

 

just copy the kext from e/e to s/l/e and your good to go

Share this post


Link to post
Share on other sites

I just want to give my big thanks for your work on this tool :)

 

...I think it needs some exposure in the community so it can become more widely adapted, as it deserves!!

 

This is a great community... so exchange, share, help out others to pay thanks to those who helped you out, and always say thank you. Lets keep it alive !

Share this post


Link to post
Share on other sites
Post me a terminal commands how to do that.

this the command that creat kernel cache for my kernel (cyrus_kernel):

sudo kextcache -system-prelinked-kernel -K /cyrus_kernel

 

may the option that specty the kernel name be good.

thanks

Share this post


Link to post
Share on other sites

Hi Janek202. As per "Please report me any bugs or ideas for new features" (I did NOT read through the pages, so a duplicate submission is well possible), here's some *constructive* feedback:

 

- when installing new kexts to E/E, as of now the mkext there does NOT get rebuilt automatically. I basically consider this a bug because it might lead to the kext which got installed to E/E and is not included in the mkext might not get loaded correctly. So now, after installing kexts to E/E, one has to click onto Maintenance, activate 'Extra/Extensions', rebiult mkext. Those extra steps should not be necessary. It would be great if you could fix that. If there is some kind of pro for not auto-rebuild E/E mkext, then please at least ad an option field "Auto-Rebuild mkext", which is *activated by default*; whoever does for some reason *not* want the mkext rebuilt can toggle it off.

 

- please have "Backup kexts that will be replaced" *activated* by default! In times of terrabytes HDs, looking at the tiny size of almost all kexts, and noting the security aspect of backups in general I don't see *any* reason why this option shall not be active by default. Thank you

 

- again regarding kext backups: when I first utilized your tool I was totally startled because even though I had ticked "Backup kexts that will be replaced" I did not find them! I installed to a different volume, and after booting into that volume and realizing I had to restore one kext, first looked into the extension folder there, being used to Kext Utility's approach to simply rename existing.kext --> existing.bak. Then I remembered having read something about a folder 'Kext Backup' being created. Analog to what Kext Helper (and I think OSX86Tools) used to do, I looked on / of the volume to which I had installed kexts to, but to my disappointment did not find any like folder there. After finding and reading your ReadMe I was very amazed that the default backup path is the Desktop of the user account one installed FROM, not the / of the volume on installs TO. That is very awkward, esp. if one installed from as root user (...), and also makes much less sense than backing up to the actual volume. Reason is evident I dare say: when, after running an install for a while, one realizes one has to revert to an older kext, it would be easy to do so just looking on / of that particular volume. The backup on the desktop of some user folder (which might even be on a completely different computer if one installed to a USB volume .....) might simply not be retrievable anymore.

 

Right now I "jerryrig" by, after installing kexts to another volume, MANUALLY creating a folder "Kext backup" on / of that volume, then copy the appropriate date/time folder into folder I created on the other volume.

 

Again, if there is some pro of choosing the current desktop as backup, then, instead of ONE line "Backup kexts that will be replaced" you could change that to "Backup kexts that will be replaced to / of destination", and a 2nd line "Backup kexts that will be replaced to current Desktop". Not too much space lost there, but a highly usable feature addition. And PLEEAASE ;), make "Backup kexts that will be replaced to / of destination" active by default :)

 

- after installing kexts to S/L/E, the option button jumps back onto E/E. Why? That's confusing because (esp. late @ nite .. :) ) I can make one doubt if one really chose the correct destination. This can be considered a bug. I think similar with "Target Disk": if one has chosen "S/L/E" and then changes the target disk, it jumps back to to E/E. But I am not sure about that right now (am not writing from OS X so cannot test)

 

Other than that, awesome tool! Makes deploying h'tosh soooo much easier (and I bet Hagar hates it because he kept on deleting my postings back then when I asked for exactly what you coded, labeling my requests 'forum spam' and eventually even blocked my account - and now look at the popularity).

 

Thank you Janek - RESPECT!

Bugs

Share this post


Link to post
Share on other sites
- when installing new kexts to E/E, as of now the mkext there does NOT get rebuilt automatically.

 

It does. Installation checks if E.mkext exists. If it does it will be updated. I didn't wanted to confuse newbies with new "unknown" files. So basically, if you made an mkext in the Maintenance tab it will be updated after each kext installation.

 

- please have "Backup kexts that will be replaced" *activated* by default!

OK.

 

Reason is evident I dare say: when, after running an install for a while, one realizes one has to revert to an older kext, it would be easy to do so just looking on / of that particular volume. The backup on the desktop of some user folder (which might even be on a completely different computer if one installed to a USB volume .....) might simply not be retrievable anymore.

It shows in your desktop, so you can move it to the location you like. I don't want to keep this kexts like .bak or something, because I think it will be hard to find working kext among others like bak1, bak2, bak3 etc. But I think I will make directory [target disk]/Extra/Backups.

 

- after installing kexts to S/L/E, the option button jumps back onto E/E. Why? That's confusing because (esp. late @ nite .. :blink: ) I can make one doubt if one really chose the correct destination. This can be considered a bug. I think similar with "Target Disk": if one has chosen "S/L/E" and then changes the target disk, it jumps back to to E/E. But I am not sure about that right now (am not writing from OS X so cannot test)

 

It was the simplest way. I had to make something default so after you change partition with Extra and no S/L/E to the partition without Extra but with /S/L/E it won't stay selected on the wrong option. But I will try to make it better.

Share this post


Link to post
Share on other sites
It does. Installation checks if E.mkext exists. If it does it will be updated. I didn't wanted to confuse newbies with new "unknown" files. So basically, if you made an mkext in the Maintenance tab it will be updated after each kext installation.
LOL that's funny - the way I tested it was by DELETING the mkext and see if it gets built. I understand your reasoning - however it will slow down boot and display all these kexts and sub-kexts running down the screen. I think that will confuse nubies even more than a file in a (hidden) directory they will never see anyway.
But I think I will make directory [target disk]/Extra/Backups.
YIPPIE :) The Desktop location could remain as a toggleable option, if you decide to.
But I will try to make it better.
cool, thanks.

 

I also like your other utils and donated from your sig. Solidarności - you Polaks rock :)

 

Bugs

Share this post


Link to post
Share on other sites
this the command that creat kernel cache for my kernel (cyrus_kernel):

sudo kextcache -system-prelinked-kernel -K /cyrus_kernel

 

may the option that specty the kernel name be good.

thanks

hi janek plz add the above command to next wizard

thanks

Share this post


Link to post
Share on other sites

sskwi_en.PNG

 

Hi, is certainly a stupid question but how do I know where should I install the Kext's files?

What is the default location?

 

Many thanks,

 

Vasco

Share this post


Link to post
Share on other sites
Installation and Maintenance can be executed for any OS X partition.

 

Why are my choices: Choose, Item1, Item 2

 

My partitions do not appear.

Share this post


Link to post
Share on other sites

Great.

But does this new utility handle the rights of kext "correct" if i use kext utitlity works but next OS X Diskutility must repair all of them again.

Yes.

Maintenance: First it sets owner (root:wheel) and permissions (755) for the whole System/Library/Extensions. Some system kexts requires other permissions etc. so after that it repairs permissions on whole target disk using: "diskutil repairpermissions".

 

Installation: It sets owner and permissions only for newly installed kexts. Others aren't modified. After that it rebuilds cache.

 

So there's no need to run Disk Utility after using my application.

Don't know if this was addressed in this thread or not, as I haven't read it all. :-P

But, this is an issue I ran into awhile back and I found that the system expects 644 to be applied to the files and 755 to the folders/kext package.

So, running the following commands (or similar) fixes this minor issue:

 

chmod -R 755 /System/Library/Extensions
find /System/Library/Extensions -type f -execdir chmod 644 {} \;

 

It simply applies 755 to all the files/folders/kext packages, then finds just the files and applies 644 to them.

best regards,

MAJ

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 ITzTravelInTime
      Hi guys, this thread is to show you a new and open source app, created by me, that I called TINU:
       
      The name means: TINU Is Not #####, the U refers to a popular software that is used to create Mac OS hackintosh installers (that for good reasons is banned on this forum), but the aim of the name is to explain that this app is a totally different thing from that software and works in a totally different way.
       
      This app basically is a graphical interface for the createinstallmedia executable that is inside the Mac OS installer apps, it is capable to create a Mac OS installer on a drive completely vanilla like what you do using the command line method, and also this method is recommended by apple itself.
       
      Allows you to create easily a macOS install media without messing around with command line stuff and without using disk utility, all you need to do is use the app and then install clover on the usb drive once TINU has finished or leave it as is you want to use it on a Mac.
       
      Features:
        - Simple to use UI that allows you to easily start the macOS install media creation process   - It can work with every Mac OS installer app that has the createinstallmedia executable inside of it's resources folder (including also beta and newly released installers)   - You can use any drive or partition you want that can be erased and is at least 7 GB of size   - Works on Mac OS recovery, so you can create a macOS install media from a bootable macOS installer or from the macOs recovery   - All vanilla, the macOS install medias created with this tool are 100% vanilla, just like you created them using the command line "createinstallmedia" method   - Open source, you will know what this program does on your computer and also you can create your own version by downloading and playing with the source code   - Does not requires to do anything of special first, just open the program   - No need to go in disk utility first, TINU can format your drive for you   - Uses recent and more modern APIs and SDKs and Swift 3 language   - Transparent graphics style available (use alt + s on the keyboard or View->Use transparent style)   - Works using the latest versions of macOS and will also support newer Mac installers out of the box without needing for an update    Features that I'd like to add in the future:    - Advanced section, to customize your macOS install media   - Installer customization: Kernelcache/prelinkedknerel and boot files replacement (a feature that can be handy while dealing with old Macs or with beta installers when you need to mod or change the boot files some times)   - Install clover and configure clover   - Install kexts inside the kexts folder of clover   - Clover drivers customization   - Use custom dsdt in clover   - integrated pre-made clover config templates database from a remote and open repository   - Support for other languages, at least Italian   Rquirements:  - A computer that runs Mac OS X Yosemite or a more recent version (Mac OS X El Capitan is required to use TINU in a macOS recovery or installer)  - A drive or a free partition of at least 7 GB that you want to turn into a macOS/Mac OS X installer  - A copy of a macOS/Mac OS X installer app (Maveriks or newer versions are supported) in the /Applications folder or in the root of any storage drive in your machine (excepted the drive or volume you want to turn into your macOS install media)   Note that this app is under the GNU GPL v3 license so any reuse of the source code must follow the license's terms   TINU 1.1 Stable release:    - Download available here:    https://github.com/ITzTravelInTime/TINU/releases    - Source code:     https://github.com/ITzTravelInTime/TINU   TINU 2.0 pre-release:    - Source code:    https://github.com/ITzTravelInTime/TINU/tree/development    - Download available here:    https://dl.dropboxusercontent.com/s/nvzss51qcieynve/TINU.zip     Frequently asked questions about TINU: https://github.com/ITzTravelInTime/TINU/wiki/FAQs     NOTE: if you have problems with your USB installer of 10.13.4 or newer version not being detected by clover you have to use the latest clover and if it still does not detectets your usb installer you have to remove the invivible file called .IAPhysicalMedia located into the root of the usb installer. This issue is caused by a changement in the apple's createinstallmedia, don't blame TINU for that, tinu does only uses the installer creation method from apple, which has been changed, causing this problem for hackintosh users, this issue should be resolved in the latest versions of clover which will no longer require that you do changements to let your usb dive to be detected, a setting to do this fix automatically in tinu is also comeing in a new pre-release of TINU 2 I leave also some screenshots as well








    • By JDizz
      #UPDATE AS OF APRIL 27, 2018 Thursday, 3:53 PM EST

      SIMPLE INSTRUCTIONS
      After you figure out how to get High Sierra 10.13 or 10.13.4 installed to a USB with Clover Bootloader, and you're loaded onto MacOS High Sierra:

      Download Clover Configurator and MOUNT your partition and OPEN it to reveal your EFI folder. Delete it.
      Simply download the attached ZIP and unzip it by double clicking it. Then copy and paste the EFI folder you unzipped to the location of your mounted partition.

      Done. Enjoy. Special thanks to Jake Lo !


      WORKING [Dell M6800 - High Sierra 10.13.4]
      Sleep/Wake WHILE THE POWER CORD IS PLUGGED IN (Not from closing the screen down, but from clicking the Apple logo and sleep or by timer).
      Wi-Fi (AirPort Extreme) via Broadcom BCM43xx.
      2 USB ports on the LEFT side as USB 2.0/3.0 and the 1 USB 2.0/eSATA on the back.
      KeyBoard.
      TouchPad (With MultiTouch - Fully functional)
      iMessage, iCloud, FaceTime, AppStore work perfectly.
      NVIDIA Graphics work perfectly thanks to the Lilu and NvidiaGraphicsFixUp kext. THIS FIXES THE BLACK OR BLANK SCREEN PROBLEM.
      DVD-Drive/Burning if you even care to use CD, DVD disk.
      Bluetooth (Works even with Apple HomePod =] )
      Ethernet/RJ-45
      2 USBs on right side as USB 2.0/3.0
      Native Sound (On board Speakers and can adjust sound with buttons)
      SD Card Readers
      Adjusting Brightness (Download an app from the AppStore called Brightness Slider -OR- use Night Shift [will not adjust brightness, but will be bearable]).


      NOT WORKING [Dell M6800 - High Sierra 10.13.4]
      Headphone Jack (Excessive Static)
    • By ivanagui2
      VMQemuVGA display adapter driver for OSx86 running as a VirtualBox guest. The binary should work on all OSs from Snow Leopard up to Yosemite 10.10. It allows to set different screen resolutions in VirtualBox from System Preferences.   The changes I've made to the fork have been minimal.
      GitHub project page Binary and source releases Special thanks:
      PureDarwin
      probonopd
      rafirafi
      Zenith432
      VMware, Inc


    • By ITzTravelInTime
      Questo è il thread in italiano dedicato alla mia app TINU, l'app open source che ho creato per creare chiavetta di installazione di mac utilizzando il metodo "createinstallmedia".
      Il nome è l'acronimo di TINU Is Not U (Per le regole del forum devo censurare, ma la U si riferisce ad un programma che piu o meno svolge lo stesso scopo che che per buoni motivi è bandito su questo sito, il punto del metterlo nel nome sta nel sottolineare che la mia app è totalmente divera)
      L'app è pensata per essere molto semplice ed immediata da usare (con un interfaccia grafica progettata con criteri e metodi usati in ambito professionale per lo sviluppo di applicazioni utente) e per essere molto solida e stabile che funziona sempre al primo colpo (a differenza di altri tool che conosciamo ...)
      A livello funzionale quest'app non è altro che un interfaccia grafica per il metodo da terminale "createinstallmedia" che viene sfrutatto dalla stessa per creare la chiavetta, quindi le chiavette create con TINU sono chiavette al 100% vanilla come se le aveste create dal terminale, a questo l' applicazione aggiunge funzioni utili come la formattazione automatica della chiavetta USB che si sceglie di usare in formato Mac OS Extended (journaled) (detto anche HFS+) con mapatura di partizione GUID.
      Tra gli altri vantaggi troviamo il fatto che permette di creare chiavette utilizzando qualunque applicazione di mac che contiene l'eseguibile "createinstallmedia" inclusi installer delle beta ed installer appena rilasciati, e non richiede di fare cose particolari prima come formattare la chiavetta e cambiare lingua al sistema e puo utilizzare applicazioni di mac che si trovano in vaie directory nel sistema e non solo quelle sche stanno in applicazioni ed hanno un nome specifico (nota che l'applicazione di installazione di mac deve essere quella interacche pesa diversi gb e non quella da pochi mb che l'app store puo scaricare alcune volte e che contiene tutto quello che serve per permettere a createinstallmedia di funzionare)
      l'applicazione è completamente aprta ed open source e trovate qui alcuni link utili:
       - Scarica l'app: https://github.com/ITzTravelInTime/TINU/releases
       - Repo github di TINU: https://github.com/ITzTravelInTime/TINU
       - FAQs (in inglese): https://github.com/ITzTravelInTime/TINU/wiki/FAQs
       - Thread in inglese su tinu (English thread about TINU): http://www.insanelymac.com/forum/topic/326959-tinu-the-macos-install-media-creation-tool-mac-app/
      Qui invece ci sono un paio di guide (Anche se l'app è molto facile da usare):
       - Piccola guida su come usare TINU per un hackintosh: https://www.youtube.com/watch?v=fZOZOUt2ErM
       - Piccola guida su come usare TINU per creare cheiavette per Mac "originali": https://www.youtube.com/watch?v=fZOZOUt2ErM
      Attualemente è in fase di sviluppo una nuova versione di questa app che verrà rilasciata a breve e che include diverse novità e migliorie importanti.
      Per chi se lo chiede, il supporto a clover in TINU è pianificato per una versione futura, anche se dei protipi a livvello codice per renderlo possibile, sono gia stati sperimentati con successo.
       
      Spero che anche voi del forum italiano aprezzerete questa app come gli utenti del forum inglese, per idee e suggerimenti, siete liberi di esprimervi :-)

×