Jump to content

[SOLVED] DSDT error in OS X verbose after Windows shutdown


  • Please log in to reply
17 replies to this topic

#1
SRSR333

SRSR333

    InsanelyMac Protégé

  • Members
  • PipPip
  • 84 posts
  • Gender:Male
  • Location:Singapore
Well, as the title says, I am not able to boot to OS X desktop with a DSDT in my /Extra folder after I shutdown from Windows on my Samsung RF411 notebook. Verbose mode always hangs somewhere around System State [S0 S3 S5 etc..]
What's the problem?

#2
Lejenk

Lejenk

    InsanelyMac Legend

  • Members
  • PipPipPipPipPipPipPipPipPip
  • 1,381 posts
  • Gender:Male
  • Location:Netherlands
Take a photo of the verbose error, and upload it here please. I don't think it has to to anything with your DSDT.

Also, some information about your system would be nice.

#3
SRSR333

SRSR333

    InsanelyMac Protégé

  • Members
  • PipPip
  • 84 posts
  • Gender:Male
  • Location:Singapore
My system specs:

Samsung NP-RF411-S03SG
Intel Core i7-2630QM
8GB DDR3 RAM 1333 MHz
NVIDIA GT 525M + Intel HD Graphics 3000 NVIDIA Optimus

Windows 7 + OS X 10.8.2 Dual-boot on single hard drive

My laptop isn't with me right now, so I can't upload a photo. But let me elaborate on what happens: after shutting down completely from Windows, I boot up to OS X with Chameleon. I get a hang. I boot up again with boot flag 'DSDT=null' and I can boot to OS X desktop. I think it is indeed something to do with DSDT...

#4
Gringo Vermelho

Gringo Vermelho

    The Jan Bird fix

  • Supervisors
  • 6,034 posts
  • Gender:Male
  • Location:Brazil
Did you extract and patch the DSDT yourself or did you download a premade one from somewhere?

#5
SRSR333

SRSR333

    InsanelyMac Protégé

  • Members
  • PipPip
  • 84 posts
  • Gender:Male
  • Location:Singapore
No, self extracted DSDT but I used a patch file from the Olarila forum... No weird stuff happening in the DSDT editor. Only 2 errors and 2 warnings which I corrected myself. I use a DSDT for brightness and audio and battery detection. I prefer DSDT over third-party kexts...

#6
SRSR333

SRSR333

    InsanelyMac Protégé

  • Members
  • PipPip
  • 84 posts
  • Gender:Male
  • Location:Singapore
And the screenshot now:

Attached Files



#7
Lejenk

Lejenk

    InsanelyMac Legend

  • Members
  • PipPipPipPipPipPipPipPipPip
  • 1,381 posts
  • Gender:Male
  • Location:Netherlands
Mind uploading the unedited DSDT?
What patches did you apply on the current?

Forgot to follow the topic, sorry about that.

#8
SRSR333

SRSR333

    InsanelyMac Protégé

  • Members
  • PipPip
  • 84 posts
  • Gender:Male
  • Location:Singapore
Alright, here's my extracted unedited DSDT.dsl, the patch file I use, and my currently patched DSDT. Please take a look... Thanks...

Attached Files



#9
Lejenk

Lejenk

    InsanelyMac Legend

  • Members
  • PipPipPipPipPipPipPipPipPip
  • 1,381 posts
  • Gender:Male
  • Location:Netherlands
Thank you.
Can you try the following file and see if it solves the problem? Applied basic patches and fixes.

The 2 dsl files differ a lot, and the patched one, did not match the txt, had extra info in it that is not provided by the patch.

Attached Files



#10
SRSR333

SRSR333

    InsanelyMac Protégé

  • Members
  • PipPip
  • 84 posts
  • Gender:Male
  • Location:Singapore

Thank you.
Can you try the following file and see if it solves the problem? Applied basic patches and fixes.

The 2 dsl files differ a lot, and the patched one, did not match the txt, had extra info in it that is not provided by the patch.


Right.. I'm not too literate when it comes to DSDT. What exactly do you mean when you say that the patched DSDT had 'extra info in it that was not provided by the patch'?

I simply extracted my DSDT with DSDT Editor, applied the patch, then edited out errors and warnings with the 'Fix Errors' button in the compiler. I didn't do anything else..

#11
Lejenk

Lejenk

    InsanelyMac Legend

  • Members
  • PipPipPipPipPipPipPipPipPip
  • 1,381 posts
  • Gender:Male
  • Location:Netherlands
Mostly these extra references. So you extracted the DSDT from within OSX?

Attached Files



#12
k3nny

k3nny

    InsanelyMac Legend

  • Members
  • PipPipPipPipPipPipPip
  • 538 posts
  • Gender:Male
Probably a stupid question but does it hang when booting Mac without any DSDT file?
You don't mention it explicitly in your first post.

If it doesn't, does it hang with a DSDT with fixed errors only?

#13
SRSR333

SRSR333

    InsanelyMac Protégé

  • Members
  • PipPip
  • 84 posts
  • Gender:Male
  • Location:Singapore

Probably a stupid question but does it hang when booting Mac without any DSDT file?
You don't mention it explicitly in your first post.

If it doesn't, does it hang with a DSDT with fixed errors only?


No, its not a stupid question. Yes, I didn't address it in my first post. OS X only shows this error WHEN I HAVE a DSDT.aml in /Extra folder. As I mentioned earlier, I have to use the boot flag DSDT = null in Chameleon before I boot else I get an error. This error only happens after a shutdown from Windows.

And @Lejenk, yes, I extracted this DSDT in OS X. I used MaciASL to extract, but I use DSDT editor to patch and stuff

#14
k3nny

k3nny

    InsanelyMac Legend

  • Members
  • PipPipPipPipPipPipPip
  • 538 posts
  • Gender:Male
So it does! work with a DSDT without any problems whatsoever as long as you don't have any Windows boots in between?
Then it is clearly not a DSDT issue.

EDIT:

What Windows version are you using?

Things that you could try.
- Use patched AppleRTC. I don't know if Chameleon can patch it, otherwise you will need to do it yourself.
- Set Windows to use Unreal err, I mean Universal Clock Time (UTC) :P instead of Local Time (click)

Edited by k3nny, 08 February 2013 - 03:37 PM.


#15
Lejenk

Lejenk

    InsanelyMac Legend

  • Members
  • PipPipPipPipPipPipPipPipPip
  • 1,381 posts
  • Gender:Male
  • Location:Netherlands
Use aida64 to extract your DSDT from Windows, this way the information will be pulled from the bios, instead of the drivers/ioreg.

A video on how to do this, can be found here:

#16
SRSR333

SRSR333

    InsanelyMac Protégé

  • Members
  • PipPip
  • 84 posts
  • Gender:Male
  • Location:Singapore
@ k3nny:

I already have a patched AppleRTC.kext. I think I'll try your fix, see if it works, because I have to readjust time every time I switch OS. I'm just wondering if this also happens on a real Mac with Boot Camp.

BTW I use Windows 7 SP1.

@Lejenk:

Yeah, I'll extract my DSDT in Windows and apply the patches in the patch file, see how it works.

Thanks for the help, guys.

#17
SRSR333

SRSR333

    InsanelyMac Protégé

  • Members
  • PipPip
  • 84 posts
  • Gender:Male
  • Location:Singapore

Things that you could try.
- Use patched AppleRTC. I don't know if Chameleon can patch it, otherwise you will need to do it yourself.
- Set Windows to use Unreal err, I mean Universal Clock Time (UTC) :P instead of Local Time (click)


Yeah, the time fix fixes my time issue. I've not tried DSDT yet, so have to wait a little..

And after using a DSDT extracted in Windows and then edited in OS X with the patch file, I don't get the error anymore! It works perfectly! Thanks!

#18
SRSR333

SRSR333

    InsanelyMac Protégé

  • Members
  • PipPip
  • 84 posts
  • Gender:Male
  • Location:Singapore
HELP! It's cropped up again... Only now, it happens after I force a shutdown when OS X panics (this happens because of a kext installed by InsomniaX)... The exact same error!





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