Jump to content


  • Content count

  • Joined

  • Last visited

About bilditup1

  • Rank
    InsanelyMac Geek
  • Birthday 09/27/1987

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    New York
  1. Are you installing to the regular 2.5" SATA hard drive, or an mSATA SSD? Does this make a difference? I'm not sure how to do dual boot without losing my existing Windows 7 partition and Lenovo recovery partition -- is this possible?
  2. Mavericks Realtek ALC AppleHDA Audio

    As it turns out, running the script again wasn't necessary, since I ran it multiple times, and the last backup of config.plist it made contains the error. It is attached. Also, here are the lines in question: <key>KernelAndKextPatches</key> <dict> <key>AppleRTC</key> <true/> <key>KextsToPatch</key> <dict> <key>0</key> <dict> <key>Comment</key> <string>t1-10.9/AppleHDA/Resources/xml>zml</string> <key>Find</key> <data>eG1sLnps</data> <key>Name</key> <string>AppleHDA</string> <key>Replace</key> <data>em1sLnps</data> </dict> </dict> </dict> Nothing else was copied to the config.plist file when the script ran. In fact, there were some error messages in the log that may have clued at this (not sure): Print: Entry, ":KernelAndKextPatches:KextsToPatch:0 dict", Does Not Exist Add: ":KernelAndKextPatches:KextsToPatch:0" Entry Already Exists Add: ":KernelAndKextPatches:KextsToPatch:0:Comment" Entry Already Exists Add: ":KernelAndKextPatches:KextsToPatch:0:Find" Entry Already Exists Add: ":KernelAndKextPatches:KextsToPatch:0:Name" Entry Already Exists Add: ":KernelAndKextPatches:KextsToPatch:0:Replace" Entry Already Exists Add: ":KernelAndKextPatches:KextsToPatch:0:Replace" Entry Already Exists Add: ":KernelAndKextPatches:KextsToPatch:0" Entry Already Exists Add: ":KernelAndKextPatches:KextsToPatch:0:Comment" Entry Already Exists Add: ":KernelAndKextPatches:KextsToPatch:0:Find" Entry Already Exists Add: ":KernelAndKextPatches:KextsToPatch:0:Name" Entry Already Exists Add: ":KernelAndKextPatches:KextsToPatch:0:Replace" Entry Already Exists Add: ":KernelAndKextPatches:KextsToPatch:0:Replace" Entry Already Exists Here is what that part of my config.plist looks like now, after manual editing: <key>KernelAndKextPatches</key> <dict> <key>AppleRTC</key> <true/> <key>KextsToPatch</key> <array> <dict> <key>Name</key> <string>AppleHDA</string> <key>Find</key> <data> eG1sLnps </data> <key>Replace</key> <data> em1sLnps </data> <key>Comment</key> <string>10.9/AppleHDA/Resources/xml>zml</string> </dict> <dict> <key>Name</key> <string>AppleHDA</string> <key>Find</key> <data> ixnUEQ== </data> <key>Replace</key> <data> mQjsEA== </data> <key>Comment</key> <string>10.9/AppleHDA/Realtek ALC898</string> </dict> </array> </dict> Hopefully this turns out to be helpful. Thanks to all the devs (inc you, toleda) who made Clover, ALC, and Clover + ALC possible! config-backup.plist.zip
  3. Mavericks Realtek ALC AppleHDA Audio

    I had completely removed AppleHDA before applying the Combo Update though. Will try to run the script on an older config.plist and see if the error happens again.
  4. Mavericks Realtek ALC AppleHDA Audio

    Guys, I got it to work. Two things: It looks like the config.plist is not being properly patched by the script. After manually copying in the following: <dict> <key>Name</key> <string>AppleHDA</string> <key>Find</key> <data> eG1sLnps </data> <key>Replace</key> <data> em1sLnps </data> <key>Comment</key> <string>10.9/AppleHDA/Resources/xml>zml</string> </dict> in addition to the ALC898-specific stuff in the last post, and then rebooting, all onboard audio became recognized. Second thing: I didn't have the virgin, untouched AppleHDA.kext initially. But contrary to what you guys are saying above, installing the 10.9.5 Combo Update DID in fact install a working AppleHDA, or enough of one to matter. Interestingly, extracting the kext from the Combo Update using Pacifist did NOT work and was NOT recognized as a valid AppleHDA.kext by the cloverALC script. So I think there must be something in the installer that detects the presence of the kext and installs it completely if it isn't there at all and just patches it if it IS there. ED: Added proof. I just noticed flyinace2000's IOReg doesn't have layout_id set properly btw. Working_ALC898_screen_log.zip
  5. Mavericks Realtek ALC AppleHDA Audio

    I've been having similar problems with my ALC898 on a Z87X-UD4H. Attached are my IOReg and command line log. ED: Looking at what the proper formatting of the patch should be in "config_audioClover_ALC.plist", it seems like the config.plist was getting patch improperly. A new dictionary indexed at 0 is made before the actual patch. So I just copied the proper information from that config file into mine. <dict> <key>Name</key> <string>AppleHDA</string> <key>Find</key> <data> ixnUEQ== </data> <key>Replace</key> <data> mQjsEA== </data> <key>Comment</key> <string>10.9/AppleHDA/Realtek ALC898</string> </dict> After dropping that in, the config.plist is recognized properly by Clover Configurator. But, still no sound. eli.zip
  6. Hey all- After a long hiatus from Mac hackery I finally decided to try osx86 again in the wake of El Jobso's death and because I finally have a computer that's easy to do virtualization on, an i7 ThinkPad X220. I've come to report my findings and ask for help. VirtualBox EFI Contrary to popular belief, the EFI implementation built-in to VirtualBox can boot the system properly, albeit very slowly. This is great because Shutdown/Restart doesn't cause a kernel panic, and About This Mac doesn't cause Finder to restart. (Note that on Sandy Bridge-based systems like mine, you'll have to get the 10.8.0 kernel to avoid a kernel panic; my solution was to use a bootloader disc image that included it and then to run the 10.6.8 update. Alternatively, one can simply acquire the 10.8.0 kernel and change com.apple.Boot.plist to point to it until you decide to upgrade). Screen resolution The cost of this though is looong startup times while the kernel and extensions are loaded, and no ability to change resolution via changing Boot.plist/adding a CustomVideoMode to your VirtualBox configuration. One might be able to use the alternative method of selecting between several hardcoded resolutions via 'GOP', but I didn't try this as the hard-coded resolutions aren't useful on a 12.5" 1366x768 native screen. [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url]/Chimera The solution was to use tonymac's [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] installer to get the Chimera bootloader on there; afterwards Shutdown/Restart are no longer graceful and 'About This Mac' doesn't work, but changing resolution via com.apple.Boot.plist and adding "CustomVideoMode1" works fine. All updates to date, including SecUpd 2011-006, install without issue. XCode 4.0.2, iTunes 10.5, Safari 5.1.1 - all up and running. (Needless to say, networking works fine, too.) Sound But sound doesn't. It seemed to be working during my initial install of 10.6 without any problems (was playing fine while putting in my initial info). After upgrading to 10.6.8 (immediately afterward) it stopped though. VirtualBox is configured to present an Intel HD Audio device. At first I tried to use several different flavors of VoodooHDA. While most of them recognized my device and produced sound, it was garbled and pitched down/running too slow/sampled at a very low rate (though sometimes it 'breaks through' in the middle of a song and samples properly, which is very jarring). This was true both when using my computer's built-in Conexant 20672 audio and with a HotAudio DAC Destroyer (though problems were a little more bearable on the latter, some of the time). Tweaks like setting 'Vectorize' to 'true' in the Info.plist of the kext changed nothing for me; so I gave up and eradicated it from my system. Reading a bit more I found that some people were claiming that the vanilla AppleHDA kext worked fine, without patching (uh which should have occurred to me considering that audio worked at first), so then I tried a few version of that by downloading Combo Updates and extracting AppleHDA.kext via Pacifist. All of the following I tested with 10.6.8. The one that ships with 10.6.8 (2.0.5) doesn't work at all (the kext doesn't load). The one that ships with 10.6.6 (1.9.9) suffers from VoodooHDA like problems - especially with the sampling rate, but also suffers from crackling. Using external DAC makes it a little more bearable, but not much. The one that ships with 10.6.6 (1.7.9) is interesting. With the built-in audio, the sampling rate is jumpy and crackling abounds, but with my external DAC it works almost without issue - some random crackling but otherwise, some very pure sound; no slowdown and no sampling rate shenanigans. The one that ships with 10.6.0 (1.7.4) doesn't work at all (kext doesn't load). I tried changing the Audio setting in VirtualBox to AC97and then using a custom driver purportedly made for VirtualBox AC97, but I got the same problems as 1.9.9 except worse. So does anybody know, definitively, what driver I should be using? And I just want to confirm - due to the lack of guest additions, video acceleration is impossible, right? cheers, -e EDIT: Wow is that sig old I also kept a working 10.6.8 image that doesn't use Chimera/is still on VirtualBox's EFI, in case it turns out some solution presents itself here that lets me use it at full resolution. Would 'editing DSDT' help? I'm not sure how to do this and if it's even relevant when virtualizing instead of doing a native install. Thanks in advance...
  7. Hey- I've made one of these DVDs successfully, but apparently messed up the kexts on the Boot132 side. (As it happens now, by the way, only the BOOT132 is visible in Windows, and only the Mac OS X Install DVD is visible in Leopard.) I want to keep experimenting with this, however, my efforts at making a standalone Boot132 USB loader have failed (all I get when I try this is an endless 'underscore' blinking at the top left corner of my screen.) So what I was thinking of doing is just using this guide to create a BOOT132/OSX hybrid DVD stick. I tried to do this by 1) ripping a bit-for-bit image with ImgBurn and then 2) using dd for windows (deadmoo-style!) to get it onto the stick. Now apparently the OSX side is there when I mount the stick in Leopard, but boot132 is not seen in Windows and the stick does not boot. Any pointers on this? A thousand apologies if this is obviously not doable or if I haven't read enough yet (which clearly I haven't; otherwise I wouldn't have messed up the Boot132 kexts in the first place. For the record the CPU is a Core2Duo ULV...) -e
  8. Installing Leopard

    Hey: -Does anybody know if GMA950 graphics is fully supported? Tiger 10.4.10 breaks support for it as I recall, I had to go back to 10.4.8/JaS. -What about wireless and such? Any concrete confirmations? I'm gonna check the wiki -e
  9. awesome! this is probably the best trick to use right now, thanks alot! unfortunately since qe/ci is dead in the water for me right now, im not gonna be using osx that heavily anymore, but this is still pretty great. -eli b.
  10. This is great buddy, I'm gonna try it out soon... you learn something new everyday
  11. Hey, thanks coen! I guess we could put the silly hack to rest now
  12. Hmm...the drivers here didn't seem to work at all. I went back and installed the ones from the 10.4.4 dvd, which are ever older than those in the file pvil uploaded. That in conjunction with AGPGart got me back to having at least the mouse tearing errors and such, but still no QE/CI. I honestly have no idea how I got the damn thing working in the first place... ...perhaps its an AMD issue? Do these frameworks need to be 'decrypted'?
  13. MacNugget - I've been using terminal for a while, but this is the first time I ever tried to write a shell script. It's written for my computer only, but what it does is, it goes through several steps to dismount your drive, verify there's a folder for it, and then remount it. Everything in the script, obviously, can be achieved through terminal commands. First, however, you have to copy ntfs-3g from /usr/local/bin to /bin (or sbin? I don't remember). sudo cp /usr/local/bin/ntfs-3g /bin Also, you need to give ntfs.command execution permissions; do that with the following code: sudo -s cd ../.. chmod u+rx ntfs.command That was assuming that you put ntfs.command in the root directory, which I suggest that you do. OK, now let's go through it line by line: echo echo NTFS-3g QuickFix by eli b. echo Enter password if prompted That was just an introduction, edit this to wtvr you want it to say. if sudo umount /Volumes/"Windows XP" then echo Volume Windows XP unmounted fi So the rest of the code is basically a bunch of if-then statements, which you've seen if you've done any programming at all. I come from a Java/C background, and not much of one for that matter. Instead of using curly braces , the '{' becomes 'then' and the '}' becomes fi. Here, we're telling umount to unmount /Volumes/"Windows XP", if such a drive is mounted. Substitute the name of your NTFS drive in between the quotes on that line. The echo statement on the next line just prints us a confirmation for convenience sake; but it's not neccesary. Repeat this code fragment for all of your NTFS drives. If this section fails for some reason, umount will display some kind of error message instead. if cd /Volumes/"Windows XP" then echo Volume folder for Windows XP found! else sudo mkdir /Volumes/"Windows XP" echo Volume folder for Windows XP created! fi Sometimes, there is no Volume folder for whatever drive you wanted to unmount. This usually happens if you manually dismount it before opening the shell script, or if the drive was never mounted at all. If this is the case, then this fragment makes the folder for you. Of course, substitute Windows XP for the name of your drive in all instances, and repeat this code fragment for all of your drives. if sudo ntfs-3g /dev/disk0s2 /Volumes/"Windows XP" -o default_permissions then echo Volume Windows XP @ /dev/disk0s2 remounted elif sudo ntfs-3g /dev/disk1s2 /Volumes/"Windows XP" -o default_permissions then echo Volume Windows XP @ /dev/disk1s2 remounted fi This section actually remounts the volume with the default_permissions option. Now, this part looks a little complicated because of a quirk in how OSX assigns BSD names (that's the /dev/disk0s2 portions above). Sometimes, the primary disk will come up as disk0 and sometimes as disk1. This is obviously very frustrating, and I couldn't find a fix for it, so I just had the code try to mount the volume twice, first on disk0, and if that didn't work (that's elif, which is the same as 'else if' in C languages and Java). For this section to work for you, just substitute /dev/disk0s2 with the bsd name of your NTFS drive, and "Windows XP" with the regular name of your NTFS drive. Do the same thing for the second part of the code (starting with elif) except substitute the opposite number for diskXsY. In other words, if you have disk0s2 for your drive, substitute a 1 for the 0 - disk1s2, and vice versa. The BSD Name can be easily found under Disk Utility or I think by right-clicking the drive on your Desktop. I found a C program that does the same thing, but I dunno where I put it right now. Finally, substitute the regular name of your NTFS drive everytime I wrote "Windows XP". killAll Finder echo Finder reset echo Enjoy! This just resets the Finder just in case the drive wasn't showing up before. To test if it works, just double-click on it. To have it start up with your computer, just add it to System Preferences >>> Accounts >>> Login Items. You'll have to enter your password in order for it work each time though. That's about it Bear in mind this is basically a hack, and not a very good one at that, since at random points the original problem resurfaces; and at other times, the drives won't show up with the correct name because I don't ping diskarbitration with the right name (I don't know how to both to do that and default_permissions at the same time - ntfs-3g throws an error). Hope this helped, and here's hoping ntfs-3g 1.616 doesn't have these silly errors... -eli b.
  14. I've posted ntfs-3g 1.417 on my webspace...it's in my signature now...
  15. ...so the last two versions of NTFS-3g have fundamental errors as far as I know: 1.417 has the insufficient privileges error, which is fixable with a shell script that runs at startup that unmounts the ntfs-3g drive and remounts it with default_permissions The next version has the 'can't mount most .dmgs' error which is impossible to fix. It seems the best thing to do is to find older versions of both ntfs-3g and macfuse. I was using macfuse .17 and an earlier version of ntfs-3g and they ran just fine...it's either that or live with 1.417 and wait for shadowofged to return from employer hell...