raymondh Posted May 2, 2011 Share Posted May 2, 2011 It was locked up again this morning. Monitors wouldn't come on and I couldn't ssh in. I hit the reset button at about 6:29am. I have unplugged the USB time machine drive and will leave it that way. Here's a bit from the console: 5/2/11 4:51:35 AM SMARTReporter[207] Drive: 'WDC WD1001FALS-00J7B1 (SnowLeo, Untitled 2 | WD-WMATV6281413 | disk3)' Status: SMARTOK (S.M.A.R.T. condition not exceeded, drive OK) 5/2/11 4:51:35 AM SMARTReporter[207] Drive: 'ST31500341AS ( | 9VS2BT5S | disk2)' Status: SMARTOK (S.M.A.R.T. condition not exceeded, drive OK) 5/2/11 4:51:35 AM SMARTReporter[207] Drive: 'ST31500341AS ( | 9VS2BV0M | disk4)' Status: SMARTOK (S.M.A.R.T. condition not exceeded, drive OK) 5/2/11 4:51:56 AM com.apple.backupd[3215] No pre-backup thinning needed: 198.0 MB requested (including padding), 182.88 GB available 5/2/11 4:54:28 AM com.apple.backupd[3215] Copied 70153 files (1.6 MB) from volume SnowLeo. 5/2/11 4:54:29 AM com.apple.backupd[3215] Copied 70156 files (1.6 MB) from volume Lightroom_Library. 5/2/11 4:54:35 AM com.apple.backupd[3215] No pre-backup thinning needed: 196.2 MB requested (including padding), 182.88 GB available 5/2/11 4:54:44 AM com.apple.backupd[3215] Copied 736 files (60 KB) from volume SnowLeo. 5/2/11 4:54:44 AM com.apple.backupd[3215] Copied 739 files (60 KB) from volume Lightroom_Library. 5/2/11 4:54:48 AM com.apple.backupd[3215] Starting post-backup thinning 5/2/11 4:57:24 AM com.apple.backupd[3215] Deleted backup /Volumes/TimeMachine/Backups.backupdb/Ray Hendricks’s Mac Pro/2011-05-01-035447: 182.88 GB now available 5/2/11 4:57:24 AM com.apple.backupd[3215] Post-back up thinning complete: 1 expired backups removed 5/2/11 4:57:24 AM com.apple.backupd[3215] Backup completed successfully. 5/2/11 5:51:14 AM com.apple.backupd[3283] Starting standard backup 5/2/11 5:51:15 AM com.apple.backupd[3283] Backing up to: /Volumes/TimeMachine/Backups.backupdb 5/2/11 5:51:35 AM SMARTReporter[207] Drive: 'Hitachi HDS723020BLA642 (Media | MN1220F304BLHD | disk1)' Status: SMARTOK (S.M.A.R.T. condition not exceeded, drive OK) 5/2/11 5:51:35 AM SMARTReporter[207] Drive: 'WDC WD1001FALS-00J7B1 (SnowLeo, Untitled 2 | WD-WMATV6281413 | disk3)' Status: SMARTOK (S.M.A.R.T. condition not exceeded, drive OK) 5/2/11 5:51:35 AM SMARTReporter[207] Drive: 'ST31500341AS ( | 9VS2BT5S | disk2)' Status: SMARTOK (S.M.A.R.T. condition not exceeded, drive OK) 5/2/11 5:51:35 AM SMARTReporter[207] Drive: 'ST31500341AS ( | 9VS2BV0M | disk4)' Status: SMARTOK (S.M.A.R.T. condition not exceeded, drive OK) 5/2/11 5:52:22 AM com.apple.backupd[3283] No pre-backup thinning needed: 198.2 MB requested (including padding), 182.88 GB available 5/2/11 5:55:35 AM com.apple.backupd[3283] Copied 71753 files (1.7 MB) from volume SnowLeo. 5/2/11 5:55:36 AM com.apple.backupd[3283] Copied 71756 files (1.7 MB) from volume Lightroom_Library. 5/2/11 5:55:40 AM com.apple.backupd[3283] No pre-backup thinning needed: 197.2 MB requested (including padding), 182.87 GB available 5/2/11 5:55:48 AM com.apple.backupd[3283] Copied 698 files (831 KB) from volume SnowLeo. 5/2/11 5:55:48 AM com.apple.backupd[3283] Copied 701 files (831 KB) from volume Lightroom_Library. 5/2/11 5:55:51 AM com.apple.backupd[3283] Starting post-backup thinning 5/2/11 5:57:49 AM com.apple.backupd[3283] Deleted backup /Volumes/TimeMachine/Backups.backupdb/Ray Smith’s Mac Pro/2011-05-01-045437: 182.88 GB now available 5/2/11 5:57:49 AM com.apple.backupd[3283] Post-back up thinning complete: 1 expired backups removed 5/2/11 6:29:04 AM kernel npvhash=4095 5/2/11 5:57:50 AM com.apple.backupd[3283] Backup completed successfully. 5/2/11 6:29:04 AM kernel PAE enabled 5/2/11 6:29:04 AM kernel 64 bit mode enabled 5/2/11 6:29:04 AM kernel Darwin Kernel Version 10.6.0: Wed Nov 10 18:13:17 PST 2010; root:xnu-1504.9.26~3/RELEASE_I386 5/2/11 6:29:04 AM kernel vm_page_bootstrap: 3075154 free pages and 54190 wired pages 5/2/11 6:29:04 AM kernel standard timeslicing quantum is 10000 us 5/2/11 6:29:04 AM kernel mig_table_max_displ = 73 5/2/11 6:29:04 AM kernel Warning - kext com.psystar.driver.OpenHaltRestart has immediate dependencies on both com.apple.kernel* and com.apple.kpi.* components; use only one style. 5/2/11 6:29:04 AM kernel [sleepEnabler] Exiting, invalid PM version 5/2/11 6:29:04 AM kernel Kext sk.triaxis.kext.SleepEnabler start failed (result 0x5). 5/2/11 6:29:04 AM kernel Kext sk.triaxis.kext.SleepEnabler failed to load (0xdc008017). 5/2/11 6:29:04 AM kernel Failed to load kext sk.triaxis.kext.SleepEnabler (error 0xdc008017). 5/2/11 6:29:04 AM kernel NullCPUPowerManagement::init: properties=0x11ba6b00 5/2/11 6:29:04 AM kernel Couldn't alloc class "SleepEnabler" 5/2/11 6:29:04 AM kernel NullCPUPowerManagement::start 5/2/11 6:29:04 AM kernel AppleACPICPU: ProcessorId=0 LocalApicId=0 Enabled I'm no expert but it looks like Time Machine backup prunning activities locked the machine up around 5:57. You can see a console entry at 5:57 then at 6:29 a message that must be from my reboot then it through another time machine message that is stamped 5:57. What do you think? Link to comment Share on other sites More sharing options...
tsunoo Posted May 2, 2011 Share Posted May 2, 2011 What do you think? sorry dude but I think it is not related to this topic wich is "Snow Leopard (10.6.7) and Lion DP2 Install on Gigabyte Mobos" Link to comment Share on other sites More sharing options...
fruitbat04 Posted May 2, 2011 Share Posted May 2, 2011 Look into /System/Library/CoreServices on your installer disk and you'll find the PlatformSupport.plist that should be deleted.The Boot Disk routine in the script should be deleting this plist, if found, so I wonder how this was installed or ignored. MAJ Thanks but the file was not there. It did exist in com.apple.recoveryboot (in the root of the thumb drive) but removing this did not help. Any other ideas? Edit : Not to worry, It works using the patched OSinstall package. Link to comment Share on other sites More sharing options...
digital_dreamer Posted May 2, 2011 Author Share Posted May 2, 2011 5/2/11 4:54:28 AM com.apple.backupd[3215] Copied 70153 files (1.6 MB) from volume SnowLeo.5/2/11 4:54:29 AM com.apple.backupd[3215] Copied 70156 files (1.6 MB) from volume Lightroom_Library. 5/2/11 5:55:35 AM com.apple.backupd[3283] Copied 71753 files (1.7 MB) from volume SnowLeo. 5/2/11 5:55:36 AM com.apple.backupd[3283] Copied 71756 files (1.7 MB) from volume Lightroom_Library. Three things I see suspicious about the above TM log: 1. I don't how the number of files copied compared to their total size is even possible. That's an average of 22 bytes per file, well below the typical file allocation size of a large hard drive (typically 4K and up). 2. The number of files copied for volume Lightroom_Library is always 3 files more than SnowLeo. 3. The number of files copied in the second backup is exactly 1,000 file more than the previous backup. The only thing I can imagine is that metadata was added to all those files. Or, the directory is really messed up on your boot drive and Time Machine volume. This is vitally crucial when you consider that the integrity of your TM backups depends on the integrity of the directories being backed up. MAJ Edit : Not to worry, It works using the patched OSinstall package. That's certainly an option. Although I'm confused, as all the patched installer does is ignore the platform check. EDIT: Which Lion installer or build were you using? Did you change any of the smbios.plist strings in the Kexts_10.7/Boot_Disk/Extra? They may have added more checks in the installer for later versions. The original installer has the following uncompleted checks that always return true: function checkSupportedMachine(machineType) { return true; } function checkSupportedBootRom(machineType) { return true; } Following that is the "isSupportedPlatform" function that checks for a valid board ID. MAJ Link to comment Share on other sites More sharing options...
fruitbat04 Posted May 2, 2011 Share Posted May 2, 2011 That's certainly an option. Although I'm confused, as all the patched installer does is ignore the platform check. EDIT: Which Lion installer or build were you using? Did you change any of the smbios.plist strings in the Kexts_10.7/Boot_Disk/Extra? They may have added more checks in the installer for later versions. The original installer has the following uncompleted checks that always return true: function checkSupportedMachine(machineType) { return true; } function checkSupportedBootRom(machineType) { return true; } Following that is the "isSupportedPlatform" function that checks for a valid board ID. MAJ I didn't change my smbios.plist file (intentionally anyway). It certainly has a completely different modified date from the SL one anyhow. The build number for mine is 11A419. Works a treat anyhow. The only minor niggle is for some reason the scroll wheel on my mouse seems inverted! I have a feeling it doesn't shut down properly either but not really tested. Network, Bluetooth and my Mbox 2 are all fine. Edit : Nope shut down works! Must just have been a one off. Link to comment Share on other sites More sharing options...
digital_dreamer Posted May 3, 2011 Author Share Posted May 3, 2011 Works a treat anyhow. The only minor niggle is for some reason the scroll wheel on my mouse seems inverted! Check off the first option (at top) under System Preferences/Mouse! MAJ Link to comment Share on other sites More sharing options...
fruitbat04 Posted May 3, 2011 Share Posted May 3, 2011 Check off the first option (at top) under System Preferences/Mouse! MAJ Thanks! Strange default option... Anyway my Shutdown works but restart doesn't. Get's stuck on a black screen with fans still going but HDD powered down. I've not really played with my DSDT much though so will have a look at d00d's guide. Link to comment Share on other sites More sharing options...
DariosF Posted May 4, 2011 Share Posted May 4, 2011 I've installed lion on my drive following this guide. But when i try to boot into lion partition, my system reboot. How can i solve? Link to comment Share on other sites More sharing options...
joeblough Posted May 4, 2011 Share Posted May 4, 2011 hi - this is a 10.6.7 question. i originally set up my ex58-ud4p using D_D's script for 10.5, and then migrated to 10.6.3. along the way i did d00d's dsdt patches, but i never removed SleepEnabler.kext. i upgraded to 10.6.4 and ran that way for a very long time, until recently i decided to upgrade to 10.6.7. had to upgrade SleepEnabler.kext twice, and while debugging sleep problems i removed SleepEnabler to find that native sleep definitely does not work. that's kind of confusing to me. anyway, sleep does work for me with SleepEnabler.kext, but maybe 1 in 10 times the machine seems to die while going to sleep. the sleep seems to take the normal amount of time, but then when trying to wake the machine with the keyboard nothing happens, and pressing the power button causes the machine to cold boot. i'm not sure i could actually debug this without a serial console because i don't think the realtek drivers support remote kernel debug by ethernet. anyway, right now i have the following kexts in /E/E EvOreboot.kext FakeSMC.kext IOAHCIBlockStorageInjector.kext LegacyAppleRTC.kext NullCPUPowerManagement.kext PlatformUUID.kext SleepEnabler.kext and i am using Chameleon 2.0 RC4, but somehow i ended up on AsereBLN's r111 fork, which is not D_D's. can't remember why i did that. at some point i switched to lnx2mac's realtek driver (in /S/L/E) after a KP while initiating a file download. i thought maybe my sleep problems were caused by the chucko driver but my problems persisted even after changing network kexts. is there any reason to upgrade Chameleon for 10.6.7? i am on bios F13. i don't really want to upgrade the bios because i think i'll have to re-do all the DSDT edits again if i do that... anyone else with flaky sleep on a UD4P? thanks Link to comment Share on other sites More sharing options...
joeblough Posted May 5, 2011 Share Posted May 5, 2011 hi - this is a 10.6.7 question.... had to upgrade SleepEnabler.kext twice, and while debugging sleep problems i removed SleepEnabler to find that native sleep definitely does not work. that's kind of confusing to me. ... anyway, right now i have the following kexts in /E/E NullCPUPowerManagement.kext SleepEnabler.kext anyone else with flaky sleep on a UD4P? thanks okay, now i understand what's going on. If you load NullCPUPowerManagment.kext, then you need SleepEnabler.kext to enable sleep. SleepEnabler replaces the part of AppleIntelCPUPowerManagement that's needed to enable sleep. if you remove just sleepenabler, but leave NullCPUPowerManagement.kext, the system will boot but crash when you try to put it to sleep. if you remove just NullCPUPowerManagement.kext then both SleepEnabler.kext and AppleIntelCPUPowermanagement both try to install the hooks for the sleep function, and you get a kernel panic on boot with "i386_pmGetDeadline: Nullpointer ..." etc. but of course if you remove both of those kexts and you have d00d's native sleep DSDT hacks (and probably you need the SSDT hacks as well) then AppleIntelCPUPowerManagment.kext loads properly at boot time and registers the callback for sleep and... you get native sleep. we'll see if the machine is any more stable like this. Link to comment Share on other sites More sharing options...
student_al Posted May 6, 2011 Share Posted May 6, 2011 Anyone happen to have any experience with this? Never got a response. Hey Y'all! I would like to bump this. It is almost summer time, that means almost only 1 thing right now for me! Hackintosh upgrades!!! I was curious about the SSD/RAID situation with the SATA III drives - is it currently possible to set up a SSD SATA III RAID 0 array as the MBR on the GA-X58? -Al Link to comment Share on other sites More sharing options...
raymondh Posted May 11, 2011 Share Posted May 11, 2011 i just downloaded the latest script and ran it on my 10.6.6 install that seems to lock up overnight (set to not sleep) and it show the attached changes will be made. im assuming it is replacing out of date kexts? should i just accept this and let it do it's thing? Also, is combo update the way to go? i really hope there is something inhere that fixes the overnight lockups. If it matters i have pmversion=0 in com.apple.boot.plist. Link to comment Share on other sites More sharing options...
digital_dreamer Posted May 11, 2011 Author Share Posted May 11, 2011 i just downloaded the latest script and ran it on my 10.6.6 install that seems to lock up overnight (set to not sleep) and it show the attached changes will be made. im assuming it is replacing out of date kexts? should i just accept this and let it do it's thing? Also, is combo update the way to go? i really hope there is something inhere that fixes the overnight lockups. If it matters i have pmversion=0 in com.apple.boot.plist. Yep, they are all being replaced/updated. However, note that not all kexts in the default install are necessarily the ones you may need or want, just the ones I'm using or are recommended for use with the UD5 and my setup. Kexts updated in that screenshot are: fakesmc.kext v2 to FakeSMC.kext v3.1.0 RealtekR1000SL.kext v2.0.0d1 to IONetworkingFamily.kext v1.11 (includes RealtekR1000SL.kext in PlugIns) Kexts you may not need: PlatformUUID.kext (Chameleon RC5 bootloader takes care of this) OpenHaltRestart.kext (Bootloader should take care of this) JMicronATA.kext (needed only if you use the onboard IDE/ATA port) AppleIntelPIIXATA.kext (not needed as our ICH10 is recognized natively) Others: I see you had a LegacyATI4800Controller.kext installed, so presume you have a 48XX series GPU. You may wish to install it in place of the ATY_Init.kext. Your choice. JMicron36xeSATA.kext is for eSATA drives on the JMicron ports (white). There is also (in repository) a JMicron36xSATA.kext, which is the same, except for internal drives. The only difference between the two is that one will show the drives as external and the other will show drives as internal. Hope that helps. MAJ Link to comment Share on other sites More sharing options...
raymondh Posted May 12, 2011 Share Posted May 12, 2011 Yep, they are all being replaced/updated.However, note that not all kexts in the default install are necessarily the ones you may need or want, just the ones I'm using or are recommended for use with the UD5 and my setup. Kexts updated in that screenshot are: fakesmc.kext v2 to FakeSMC.kext v3.1.0 RealtekR1000SL.kext v2.0.0d1 to IONetworkingFamily.kext v1.11 (includes RealtekR1000SL.kext in PlugIns) Kexts you may not need: PlatformUUID.kext (Chameleon RC5 bootloader takes care of this) OpenHaltRestart.kext (Bootloader should take care of this) JMicronATA.kext (needed only if you use the onboard IDE/ATA port) AppleIntelPIIXATA.kext (not needed as our ICH10 is recognized natively) Others: I see you had a LegacyATI4800Controller.kext installed, so presume you have a 48XX series GPU. You may wish to install it in place of the ATY_Init.kext. Your choice. JMicron36xeSATA.kext is for eSATA drives on the JMicron ports (white). There is also (in repository) a JMicron36xSATA.kext, which is the same, except for internal drives. The only difference between the two is that one will show the drives as external and the other will show drives as internal. Hope that helps. MAJ Thanks, that does help. I actually have a eVGA e-GeForce 9800GTX+ so I'm not sure why the ATI kext is in there, I'll remove it. I don't use the JMicron SATA connectors at all so I'll remove that as well. Link to comment Share on other sites More sharing options...
raymondh Posted May 12, 2011 Share Posted May 12, 2011 Yep, they are all being replaced/updated.However, note that not all kexts in the default install are necessarily the ones you may need or want, just the ones I'm using or are recommended for use with the UD5 and my setup. Kexts updated in that screenshot are: fakesmc.kext v2 to FakeSMC.kext v3.1.0 RealtekR1000SL.kext v2.0.0d1 to IONetworkingFamily.kext v1.11 (includes RealtekR1000SL.kext in PlugIns) Kexts you may not need: PlatformUUID.kext (Chameleon RC5 bootloader takes care of this) OpenHaltRestart.kext (Bootloader should take care of this) JMicronATA.kext (needed only if you use the onboard IDE/ATA port) AppleIntelPIIXATA.kext (not needed as our ICH10 is recognized natively) Others: I see you had a LegacyATI4800Controller.kext installed, so presume you have a 48XX series GPU. You may wish to install it in place of the ATY_Init.kext. Your choice. JMicron36xeSATA.kext is for eSATA drives on the JMicron ports (white). There is also (in repository) a JMicron36xSATA.kext, which is the same, except for internal drives. The only difference between the two is that one will show the drives as external and the other will show drives as internal. Hope that helps. MAJ I let it do it's thing but then it no longer would power down. It would shut everything down and the monitors would go black but the fans all continued to run. I had to add openhaltrestart back in so it would shutdown properly. I have everything else installed as the script wanted it and removed my pmversion=0 but it still wouldn't shutdown without openhaltrestart. Link to comment Share on other sites More sharing options...
digital_dreamer Posted May 12, 2011 Author Share Posted May 12, 2011 raymondh, RE: openhaltrestart.kext Okay, so you need it. I haven't needed it or any other restart kext. What bootloader are you using? I'm on Cham RC5 r760, the same one I'm using for Lion. MAJ Link to comment Share on other sites More sharing options...
Sidewinder33 Posted May 13, 2011 Share Posted May 13, 2011 Hey DD, I know this is not really the place, but I'm running 10.6.7 and I am having to switch from wired ethernet to wifi. I'm wondering if you had any knowledge on which usb or ethernet wifi adaptors worked with our boards. I'm not wanting to do a card, but I would like to get something with N capability. Thanks for the help. Link to comment Share on other sites More sharing options...
Windows04 Posted May 13, 2011 Share Posted May 13, 2011 Hey, Windows04,I reckon you're talking about installing it while in Lion. I haven't tried that. yet. I'll see what's going on. Sounds like a VoodooHDA issue. The kext is rather unusual, as it doesn't have a mkext filter flag, so maybe the kextcache command is confused in Lion. Up to this point, I've always installed from SL (no kernelcache is really built in SL). If this is really a issue, I may have to have the script update the kernel cache without including the VoodooHDA.kext, but keep it installed in S/L/E and just expect the OS to do its job in loading it for the kernel on a reboot. MAJ Hi DD I'm sorry for my late response to your answer . Well, I do have a modified DSDT, but it seems that the standard DSDT fixes you apply to the DSDT already modify the HDEF entry (or am I totally in the wrong way here...) -> anyway I compared my DSDT to a DSDT made in your script: Although my DSDT was more modified (mostly power related), the HDEF part was exactly the same in both DSDT's... so that couldn't be the problem. I tried to install Voodoohda in S/L/E from Lion, while running your script in Snow Leopard (so installing the kext with your script while running Snow Leopard), but then I just get a kernel panic when I boot Lion (related to that kext) with both DSDT's... SO -> When I install absolutely nothing that's related to sound (so that means, the standard DSDT from your script + NO voodoohda) -> stereo sound + headphone jack on the front of my computer works, but I can't configure a surround sound like in Snow Leopard (which I achieve in Snow Leopard with my modified DSDT and a modified LegacyHDA.kext...) Also, I've encountered a second problem :s... with the latest version of your script, I can't make a combo boot cache (both in Lion and Snow Leopard), have included a pic of the error I receive while trying to update boot cache on my Test Mac drive (a fresh install of Snow Leopard I use for testing).... Hope you can find a solution . Thanks in advance . EDIT: Allright, it has been a while since I experimented with Lion. But now, in addition to the problems described above, I discovered an additional problem: I installed the latest chameleon trunk you provided (so GUI + No DF KP), but when I boot Lion, it always loads all the kexts of S/L/E (like I was using the -f option, but I'm not using, have tried it with -usecache, but also no success...). EDIT 2: So... to wrap things up: 1) Can't make a combo boot cache anymore for Snow Leopard with newest version script 2) Lion always loads all kexts (like the -f command) when it boots 3) Can't configure a surround sound setup, because only Line out, Headphone and Digital out appear as option in Sound (This comes because i'm unable to install Voodoohda). Allright, a lot of problems, but don't see this as complaining, you don't know how much I appreciate your work . Link to comment Share on other sites More sharing options...
digital_dreamer Posted May 15, 2011 Author Share Posted May 15, 2011 Hey Windows04!, 1) Can't make a combo boot cache anymore for Snow Leopard with newest version script That's a most bizarre and puzzling screenshot. I can't imagine how the letter "C" is creating that response. Are you using English or a different language? Somehow the "C" is getting converted to a ".0" Do the other letters work okay (A, B, and E). What about lower case? Here's a test script that will print on the screen your typed input at 4 different places in the parsing area, so I can see what's going on. Put the script in /~extra/Resources. Save the original by renaming or moving. Post feedback on what the script is outputting in those 4 areas. 2) Lion always loads all kexts (like the -f command) when it boots That was a issue with the first working Chameleon bootloader release for Lion. I had the same issue and many complained about it. Here is Chameleon RC 5 r800 - the latest from the trunk. There's a issue with the memory parsing for System Information (Lion) and System Profiler (Snow). Drop this in /~extra/Bootloaders/Chameleon_2.0_RC5/i386 and replace the existing one. 3) Can't configure a surround sound setup, because only Line out, Headphone and Digital out appear as option in Sound (This comes because i'm unable to install Voodoohda). This sounds like a problem. My DSDT script doesn't make any changes to the HDEF parts. It doesn't even change the AZAL name to HDEF. If we are going to use VoodooHDA.kext, let's start by disabling AppleHDA.kext in S/L/E. In Terminal: cd /System/Library/Extensions sudo mv AppleHDA.kext AppleHDA.kext.original Then, reboot and install VoodooHDA.kext See if that will get you going. best regards, MAJ Link to comment Share on other sites More sharing options...
Windows04 Posted May 15, 2011 Share Posted May 15, 2011 Hey Windows04!, 1) Can't make a combo boot cache anymore for Snow Leopard with newest version script That's a most bizarre and puzzling screenshot. I can't imagine how the letter "C" is creating that response. Are you using English or a different language? Somehow the "C" is getting converted to a ".0" Do the other letters work okay (A, B, and E). What about lower case? Here's a test script that will print on the screen your typed input at 4 different places in the parsing area, so I can see what's going on. Put the script in /~extra/Resources. Save the original by renaming or moving. Post feedback on what the script is outputting in those 4 areas. 2) Lion always loads all kexts (like the -f command) when it boots That was a issue with the first working Chameleon bootloader release for Lion. I had the same issue and many complained about it. Here is Chameleon RC 5 r800 - the latest from the trunk. There's a issue with the memory parsing for System Information (Lion) and System Profiler (Snow). Drop this in /~extra/Bootloaders/Chameleon_2.0_RC5/i386 and replace the existing one. 3) Can't configure a surround sound setup, because only Line out, Headphone and Digital out appear as option in Sound (This comes because i'm unable to install Voodoohda). This sounds like a problem. My DSDT script doesn't make any changes to the HDEF parts. It doesn't even change the AZAL name to HDEF. If we are going to use VoodooHDA.kext, let's start by disabling AppleHDA.kext in S/L/E. In Terminal: cd /System/Library/Extensions sudo mv AppleHDA.kext AppleHDA.kext.original Then, reboot and install VoodooHDA.kext See if that will get you going. best regards, MAJ Well, making a little bit of progress, but not in the areas I hoped... 1) Combo cache Well... apparently... if I use the lowercase letter "c" instead of the uppercase letter "C", it works XD. So, the newest version of your script treats c and C differently (which is weird, because I tried it with version 5.1 of your script, and with that version, I could use both c and C and it would create the boot cache. So yeah, sorry for wasting your time on that XD. 2) The kernel cache issue I installed the chameleon boot file you provided (r800), but the issue is still there. Each time I boot Lion, it loads all the kexts, just like the -f option. I thought there could be a problem with the kernel cache (maybe Lion isn't creating one automatically), so I tried booting in -f (forcing the creation of a cache) and then reboot with -usecache, but that hasn't helped... So problem not solved here... 3) Sound Problem I renamed AppleHDA and installed VoodooHDA and it works (no more KP!) but voodoohda doesn't really help me out because I still get the same 3 audio options (Line out, Headphones, SPDIF out) only now, I see which ports they are (but that's probably because of voodoohda telling me that)... So I don't get a difference in sound if I use voodoohda or my DSDT. Have asked dood (my DSDT is based on his topic) for more help on the sound problem 4) The DSDT problem I recreated a DSDT using your script and your script DOES change my audio information from AZAL to HDEF: Device (HDEF) { Name (_ADR, 0x001B0000) Method (_PRW, 0, NotSerialized) { Return (Package (0x02) { 0x0D, 0x06 }) } Method (_DSM, 4, NotSerialized) { Store (Package (0x04) { "layout-id", Unicode ("B"), "PinConfigurations", Buffer (Zero) {} }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } BUT, can it be that the creation of the DSDT by the script is influenced by the fact the system is booted using my modified DSDT? Can it be that, because my modified DSDT injects the HDEF code into the system, your scripts picks up that code and inserts it into his DSDT? I thinks it does, because apparently the DSDT that the script makes also includes code that makes it possible to use AppleIntelCPUPowerManagement.kext... I don't have much time now, but will also try to revert my DSDT to original and see if that helps, so an edit to this post is coming later... I hope this info helps a bit, although I haven't made much progress yet (except for the c thing XD) Link to comment Share on other sites More sharing options...
everdone Posted May 15, 2011 Share Posted May 15, 2011 For r800 (and several others) the "-usecache" command has been changed. You now use (in 'key', 'string' format in com.apple.boot.plist) "UseKernelCache" = "Yes" to stop loading all kexts at each boot. Link to comment Share on other sites More sharing options...
digital_dreamer Posted May 15, 2011 Author Share Posted May 15, 2011 1) Combo cacheWell... apparently... if I use the lowercase letter "c" instead of the uppercase letter "C", it works XD. So, the newest version of your script treats c and C differently (which is weird, because I tried it with version 5.1 of your script, and with that version, I could use both c and C and it would create the boot cache. So yeah, sorry for wasting your time on that XD. I'm going to still need some feedback if possible, as I cannot create this issue and my newest unreleased script is unchanged in this area. 2) The kernel cache issueI installed the chameleon boot file you provided (r800), but the issue is still there. Each time I boot Lion, it loads all the kexts, just like the -f option. I thought there could be a problem with the kernel cache (maybe Lion isn't creating one automatically), so I tried booting in -f (forcing the creation of a cache) and then reboot with -usecache, but that hasn't helped... So problem not solved here... Sorry I didn't mention this to you sooner, but just as everdone posted, create a new key and string with "UseKernelCache" and "Yes" without quotes. The older -usecache kernel flag no longer functions as it used to. 4) The DSDT problem<snip> BUT, can it be that the creation of the DSDT by the script is influenced by the fact the system is booted using my modified DSDT? Can it be that, because my modified DSDT injects the HDEF code into the system, your scripts picks up that code and inserts it into his DSDT? I thinks it does, because apparently the DSDT that the script makes also includes code that makes it possible to use AppleIntelCPUPowerManagement.kext... I think you're getting it, because I know my script doesn't change the sound label. Anytime you run a DSDT patcher (mine or others), it's going to get the existing DSDT info that is loaded. If it was patched before, then that's what it'll get. This is why once you have patched the DSDT and booted from it, it no longer needs the same patches. DSDT patchers cannot load a virgin, unmodified DSDT file if it has been patched before. If you want a clean patch, it's good practice to boot without a DSDT file, then run the patcher. That way the patcher is able to grab the virgin ioreg info just as it was created from the BIOS - unmodified. Naturally, DSDT patchers are coded to look for specific strings or patterns to change. If the DSDT has already been patched, say manually with a sloppy edit (extra spaces/tabs/carriage returns, misspelled labels, etc.), it may create undesirable results, as the patcher may not be able to consider every possible variation in editing when doing its search and replace. I recommend MaLd0n's DSDT Auto-Patcher for patches beyond what my script will do. But, to use it, either boot without a DSDT patch or create a unmodified one with my script by turning off all fixes. For r800 (and several others) the "-usecache" command has been changed. You now use (in 'key', 'string' format in com.apple.boot.plist) "UseKernelCache" = "Yes" to stop loading all kexts at each boot. Thanks for the reminder! MAJ Link to comment Share on other sites More sharing options...
Windows04 Posted May 15, 2011 Share Posted May 15, 2011 Allright, back with some updates on my problems . 1) The combo cache Allright, sorry for not telling you earlier, but I have a RAID system for my Snow Leopard drives. This RAID is made using the built-in Apple Disk Utility in Snow Leopard, and it is Raid-0 (2 1TB drives combined into 1 2TB drive). This of course changes a lot, so i'm sorry for not mentioning it earlier. Well, think I have another problem here... So the c and C issue persists (if I type the uppercase letter C, then the script fails and logs out), but now, when I type the lower case letter c, the scripts first encounters some errors with the grep command and then it waits endlessly for the system to create a boot cache (which apparently it doesn't do anymore for some bizarre reason)... -> See screenshot below! With your 5.1 script, I don't have any problem creating a boot cache (although I first have to manually delete Extensions.mkext from both BOOT_OSX drives, otherwise your script fails to make a cache because it hasn't enough space). BUT in version 5.1 of the script, you used the letter "S" to make a Super Combo Boot Cache. So this letter "S" has been changed to the letter "C" in later versions of your script, don't know if it makes any difference... PS: My language is set to English, so normally I shouldn't have any problem with that... 2) Lion's Kernelcache Yes Thank you Everdone and Digital_dreamer for pointing out this UseKernelCache option, now my Lion boots perfectly, no more waiting for every kext to load . Problem Solved 3) The Audio/DSDT thing Well, don't have much time anymore today for trying your idea, but will do it tomorrow. I always have a spare test drive I use for hackintosh testing, so will use that to boot without any DSDT and create a virgin one. After I have this "virgin" DSDT, will put it on the lion drive, disable AppleHDA.kext and install VoodooHDA.kext, hope it works... Have also asked for a new LegacyHDA.kext (which is a kext I use in conjunction with the DSDT to have all of my audio out ports recognized on my ga-ex58-ud5) which is lion compatible, but haven't had any response yet in dood's thread. But I do hope that eventually, I can get my sound working using my DSDT and LegacyHDA.kext, don't like to mess around with the stock Apple kexts (like AppleHDA...) Oh and almost forgot to mention: Thanks for your help, you and everdone are great people . Link to comment Share on other sites More sharing options...
colddiver Posted May 17, 2011 Share Posted May 17, 2011 Hello all, Here is how I got Lion DP2 up and running on my hackintosh. Please note that I am running with dood’s DSDT method. The following guide assumes you have a free hard drive, setup with a few test partition (I use 3 partitions called mLion, mSnow and mLion Installer - this allows me to test both Snow Leopard and Lion from the same HD). 1. Building a custom installer on a partition Mount the Lion Install DVD and open the BaseSystem.dmg (open /Volumes/Mac\ OS\ X\ Install\ ESD/BaseSystem.dmg ) Use Carbon Copy Cloner to clone the BaseSystem disk image to a spare partition (in my case, I cloned to mLion Installer) In the newly cloned install partition, you will find an alias called Packages in /System/Installation. This alias needs to be replaced by the original files located in /Volumes/Mac\ OS\ X\ Install\ ESD/Packages/ (i.e. replace the alias by the Package folder). 2. Install bootloader & kext on your Lion install partition At this point, we will use the latest version of DD’s script to install the necessary files but first, you must manually add the latest Chameleon bootloader as described in DD’s post #3395 (reproduced here for your convenience): Here is Chameleon RC 5 r800 - the latest from the trunk. There's a issue with the memory parsing for System Information (Lion) and System Profiler (Snow). Drop this in /~extra/Bootloaders/Chameleon_2.0_RC5/i386 and replace the existing one. Once this is done, fire up DD’s script in run step 2 (Install bootloader - select Chameleon RC5 r800) and step 5 (Run next/kernel installer). Install whatever kext you normally use (in my case, because I’m using Dood’s DSDT method, all I need is FakeSMC). Please note that you will need to install your next in S/L/E and not in Extra. Once completed, exit the script. You can now copy your Snow Leopard/Extra com.apple.boot.plist, dsdt.aml and smbios.plist over to the Lion Installer/Extra folder. This will allow you to keep your exiting setup pretty much as is. Of note: the Lion installer will check (among other things) your SMproductname and SMserial and will require a matching pair. If both keys don’t match, it will refuse to install. You have 2 choices here, you can either modify your smbios.plist and add the required keys or you can hack the Lion installer to install anyway (I chose the later - I will figure out the pairing keys later). 3. Hack OSInstall.mpkg to remove system checks To do so, copy OSInstall.mpkg in a directory and uncompress it using the following command in a terminal window (make sure you cd into your directory first): xar -x -f OSInstall.mpkg Once uncompressed, rename the OSInstall.mpkg to OSInstall.mpkg.orig and move it out of the working directory but keep it just in case. Open Distribution in a text editor and change the following methods so that they all return true all the time: function checkSupportedMachine(machineType) { return true; } function checkSupportedBootRom(machineType) { return true; } function isSupportedPlatform(){ return true; } function installCheckScript(){ return true; } function volCheckScript(){ return true; } Repack the OSInstall.mpkg using: xar -c -f OSInstall.mpkg * Note: if you left the original OSInstall.mpkg in the directory, it will be added to the new hacked OSInstall.mpkg (not good) so make sure it is out of the directory before you run the above command in the terminal. Now replace the [Your Lion Install Partition]/System/Installation/Packages/OSInstall.mpkg by the one you just made. 5. Reboot and select your Lion installer partition (make sure you select the right hard drive in your BIOS as the boot drive - avoid trying to boot your Lion install partition from your main. If all goes well, you will now boot into your Lion installer partition and will be able to install wherever you want. Once the install is complete, boot back into your Snow Leopard and install the bootloader and kext on your freshly installed Lion (go back to step 2 above but install on you newly intalled Lion instead of your Lion Installer Partition). Once done, you should be able to reboot in Lion and to upgrade to the latest version using Software Updates. On my setup, almost everything seems to work (reboot, audio, graphics, network…). I did get a CMOS reset when trying to sleep the machine (will investigate this further later). I am also getting incorrect info in the about this Mac/More Info (wrong model since I don't have a valid serial number and incorrect memory info - amount of installed RAM is OK but it tells me that my Mac has 0 memory slots and will accept a ??? memory module). Big thanks to DD, Dood, Netkas and the Chameleon devs for making thing easy... Colddiver Link to comment Share on other sites More sharing options...
Windows04 Posted May 17, 2011 Share Posted May 17, 2011 Colddiver, are all of your audio ports working using dood's dsdt? Can you create a surround sound setup using audio midi setup from utilities? Link to comment Share on other sites More sharing options...
Recommended Posts