Jump to content

426 posts in this topic

Recommended Posts

Hi Slice

 

So are you saying a dmidecode dump from a system booted with Clover with SMBIOS v2.6 and newer would have the UUID in the byte order as the specification and not as my MacBook Pro?

Hmmm.... I have to follow Apple's rule to be sure to see UUID in System Profiler and in diskutility the same as written in ascii. But I don't know why we need to see SmUUID.

Share this post


Link to post
Share on other sites
Advertisement

Hello man,

 

Did you also compare your 'Hardware UUID' from system_profiler with 'IOPlatformUUID' from ioreg?

Look the (officially) way they wrote & read that value? Is that looks identical for you?

Sorry, I choose 'IOPlatformUUID' as an example here because I dont have mac & cant found references how Apple display the (system-id) value in their way without any 3rd party :)

system_profiler SPHardwareDataType | awk '/UUID/ { print $3; }'
ioreg -rd1 -c IOPlatformExpertDevice | awk '/IOPlatformUUID/ { split($0, line, "\""); printf("%s\n", line[4]); }'

** My 'IOPlatformUUID' was auto generated by OS (because I didnt inject em / store fixed value with boot manager).

** I wont force you to update current dmidecode, please take it as reference :)

 
Yes. All other values checked and are correct. It's just the system-id which is incorrectly shown in cavaliercoder's dmidecode due to Apple not conforming to the SMBIOS spec.
 
ioreg system-id = DMI type 1 -> UUID
Your IOPlatformUUID is generated by the OS using the ioreg system-id.
 
That can be overridden by using one of:
Clover's SMBIOS/SMUUID, OZ SMBIOS/HardwareSignature, Chameleon's SMBIOS.plist/SMSystemUUID

Hmmm.... I have to follow Apple's rule to be sure to see UUID in System Profiler and in diskutility the same as written in ascii. But I don't know why we need to see SmUUID.

Diskuility? what's that to do with the output from dmidecode?

As far as I see here the values when booted using Clover are fine, but I don't have a SMBIOS version greater that 2.4 to check with to be sure, other than using Clover on my MacBook Pro.

Share this post


Link to post
Share on other sites
ioreg system-id = DMI type 1 -> UUID

Your IOPlatformUUID is generated by the OS using the ioreg system-id.

 

Exactly.

 

In fact, the current v2.12b in DarwinDumper shows better explanation of some information

 

Well said, showing known Apple tables is a plus.

Share this post


Link to post
Share on other sites

DarwinDumper has gone a while without any updates so I've pushed out v3.0.4.

 

Changes:

- Revised parsing of getcodecid result.
- Added Pike R. Alpha's' AppleIntelInfo.kext v2.9.
- Dump diskutil list unconditionally when running a disk scan.
- Include APFS and CoreStorage dumps when performing diskutil list.
- Added Pike R. Alpha's' lzvn tool for listing of prelinked kexts.
- Move kext dump out of section requiring elevated privileges.
- Limit kernel message log dump to 512KB.
- Limit disassembled ATI rom file to 1MB.
- Update Pike R. Alpha's' csrstat v1.8 for SIP with extended bits.
 
Edit: Oops forgot to add fix for case-sensitive file systems by Derek Zhu.
 
Previous versions should notify of the update, but otherwise here's a download link:
Edited by blackosx

Share this post


Link to post
Share on other sites

Recent versions of macOS started to download firmware.scap files.

Do the darwindumper takes the fresh datum (acpi, smc, ...) if supplied by firmware.scap?

Real mac assumed.

Share this post


Link to post
Share on other sites
Good evening everyone, like everyone else I was interested in the Hardware-Id "UUID "System Profiler" Utility I learned with the help of all that we could modify the UUID by modifying or creating the key" SMsystemid " in the "smbios.plist", but that the UUID injected by the key will never be the System Profiler's UUID Hardware-id, but that it will still be modified by UUID of key in "smbios.plist". At the boot there is application of a matrix or a hash, and I was able to find in the kernel the hash function SHA1 which is applied to the UUID of "system-id", a function of hash SHA1 which transforms this UUID in another UUID This transformed UUID is the one that appears in the System Profiler Utility and becomes the official UUID of your hardware (Imac, MacBook, MacPRO, Mac Mini) I found the answer to my question "Why?" is different from the hardware ID? "

below hardware-d uuid
ioreg -l -p IODeviceTree | grep \ "IOPlatformUUID \"

below "system-d" UUID
ioreg -l -p IODeviceTree | grep \ "system-id \"
it is with this one that we create the other (harware-id) after SHA1 hash
 
 
 
 
 
 
 
 

Share this post


Link to post
Share on other sites

I know this since Clover first release. The rule is follow

1. If we want determine UUID exactly same as in System Profiler then we have to set

                <key>CustomUUID</key>

           <string>511CE200-1000-4000-9999-010203040506</string>

and 

<key>InjectSystemID</key>

<false/>

 

2. If we want UUID same as with Chameleon then we took the digits from ioreg

IODeviceTree:/ef/platform=>system-id

use it as CustomUUID and set InjectSystemID=true

Share this post


Link to post
Share on other sites
For my part, I especially wanted to understand and find how a UUID we came to another UUID just by the boot and I found the answer in the kernel obviously.
Below is the SHA1 hash applied by the kernel to create the official UUID of Hardware-id
"
     SHA1_CTX context;

     const uuid_t space = {0x2A, 0x06, 0x19, 0x90, 0xD3, 0x8D, 0x44, 0x40, 0xA1, 0x39, 0xC4, 0x97, 0x70, 0x37, 0x65, 0xAC};
    
SHA1Init (& context);
     SHA1Update (& Context, space, sizeof (space));
     SHA1Update (& context, uuid, 16);
     SHA1Final (uuid, & context);
     uuid [6] = (uuid [6] & 0x0F) | 0x50;
     uuid [8] = (uuid [8] & 0x3F) | 0x80;

"
I prefer using Enoch to boot, and if I have to modify the UUID, I do it with smbios.plist, SMsystemid, with Clover it works very well too.
Edited by deek5

Share this post


Link to post
Share on other sites

As we know Apple makes 32bit platform obsolete, so we need to convert some tools in 64bit

here are all tools that still has no 64bit support (except nvram, this I was able to compile in 64bit from @blackosx repo from bitbucket)

208164223_Bildschirmfoto2018-06-20um01_59_54.png.32db09de65dd0d656854515aa63b996e.png

 

Has anyone source code for other tools?

 

Share this post


Link to post
Share on other sites

hmmm.. thanks for the note.

 

I know AppleIntelInfo used to 'sometimes' cause a system freeze, especially on older Sandy Bridge CPU's but Pike's last update(s) fixed that. But as we know Pike's gone and no longer working on it so it's good to know that headkaze has picked it up. I wonder if the crashes are specific to 10.14 or just with specific CPUs?

 

I could change DarwinDumper to NOT run AppleIntelInfo when selecting the CPU dump?

Share this post


Link to post
Share on other sites

Yes, it is very dangerous. I catch the reboot on IvyBridge under 10.13.6.

I may propose that reading MSR requires CPU-dependency. We can't read all MSR from all CPU. But I am not sure in AppleIntelInfo details.

Share this post


Link to post
Share on other sites

Hi @blackosx

I have i9-9980XE

If I run DarwinDumper getting panic when get CPU Information.

machdep.cpu.brand_string: Intel(R) Core(TM) i9-9980XE CPU @ 3.00GHz

Share this post


Link to post
Share on other sites
8 hours ago, nmano said:

Hi @blackosx

I have i9-9980XE

If I run DarwinDumper getting panic when get CPU Information.

machdep.cpu.brand_string: Intel(R) Core(TM) i9-9980XE CPU @ 3.00GHz

Not only this CPU

 

Share this post


Link to post
Share on other sites
On 1/18/2019 at 5:44 PM, Slice said:

Thanks Slice.

 

On 1/31/2019 at 9:36 PM, nmano said:

Hi @blackosx

I have i9-9980XE

If I run DarwinDumper getting panic when get CPU Information.

machdep.cpu.brand_string: Intel(R) Core(TM) i9-9980XE CPU @ 3.00GHz

 

Yeah. Slice mentioned the issue also.

When I get time I'll update DD to not include appleIntelInfo by default when running the CPU info dump.

Share this post


Link to post
Share on other sites
14 minutes ago, blackosx said:

Thanks Slice.

 

 

Yeah. Slice mentioned the issue also.

When I get time I'll update DD to not include appleIntelInfo by default when running the CPU info dump.

Thanks @blackosx

Share this post


Link to post
Share on other sites

Hi @blackosx thank you for your recent update of DarwinDumper, just to tell you that the URL as source for SMC_util3 is probably dead :( as ProjectOSX has been silent for long time, as far as I know.

http://www.projectosx.com/forum/index.php?s=&showtopic=2447&view=findpost&p=23230

Thank you.

Edited by MacKonsti

Share this post


Link to post
Share on other sites

@blackosx

Sorry for intervention I want to present the DarwinDumper with follow changes

- exclude Pike R. Alpha's' AppleIntelInfo.kext v2.9. as it crashes on most CPU

- replace dmidecode by acidanthera version with more information

- replace gfxutil by joevt version https://github.com/joevt/gfxutil

- latest iasl version

- latest smcutil version

 

For users wanted to share their dumps I have to recommend:

- exclude BIOS dump as it very large

- exclude HTML report as it very large and contain no new information

- make dump private. You will not do this if you save the dump for own use

- archive as lzma. It is like 7z and create very compact archive. But there may be problems to unpack in Windows. More universal to archive as ZIP.

DarwinDumper-305.app.zip

Share this post


Link to post
Share on other sites

Sorry, I forgot to exclude AppleIntelInfo

0xffffff91197fbec0 : 0xffffff80003ef715 
0xffffff91197fbf40 : 0xffffff80003ef2b5 
0xffffff91197fbfa0 : 0xffffff800035d0ce 
      Kernel Extensions in backtrace:
         com.pikeralpha.driver.AppleIntelInfo(2.9)[319606A5-8247-37F6-91F5-79DFF4ACA558]@0xffffff7f849ff000->0xffffff7f84a15fff

It is here

/DarwinDumper.app/Contents/Resources/public/drivers/AppleIntelInfo.kext

Move it to trash!

Share this post


Link to post
Share on other sites
On 6/4/2013 at 5:28 PM, Andy Vandijck said:

 

Sources are included.

Enjoy ;)

RadeonPCI_AnV_Dong.zip

 

How to build it for new macOS?

(kernel) kxld[com.dong.driver.RadeonPCI]: The following symbols are unresolved for this kext:
(kernel) kxld[com.dong.driver.RadeonPCI]:     __ZN11IOPCIDevice20extendedConfigRead32Ey
(kernel) Can't load kext com.dong.driver.RadeonPCI - link failed.

Thanks!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Rohan20
      Opencore is running really really slow on Catalina 10.15.4. So It was running perfectly before I put the ssdt-pnlf for enabling Brightness control. it is running really slow and I verified my config with the sanity checker and its all correct. can someone please help. I am attaching my oc folder.

       
      https://www.dropbox.com/s/drkek0eaz19ina5/OC.zip?dl=0
       
    • By StarFighter_77
      I built this hack years ago now. Started with Lion, now on El Cap. I want to update now to High Sierra.

      I think I messed up my Clover when I downloaded the update .pkg and just installed it without taking my time or customizing the install. Was on Clover r3423, now I think I'm on r5104

      I've been searching and reading this site and others for a few days before making this thread, but I need help compiling what I've learned to get my system running correctly again and ready to update to High Sierra. Then, eventually, I want to update my graphics card, switch to UEFI (if necessary) and update to Mojave.

      I couldn't get system to boot. Could get to Clover and all the options, except the Shell... I hit enter on the Shell and I get black screen and nothing.

      The only way I got it to boot was to add -v to boot args, and change smbios from 14,2 to 13,2. Not sure why that worked still. Also I'm running two monitors, but I can only now run one of them off the Intel 3000 Graphics and the second one off my GFX Card.

      So now I'm afraid to shut down or reboot.... I could really use some help with Clover.

      I'm pretty sure my config file in Clover is not right. Also, some of the files in my Clover backups are not in the new Clover install. (2.5k 5104)

      If someone could please take a look at the files I've attached and help me sort this out, I would be grateful. Thank you, Thank you, Thank you.

      I've attached
      - The last boot log
      - The current Clover folder from the EFI partition after performing Clover update. (.zip)
      - The Clover backup that was working before Clover update (.zip)
      - Library/Extensions Folder (screen shot)
      - System/Library/Extensions Folder (.zip)

      Here is my current hardware:

      Mobo: GIGABYTE GA-Z68MX-UD2H-B3

      CPU: Intel Core i7-2600K

      GPU: GIGABYTE ATI Radeon HD6870 1GB DDR5 2DVI/HDMI/2x

      RAM: Corsair Vengeance Blue 16 GB DDR3 SDRAM Dual Channel Memory Kit CMZ16GX3M4A1600?C9B

      HD0 (for OS and Apps): OCZ Technology 120 GB Vertex Series SATA II Solid State Drive

      HD1 (file storage, Adobe scratch disk): Samsung 1 TB Spinpoint 7200 RPM 32MB Cache SATA

      BURNER: LG CD/DVD Burner Model GH22NS50

      CPU COOLER: Corsair Cooling Hydro Series H50 All in One High-performanc?e CPU Cooler CWCH50-1

      P/S: Antec CP-850 850 Watt CPX Power Supply Unit

      CASE: Antec Performance One P183 V3 Case
      CLOVER.zip
      CloverBackup.zip
      bootlog.txt

      S_L_E.zip
    • By MaLd0n
      --Donations via PayPal--
      https://tinyurl.com/r2bvzm7
       
      --Original Topic--
      https://www.olarila.com/topic/6874-olarila-hackbook-lenovo-ideapad-s145-mojave-catalina-full-dsdt-patches/
       

       
      -Perfect HackBook, HDMI Audio/Video, Bluetooth, AirPlay, Sleep, Lid Sleep, Auto Sleep, Audio, etc!
      -Wifi card has been replaced with Dell DW1560!
      -I'm using a S145-15IWL Model with Intel Core i5 8265u / Intel UHD Graphics 620
      -Update bios/uefi to last version
       
      --Installation--
      https://www.olarila.com/topic/5794-guide-install-macos-with-olarila-image-step-by-step-install-and-post-install-windows-or-mac/
       
      --Clover Folder--
      Just paste EFI folder inside EFI partition
      https://www.olarila.com/files/Clover.Folder/Lenovo IdeaPad S145.zip
      Notebooks with ELAN trackpad use it with my folder above
      IdeaPad S145 ELAN.zip
       
      Bluetooth Broadcom
      Bluetooth Broadcom.zip
       
      CPUFriend for i5-8265U
      CPUFriend i5-8265U.zip
       
      --Full DSDT Patches--
      -My DSDT
      DSDT Lenovo IdeaPad S145.zip
       
      This DSDT work on S145-14IWL, S145-15IWL, V14-IWL, V15-IWL models
      -Patches
      -FIX ERRORS AND WARNINGS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA SERIE 11 ID -DMAC -REMOVE LINES, PROBLEMATIC and UNUSED -SLPB -DARWIN / WINDOWS 2015 -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -REAL TIME CLOCK -ARTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -FWHD -USBX -PMCR -PPMC -XSPI -GMM -IMEI -EC -PRWs -_DSMs -PNLF -BRIGHTNESS KEYS -I2C -NATIVE USB -ARPT -GFX0 -DTGP -kUSBCompanionIndex -io-device-location -FULL RENAMED DEVICES   --IGPU Patch--
      Video solution with HDMI Audio and Video
      <key>PciRoot(0x0)/Pci(0x2,0x0)</key> <dict> <key>AAPL,GfxYTile</key> <data> AQAAAA== </data> <key>AAPL,ig-platform-id</key> <data> CQClPg== </data> <key>device-id</key> <data> pT4AAA== </data> <key>enable-hdmi20</key> <data> AQAAAA== </data> <key>framebuffer-con0-alldata</key> <data> AAAIAAIAAACYAAAA </data> <key>framebuffer-con0-enable</key> <integer>1</integer> <key>framebuffer-con1-alldata</key> <data> AQEJAAAIAADHAQAA </data> <key>framebuffer-con1-enable</key> <integer>1</integer> <key>framebuffer-con2-alldata</key> <data> AgYKAAAEAADHAQAA </data> <key>framebuffer-con2-enable</key> <integer>1</integer> <key>framebuffer-fbmem</key> <data> AACQAA== </data> <key>framebuffer-patch-enable</key> <data> AQAAAA== </data> <key>framebuffer-stolenmem</key> <data> AAAwAQ== </data> <key>framebuffer-unifiedmem</key> <data> AAAAgA== </data> <key>hda-gfx</key> <string>onboard-1</string> <key>model</key> <string>Intel Corporation, Cannon Point-LP Iris Plus Graphics 655</string> </dict>   --Native USB Fix for Notebooks - No Injector/Kext Required--
      https://www.olarila.com/topic/6878-guide-native-usb-fix-for-notebooks-no-injectorkext-required/
      https://www.olarila.com/topic/6181-guide-native-usb-fix-for-desktops-no-injectorkext-required-skylake/
       
       
      -ScreenShots

































      -Links
       
       
      Clover https://github.com/CloverHackyColor/CloverBootloader
      AirportBrcmFixup.kext https://github.com/acidanthera/AirportBrcmFixup
      AppleALC.kext https://github.com/acidanthera/AppleALC
      Brcm Bluetooth https://github.com/acidanthera/BrcmPatchRAM
      Lilu.kext https://github.com/acidanthera/Lilu
      SystemProfilerMemoryFixup.kext https://github.com/Goldfish64/SystemProfilerMemoryFixup
      VirtualSMC.kext https://github.com/acidanthera/VirtualSMC
      VoodooI2C.kext https://github.com/alexandred/VoodooI2C
      VoodooPS2Controller.kext https://github.com/acidanthera/VoodooPS2
      WhateverGreen.kext https://github.com/acidanthera/WhateverGreen
      MaciASL - https://github.com/acidanthera/MaciASL
      acpica - https://github.com/acpica/acpica
      AptioMemoryFix.efi https://github.com/acidanthera/AptioFixPkg
      ApfsDriverLoader.efi https://github.com/acidanthera/AppleSupportPkg
      HFSPlus.efi https://github.com/JrCs/CloverGrowerPro/blob/master/Files/HFSPlus/X64/HFSPlus.efi?raw=true
      Hackintool https://github.com/headkaze/Hackintool
       
      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
       
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad, Sampath007, onemanosx, erroruser, Jenny David, Olarila Facebook Community, Hackintosh Facebook Community and many others!
       
      We're all here to have fun and learn from each other!
    • By kevin_1351
      tl;dr: VirtualSMC causes me a flood of log messages and correlated cpu spikes. FakeSMC doesn't.
       
      Hi, I have almost finalized my Huawei Matebook X Pro Opencore setup and everything is working very well besides wifi/bt ofc (which is about to change).
       
      However, I noticed how the cpu usage sometimes went up a little and when looking at the Console I could see a never-ending flood of:
      default 14:05:05.983292+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:05.982975+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:05.982996+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:06.985932+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:06.985949+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:06.986134+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:39.426574+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:39.426729+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:39.426585+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:41.431085+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:41.431097+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:41.431246+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:42.433068+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:42.433227+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:42.433078+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:43.434453+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:43.434465+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:43.434622+0100 loginwindow clamshellStateChanged | Clamshell state changed: closed=0, shouldSleepWhenClosed=2 default 14:05:44.436155+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0 default 14:05:44.436166+0100 kernel PMRD: clamshell closed 0, disabled 0, desktopMode 0, ac 0 sleepDisabled 0  
      As you can see, multiple of these per second. Another guy with the same computer is also having this issue and posted a dsdt change to fix it. This fix didn't solve anything though
      He tried to limit the Notify call by implementing a state change requirement before calling Notify.
       
      Here is the original acpi:
      Scope (_SB) { Device (LID) { Name (_HID, EisaId ("PNP0C0D") /* Lid Device */) // _HID: Hardware ID Method (_LID, 0, NotSerialized) // _LID: Lid Status { Local0 = One Local0 = ^^PCI0.LPCB.EC0.RPIN (0x05, 0x06) If ((Local0 == 0x55)) { Local0 = Zero } Else { Local0 = One } ^^PCI0.GFX0.CLID = Local0 Return (Local0) } } Device (PWRB) { Name (_HID, EisaId ("PNP0C0C") /* Power Button Device */) // _HID: Hardware ID Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0B) } } } Scope (_SB.PCI0.LPCB.EC0) { Method (_Q81, 0, NotSerialized) // _Qxx: EC Query, xx=0x00-0xFF { Local0 = ^^^^LID._LID () If ((Local0 == Zero)) { ADBG ("LID-OFF") SGOV (0x02030009, Zero) SGOV (0x02060000, Zero) } Else { ADBG ("LID-ON") SGOV (0x02030009, One) SGOV (0x02060000, One) Notify (ALSD, 0x80) // Status Change } Notify (LID, 0x80) // Status Change } } Which he changed to: 
      Scope (_SB) { Device (LID) { Name (_OLD, One) // assuming everything else.. the lid should start open? Name (_HID, EisaId ("PNP0C0D") /* Lid Device */) // _HID: Hardware ID Method (_LID, 0, NotSerialized) // _LID: Lid Status { Local0 = One Local0 = ^^PCI0.LPCB.EC0.RPIN (0x05, 0x06) If ((Local0 == 0x55)) { Local0 = Zero } Else { Local0 = One } Return (Local0) } } Device (PNLF) { Name (_HID, EisaId ("APP0002")) // _HID: Hardware ID Name (_CID, "backlight") // _CID: Compatible ID Name (_UID, 0x0A) // _UID: Unique ID Name (_STA, 0x0B) // _STA: Status } Device (PWRB) { Name (_HID, EisaId ("PNP0C0C") /* Power Button Device */) // _HID: Hardware ID Method (_STA, 0, NotSerialized) // _STA: Status { Return (0x0B) } } } Scope (_SB.PCI0.LPCB.EC0) { Method (_Q81, 0, NotSerialized) // _Qxx: EC Query, xx=0x00-0xFF { Local0 = ^^^^LID._LID () If ((Local0 == Zero)) { ADBG ("LID-OFF") SGOV (0x02030009, Zero) SGOV (0x02060000, Zero) } Else { ADBG ("LID-ON") SGOV (0x02030009, One) SGOV (0x02060000, One) Notify (ALSD, 0x80) // Status Change } If ((^^^^LID._OLD != Local0)) { Notify (LID, 0x80) // Status Change ^^^^LID._OLD = Local0 } } } Besides me not seeing any reason to declare _OLD in LID. The idea itself shouldn't be too bad right? Well, as I said, his fix didn't work.
       
      In fact, to prove that Method _Q81 doesn't have anything to do with the issue at all, I created a Clover/Opencore patch to change _Q81 to XQ81. This resulted in my lid not working at all of course, but the log flooding still persisted!
      So _Q81 doesn't have anything to do with the issue afaik.
       
      Now, further Google searches led me to a chinese post where he tied the issue to VirtualSMC. And indeed, by migrating to FakeSMC the issue is no more.
       
      Unfortunately, I'm very fond of VirtualSMC for various reasons. So I would very much like to keep it. If not I'd have to implement the old way of doing Battery monitoring etcetc. Which isn't very elegant and update proof as it requires DSDT patching.
       
      So, I do believe that the issue may very well be in the DSDT code, perhaps in the ambient light part. I'm not very skilled at this and just started studying the ACPI spec 3 days ago.
       
      Could someone please help me out? Thanks a lot in advance
       
       
      origin.zip
      OC.zip
×