This time , I’ll be taking a look at ASUS PCE-AC68. It’s a 802.11ac Dual Band Wireless PCI-E Adapter for your desktop and best of all it is compatible with Hackint0shes – that’s right it works with MacOSX 10.85 and above. So if you are looking for a Hackint0sh compatible card – have a look
It’s great news for AMD users out there as bronzovka has finally managed to get up AMD Systems to play nice with OSX Lion. A guy by the name R:A:W:X86 took a step further by allowing AMD Bulldozer CPU to work with Lion and as well as fully 64-bit support for AMD processors (yes you can run in 64-bit kernel mode). At the moment there is no clear guide or installation software that to work with AMDs yet. I was hoping that my good friend , Conti updates his myHack to make it AMD compatible or a special version with AMD. If I have the time (which I should find),
So what I would currently recommend to folks that want to try AMD is that , you would have to a working OSX86 Installation and try with swapping with the kernel (I am quite sure that you have probably installed on an Intel system). Get RAWX86’s kernel , swap it and test it out. At least your system should boot , if it does not. Its time to troubleshoot and remove offending kexts.
AMD Users rejoice and I am quite sure that in OSX 10.8 , there would be good news – as we have people who have managed to get AMD working in OSX 10.7 and have released their sources and diffs so that talented developers out there can carry out their work and improvise it !
MacOS X Lion has lots of great features and it somewhat makes MacOS X as close as iOS (this is what Apple is trying to do) . One thing which I hated in OSX was its resume functionality , like how application and system resumes when you shut it off or restart it. Of course you have the option of turning it off every time you reboot/restart , but you’ll have to untick it and reboot for a clean reboot , else it would load up all the applications that you had previously and this would have an impact on boot time (unless of course you are using SSD).
I’ve found this great guide in MacOS X hints which describes how to do it , but unfortunately , it was not clearly explained as I would prefer to explain on what these commands do as you could understand them and improve your UNIX skills.
G’day and greetings from Australia. If you are wondering , where was I for the past 2 weeks or so. I am in australia now (VIC – the place to be ) to be exact and settling down here. The weather is ugh unpredictable , nevertheless its an awesome place. I’ll write another blog on my Aussie adventures.
Anyway , back to OSX86. I find it that it may be possible for us to run OSX Lion on our Atom as what this guy did with DP4. It just requires us to replace a couple of files in order to get it to work. The bigger problem is that few things appear to be broken when you do that. Only time will tell us if its really possible for us to run. In the meantime , if you are being adventurous and if you want to do something for the OSX86 community , I strongly urge you to read this and even prepare a guide or test it out with legit Lion to determine if it is even possible.
We may just need a few kexts , patched DP1 kernel and it may just work. I am not sure at all , but when I have the time , I’ll certainly have a look at it when I have the time
If you are an Aussie and if you want to invite me for beer/tea/coffee , just drop by me a mail and we can meet up
Apple launched MacOSX 10.6.8 update couple of days a go. It was a smooth update for my on my Hackint0sh Desktop and on my MacBook Pro (duh!). However , there were a lot of outcries from the netbook community users saying that the update is broken and such.
The reason why the update failed is because of the kernel patcher which did not patch the new kernel properly thus resulting in an infinite loop. This is because Apple has changed a couple of stuff in their kernel differently as how they did in previous kernels. The only way to fix is it either to wait for a new Chameleon (or NetBookInstaller) or to use a patched kernel.
On a side note , if everything is working great with 10.6.7 , I recommend you to keep it and do not upgrade till someone (hopefully merk) patches the the normal kernel . This is meant to help you to get your system back up and running if you have upgraded or if you plan to upgrade (if you’re being curious to discover whats new)
Thankfully , nawcom has just released his MacOS X 10.6.8 legacy kernel (which works great with our Intel Atom) and this is the fix that we need. That is to replace the kernel and everything works great.
Here are the instructions :-
Assumption : You are running MacOSX 10.6.7 with everything working and you have made backup of your system just incase if something went wrongdownload these legacy kexts – EvilAppleACPIPlatform.kext and EvilIOPCIFamily.kext . This is to avoid the infamous stuck at PCI Configuration or non-working WiFi. Its completely optional though
3. Install OSX 10.6.8 Combo updater but do not REBOOT.
4. Fire up Terminal and run the following commands :-
sudo mv /mach_kernel /mach_kernel_bad
Renames default kernel into mach_kernel_bad
sudo mv /legacy_kernel-10.6.8 /mach_kernel
Renames nawcom’s patched kernel as default mach_kernel
For those who are using NBI – You may reboot now as Intel Graphics kexts are automatically patched , and the system should be good to go
For those who are using UpdateEFI2 – Simply run UpdateEFI2 and select System Update. Let it patch Intel Graphics kext and you are good to go
[Optional] – Place the legacy kexts in your /Extra/Extensions or EFI partition
For those “I did it my way…” – You are on your own. Basically you’ll have to patch Intel Graphics and thats about it
6. Reboot and keep your fingers crossed . If you are having few issues , feel free to read the troubleshooting guide
Stucked at PCI Configuration – Simply install the legacy kexts which I’ve included above. You may have to revert back or use a boot loader from USB to get past and install these kexts back
Broken WiFi – Again , simply install back the legacy kexts , make sure that your SMBIOS.plist is populated with the correct mac information and stuff. For more information , please read this guide
That’s right , nawcom (yeah the author of ModUSBCD) , merklot (the talented guy who made NBI and whos improving Chameleon) , and (hopefully) myself would be working on a new project called v0ltr0n. Whats that you ask , head over here to find out more.
Anyhow to cut the long story short. Voltron is what that something that would change how we install OSX Lion in our hackint0sh. It would make life easier for every one of us. In fact , all you would have to do is install OSX Lion on how would you would do on a real mac. We are not reinventing the wheel here but rather improvising the wheel here
Personally , I would like to get more people to get involved in this. If you are a good coder , or in fact if yo are good in OSX86 or in fact if you think can contribute in any way , feel free to visit nawcom’s blog. Post it . To my old friends (yes you know who you are) , we really need you this time. Hopefully we can work on this project , improving chameleon and hopefully improve entire OSX experience for everyone .
I do hope that there would be a working prototype (or a working version) by the time Lion hits the store . Let us hope and put our hands together to make this project a success !
It has been in the new for a while , but ATI users are able to rejoice finally dong (yes thats his name) managed to discover a way to get LVDS (your laptop LCD screen) to work with Apple’s ATI Driver. He did some magic and kaboom , you are able to get your Mobility Radeon HD card to support QE/CI , Native Resolution and other stuff
However, its not for the faint of heart . Its a bit technical and it would require you to go through some editing and stuff. You would need to be on MacOS X 10.6.7 for you to test few things out. Its a bit sacrrated around InsanelyMac , I’ll try to compile a guide and simplfy things.
But if you are curious and want to get your card working so badly , I recommend you to check this thread out
UPDATE #1 – Check this thread out , its a one stop thread for your ATI Mobility needs. It contains a tutorial and how-to. Again its a bit technical , I recommend you to spend your time. If you are still not sure what’s what , I recommend you to drop by IRC (irc.osx86.hu , #hackint0sh ) – Be sure you’ve done your homework first before asking ! Thanks Joe
Couldn’t fix your OSX partition via fsck or OSX tools ? You want your data back , if so , read this guide
Most of the guides out there explains on how to get OSX86 up and running but there are very few guides out there which explains on how to recover OSX86 partition in an event of file structure corruption. Bear in mind that this guide does not cover fully if your disk starts to fail. By default OSX or your BIOS should alert you if SMART (Its a simple self-check of the device to determine if its O.K or K.O ) status shows that it is not okay.
I’ve faced couple of issues with my disk , mostly related to directory structure. I believe this is because I do not shutdown my computer properly and bam one day OSX did not boot at all. Of course , I tried the usual stuff such as booting into (single user) and tried running fsck . Of course it did show that there was an error with my partition , however it could not fix it. Thankfully I’ve managed to discover few great tools which would help to fix your disk-related issues.
1. You need to have MacOS X Installed on another hard disk or on USB pendrives. I highly recommend you to grab a 16GB or 32GB USB pendrive and install OSX to it. It will be a “reecovery” OSX partition whereby you are able to use it in times of fixing your main partition. This is a must have as for us hackint0sh uses we don’t have the privilege of creating a Disk Warrior recovery disc or stuff like that
2. Your OSX partition (your main system that is) must be using GPT , some recovery tools for Mac (especially related to fixing file structure ) would cease to work in MBR.
Tools that you’ll be needing (provided that you are willing to pay and your data is very important)
Disk Warrior (I highly recommend you to purchase this , if you really want to recover data)
Some of the functionality of these tools do overlap with one another , but I prefer to have more than one tool . These softwares do cost money , so do keep that in mind ! I know , you could resort to dark side if you want too , but thats your call
The Free Method
So you don’t want to fork out $50 on a recovery software. The best way is for you to boot via your “recovery OSX disk” and start copying files over to another drive. If you want to keep your “user settings” preserved , I highly recommend backing up your home folder as it would contain your wallpaper , your downloads and whatever you’ve stored. You could move it as well , however it would not contain your applications which you have installed and other system kexts.
However , it would not fix the problem with the hard disk if the file structure is corrupted. Basically you would have to wipe your hard disk and start all over again
If you insist on doing a 1:1 copy , try CopyCatX or Clone X
(Yes , I know what you are thinking . I am just stating an alternative anyway)
Fixing File System related issues
If you have tried fsck and it did not fix your hard disk issue. This is where Disk Warrior comes in play . Disk Warrior fixes a lot of problem related to the file structure. So if fsck couldn’t fix it , you would use Disk Warrior. A word of caution , Disk Warrior could fix your drive , however you may have risk of losing some of your files. Be sure that you have backed them up. So far I have not faced any issue.
Fixing HDD sectors
If fsck reports no errors with the directory/file structure , and OSX is taking a long time to boot with kernel panics. It simply means one of your HDD sectors is bad.By default , your HDD should alert you that it is failing. If you insist on fixing your hdd sectors , give Drive Genius or Tech Tool pro a shot. There are risks involved in fixing hdd bad sectors. If you want to learn more about HDD sectors , click here
It has been ages since I’ve updated on OSX. I am pleased to announce that , there are newer hardware supports out there. So if you are on a second generation Core i7 computer or if you are using ATI Mobility card there is some hope for you. I’ve discovered some thread in InsanelyMac today.
However bear in mind , that the article on ATI Mobility 4xxx support for hackbook is technical. So you may have to spend some time on understanding. Nevertheless , if you have some questions to ask , feel free to post in that thread or ask me here. I may give you a clearer explanation as mostly its related to programming and stuff. Here is the thread , feel free to check it out
As for the latest and greatest hardware support , tonymac has updated his iBoot to include latest generation stuff
EDIT : Made a mistake there , nawcom’s blog is the place that you should be going to and yes i’ll be updating my blog as well
My blog you ask – I’ll be here on providing some tutorial advice and stuff on OSX issues and Hackintosh in general. Stay tuned for it
Recently , I noticed that my CSR (Cambridge Silicon Radio) bluetooth does not quite work well . These Bluetooth adapters generally cost under $5 and its widely used in many of the laptops. Even real macs do use CSR. I did notice that generic ones would use Apple Generic Bluetooth driver instead of Apple CSR Drivers. Even if you did change the device id and included your device ID in the kext , it would still fail. Of course the generic Bluetooth driver has few issues when it comes to pairing , waking Bluetooth keyboard/mouse from sleep and other general issues
I did a research further and found out that the kext were hardcoded to work with Apple-branded CSR Devices. Yes , we could simply fire up hex editor and include our Device ID and Vendor but this would be complicated and in return it would require us to perform patching every time we upgrade OSX. Thankfully , AnV did something for Broadcom devices. I took the kext and modified it to work with CSR Devices (Cambridge Silicon Devices). Basically it fools , OSX thinking that our Bluetooth adapter is Apple’s Bluetooth Adapter therefore forcing OSX to load Apple’s CSR driver instead of Generic drivers.
Anyway , I am quite sure that you are tired with the explanation. Now lets get our hands dirty and start fixing it.
1. Firstly you would need to know your Device ID and Vendor ID for your Bluetooth adapter. It can be obtained from System Profiler. Be sure to convert it from Hex to Dec. If you are unsure , just google for Hex to Dec Calculator
2. Download this kext . Open it up and navigate your way to Info.plist (if you are unsure , right click and select view package content)
3. In Info.plist replace instances of
<key>idProduct</key> <integer>1</integer> <key>idVendor</key> <integer>2578</integer>
with your Product ID and Vendor ID in base 10 (Dec). You shouldn’t need to replace this value as most of the generic CSR adapter would use this value
4. Place it in your /Extra/Extensions folder (or EFI partition) and fix permission.
5. Reboot and the first thing you should notice is that Bluetooth can be toggled on and off and Wake from Sleep option in Bluetooth shouldn’t be grayed out. If it is still grayed out , you will have to fix your USB (Search for USB DSDT patch)
UPDATE #1 – After studying a bunch of IORegistry (just think of a bunch of detailed stuff , that gives the internal working of a system) . I’ve found out that Firmware version plays an important role here. It seems that these cheap $5 dongle that comes from China have different frimware. Each of it reacts differently