Jump to content

Asus P6T SE Retail Snow Leopard Installation Guide [FLASHDRIVE] [UPDATED JUN. 28]]

tweak41

By tweak41,
in OSx86 10.6 (Snow Leopard)

 Share
1,279 posts in this topic

Recommended Posts

Defender666
Defender666
Posted
Posted
These audio kexts should fix the problem. If not let me know. Since I'm not on my system to test it I may have forgotten one small thing.

 

works but breaks possibility to attach usb soundcard. I use a Logitech usb soundcard for Skype so I don't need to change plugs.

 

Any ideas how to fix it?

 

Isn't it possible to get sound through dsdt?

Link to comment
Share on other sites
tweak41
tweak41
Posted
  • Author
Posted
Hey,

 

I did everything like described but I get stuck at the point you can see in the picture.

 

If DSMOS is still in the kexts folder, delete it. You only need fakesmc.kext

 

ATTENTION:

 

NEW AUDIO FOR 10.6.2

 

You're USB-based audio stuff will still work with this. Just tested. :(

 

http://www.insanelymac.com/forum/index.php?showtopic=161430

 

Make sure to delete the HDAEnabler.kext too when installing this.

Link to comment
Share on other sites
akhenamenra
akhenamenra
Posted
Posted
If DSMOS is still in the kexts folder, delete it. You only need fakesmc.kext

 

ATTENTION:

 

NEW AUDIO FOR 10.6.2

 

You're USB-based audio stuff will still work with this. Just tested. :(

 

http://www.insanelymac.com/forum/index.php?showtopic=161430

 

Make sure to delete the HDAEnabler.kext too when installing this.

 

 

cheers bruv works like a charm

 

peace

Link to comment
Share on other sites
athlon1977
athlon1977
Posted
Posted

Hi folks,

 

It's my first time with mac. I am following the guide but running "2 boot prep" the mac tells me that "sudo" is a dangerous operation and asks me for a password. Is it everything ok?.

As you can understand the mac is of a friend of mine and i don't want to make a mess

thanks in advance

Link to comment
Share on other sites
akhenamenra
akhenamenra
Posted
Posted
Hello

I cant update 10.6.2=kernel panic.how to?

thank you

 

 

follow my post or tfc byern or netkas v easy

just back up your mach_kernel with osx86tools (backup to drive where osx is )

 

then update then delete sleep enabler and make sure you have a disabler for the applecpumanagement either nullcpu or disabler (before reboot)

 

then reboot in with mach_kernel.backup command

Link to comment
Share on other sites
Bchemist
Bchemist
Posted
Posted

The DSDT didn't work for me when I tried it a few weeks ago and since then I've learned a couple of things about how to optimize the file. One of a few fixes (taken from the ESSENTIALS pack) is below if you feel that your system is less than optimal. This was from the DSDTSE compiler. There are several other steps that you can take such as renaming devices in your bios. Hopefully I'll be able to post an advanced DSDT soon. I really am not sure why the first DSDT didn't work, but either way it don't give up if yours doesn't work. There are many floating around from similar systems with similar specs. The DSDT is the most important file, so learn as much as you can about it...that is, if you are in this for the long haul and want a rock-solid system. I'm not a programmer other than knowing some basic html. It's just a matter of recognizing patterns and getting to know the concepts with time. But after a few hours of hands-on messing with the compiler, saving, recompiling, etc, I have a pretty good idea of what works and what doesn't. Now it's just a matter of piecing together what the real programmers on these forums have already put out there in a general sense to make our "hacks" even better than a real mac in that we have total control over every aspect of our system. Since our bios is not meant to run OSX, you cannot rely on it. OSX actually "confuses" the bios making the DSDT file essential to expedite data from hardware to software.

 

CPU Before:

 

    Scope (_PR)
   {
       Processor (P001, 0x01, 0x00000810, 0x06) {}
       Alias (P001, CPU1)
       Processor (P002, 0x02, 0x00000000, 0x00) {}
       Alias (P002, CPU2)
       Processor (P003, 0x03, 0x00000000, 0x00) {}
       Alias (P003, CPU3)
       Processor (P004, 0x04, 0x00000000, 0x00) {}
       Alias (P004, CPU4)
       Processor (P005, 0x05, 0x00000000, 0x00) {}
       Alias (P005, CPU5)
       Processor (P006, 0x06, 0x00000000, 0x00) {}
       Alias (P006, CPU6)
       Processor (P007, 0x07, 0x00000000, 0x00) {}
       Alias (P007, CPU7)
       Processor (P008, 0x08, 0x00000000, 0x00) {}
       Alias (P008, CPU8)
       Processor (P009, 0x09, 0x00000000, 0x00) {}
       Alias (P009, CPU9)
       Processor (P010, 0x0A, 0x00000000, 0x00) {}
       Processor (P011, 0x0B, 0x00000000, 0x00) {}
       Processor (P012, 0x0C, 0x00000000, 0x00) {}
       Processor (P013, 0x0D, 0x00000000, 0x00) {}
       Processor (P014, 0x0E, 0x00000000, 0x00) {}
       Processor (P015, 0x0F, 0x00000000, 0x00) {}
       Processor (P016, 0x10, 0x00000000, 0x00) {}
   }

 

CPU After:

 

    Scope (_PR)
   {
       Processor (P001, 0x01, 0x00000810, 0x06) {}
       Processor (P002, 0x02, 0x00000000, 0x00) {}
       Processor (P003, 0x03, 0x00000000, 0x00) {}
       Processor (P004, 0x04, 0x00000000, 0x00) {}
       Processor (P005, 0x05, 0x00000000, 0x00) {}
       Processor (P006, 0x06, 0x00000000, 0x00) {}
       Processor (P007, 0x07, 0x00000000, 0x00) {}
       Processor (P008, 0x08, 0x00000000, 0x00) {}
       Processor (P009, 0x09, 0x00000000, 0x00) {}
       Processor (P010, 0x0A, 0x00000000, 0x00) {}
       Processor (P011, 0x0B, 0x00000000, 0x00) {}
       Processor (P012, 0x0C, 0x00000000, 0x00) {}
       Processor (P013, 0x0D, 0x00000000, 0x00) {}
       Processor (P014, 0x0E, 0x00000000, 0x00) {}
       Processor (P015, 0x0F, 0x00000000, 0x00) {}
       Processor (P016, 0x10, 0x00000000, 0x00) {}
   }

Link to comment
Share on other sites
akhenamenra
akhenamenra
Posted
Posted

props to the makers and creater of this guide

 

 

( this is just to streamline the commands the computer has to work with at boot up and to make the cores more optimal as stated above and in the prev posts

 

 

in the zip

- DSDT Patcher (you will also here this called the Patcher)

- Readme

- Tools

Open up the DSDT Patcher file, a terminal will launch.

 

Next it will say, Press any key to continue.

 

Go ahead and press Enter on your keyboard.

 

Now the last line will state the following: Which OS to Emulate [0=Darwin, 1=WinXP, 2=WinVista]. Go ahead and hit 0 for Darwin and press Enter again.

 

Now if you go back to the DSDT Folder where the three files were originally located (the DSDT Patcher, Readme and Tools), you will notice two additional files/folders were created:

- Debug

- dsdt.aml

 

Go ahead and open up the Debug folder, locate a file called dsdt.dsl. Right click on this file and open it with TextEdit (this is an application located within the Applications folder). Once this file is open, locate the Alias CPU section (just run a search and type in the word CPU). For my computer, there were only two results which looked like this:

{

Processor (P001, 0x01, 0x00000810, 0x06) {}

Processor (P002, 0x02, 0x00000000, 0x00) {}

Alias (P002, CPU2)

Processor (P003, 0x03, 0x00000000, 0x00) {}

Processor (P004, 0x04, 0x00000000, 0x00) {}

Alias (P004, CPU4)

}

Go ahead and delete/clean the Alias lines so the end result should look something like this:

{

Processor (P001, 0x01, 0x00000810, 0x06) {}

Processor (P002, 0x02, 0x00000000, 0x00) {}

Processor (P003, 0x03, 0x00000000, 0x00) {}

Processor (P004, 0x04, 0x00000000, 0x00) {}

}

 

 

for all of them

 

 

 

Go ahead and save the file and close it.

 

Now drag and drop the dsdt.dsl file to your desktop,

 

 

Go back to your DSDT Patcher folder, delete the Debug folder and the dsdt.aml file

 

(NOT the dsdt.dsl file you just saved to your desktop).

 

 

Double click on your hard drive and go to Applications and find the Terminal (just type in Terminal in the finder if you have having trouble). Before opening the Terminal application,

 

 

make sure the DSDT Patcher terminal has been closed.

 

 

 

 

Now open the Terminal application.

 

Now drag and drop the DSDT Patcher file which is located within your DSDT Patcher folder in the Terminal. Hit the spacebar and drag and drop the dsdt.dsl file (the one you saved to your desktop) into the Terminal. Now hit Enter, it will not look like much happened and you will be back to a similar terminal window that you saw when you first opened up the DSDT Patcher terminal. It will ask you to Press any key to continue. Go ahead and hit enter and then select 0 for the Darwin OS to emulate and hit enter again.

 

 

Now if you don’t have any errors (errors should be zero forget the other warnings)

 

you should be good to go.

 

Lets go ahead and open up the new dsdt.aml file which has been created within the DSDT Patcher folder once again in TextEdit. Run a search on the word CPU, you should not find anything. My current version, the unpatched version of the DSDT.aml file which is located (hidden) within the root drive looks like this on the fourth line:

ñ L _PR_[É P001 [É P002 P002CPU2[É P003 [É P004 P004CPU4 DP80

 

Our new patched file looks like this:

ñ 9_PR_[É P001 [É P002 [É P003 [É P004 DP80

 

Notice CPU has been removed. Okay, now take the patched version of the dsdt.aml file located within the DSDT Patcher folder and rename it to DSDT.aml.

 

 

Go to your root drive ( where your efi is ) and delete the DSDT.aml file and drag and drop the new, patched DSDT.aml file.

 

 

to save as a aml file make sure you have extions turned on

 

 

finder/preferences/advanced/tick show all filename extensions

 

Now restart your computer,

 

 

once open again

 

do this

Open up the DSDT Patcher file, a terminal will launch.

 

Next it will say, Press any key to continue.

 

Go ahead and press Enter on your keyboard.

 

Now the last line will state the following: Which OS to Emulate [0=Darwin, 1=WinXP, 2=WinVista]. Go ahead and hit 0 for Darwin and press Enter again.

 

Now if you go back to the DSDT Folder where the three files were originally located (the DSDT Patcher, Readme and Tools), you will notice two additional files/folders were created:

- Debug

- dsdt.aml

 

Go ahead and open up the Debug folder, locate a file called dsdt.dsl. Right click on this file and open it with TextEdit (this is an application located within the Applications folder).

 

Once this file is open you will notice the code has been streamlined

 

 

without tweak41 we wouldnt be here and without the other dudes optimising the code we woulnt have a nice machine

 

peace

DSDT_Patcher1_1.0.1e.zip

Link to comment
Share on other sites
Bchemist
Bchemist
Posted
Posted

I was just using the patcher posted above for a laptop....it definitely cleans up the code quite a bit. I haven't tried it on my current system however to see if it can reduce the size of my .dsl file. That's next ;)

 

Here's my latest DSDT file, 4 more OCD hours later and I've tested it, running Photoshop, Final Cut, as well as the compiler at the same time. Everything is really screaming without the slightest hiccup now. The key is to compile each and every time you do a hack, otherwise errors will quickly spiral out of control and if there's no backup, you'll be back to square one. I learned this the hard way after 2 hours of not looking up from my first attempt and then getting 5 errors that turned into 104 after I "thought" I fixed it...

 

Anyway this is the DSDT file here is patched for the proper CST info for x58 chipsets. What I posted earlier was just to clean up the code but. The code added additionally is at the beginning and end to optimize the use of 8 cores when hyperthreading. Also SATA is fully fixed where I think that my RAID is faster than my Falcon 128 that has a 200mbps write speed. I just need to add a terabyte and see if time machine will work as well as it does on my P5Q where I have a pseudo RAID 10 working there with a SSD, 3-320gig in a striped array, and a 1 terabyte mirroring the two as well as the boot drive serving as the backup to all. I did several other patches and hacks to various components where everything should be working fully if it wasn't before...but this mobo is fairly easy to deal with so far. I may even upgrade again to the 10.6.2, but for now I'm having a hard time in seeing a reason to do so since I need to focus on actual work again heh heh

dsdt_23NovP6t_se.aml.zip

Link to comment
Share on other sites
mikeosx86
mikeosx86
Posted
Posted
Hi folks,

 

It's my first time with mac. I am following the guide but running "2 boot prep" the mac tells me that "sudo" is a dangerous operation and asks me for a password. Is it everything ok?.

As you can understand the mac is of a friend of mine and i don't want to make a mess

thanks in advance

 

That's okay dude. You cannot run certain commands without sudo. Just be careful and make sure you know what you are doing. Don't use it without knowing the consequences of your command.

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...