Conti

PS: Is that the HD3000 IGP (Integrated Graphics Processor) on the Sandy Bridge intel platform? I'd be interested to see your system specs if you could post them to the thread we have running in the hardware forum, or if it is not too much trouble submitting a User Guide for your system would be nice. I haven't had a chance to play with any Sandy Bridge hardware myself yet.

I'll include the latest from SVN in my next release, also the chameleon team is quickly working toward a final STABLE 2.0 release, which will be amazing to finally see it without an "RC" attached to it lol. There are some other things in the works but we're keeping that under wraps for now. For future reference you can simply drop boot, boot0, and boot1h into myHack.app/Contents/Resources/Resources/Chameleon/usr/standalone/i386/ (you can right click on the app and 'show package contents' to enter the app bundle, then drag and drop) from any version of chameleon at any time, then simply run myHack "Install Chameleon Only" option - this will properly flush your boot sector and install chameleon without having to spend any time in the terminal. Also most changes generally happen in "boot" which is something you can simply drag and drop to / to overwrite the existing one, a simple way to update.

If you have a kernel extension you would like to submit to this forum please post a detailed description of the kext, it's capabilities, known compatibility/incompatibility, and reference the source of the kext in this thread. Include a download link to the kext on a free file hosting site that does not require registration or login. If the extension is deemed worthy and the description is complete one of the staff will post a thread including the description you submitted, a "Submitted by" line with your nickname, and include the kext as an attachment.

Only respected members, moderators, or administrators can start a new topic in this section. This is to ensure the highest standards are met with the information presented here. If you have a kernel extension you would like to submit to this forum please post it as a reply to THIS THREAD. Please do review the posting guidelines as described in the first post. All registered users may reply to the threads in here though, so feel free to add your two cents. If a kext works/does not work for you it is important to let others in the community know.

Should be

Someone else reported this when trying to run it on a xen VM... I can't reproduce the error on my end, but I will give that floating point a bit more memory to gobble up to see if it helps. I'll reply when I release an update. Thanks for reporting this, at first I just assumed it was an issue with the xen system, but by including the information that RC1 worked under the same VM/host it makes me think there is more to it.

Ya I haven't done any work on the chameleon theme... That's on my todo list. And thanks for reminding me about the /Extra/[10.6/10.7]/Extensions - not many people dual boot OS X versions but I may add something in the app for it just to polish things off. Thanks for taking the time to comment on the latest release.

Note: As of myHack 2.0 RC3 I have included this kext in the generic extra that is bundled with the myHack app. I tested it and yes, it does work in Snow Leopard as well. The information found below is useful however because it serves as a good example of how to create a patched kext without altering your /System files. So yes, as we all know by now and you have probably figured out, the dsdt fix for RTC does not work on Lion. You have basically two options - use the ElliottForceLegacyRTC.kext which is based off of the AppleRTC.kext from 10.5 Leopard.... (Just recompiled to have x86_64 support) - or you can patch the Lion AppleRTC.kext, which is probably the better option of the two, especially given the fact that the ElliottForceLegacyRTC.kext causes kernel panics on some systems. So basically what we are going to do here is a basic run of the mill hex edit that replaces one string with another, we often refer to it as a 'binpatch' or binary patch. Taken a step further - I will show you what we can do to make sure that this change is retained after any software updates which may overwrite this patched AppleRTC.kext and to do this without touching your vanilla kexts in /System/Library/Extensions. First we are going to make a copy of the AppleRTC.kext to work with. Open a terminal and run the following commands: cp -R /System/Library/Extensions/AppleRTC.kext /Extra/Extensions/ Now we are going to binpatch this extension by running the following command: sudo perl -pi -e 's|\x75\x30\x44\x89\xf8|\xeb\x30\x44\x89\xf8|; s|\x75\x3d\x8b\x75\x08|\xeb\x3d\x8b\x75\x08|' /Extra/Extensions/AppleRTC.kext/Contents/MacOS/AppleRTC Now to ensure that this kext is loaded instead of the one in /System/Library/Extensions - or any future version that may be installed with a software update, we are going to "version bump" this modified extension by using the following commands: sudo defaults write /Extra/Extensions/AppleRTC.kext/Contents/Info CFBundleVersion 9.9 sudo defaults write /Extra/Extensions/AppleRTC.kext/Contents/Info CFBundleShortVersionString 9.9 sudo defaults write /Extra/Extensions/AppleRTC.kext/Contents/version BuildVersion 999 sudo defaults write /Extra/Extensions/AppleRTC.kext/Contents/version CFBundleVersion 9.9 sudo defaults write /Extra/Extensions/AppleRTC.kext/Contents/version CFBundleShortVersionString 9.9 Now we will convert the plist's back to a human readable format (just to be nice to people who may want to poke around later) with plutil sudo plutil -convert xml1 /Extra/Extensions/AppleRTC.kext/Contents/Info.plist sudo plutil -convert xml1 /Extra/Extensions/AppleRTC.kext/Contents/version.plist Now set the permissions so everything is happy sudo chmod -R 0755 /Extra/Extensions/AppleRTC.kext And rename it so we know what it is sudo mv /Extra/Extensions/AppleRTC.kext /Extra/Extensions/Patched_10.7_AppleRTC.kext Finally run myFix to apply these changes to the Extensions.mkext and that's it, u have a binpatched extension that will continue to work even after OS updates that may replace the vanilla one, and you haven't altered the /System files. If you are particularly lazy I have attached the finished product to this post. Patched_10.7_AppleRTC.kext.zip

This is one of the most common issues myself and other chameleon developers have been running into lately. Note: As of myHack 2.0 RC2 you should not need to do this unless your system fails to boot to chameleon, but I have seen a few users who's systems are too badly damaged for the attempted auto-repair method in myHack to repair on it's own so some users may still need this. The issue is poorly written or hacked up stolen software from other sources - like "unofficial chameleon installers", "multifail", or even a bad tutorial on how to install chameleon manually results in corruption of the boot sector on usb sticks, external/internal hard drives, etc. This will cause myHack and *correct* manual chameleon installation to fail or behave in an unpredictable manner. If you have used any of the methods I have just mentioned at any point in the past it is important that you do the following prior to attempting a new installation of myHack or a proper installation of chameleon manually. Before continuing please understand one thing, even though the commands I have listed usually work as expected - whenever you are playing with boot sectors and partition tables there is a risk of something going wrong and data loss. If there is anything on the device you are about to run these commands on worth saving, ensure that you have made a backup to a separate device of that data prior to running any of these commands! Before we begin let me explain how to get your device ID of the device you want to target... It seems to have caused some confusion when I initially posted this. Suppose you want to fix the boot sector on a device that is mounted on /Volumes/my_stick Open up a terminal and type "mount" without the quotes. Then look for the line that contains /Volumes/my_stick - for example: /dev/disk5s1 on /Volumes/my_stick (hfs, local, nodev, nosuid) The device id is "5" in this example, and the partition is "s1" (which stands for slice 1) so when running the following commands you will instead of typing /dev/disk5s1 type /dev/rdisk5 - so you are now targeting the raw device (this is what the r stands for) and the device id - but not the partition. If you are going to repartition the entire disk and do not care about the partition table being destroyed do the following from a terminal: WARNING THIS WILL DESTROY THE PARTITION TABLE AND ALL DATA ON THE TARGETED DEVICE! sudo dd if=/dev/zero of=/dev/rdiskX bs=512 count=1 Replacing "X" with the device ID of the device you want to wipe. After this use disk utility to create a new partition. If you only want to flush out the boot sector without damaging the partition table (useful if this is not a USB stick but your internal drive and you would rather not lose your partition table) do the following from a terminal: sudo dd if=/dev/zero of=/dev/rdiskX bs=446 count=1 Replacing "X" with the device ID of the device you want to clean the MBR of. After this you can use myHack or manual methods to install chameleon to the device successfully. If you get an error when trying to run either of these commands that says "Resource Busy" then ensure that you have closed all terminals/finder windows/apps/etc that may be accessing the drive in any way, and unmount (not eject) the device using disk utility prior to running the commands. If it fails to unmount there may be a process attempting to write to it in the background, you can either kill that process (a rather advanced task, if you don't know how to do it already then it is simpler to just reboot) or reboot and try again.