Jump to content


  • Content count

  • Joined

  • Last visited

About tstm

  • Rank
    InsanelyMac Protégé
  1. Just a quick status update: I tried to get sleep to work with both EVOenabler and the d_d supplied ATY_Init. Neither works. Though EVOenabler seems that it could work in 64bit too.. but network doesen't work on 64 as of yet, so I don't think I'm gonna try. I stumbled upon one weird thing though: tstm@orion% kextstat | grep -i ATI ~ 24 0 0x77cd9000 0x8000 0x7000 com.apple.nke.applicationfirewall (2.0.11) <7 6 5 4 3 1> 79 2 0x81309000 0x2a000 0x29000 com.apple.kext.ATISupport (6.0.2) <78 14 13 7 5 4 3 1> 80 0 0x817b6000 0x94000 0x93000 com.apple.kext.ATI4800Controller (6.0.2) <79 78 14 13 5 4 3 1> 87 0 0x81b82000 0xf9000 0xf8000 com.apple.ATIRadeonX2000 (6.0.2) <86 78 14 7 6 5 4 3 1> 93 0 0x8208d000 0x11000 0x10000 com.apple.kext.ATIFramebuffer (6.0.2) <79 78 14 13 7 5 4 3 1> Why is the system loading ATIRadeonX2000 even though I don't have one? Is this happening to everyone?
  2. I've got my SL setup running and almost everything works like a charm! Thanks D_D! (although, as I previously mentioned, the umount still does _not_ work and I have to manually edit the script so that it won't erase my EFI every time I run the script) But I did have a question, too: Does anyone have sleep working with Radeon 4870? Going to sleep works just fine, but waking up just doesen't wake up the display. If someone has working sleep with 4870, I'd be very glad to know what kexts and where you use, and what boot options you run.
  3. Has anyone tried 10.6.1 yet? It's up in SU already.
  4. I found the bug in the script that was causing problems. The unmount_EFI() function did not properly unmount the EFI partition in SL, and thus the rm -rf command in the same function deleted the whole directory and all contents. What I did, was change the row umount /Volumes/EFI > "$TEST_LOG" 2>&1 to: diskutil unmount /Volumes/EFI > "$TEST_LOG" 2>&1 and got significantly further. I still have some issues with graphics (Radeon 4870). The SL installation sounds come up fine (and it responds to keyboard etc), but the screen stays at the verbose command prompt..
  5. It appears that the 4.0 RC installer does not work from inside Snow Leopard. I have SL installed on my MacBook Pro, and I'm trying to install SL on my desktop disk via USB. The SL install does not have all the files required to run the script, I get the following error in install.log: fdisk: could not open MBR file /usr/standalone/i386/boot0: No such file or directory And when listing what's inside /usr/standalone/i386 I get: Firmware.scap boot.efi The whole fdisk section of the logfile goes as follows: fdisk: could not open MBR file /usr/standalone/i386/boot0: No such file or directory Enter 'help' for information fdisk: 1> Disk: /dev/disk3 geometry: 77825/255/63 [1250263728 sectors] Offset: 0 Signature: 0xAA55 Starting Ending #: id cyl hd sec - cyl hd sec [ start - size] ------------------------------------------------------------------------ *1: EE 1023 254 63 - 1023 254 63 [ 1 - 1250263727] <Unknown ID> 2: 00 0 0 0 - 0 0 0 [ 0 - 0] unused 3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused 4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused fdisk: 1> Partition 1 marked active. fdisk:*1> Writing MBR at offset 0. fdisk: 1> Invalid command 'y'. Try 'help'. fdisk: 1> Is there any way to go around this issue for now?
  6. I did a fresh SL install on a dual-partitioned drive (first visible partition being the old 10.5.6 install and the second one being the new SL one) I followed the instructions and got it to boot - once. After I completed the steps of selecting 8, 9, 10 and 11 to go to /Extra and rebooted, I'm greeted with the following lines on boot: ACPI_SMC_PlatformPlugin::start - waitForService(resourceMatching(AppleIntelCPUPowerManagement) timed out Kext com.apple.Dont_Steal_Mac_OS_X module stop pointer is outside of kext range (stop 0x77846053 - kext at 0x81eed000-0x81ef3000).. Kext com.apple.Dont_Steal_Mac_OS_X can't unload - module stop returned 0xdc008007 Im thinking dsmos.kext is having some kind of issues? It does load (gives some success info to the console) but it doesn't seem to work.
  7. Could you tell us some details of your configuration? Namely: BIOS version (F6, F5, F4?) BIOS Settings (USB, SATA, CPU atleast) Motherboard variant, UD5? UD4? Graphics card and driver? Kernel version Bootloader Are you using EFI or Boot132? Versions and names of kexts you are using? (I'm sure someone will come up with a simple command line to list this info, at least if you are on EFI) - One method would be to post a text file or a code quote of the output of "kextstat" when run in a terminal. Amount of memory, and configuration of memory (triple channel?) Boot.plist settings and kernel boot parameters Uh, that's all I can think of now.. but getting that should at least be a good start for us others to get sleep up and running.
  8. I have a gigabit connection to my home (Linux) server, and I can get average transfer speeds up to 75MB/s (600Mbit/s) from an AFP share on said server. So, my network card is working fast enough (this is a _lot_ faster than what I get using Vista & Samba on this same hardware - but that might be a TCP window size issue or something) Oh, and I'm using the integrated network card on the GA-EX58-UD5 (BIOS F5).
  9. You might have the wrong UUID in your com.apple.boot.plist (that was my problem when I first tried EFI boot). If you're using wolfienukes method, either remove the com.apple.boot.plist and regenerate it or simply choose to edit it when the script asks you to. The UUID should be filled in automatically. You can also go and manually edit your com.apple.boot.plist in the EFI partition. You can get the correct UUID by writing: diskutil info "/Volumes/<volume_name>" | grep "UUID" into a terminal. <volume_name> should be replaced by the name of the volume you are installing to.
  10. I tested it a bit further - yes, it seems to be a RAW conversion issue. Everything works fine as long as you don't touch RAW files. Unfortunately I only shoot RAW, I need this feature. Luckily I have my Macbook Pro still operational.. it's just a lot slower than this hackintosh.. I think Aperture is using the builtin RAW conversion in OSX. I'm thinking the issue could be found there?
  11. Oh {censored}. I tried Aperture too, and it crashes on startup. =( Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000 Crashed Thread: 30 I'm assuming this happens to everyone using voodoo/X58/i7 combo? Or could it be only some configuration/kext issue?
  12. I don't know. From wikipedia: S1: All processor caches are flushed, and the CPU(s) stop executing instructions. Power to the CPU(s) and RAM is maintained; devices that do not indicate they must remain on may be powered down. S2: The CPU is powered off. S3: Commonly referred to as Standby or Sleep. RAM is still powered. S4: Hibernation. All content of main memory is saved to non-volatile memory such as a hard drive, and is powered down. UD5 supports S1 and S3 (and S4, too, but that's not a BIOS feature), you can switch between the modes in the BIOS. S1 is useless though, it still uses almost as much power as it does when the computer is on. So, even if S1 worked, it doesen't matter since it's not useful for anything.
  13. You have working S3 sleep? Give me the details! Which BIOS version? You're using UD5? Are you booting via EFI or boot-1-2-3? Which bootloader do you use? Which kernel are you running? It would really be nice to get sleep to work.
  14. There's a new BIOS up, F6. Has anyone tried it already? Does it fix the sleep issues? Does DD have sleep working, and if, with what BIOS? Link to BIOS
  15. Well, I can tell you how NOT to do it. The install itself seemed fine using the following instructions (of course <disk> should be replaced with the correct number): 1. download Chameleon zip file 2. unzip file 3. open up terminal 4. cd / 5. mkdir /Volumes/EFI; sudo mount_hfs /dev/disk<disk>s1 /Volumes/EFI; cd /Volumes/EFI 6. sudo mkdir Extra; sudo cp -R /Volumes/EFI/Extensions /Volumes/EFI/Extra 7. cd into Chameleon download directory 8. sudo cp -R smbios.plist Themes /Volumes/EFI/Extra 9. sudo fdisk -f boot0 -u -y /dev/rdisk<disk> 10. sudo dd if=boot1h of=/dev/rdisk<disk>s1 bs=512 count=2 11. sudo cp boot /Volumes/EFI The Chameleon bootloader loaded and everything seemed to work fine (Windows booted like a charm) - but ALAS when I tried to boot into OSX, I got lots of SMC errors and IOKitWaitQuiet errors etc, and then the system hung with a light blue screen. With a little googling, I think the reason was that the blacklists needed for Wolfies EFI are not working properly. The IOKitWaitQuiet errors manifest when AppleHWSensor.kext (which is normally blacklisted) loads up (correct me if I'm wrong). So, as of now, I didn't get the EFI solution working with the Chameleon bootloader. Luckily the boot code is easy enough to replace.. and now I'm back to the standard boot process..