Jump to content

verteks

Members
  • Content count

    13
  • Joined

  • Last visited

About verteks

  • Rank
    InsanelyMac Protégé
  1. AppleIntelHDGraphicsFB fixed (SL 10.6.8)

    alexanderq: You need to edit the os-info. Editing os-info: If you are using MBP6,1 smbios the offset is 0x00012644, otherwise it is 0x000126B4. Set the byte at that offset to: 0x01 for LVDS, 0x04 for VGA, 0x10 for DisplayPort. These values can be ORed to get multiple outputs.
  2. AppleIntelHDGraphicsFB fixed (SL 10.6.8)

    alexanderq: HDMI is not supported, the only supported ports are LVDS, VGA and DisplayPort. GhostRaider: Does it freeze with a spinning wheel? I don't think it has anything to do with os-info, because it does work without AppleIntelHDGraphics.kext. Try this instead: In the Info.pllist of the FB kext, there are properties like FBCompression, Watermarks, etc... Set them all to 0. If it doesn't work, please do a reg dump from Linux. pentothal: Do what GhostRaider did, try removing AppleIntelHDGraphics.kext. iWin32: Don't use the Resolution module. fmac: It won't work for you, your laptop is connected through eDP. PEOPLE WHO GET A BLACK SCREEN: This means that your laptop is connected through eDP, which is not supported. There is no fix for this. I'll update my first post once I figure out the freezing problem.
  3. AppleIntelHDGraphicsFB fixed (SL 10.6.8)

    Apart from using the Resolution module, there is no alternative.
  4. AppleIntelHDGraphicsFB fixed (SL 10.6.8)

    voidRunner: Your laptop's panel is connected through eDP, not through LVDS, and eDP is NOT supported. Sorry, there is nothing I can do for you.
  5. AppleIntelHDGraphicsFB fixed (SL 10.6.8)

    voidRunner: The one I'm using only works in 32 bit mode, and it's for Snow Leopard. You got a black screen, right? I need you to do a reg dump from Linux.
  6. AppleIntelHDGraphicsFB fixed (SL 10.6.8)

    I am using MacBookPro6,1, but I've applied a patch to the kext I'm using. The ones I've posted here do not have this patch applied. The kext uses a different os-info structure depending on the model name. The 4th byte of the os-info structure contains the ORed value of the connectors (0x01 = LVDS, 0x04 = VGA, 0x10 = DisplayPort). The MBP6,1 and MBP6,2 os-info has the value 0x11, which means LVDS + DisplayPort. I think if you don't have a monitor attached to DisplayPort, it may cause it to hang. See if this one fixes the pixelated image. AppleIntelHDGraphicsFB_ML_SingleLink.zip
  7. AppleIntelHDGraphicsFB fixed (SL 10.6.8)

    My internet connection really sucks, it goes down a lot, so I may not be able to reply. I have a few suggestions: - Don't use Natit or Resolution.dylib. - Make sure you don't have "AAPL00,DualLink" defined in your DSDT. - Don't use MacBookPro6,1 or MacBookPro6,2 smbios. As for the pixelated image, I have no idea, it looks normal on my laptop. Are you using your monitor's native res?
  8. AppleIntelHDGraphicsFB fixed (SL 10.6.8)

    OK, here they are, for Mountain Lion. pentothal: use the SingleLink version. AppleIntelHDGraphicsFB_ML_Fixed.zip
  9. AppleIntelHDGraphicsFB fixed (SL 10.6.8)

    I can't upload them, I have a {censored} connection. I have patched both 32 and 64 bit versions. You could upload the one from ML and I'll try to patch it (if it's not too different.)
  10. AppleIntelHDGraphicsFB fixed (SL 10.6.8)

    It didn't get attached! I've uploaded both here: http://www.fileconvoy.com/dfl.php?id=g2a922fb2d672c917999239550b57025242d1a01d2 pentothal: Well, I can't guarantee it working on ML, I only have SL.
  11. AppleIntelHDGraphicsFB fixed (SL 10.6.8)

    pentothal: Are you using Mountain Lion? Are you sure it is Intel HD Graphics 1st gen (Ironlake)? Do you have anything in your kernel log? Your registers look fine (link width X1), but you have some additional registers that don't exist on Ironlake. I have attached the DualLink version here, I hope this works.
  12. AppleIntelHDGraphicsFB fixed (SL 10.6.8)

    I have fixed the artifacts now, it works perfectly now. People who got a black screen: If you have Linux, I want you to do a register dump using 'intel_reg_dumper' command. The problem was in the TrainFDI function. It sets the FDI_RXA_CTL and FDI_TXA_CTL registers using link width X4, but doing a reg dump from Linux, I found out that it should be X1. Now, I don't know if X1 works for DualLink, this might explain why some people got a black screen. For some reason, I can't attach two files. WTF?EDIT: WTF? I tried editing and attaching but it didn't work. AppleIntelHDGraphicsFB_SingleLink.zip
  13. Using a resolution higher than 1024x768 produces artifacts, so I have to look into it a bit more. Also, shutdown/reboot using a higher resolution causes a kernel panic. Use the DualLink version if your monitor supports a resolution higher than 1366x768. I have only tested it on a laptop, so I don't know if it works on an external monitor. UPDATE: I've made a commandline tool for patching, so you can try different options, you can also choose the output (LVDS, VGA, DP). Please, carefully read the included README file before using. THE FOLLOWING ARE NOT NECESSARY: - "GraphicsEnabler" boot option - "Graphics Mode" boot option - Natit.kext - Resolution.dylib Also, it does not matter which smbios.plist you are using. DO NOT MIX DIFFERENT KEXTS FROM DIFFERENT VERSIONS OF OS X! AppleIntelHDGraphicsFB is responsible for setting up the framebuffer, thus providing the ability to switch resolutions. The other AppleIntelHDGraphics* kexts provide hardware acceleration (QE/CI/OpenGL/Video playback). So, if using the FB kext on it's own works (switching resolutions but no QE/CI), while using it with the others does not, means there's an incompatibility between the kexts you are using. Please use this tool instead of the kexts I've uploaded here. AppleIntelHDGraphicsFB_SingleLink.zip hdgraphics_patcher.zip
×