Oct 23, 2016 - How to Install & Fix macOS Sierra Bootloader, Ethernet, Audio. And to use WiFi on the laptop, you need to buy WiFi card for that. After that go to Drivers section and choose the proper audio and network options for your system. Also, make you sure that Internal Microphones is select in Input Section. When possible, for Microsoft Windows users, we try to have drivers available for. For Mac OS X users with supported products, if a driver is not provided by the. USB Network & WiFi Adapters USB Serial Adapter USB 2.0 Bluetooth 4.0 LE.
Contents. Audio Device Manufacturers Supported Devices OSx86 versions tested Link Notes Credits AC97 All AC97 implementations 10.4.5 10.4.6 10.4.8 10.5.8 Sound tends to come out of left speaker only on some chipsets. Was recompiled from public Darwin source thx to macgirl. NOTE: 10.4.8 JaS has native Support macgirl Almost Any All Audio implementations 10.4.8 10.5.8 This is a driver which works with almost every sound card. Worked with two computers of mine when any other driver did not recognize them. Machine C-Media 8738 Various CMI8738 cards like Terratec Aureon 5.1, Genius Soundmaker Value 5.1, Hercules Gamesurround Muse 5.1, M-Audio (Midiman) DiO 2448 and onboard incarnations 10.4.1 10.4.3 10.4.4 10.4.5 10.4.6 10.4.8 Audio input is currently not implemented. SPDIF and analog out are fully supported.
The source has been released under a 'BSD like' license. Dogbert C-Media 8738 Various CMI8738 cards like Terratec Aureon 5.1, Genius Soundmaker Value 5.1, Hercules Gamesurround Muse 5.1, M-Audio (Midiman) DiO 2448 and onboard incarnations 10.5 10.6 Audio input is currently not implemented Creative ES1370/1371, CT-5880 Creative PCI128 and VMWare sound emulation 10.4.3 and later 10.4.7 (Tested) 10.4.8 (Tested) Sound shuttering reported from users yet it works. Maxxuss Echo Digital Audio AudioFire 2,4,8,12 and Pre8 10.4 and later 10.5 and later Intel HDA Audio Sigmatel 9223 10.4.8 and later 10.4.9 (Tested) Line In, Line Out (2ch), Mic In, SPDF. TARUGA Intel HDA Audio Realtek ALC882 and bunch of Sigmatel ie: 9200, 9225 10.4.8 Kernel 8.8.1 Only(Tested) Have a try! Line In, Line Out (stereo), Mic In, SPDF TARUGA Intel HDA Audio Realtek ALC262 10.4.8 and later (Requires AppleAzaliaAudio.kext) Line In, Line Out (stereo), Mic In Alfred Intel HDA Audio Realtek ALC262XXX 10.4.8 and later (RequiresTaruga's patcher) Line In, Line Out, (stereo), Mic In, SPDF bronxboyXXX Focusrite Saffire Pro 26 I/O Firewire 10.4.8 Everything works perfectly, have just a problem with bundeled plugins and cubase 4 but audio works like heaven.
Install Universal Binary drivers from the site, Fully Working. (Not tested ADAT in/out and wordclock) everything else works like a charm.
Focusrite M-AUDIO DELTA SERIES PCI. M-Audio Delta 44 (verified). M-Audio Delta 66 (verified). M-Audio Delta 410 (verified). M-Audio Delta 2496 (verified). M-Audio Delta 1010 (works for some).
M-Audio Delta 1010LT (verified). Terratec Phase 88 / EWS88MT / TS88PCI (tested only on EWS88MT). Terratec EWX2496 10.5.8 doesn't support multiple card stacking M-Audio M-AUDIO M-AUDIO FastTrack USB 10.4.5 FastTrack USB being detected as USB Audio Devices. Also most M-AUDIO products include drivers or support CoreAudio with OS X drivers M-Audio M-AUDIO M-AUDIO Quattro USB 10.4.8 Detected as M-Audio Quattro.
Includes CoreAudio M-Audio M-AUDIO Midisport 2x2 10.4.6 Just the drivers from M-Audio website and install. Fully working. M-Audio M-AUDIO Midisport 4x4 10.4.6 Install the MacOSX Driver from the M-Audio Website. Fully working. M-Audio M-AUDIO Firewire410 10.4.8 Grab the latest driver from m-audio.com doesnt work off of the CD.Start the utility from system preferences before opening any sound apps.
M-Audio RME RME Fireface 800 10.4.6 Fireface 800 mac driver works straight away, fully working RME Presonus Firepod 10.4.7 No dirver required. Fully working. Presonus SiS SiS7012 10.4.6 10.4.7 Antiben TASCAM US-428 USB Midi/Audio Controller 10.4.5 original driver for Intel Macs, work also on AMD Systems. Full working Midi Controller and Soundcard with 2 ms latency Tascam ATI-IXP Audio ATI X200 and IXP150 chipset soud controller 10.4.3-10.4.7 Beta driver, Sound on 0x4370 and 0x4341 chipsets ATI AUDIO Terratec Terratec Phase 88 Firewire/FW 10.4.6 Original drivers from manufacturer.
Work perfectly. You might need to restart your Phase 88 after installing to get it to work. Terratec Mark of the Unicorn (MOTU) PCI-424 Card (PCI/PCI-X version) and Applicable Interfaces (tested with 24I/O and 2408mk3) 10.4.8 Stock MOTU drivers for OS X version 1.1.0. Working: MOTU Audio Setup applet, CueMix Console, CoreAudio (tested in Cubase SX 3.1.1.994). Works as a system audio device - all apps that output audio (such as QuickTime 7.0, iTunes 7.0.2) work fine.
Mic Driver For My Computer
PCI express version not working for either Gigabyte GI945GMH-RH or Asrock Conroe945G-DVI mobos, 1.1.0 or 1.1.1 drivers. MOTU Mark of the Unicorn (MOTU) MIDI TimePiece AV USB MIDI Interface (via USB connection) 10.4.8 Stock MOTU drivers for OS X version 1.35. Working: ClockWorks, CoreMIDI (tested in Cubase SX 3.1.1.994).
MOTU Universal Audio UAD-1 DSP Card (PCI version) and Powered Plugins 10.4.8 Stock drivers for OS X version 4.5.0. Working: UAD Meter applet, card configuration, all plugins (tested in Cubase SX 3.1.1.994). Universal Audio Emagic Unitor 8 MK II 10.4.9, 10.5.0 You need the Universal EmagicUSBMIDIDriver.plugin file from the 7.2 Logic Express Installation Disc. Mount the Logic Exp 7.2.dmg and use Pacifist to extract the file and install to the /Library/Audio/Midi Drivers folder.
Open Audio MIdi Setup and the Unitor 8 MK II should be there. Probably also works for the AMT8, and MT4. This file isnt easy to get unless you have a Logic install disk so i posted it on rapidshare. I dont use Logic!
Tested with Reason 4.0. Djparada78, Apple,. SATA Device Manufacturer Supported Devices OSx86 versions tested Link Notes Credits nVidia nforce 4 chipset 10.4.8 This is the installer for SATA support on nforce 4 chipsets.
Huge thanks to Bikedude, Medevil, and whoever else helped with this effort. ATA Device Manufacturer Supported Devices OSx86 versions tested Link Notes Credits Marvell 88SE6111 10.5.3 This is a modified kext version of 'AppleVIAATA.kext' supporting Marvells ATA/SATA chip 88SE6111 used by Asus P5K-SE mainboard for example.
Huge thanks to podarok. Marvell 88SE6145 10.5.3 This is a modified kext version of 'AppleVIAATA.kext' supporting Marvells SATA chip 88SE6145 used by some mainboards. Huge thanks to podarok. Graphics Device Manufacturer Supported Devices OSx86 versions tested Link Notes Credits nVidia NV10,NV20,NV30,NV40 family and, NV50! 10.4.3 10.4.4 10.4.5 10.4.6 10.4.7 Beta2 has full 2D hardware acceleration supported no QE/CI yet, but coming soon HUGE THANKS FLIES OUT TO np, gave hope for the hackintosh community but and kext now supports QE/CI, even dual screen support.
ATi could be R100-R400 and perhaps some of the R4xx series, Radeon mobility 9600 128mb 10.4.4 10.4.5 10.4.6 10.4.7 10.4.8 development stopped omni,U're our hero though exited ATi for X1600 and X1800, and perhaps some of the X1000 series. Does not support X1400. 10.4.4 10.4.5 10.4.7 10.4.8 10.4.9 Working just like the original ATINDRV with resolution change, DVI support, QE+CI and no artefacts!
Omni is our hero for finding the information, and boris for merging them:) thanx goes to Neophus for the installer Intel,Via,Ati for AGP users having video speed issue due to the lack of AGP recognization under OSX 10.4.6 10.4.7 Work in progress, works fine for AMD Via Chipset users: as fast as under XP! Thanx goes to Joblo ATi ATI Radeon® 9250 256MB PCI Card 10.4.8 Works fine plug and play, resolution defaults to 1024X768 but can be adjusted to video cards full resolution M ck / Coolninjas / Anthony Novak ATi ATI Radeon® HD 3200 10.5.8 and (install both!) Lets you change the resolution to any resolution supported by video card. Thanks to Dong / play736 / lebidou. Network Device Manufacturers Supported Devices OSx86 versions tested Link Notes Credits linksys it needs to be broadcom Attansic Attansic L1 Gigabit Ethernet 10/100/1000Base-T 10.5.2 This network device is integrated in some ASUS Motherboards. Post #342 on the given link contains zipped package for automated install. Most reports indicate that entering Sleep mode 'kills' the network controller (you need to restart to regain network functionality).
Coding: DaemonES, MadInt Packaging: Jimmy Mallmann ALi ALi/ULi 5261 5263 100Mbit Ethernet 10.5.4 Also known as the ALi 1567, this chip is found on some ASRock motherboards. Should be hardware-compatible with the linux 'uli526x' driver. Thanks to orByte Intel Intel® 82540EM Ethernet port 10.4.8 will run nativly without additional.kexts or drivers Credit: M ck Intel Intel 2200bg/2100/3945/4965 WiFi card 10.4.6 10.4.7 10.4.8 10.4.9 10.5.2 10.5.3 10.5.4 10.5.5 10.5.6 closest thing to install note Posted by: Maciekish ASIX ASIX AX88772 USB 2.0 Ethernet (Nintendo Wii USB-2-LAN adapter) 10.6 embedded?? com.apple.driver.AppleUSBEthernet (2.0.9) Tested on Acer aspire 3810TZ on 10.6 Works out of the box! Provided by jtsop. Peripherals Device Manufacturer Supported Devices OSx86 versions tested Link Notes USB/Bluetooth mouse 10.5.8 Logitech Control Center 2.0 - 2.1 - 2.1.3 for USB Keyboard and Mice Logitech LX500/501 cordless desktop set 10.4.5 10.4.6 10.4.7 10.4.8 Logitech Control Center 2.0 for USB devices.
Disables mouse acceleration.
FIRST OF ALL, WARNING! Mac os x 10.5 support exists for 2100, 2200, 2915, 3945, 4965, 5150, 5350, 6x00, 6x50, 1000 series at this time (oct 09) only iwi2100 and iwi2200 driver works - for mac os x 10.4 and 10.5 UPDATE! UPDATE SLOT! This thread is now a collaboration thread for ALL developers and users seeking to get ALL intel wireless cards working on OSx86: Head on over to to get your hands on the newly updated intel drivers that everyone has put so much time into. Help debug and report everything.
Forget P.Diddy's Vote or Die slogan. This is an SOS.Contribute or Die! Seeing as nobody else is stepping up to the plate, I'll write out a decent tutorial.
Mods: Feel free to move this to where you think it should be. I'm only posting it in this thread for the sake of keeping things easy to find. This assumes that the reader has no knowledge whatsoever of how to do anything. (obtaining from SVN, compiling, loading the kext, logging) WARNING: Testing these experimental drivers may cause irreversible system changes. WARNING: Setting up OS X just to be able to compile the kext requires XCode, which is a hefty download.
( version 3.0: 1.1GB, @ ) RECOMMENDED: Back up your kexts, just in case. ( see ) Part I: How to download from the SVN. Potentially considered an unnecessary step, see note below Note: You /may/ be able to skip this portion (Part I) by downloading XCode and following the steps shown in the Post-script, Part III. After finishing the instructions in the Post-script, Part III, proceed with the instructions in the body of the tutorial, Part II: Compiling the source from the SVN. (Once again, XCode 3.0 is used in this tutorial, and it is a large download.) 1. Obtain SVN Client software Personally, I use svnX. It can be found on: Make sure to download and install the Subversion binary package linked on the page too.
Setting up svnX to download the latest source from the SVN. Here are the two repository locations Make note of the one that applies to your card.
You'll see two windows appear. Pay no heed to the 'Working Copies' window, but instead focus your attention to the 'Repositories' window. Now look back to the two repository locations, for this tutorial, I'll be explaining instructions on how to download the iwi4965 source. On the repositories window, click the '+' sign to add a new SVN location. Select the new entry that appears in the window and change the following: Name: 'My Repository' to 'iwi4965-osx10.5' Path: 'svn://' to ' (Without the quotes, for those of you that must ask) Also, for those sleepyheads out there. These are the instructions for the Intel 4965 card. The window should now look like this: Now, highlight and double-click that entry.
Another window should now appear. It should look like this: The latest revision should be selected, if not, do so. (Rev#) Seeing as we want to download the stuff shown down at the bottom, click the 'svn export' to save a local copy of the svn repository to your drive. (The green arrow on the top right) For the sake of convenience, select your desktop as the location to save everything to.
As the files are being downloaded, you'll see a progress bar appear at the bottom right of the svnX iwi4965-osx10.5 window. Do NOT quit svnX until that disappears.
See below for an example: You should now see a folder named 'root' on your desktop. It should contain all the sources required to build the kext.
Part II: Compiling the source from the SVN. Obtain XCode.
Get it: I used the 1.1 GB XCode 3.0 DMG. You might need to set up an Apple Developer Connection member account to download it. Mount the disk image and install the XcodeTools.mpkg package file. I didn't need to install anything else. Launch XCode to compile the kext and networkSelector. Now refer back to the 'root' folder on your desktop. Open it up and open the iwi4965.xcodeproj file.
(Double click it, XCode should be automatically launched) You should now see: note: if you do not see this exact screen, make sure you have selected the iwi4965 project file, as shown under 'Groups & Files' Notice the iwi4965.kext in red? We need to build that.
What do you do? Click the 'Build' hammer on top. You should receive a bunch of warnings, but we'll ignore them. Afterwards, you should see 'Build succeeded' and 'iwi4965.kext' should no longer be in red text. If its text color is black, select it and open up a context menu and choose to 'Reveal in Finder'. (See below) Drag the kext to your desktop for easy access. Now, follow the same steps for networkSelector.
(See the /networkSelector directory for the.xcodeproj) Note: If you are having trouble compiling networkSelector, see:://forum.insanelymac.com/index.php?s=&.t&p=727429 or The posts linked above might also solve future problems when following the rest of this tutorial. Part III: Getting ready to test. Setting up the console. Open up the Console. (ApplicationsUtilitiesConsole) Show the log list, if not already visible. (The top left button) Select the system.log file.
(Under LOG FILESsystem.log) This is what a typical user should see, notice how messy it is? It has all of these irrelevant error messages. Let's clear up that log, to make it simpler to see the information we need. Reveal the file in Finder. Then open it using your favorite text editor. Afterwards, clear the log. (Select everything, delete, and save) You may need to authenticate for this action.
That's normal. Click Reload in the Console. Everything should be squeaky clean (empty). If not, there should at least be fewer error messages in the system log. Mine is squeaky clean 2. Obtain Kext Helper b7 Seriously.
It kicks ass! No more repetitive Terminal work. Part IV: Testing Here's where the real fun begins. Kernel panics, lock-ups, and system instability. If you got lost more than 10 times up to now, it's never too late to turn back.
But since I'm taking the time to write this tutorial, why not follow it? Checklist Make sure that you have done the following: Compiled the kext and networkSelector and know where they are Cleared system.log of any error messages generated before the testing Downloaded Kext Helper Realized that I'm not responsible for any damage to your system Thanked jalavoui and the other hard-working people, all dealing with this enormous pain in the arse. (Driver development = ew) Read all of the above 2. Loading the kext Run Kext Helper b7. Drag your iwi4965.kext into the window. Enter the password for the user logged in. It should look like this.
(Check the 'advanced' box if you want to look cool) Ready? Click the EASY INSTALL button. Are you really ready?
If so, click OK. Now, after a couple seconds, you should see: BUT WAIT! You don't necessarily want to reboot yet!
Check the Console first! Make sure OS X detects your card. You might see something as follows (from rev 872) If you do, congrats!
You have the experimental drivers loaded! Now, you have two options, unless I'm mistaken. 1 Save the system.log as a text file now (FileSave Copy As) and unload the kext 2 Or reboot with the kext loaded still to see what happens (Kernel Panic? Pancakes?) After saving system.log, post it to this topic and be sure to indicate your revision number! I'll add a more detailed section regarding networkSelector if I should ever feel like it. You basically just need to launch it, and initiate a scan from it. From my experience, if I don't initiate a scan from networkSelector, my card defaults into 802.11a.
When I do use networkSelector to initiate a scan, it's forced into 802.11b/g. That concludes the main portion of the tutorial.
Onto the aftermath portion. Post-script Part I: Unloading the kext. There are many ways to do this, I'll go over three situations. Situation 1 You've barely made it through this godly tutorial and haven't yet restarted as you're too scared as to what may happen. You're still logged in and want to unload the kext while your system is still stable.
What do you do? Open up Finder. Browse to your Extensions directory. /System/Library/Extensions Locate iwi4965.kext and drag it to the trash.
You'll have to authenticate. That's normal. You can now reboot and everything should be back to how it was before.
You're in the same situation as above. However, you want to be pro and unload it using the terminal. Open up the Terminal. Type in the following: sudo rm -rf /System/Library/Extensions/iwi4965.kext. You'll have to authenticate, and it should be unloaded after you rebooted. You've rebooted and you either get a kernel panic or OS X simply locks up before you can get to a GUI. Edit note: For all I know, austinsnyc has a point there, but I've gotten into a forced habit of adding more boot flags than necessary.
In this part, something is definitely not going right if you're getting kernel panics, so at least have '-v -s' so you can easily diagnose the issue. Removing the '-x' flag will save you an extra reboot, after you've unloaded the kext and want to have full functionality. If you want more info about boot flags, please see: Try booting into OS X with the following flags (all at once): -v -x -s. You should then be able to boot into OS X. (With minimal kexts loaded) If you are able to, and wish to be able to have full functionality, reboot yet again without the flags to load all installed kexts.
If you are not, and you performed all the steps on Try restoring the backups. Post-script Part II: Messing around Sometimes jalavoui (or someone else) may suggest that you edit some source code and experiment with certain values. Here's how you'd do it in XCode. Let's assume you need to change an IOSleep value. How would you find what to change in the jungle of code? Load up iwi4965.xcodeproj or whatever.
Go to EditFindFind in Project The following window will pop up. Search for the proper string, and scroll around for the right instance you're looking for. Make a change, save it, and build the kext. It's that easy Post-script Part III: Subversion (SVN) in XCode Now, since you've already gotten the XCode project file, and XCode, why bother with svnX? (I still use it, due to force of habit, but this alternative method could save you lots of time) Original instruction set used in this portion by jalavoui @ 1. Enable Subversion integration.
Basically, we'll be linking your XCode project directly to the SVN repository. This way, you'll be able to switch between revisions, check for changes, and other things, all in XCode. Note: I've just realized that this portion may be able to replace the portion regarding svnX, the tutorial will be changed to reflect this. Launch XCode. Go to SCMConfigure Repositories Click on the + to add a new repository. (You choose whatever name you want, it doesn't affect much, just the name of the directory everything is saved in) Make sure Subversion is set as the SCM System. Now you'll see this: Paste in http://iwidarwin.googlecode.com/svn/trunk.UPDATE.
I've hit many speed bumps along the way but I believe that my GUI is only needed to turn the wireless card on.FOR NOW THAT IS until I hit another problem. What does this mean to me? You will only need to use my app to turn the wireless card on, after that apple is detecting it. I've masked it and am in the process of tricking the OS into thinking it's a Broadcom airport card (through the process of leaving my app open and running in bg). One that comes supported by Mac OS X by default. My only problem was the card had to be turned on by the software but I didnt think the intel cards power was app controlled, or am I mistaken here?.UPDATE. I've hit many speed bumps along the way but I believe that my GUI is only needed to turn the wireless card on.FOR NOW THAT IS until I hit another problem.
What does this mean to me? You will only need to use my app to turn the wireless card on, after that apple is detecting it. I've masked it and am in the process of tricking the OS into thinking it's a Broadcom airport card (through the process of leaving my app open and running in bg). One that comes supported by Mac OS X by default.
My only problem was the card had to be turned on by the software but I didnt think the intel cards power was app controlled, or am I mistaken here? So are you implying that you can somehow make this card airport compatible by making the OS pretend it's a Broadcom card, or am I mistaken? How long will it take for there to be a testing driver that one who has this card can use? So are you implying that you can somehow make this card airport compatible by making the OS pretend it's a Broadcom card, or am I mistaken?
How long will it take for there to be a testing driver that one who has this card can use? No, you're not mistaken. You're right on the money. I'd imagine withing the next week or two I should have a stable enough beta to distribute.
I have another friend helping me out as well. His background is linux so he's also helping me on another project of porting the linux drivers for the intel 5100+ cards to the mac os x / unix system. Of course re-coding it from scratch into something IOkit compatible. I've planned it out this way in hopes that if one fails, the other will pick up the pace and continue into a working solution for all of us having a 5100+ card(s). I haven't tryed DSDT hack before but i think it can be used to make the hardware more 'apple' compatible after patching DSDT it can be used with future kernel versions (vanilla,voodoo,etc) but before doing that it's better to focus on firmware i've tested all 3945 firmware versions on iwi3945 driver i did notice some work better than others have you tryed all firmware versions? - maybe this can be a start point download from i use hex2string to convert the files (get it from svn tree of any iwidarwin driver).
Hi, I have Toshiba f50-10q labtop with intel 5100 too. I never program in xcode enviorement but i program in C and in the last days i programming in C# So if i can colaborate in anyway no doubt to ask me Thanks, Blady hell yeah. Be getting in touch with you. And as far as programming in xcode.
You just gotta learn how to mac does things a lil different and also its objective c itself so. It shouldnt be too hard. So you have an up and running osx86 mac installed? I take it as yes just had to ask or see if you had any major problems, etc. Be getting in touch with you.
And as far as programming in xcode. You just gotta learn how to mac does things a lil different and also its objective c itself so.
It shouldnt be too hard. So you have an up and running osx86 mac installed? I take it as yes just had to ask or see if you had any major problems, etc. Hey Miller I am a Software Engineer too, with some linux driver experience and C/C experience. But, I am new to Mac development. I got leopard 10.5.7, XCode and ethernet working on my Sony Laptop. I can help you with the 5100 driver, show me a way forward.
Wireless Lan Driver
I most definitely can't wait. I just bought an acer aspire 6930 with an intel wireless wifi 5100 card.
I got ideneb 10.5.6 v4 installed without a hassle. Booted the first time, no sound at first but i know have a fix which has been implemented into the system so it works perfect: ) all i'm missing is the wifi. If you would like to have a tester for your software i'm quite open to that. I'm up for testing too if you need some.
Mic Lan Card Drivers For Mac
I have a HP dv7 with the 5100 agn and another sony vaio with one too. Both work almost 100% other than wifi.