Jump to content
14 posts in this topic

Recommended Posts

Can someone clarify the DSDT file for me please?

 

All of these patchers seem to need to be run on the target hackintosh machine to create a DSDT specifically for the hardware.

 

And all of these guides require that I put my own patched DSDT file in the installation directory.

 

How do I go about this? I'm probably overlooking something very simple... but can someone just clarify a bit for me what I'm supposed to do with this DSDT file. Thanks guys

Link to comment
https://www.insanelymac.com/forum/topic/190110-dsdt-clarification-please/
Share on other sites

The DSDT is a table found in your motherboard's BIOS. The table contains information that tells an operating system how to interact with the hardware in your system such as CPU, audio, LAN, memory, USB, power management, etc. The BIOS tells your operating system how to load and use the DSDT and other tables found in the BIOS. Most operating systems like Windows and Linux can fully understand these tables and will recognize your system's hardware with little or no problems. Mac OS X, however, does not. That is why certain functions of your system will not work out-of-the-box (and often the cause of kernel panics) without the use of what are called "injectors", such as the DSDT.aml file, that fill in the missing information to tell Mac OS X how to interact with the hardware. This file is usually located in the /Extra folder and gets loaded at boot up. Another popular option is the use of customized BIOSes with patched DSDT tables that various people have made that serves the same purpose without the need for a DSDT.aml file.

 

As you migh have guessed, each DSDT.aml will be system specific. That is why people like fassl came with a DSDT patcher that will create a DSDT.aml file specific to your system. You can find his patcher here:

 

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

 

You might also want to look up MACinized's MacLoader_SL kit that simplifies things even more.

 

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

Thank you so much for the reply, but since its hardware specific, does the patcher need to be run on the machine that will have OSX installed on it?

 

So following that guide you sent me, what do i have to change in my dsdt? All it says is change length to 0x02 on one of the lines...

Thank you so much for the reply, but since its hardware specific, does the patcher need to be run on the machine that will have OSX installed on it?

 

So following that guide you sent me, what do i have to change in my dsdt? All it says is change length to 0x02 on one of the lines...

 

Yes, the patcher needs to run on the target machine in order to grab the DSDT table from the BIOS.

 

The 0x02 patch is to fix the real-time clock (RTC) and is most common across all motherboards. But that is just one patch. There are patches for sound, network, sleep, etc. Since those patches are board specific, you have to dig around for the exact patch for your motherboard. If you're lucky, somebody alredy has a fully tested and working dsdt.aml already compiled.

 

If your motherboard has an Award BIOS chip, then I suggest reading blackosx's guide on generating a custom dsdt.aml file:

 

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

 

Although his guide is specific to the Gigabyte EP45-DS3L board, the instructions and tools he uses should work for just about any motherboard using an Award BIOS. That is because the ACPI patcher utility works well for Award chips and not so well for AMI chips.

 

Short of finding a custom dsdt, your alternative is to find custom kext files for your hardware. Again, you need to do some searching.

 

So there are many ways to get your system up and running. The ideal way seems to be generating a custom dsdt.aml file with all the patches as this will be the most "vanilla" or "retail" method. Otherwise, look for kext files for whatever hardware you need to get working. Using third party kext files won't get your system working as close to a real Mac, but as long as it works...

A huge thank you to mattlowe01 for brining up a question I've been thinking about but been to shy to ask,

and even more thanks to thechasman for his good answers...

 

Soo.. have I understood it correctly that if I changed my bios - in my case to one of Juzzis bios'es (http://www.insanelymac.com/forum/index.php?showtopic=136586) - I would not have to mess around with DSDT-files?

 

If that's the case it just made my ongoing inter-brain-ial :) process leading to an install of SL much easier.

 

Thanks!

Thank you thechasman for that, clears up a lot of questions I had.

 

The problem is I have a factory built machine, so its not an aftermarket motherboard. I'll have to do some digging around on the net to find specifics.

 

It seems that all of my problems have been accompanied by ACPI errors, would this have something to do with the DSDT file? Or would this error be caused by a completely different aspect of the install.

 

After like two weeks of failed attempts, I was able to boot and install a SL retail disk using the boot 132 method. It wouldnt boot without the safemode flag, but once i applied -x, along with cpus=1 and busratio=20, it got about 80% through the install, yet whenever I try to boot into the partition it gives me a kernel panic having to do with the ACPI.

Bump, please.

 

Yes, I second that - how can you run a dsdt patcher if no osx is installed? I have a different computer running OSX but my home computer runs a vista64. Do I have to run it on the computer that has the leopard installed in it? It obviously has a totally different hardware specifications (It's a true Mac and my home computer is a PC).

 

One more question - can I use a FAT32 formatted partition on my HD to install the SL? will the cameleon recognize that partition? I cannot format just a partition of my (signle) NTFS HD (using MacDrive and such) to be HFS+

 

Thanks!

Can someone give me a quick explanation on how I can run fassl's DSDT patcher on vista 64bit?

 

You can't, it's an OS X app.

 

You can, however, extract your DSDT on Windows using Everest Corporate Edition, and then patch it with koalala's ACPIPatcher (search the forum) or by hand. DO NOT extract the DSDT directly from a BIOS file (Koalala's ACPIPatcher lets you do this) it must be extracted from a running system.

 

Juzzi's BIOS only has the CPU aliases removed from the DSDT, which is required on some motherboards to boot anything OSX (retail, hacked distro) at all. If CPU aliases is the only thing preventing you from booting, you can use his BIOS.

Later you can use DSDT.aml and remove the CPU aliases from there, and reflash an unmodified BIOS if you want.

 

If you're working from Windows and attempting to install retail OS X, there are a few guides around that shows how to install the Chameleon bootloader (with DSDT.aml, mandatory/patched kernel extensions for your hardware and so on) to an USB drive and use that to boot retail or hacked distribution media.

×
×
  • Create New...