Jump to content

Problems with DSDT for OSX 10.8.2 on Dell Precision T1600


  • Please log in to reply
17 replies to this topic

#1
aznphatb0i

aznphatb0i

    InsanelyMac Protégé

  • Members
  • Pip
  • 11 posts
Summary/TLDR:

Attached is my original DSDT.aml file.
Patch file:
http://olarila.com/P...ision T7500.txt

Cannot patch due to 2 errors:

6538 Error Name already exists in scope (SBUS)
6540 Error Name already exists in scope (_ADR)



Full information:

Hello!


My System: http://www.dell.com/...-spec-sheet.pdf


The resources I have been using:
• ###### - Mountain Lion 1.5.3: http://www.tonymacx8...?do=file&id=134
• ###### - Mountain Lion 5.1.3: http://www.tonymacx8...?do=file&id=148
• DSDT Editor: http://olarila.com/f...ic.php?f=7&t=62
• DSDT Autopatcher: http://olarila.com/f....php?f=22&t=507
• KEXTUtility: http://cvad-mac.narod2.ru/Kext_Utility
• T7500 Patch file (T1600 & T7500 desktops use the exact same motherboard): http://olarila.com/P...ision T7500.txt
• Mountain Lion ALCA269 KEXT: http://www.osx86.net...ersion__...html


What I did:


I installed using ###### using this guide (had to use PCIRootUID=0, -x flags). The install was successful -- however I am only able to boot into the OS via the ###### USB, and only when using the flags PCIRootUID=0 and -x.


I attempted to extract my DSDT using DSDT Editor. I ended up with 4 errors that could not be fixed -- the error in all 4 cases was "Must be a multiple of alignment/granularity value." I came across this page which mentioned the same error (third code segment up from the bottom of the page). By changing the code commented /alignment from 0x08 to 0x01 I was able to successfully compile and save the DSDT and save it to my desktop.


Attempted to use AutoPatcher using the DSDT file just generated and the T7500 patch file. Autopatcher log shows an error - it was unable to compile.


I ran ######, located on my desktop. I referenced this page to see what options I should select (T7500 and T1600 desktops use the same motherboard). I selected User DSDT, NullCPUPowerManagement, and PCIRootUID fix.


I opened KEXTUtility and dragged on the ALCA269 file.






After all these steps -- I am still at my initial stage -- I can boot into OSX, but only via the ###### USB bootloader, and only with the PCIRootUID=0 and -x (safemode) flags. Attempting to boot the PC without the USB inserted results in no bootable device being detected.

Attempting to boot without the -x flag results in the boot stopping at:
"com.apple.launchd 1 com.apple.mrt 54 Stopping job..."


Would love any feedback on what i'm doing wrong! If you need any more information I would be happy to provide it.




Thank You!

Attached Files

  • Attached File  DSDT.zip   10.45KB   13 downloads


#2
aznphatb0i

aznphatb0i

    InsanelyMac Protégé

  • Members
  • Pip
  • 11 posts
UPDATE: Seems I am able to boot from hard drive -- have to manually select boot device during POST via F12 to do so

All other issues stand.

#3
Rampage Dev

Rampage Dev

    InsanelyMac Deity

  • Local Moderators
  • 2,014 posts
  • Gender:Male
See attached:

Attached Files



#4
aznphatb0i

aznphatb0i

    InsanelyMac Protégé

  • Members
  • Pip
  • 11 posts
Thanks for the reply Rampage Dev!

Ran MultiBaest with that DSDT.aml on the desktop and only 'User DSDT' option checked on a fresh install of OSX.

System now automatically starts booting into OSX -- but fails to boot all the way:

Verbose is as follows:

PMAP: PCID enabled
Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64
vm_page_bootstrap: 2019853 free pages and 60915 wired pages
kext submap [0xffffff7f80741000 - 0xffffff8000000000], kernel text [0xffffff8000200000 - 0xffffff8000741000]
zone leak detection enabled
standard timeslicing quantum is 10000 us
standard background quantum is 2500 us
mig_table_max_displ = 74
TSC Deadline Timer supported and enabled!
correcrypto kext started!
Running kernel space in FIPS MODE
Plist hmac value is 735d392b68241ef173d81097b1c8ce9ba283521626d1c973ac376838c466757d
Computed hmac value is 735d392b68241ef173d81097b1c8ce9ba283521626d1c973ac376838c466757d
corecypto.kext FIPS integrity post tested passed!
corecypto.kext FIPS AES CBC POST passed!
corecypto.kext FIPS TDES CBC POST passed!
corecypto.kext FIPS AES ECB AESNI passed!
corecypto.kext FIPS AES XTS AESNI passed!
corecypto.kext FIPS SHA POST passed!
corecypto.kext FIPS HMAC POST passed!
corecypto.kext FIPS ECDSA POST passed!
corecypto.kext FIPS DRBG POST passed!
corecypto.kext FIPS POST passed!

#5
Rampage Dev

Rampage Dev

    InsanelyMac Deity

  • Local Moderators
  • 2,014 posts
  • Gender:Male
You never do what you do... you just place the DSDT in your extra folder. You will have to do a clean install...

#6
aznphatb0i

aznphatb0i

    InsanelyMac Protégé

  • Members
  • Pip
  • 11 posts
Already did a fresh install -- though I also learned that boot option DSDT=Null would also have worked!

So now i'm back to square one -- where should I go from here?

#7
Rampage Dev

Rampage Dev

    InsanelyMac Deity

  • Local Moderators
  • 2,014 posts
  • Gender:Male
What happens when you place the DSDT in your extra folder manualy?

#8
aznphatb0i

aznphatb0i

    InsanelyMac Protégé

  • Members
  • Pip
  • 11 posts
On a fresh install of OSX I have taken your DSDT and put it in a folder /Extras which I created in the root of the operating systems drive.





Verbose is as follows:

PMAP: PCID enabled
Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64
vm_page_bootstrap: 203271 free pages and 67497 wired pages
kext submap [0xffffff7f80741000 - 0xffffff8000000000], kernel text [0xffffff8000200000 - 0xffffff8000741000]
zone leak detection enabled
standard timeslicing quantum is 10000 us
standard background quantum is 2500 us
mig_table_max_displ = 74
TSC Deadline Timer supported and enabled!
correcrypto kext started!
Running kernel space in FIPS MODE
Plist hmac value is 735d392b68241ef173d81097b1c8ce9ba283521626d1c973ac376838c466757d
Computed hmac value is 735d392b68241ef173d81097b1c8ce9ba283521626d1c973ac376838c466757d
corecypto.kext FIPS integrity post tested passed!
corecypto.kext FIPS AES CBC POST passed!
corecypto.kext FIPS TDES CBC POST passed!
corecypto.kext FIPS AES ECB AESNI passed!
corecypto.kext FIPS AES XTS AESNI passed!
corecypto.kext FIPS SHA POST passed!
corecypto.kext FIPS HMAC POST passed!
corecypto.kext FIPS ECDSA POST passed!
corecypto.kext FIPS DRBG POST passed!
corecypto.kext FIPS POST passed!
NullCPUPowerManagement::init: properties=0xffffff8012d840c0
NullCPUPowerManagement::start


#9
Rampage Dev

Rampage Dev

    InsanelyMac Deity

  • Local Moderators
  • 2,014 posts
  • Gender:Male
-v cpus=1 DSDT=No

Then report back.

#10
aznphatb0i

aznphatb0i

    InsanelyMac Protégé

  • Members
  • Pip
  • 11 posts
Fresh install of OSX
Created a folder called "Extra" in the root directory
Placed the provided DSDT.aml file in the "Extra" folder
Booted with flags: -v cpus=1 DSDT=No


Boot stops at: [IOBluetoothHCIController][start] -- completed

More: http://i.imgur.com/oqSg9.jpg
http://i.imgur.com/wDaIk.jpg

#11
Rampage Dev

Rampage Dev

    InsanelyMac Deity

  • Local Moderators
  • 2,014 posts
  • Gender:Male
Boot with GraphicsEnabler=No

then try yes. Its stuck on the framebuffer of your GPU.

#12
aznphatb0i

aznphatb0i

    InsanelyMac Protégé

  • Members
  • Pip
  • 11 posts
Fresh install of OSX
Created a folder called "Extra" in the root directory
Placed the provided DSDT.aml file in the "Extra" folder

Booted with flags: -v GraphicsEnabler=No

Boot stops at:
NullCPUPowerManagement::start

Booted with flags: -v GraphicsEnabler=Yes

Boot stops at: NullCPUPowerManagement::start

Booted with flags: -v GraphicsEnabler=No cpus=1 DSDT=no

Boot stops at:
[IOBluetoothHCIController][start] -- completed

Booted with flags: -v GraphicsEnabler=Yes cpus=1 DSDT=no

Boot stops at: [IOBluetoothHCIController][start] -- completed

Booted with flags: -v GraphicsEnabler=Yes cpus=1

Boot stops at: [IOBluetoothHCIController][start] -- completed

Booted with flags: -v GraphicsEnabler=No cpus=1

Boot stops at: [IOBluetoothHCIController][start] -- completed

#13
aznphatb0i

aznphatb0i

    InsanelyMac Protégé

  • Members
  • Pip
  • 11 posts
SOLUTION!

I disabled "VT-d" in my BIOS

I am now on a fresh installation of OSX -- I am able to boot into OS successfully with just the PCIRootUID=0 flag

Now where do I go from here?

• What is the best way to get the OS to boot from HD instead of USB without breaking anything?

• How to enable audio (ALCA269) ?

• Anything else I need to configure for full functionality? • Should I try using patched DSDT again? • Patched SSDT? Or unnecessary?

• Anyway to get VT-d working (does VT-d come into play when running a VM under OSX86?)

#14
aznphatb0i

aznphatb0i

    InsanelyMac Protégé

  • Members
  • Pip
  • 11 posts
Where should I go from here?

#15
Rampage Dev

Rampage Dev

    InsanelyMac Deity

  • Local Moderators
  • 2,014 posts
  • Gender:Male
OK. List what you have installed post install.

#16
aznphatb0i

aznphatb0i

    InsanelyMac Protégé

  • Members
  • Pip
  • 11 posts
Did the following:


Followed these steps:
http://olarila.com/f...php?f=18&t=1703
http://olarila.com/f...php?f=27&t=1716



Now boot stops at


Waiting for DSMOS...
macx_swapon SUCCESS
ACPI_SMC_PlatformPlugin::initfanthrottlecontrol - waiting for AppleSMC


Should I be using ###### instead? Did I miss some options?


Help! A step-by-step from clean installation would be much appreciated :]

#17
aznphatb0i

aznphatb0i

    InsanelyMac Protégé

  • Members
  • Pip
  • 11 posts
UPDATE:


I installed FakeSMC and plugins via ###### -- system now boots!


I have to use "GraphicsEnabler=Yes" and "PCIRootUID=0" flags --- is there any 'negative' ramifications from using either of these flags?


Now I guess the last thing to do (or am i forgetting anything else?) is to get sound functioning -- any advice on this? my chipset is ALC269

#18
speedyrazor

speedyrazor

    InsanelyMac Protégé

  • Members
  • Pip
  • 18 posts
Hi, I am sucsssfully running OSX 10.7.5 on a Dell Precision T7500, specs below.
Should I place the above DSDT.aml in the extras folder, or should I leave it as is?
What would I gain from using DSDT.aml, as everything 'seems' to be running ok?

Here are my specs:
Dell Precision T7500
Single X5650 2.79Mhz 6 core Xeon CPU (would love to use two, but have to remove one CPU, kernel panik)
8GB Ram
NVidia 560 Ti 1GB
SAS boot hard rive

Kind regards.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy