Jump to content

bcc9

bcc9

Member Since 23 Feb 2009
Offline Last Active Nov 23 2014 03:38 AM
*****

#2022427 Script to patch AppleHDA binary for osx10.7/10.8/10.9

Posted by bcc9 on 26 May 2014 - 08:03 PM

Ok, I've posted a new version that includes support for outputting a clover compatible XML configuration, instead of patching AppleHDA directly. The new version number is 3.3. New command line switch -x to enable this XML output. Example: % ./patch-hda.pl 10ec0892 -c 2 -xOSX version 10.9.2 detectedDefault target codec: 10ec0892 detected.Patching AppleHDA codec 11d4198b with 10ec08921 codec range comparison(s) to patchPatching range comparison 11d41984 <dict> <key>Name</key> <string>AppleHDA</string> <key>Comment</key> <string>Expect 2 matches</string> <key>Find</key> <string>8419d411</string> <key>Replace</key>...

#2021870 Script to patch AppleHDA binary for osx10.7/10.8/10.9

Posted by bcc9 on 24 May 2014 - 01:52 AM

Generally speaking I don't like making the match string contain extra stuff that isn't being changed just to lower the chance of a false match. I think it'd be much better for the syntax to support an expect count, so the program can throw a warning if the match is being potentially mis-applied. The perl script does this now. Going ahead and supporting a syntax for clover that doesn't allow for this is a bit of a step backwards. But if everyone is happy with sloppy matching, I can make this script output the XML as is... I think there are almost no cases where this has been burning folks so far. Maybe not, but there is a bit of that out there :-)Yes, and it'd be debatable whether there really is any violation going on. I just don't want to be putting up any such web page myself. @bcc9 this is the wiki: http://wiki.osx86project.org/wiki/ you need something in particular? I can propose the changes you need..Yes, that seems like the right place. I wasn't sure that was really...

#1972117 AppleIntelE1000e.kext for 10.8/10.7/10.6/10.5

Posted by bcc9 on 28 November 2013 - 07:43 PM

I was running 2.4.14 fine under 10.8, but after upgrading to 10.9, the ethernet breaks after about 1 day of uptime. The system begins flooding the LAN with packets, causing collisions and saturating my gig-e hub. I just upgraded to 2.5.4d, hope that works better. When the ethernet is malfunctioning, the display is also unresponsive so I can't really debug it further.Ok, it took a lot longer for the bug to re-occur for me with the current release, but now it has, failing in the same way as the old version. Pretty nasty bug. And, it looks like this driver is no longer being actively maintained? I have experience fixing ethernet drivers under *nix, but if this driver is going to continue being unmaintained, then the recommendations to switch to a pci-e gig-e card seem like good advice. However I would disagree that a realtek nic or a usb ethernet solution are good choices - realtek doesn't have a great track record with their open source driver support (look at the bug history of the...

#1958914 IOUSBFamily 10.8.4 Slice+AnV with full AppleUSBXHCI support for any USB3 chip...

Posted by bcc9 on 26 October 2013 - 07:01 PM

I'll update it for 10.9 when the sources come out. If Slice still has a 10.8 installed, you could ask him to compile a 10.8.5 IOUSBFamily when the sources come out :DSo now that 10.9 sources are out and IOUSBFamily is MIA, what's the plan for usb 3; compile this for 10.9 anyway, or merge efforts with zenith432's genericusbxhci? I know that sometimes some packages release later than others at opensource.apple.com, so maybe we can keep waiting and it'll come out. Still hoping to someday be able to resume from suspend with working usb3 on my old sandy bridge system :)

#1958618 Intel HD Graphics 4600 (Haswell) working displayport

Posted by bcc9 on 26 October 2013 - 07:31 AM

All he is saying he has HD4600 model being injected by chameleon, but he wants Iris Pro string instead...The names are hard coded into chameleon, so if one doesn't like them, there are a few choicesuse dsdt injection instead of chameleon,change the name in the chameleon source and recompile yourself,update the ioregistry with another name after chameleon has run

#1957347 New Mac Pro hackintosh comparable build?

Posted by bcc9 on 23 October 2013 - 10:48 PM

Ok, that's in line with what everyone has been doing for their haswell desktop hackintoshes (myself included). Hardly a macpro however. More like a haswell imac with a consumer desktop cpu instead of mobile. Looks like this thread should be deleted since you aren't actually discussing mac pro hardware.

#1956657 Script to patch AppleHDA binary for osx10.7/10.8/10.9

Posted by bcc9 on 22 October 2013 - 04:49 AM

In preparation for the OSX 10.9 release, I've cleaned up post #1 a bit and moved the script there.

#1954411 Script to patch AppleHDA binary for osx10.7/10.8/10.9

Posted by bcc9 on 14 October 2013 - 07:00 AM

Great Work bcc9, I think you perfected our conversation and did efficiently though without a GUI. I can help in any way with the PCI's device's? All the best!!Thanks. I should have mentioned that your private PMs helped to push me to make this latest version a bit more user friendly. Sure, you could hack up a kext that dumps out the information (similar to the lspci port). Then I can just invoke the kext and parse the result from this script. Can you add a param to allow custom location of AppleHDA.kext?The functionality is already in there, I just hadn't documented all the command line switches: -s <directory> to specify an alternative to /System/Library/Extensions -r <volume root> to specify an alternate disk volume to use as the root for everything (particularly useful when you have multiple installs of OSX and you want to patch OSX on one of those other volumes. Also, for both of the above the script determines the OS release based upon the AppleHDA kext version...

#1953762 Script to patch AppleHDA binary for osx10.7/10.8/10.9

Posted by bcc9 on 12 October 2013 - 05:31 AM

Here's a new version of patch-hda.pl, version 3.0. This version attempts to auto-detect your system's codec and offers that as a default. Also, you can run the script interactively with a bit more help than the wrapper script had before. For example: % ./patch-hda.plOSX version 10.9 detectedDefault target codec: 10ec0892 detected.Enter codec-id or codec-name for AppleHDA patch. Eg. 111d7675 or IDT 7675Press enter for default, or ? for help (Default: 10ec0892)? <enter>There are 2 choices for target codecChoose codec number to patch to (1 thru 2) (default 1)Choice 1: ALC 885Choice 2: ADI 1984B? 2Patching AppleHDA codec 11d4198b with 10ec08921 codec range comparison(s) to patchPatching range comparison 11d41984This script requires superuser access to update AppleHDAPassword:/System/Library/Extensions/AppleHDA.kext/Contents/MacOS/AppleHDA patched successfully.%The new command line argument -y allows you to pick up the auto-detected codec without running the script interactivel...

#1949622 Intel HD Graphics 4600 (Haswell) working displayport

Posted by bcc9 on 29 September 2013 - 07:23 PM

It appears to be reading the controller id from physical PCI root (same as with codec-ids), as substituting ID hasn't done anything. I've tried it at one point and even though IOReg pretty much was matching one from MBA6,2 there wasn't any improvement. I found that on my mobo with no DP I'm perfectly fine with 0x0A160000 platform id, which makes my HDMI appear with signal type 8 and connector type 8 with no additional edits to the framebuffer. You can dsdt edit a patch that changes the PCI ID for a device in the PCI config memory, thru the device's _INI method.  This is what I really meant, and it sounds like it would do the job. Edit: Actually, wait, I think that only works for subsystem ID, with the device-id being read only.   Edit: Actually, wait, I think that only works for subsystem ID, with the device-id being read only.  I wonder if we could patch this via an efi driver, since the integrated graphics device-id is being determined at run-time bas...

#1949619 Intel HD Graphics 4600 (Haswell) working displayport

Posted by bcc9 on 29 September 2013 - 06:41 PM

So my suspicion here http://www.insanelym...-3#entry1937848 that you needed the connector-type set correctly for working HDMI audio was right.  I originally found this years back when working on HDMI audio for nvidia graphics, and some people found it to be a necessary fix at the time.Looks like it's now needed for intel too; nice work.I agree with TimeWalker that a patch that needs to be re-done each release is not very desirable.   I haven't seen documentation for the patch, or bothered to look at the code, but if it's just matching on the device-id have you tried overriding that via injection, instead of doing a binary patch?

#1948873 10.8.5 out

Posted by bcc9 on 26 September 2013 - 07:05 PM

Here it is.http://d.pr/f/68JyMy original kext post including package installer & source is over here:  http://www.insanelym...h/#entry1239975Wow 3500+ downloads.  Pretty good for just a dell driver.

#1947789 10.8.5 out

Posted by bcc9 on 22 September 2013 - 03:52 PM

Netkas has provided us many great things, but wasn't the ncpi=0x... flag discovered by bcc9?Yes, thanks, that and the dart=0 fix for the vt-d issue with some motherboards.  These simple boot argument fixes spread like wildfire so it's understandable that most never learn where they came from.  Too bad though when the original technical discussion gets all but lost in the process.

#1943009 Editing custom personalities for ATI Radeon HD[45]xx

Posted by bcc9 on 03 September 2013 - 04:12 AM

I've updated post #1 with version 0.11. otool is simply invoked as otool -Q to get its former (more useful IMO) behavior. The script also warns the user when otool is missing instead of simply failing to run correctly.

#1942982 Editing custom personalities for ATI Radeon HD[45]xx

Posted by bcc9 on 02 September 2013 - 11:01 PM

@smx: Look here for the fixed version.Thanks, this is the first time I've been made aware that users were bumping into the otool compatibility issue with this script. Xcode as of 4.6 broke my scripts by changing the (default) output style from hex to decimal in otool. I did notice this before with my ahci patch script but I forgot about this one. I'll update.
  • smx likes this

© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy