Jump to content

[Guide] Vanilla Retail 10.6.x with Chameleon v2 for Gigabyte GA-EP45-DS3L

blackosx

By blackosx,
in OSx86 10.6 (Snow Leopard)

 Share
3,676 posts in this topic

Recommended Posts

blackosx
blackosx
Posted
  • Author
Posted
How "in there" are you with the insanelymac.com admins, do they have a spare DB and some file space perhaps?

 

Oli

I am not "in there" at all, just an operator on the fringes... Lol

But we could ask? I'll send a PM..

 

EDIT: Sent

 

But it we get blankly refused any ideas for a different charitable host?

Link to comment
Share on other sites
blackosx
blackosx
Posted
  • Author
Posted
Ah,

 

I see, well to answer your previous post then perhaps one of these as a backup?

 

http://www.absolutely-free-hosting.com/free-php-hosting.php

The first one on the list would do, 000a.biz. Though I can't believe it offers all that for free.. what's the catch?

I guess you could proceed with building the site then move servers later if it gets approved here?

 

I see you added an update, thanks very much for keeping this motherboard going, you are doing a fine job

Hi lensboard, Thanks.

 

Yes, it's not finished yet, and I am still trying to find the time to work on the remaining chapters. After our discussion I took onboard your suggestions and although you mentioned having the all-in-one package which does make sense, I felt it better to split it in to manageable sections. That way I can keep relevant parts up to date more easily.

Link to comment
Share on other sites
Xider59
Xider59
Posted
Posted

Sorry, if i'm repeating.

I booted my 10.6.1 mac with old supported files and VoodooPS2Controller-0.98 from Chameleon's site.

But with new files I can't use my PS2 mouse and keyboard. The cursor don't move! Maybe there's some incompatibility?

 

I've used fakesmc, legacyhda, nullcpupowermanagement, orangeiconfix, sleepenabler and DSDT from the v2.4.1 support files and Asere's bootloader.

Link to comment
Share on other sites
blackosx
blackosx
Posted
  • Author
Posted
But with new files I can't use my PS2 mouse and keyboard. The cursor don't move! Maybe there's some incompatibility?

Hi Xider59

 

There aren't any PS2 device drivers in the support files as the requirements are for a USB keyboard & mouse.

You will need to add them yourself like you did previously with VoodooPS2Controller.

 

You can find a decent list of optional Snow Leopard kexts on this page of Stellarola's blog

Link to comment
Share on other sites
mm67
mm67
Posted
Posted
Hi Xider59

 

There aren't any PS2 device drivers in the support files as the requirements are for a USB keyboard & mouse.

You will need to add them yourself like you did previously with VoodooPS2Controller.

 

You can find a decent list of optional Snow Leopard kexts on this page of Stellarola's blog

 

I don't know about your version number's but if dsdt in that pack is recent then it probably is one that has all PS2 code removed. All that code has to be put back if someone wants to use PS2 devices.

Link to comment
Share on other sites
blackosx
blackosx
Posted
  • Author
Posted
I don't know about your version number's but if dsdt in that pack is recent then it probably is one that has all PS2 code removed. All that code has to be put back if someone wants to use PS2 devices.

Thanks for pointing that out mm67.

You should know as this DSDT is your work with only a few tweaks :D

 

Well I am going to make a decision not to change it and stick with the requirements set out at the beginning of this thread.

Requirements

 

• for 64-bit you need a CPU with SSE3. So all core 2 duos, quads & extremes.

• SATA HD's and SATA DVD drive and make sure BIOS SATA AHCI mode is set to AHCI.

• A purchased Retail Mac OS X install DVD (not the restore DVD you get with Apple hardware).

• A USB keyboard & Mouse.

....

....

But Xider59, I don't want to alienate you or others who have used this guide previously with PS2 devices. So I will try to post a different DSDT which you can use, though it might be a lot older, it will still include the latest fixes.

 

EDIT: Can you post your current DSDT and I can look at adding the latest fixes to it?

Link to comment
Share on other sites
helob
helob
Posted
Posted

Vanilla retail 10.6.2 install with Chameleon on a separate partition for the Gigabyte GA-EP45-DS3L

 

I have also produced three other guides for the GA-EP45-DS3L

Using DSDT on the GA-EP45-DS3L

Vanilla Retail 10.5.7 install guide with Chameleon on a separate partition

Vanilla Retail 10.5.7 install guide with Chameleon on the EFI partition with Dual Boot Windows 7 on same HDD

 

 

News

 

12th January 2010 - 07:50

Revised PDF guide in progress - 6 out of 9 PDF's uploaded

I have been slowly re-writing the PDF guide to bring it up to date with the current state of the OSX86 scene. I have now split it in to individual sections to make it easier for me to manage. I have posted six sections below in the Files section for reading now as they will help give up to date details. When I have them written & finshed everything I will clean up this front page as most of it will all be in the revised guide sections.

 

Hi blackosx,

Brilliant.

Just glanced through the 6 completed update PDF guide. Looks good and professional.

Will go through them in detail and advise if I see any glitches.

I hope you are planning on doing the same for "using DSDT on the GA-EP45-DS3L" after completing Vanilla Retail 10.6.2

TQ and have a nice day

Link to comment
Share on other sites
LOLmoe
LOLmoe
Posted
Posted

blackosx,

 

i have a question about smbios.plist

 

im not sure what is necessary and what is not..

this my smbios here

<?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>SMbiosvendor</key>
<string>Apple Computer, Inc.</string>
<key>SMbiosversion</key>
<string>MP11.88Z.005C.B08.0707251237</string>
<key>SMmanufacter</key>
<string>Apple Computer, Inc.</string>
<key>SMproductname</key>
<string>MacPro1,1</string>
<key>SMsystemversion</key>
<string>1.0</string>
<key>SMserial</key>
<string>XXXXXXXXX</string>
<key>SMfamily</key>
<string>macpro</string>	
<key>SMboardmanufacter</key>
<string>Gigabyte</string>
<key>SMboardproduct</key>
<string>GA-EP45-DS3L</string>
<key>SMexternalclock</key>
<string>333</string>
<key>SMmaximalclock</key>
<string>2666</string>
<key>SMbusspeed</key>
<string>0</string>
<key>SMmemserial_1</key>
<string>OCXXXXXXXXX*2-1</string>
<key>SMmemserial_3</key>
<string>OCXXXXXXXXX*2-2</string>
</dict>
</plist>

 

what should i add/takeout? thanks

Link to comment
Share on other sites
blackosx
blackosx
Posted
  • Author
Posted
[brilliant.

Just glanced through the 6 completed update PDF guide. Looks good and professional.

Will go through them in detail and advise if I see any glitches.

I hope you are planning on doing the same for "using DSDT on the GA-EP45-DS3L" after completing Vanilla Retail 10.6.2

TQ and have a nice day

I look forward to hearing how you get on. Thanks

 

I have a question about smbios.plist

 

im not sure what is necessary and what is not..

this my smbios here

... /snip/ ....

what should i add/takeout? thanks

Hi LOLmoe

 

The required contents of SMBIOS are changing at the moment with the release of the new code in Asere's modified RC4 bootloader. I think you are pretty much there ;)

 

My current SMBIOS looks like this...

<?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>SMbiosvendor</key>
   <string>Apple Inc.</string>
   <key>SMbiosversion</key>
   <string>IM91.008D.B08</string>
   <key>SMmanufacter</key>
   <string>Apple Inc.</string>
   <key>SMproductname</key>
   <string>iMac10,1</string>
   <key>SMsystemversion</key>
   <string>1.0</string>
   <key>SMserial</key>
   <string>XXXXXXXXXXXX</string>
   <key>SMfamily</key>
   <string>mac</string>
   <key>SMboardmanufacter</key>
   <string>Gigabyte.</string>
   <key>SMboardproduct</key>
   <string>GA-EP45-DS3L</string>
</dict>
</plist>

I currently have a conflict between iMac10,1 and my SMbiosversion reading that of an iMac9,1which doesn't seem cause issue (as far as I can tell) and the externalclock and maximalclock I am experimenting without as I did read something about these being auto injected. As for the serial numbers of the memory, I have left them out, but I see you have added yours. I might do the same as my modules don't have the codes embedded for Asere's bootloader to read them.

Link to comment
Share on other sites
LOLmoe
LOLmoe
Posted
Posted

Hey, BlackOSX,

 

Thank you very much for your reply.

Yea, I also heard that the CPU information was being injected by RC3 I think...

I am going to try without the CPU External Clock and Maximum clock.

 

Thanks!

 

UPDATE:

I don't know if I ever noticed this... but my Bus speed is 1.33 GHz (1/2 of my CPU Freq.)

hm...

Link to comment
Share on other sites
Xider59
Xider59
Posted
Posted

Hi blackosx!

I use DSDT that is precisely from the latest support files v2.4.1!

Can't I just put the kext required for working ps/2 into extra folder or if it's been deleted from DSDT, it won't work anyway?

If I had an usb controllers...

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

 

Thank you very much for your reply.

Yea, I also heard that the CPU information was being injected by RC3 I think...

I am going to try without the CPU External Clock and Maximum clock.

 

Thanks!

Yes. Oldnapalm created some code for auto detection of CPU's and it was included in PC-EFI 10.5 and you can also find it in Chameleon RC4. And the auto FSB detection is there too.

Link to comment
Share on other sites
blackosx
blackosx
Posted
  • Author
Posted
Hi blackosx!

I use DSDT that is precisely from the latest support files v2.4.1!

Can't I just put the kext required for working ps/2 into extra folder or if it's been deleted from DSDT, it won't work anyway?

If I had an usb controllers...

As mm67 said. The PS2 code has been removed from the DSDT that's supplied in the Support Files v2.4.1, so you can't use PS2 devices, even if you install the kexts.

 

blackosx,

 

OK, I got rid of the CPU freq, etc.

 

Oh if you noticed, I changed my SMbiosversion, and SMproductname to MacPro1,1 not 3,1.

Geekbench reports now that it's a MacPro1,1 not a hackintosh.

Sorry, my network connection at work is playing up here.... :(

But yes, some SMBIOS options result in Geekbench reporting your machine as a hackintosh.

Link to comment
Share on other sites
mm67
mm67
Posted
Posted
As mm67 said. The PS2 code has been removed from the DSDT that's supplied in the Support Files v2.4.1, so you can't use PS2 devices, even if you install the kexts.

 

 

Sorry, my network connection at work is playing up here.... :(

But yes, some SMBIOS options result in Geekbench reporting your machine as a hackintosh.

 

MacPro1,1 or 2,1 just don't do speedstepping. If one really is bothered about that Hackintosh label in Geekbench then iMac10,1 is a better choice since it does speedstepping like MacPro3,1 and has iMac10,1 as name in Geekbench.

Link to comment
Share on other sites
xAberracus
xAberracus
Posted
Posted

Hi Blackosx

 

I have been following your guides since 10.5.8 with EXTREME sucess in more than one computer, i would say my hackintosh has never feel so "retail" , lol

 

 

i want to ask you 3 questions

 

1. : its in my understatement that you don't use/have firewire card or devices, but i need them, and they are not working with your DSML, have you erased some part of the dsml so they dont woork? how do i enable it back?, i am using a PCI -E fw800 card wich is mac compatible and have worked in the past with 10.5.8 and 10.6.1 with a very basic modified dsml.

 

2. : My system has a Q9550 which means a Quad core 2.83 ghz, but about my mac says 2.66 ghz

 

3. : My system temp is getting to 85 Celsius (186.8 F) when its heavily taxed, i think its too much maybe is some problem in my dsml?

 

here is my dsml, please give me a hand

 

Thanks in advance

dsdt.aml.zip

Link to comment
Share on other sites
blackosx
blackosx
Posted
  • Author
Posted
Hi Blackosx

 

I have been following your guides since 10.5.8 with EXTREME sucess in more than one computer, i would say my hackintosh has never feel so "retail" , lol

 

 

i want to ask you 3 questions

 

1. : its in my understatement that you don't use/have firewire card or devices, but i need them, and they are not working with your DSML, have you erased some part of the dsml so they dont woork? how do i enable it back?, i am using a PCI -E fw800 card wich is mac compatible and have worked in the past with 10.5.8 and 10.6.1 with a very basic modified dsml.

 

2. : My system has a Q9550 which means a Quad core 2.83 ghz, but about my mac says 2.66 ghz

 

3. : My system temp is getting to 85 Celsius (186.8 F) when its heavily taxed, i think its too much maybe is some problem in my dsml?

 

here is my dsml, please give me a hand

 

Thanks in advance

Thanks

 

1: The GA-EP45-DS3L doesn't have Firewire so I don't use it. And yes, I have removed the Firewire code from DSDT also.

 

mmmm...The stripped down DSDT that I thought was so wonderful is proving to be a problem for others with different hardware.

I will have to work out how to add PS2 info back in (If I can find out exactly how to)

 

Here's a version of the generic one in the new support files, but with FireWire added back in.

GA_EP45_DS3L_DSDT_with_included_FireWire.zip

 

2: The CPU identification should work, but maybe for your CPU that's how it reads it? This will need to be verified by somebody else with your CPU.

 

3: That temp does sound high. Have you just added your stepping data, and is this the first time you've tried it?

I think you should remove this. You don't want to have duplicate declarations for your Processor.

 

 Scope (_PR)
   {
       Processor (CPU0, 0x00, 0x00000410, 0x06) {}
       Processor (CPU1, 0x01, 0x00000410, 0x06) {}
       Processor (CPU2, 0x02, 0x00000410, 0x06) {}
       Processor (CPU3, 0x03, 0x00000410, 0x06) {}
   }

 

I now use a slightly different style now, but it shouldn't matter as long as the values are correct.

For ref: This is how I have my data, thanks to the info and help from FormerlyKnownAs' speedstep thread.

Name (PSS, Package (0x05) // For Intel Core 2 Duo E7300 @ 2.66Ghz
       {
           Package (0x06) { 2670, 0, 10, 10, 0x0A1D, 0 },
           Package (0x06) { 2403, 0, 10, 10, 0x091D, 1 },
           Package (0x06) { 2136, 0, 10, 10, 0x081C, 2 },
           Package (0x06) { 1869, 0, 10, 10, 0x071B, 3 },
           Package (0x06) { 1602, 0, 10, 10, 0x061A, 4 }
       })

       Name (PSD, Package (0x05)
       {
           0x05,
           0x00,
           0x00,
           0xFC, // Double-checked the 0xFC value with ACPISpec v4.0 pdf
           0x02  // Number of Processors - If you have a Quad core CPU then this value should read 0x04
       })

       Name (CST, Package (0x04)
       {
           0x03, 
           Package (0x04) {ResourceTemplate () {Register (FFixedHW, 1, 2, 0x000,)},0x01,0x01,0x03E8},
           Package (0x04) {ResourceTemplate () {Register (FFixedHW, 1, 2, 0x010,)},0x02,0x01,0x01F4},
           Package (0x04) {ResourceTemplate () {Register (FFixedHW, 1, 2, 0x030,)},0x04,0x39,0x064}
       })

       Processor (CPU0, 0x0, 0x00000410, 0x06)
       {
           Alias (PSS, _PSS)
           Alias (PSD, _PSD)
           Alias (CST, _CST)
       }

       Processor (CPU1, 0x01, 0x00000410, 0x06)
       {
           Alias (PSS, _PSS)
           Alias (PSD, _PSD)
           Alias (CST, _CST)
       }

 

But, please understand, although I have a basic grasp of DSDT, I am by no means proficient, so for correct/expert advice I recommend seeking help at either the Vanilla SpeedStep thread or the Gigabyte DSDT Fix thread.

Link to comment
Share on other sites
xAberracus
xAberracus
Posted
Posted

Great Blackosx,

 

thanks for your help

 

Look using the dsdml with firewire that you just have sent me,

 

and adding my speedstep values, is this correct please?

 

 

  Scope (_PR) // Processor Tree - revised layout as MasterChief's latest DSDT v3.3
   {
       Name (PSS, Package (0x05) // For Intel Core 2 Qua2 E9550 @ 2.83Ghz
       {
           Package (0x06) { 2831, 0, 10, 10, 0x4822, 0 },
           Package (0x06) { 2664, 0, 10, 10, 0x0821, 1 },
           Package (0x06) { 2498, 0, 10, 10, 0x471F, 2 },
           Package (0x06) { 2331, 0, 10, 10, 0x071E, 3 },
           Package (0x06) { 2165, 0, 10, 10, 0x461C, 4 },
           Package (0x06) { 1998, 0, 10, 10, 0x061A, 5 }
                   })

       Name (PSD, Package (0x05)
       {
           0x05,
           0x00,
           0x00,
           0xFC, // Double-checked the 0xFC value with ACPISpec v4.0 pdf
           0x04  // Number of Processors - If you have a Quad core CPU then this value should read 0x04
       })

       Name (CST, Package (0x04)
       {
           0x03, 
           Package (0x04) {ResourceTemplate () {Register (FFixedHW, 1, 2, 0x000,,)},0x01,0x01,0x03E8},
           Package (0x04) {ResourceTemplate () {Register (SystemIO, 8, 0, 0x414,,)},0x02,0x01,0x01F4},
           Package (0x04) {ResourceTemplate () {Register (SystemIO, 8, 0, 0x415,,)},0x03,0x55,0xFA} 
       })

       Processor (CPU0, 0x0, 0x00000410, 0x06)
       {
           Alias (PSS, _PSS)
           Alias (PSD, _PSD)
           Alias (CST, _CST)
       }

       Processor (CPU1, 0x01, 0x00000410, 0x06)
       {
           Alias (PSS, _PSS)
           Alias (PSD, _PSD)
           Alias (CST, _CST)
       }

         Processor (CPU2, 0x02, 0x00000410, 0x06)
       {
           Alias (PSS, _PSS)
           Alias (PSD, _PSD)
           Alias (CST, _CST)
       }

       Processor (CPU3, 0x03, 0x00000410, 0x06)
       {
           Alias (PSS, _PSS)
           Alias (PSD, _PSD)
           Alias (CST, _CST)
       } 
   }

   Name (_S0, Package (0x04){Zero,Zero,Zero,Zero})
   Name (_S1, Package (0x04){One,Zero,Zero,Zero})
   Name (_S3, Package (0x04){0x05,Zero,Zero,Zero})
   Name (_S4, Package (0x04){0x06,Zero,Zero,Zero})
   Name (_S5, Package (0x04){0x07,Zero,Zero,Zero})

   OperationRegion (EXTM, SystemMemory, 0x000FF830, 0x10)
   Field (EXTM, WordAcc, NoLock, Preserve)
   {
       ROM1,   16, 
       RMS1,   16, 
       ROM2,   16, 
       RMS2,   16, 
       ROM3,   16, 
       RMS3,   16, 
       AMEM,   32
   }

   OperationRegion (DEBG, SystemIO, 0x80, One)
   Field (DEBG, ByteAcc, NoLock, Preserve)
   {
       DBG1,   8
   }

   OperationRegion (PMRS, SystemIO, 0x0430, 0x13)
   Field (PMRS, ByteAcc, NoLock, Preserve)
   {
       	,   4,
       SLPE,   1,
               Offset (0x08),
       GPSE,   16, 
       GPSS,   16,
               Offset (0x12),
           ,   1, 
       SWGC,   1 
   }

Link to comment
Share on other sites
mm67
mm67
Posted
Posted
Thanks

 

1: The GA-EP45-DS3L doesn't have Firewire so I don't use it. And yes, I have removed the Firewire code from DSDT also.

 

mmmm...The stripped down DSDT that I thought was so wonderful is proving to be a problem for others with different hardware.

I will have to work out how to add PS2 info back in (If I can find out exactly how to)

 

Here's a version of the generic one in the new support files, but with FireWire added back in.

GA_EP45_DS3L_DSDT_with_included_FireWire.zip

 

2: The CPU identification should work, but maybe for your CPU that's how it reads it? This will need to be verified by somebody else with your CPU.

 

3: That temp does sound high. Have you just added your stepping data, and is this the first time you've tried it?

I think you should remove this. You don't want to have duplicate declarations for your Processor.

 

 Scope (_PR)
   {
       Processor (CPU0, 0x00, 0x00000410, 0x06) {}
       Processor (CPU1, 0x01, 0x00000410, 0x06) {}
       Processor (CPU2, 0x02, 0x00000410, 0x06) {}
       Processor (CPU3, 0x03, 0x00000410, 0x06) {}
   }

 

I now use a slightly different style now, but it shouldn't matter as long as the values are correct.

For ref: This is how I have my data, thanks to the info and help from FormerlyKnownAs' speedstep thread.

Name (PSS, Package (0x05) // For Intel Core 2 Duo E7300 @ 2.66Ghz
       {
           Package (0x06) { 2670, 0, 10, 10, 0x0A1D, 0 },
           Package (0x06) { 2403, 0, 10, 10, 0x091D, 1 },
           Package (0x06) { 2136, 0, 10, 10, 0x081C, 2 },
           Package (0x06) { 1869, 0, 10, 10, 0x071B, 3 },
           Package (0x06) { 1602, 0, 10, 10, 0x061A, 4 }
       })

       Name (PSD, Package (0x05)
       {
           0x05,
           0x00,
           0x00,
           0xFC, // Double-checked the 0xFC value with ACPISpec v4.0 pdf
           0x02  // Number of Processors - If you have a Quad core CPU then this value should read 0x04
       })

       Name (CST, Package (0x04)
       {
           0x03, 
           Package (0x04) {ResourceTemplate () {Register (FFixedHW, 1, 2, 0x000,)},0x01,0x01,0x03E8},
           Package (0x04) {ResourceTemplate () {Register (FFixedHW, 1, 2, 0x010,)},0x02,0x01,0x01F4},
           Package (0x04) {ResourceTemplate () {Register (FFixedHW, 1, 2, 0x030,)},0x04,0x39,0x064}
       })

       Processor (CPU0, 0x0, 0x00000410, 0x06)
       {
           Alias (PSS, _PSS)
           Alias (PSD, _PSD)
           Alias (CST, _CST)
       }

       Processor (CPU1, 0x01, 0x00000410, 0x06)
       {
           Alias (PSS, _PSS)
           Alias (PSD, _PSD)
           Alias (CST, _CST)
       }

 

But, please understand, although I have a basic grasp of DSDT, I am by no means proficient, so for correct/expert advice I recommend seeking help at either the Vanilla SpeedStep thread or the Gigabyte DSDT Fix thread.

 

This DSDT doesn't have anything to do with the one we are using. It looks like some kind of a mixup of vanilla Gigabyte and MC's Asus DSDT and it has a lot of code that is useless on GB boards.

 

Firewire doesn't need any code in dsdt to work and adding PS2 support back shouldn't be too difficult, it just requires adding a couple of hundreds lines of code back to DSDT.

 

Those P-states don't look right, I have never seen VID values being so close to each other, on my Q9550 PSS table values go from 0x616 to 0x4820.

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