lateralusman Posted December 27, 2009 Share Posted December 27, 2009 I still can't get QE/CI in Snow Leo. Tried OSXTools as well... Link to comment Share on other sites More sharing options...
d00m42 Posted December 27, 2009 Author Share Posted December 27, 2009 Thanks for the reply and pardon me but the guide in your sig is....on this thread right? And as you pointed out that I need to install OS X Leopard 10.5 first b4 using the Snow Leopard version, I'm just wondering where can I get a guide to install the Leopard 10.5. Sorry for the confusion, I just don't know where to start. I was making a little joke lol... You're looking for a guide, and there's one right here! If you have any issues with it, let me know and I can guide you through it. Link to comment Share on other sites More sharing options...
gmacman Posted December 27, 2009 Share Posted December 27, 2009 The forum was bitching to me about incorrect BBCode when I tried to edit my thread, but since I don't want to completely erase everything yet (I want to wait until I am ready to post the new guide), I'll post the new pack here. It's "beta" for now, until I make sure it's absolutely perfect. I'll have an index of the pack in the new guide, but for now you can explore and see what I've included. SL Pack v5.0b is Here! http://uppit.com/v/ZZ507CIG d00m42, I have a question for you. I notice that the PlatformUUID.kext is not included in the v5 pack. Is there a reason for that (or just an oversight)? Thanks, Steve Link to comment Share on other sites More sharing options...
marinn Posted December 27, 2009 Share Posted December 27, 2009 Hi guys, Merry Christmass and happy New Year to all I have a little problem.. Runnin' SL 10.6.2 , everything OK, except the graphics card. When I was running 10.5.x Kalyway, with NVInject drivers, it worked good, but as I see, with less performance than now with EFI string. But, I use computer for music production, and I need to have 2 monitors running(Samsung 2343NW). Graphics card is Nvidia xfx 9400gt 512mb, one dvi and one vga connector. Problem goes on when I connect the second monitor (via DVI2VGA converter) , and click Detect, then I have only the black screen and must restart, disconnect the second monitor and use only this VGA-VGA. Monitors have only VGA connection, and on other operating systems that works pretty good. I'm wondering if there's a way to install driver on another way, or something else to do, to connect both monitors and make them work And then what to do with efi string in com.apple.boot.plist? And, if it's not hard, if you can explain in one-two sentences why is not good to use injections. Regards from Croatia Marin Link to comment Share on other sites More sharing options...
d00m42 Posted December 27, 2009 Author Share Posted December 27, 2009 d00m42, I have a question for you. I notice that the PlatformUUID.kext is not included in the v5 pack. Is there a reason for that (or just an oversight)? Thanks, Steve PlatformUUID.kext is not needed when using Chameleon RC4 : ) Hi guys, Merry Christmass and happy New Year to all I have a little problem.. Runnin' SL 10.6.2 , everything OK, except the graphics card. When I was running 10.5.x Kalyway, with NVInject drivers, it worked good, but as I see, with less performance than now with EFI string. But, I use computer for music production, and I need to have 2 monitors running(Samsung 2343NW). Graphics card is Nvidia xfx 9400gt 512mb, one dvi and one vga connector. Problem goes on when I connect the second monitor (via DVI2VGA converter) , and click Detect, then I have only the black screen and must restart, disconnect the second monitor and use only this VGA-VGA. Monitors have only VGA connection, and on other operating systems that works pretty good. I'm wondering if there's a way to install driver on another way, or something else to do, to connect both monitors and make them work And then what to do with efi string in com.apple.boot.plist? And, if it's not hard, if you can explain in one-two sentences why is not good to use injections. Regards from Croatia Marin Hey Marin, Honestly, it just depends what you prefer. I (and most others) want our installs to be as "Vanilla" (fewer hacked/modified kexts) as possible. com.apple.Boot.plist EFI strings allow you to use Apple's standard graphics drivers (which should work fine with a 9400 GT 512MB). If you must use a separate injector kext (or other add-on drivers) it will just be a little more work when updating (you have to manually back up and re-install graphics kexts after any updates). You might have to make modifications to the EFI string's layout if you're using two monitors on DVI/VGA rather than DVI/DVI, but I can say that I am getting full performance on two monitors with just an EFI string using a eVGA 9800 GTX 512MB. Link to comment Share on other sites More sharing options...
gmacman Posted December 28, 2009 Share Posted December 28, 2009 PlatformUUID.kext is not needed when using Chameleon RC4 : ) Thanks. Actually I just got everything up and running a few moments ago. Used the USB/2nd Drive install method. Odd thing was I couldn't for the life of me get the drive (the installer drive) to work via external USB but once I put it into the box as an internal it worked perfectly. Ethernet, sound, graphics (nVidia 9400 GT) working well. I used the PC EFI 10.1 so I guess I need to add the RC4 later, I believe that's merely replacing the boot file (I'll have to look back through the thread to be sure). The other finishing work for me will be to do Eliade's Bonjour fix. But just wanted to post another Thank You! comment for your great work on putting this guide together. Made the move to SL painless. And of course thanks to the various other contributors (many of whom I recall from the old Eliade's Leopard Guide). Cheers! Link to comment Share on other sites More sharing options...
iTravis Posted December 28, 2009 Share Posted December 28, 2009 This is the guide I followed very easy. My Leo build works 100%. Much appreciate for the help, I also found this guide: http://lifehacker.com/5360150/install-snow...acking-required It looks pretty straightforward so I'm wondering if anybody did try it? Link to comment Share on other sites More sharing options...
d00m42 Posted December 28, 2009 Author Share Posted December 28, 2009 Much appreciate for the help, I also found this guide: http://lifehacker.com/5360150/install-snow...acking-required It looks pretty straightforward so I'm wondering if anybody did try it? Not exactly sure why you are posting in a guide thread with information about other guides... Why not use my guide first and see if it works out for you? I can safely say at this point that hundreds of people have had success; what's deterring you from using this guide? Link to comment Share on other sites More sharing options...
gmacman Posted December 28, 2009 Share Posted December 28, 2009 Just wanted to get a confirmation on the correct use of RC4. I've searched back through the pages of the thread but I just want to be 100% sure I'm doing it correctly. Since I used the PC EFI 10.1 Installer in your v4 pack it installed Chameleon RC1 (I think). I'm looking to use RC4 from your v5b pack I see it is just the boot file and RC2. So my question is....do I need to reinstall RC2 over the existing RC1 on my boot drive, and then replace the RC4 "boot" file? Or can I merely replace the "boot" file from RC4 over the existing RC1 installed on the boot drive? Also I had read back several pages ago about someone who was using Parallels (which I do too) and that you must have within the BIOS "Virtualization Technology" enabled instead of disabled as per your guide. I did that (enabled it I mean) and everything seems to be just fine. You may wish to note that on your new guide, no biggie, it's up to you. Link to comment Share on other sites More sharing options...
SavvyX4 Posted December 28, 2009 Share Posted December 28, 2009 Has anyone else had problems with hard drive performance being very spotty? My system seems great most of time, but there are other times when I am only seeing a few MB a sec throughput and my system basically grinds to a halt waiting for the disk, and at that speed it takes forever to get back to a usable state. I have an EP45-UD3R w/ 8GB and a Q9550. I'm thinking that maybe I need to make a fresh DSDT for my system, but I don't want to go through this work and miss out on the latest advances that have been found to make my system even better. I've looked at the thread in the SpeedStep forum but mostly I end up more confused than when I start. Any recommendations about how to make a proper, modern DSDT for my system? Link to comment Share on other sites More sharing options...
marinn Posted December 28, 2009 Share Posted December 28, 2009 PlatformUUID.kext is not needed when using Chameleon RC4 : ) Hey Marin, Honestly, it just depends what you prefer. I (and most others) want our installs to be as "Vanilla" (fewer hacked/modified kexts) as possible. com.apple.Boot.plist EFI strings allow you to use Apple's standard graphics drivers (which should work fine with a 9400 GT 512MB). If you must use a separate injector kext (or other add-on drivers) it will just be a little more work when updating (you have to manually back up and re-install graphics kexts after any updates). You might have to make modifications to the EFI string's layout if you're using two monitors on DVI/VGA rather than DVI/DVI, but I can say that I am getting full performance on two monitors with just an EFI string using a eVGA 9800 GTX 512MB. Ok, tnx for the answer. But, can you help me on the some other way to do it? I've tried with your string, it displays that's 9800 + EFI inside, but phisycally it acts the same, now i'm back to my string. And one more question, i've seen that, when hacked on this way, my snow leo gets a lot more time to boot (on the white screen with grey apple and rounding circle) than the other hacks i've made on "bad" way Link to comment Share on other sites More sharing options...
waldo_pepperjack Posted December 29, 2009 Share Posted December 29, 2009 Awesome! My GA-EP45-UD3L - based Quad core Hackintosh is now running SL nicely. I already had a nice Leopard setup, and since Santa brought me Snowy I decided it was time to try it out... Pretty much 99% success: - followed this guide (thank to author & contributors) - followed Using DSDT on the GA-EP45-DS3L and the guide called DSDT Guide for GA-EP45-DS3L ... patience, patience, patience ... payed off... Everything works perfectly, except for a minor fidget that my nVidia 8400GS card gives... at login/startup it displays only a light blue screen... as soon as the monitor sleeps and wakes it is 100% normal. My current workaround is just to make the upper right hand corner a "hot corner" for sleep, and to move the mouse it that direction for a second or two. Link to comment Share on other sites More sharing options...
grice Posted December 29, 2009 Share Posted December 29, 2009 Also I had read back several pages ago about someone who was using Parallels (which I do too) and that you must have within the BIOS "Virtualization Technology" enabled instead of disabled as per your guide. I did that (enabled it I mean) and everything seems to be just fine. You may wish to note that on your new guide, no biggie, it's up to you. -CPU Enhanced Halt (C1E)-C2/C2E State Support -CPU EIST Function -C4/C4E State Support -Virtualization Technology I installed Snow using usb drive with those things disabled in bios then reenabled them afterwards. No problems here either. I don't know if we still need to disable them to install. Link to comment Share on other sites More sharing options...
SavvyX4 Posted December 29, 2009 Share Posted December 29, 2009 Ok, so I am using the DSDT from swavek's post, with changes for my cpu pstates, and everything seems to be working great, except for sound. I've also followed swavek's link about using the modified boot loader with the FADT along with your DSDT and I have my system running with just 2 kexts in E/E: fakesmc and LegacyHDA. That being said, I've tried everything I can find and I cannot get my sound working at all . In System Profiler it shows that the sound hardware is there, but there are no Available Devices. I've tried several different LegacyHDAs with no luck, and cannot seem to put my finger on what I'm missing. It does seem that my disk performance issues are fixed, but I'm still waiting to use my system for a longer sustained period between restarts before I'm 100% on that. Booyah! I figured out that I didn't have a clean AppleHDA.kext in S/L/E based on my system's lifespan and various sound hacks that I had previously employed. I grabbed this off my install DVD and now I'm up and running with sound, and only 2 kexts in E/E. Thanks for everyone's awesome info in this thread, and it looks like even LegacyHDA may be elimiated soon with another DSDT fix, which would leave us with one kext for our boards, which I think is friggin amazing! Link to comment Share on other sites More sharing options...
sw170 Posted December 29, 2009 Share Posted December 29, 2009 ...and it looks like even LegacyHDA may be elimiated soon with another DSDT fix, which would leave us with one kext for our boards, which I think is friggin amazing! you can already try it: with this code and without LegacyHDA, downside - green jack output only :/ Device (HDEF) { Name (_ADR, 0x001B0000) Method (_PRW, 0, NotSerialized) { Return (Package (0x02) { 0x0D, 0x05 }) } Method (_DSM, 4, NotSerialized) { Store (Package (0x0A) { "built-in", Buffer (One) { 0x00 }, "codec-id", Buffer (0x04) { 0x89, 0x08, 0xEC, 0x10 }, "layout-id", Buffer (0x04) { 0x42, 0x00, 0x00, 0x00 }, "device-type", Buffer (0x11) { "ALC889a" }, "PinConfigurations", Buffer (One) { 0x00 } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } Link to comment Share on other sites More sharing options...
sw170 Posted December 29, 2009 Share Posted December 29, 2009 ...I'm wondering if there's a way to install driver on another way, or something else to do, to connect both monitors and make them work And then what to do with efi string in com.apple.boot.plist? And, if it's not hard, if you can explain in one-two sentences why is not good to use injections. ... There is nothing wrong about using efi injectors another option you can try for your graphic card without efi injection is add this code to com.apple.boot.plist: <key>GraphicsEnabler</key> <string>y</string> Link to comment Share on other sites More sharing options...
marinn Posted December 30, 2009 Share Posted December 30, 2009 There is nothing wrong about using efi injectorsanother option you can try for your graphic card without efi injection is add this code to com.apple.boot.plist: <key>GraphicsEnabler</key> <string>y</string> Thx, I've tried with it now, but no success, the same problem. I'll try to connect tomorow brother's samsung with real DVI port and see what's happening, maybe this driver has a problem with converting analog-digital. But in windows and ubuntu works fine. Is there a chance to modify the efi string on some way? I have no idea where to start.. Here's the string: 6c0200000100000001000000600200000d00000002010c00d041030a010000000101060 000010101060000007fff04000e0000004e00560050004d0000002000000001000000000000000000 000000000000000000000000000000000000220000005600520041004d002c0074006f00740061006 c00730069007a006500000008000000000000201c0000006400650076006900630065005f00740079 007000650000000f0000004e5644412c506172656e740e0000006e0061006d00650000000b0000006 46973706c617922000000400030002c006400650076006900630065005f0074007900700065000000 0b000000646973706c617922000000400031002c006400650076006900630065005f0074007900700 0650000000b000000646973706c6179100000006d006f00640065006c0000001a0000006e56696469 61204765466f726365203934303020475420000000400031002c0063006f006d00700061007400690 062006c00650000000e0000004e5644412c4e564d616314000000400030002c006e0061006d006500 0000120000004e5644412c446973706c61792d4114000000400031002c006e0061006d00650000001 20000004e5644412c446973706c61792d4220000000400030002c0063006f006d0070006100740069 0062006c00650000000e0000004e5644412c4e564d6163100000004e0056004300410050000000180 0000004000000000003000c00000000000007000000001e00000072006f006d002d00720065007600 6900730069006f006e0000002e0000006e5669646961204765466f7263652039343030204754204f7 0656e474c20456e67696e65205b4546495d Link to comment Share on other sites More sharing options...
d00m42 Posted December 30, 2009 Author Share Posted December 30, 2009 There is nothing wrong about using efi injectorsanother option you can try for your graphic card without efi injection is add this code to com.apple.boot.plist: <key>GraphicsEnabler</key> <string>y</string> There's nothing "wrong" with them, but I really do think using Chameleon's GraphicsEnabler as you mentioned or a com.apple.Boot.plist EFI string is a "nicer" way to handle graphics support. If it's necessary to have a fully-working system, the by all means do it, but when you can drop a few more unnecessary kexts, it's "nicer" to keep everything as "Vanilla" as possible. Link to comment Share on other sites More sharing options...
marinn Posted December 30, 2009 Share Posted December 30, 2009 There's nothing "wrong" with them, but I really do think using Chameleon's GraphicsEnabler as you mentioned or a com.apple.Boot.plist EFI string is a "nicer" way to handle graphics support. If it's necessary to have a fully-working system, the by all means do it, but when you can drop a few more unnecessary kexts, it's "nicer" to keep everything as "Vanilla" as possible. Ok, got it. But this graphics enabler.. i used it with EFI string. Shall I remove the string when using graphicsenabler? Link to comment Share on other sites More sharing options...
sw170 Posted December 30, 2009 Share Posted December 30, 2009 Thx, I've tried with it now, but no success, the same problem.... marinn, please try this Efi string: 6e0200000100000001000000620200000d00000002010c00d041030a010000000101060 000010101060000007fff04001e00000072006f006d002d007200650076006900730069006f006e00 00002f0000004e76696469612058465820393430304754203531324d62204f70656e474c20456e676 96e65205b4546495d22000000400030002c006400650076006900630065005f007400790070006500 00000b000000646973706c6179100000004e005600430041005000000018000000040000000000030 00400000000000007000000000e0000006e0061006d00650000000b000000646973706c6179140000 00400030002c006e0061006d0065000000120000004e5644412c446973706c61792d41100000006d0 06f00640065006c0000001b0000004e76696469612058465820393430304754203531324d620e0000 004e00560050004d00000020000000010000000000000000000000000000000000000000000000000 0000014000000400031002c006e0061006d0065000000120000004e5644412c446973706c61792d42 20000000400031002c0063006f006d00700061007400690062006c00650000000e0000004e5644412 c4e564d6163220000005600520041004d002c0074006f00740061006c00730069007a006500000008 0000000000002020000000400030002c0063006f006d00700061007400690062006c00650000000e0 000004e5644412c4e564d616322000000400031002c006400650076006900630065005f0074007900 7000650000000b000000646973706c61791c0000006400650076006900630065005f0074007900700 0650000000f0000004e5644412c506172656e74 There's nothing "wrong" with them, but I really do think using Chameleon's GraphicsEnabler as you mentioned or a com.apple.Boot.plist EFI string is a "nicer" way to handle graphics support. If it's necessary to have a fully-working system, the by all means do it, but when you can drop a few more unnecessary kexts, it's "nicer" to keep everything as "Vanilla" as possible. agreed, actually I meant nothing wrong with Efi strings, sorry for confusion, too much wine maybe.. But this graphics enabler.. i used it with EFI string. Shall I remove the string when using graphicsenabler? yes, remove efi string if use GraphicsEnabler Link to comment Share on other sites More sharing options...
SavvyX4 Posted December 30, 2009 Share Posted December 30, 2009 you can already try it:with this code and without LegacyHDA, downside - green jack output only :/ Device (HDEF) { Name (_ADR, 0x001B0000) Method (_PRW, 0, NotSerialized) { Return (Package (0x02) { 0x0D, 0x05 }) } Method (_DSM, 4, NotSerialized) { Store (Package (0x0A) { "built-in", Buffer (One) { 0x00 }, "codec-id", Buffer (0x04) { 0x89, 0x08, 0xEC, 0x10 }, "layout-id", Buffer (0x04) { 0x42, 0x00, 0x00, 0x00 }, "device-type", Buffer (0x11) { "ALC889a" }, "PinConfigurations", Buffer (One) { 0x00 } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } Thanks for the tip! I just put this snippet in my DSDT and I am running with only fakesmc now in E/E. I am extremely impressed with how much progress has been made in getting our systems up and running as awesome as they do. I'm excited to see whats next Link to comment Share on other sites More sharing options...
d00m42 Posted December 30, 2009 Author Share Posted December 30, 2009 Thanks for the tip! I just put this snippet in my DSDT and I am running with only fakesmc now in E/E. I am extremely impressed with how much progress has been made in getting our systems up and running as awesome as they do. I'm excited to see whats next Great! I'm still working on the new guide, but I've been impressed as well how far OS X support on non-standard hardware has come in the past few years and even months. Link to comment Share on other sites More sharing options...
jamse Posted December 31, 2009 Share Posted December 31, 2009 Great! I'm still working on the new guide, but I've been impressed as well how far OS X support on non-standard hardware has come in the past few years and even months. hey d00m42 are you having any issues upgrading to 10.6.2? everytime i update it to that it breaks my install. have any suggestions? Link to comment Share on other sites More sharing options...
Chrisbees Posted December 31, 2009 Share Posted December 31, 2009 hey d00m42 are you having any issues upgrading to 10.6.2? everytime i update it to that it breaks my install. have any suggestions? How did it break your install? Make sure you do NOT have old SleepEnabler.kext installed when you update or it will kernel panic the whole way home and back. Has anyone had any luck getting their hard drives to show up as internal? I thought the IOAHCIBlockStorageInjector.kext was supposed to do that but its not. Read about tricking drivers via the DSDT here on the forum but it talks about lspci command which is not even a valid command. Had got bootcamp to work but it won't let me work on the hard drives because they are listed as external. Link to comment Share on other sites More sharing options...
d00m42 Posted December 31, 2009 Author Share Posted December 31, 2009 How did it break your install? Make sure you do NOT have old SleepEnabler.kext installed when you update or it will kernel panic the whole way home and back. Has anyone had any luck getting their hard drives to show up as internal? I thought the IOAHCIBlockStorageInjector.kext was supposed to do that but its not. Read about tricking drivers via the DSDT here on the forum but it talks about lspci command which is not even a valid command. Had got bootcamp to work but it won't let me work on the hard drives because they are listed as external. The IOAHCIBlockStorageInjector.kext should be the one that makes the HDs show up as internal... If I remember correctly, because I have IDE DVD drives, I messed around with the two different AHCI settigns and left one of them on IDE (and that fixed the problem). If you want to keep both settings on AHCI, however, I would look into the DSDT solution (as it's a little more elegant) or try a different IOAHCI kext. Link to comment Share on other sites More sharing options...
Recommended Posts