Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.


  • Content count

  • Joined

  • Last visited

About dtessier

  • Rank
    InsanelyMac Protégé
  1. USB 3.0 OSX Support By Caldigit

    Since he installed the driver on his Gigabyte X58A-UD3R, and it seems to have picked up the device properly, I would say the LaCie PCIe USB3 card is indeed NEC-based (the X58A-UD3R has a NEC uPD720200 on-board).
  2. Here's the information for my card. It's a PowerColor PCS+ HD5770, so I was surprised to see the subsystem listed as Hightech Information System... I'm using the Vervet fb by the way. 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Unknown device [1002:68b8] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Unknown device [1787:2288] -- 01:00.1 Audio device [0403]: ATI Technologies Inc Unknown device [1002:aa58] Subsystem: Hightech Information System Ltd. Unknown device [1787:aa58]
  3. ATi HD5000 BootLoader !

    If you ever see one in person, you will not soon forget it. The thing is HUGE, and weighs just over 90 pounds!
  4. I have a PowerColor PCS+ HD5770 1GB, and it mostly works fine with the Vervet framebuffer. The only part that does not work properly is when scrolling some web sites (most notably this one ) in Safari. I get long, perfectly vertical lines over portions of the screen, and sometimes the screen goes completely grey. If I keep scrolling, or pop dashboard in and out, eventually it comes back. Has anyone else ever encountered this problem? I've tried a bunch of other framebuffers, but no other ones work as well as Vervet. I've attached a zip file of the IOReg dump and a screenshot of System Profiler. EDIT: Of course I forgot to mention two things. I only have VGA monitors, but both DVI ports work fine with DVI2VGA adapters, either one at a time, or both at once. And in case it matters I have the following HW: Gigabyte P55M-UD2, i7-860, G.Skill ECO 2x2GB RAM, and the PowerColor card previously mentioned. Archive.zip
  5. Chameleon RC4 is out!

    Not trying to be antagonistic here, just an honest question. The data needs to be obtained on startup, either directly from SPD, or a "cached" version in a plist file. Is SPD/SMBus access really that much slower than reading and parsing the XML in the plist file? Or are you strictly worried about boot load size?
  6. I too get proper SpeedStep and TurboBoost without putting anything in my DSDT. I have been advocating this for a while, and I've even asked around to see if there was some advantage I was missing in putting all the code in the DSDT as opposed to simply relying on my built-in SSDT. I have confirmed it to work with MSR Tools (32-bit) and PStateChanger with VoodooPState.kext (64-bit) I'm using the P55M-UD2 (same as Tony).
  7. I have tried to use this, by performing the following steps: Install the full Chameleon RC4 package Copy your boot file to the root of my drive, since stage 2 is the only place your fake_efi.c change is used Add a string with my desired UUID for the SystemID key in /Extra/com.apple.Boot.plist Removed PlatformUUID from /Extra/Extensions, and rebuild /Extra/Extensions.mkext I still see a different UUID after each boot in the profiler under "Hardware UUID". Am I doing something wrong, or are SystemID and "Hardware UUID" actually two different things?
  8. I've got the 12X memory multiplier in the BIOS on my P55-UD2, and that's with BIOS F4.
  9. Yeah, I just realized I mixed up SpeedStep and Turbo. Oh well, at least the logic still applies, the only difference is the SpeedStep values in DSDT/SSDT will not affect it.
  10. I just caught up on this thread today, and i saw a lot of posts on overclocking, so I thought I'd attempt to clarify things up a bit. Since I have an i7-860, that's what I'll use but it works the same for the i5-750 as well. By default, the 860 runs at 2.80GHz, using a bus speed of 133.333MHz and a multiplier of 21. When speedstep is enabled, and the temperature of the chip allows it, it can automatically bump the multiplier to 22 (2.93GHz) when using 3 or 4 cores, up to 25 (3.33GHz) when using 2 cores, and up to 26 (3.46GHz) when only using 1 core. So let's say you're doing a 3.5GHz overclock by bumping the bus speed to 166.667MHz, which multiplied by the default 21 gives you 3.5GHz. If speedstep is enabled, the multiplier could be automatically changed on you, and it could be trying to go as high as 26 * 166.667 = 4.33GHz, which most likely will not work. So you have two choices: disable speedstep and go with 3.5GHz all the time on all cores, which uses more power and generates more heat. Or go with a lower base overclock, say a bus speed of 150MHz, which would give you a base speed of 150 * 21 = 3150, and a maximum potential speedstep of 150 * 26 = 3.9GHz, which might be doable depending on your cooling and what voltage you're willing to apply. Or lower the bus speed until you get something that's always stable. One last point I'd like to make: I don't know how the SSDT table is handled when you disable speedstep in the BIOS, but I believe it automatically modifies the SSDT to change the _PSS method to not use speedstep. If that's the case, there's a chance that if you disable speedstep in your BIOS but include the _PSS in your DSDT file instead, that speedstep may not be disabled as expected. Something to keep in mind. I hope this long-winded post will end up helping someone, otherwise it will have been a great waste of bandwidth! :mellow:
  11. I've just tried the tonymacx86's new fixed DSDT, and speedstep seems to work perfect (at least in 32-bit mode, I can't check in 64-bit as MSR Tools doesn't work). I've seen the speed drop down as far as 1.2 GHz (43.3%), and go as high as 3.1 GHz (111%). According to this article at Anandtech, it can go as high as 3.46GHz. Here are a few things I have observed: On my UD2, I do not need to put the speedstep data in the DSDT; it's already in the SSDT. Sleep works perfect in 32-bit, but in 64-bit it locks up on wakeup I get the "Please hold the power button to shut down" screen. As mentioned above, MSR Tools only works in 32-bit. Is there another tool I can use to monitor speedstep? If not, maybe I can try and find the source for MSR, and port it myself. When going to sleep once, I had left MSR Tools running. Upon wakeup, MSR Tools used up 100% CPU on one core, and I could not quit it or kill it using Activity Monitor. Actually, trying to kill it locked up the entire system. So it is probably not a good idea to leave MSR Tools running when going to sleep. Also, a quick question for Bansaku and/or rekursor. I have seen in some of your posts that you use MacPro 4,1 as the model. Is there any advantage to using that, as opposed to iMac 11,1? I'm just asking because the iMac uses the same chipset (P55) and CPUs (i5 750, i7 860)
  12. I just built a system based on the i7 860 last week. Look at my sig for the specs. This thread discusses installs on the P55-based motherboards, and this blog has some very good tutorials. I can't speak for the X58 side of things, but it's hard to imagine my install having been any easier or smoother.
  13. Hmmm, where did you get yours from? I downloaded a program called "aboutthismac.pkg", installed it, but I cannot find an application to run and mine still says "Quad-Core Intel Xeon".
  14. I just wanted to repost a small part of the dual-boot guide here, since it bit me when I was installing SL, and I thought it might help others as well. My USB flash drive is considered a hard drive by the BIOS, so this needs to be done in order to ensure booting from it. Go to CMOS Setup Utility and choose Advanced BIOS Features. Select Hard Disk Boot Priority. Move your Chameleon USB drive to top of list.
  15. This post shows the fix required for Chameleon, and it seems very simple, so i assume we will see a fixed PC-EFI soon, if not directly from netkas, then a patched version from someone else.