Jump to content

type40

Members
  • Content count

    5
  • Joined

  • Last visited

About type40

  • Rank
    InsanelyMac Protégé
  1. Hello all, I have a Sandy Bridge set-up with i5 2500 on Gigabyte GA-H67MA-D2H-B3 and minimal graphics with nvidia 8400GS. Installation is mostly working using clover as bootloader but I have a remaining power management problem. I am using SSDT generated by the usual script, ssdtPRGen.sh (with no errors upon running it) and DSDT from Tonymac repository for my board. I use DropOEM option in clover (to allow SSDT to work) and haven't told clover to generate p-states or c-states itself. Using the imac12,2 system definition (one of those recommended for Sandy Bridge) I get only two cpu states recognised in HWmonitor but intel power gadget seems to recognise more and change about as normal in terms of clock speed. Using macpro3,1 system definition I get more lower CPU states it seems but still works ok.. the problem is that temps are 5-6 degrees higher than with Snow Leopard at idle and HWmonitor displays Vcore of 1.07 all the time.. Now given HWmonitor's not displaying my clock states properly I can't be sure but I am guessing that Vcore being stuck there may be the reason. (It should be able to drop to 0.89 or so at idle I believe. So my questions are: 1. Where do I go from here to diagnose my problem? 2. I have seen people patch system definitions as these seem to affect power management - some people use macmini sysdefs for sandy bridge but I can't boot - getting stuck at video initialisation so does anyone know how to patch sysdefs or associated files in Mavericks to allow proper CPU power management? 3. If you can suggest any tricks to get my system to boot with macmini sysdef I'm all ears. (This might be a shortcut and achieve the goal without knowing what we're doing!) All the best from Australia and thank you in advance!
  2. Yes, I'm in the same boat with broken speedstep despite nice SSDT and DSDT in mavericks. Is there any way to fix this these days? Any pointers gratefully accepted!
  3. Clover General discussion

    pop sound can be power saving of Realtek audio chipset.. no fix as yet (well not if you plan on using vanilla kexts - you can use other sound kexts like voodooHDA too).. only workaround with vanilla is with pop buster plist. google for details. does it play normal sounds ok (apart from beginning with a pop if left for more than a minute? Anyone know why starting up with attached USB drives (all WD in my case) leaves me at a cursor before the clover GUI for two minutes? I know it may be drive related because the motherboard (an H67 Gigabyte) will do it when I enable USB storage too.
  4. Clover General discussion

    Hello all. 8) I wonder if anyone might know how to disable scanning of the attached usb drives for clover since when i have a couple of WD externals connected I have a long delay with a white underscore cursor at top left of the screen prior to the arrival of the clover GUI. When I don't have them connected it's nice and fast. Since I'd like to have them connected and it'd be nice if I didn't have to wait for 3 or 4 minutes for my pc to get to the clover GUI I wonder if any of you chaps might have a hint as to boot options etc? I have heard "external" flag mentioned.. and people talk about EFI commands too but I can't find anything relating. I can't see anything in the config.plist but I've heard something along the lines of "fast" as a boot flag might work too. Any suggestions appreciated. (yes, I know.. be nice.. I'm a clover virgin!) 8p
  5. Raid0 Updater

    G'day All, I have an unusual situation I think - I have two helper partitions on each raid volume like this: /dev/disk1 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *2.0 TB disk1 1: EFI 209.7 MB disk1s1 2: Apple_RAID 250.0 GB disk1s2 3: Apple_Boot Boot OSX 134.2 MB disk1s3 4: Apple_RAID 1.7 TB disk1s4 5: Apple_Boot Boot OSX 134.2 MB disk1s5 ... /dev/disk3 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *2.0 TB disk3 1: EFI 209.7 MB disk3s1 2: Apple_RAID 250.0 GB disk3s2 3: Apple_Boot Boot OSX 134.2 MB disk3s3 4: Apple_RAID 1.7 TB disk3s4 5: Apple_Boot Boot OSX 134.2 MB disk3s5 I tried twice to create the volumes and Diskutil did it both times.. when I messed with it once (though I can recall which of them I removed) it broke the raid volume.. anyhow.. Your script finds the two helper partitons on the first volume and then misses the ones on the second.. Is there a way to make it only work on helper partitions that are hd(x,3)? Or do you know maybe why I have ended up with two per disk since I haven't seen anyone else with them... Kind regards, Trevor from Australia
×