Jump to content


  • Content count

  • Joined

  • Last visited

About Potemkin

  • Rank
    InsanelyMac Protégé

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
  1. Gigabyte EP45-DS4P For those looking into EP45-DS4P motherboards - glad to report it works almost a 100%. All the motherboard features including 2xLAN, Firewire, and audio seem to work short of going to sleep at the moment which I haven't looked too much into yet. I've only had the Kalyway install sitting around which I set up using a vanilla kernel but I'm sure a retail install with a bootloader will work just fine (see the LS8 guide). The mobo is in many respects similar to the D6Q. I'll go into a bit of detail on how to get some things going, and in the meantime here is my setup: EP45-DS4P Q6600 4GB of Mushkin RAM Pioneer SATA DVD-RW Radeon HD 2400XT (the dreaded 94c1) Radeon X1950 XT Linksys WUSB54GC wireless adapter Mini Ninja heatsink (zero to do with Macs - just thought it's a cool name, mini NINJAAaaaa.... yeah) INSTALLATION I've tried SATA in both AHCI and RAID modes and they both work (haven't tried setting up an actual hardware RAID yet though - would be neat). All the BIOS settings aside from SATA were left as default. Installation was a simple as popping in the Kalyway DVD and installing off of it. Among the components I've chosen both the ACL889 audio and the rt73 drivers for my WUSB54GC wireless but neither worked after the install was done. Outside of that everything installed great and I even transferred all data from my MacBook via Firewire upon the first bootup. Four things did not work out of the box - wireless, audio, my Radeon 2400XT (no kext loaded) and shutdown/sleep/restart. Let's do them one by one. RESTART/SHUTDOWN Kinda nice to be able to restart and shutdown. I used the OpenHaltRestart.kext though there is also the "classic" ACPI method. I tried both from karaakeha's guide and the ACPI way resulted in a kernel panic. I'll try it again tonight but for now OpenHaltRestart the way that works for sure. Here is how: Copy OpenHaltRestart.kext into your /System/Library/Extensions folder Go to Terminal (spotlight to the rescue! Command+Space that sucker) Type out: sudo -s and punch in your admin password Do this: chmod -R 755 /system/library/extensions/OpenHaltRestart.kext Then this: chown -R root:wheel /system/library/extensions/OpenHaltrestart.kext Ok, then: rm -R /system/library/extensions.mkext And lastly: kextload -k /system/library/extensions That otta do it. That procedure is what you should follow any time you install an extension. All you're doing is setting the proper permissions: chmod 755 sets the file to be writable only by the owner and read-only for everyone else and chown changes the owner to the root user (the -R flag means recursively apply the commands to all files in the folder - after all extensions are not files but folders). And in the last two steps you're deleting the extensions cache and then recreating it. Oh, and I really don't know why all those guides bother to use proper letter casing for paths - the default HFS+ partition is case insensitive, a nice break for any *nix user. LINKSYS WUSB54GC Getting the WUSB54GC by Linksys running took a bit of searching but is fairly easy to get going: Download these two archives: One and Two (both are from this thread) Install #1, reboot with the -f flag, then install #2. That's it. After the second reboot you should see the USBWireless utility and be able to connect to any network using either WEP or WPA. Hooray! Audio (ACL889) The EP45-DS4P comes with the ALC889a audio chip much like the D6Q. I've tried a number of extensions here and the ones that worked were all in the D6Q thread. Download the extension here (alternatively there is a supposedly pop free extension but I haven't tried it yet - haven't noticed any disturbing pops yet). Unpack the archive, that'll produce AppleHDA.kext and the HDAEnabler.kext Follow the same steps as in the wireless section above (ie. copy both into /System/Library/Extensions, set the correct permissions and reload the kext cache) Reboot and you should now have sound (check in System Profiler and the Sound pane of the system preferences). Time to put some of that Diana Ross on! Radeon HD 2400XT My graphics card, the Radeon HD 2400XT (fanless Gigabyte GV-RX24T256H - awesome for audio production work I'm involved in) took a bit of work but works great now. None of the extensions I found (the x2000 ones) worked for me - all I got was a bunch of random lines of screen and had to reboot in safe mode (-x flag) to get rid of the offending kext file. So, what you do is you flash the BIOS with one for an HD 2400 Pro. Yes, the Pro is worse than the XT but come on, you weren't really planning on building a high-end gaming machine with that s**t to begin with were you? The original thread I found isn't terribly specific and I ended up f**cking up my Radeon's video BIOS, which is why I got a x1950 now, good for playing the many games on the Mac, such as umm... Dora the Explorer Animal Adventures I guess. Anyway, here is what you do: Double-check you've got the right Radeon - click on the Apple logo > About This Mac > More Info and under Graphics check to see 94c1 is listed as the Device ID. If you don't have a floppy drive or a DOS bootdisk, get yourself an Ultimate Boot CD. Download the latest image and burn it on a CD. The nice thing about it is it's got FreeDOS which gives you NTFS and USB drive support. As you'll see in the next steps that comes in handy. Get the latest BIOS and the ATIFLASH utility. Make sure to get the BIOS for the 2400 Pro 256MB (in the release notes for the BIOS you should see the device ID as 94c3). Unpack everything and save it somewhere convenient. I used a USB stick which will work great if you have an Ultimate Boot CD or any other boot disc that supports USB devices. Load up from Ultimate Boot CD (hit F12 on POST screen to pick the optical drive) and go into Boot floppies > DOS > FreeDOS. In my case C: drive ended up being the USB stick, if that's not the case just type in D: or whatever letter name your stick is at. Navigate your way through to the folder with ATIFLASH and the BIOS's (if you're too young to remember the DOS days or have amnesia, use dir to list the files and cd [directory name] to move from folder to folder). Do this: atiflash -ai That will list all display adapters you've got along with some helpful info. Take note of the number of the adapter (one of the first things listed on the left). If you've only got one graphics card it will be 0. In my case the x1950 is 0 and the 2400XT is 1. Also make sure once again you've got 94c1 as the ID. Now run this: atiflash -s [adapter number] OLDBIOS.bin That will create a backup of your current video BIOS and save it under OLDBIOS.bin. If you screw up you can restore from it later, though you'll need another graphics card in your system like I do. Aight, we're all set. A deep breath and: atiflash -p [adapter number] [newbios.bin] -f Instead of newbios.bin substitute whatever the filename is of the 2400 Pro BIOS file. My guess your name will be ugly as it's probably more than 8 characters. Ah, DOS! . The -f flag is there to force the BIOS in regardless of errors - on my card the SSID's didn't match and the utility seemingly errored out but upon next reboot everything on the screen was f**cked up which was inconvenient. Reboot. If you see the POST screen it's all good. If you see something else then call up your nerd friend and borrow a PCIe video card. Repeat the procedure, just replace the newbios.bin with oldbios.bin in the previous step. Boot into OS X. If you've already got the x2000 kext from a Kalyway install you should see that the resolution has improved and you can enable QE. To double-check, open up the System Profiler (under About this mac) and check under Graphics - it should give you information about the card now. If you haven't got the kext or everything looks the same ie. you can't change the resolution under the Display settings, read on. Get the x2000 kext. Edit the Info.plist to include the 94c3 device ID. This needs a separate thread of its own, and luckily for me there is one out there already - just follow this mini-guide for the 2400 Pro. Remember - now that you flashed the BIOS your videocard is a 2400 Pro, not an XT. Install the kext file like the guide suggests or do it the manual way I described in the Linksys wireless adapter section - I personally like to do things manually so I know what's going on, and I'm assuming you're nerdy enough too. How do I know that? Come ON, you're reading a freaking hackintosh guide! Eesh). Reboot. You should now have the video working properly. Time to enable Quartz GL for some EKSTREME GRAFiX. Save time and get the OSX86 Tools. Unpack and run them, and just click Enable QGL at the top left. To add Quartz Extreme check this link out. Basically you have to add the 94c3 to the Info.plist file. Easy-peasy! Reboot and wooow, it should all work. Mandatory step - while holding Shift press F12 to call up the widgets. WHOAA. It's like, widgets MATRIX-style dude! Trippy. That's it. You should be up and running with the 2400XT now. BACKUP At this point it wouldn't hurt to backup. I personally use SuperDuper! because it makes very nice bootable backups. If you like it too you'll encounter a weird error on the hackintoshes as the program tries to erase your drives. It'll say _CFGetHostUUIDString: unable to determine UUID for host. Just follow this short guide. Fixed the problem for me. POST-SCRIPTUM This is my second hackintosh and I'm quite happy. I've sold my MacBook and was waiting for Apple to come up with their new Air-like MacBook Pros but the specs on there turned out to be plain s**t so here I am, with a quad-core Mac for the price of a midrange MacBook. SCORE! I'll try to keep this guide updated as I go along and install updates and other add-ons to make the system polished. Let me know if you find an error or just want to b*tch for no good reason.
  2. The uber searching skills of the quoted person are Greatly appreciated! Would be nice to get admins to edit the original post so hunting around wouldn't have to be done.
  3. linksys wusb11 v2.8

    WUSB11v2.8 is Not based on a Prism chipset, but rather on an Atmel. Here is a table with all the revisions and the chipsets they're based on - http://kismac.de/_trac/wiki/WUSBVersions Still, none of the versions have any drivers for Intel Macs. The driver you would use on a PowerPC would be the D-Link DWL122 with some changes to the Info.plist. Otherwise.. Even if you had the right version, it still would not be compatible. You can, however, use Kismac with with v.2.5, so I suppose it's good for Something.
  4. 10.4.3 broadcom wireless effort

    Thanks a lot, crusher. That helped, and the wireless chip on my HP Compaq nx6110 was recognized as AirPort. Right now I'm trying to connect to some of the neighbour's networks . EDIT: Shame AirPort isn't based on a Prism2 chip.. I could KisMAC those maroons =).
  5. (Almost) Hidden Secrets of OS X

    Try calling Expose and widgets up while pressing shift. It should produce a slow-mo effect. Don't ask me how that's useful... Maybe there were a series of customers for whom the suddenly popping up widgets created a migrane, I don't know..
  6. Final Cut Pro 5.0 - installed and working.

    I couldn't install using the main file even after deleting all the files as suggested and editing the script, so I followed the method of installing every package seperately. It worked. I install every single but one, and FCP loaded. Now is the time to get some test footage from the back up DVDs .
  7. Interesting phenomena

    Guess what . I was right. I freed up some space on the new partition so there's over a gig left and it booted again! SO. It looks like even though OSX sees that there is more space available, it does not somehow recognize it during the booting process and hangs. I'm going to test it again one more time now, but I'm pretty sure it's going to be the same. And for those of you who started getting the root device error while the system worked before and you used the same method of cloning, try freeing up some space after booting up from the old small partition which you should've kept since you really are supposed to know there is nothing stable about this yet .
  8. Hello everyone . After installing OSX, I now occasionally have questions about it. Some of them I can find answers, some I can't. I've found the way to solve the problem with the End and Home buttons being absent in OSX which is Command+Arrow Left or Right. But now I have a networking question. I have my MP3s residing on a windows tower, so to reach them in OSX I go on the network and connect to the folder. But the problem is that I have to do it every time I start OSX, or run iTunes. For some reason it appears to be connected every time an app requests the folder on the network, like iTunes. As soon as I try playing a track, I get an error about the file being absent, BUT the folder with MP3s gets mounted. I have to restart iTunes to listen to music. Now, is there a way to write a line of code in some config file to automount the folder during the booting process, or maybe that's too much of a linux approach . Maybe there is some way to do it through the GUI? Thanks. I'll probably have more OSX questions coming .
  9. Interesting phenomena

    Hello everyone. I have just noticed a weird problem. The first time it happened I didn't pay much attention but... I sucessfully made a clone of the small partition, and started copying new stuff over it. But today it got stuck while booting from it, so I erased everything with the Disk Utility and recreated the bigger partition. It worked, I moved all the new stuff over again and started unpacking it when... After a reboot it won't load again! And everything seems fine until you reboot. I think this has to do with the size of the partition. I think somehow there is still data on the HDD that the partition is 6 GB. When I start moving things over it works, but then during the booting process the system gets confused, as the partition size is supposedly 6GB but the amount of space occupied by data is, say, 8 GB. Is that possible? Because I think that's where it lies. Everything works until I start installing all the stuff on the big partition which starts exceeding the 6GB limit. EDIT: I used the method described in Wiki. I used Carbon Copy Cloner to copy the files, and then fdisk to make the partition bootable. I'm yet to make the Disk utility method work. Maybe that way the system will boot.
  10. mitnicki - Boot in verbose mode (type in "-v" when you're promted to choose which partition to boot from) and note the line where it gets stuck. It will probably say "still waiting for the root device", but you can at least see what is causing it.
  11. I get this message whenever there is Quartz used. I.e. when I try running Preview natively, without Rosetta, loading a screen saver, or now, after a 10.4.3 update, when I load up a website with some flash graphics in Safari (apparently the "updated flash plugin" is causing it). Any idea about how to resolve that? It was kinda fun trying to turn off the screen saver, cause it would freeze whenever I go into Preferences. I ended up just trashing all the screen savers from /System/Library/Screen Savers, and then setting the timer to Never. Preview is also fixable. But flash plugin...Ah.. Bound to use Camino for now, I guess. Or firefox.
  12. no: Cursor Shadow

    JESUS CHRIST. It's only a cursor shadow!! First people go crazy over iTunes universal binary, now it's the cursor shadow... BUY A MAC!!!
  13. Cloning on another HDD

    On another note, updating to 10.4.3 hasn't changed much. My Xbench results went up from 21.52 to 25.50... Heh.
  14. Cloning on another HDD

    OK. I got this working . I think the important detail that the guides so far were missing is that you have to make the new bigger partition ACTIVE. In Windows I just used "select partition" and then typing "active". So I did that, and after that I wouldn't get the chain0 booting error that I would get prior to that. Then I copied everything using Carbon Copy Cloner, and made the partition bootable after writing the MBR on the partition using fdisk (check the Technical FAQ on Wiki if you don't know how). Then rd=disk0s3, voila! .
  15. Cloning on another HDD

    I have just loaded in the verbose mode with the "rb=NewPartition" (NewPartition, of course, not being the actual name I'm using), and it gets stuck telling me that "ATA device claims FLUSH CACHE EXT feature support but does not claim Extended LBA feature support". Just to be sure I checked the BIOS, disabled the SATA controller to only have the PATA devices, and checked that both of the hard drives have the LBA mode on (which isn't the extended one, I believe). The interesting part is that the master hard drive is 80GB and the slave 40 GB (both by Maxtor). So neither of them even needs the Extended LBA mode. I need to look for a way to disable it.. Still no luck... OSX now will only boot from the 6 GB partition of the slave drive. EDIT: One more detail. Each drive has 2 NTFS partitions before the HFS+ partition, so the OSX partitions don't take up the whole drive on either of those. Another EDIT: I have just searched through various Darwin boards and it appears that the Extended LBA warning has nothing to do with the system freeze. On all other machines the system just continues on with booting. But here I get the same "waiting for the root device" error as a lot of other people. That's quite peculiar..