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 hotKoffy

  • Rank
    InsanelyMac Protégé
  1. ACPI Backlight Driver

    AppleBacklight.kext and ACPIBacklight.kext are both attaching to PNLF ACPI device, so only one can be running. My kext will win if it finds the good ACPI methods in the DSDT (_DOS, _BCL....) so no conflicts could occure. If you can use AppleBacklight.kext, my driver is not for you You skrew up injecting this property: "@0,AAPL,boot-display", Buffer (0x04) { 0x01, 0x00, 0x00, 0x00 }, It is supposed to be an array not a boolean. but ACPIBacklightDisplay.kext shall no longer be used !! I think you have an ATI graphics with a personnality showing your internal display as VGA instead of LVDS. The solution is to patch ATI personnality following: Editing custom personalities for ATI Radeon HD[45]xxx
  2. ACPI Backlight Driver

    try without this test in _BCM If (LGreaterEqual (OSFG, OSVT)) I think its a windows version test
  3. ACPI Backlight Driver

    You should check your dsdt battery _STA And ask 'gsly' for the sources. On the original driver _STA is used for battery state. I've no problem with sleep so I can only help with ideas. I've notice in some dsdt that there are two registers for setting the brightness in EC: one for AC and one for DC. I'm also surprise that the driver can be unloaded. once AppleBacklightDisplay find it, it retains it (because it use it) which prevents unloaded (which is painful for testing !). The only moment when the AppleBacklightDisplay is unloaded is when I plug an external display but a new instance is created immediately. It would be interesting to test the wake / sleep behavior with ioregisteryexplorer (with option to show terminated objects) open to see what's happening.
  4. ACPI Backlight Driver

    No, the drivers can't save anything. The sortage of the current value is made by DSDT in the PC CMOS NVRAM and so shall work in a multiboot environment. I think the first 2 entries in BCL shall be corrected. You can find explaination in the topic. Do you have made modifications on your DSDT related to backlight levels ? The level returned by BQC must exist in BCL. The drivers seek the battery driver to see if the AC plug is connected. On all IOreg I've read, this property exists. Which driver do you use for your battery ? I will test it. look at post 36
  5. Netbook hot key driver Asus Dell HP

    Maybe it because EisaId is missing. Nevertheless, the driver can't works. There is a new driver in linux 3.0.4 "asus-nb-wmi.c" matching your hardware. I will try to integrate it later.
  6. Netbook hot key driver Asus Dell HP

    Would have been simpler to put uppercase in your dsdt put an ioregisteryexplorer dump with the driver loaded, I want to see the properties exposed
  7. Netbook hot key driver Asus Dell HP

    Change also Name (_UID, "ATK") to Name (_UID, "ASUSWMI")
  8. ACPI Backlight Driver

    No the Nvidia has nothing to do with it. I think there is something OS specific in your DSDT. You have to understand how the DSDT behave depending on the value returned by _OSI or _OS. I think the best way is to follow windows 7 specificities If (_OSI ("Windows 2009")) { Store (OSW7, OSFG) } using If (_OSI ("Darwin")) { Store (OSW7, OSFG) }
  9. Howto: configure Lion to auto generate MKext

    Indeed I was having this trouble before I do the modification. Now its OK Do you have verified that the mkext is generated in /System/Library/Caches/com.apple.kext.caches/Startup/ ? if not, sudo touch /S*/L*/Ex* Do not put usekernelcache = yes in chameleon I'm using root HD and no kext in /E/E
  10. ACPI Backlight Driver

    try this Method (_BCM, 1, NotSerialized) { DBGR ("\n_BCM: ") DBGR (Arg0) Store (GCBL (Arg0), Local0) Subtract (0x0A, Local0, LBTN) DBGR ("\n LBTN = ") DBGR (LBTN) //^^^^SBRG.EC0.STBR () ^^^^SBRG.EC0.ECCB () }
  11. Howto: configure Lion to auto generate MKext

    Yes, kexd daemon will do it for you every time the directory /S/L/E is modified.
  12. Howto: configure Lion to auto generate MKext

    The generated mkext contains basic drivers needed for boot (not net-boot) so it is normal.
  13. ACPI Backlight Driver

    for BQC change Method (_BQC, 0, NotSerialized) { DBGR ("\n_BQC: ") DBGR (LBTN) Return (LBTN) } to Method (_BQC, 0, NotSerialized) { Store (LBTN, Local0) Store (BRTI, Local1) ShiftLeft (Local1, 0x04, Local1) Add (Local0, Local1, Local1) Store (DerefOf (Index (PWAC, Local1)), Local0) Return (Local0) } and verify than your embedded controller EC0 has the driver loaded
  14. ACPI Backlight Driver

    I've an idea: you have 3 times the methods _DOS _BCL... nested in 3 devices PEG1 PEG3 GFX0 I think all this objects are populated in the device tree even if only one is valid. So the driver takes the first it finds and it is not the good one. So no effect when you move the slider. Locate in ioreg on which device the graphics drivers is on and then put this on PNLF, changing in my example \_SB.PCI0.IXVE.IGPU.LCDD with the good paths. Device (PNLF) { Name (_HID, EisaId ("APP0002")) Name (_CID, "backlight") Name (_UID, 0x0A) Name (_STA, 0x0B) Method (_BCL, 0, NotSerialized) { return (\_SB.PCI0.IXVE.IGPU.LCDD._BCL()) } Method (_BCM, 1, NotSerialized) { \_SB.PCI0.IXVE.IGPU.LCDD._BCM(Arg0) } Method (_BQC, 0, NotSerialized) { return (\_SB.PCI0.IXVE.IGPU.LCDD._BQC()) } Method (_DOS, 1, NotSerialized) { \_SB.PCI0.IXVE.IGPU._DOS(Arg0) } }
  15. Howto: configure Lion to auto generate MKext

    Do you have verified that the mkext is generated in /System/Library/Caches/com.apple.kext.caches/Startup/ ? if not, sudo touch /S*/L*/Ex* Do not put usekernelcache = yes in chameleon