As discussed in the chapter Kernel Architecture Overview,OS X provides a kernel extension mechanism as a means of allowingdynamic loading of code into the kernel, without the need to recompileor relink. Because these kernel extensions (KEXTs) provide both modularityand dynamic loadability, they are a natural choice for any relatively self-containedservice that requires access to internal kernel interfaces.

• Heimdall Kext For Os X Download
• Heimdall Kext For Os Xml
• Heimdall Kext For Os X 8
• Heimdall Kext For Os X Download
• Heimdall Kext For Os Xenon

Open a terminal and navigate to the directory you extracted Heimdall to. Enter the following commands to compile and install Heimdall Frontend: $ cd heimdall-frontend $ qmake heimdall-frontend.pro Open Finder and navigate to the heimdall-frontend sub-directory. VirtualSMC.kext is a requirement - it emulates the SMC chip found on real macs, and convinces the OS that yes, this is a real Mac. Without it, no Hackintosh: (All of the following kexts are available on this repo courtesy of Goldfish64. Each kext is auto-built whenever a new commit is made. The kext that is absolutely required VirtualSMC.kext (or FakeSMC.kext) is as aforementioned essential. This kext is what tells macOS 'Yes this is a real mac', emulating the functionality of the SMC on real Macs (hence the name). Without it, no Hackintosh. Jan 06, 2012 Release: Heimdall Suite 1.3.2 (Binaries) Platforms: OS X 10.4+ (Universal – x86/AMD64/Intel 64) License: MIT License Includes: Heimdall command line tool. Heimdall Frontend. Codeless kext (aka driver). And still getting: 'Handshaking with Loke. Failed ERROR: Failed to receive response!' Aug 08, 2013 be a KEXT, the default answer is generally no. Even if your code was a system extension in Mac OS 9, that does not necessarily mean that it should be a kernel extension in OS X. There are only a few good reasons for a developer to write.

Because KEXTs run in supervisor mode in the kernel’saddress space, they are also harder to write and debug than user-levelmodules, and must conform to strict guidelines. Further, kernelresources are wired(permanently resident in memory) and are thus more costly to usethan resources in a user-space task of equivalent functionality.

In addition, although memory protection keeps applicationsfrom crashing the system, no such safeguards are in place insidethe kernel. A badly behaved kernel extension in OS X can causeas much trouble as a badly behaved application or extension couldin Mac OS 9.

Bugs in KEXTs can have far more severe consequences than bugsin user-level code. For example, a memory access error in a userapplication can, at worst, cause that application to crash. In contrast,a memory access error in a KEXT causes a kernel panic, crashingthe operating system.

Finally, for security reasons, some customersrestrict or don’t permit the use of third-party KEXTs. As a result,use of KEXTs is strongly discouraged in situations where user-level solutionsare feasible. OS X guarantees that threading in applications is just asefficient as threading inside the kernel, so efficiency should notbe an issue. Unless your application requires low-level access tokernel interfaces, you should use a higher level of abstraction whendeveloping code for OS X.

When you are trying to determine if a piece of code shouldbe a KEXT, the default answer is generally no.Even if your code was a system extension in Mac OS 9, that doesnot necessarily mean that it should be a kernel extension in OS X. There are only a few good reasons for a developer to writea kernel extension:

• Your codeneeds to take a primary interrupt—that is, something in the (built-in) hardwareneeds to interrupt the CPU and execute a handler.

• The primary client of your code is inside the kernel—forexample, a block device whose primary client is a file system.

• Your code needs to access kernel interfaces that are not exportedto user space.

• Your code has other special requirements that cannot be satisfiedin a user space application.

If your code does not meet any of the above criteria (andpossibly even if it does), you should consider developing it asa library or a user-level daemon, or using one of the user-levelplug-in architectures (such as QuickTimecomponents or the CoreGraphics framework) instead of writing a kernel extension.

If you are writing device drivers or code to support a newvolume format or networking protocol, however, KEXTs may be theonly feasible solution. Fortunately, while KEXTs may be more difficultto write than user-space code, several tools and procedures are availableto enhance the development and debugging process. See Debugging Your KEXT formore information.

Heimdall Kext For Os X Download

This chapter provides a conceptual overview of KEXTs and howto create them. If you are interested in building a simple KEXT,see the Apple tutorials listed in the bibliography. These providestep-by-step instructions for creating a simple, generic KEXT ora basic I/O Kit driver.

Implementation of a KernelExtension (KEXT)

Kernel extensions are implemented asbundles,folders that the Finder treats as single files. See the chapterabout bundles in Mac Technology Overview for a discussion of bundles.The KEXTbundle can contain the following:

• Informationproperty list—a text file that describes the contents,settings, and requirements of the KEXT. This file is required. AKEXT bundle need contain nothing more than this file, although mostKEXTs contain one or more kernel modules as well. See the chapterabout software configuration in Mac Technology Overview for further information about propertylists.

• KEXT binary—a file in Mach-O format, containing the actualbinary code used by the KEXT. A KEXT binary (also known as a kernelmodule or KMOD)represents the minimum unit of code that can be loaded into thekernel. A KEXT usually contains one KEXT binary. If no KEXT binariesare included, the information property list file must contain areference to another KEXT and change its default settings.

• Resources—for example, icons or localizationdictionaries. Resources are optional; they may be useful for a KEXTthat needs to display a dialog or menu. At present, no resourcesare explicitly defined for use with KEXTs.

• KEXT bundles—a kext can contain otherKEXTs. This can be used for plug-ins that augment features of aKEXT.

Kernel Extension Dependencies

Any KEXT can declare that it is dependent upon any other KEXT. The developer lists these dependencies in the OSBundleLibraries dictionary in the module’s property list file.

Before a KEXT is loaded, all of its requirements are checked.Those required extensions (and their requirements) are loaded first,iterating back through the lists until there are no more requiredextensions to load. Only after all requirements are met, is therequested KEXT loaded as well.

For example, device drivers (a type of KEXT) are dependentupon (require) certain families (another type of KEXT). When a driveris loaded, its required families are also loaded to provide necessary,common functionality. To ensure that all requirements are met, each devicedriver should list all of its requirements (families and other drivers)in its property list. See the chapter I/O Kit Overview, for an explanationof drivers and families.

It is important to list all dependencies for each KEXT. Ifyour KEXT fails to do so, your KEXT may not load due to unrecognizedsymbols, thus rendering the KEXT useless. Dependencies in KEXTscan be considered analogous to required header files or libraries incode development; in fact, the Kernel Extension Manageruses the standard linker to resolve KEXT requirements.

Building and Testing Your Extension

After creating the necessary property list and C or C++ source files, you use Project Builder tobuild your KEXT. Any errors in the source code are brought to yourattention during the build and you are given the chance to edityour source files and try again.

To test your KEXT, however, you need to leave Project Builderand work in the Terminal application(or in console mode).In console mode, all system messages are written directly to yourscreen, as well as to a log file (/var/log/system.log).If you work in the Terminal application, you must view system messagesin the log file or in the Console application.You also need to login to the root account (or use the su or sudo command), sinceonly the root account can load kernel extensions.

When testing your KEXT, you can load and unload it manually,as well as check the load status. You can use the kextload commandto load any KEXT. A manual page for kextload isincluded in OS X. (On OS X prior to 10.2, you must use the kmodload command instead.)

Note that this command is useful only when developing a KEXT.Eventually, after it has been tested and debugged, you install yourKEXT in one of the standard places (see Installed KEXTs for details).Then, it will be loaded and unloaded automatically at system startupand shutdown or whenever it is needed (such as when a new deviceis detected).

Debugging Your KEXT

KEXT debuggingcan be complicated. Before you can debug a KEXT, you must firstenable kernel debugging, as OS X is not normally configuredto permit debugging the kernel. Only the root account can enablekernel debugging, and you need to reboot OS X for the changesto take effect. (You can use sudo to gainroot privileges if you don’t want to enable a root password.)

Kernel debugging is performed using two OS X computers,called the development or debug host and the debug target. Thesecomputers must be connected over a reliable network connection onthe same subnet (or within a single local network). Specifically, theremust not be any intervening IP routers or other devices that couldmake hardware-based Ethernet addressing impossible.

The KEXT is registered (and loaded and run) on the target.The debugger is launched and run on the debug host. You can alsorebuild your KEXT on the debug host, after you fix any errors youfind.

Debugging must be performed in this fashion because you musttemporarily halt the kernel on the target in order to use the debugger.When you halt the kernel, all other processes on that computer stop.However, a debugger running remotely can continue to run and cancontinue to examine (or modify) the kernel on the target.

Note that bugs in KEXTs may cause the target kernel to freezeor panic. If this happens, you may not be able to continue debugging,even over a remote connection; you have to reboot the target andstart over, setting a breakpoint just before the code where theKEXT crashed and working very carefully up to the crash point.

Developers generally debug KEXTs using gdb,a source-level debugger with a command-line interface. You willneed to work in the Terminal application to run gdb.For detailed information about using gdb,see the documentation included with OS X. You can also use the help commandfrom within gdb.

Some features of gdb areunavailable when debugging KEXTs because of implementation limitations.For example:

• You can’tuse gdb to call a functionor method in a KEXT.

• You should not use gdb todebug interrupt routines.

The former is largely a barrier introduced by the C++ language.The latter may work in some cases but is not recommended due tothe potential for gdb to interrupt something uponwhich kdp (the kernel shim used by gdb)depends in order to function properly.

Use care that you do not halt the kernel for too long whenyou are debugging (for example, when you set breakpoints). In ashort time, internal inconsistencies can appear that cause the targetkernel to panic or freeze, forcing you to reboot the target.

Additional information about debugging can be found in When Things Go Wrong: Debugging the Kernel.

Installed KEXTs

The Kernel Extension Manager (KEXT Manager) is responsiblefor loading and unloading all installed KEXTs (commands such as kextload areused only during development). Installed KEXTs are dynamically addedto the running OS X kernel as part of the kernel’s addressspace. An installed and enabled KEXT is invoked as needed.

Important: Note that KEXTs are only wrappers (bundles) arounda property list, KEXT binaries (or references to other KEXTs), andoptional resources. The KEXT describes what is to be loaded; itis the KEXT binaries that are actually loaded.

KEXTs are usually installed in the folder /System/Libraries/Extensions.The Kernel Extension Manager (in the form of a daemon, kextd),always checks here. KEXTs can also be installed in ROM or insidean application bundle.

Installing KEXTs in an application bundle allows an applicationto register those KEXTs without the need to install them permanentlyelsewhere within the system hierarchy. This may be more convenientand allows the KEXT to be associated with a specific, running application.When it starts, the application can register the KEXT and, if desired,unregister it on exit.

For example, a network packet sniffer application might employa Network Kernel Extension (NKE). A tape backup application wouldrequire that a tape driver be loaded during the duration of thebackup process. When the application exits, the kernel extension isno longer needed and can be unloaded.

Note that, although the application is responsible for registeringthe KEXT, this is no guarantee that the corresponding KEXTs areactually ever loaded. It is still up to a kernel component, suchas the I/O Kit, to determine a need, such as matching a piece ofhardware to a desired driver, thus causing the appropriate KEXTs(and their dependencies) to be loaded.

Copyright © 2002, 2013 Apple Inc. All Rights Reserved. Terms of Use | Privacy Policy | Updated: 2013-08-08

• 1Linux
  • 1.2Debian based
  • 1.4Generic Linux Instructions
• 2OSX
• 3Windows

Linux

Fedora

After this step, skip to the instructions for generic Linux distributions below.

Debian based

These instructions are for Debian based distributions including Ubuntu and Linux Mint.

With apt-get

Compiling from source

After this step, skip to the instructions for downloading and compiling below.

Arch Linux

heimdall is available in the official repositories. heimdall-git is available in the AUR for building from source.

Generic Linux Instructions

These are distro-independent instructions.

Installing prerequisites

Use your favourite package manager to install (the development version if your distro has seperate “-dev” packages)of the following pre-requisites:

1. gcc/g++
2. make(automake)
3. libc(glibc)
4. libusb
5. qt5
6. CMake
7. OpenGL
8. zlib

Downloading and compiling

Start Heimdall by issuing either heimdall or heimdall-frontend in a terminal.

OSX

Installing prerequisites

• First make sure you have installed XCode and pkgconfig.
  • There are several different ways you can install pkgconfig, the simplest option is to use Homebrew.

• Open a terminal and navigate to the directory you downloaded, or extracted, Heimdall to.
• Install libusb >= 1.0:
  • The simplest option is to use Homebrew.

• • Alternatively you may download and compile from: http://www.libusb.org/
• Enter the following commands to compile libpit.

• • NOTE: There is no need to run “sudo make install”.

Installing heimdall

• Enter the following commands to compile and install Heimdall:

Heimdall Kext For Os Xml

• • NOTE: The export line is needed to overcome a compile error with 1.4RC and will hopefully be unnecessary soon.
  • NOTE: Do not be alarmed if the sudo make install ends with: make[2]: Nothing to be done for `install-data-hook'
• If you haven’t installed the driver before, enter the following:

Installing the Frontend

• First make sure you have installed XCode from your OS X install DVD.
• You’ll also need Qt 4.7 or later, available from: http://qt.nokia.com/downloads/
• Open a terminal and navigate to the directory you extracted Heimdall to.
• Enter the following commands to compile and install Heimdall Frontend:

Heimdall Kext For Os X 8

• Open Finder and navigate to the heimdall-frontend sub-directory. Open the newly created XCode project.
• From the menu bar select Build -> Build. This outputs heimdall-frontend to /Applications

Windows

Prebuilt package

Heimdall is available for download at http://glassechidna.com.au/heimdall/. However, to get the latest version, you must follow the instructions below to compile from source.

Heimdall Kext For Os X Download

Compile with CMake

Heimdall Kext For Os Xenon

Download and install MSYS2 to set up a MinGW-W64 build environment. After installing, a terminal will launch. Issue the following commands:

After compiling, open a command prompt/Explorer window and navigate to %msys64%home%username%Heimdallbuildbin (where “%msys64%” is the directory you installed MSYS2 to, C:msys64 by default). There should now be two executable files in that folder: heimdall.exe and heimdall-frontend.exe. You can run them from that directory or move them to a more suitable location. Navigate to %msys64%home%username%HeimdallWin32Drivers for the Zadig (driver) executable.

Content of this page is based on informations from wiki.cyanogenmod.org, under CC BY-SA 3.0 licence.