Jump to content

Sluggish operation, no sleep, no restart, no shutdown...


skysea76
 Share

53 posts in this topic

Recommended Posts

this must be what you need

DTGP

HID/CID

IRQs

REMOVE

RENAME

SMBUS

SHUTDOWN

FIX WARNINGS

HPET

 

Look for USBs

they appear as integrated?

Use this DSDT and see

 

LPC works natively?

With that DSDT I get:

-Orange Icons

-USB detected as "Built-in USB"

-HDDs detected as "Intel ICH10 AHCI"

 

What's the "official" LPC test? I get three checkbox options in sys prefs (all checked), AppleLPC appears in IOReg, and kextstat gives me com.apple.driver.AppleLPC. Does this mean it's "working"?

 

I'm about to try sleep, I'll post the results back.

 

 

Sleep is the same as before: it immediately (as in within 2s) goes all off, and if I press a mouse button or the powerbutton, the lights come on, the fans spin up, but in 1s it reboots.

Link to comment
Share on other sites

With that DSDT I get:

-Orange Icons

-USB detected as "Built-in USB"

-HDDs detected as "Intel ICH10 AHCI"

 

What's the "official" LPC test? I get three checkbox options in sys prefs (all checked), AppleLPC appears in IOReg, and kextstat gives me com.apple.driver.AppleLPC. Does this mean it's "working"?

 

I'm about to try sleep, I'll post the results back.

 

Sleep is the same as before: it immediately (as in within 2s) goes all off, and if I press a mouse button or the powerbutton, the lights come on, the fans spin up, but in 1s it reboots.

dont use ESB2, use kext

 

go to Energy saver and select "Start up automatically after a power failure"

try it

Link to comment
Share on other sites

dont use ESB2, use kext

 

go to Energy saver and select "Start up automatically after a power failure"

try it

Sorry about adding that as a reply, I thought you might not get a notification of my edit and was trying to keep the thing clean; I'll revert it in a sec.

I have "Start up automatically..." checked (and always have).

What do you mean by "don't use ESB2, use kext". From what I understood:

you want to edit your DSDT so that you get ICH10R detected as ESB2 so that you don't get orange icons, and it doesn't affect the functionality of SATA (except you loose the ability to hotswap, I guess).

Link to comment
Share on other sites

Sorry about adding that as a reply, I thought you might not get a notification of my edit and was trying to keep the thing clean; I'll revert it in a sec.

I have "Start up automatically..." checked (and always have).

What do you mean by "don't use ESB2, use kext". From what I understood:

you want to edit your DSDT so that you get ICH10R detected as ESB2 so that you don't get orange icons, and it doesn't affect the functionality of SATA (except you loose the ability to hotswap, I guess).

 

hotplug and other problems

corrupting files in some cases

 

AHCIPortInjector.kext.zip

IOAHCIBlockStorageInjector.kext.zip

 

try it

dsdt.adrian95_02.zip

op reg in SBRG / fix in _PTS

 

Shutdown Work?

Link to comment
Share on other sites

hotplug and other problems

corrupting files in some cases

 

AHCIPortInjector.kext.zip

IOAHCIBlockStorageInjector.kext.zip

 

try it

dsdt.adrian95_02.zip

op reg in SBRG / fix in _PTS

 

Shutdown Work?

Man, I'd truly appreciate it if you gave some more detailed responses, I never get what you really want me to do!

In this case: I use that DSDT, add those kexts and check IOReg and do/check for what?

 

I also just noticed I lost audio with that DSDT (not the latest, the previous one, but since this latest one doesn't have a Device (HDEF either, I'm guessing I won't get audio either. I'm rebuilding caches and will reboot.

Link to comment
Share on other sites

Man, I'd truly appreciate it if you gave some more detailed responses, I never get what you really want me to do!

In this case: I use that DSDT, add those kexts and check IOReg and do/check for what?

 

use two kexts

ioAHCI --> fix orange icon

 

AHCIport..

MaLd0n_2011_02_17___s_01.52.21.png

in your case AHCI ICH10..

if runs natively

do not use this kext

 

my english sucks

sorry

 

I also just noticed I lost audio with that DSDT (not the latest, the previous one, but since this latest one doesn't have a Device (HDEF either, I'm guessing I won't get audio either. I'm rebuilding caches and will reboot.

 

what codec?

Link to comment
Share on other sites

use two kexts

ioAHCI --> fix orange icon

 

AHCIport..

post-557433-1297914776_thumb.png

in your case AHCI ICH10..

if runs natively

do not use this kext

 

my english sucks

sorry

 

 

 

what codec?

 

Yes, ICH10R runs natively, so I should remove AHCIport?

The codec is some weird variant of ALC889a, I've gotten it to work with most ALC889a edits thou.

Don't worry about the english, but you'll have to put up with me asking evereything twice :D

What I don't get is where all this is going related to sleep... that's the only real problem I was having.

Link to comment
Share on other sites

Yes, ICH10R runs natively, so I should remove AHCIport?

The codec is some weird variant of ALC889a, I've gotten it to work with most ALC889a edits thou.

Don't worry about the english, but you'll have to put up with me asking evereything twice :D

What I don't get is where all this is going related to sleep... that's the only real problem I was having.

 

which work natively you need not change

apply only the necessary

No sleep, no shutdown

:)

send me a kextstat, run on terminal

kextstat

 

Shutdown and restart works? without kext?

Link to comment
Share on other sites

which work natively you need not change

apply only the necessary

 

:D

send me a kextstat, run on terminal

kextstat

 

Shutdown and restart works? without kext?

If you read further on you will see that shutdown is working, and that the only issue remaning is really sleep.

kextsat (with your stuff):

 

Index Refs Address Size Wired Name (Version) <Linked Against>

1 65 0 0 0 com.apple.kpi.bsd (10.6.0)

2 4 0 0 0 com.apple.kpi.dsep (10.6.0)

3 98 0 0 0 com.apple.kpi.iokit (10.6.0)

4 104 0 0 0 com.apple.kpi.libkern (10.6.0)

5 86 0 0 0 com.apple.kpi.mach (10.6.0)

6 32 0 0 0 com.apple.kpi.private (10.6.0)

7 53 0 0 0 com.apple.kpi.unsupported (10.6.0)

8 0 0 0 0 com.apple.kernel.6.0 (7.9.9)

9 0 0 0 0 com.apple.kernel.bsd (7.9.9)

10 1 0 0 0 com.apple.kernel.iokit (7.9.9)

11 1 0 0 0 com.apple.kernel.libkern (7.9.9)

12 0 0 0 0 com.apple.kernel.mach (7.9.9)

13 11 0x77c0f000 0x4000 0x3000 com.apple.iokit.IOACPIFamily (1.3.0) <7 6 4 3>

14 24 0x77db0000 0x11000 0x10000 com.apple.iokit.IOPCIFamily (2.6) <7 5 4 3>

15 1 0x77e51000 0x42000 0x41000 com.apple.driver.AppleACPIPlatform (1.3.5) <14 13 7 6 5 4 3>

16 7 0x77bb4000 0x5000 0x4000 org.netkas.FakeSMC (3.1.0) <13 7 5 4 3>

17 0 0x77c01000 0x4000 0x3000 org.mozodojo.IntelCPUMonitor (1.0) <16 7 5 4 3>

18 0 0x77f0c000 0x10000 0xf000 org.usrsse2.NVClockX (1.0.0d1) <16 14 7 5 4 3>

19 4 0x77dad000 0x3000 0x2000 org.mozodojo.SuperIOFamily (1.0.0d1) <16 7 5 4 3>

20 0 0x77de4000 0x3000 0x2000 org.mozodojo.F718x (1) <19 16 7 5 4 3>

21 0 0x77e3d000 0x3000 0x2000 org.mozodojo.IT87x (1.0.0d1) <19 16 7 5 4 3>

22 0 0x77ee4000 0x3000 0x2000 org.slice.PC8739x (1) <19 16 7 5 4 3>

23 0 0x77edd000 0x4000 0x3000 org.mozodojo.W836x (1.0.0d1) <19 16 7 5 4 3>

24 0 0x77f43000 0x1e000 0x1d000 com.apple.driver.AppleIntelCPUPowerManagement (105.13.0) <7 6 5 4 3 1>

25 9 0x77f1c000 0x18000 0x17000 com.apple.iokit.IOStorageFamily (1.6.2) <7 6 5 4 3 1>

26 0 0x77e40000 0x11000 0x10000 com.apple.driver.DiskImages (289) <25 7 6 5 4 3 1>

27 0 0x780c6000 0x8000 0x7000 com.apple.nke.applicationfirewall (2.1.11) <7 6 5 4 3 1>

28 2 0x780bc000 0x3000 0x2000 com.apple.kext.AppleMatch (1.0.0d1) <4 1>

29 0 0x780ce000 0x5000 0x4000 com.apple.security.quarantine (0) <28 7 6 5 4 2 1>

30 0 0x780de000 0x8000 0x7000 com.apple.security.sandbox (1) <28 7 6 5 4 2 1>

31 0 0x780c2000 0x3000 0x2000 com.apple.security.TMSafetyNet (6) <7 6 5 4 2 1>

32 0 0x780bf000 0x3000 0x2000 com.apple.driver.AppleAPIC (1.4) <4 3>

33 0 0x780d3000 0x4000 0x3000 com.apple.driver.AppleSMBIOS (1.6) <7 4 3>

34 0 0x80d31000 0x6000 0x5000 com.apple.driver.AppleRTC (1.3.1) <13 5 4 3 1>

35 0 0x781fd000 0x3000 0x2000 com.apple.driver.AppleHPET (1.5) <13 7 5 4 3>

36 5 0x80dfe000 0x3c000 0x3b000 com.apple.iokit.IOHIDFamily (1.6.5) <7 6 5 4 3 1>

37 0 0x77efd000 0x4000 0x3000 com.apple.driver.AppleACPIButtons (1.3.5) <36 15 13 7 6 5 4 3 1>

38 1 0x77efa000 0x3000 0x2000 com.apple.driver.AppleEFIRuntime (1.4.0) <7 6 5 4 3>

39 10 0x80e6d000 0x34000 0x33000 com.apple.iokit.IOUSBFamily (4.1.7) <14 7 5 4 3 1>

40 0 0x80d8a000 0x10000 0xf000 com.apple.driver.AppleUSBUHCI (4.1.5) <39 14 7 5 4 3 1>

41 0 0x77ef2000 0x3000 0x2000 com.apple.driver.AppleIntelCPUPowerManagementClient (105.13.0) <7 6 5 4 3 1>

42 3 0x80d7b000 0x6000 0x5000 com.apple.iokit.IOAHCIFamily (2.0.4) <5 4 3 1>

43 0 0x80ecb000 0x14000 0x13000 com.apple.driver.AppleAHCIPort (2.1.5) <42 14 5 4 3 1>

44 0 0x80edf000 0x16000 0x15000 com.apple.driver.AppleUSBEHCI (4.1.7) <39 14 7 5 4 3 1>

45 0 0x80d81000 0x6000 0x5000 com.apple.driver.AppleEFINVRAM (1.4.0) <38 7 5 4 3>

46 4 0x80da4000 0x16000 0x15000 com.apple.iokit.IONetworkingFamily (1.9) <7 6 5 4 3 1>

47 0 0x80f2a000 0x21000 0x20000 com.lnx2mac.driver.RealtekRTL81xx (0.0.67) <46 14 5 4 3 1>

48 2 0x80fde000 0x43000 0x42000 com.apple.iokit.IOFireWireFamily (4.2.6) <5 4 3 1>

49 0 0x80ef5000 0x27000 0x26000 com.apple.driver.AppleFWOHCI (4.7.1) <48 14 7 6 5 4 3 1>

50 0 0x80f1c000 0x6000 0x5000 com.apple.driver.AppleRTL8169Ethernet (1.1) <46 14 5 4 3 1>

51 0 0x80fa5000 0x13000 0x12000 com.apple.iokit.IOAHCIBlockStorage (1.6.3) <42 25 5 4 3 1>

52 0 0x82146000 0x3000 0x2000 com.apple.driver.XsanFilter (402.1) <25 5 4 3 1>

53 3 0x82188000 0x1a000 0x19000 com.apple.iokit.IOSCSIArchitectureModelFamily (2.6.5) <5 4 3 1>

54 0 0x8213d000 0x9000 0x8000 com.apple.iokit.IOAHCISerialATAPI (1.2.5) <53 42 5 4 3 1>

55 3 0x8214f000 0x8000 0x7000 com.apple.iokit.IOCDStorageFamily (1.6) <25 5 4 3 1>

56 2 0x82157000 0x6000 0x5000 com.apple.iokit.IODVDStorageFamily (1.6) <55 25 5 4 3 1>

57 1 0x8215d000 0x5000 0x4000 com.apple.iokit.IOBDStorageFamily (1.6) <56 55 25 5 4 3 1>

58 0 0x8221d000 0x18000 0x17000 com.apple.iokit.IOSCSIMultimediaCommandsDevice (2.6.5) <57 56 55 53 25 5 4 3 1>

59 0 0x821eb000 0x7000 0x6000 com.apple.iokit.SCSITaskUserClient (2.6.5) <53 25 5 4 3 1>

60 0 0x82135000 0x2000 0x1000 com.apple.iokit.IOUSBUserClient (4.1.5) <39 7 5 4 3 1>

61 0 0x8230d000 0x12000 0x11000 com.apple.driver.AppleUSBHub (4.1.7) <39 5 4 3 1>

62 0 0x82185000 0x3000 0x2000 com.apple.driver.AppleFileSystemDriver (2.0) <25 4 3>

63 0 0x823bd000 0x6000 0x5000 com.apple.AppleFSCompression.AppleFSCompressionTypeZlib (1.0.0d1) <6 4 3 2 1>

64 0 0x823d6000 0x5000 0x4000 com.apple.BootCache (31) <7 6 5 4 3 1>

65 5 0x8249f000 0x3d000 0x3c000 com.apple.iokit.IOBluetoothFamily (2.3.8f7) <7 5 4 3 1>

66 1 0x8243e000 0xb000 0xa000 com.apple.driver.AppleUSBBluetoothHCIController (2.3.8f7) <65 39 7 5 4 3>

67 0 0x823db000 0x4000 0x3000 com.apple.driver.CSRUSBBluetoothHCIController (2.3.8f7) <66 65 39 5 4 3>

68 1 0x823ca000 0x4000 0x3000 com.apple.driver.AppleUSBComposite (3.9.0) <39 4 3 1>

69 0 0x8246c000 0x4000 0x3000 com.apple.driver.AppleUSBMergeNub (4.1.5) <68 39 4 3 1>

70 0 0x82461000 0x6000 0x5000 com.apple.iokit.IOUSBHIDDriver (4.1.5) <39 36 5 4 3 1>

71 1 0x82a66000 0x9000 0x8000 com.apple.driver.AppleMultitouchDriver (207.10) <36 7 6 5 4 3 1>

72 1 0x82a50000 0xd000 0xc000 com.apple.driver.IOBluetoothHIDDriver (2.3.8f7) <65 36 4 3>

73 0 0x82aa0000 0xa000 0x9000 com.apple.driver.AppleBluetoothMultitouch (54) <72 71 65 36 5 4 3>

74 1 0x82c6e000 0x60000 0x5f000 com.apple.filesystems.ntfs (3.3) <7 6 5 4 1>

75 0 0x82b35000 0xa000 0x9000 com.apple.filesystems.autofs (2.1.0) <7 6 5 4 3 1>

76 0 0x77d9f000 0x3000 0x2000 com.apple.driver.AppleLPC (1.4.12) <14 5 4 3>

77 0 0x77d98000 0x2000 0x1000 com.apple.driver.AppleSMBusPCI (1.0.8d0) <14 5 4 3>

78 2 0x77da2000 0xb000 0xa000 com.apple.driver.IOPlatformPluginFamily (4.5.0d5) <6 5 4 3>

79 2 0x82af9000 0xa000 0x9000 com.apple.driver.AppleSMC (3.1.0d3) <13 7 5 4 3>

80 0 0x82bac000 0x10000 0xf000 com.apple.driver.ACPI_SMC_PlatformPlugin (4.5.0d5) <79 78 14 13 7 6 5 4 3>

81 1 0x82aeb000 0x7000 0x6000 com.apple.iokit.IOHDAFamily (1.9.9f12) <5 4 3 1>

82 8 0x82b69000 0x22000 0x21000 com.apple.iokit.IOGraphicsFamily (2.2) <14 7 5 4 3>

83 0 0x82b8b000 0x18000 0x17000 com.apple.driver.AppleHDAController (1.9.9f12) <82 81 14 5 4 3 1>

84 10 0x82dbe000 0x2c000 0x2b000 com.apple.iokit.AppleProfileFamily (41) <14 7 6 5 4 3 1>

85 0 0x82ba3000 0x7000 0x6000 com.apple.driver.AppleIntelMeromProfile (19) <84 6 5 4 3>

86 0 0x82adb000 0x6000 0x5000 com.apple.driver.IOBluetoothBNEPDriver (2.3.8f7) <65 46 7 5 4 3 1>

87 0 0x82bc7000 0x9000 0x8000 com.apple.iokit.IOFireWireIP (2.0.3) <48 46 5 4 3 1>

88 3 0x82cce000 0xd000 0xc000 com.apple.iokit.IONDRVSupport (2.2) <82 14 7 5 4 3>

89 2 0x839eb000 0x2ee000 0x2ed000 com.apple.NVDAResman (6.2.6) <88 82 14 5 4 3 1>

90 0 0x84150000 0x415000 0x414000 com.apple.nvidia.nv50hal (6.2.6) <89 4 3>

91 1 0x80de9000 0x3000 0x2000 com.apple.iokit.IOSMBusFamily (1.1) <5 4 3>

92 0 0x80df2000 0x9000 0x8000 com.apple.driver.AppleSMBusController (1.0.8d0) <91 14 13 5 4 3>

93 1 0x82944000 0x4000 0x3000 com.apple.kext.OSvKernDSPLib (1.3) <5 4>

94 2 0x82d5b000 0x18000 0x17000 com.apple.iokit.IOAudioFamily (1.8.0fc1) <93 5 4 3 1>

95 0 0x82a61000 0x4000 0x3000 com.apple.driver.AudioIPCDriver (1.1.6) <94 5 4 3 1>

96 0 0x82d87000 0x8000 0x7000 com.apple.driver.AppleIntelNehalemProfile (11) <84 6 4 3>

97 0 0x83096000 0xb6000 0xb5000 com.apple.GeForce (6.2.6) <89 88 82 14 7 6 5 4 3 1>

98 0 0x82b29000 0x6000 0x5000 com.apple.Dont_Steal_Mac_OS_X (7.0.0) <79 7 4 3 1>

99 0 0x8216c000 0x7000 0x6000 com.apple.driver.AppleIntelPenrynProfile (17) <84 6 4 3>

100 0 0x82d73000 0x7000 0x6000 com.apple.driver.AppleMCCSControl (1.0.17) <82 14 7 5 4 3 1>

101 2 0x82e53000 0x9000 0x8000 com.apple.iokit.IOSerialFamily (10.0.3) <7 6 5 4 3 1>

102 0 0x82eb0000 0x9000 0x8000 com.apple.iokit.IOBluetoothSerialManager (2.3.8f7) <101 7 5 4 3 1>

103 0 0x82ad2000 0x5000 0x4000 com.apple.driver.AppleIntelYonahProfile (14) <84 6 4 3>

104 0 0x82b1a000 0x5000 0x4000 com.apple.driver.AppleUpstreamUserClient (3.4.5) <82 14 13 7 5 4 3 1>

105 0 0x82e9f000 0xb000 0xa000 com.apple.iokit.IOSurface (74.2) <7 5 4 3 1>

106 0 0x80dfb000 0x3000 0x2000 com.x86dev.driver.lspcidrv (1.0) <11 10>

107 0 0x77adb000 0x3000 0x2000 com.apple.driver.AppleProfileCallstackAction (20) <84 5 4 3 1>

108 0 0x77ae4000 0x5000 0x4000 com.apple.driver.AudioAUUC (1.13) <94 82 14 13 7 5 4 3 1>

109 0 0x77ad5000 0x3000 0x2000 com.apple.driver.AppleProfileKEventAction (10) <84 4 3 1>

110 0 0x82db2000 0xb000 0xa000 com.apple.driver.AGPM (100.12.19) <88 82 14 5 4 3>

111 0 0x82d4d000 0x9000 0x8000 com.apple.driver.AppleTyMCEDriver (1.0.2d2) <78 14 13 7 6 5 4 3 1>

112 0 0x77ad8000 0x3000 0x2000 com.apple.driver.AppleProfileRegisterStateAction (10) <84 4 3 1>

113 0 0x80de1000 0x3000 0x2000 com.apple.driver.AppleProfileThreadInfoAction (14) <84 6 4 3 1>

114 0 0x82174000 0x3000 0x2000 com.apple.driver.AppleProfileTimestampAction (10) <84 5 4 3 1>

115 0 0x80ddd000 0x3000 0x2000 com.apple.driver.AppleProfileReadCounterAction (17) <84 6 4 3>

116 0 0x82aaa000 0x4000 0x3000 com.apple.driver.InternalModemSupport (2.6.2) <101 39 7 5 4 3 1>

117 0 0x82d56000 0x5000 0x4000 com.apple.driver.AppleHWSensor (1.9.3d0) <5 4 3>

Link to comment
Share on other sites

If you read further on you will see that shutdown is working, and that the only issue remaning is really sleep.

Don't bite the hand that feeds. He's asking you because the changes he made to your DSDT can affect shutdown. Not because he can't read!

16 7 0x77bb4000 0x5000 0x4000 org.netkas.FakeSMC (3.1.0)

17 0 0x77c01000 0x4000 0x3000 org.mozodojo.IntelCPUMonitor (1.0)

18 0 0x77f0c000 0x10000 0xf000 org.usrsse2.NVClockX (1.0.0d1)

19 4 0x77dad000 0x3000 0x2000 org.mozodojo.SuperIOFamily (1.0.0d1)

20 0 0x77de4000 0x3000 0x2000 org.mozodojo.F718x (1)

21 0 0x77e3d000 0x3000 0x2000 org.mozodojo.IT87x (1.0.0d1)

22 0 0x77ee4000 0x3000 0x2000 org.slice.PC8739x (1)

23 0 0x77edd000 0x4000 0x3000 org.mozodojo.W836x (1.0.0d1)

What's with the carpet bombing? Don't install FakeSMC plugins for sensors that you don't have.

 

You can use HWMonitor (google it) on Windows to see which sensor chips your motherboard has.

Link to comment
Share on other sites

Don't bite the hand that feeds. He's asking you because the changes he made to your DSDT can affect shutdown. Not because he can't read!

;)

 

-------------------------------------------

this motherboard is very compatible

many patches he uses are not needed

the problem could be there, but really to no avail

 

@adrian95

use codebox

Link to comment
Share on other sites

@MaLd0n: sorry if I was rude man, I didn't mean to, and I've been having a hard time lately: I'm usually not in the best of moods.

@LatinMcGyver75, no, the logs don't say anything about sleep.

@Gringo Vermelho: I just installed SuperIO.kext (which has the kexts for all of those sensors, I don't know why they're being loded, as I think I only have an IT8720F, I'll check with HWMonitor). Should I delete the other plugins (supposing I check and do only have an IT8720F?).

 

Sorry I took so long to respond, It's been a crazy couple of days (tomorrow is my BD ;) , yay!?)

 

Edit 1

As far as shutdown goes, it seems to work fine with the latest DSDT MaLd0n supplied.

 

Edit 2

Thanks for introducing me to HWMonitor, I can see it's a great and very useful app.

It reports two "Hardware Monitors", one from my MB and one from the GPU (ITE IT87 and NVIDIA NVAPI respectively). It also gives me several SMB devices (what are these?). I'll attach the two output files so that you guys can look at them directly.

HWMonitor.txt

hwm_smbus.txt

Link to comment
Share on other sites

You should correct your signature now that shutdown is working.

Should I delete the other plugins (supposing I check and do only have an IT8720F?).

Yes, definitely. I'm not saying they can or will cause problems but it's good practice to eliminate unnecessary stuff when troubleshooting.

(HWMonitor) also gives me several SMB devices (what are these?).

Knock yourself out:

http://en.wikipedia.org/wiki/System_Management_Bus

http://en.wikipedia.org/wiki/I%C2%B2C

http://en.wikipedia.org/wiki/Low_Pin_Count

http://en.wikipedia.org/wiki/Super_I/O

Link to comment
Share on other sites

You should correct your signature now that shutdown is working.

 

Yes, definitely. I'm not saying they can or will cause problems but it's good practice to eliminate unnecessary stuff when troubleshooting.

 

Knock yourself out:

http://en.wikipedia.org/wiki/System_Management_Bus

http://en.wikipedia.org/wiki/I%C2%B2C

http://en.wikipedia.org/wiki/Low_Pin_Count

http://en.wikipedia.org/wiki/Super_I/O

Let's see if I understood:

SMBus (a subset of I2C) and LPC are buses, ie, standards for transmitting data. They usually connect low power devices (notably, super I/O chips, that monitor hardware and provide some other basic functions, such as power signals) to the motherboard.

Super I/O chips are chips that control a bunch of "low level" things in computers, and what interests us is power signaling (shutdown, restart, sleep).

 

So from what I can gather from this: what I need to get working well on my MB is the Super I/O chip, which is what would be preventing me from sleeping correctly.

Link to comment
Share on other sites

As far as I know, in our case, the SuperIO is only used for hardware monitoring via fakesmc and its plugins. I've never heard of anybody doing anything to any of the SMBus kernel extensions in order to get sleep working. Your kextstat output shows that they are loaded, which means you don't need this DSDT edit, or that you already have it: http://www.projectosx.com/forum/index.php?showtopic=685

 

Sleep not working can be caused by many things, video card drivers, USB, model identifier used, conflicting drivers or configuration settings etc etc.

 

The more hardware you can get working in a compatible, mac-like way, the better are your chances of working S3 sleep.

 

According to your kextstat output you have AppleLPC.kext loaded, which is a requirement for native CPU power management. S3 sleep is a power state (as is shut down, which is working for you now). This is a good start.

 

Here you can read about how to activate CPU power management with Chameleon 2.0 RC5:

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

 

I made this checklist a while back, it's not complete and some of the info is probably not 100% correct nor necessary. Anyway

http://www.projectosx.com/forum/index.php?...ost&p=10065

Link to comment
Share on other sites

As far as I know, in our case, the SuperIO is only used for hardware monitoring via fakesmc and its plugins. I've never heard of anybody doing anything to any of the SMBus kernel extensions in order to get sleep working. Your kextstat output shows that they are loaded, which means you don't need this DSDT edit, or that you already have it: http://www.projectosx.com/forum/index.php?showtopic=685

 

Sleep not working can be caused by many things, video card drivers, USB, model identifier used, conflicting drivers or configuration settings etc etc.

 

The more hardware you can get working in a compatible, mac-like way, the better are your chances of working S3 sleep.

 

According to your kextstat output you have AppleLPC.kext loaded, which is a requirement for native CPU power management. S3 sleep is a power state (as is shut down, which is working for you now). This is a good start.

 

Here you can read about how to activate CPU power management with Chameleon 2.0 RC5:

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

 

I made this checklist a while back, it's not complete and some of the info is probably not 100% correct nor necessary. Anyway

http://www.projectosx.com/forum/index.php?...ost&p=10065

Yeah, I was using that edit in my dsdt. I saw that it's also included in MaLd0n's DSDT, so I don't know if shutdown would work without that. With my "untouched" DSDT, I'm 99% sure it didn't.

 

As far as that checklist goes:

Yes, since I got GenerateCStates and GeneratePStates working, I have removed speedsteping info from my DSDT. So the only difference with the original is the removal of the Alias stuff from Scope (_PR).

All three kexts are loading.

I'm using the 10.6.6 vanilla kernel, and have an x58+i7.

I've tried with MacPro3,1 , 4,1 and 5,1. They all seem to work fine, but I get no sleep. What model identifier do you recommend? I've read mixed reviews about 4,1, info on 5,1 is scarce, 3,1 seems to be the standard. I haven't experimented with iMac identifiers.

Link to comment
Share on other sites

You can leave the CPU aliases in as well, it's not necessary to remove them when running Snow Leopard.

 

You should use either MacPro3,1 or a model identifier from a Mac that has a Nehalem Core ix CPU like yours.

 

Model identifier normally also affects video card power management via AppleGraphicsPowerManagement.kext. google/forum search for more info.

 

Go to the nvidia website and download and install the latest OS X drivers. Don't worry about video card model, the drivers are universal.

 

Try to find posts by other people with X58/ICH10 based boards and see what they have done to get S3 sleep working. All hacks are different but if there are special fixes for X58 that other people use, then you can use them too.

I can't offer any further advice other than this: Search and read until your eyes bleed. Then take a break and search and read some more.

Link to comment
Share on other sites

You can leave the CPU aliases in as well, it's not necessary to remove them when running Snow Leopard.

 

You should use either MacPro3,1 or a model identifier from a Mac that has a Nehalem Core ix CPU like yours.

 

Model identifier normally also affects video card power management via AppleGraphicsPowerManagement.kext. google/forum search for more info.

 

Go to the nvidia website and download and install the latest OS X drivers. Don't worry about video card model, the drivers are universal.

 

Try to find posts by other people with x58/ICH10 based boards and see what they have done to get S3 sleep working.

I can't offer any further advice.

I'll be making a new DSDT, with minimal edits.

 

Nvidia doesn't offer newer drivers for my GPU, but they do for the GTX 240 for example, should I try these? Nvidia page

 

I swear I've searched all I can, I've had this issue for some time now... but I haven't been able to find any fix that works (as you can see by my DSDT, I've tried a lot of them).

Link to comment
Share on other sites

I have to say this because you're doing it in almost every post - there is no reason to quote an entire post in your reply, especially when you're replying directly below it. It clutters up the forum and destroys readability.

And why make everybody read the same thing twice. Quoting is for quoting - like this:

Nvidia doesn't offer newer drivers for my GPU, but they do for the GTX 240 for example

:D

Read my post again, a little more carefully this time.

Link to comment
Share on other sites

Other than what I recommended already, I got nothing. Good luck.

Thanks for trying man, I've learnt quite a bit with your help.

Do you think it would be bad practice to re-post my issue on some other OSx86 forum, or would it be OK? I probably won't get answers anyways, and will have to live sleepless, but it can't hurt to try...

Link to comment
Share on other sites

 Share

×
×
  • Create New...