nateB Posted April 23, 2009 Share Posted April 23, 2009 Hmmm. I haven't experienced this issue. USB only works when plugged in at boot time? Have you done another restart?... Can anyone else chime in as regards USB hotplugging with the updated script? I'm at work now. regards, MAJ Same issue here. If any USB drive is inserted at start up, any external drive will mount after boot. As long as I keep a flash drive inserted I can attach and remove other drives while the system is running. I also saw this happening on the EFI boot setup with the 9.6.3 kernel. Link to comment Share on other sites More sharing options...
digital_dreamer Posted April 23, 2009 Author Share Posted April 23, 2009 i am experiencing the 'double-time' fast clock/time weirdness with an EFI install using wolfienuke's script as well. at first i thought maybe wolfie's kexts were different since they have slightly different names. so i instead moved digital_dreamer's kexts over to the efi partition and rebuilt Extensions.mkext. but i had the same problem. it seems to me like boot.plist isnt actually getting parsed, because the model number and dram are no longer set. i thought maybe i needed chameleon 2.0 for this to work right, so i upgraded but still no joy. also it does not seem to be taking my EFI strings so that's further evidence. interestingly after upgrading to chameleon 2.0, the 2x clock problem was not there. however it does seem like some kexts did not load - for instance my USB flash drive stopped mounting. so that may have 'fixed' the clock issue but the system still is not working right. does anyone know who picks up those boot flag strings? is it the kernel itself or the hacked AppleSMBIOS.kext? i know that some kexts don't load properly from the EFI partition... i have however removed the vanilla versions from /S/L/E so there should be only one place to get the new kexts. i put my boot.plist both in the root of the EFI partition and in the Extras folder. i even fixed the boot.plist in /Library/Preferences/SystemConfiguration, but still no joy. hmm. edit: i just realized that i forgot to change the osbundlerequired string in the info.plists to 'root'... i think this will prevent the kexts from loading right. this is something that wolfienuke's script does (right??) but since i moved the other kexts in it was necessary to do it by hand. i'll try this tonight, or maybe just start over and edit the script to use chameleon. also my thinking here is that if busratio=20 is not properly parsed, the timebase for the internal clock will be wrong. i realize that some kernels will not boot at all unless this flag is passed, but i am using the kernel from 10.5.7, which i assume can figure out the multiplier on its own (?) When you upgraded to Cham 2.0, did you use the included smbios.plist? (Was it installed in Extra EFI?) Curious, as that may provide a clue regarding the clock issue. Personally, I didn't use it and didn't have the clock issues, so if you didn't either, it may confirm my theory that the included smbios.plist contributes to this issue. But, I haven't had any feedback from others regarding whether they are using it or not. regards, MAJ Same issue here. If any USB drive is inserted at start up, any external drive will mount after boot. As long as I keep a flash drive inserted I can attach and remove other drives while the system is running. I also saw this happening on the EFI boot setup with the 9.6.3 kernel. I bet there's an upgraded System.kext for this kernel, but we never got a copy and have just used the 10.5.6 version. Anyone have a System.kext from 10.5.7 to make available? regards, MAJ Link to comment Share on other sites More sharing options...
phabmp Posted April 23, 2009 Share Posted April 23, 2009 Okay, so I've got all my hardware set up and BIOS configured (followed the BIOS screenshot in the first post), and attempted the first boot following the non-efi retail boot method with the vanilla kernel and so on. It boots, sits at the Apple logo for several minutes, and then moves to the darker gray screen with a controllable mouse cursor, doing nothing else. It polls the HD slightly every minute and a half or so, though. I booted in verbose mode and found that it was getting repeated smcSMCInABadState errors (stating that the SMC is stuck and cannot recover), and then it eventually goes to the gray screen. All I have currently installed in the computer is: GA-EX58-EXTREME 6x2GB DDR3 EVGA 9800 GTX+ Lite-On SATA optical drive (I forget the model number, I doubt it'd be causing the issue anyway) 750GB Seagate SATA drive Netgear WN311B wireless card Generic 3.5" card reader, working over internal USB header. I'm going to try removing the wireless card and the card reader. If that doesn't get it to boot, does anybody have any ideas? EDIT: Nope, removing the cards didn't do it. I also did a slightly different install process- after the digital_dreamer's script had me run the OS X installer, I also installed the 10.5.6 combo update. This was before the post-install scripts were run. Would that have caused the problem? Was it the wrong time to run the update? EDIT 2: Tried updating to F6 BIOS, no dice. Link to comment Share on other sites More sharing options...
mattrb Posted April 23, 2009 Share Posted April 23, 2009 I bet there's an upgraded System.kext for this kernel, but we never got a copy and have just used the 10.5.6 version. Anyone have a System.kext from 10.5.7 to make available? Too bad that no one posted the system.kext from the i7 macpro Link to comment Share on other sites More sharing options...
nine3o Posted April 23, 2009 Share Posted April 23, 2009 pssh. probably not. I tested 3.6ghz at stock, though for 3.5 hours. Still when I leave it on [auto] for voltage is it really the number shown to the left or some random voltage the bios decides? I usually don't have much to say on here but I have to jump in on this one as I don't want any one frying their CPU with too much voltage. The value to the left of AUTO is not your true voltage for the CPU. If you plan on over clocking, do not use the AUTO setting as it applies more voltage than you really need to achieve the overclock you want. At 3.7Ghz and the value set to AUTO you most likely have well over 1.4V and that is way too much for what you are trying to get. AUTO works for sh*t for some reason, and if you want to know the true voltage value, leave your settings as they are and run CPU-Z in Windo$e and that will give you the proper value you are running at. Link to comment Share on other sites More sharing options...
Brandon2004 Posted April 23, 2009 Share Posted April 23, 2009 Can't remember who PM'd me, but evidently you guys need this so here it is... sorry for not posting it earlier [edit] Sorry guys that was the one from 9.6.2 and it didn't work I can't get to the apple store today but I might be able to go tomorrow that's where I got the kernel. Link to comment Share on other sites More sharing options...
digital_dreamer Posted April 23, 2009 Author Share Posted April 23, 2009 Okay, so I've got all my hardware set up and BIOS configured (followed the BIOS screenshot in the first post), and attempted the first boot following the non-efi retail boot method with the vanilla kernel and so on. It boots, sits at the Apple logo for several minutes, and then moves to the darker gray screen with a controllable mouse cursor, doing nothing else. It polls the HD slightly every minute and a half or so, though. I booted in verbose mode and found that it was getting repeated smcSMCInABadState errors (stating that the SMC is stuck and cannot recover), and then it eventually goes to the gray screen. All I have currently installed in the computer is: GA-EX58-EXTREME 6x2GB DDR3 EVGA 9800 GTX+ Lite-On SATA optical drive (I forget the model number, I doubt it'd be causing the issue anyway) 750GB Seagate SATA drive Netgear WN311B wireless card Generic 3.5" card reader, working over internal USB header. I'm going to try removing the wireless card and the card reader. If that doesn't get it to boot, does anybody have any ideas? EDIT: Nope, removing the cards didn't do it. I also did a slightly different install process- after the digital_dreamer's script had me run the OS X installer, I also installed the 10.5.6 combo update. This was before the post-install scripts were run. Would that have caused the problem? Was it the wrong time to run the update? EDIT 2: Tried updating to F6 BIOS, no dice. Sounds like you tried the usual routes to troubleshoot the issue. You got the install process down correctly - the post-patch is just that, a patch after the OS install. I don't recall ever seeing those types of errors. Can you run any other OS on this board? Would like to see a full photo of the on-screen log. I usually don't have much to say on here but I have to jump in on this one as I don't want any one frying their CPU with too much voltage. The value to the left of AUTO is not your true voltage for the CPU. If you plan on over clocking, do not use the AUTO setting as it applies more voltage than you really need to achieve the overclock you want. At 3.7Ghz and the value set to AUTO you most likely have well over 1.4V and that is way too much for what you are trying to get. AUTO works for sh*t for some reason, and if you want to know the true voltage value, leave your settings as they are and run CPU-Z in Windo$e and that will give you the proper value you are running at. Thanks for the heads-up on this. You're right, this is too important a issue to let by with misleading information. Thanks for clarifying that. I assumed it was running at a lower voltage than usual because he reported his CPU temperatures about 10°C cooler than mine when pegged, as well. Lower voltages mean lower temps. If you're correct, would that mean that when the BIOS is running, it's not really in OC mode and it's just reporting some default startup voltage? Or, it may be that those fields are simply for the BIOS to read data from (when not in Auto mode), but not print/display data to. That might explain why in Auto it doesn't display working settings. Not exactly helpful, to be sure. Would be anxious to hear what CPU-Z reads. mangopeach? Do you have Windows? EDIT: Too bad CPU-X doesn't report voltages. Of course, it would have to support multiple motherboards for that. MAJ Can't remember who PM'd me, but evidently you guys need this so here it is... sorry for not posting it earlier [edit] Sorry guys that was the one from 9.6.2 and it didn't work I can't get to the apple store today but I might be able to go tomorrow that's where I got the kernel. Cool. I'm surprised no one else has posted this kext. We can't be the only ones running this kernel and having this issue. Well, it may be proof we are the only ones ahead of the curve. To the bleeding edge, lets go. regards, MJA Link to comment Share on other sites More sharing options...
joeblough Posted April 23, 2009 Share Posted April 23, 2009 When you upgraded to Cham 2.0, did you use the included smbios.plist? (Was it installed in Extra EFI?)Curious, as that may provide a clue regarding the clock issue. Personally, I didn't use it and didn't have the clock issues, so if you didn't either, it may confirm my theory that the included smbios.plist contributes to this issue. But, I haven't had any feedback from others regarding whether they are using it or not. regards, MAJ I bet there's an upgraded System.kext for this kernel, but we never got a copy and have just used the 10.5.6 version. Anyone have a System.kext from 10.5.7 to make available? regards, MAJ i did not use the smbios.plist to my knowledge. originally i installed using your script for a non-efi install and along the way i upgraded to chameleon 2.0, but i did not run their installer, i just copied the files by hand. so i dont think i had the smbios.plist then. last night when i did the EFI install, i don't think i used the smbios.plist, since i thought i was taking care of the important stuff (bus ratio, model name, dram speed [though the last 2 are just cosmetic, right?]) with the boot flags. i wondered if using smbios.plist would just mess things up. i guess i should try putting it in just to cover the whole space here. i think tonight i will try starting over with the EFI method, load chameleon 2.0, and hand-edit your original kexts for the non-EFI install to increase their version numbers and osbundlerequired. unless these kexts don't load from EFI properly, i dont see why this should not be equivalent to the non-EFI install. but clearly there's some problem reading the boot.plist in this configuration. to be honest i dont really know why wolfienuke's original EFI kexts didnt work right for me, but my thinking here is that since your script yielded a working install then those kexts should be good no matter where they live. the double-time problem was one issue with the EFI install, another was that the HDA driver kept throwing assertions into my system.log. if EFI try 2 doesnt work i might give up on the EFI partition and just put all your kexts in /Extra in the form of a mkcache. my goal is just to have the hacked kexts somewhere other than /S/L/E. i never did this on my badaxe2 and as a result i'm always clenching when its time to load a new release of OSX. hopefully very soon 10.5.7 will be out and we can get that system.kext. but the 10.5.6 system.kext seemed to work fine against the 9.6.3 kernel on the non-efi install. Link to comment Share on other sites More sharing options...
boogusboy Posted April 23, 2009 Share Posted April 23, 2009 When you upgraded to Cham 2.0, did you use the included smbios.plist? (Was it installed in Extra EFI?)Curious, as that may provide a clue regarding the clock issue. Personally, I didn't use it and didn't have the clock issues, so if you didn't either, it may confirm my theory that the included smbios.plist contributes to this issue. But, I haven't had any feedback from others regarding whether they are using it or not. regards, MAJ I bet there's an upgraded System.kext for this kernel, but we never got a copy and have just used the 10.5.6 version. Anyone have a System.kext from 10.5.7 to make available? regards, MAJ I really don't think smbios.plist has anything to do with it. I'm not on Cham 2.0, and I certainly don't have smbios.plist, but I am having the clock issues. My FSB reports as 533Mhz. I tried removing all SMBIOS kexts from EFI partition and it made no difference other than misreporting the CPU freq. Also tried with and without system.kext in EFI partition, no difference. If anything, I'd think having smbios.plist or some hardcoded value smoewhere would fix it, rather than break it. Link to comment Share on other sites More sharing options...
bernito Posted April 24, 2009 Share Posted April 24, 2009 Anyone having wake from sleep issues with Wolfie install? My new box goes to sleep, but cannot get it to wake up. Running wolfie, 10.6 and voodoo kernal. Thanks in advance for any suggestions. Link to comment Share on other sites More sharing options...
phabmp Posted April 24, 2009 Share Posted April 24, 2009 Sounds like you tried the usual routes to troubleshoot the issue. You got the install process down correctly - the post-patch is just that, a patch after the OS install.I don't recall ever seeing those types of errors. Can you run any other OS on this board? Would like to see a full photo of the on-screen log. After having the issues with the standard install, I tried doing my own install with the Chameleon install package and the kexts and kernels from your pack, but all I could get it to do was start Chameleon. Once I tried to boot OS X, I'd get a split-second white flash and then the computer would reboot. After that, I followed wolfienuke's method with the latest files for it. The bootloader would start, but while OS X would start up, it'd eventually get to a point where it was trying to access the hard drive, occasionally saying that it was still trying to read the hard drive. (At this point I was kind of frustrated and forgot to actually write down the actual message). Ideally, what I'd really like is to boot from EFI with Chameleon, but I'm honestly at a loss as to what to do. Does anyone have any ideas? EDIT: Also, I haven't tried any other OSes on it, yet. I suppose I'll go ahead and try loading Vista onto it. EDIT 2: I couldn't find my Vista disk, but it loaded a Windows livecd just fine. Link to comment Share on other sites More sharing options...
joeblough Posted April 24, 2009 Share Posted April 24, 2009 Anyone having wake from sleep issues with Wolfie install? My new box goes to sleep, but cannot get it to wake up. Running wolfie, 10.6 and voodoo kernal. Thanks in advance for any suggestions. had the same problem with d_d's script until i switched to the 9.6.3 kernel from 10.5.7. note that if you do this you will need to grab the system.kext from 10.5.6 and replace the one installed by the script, because the script installs the one that corresponds to the voodoo kernel, and they are not compatible. or you can just use the new script that uses the 9.6.3 kernel. i cant be 100% about this because i had another problem - the UD4P chose 1066MHz and 8-8-8-20 for my dimms. my dimms are speced to 1333MHz so i bumped up the multiplier, but i forgot to change the cas latency to 9-9-9-24 which are the spec'd latencies for that memory. this would cause the machine to occasionally fail POST, and possibly lock up when resuming from sleep. Link to comment Share on other sites More sharing options...
bernito Posted April 24, 2009 Share Posted April 24, 2009 had the same problem with d_d's script until i switched to the 9.6.3 kernel from 10.5.7. note that if you do this you will need to grab the system.kext from 10.5.6 and replace the one installed by the script, because the script installs the one that corresponds to the voodoo kernel, and they are not compatible. or you can just use the new script that uses the 9.6.3 kernel. i cant be 100% about this because i had another problem - the UD4P chose 1066MHz and 8-8-8-20 for my dimms. my dimms are speced to 1333MHz so i bumped up the multiplier, but i forgot to change the cas latency to 9-9-9-24 which are the spec'd latencies for that memory. this would cause the machine to occasionally fail POST, and possibly lock up when resuming from sleep. Thanks for the reply. I assume you meant Wolfienuke's script as I have the EFI partition boot with retail 10.5.6? Link to comment Share on other sites More sharing options...
joeblough Posted April 24, 2009 Share Posted April 24, 2009 Thanks for the reply. I assume you meant Wolfienuke's script as I have the EFI partition boot with retail 10.5.6? sorry i missed that in the title of your post. as of yet i have not had an install of Wolfienuke's package that worked as well as digital_dreamer's. i'm still working on it... i also don't currently have sleep using the EFI method. but my video card is not being recognized correctly so that might be the cause. i dont know why the EFI strings are not working; they are in com.apple.boot.plist which is in /Extras (using chameleon 2.0) Link to comment Share on other sites More sharing options...
edvardlee Posted April 24, 2009 Share Posted April 24, 2009 hi everybody, i got all my hardware now having installation problems here is the log. can someone help me with this? the mobo is DFI Lanparty Jr X58 T3H6. I'm stumped tried everything i knew. # EFI Partition Boot Install Log # diskutil eraseVolume "HFS+" "EFI" /dev/disk5s1 Started erase on disk disk5s1 Erasing Mounting disk Could not mount disk5s1 with name after erase Finished erase on disk disk5s1 # cd "/Users/edvardlee/Desktop/Digital Dreamer Hackintosh/EFI Boot Installer v3/Bootloaders" # ./fdisk -f boot0 -u -y /dev/rdisk5 # dd if=boot1h of=/dev/rdisk5s1 2+0 records in 2+0 records out 1024 bytes transferred in 0.001251 secs (818557 bytes/sec) # cd "/Users/edvardlee/Desktop/Digital Dreamer Hackintosh/EFI Boot Installer v3" # mkdir /Volumes/EFI # mount_hfs /dev/disk5s1 /Volumes/EFI # ./fdisk -e /dev/rdisk5 fdisk: could not open MBR file /usr/standalone/i386/boot0: No such file or directory Enter 'help' for information fdisk: 1> Disk: /dev/rdisk5 geometry: -5415437/4/63 [-1364690128 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 - -1364690129] GPT 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> Device could not be accessed exclusively. A reboot will be needed for changes to take effect. OK? [n] Writing MBR at offset 0. fdisk: 1> # cp "/Users/edvardlee/Desktop/Digital Dreamer Hackintosh/EFI Boot Installer v3/Bootloaders/boot-turbo-munky.bin" /Volumes/EFI/boot # cp "/Users/edvardlee/Desktop/Digital Dreamer Hackintosh/EFI Boot Installer v3/update.sh" /Volumes/EFI/ # mkdir -p /Volumes/EFI/System/Booter # mkdir -p /Volumes/EFI/Extensions # mkdir -p /Volumes/EFI/.fseventsd # touch /Volumes/EFI/.fseventsd/no_log # mkdir -p /Volumes/EFI/Extensions # cp -r "/Users/edvardlee/Desktop/Digital Dreamer Hackintosh/EFI Boot Installer v3/Extensions" /Volumes/EFI/ # cp -r "/Users/edvardlee/Desktop/Digital Dreamer Hackintosh/EFI Boot Installer v3/Kernels/" /Volumes/EFI # cp -r "/Users/edvardlee/Desktop/Digital Dreamer Hackintosh/EFI Boot Installer v3/com.apple.boot.plist" /Volumes/EFI/ # cp "/Users/edvardlee/Desktop/Digital Dreamer Hackintosh/EFI Boot Installer v3/DSDT_Patcher/dsdt.aml" /Volumes/EFI/ # cd /Volumes/EFI # chmod +x update.sh # ./update.sh Updating EFI boot cache mv: rename /Volumes/EFI/System/Booter/Extensions.mkext to /Volumes/EFI/System/Booter/Extensions.mkext.previous: No such file or directory done. # rm -r "/Users/edvardlee/Desktop/Digital Dreamer Hackintosh/EFI Boot Installer v3/EFI_Backup/" # cp -r /Volumes/EFI/ "/Users/edvardlee/Desktop/Digital Dreamer Hackintosh/EFI Boot Installer v3/EFI_Backup/" -----com.apple.boot.plist----- <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Kernel</key> <string>bt(0,0)/mach_kernel.voodoo</string> <key>Kernel Flags</key> <string>busratio=20 boot-uuid=30DD950D-EBCA-3B03-821E-4DFD02E09F27</string> </dict> </plist> -----EFI Partition File List----- /Volumes/EFI /Volumes/EFI/.DS_Store /Volumes/EFI/.fseventsd /Volumes/EFI/.fseventsd/fseventsd-uuid /Volumes/EFI/.fseventsd/no_log /Volumes/EFI/boot /Volumes/EFI/com.apple.boot.plist /Volumes/EFI/dsdt.aml /Volumes/EFI/Extensions /Volumes/EFI/Extensions/.DS_Store /Volumes/EFI/Extensions/AppleSMBIOS.kext /Volumes/EFI/Extensions/dsmos.kext /Volumes/EFI/Extensions/HDAEnabler.kext /Volumes/EFI/Extensions/IONetworkingFamily.kext /Volumes/EFI/Extensions/LegacyAppleAHCIPort.kext /Volumes/EFI/Extensions/LegacyAppleIntelPIIXATA.kext /Volumes/EFI/Extensions/LegacyHDAController.kext /Volumes/EFI/Extensions/LegacyHDAPlatformDriver.kext /Volumes/EFI/Extensions/LegacyIOAHCIBlockStorage.kext /Volumes/EFI/Extensions/LegacyJMicronATA.kext /Volumes/EFI/Extensions/seatbelt.kext /Volumes/EFI/Extensions/SMBIOSEnabler.kext /Volumes/EFI/Extensions/System.kext /Volumes/EFI/mach_kernel /Volumes/EFI/mach_kernel.voodoo /Volumes/EFI/System /Volumes/EFI/System/Booter /Volumes/EFI/update.log /Volumes/EFI/update.sh # umount -f /Volumes/EFI # rm -rf /Volumes/EFI Link to comment Share on other sites More sharing options...
mac kid from jersey Posted April 24, 2009 Share Posted April 24, 2009 Is anyone else having ethernet problems after using the new script? The ethernet devices are listed in the network properties .. i just cant get an IP. Edit: looks like it might be the entire IP stack thats not working. I tried sharing connection from my mackbook (via ethernet and firewire 400). Link to comment Share on other sites More sharing options...
mangopeach Posted April 24, 2009 Share Posted April 24, 2009 Is anyone else having ethernet problems after using the new script? The ethernet devices are listed in the network properties .. i just cant get an IP. Our motherboards have a bug that causes onboard LAN to stop working if the system gets powered down repeatedly. Try shutting down and then removing the power cord and wait till all the lights turn off on the motherboard. Then plug it back in and turn on and all that... i have had the ethernet "break" while doing stuff and had assumed it was from the software. Nope, everytime it stops working, the power down thing seems to work for me. Hope that fixes your problema. Link to comment Share on other sites More sharing options...
mac kid from jersey Posted April 24, 2009 Share Posted April 24, 2009 Our motherboards have a bug that causes onboard LAN to stop working if the system gets powered down repeatedly. Try shutting down and then removing the power cord and wait till all the lights turn off on the motherboard. Then plug it back in and turn on and all that... i have had the ethernet "break" while doing stuff and had assumed it was from the software. Nope, everytime it stops working, the power down thing seems to work for me. Hope that fixes your problema. couldnt hurt ... i've just never had that problem before. Link to comment Share on other sites More sharing options...
digital_dreamer Posted April 24, 2009 Author Share Posted April 24, 2009 Is anyone else having ethernet problems after using the new script? The ethernet devices are listed in the network properties .. i just cant get an IP. Edit: looks like it might be the entire IP stack thats not working. I tried sharing connection from my mackbook (via ethernet and firewire 400). Not too unusual on the UD5, unfortunately. A couple days ago, I just lost my net connection after boot. Couldn't connect to the router and wouldn't grab an IP. When in the BIOS, I noticed that the SMARTLAN routine (cable test) wouldn't respond - nothing would show up. So, do what I did - clear the CMOS - and you're back in business. regards, MAJ EDIT: Or, do what mangopeach suggests. Link to comment Share on other sites More sharing options...
mac kid from jersey Posted April 24, 2009 Share Posted April 24, 2009 Yeah, you guys were right. I could kiss you. Link to comment Share on other sites More sharing options...
digital_dreamer Posted April 24, 2009 Author Share Posted April 24, 2009 hi everybody, i got all my hardware now having installation problems here is the log. can someone help me with this? the mobo is DFI Lanparty Jr X58 T3H6. I'm stumped tried everything i knew. # EFI Partition Boot Install Log # diskutil eraseVolume "HFS+" "EFI" /dev/disk5s1 Started erase on disk disk5s1 Erasing Mounting disk Could not mount disk5s1 with name after erase Finished erase on disk disk5s1 # cd "/Users/edvardlee/Desktop/Digital Dreamer Hackintosh/EFI Boot Installer v3/Bootloaders" # ./fdisk -f boot0 -u -y /dev/rdisk5 # dd if=boot1h of=/dev/rdisk5s1 2+0 records in 2+0 records out 1024 bytes transferred in 0.001251 secs (818557 bytes/sec) # cd "/Users/edvardlee/Desktop/Digital Dreamer Hackintosh/EFI Boot Installer v3" # mkdir /Volumes/EFI # mount_hfs /dev/disk5s1 /Volumes/EFI # ./fdisk -e /dev/rdisk5 fdisk: could not open MBR file /usr/standalone/i386/boot0: No such file or directory Enter 'help' for information fdisk: 1> Disk: /dev/rdisk5 geometry: -5415437/4/63 [-1364690128 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 - -1364690129] GPT 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> Device could not be accessed exclusively. A reboot will be needed for changes to take effect. OK? [n] Writing MBR at offset 0. fdisk: 1> # cp "/Users/edvardlee/Desktop/Digital Dreamer Hackintosh/EFI Boot Installer v3/Bootloaders/boot-turbo-munky.bin" /Volumes/EFI/boot # cp "/Users/edvardlee/Desktop/Digital Dreamer Hackintosh/EFI Boot Installer v3/update.sh" /Volumes/EFI/ # mkdir -p /Volumes/EFI/System/Booter # mkdir -p /Volumes/EFI/Extensions # mkdir -p /Volumes/EFI/.fseventsd # touch /Volumes/EFI/.fseventsd/no_log # mkdir -p /Volumes/EFI/Extensions # cp -r "/Users/edvardlee/Desktop/Digital Dreamer Hackintosh/EFI Boot Installer v3/Extensions" /Volumes/EFI/ # cp -r "/Users/edvardlee/Desktop/Digital Dreamer Hackintosh/EFI Boot Installer v3/Kernels/" /Volumes/EFI # cp -r "/Users/edvardlee/Desktop/Digital Dreamer Hackintosh/EFI Boot Installer v3/com.apple.boot.plist" /Volumes/EFI/ # cp "/Users/edvardlee/Desktop/Digital Dreamer Hackintosh/EFI Boot Installer v3/DSDT_Patcher/dsdt.aml" /Volumes/EFI/ # cd /Volumes/EFI # chmod +x update.sh # ./update.sh Updating EFI boot cache mv: rename /Volumes/EFI/System/Booter/Extensions.mkext to /Volumes/EFI/System/Booter/Extensions.mkext.previous: No such file or directory done. # rm -r "/Users/edvardlee/Desktop/Digital Dreamer Hackintosh/EFI Boot Installer v3/EFI_Backup/" # cp -r /Volumes/EFI/ "/Users/edvardlee/Desktop/Digital Dreamer Hackintosh/EFI Boot Installer v3/EFI_Backup/" -----com.apple.boot.plist----- <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Kernel</key> <string>bt(0,0)/mach_kernel.voodoo</string> <key>Kernel Flags</key> <string>busratio=20 boot-uuid=30DD950D-EBCA-3B03-821E-4DFD02E09F27</string> </dict> </plist> -----EFI Partition File List----- /Volumes/EFI /Volumes/EFI/.DS_Store /Volumes/EFI/.fseventsd /Volumes/EFI/.fseventsd/fseventsd-uuid /Volumes/EFI/.fseventsd/no_log /Volumes/EFI/boot /Volumes/EFI/com.apple.boot.plist /Volumes/EFI/dsdt.aml /Volumes/EFI/Extensions /Volumes/EFI/Extensions/.DS_Store /Volumes/EFI/Extensions/AppleSMBIOS.kext /Volumes/EFI/Extensions/dsmos.kext /Volumes/EFI/Extensions/HDAEnabler.kext /Volumes/EFI/Extensions/IONetworkingFamily.kext /Volumes/EFI/Extensions/LegacyAppleAHCIPort.kext /Volumes/EFI/Extensions/LegacyAppleIntelPIIXATA.kext /Volumes/EFI/Extensions/LegacyHDAController.kext /Volumes/EFI/Extensions/LegacyHDAPlatformDriver.kext /Volumes/EFI/Extensions/LegacyIOAHCIBlockStorage.kext /Volumes/EFI/Extensions/LegacyJMicronATA.kext /Volumes/EFI/Extensions/seatbelt.kext /Volumes/EFI/Extensions/SMBIOSEnabler.kext /Volumes/EFI/Extensions/System.kext /Volumes/EFI/mach_kernel /Volumes/EFI/mach_kernel.voodoo /Volumes/EFI/System /Volumes/EFI/System/Booter /Volumes/EFI/update.log /Volumes/EFI/update.sh # umount -f /Volumes/EFI # rm -rf /Volumes/EFI Nothing looks amiss in the log at first glance. Some questions: Are you able to get into the bootloader? Can you type -v at the prompt and see verbiage or on-screen log? Make sure you DON'T use the "Update" feature in wolfienuke's script. That will 'nuke' your .plists and cause boot failure. The only quick way around that is to re-download the script and start fresh. Let us know how it goes. regards, MAJ Link to comment Share on other sites More sharing options...
phabmp Posted April 24, 2009 Share Posted April 24, 2009 I decided to try the standard retail install again, since it was the one I got the farthest with. I got stuck at the same spot, but I took a couple photos this time: Verbose boot log This is about the point that the boot log sits at for while, with the SMC errors. The whole process takes about three minutes before it goes to the next screen. Gray screen This screen is where the process comes to a halt. It never actually locks up, per se, as I'm still able to move the cursor, but it won't load anything beyond this point. I don't think it's a bootloader issue, since Chameleon appears to work flawlessly... So I guess it has to be an issue with something in the kexts, maybe, or a video card issue. I haven't heard anything about the 9800GTX+ being particularly incompatible with OS X, but could that be what's going on here? I guess I'll quickly swap the video card and see if that makes a difference. I also had done the whole install from within an existing OS X install on a genuine iMac. Should I be doing the install from another OS X installation on the same computer? I've started trying to toy around with different distros to see if I can get one installed on a separate HD. So far iDeneb and Kalyway have both panicked at boot (although I just kind of threw the extensions provided in this thread onto the kalyway disc). Oh yeah, and single user mode works. Is there anything I could get at in that mode that would help? EDIT: Just tried switching to an 8600 GTS, getting the same behavior. Link to comment Share on other sites More sharing options...
mangopeach Posted April 24, 2009 Share Posted April 24, 2009 well with iPC 10.5.6 I got my evga 9800gtx+ working 100% (as far as i know) still working on the new run patcher.. with 9.6.3 Dreamer, Everything about run_patcher works great except when i want to add an efi graphics string.. the script always hangs after i paste in my string and press enter. I'm confused about the boot.plist in your root folder because the markup is all funny looking compared to standard xml. I was able to successfully install the new kernel using your cookbook from page 1 but cant figure out how to get my graphics string going. -edit- basically the system boots into 1024x768 ddr2 667.. i tried editing the boot.plist in the extras folder and reinstall the bootloader but that didnt work. What boot.plist does the system actually use and where does it live and can i edit it from the retail install disk or do I have to boot into the distro hard drive and run you script? sorry for all the questions but i'm a little slow with this stuff. Link to comment Share on other sites More sharing options...
dorenthe7 Posted April 24, 2009 Share Posted April 24, 2009 After I installed OsX with the new Chameleon ... It takes a while(Apple screen with the white circle) to get in MacOSX but just to the grey background with the Mouse Pointer in it ?! What could it be , what could I change to get in OsX Kernel problems ? Link to comment Share on other sites More sharing options...
Crash4419 Posted April 24, 2009 Share Posted April 24, 2009 I reformaated my hackintosh with the lastest Chameleon, kernel, and kexts but now I have a problem. My system does not shutdown completely. The Hard drives shutoff and the screen however the fans keep spinning. WTF? Link to comment Share on other sites More sharing options...
Recommended Posts