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 mnorthern

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
  • Location
    London, United Kingdom
  1. [GUIDE] 1st Generation Intel HD Graphics QE/CI

    did anyone get HDMI out working?
  2. Thanks jerrywilborn, i will add the link to your finding to the main post
  3. AppleIntelHDGraphicsFB fixed (SL 10.6.8)

    Does anyone have any of the following problems... Take a picture that's big but not too big (say 1280 x 1024) and open it in Preview app. Try making color adjustments through Adjust Colour. I am suffering terrible lag with simple stuff like Highlights and Shadows. And if I try to adjust Sharpness to make it look softer, the whole picture disappears. Is this normal ? Also, do I understand correctly.. to enable the shell screen saver, I need to update to 10.8.3 ?
  4. Hello ! I am still here I am trying to do some work on enabling the HDMI out. I am also looking at some people's DSDT's. So this is actually a note to everyone: If I haven't answered your questions yet, please send me a private message :wink2:
  5. Realtek WLAN Client Utility Facelift

    Thanks that's amazing! I'm gonna play with it too
  6. Realtek WLAN Client Utility Facelift

    Thanks it looks good! Can you please tell us how you did it (what steps)? Did you have to decompile the original application? I am just starting with XCode and any pointers would be useful Thanks!!
  7. Felix Chan, can you add the following code to the end of your _WAK method and tell me what happens? Notify (\_SB.PCI0.VID.LCD0, 0x86) Notify (\_SB.PCI0.PEG.VID.LCD0, 0x86) Store (0xFF, \BRLV) \_SB.PCI0.LPC.EC.BRNS () Calmesal I think I know what you could try.. Can you make a backup of your ACPI BACKLIGHT kext, then copy the original kext to your desktop, show package contents, change the 'BQC use index' property in the Info.plist file to the opposite of whatever it is saying now, then reinstall using kext wizard, and restart. Let me know if anything changed and if you are still getting those messages in your log, thanks EVERYONE, one more thing i forgot to mention You will need the following properties to be injected into your screen's properties. Either via Natit or DSDT (in your GFX0/VID0/graphics device, find or create Method (_DSM, 4, NotSerialized) and inside it Store (Package ( ) { X }, Local0 ) then call DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) where X is the code below: "AAPL,BacklightRestore", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "AAPL,HasPanel", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "AAPL,Haslid", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "AAPL,backlight-control", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "@0,backlight-control", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "@0,AAPL,boot-display", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, "@0,built-in", Buffer () { One },
  8. AppleIntelHDGraphicsFB fixed (SL 10.6.8)

    I don't think it's possible to make an artificial generic EDID because timings are different for different panels! So are you saying Windows creates an EDID for you? Can you not inject that one?
  9. Possibly, but on the other hand, the ACPI specification says http://www.acpi.info...PIspec-2-0c.pdf "_WAK: Power management control method run once system is awakened." "7.3.5 \_WAK (System Wake) After the system wakes from a sleeping state, it will invoke the \_WAK method and pass the sleeping state value that has ended. This operation occurs asynchronously with other driver notifications in the system and is not the first action to be taken when the system wakes" whats going on lol
  10. I have read through all the linux drivers + Intel documentation and this should be the (nearly) complete list of registers you need to experiment with. Since people's laptops are so different, it's difficult for me to do this remotely The procedure should be: Use RW-everything to note down the value in the register Try defining that register using Operation Regions and storing its correct value in your _WAK method in your DSDT The following are related to the PCH (south display) controllers registers ending in C7200, C7204, C7208, C720C C7210 -- should be saved and then restored on wake up The following are related to the display port and power-related registers ending in E1180, C6014, C6018, C6040 The following are strictly backlight related registers ending in 48250, 48254, c8250, c8254 The following is a Legacy Backlight Register. It is possible that your laptop uses legacy mode to set brightness. This register is not memory mapped. Therefore it is not in BAR0 (BAR1). Instead, it is directly in the PCI configuration space. It is on the device 0:2:0 on the PCI, at the offset 0xF4 (bits 0 to 7) By writing 0xFF to that location, you will achieve max brightness if legacy mode is enabled. Please let me know your findings. Yes what you're forgetting is that you're defining the same thing twice! (Look at your third screenshot) Your BRIT region is the same as your BRI4 region and your LEVL field is at the exactly same location as your LEVX The same problem is with BRI2 being in the same location as BRI3 and therefore LEV2=LEVW, so it doesn't make sense to define thing twice You should define a different region (you can name them BRI5, BRI6 etc) and a different field in that region (LEV3, LEV4 etc) and then make them to point to different registers (E1180, 48250, C6018, etc etc) and then store different values in them depending on your system's values (eg. from RW-everything) Update: i STRONGLY suspect that if you write Zero (0x00000000) to your BLC_PWM_CPU_CTL2 (this is in BAR0 at offset 0x00048250) then you should be able to manipulate the brightness by writing to the LBB (Legacy Brightness) register (which is not memory mapped therefore not in BAR0 but instead on the device 0:2:0 on the PCI, at the offset 0xF4 ), so that by writing 0xFF to it you should be able to enable the backlight without having to manipulate all those other registers... the downside would be, you lose all the OS X brightness sliders and buttons unless you hack them somehow I am trying to learn how to write drivers so that maybe in a few weeks time I will be able to write a kext patch or something, this is a really cool hobby (not advisable if you have a girlfriend/boyfriend) Question: Could someone confirm that a _WAK method is guaranteed to be called on computer's wake up from sleep? If it's not guaranteed to be called, then we may be wasting time, because it's simply not called on some people's computers, and they need a kext instead of a DSDT patch
  11. AppleIntelHDGraphicsFB fixed (SL 10.6.8)

    Pentothal, maybe what I say will be useful , maybe not I was playing with my IOPlatformPluginFamily.kext and changed it so that it loaded without its component ACPI_SMC_PlatformPlugin. This was a bad idea, and I ended up seeing exactly what you saw in your second screenshot. I got a grey screen, and then the computer ended up overheating and turned off. Which leads me to suspect that the framebuffer will not work if CPU power states are not working properly So I would suggest you make sure your power kexts are working fine (IOPlatformPluginFamily.kext must be untouched from original, also check FakeSMC and other power plugins), check your SSDT, if you dont have one then try to generate one, then enable all P states C states and C2-C4 states. Maybe the framebuffer doesnt have enough power to load or something.. just my theory
  12. AppleIntelHDGraphicsFB fixed (SL 10.6.8)

    Well coil whine is "normal" if there is too much power load on coils, i.e. bad power management And i'm pretty sure its not my HDD cos i dont have a HDD I do use SSDT though In early macbooks, the coil noise was present and could be removed by a work around by disabling C4 state, but that decreased battery life so it was never an ideal workaround. People made apps such as ShhMBP to remove the noise, but all those apps had side effects. I wonder if its worth trying those apps out are you saying using a dual link fb instead of single link could possibly help ?
  13. Edit: Does anyone know how difficult is it to write a program that dumps some arbitrary memory locations (like our graphics MMIO registers) on wake up from sleep? This would be so extremely useful for debugging for people who can't enable their backlight
  14. I have a lot of DSDT's too look at so sorry for any delays guys, I will try to get them sorted as soon as i can In the meantime, If anyone wants to do their own experimenting with different Operation Regions, this document gives you the registers to look at (search for Backlight) http://www.x.org/doc...3_Part2_BJS.pdf In that document, if they say there is a register at 48250h, it means take your bar value and make it to look like 0xB0048250, and use RW-everything for seeing what this value looks like, and then try using DSDT to write these values to Operation Regions Also try googling for the source code for Linux intel i915 drivers, especially Ironlake patches to those drivers, they're very educational
  15. AppleIntelHDGraphicsFB fixed (SL 10.6.8)

    I have the same problem! I wouldn't have noticed if you didn't say. Shell doesn't work at all. Also, my graphics are really "loud" under OS X. Things like scrolling or editing pictures generate this funny squealing noise (coil whine). I don't have this under Windows.. any ideas anyone