user748832
-
Posts
29 -
Joined
-
Last visited
Everything posted by user748832
-
[ref]onemanosx[/ref], yes exactly. And I already said thank you. Now, why you're asking me to test again? Added in 4 minutes 12 seconds: The dsdt is the same as posted last time, when you (or onemanosx) asked me a RunApp. It is your DSDT in the first post, plus the 3 methods that I mentioned. I hope is clear now.
-
Hi onemanosx, what is exactly that you want me to test? Are there improvements in your version? The ELAN kext that I'm using now is just perfect for me, only thing is that touch sensibility is not high, did you improve this? If yes, than I will test a new kext, just send me the link. Thanks. PS. I've setup my Xcode env, cloned the I2C rep and merged in the changes by Sasha that I found here: https://github.com/EmotionalLove/VoodooI2CELAN Only my changes are following lines (176-182) in VoodooI2CELANTouchpadDriver.cpp, as I found that 0xFF (255) is returned when touchpad is Idle (not touched). if (reportData[ETP_REPORT_ID_OFFSET] == 0xFF) { // touchpad is IDLE (no touch) return kIOReturnSuccess; } if (reportData[ETP_REPORT_ID_OFFSET] != ETP_REPORT_ID) { IOLog("%s::%s Invalid report (%d)\n", getName(), device_name, reportData[ETP_REPORT_ID_OFFSET]); return kIOReturnError; } I don't like to have a lot of messages in kernel log (thousand and thousand) like this "Invalid report (255) ...." Added in 17 minutes 57 seconds: Your DSDT didn't work for me as I have ELAN029. This device only works in polling mode. Methods SSCN and FMCN are missing from your DSDT, they are required for polling mode. So, my current DSDT is different from your, as I added inside Device (TPD0) for Scope (_SB.PCI0.I2C0) the following methods: Method (SSCN, 0, NotSerialized) { Return (PKG3 (SSH0, SSL0, SSD0)) } Method (FMCN, 0, NotSerialized) { Return (PKG3 (FMH0, FML0, FMD0)) } Also, I added this, not sure it is really required: Method (PKG3, 3, Serialized) { Name (PKG, Package (0x03) { Zero, Zero, Zero }) PKG [Zero] = Arg0 PKG [One] = Arg1 PKG [0x02] = Arg2 Return (PKG) /* \_SB_.PCI0.I2C0.PKG3.PKG_ */ }
-
I think you have my same exact model (i3 and bluetooth in pending state always). I was unable to find any working GPIO pin number for using I2C in interrupt mode. However, I'm using the ELAN kext provided by onemanosx, which has polling mode enabled for ELAN devices. You also need to patch your DSDT as per my earlier post, otherwise polling mode will not work too. Look at my post of 29 Oct 2019, 17:30
-
Are you saying that Lenovo has updated the BIOS so that hackintosh users will get some benefit from that? I'm not so sure... but I could be wrong. Anyway I will do that. Do we have an archive of previous BIOS, just in case we need to return back? Added in 3 minutes 13 seconds: That operating system is too bad to be installed in dual boot on our lenovo machine. I suggest you to install it on an external usb drive (as I did) so you can use all the SSD space for macOS. Check on google for the WinToUSB tool...
-
I have found more issues... not critical, but annoying. First, sleep is not reliable, sometimes it works very well, sometimes not. (when I reopen the lid, the screen remains black or alternate between black and grey.. so i have to hard power off). Second, audio is usually working good. However, when I connect headphones, sometimes I get a distorted audio (similar to mono sound). This is not easy to reproduce, it seems that the issue disappear after system is rebooted. And, it seems more easy to reproduce at cold boot (turn-off completely, then turn-on and boot). I'll try to play with layout-id parameter of AppleALC in next days... or maybe I have to remove AppleALC and use VoodooHDA instead. PS. My audio device (as I see from Windows) is Realtek ALC230 (vendorID = 10ec, deviceID = 0x0230, subsys = 17aa382c) -------------- EDIT: The problem with headphones is apparently resolved. I was using an older version of config.plist with an injected audio device not needed. Now, I'm using same settings from config.plist in first post by Mald0n, that is removing audio device (keeping only the device for uhd620), and specifying '20' in Audio inject field. Let's cross the fingers...
-
There are no fixes, but only a lot of patches for Security Vulnerabilities (CVE-...). I don't think it's very interesting for an hackintosher.. ----------------------- SEnhancement to address CVE-2019-6171. Enhancement to address CVE-2019-0123; Enhancement to address CVE-2019-0117; Enhancement to address CVE-2019-0185; Enhancement to address CVE-2019-11135; Enhancement to address CVE-2019-0154. Enhancement to address CVE-2019-0131; Enhancement to address CVE-2019-0165; Enhancement to address CVE-2019-0166; Enhancement to address CVE-2019-0168; Enhancement to address CVE-2019-0169; Enhancement to address CVE-2019-11086; Enhancement to address CVE-2019-11087; Enhancement to address CVE-2019-11088; Enhancement to address CVE-2019-11090; Enhancement to address CVE-2019-11097; Enhancement to address CVE-2019-11100; Enhancement to address CVE-2019-11101; Enhancement to address CVE-2019-11102; Enhancement to address CVE-2019-11103; Enhancement to address CVE-2019-11104; Enhancement to address CVE-2019-11105; Enhancement to address CVE-2019-11106; Enhancement to address CVE-2019-11107; Enhancement to address CVE-2019-11108; Enhancement to address CVE-2019-11109; Enhancement to address CVE-2019-11110; Enhancement to address CVE-2019-11131; Enhancement to address CVE-2019-11132; Enhancement to address CVE-2019-11147. -----------------------
-
[ref]MaLd0n[/ref], for WIFI, I see that Dell DW1560 is really expensive (it is based on Broadcom BCM94352Z). Is there some other compatible WIFI card which can fit with our M.2 NGFF connector? I found this one, about 10EUR, but I'm not sure: "Etase DW1820A BCM94350ZAE 802.11Ac BT4.1 Adattatore WiFi 867 Mbps BCM94350 M.2 NGFF DW1820 Scheda WiFi Migliore di BCM94352Z"
-
Why not? I just upgraded from 10.15.0 to 10.15.1... no issues. If you keep all your kexts in CLOVER/kexts/Other directory instead of /S/L/E/ you're safe. Just make sure to have a second way to boot from an external key, just in case...
-
If your specific model of Ideapad S145 has really an Ethernet port, and you have the Kext loaded for that, I think it is not normal. In my case, my S145 model is without Ethernet so I have your same view. And I'm using this one, working fine on Catalina by using the driver on github (WIFI-Dlink Catalina-Panel-V2) by chris1111 https://www.sitecom.com/it/wireless-network-usb-micro-adapter-n300-x3/wla-3000/p/297
-
Yeahhh right I should have thought it before! Version 1.8.34 ( VoodooPS2Controller_2018-0506.kext ) is working fine!!! While v2.0.4 (the latest) and v1.9.2 appear incompatible with your patched kext. I think you can update the VoodooI2C repo with the information that ELAN0629 is supported by your patch, in polling mode. Thank you onemanosx!
-
[ref]onemanosx[/ref], this version is working same as before. 1) I have to use "-v darkwake=0" so I can boot without a panic. 2) By removing "VoodooPS2Controller.kext" (which contains only VoodooPS2Keyboard.kext) I can boot without boot args 3) Apart of this, the touchpad is OK (smooth and multitouch) 4) In kernel log, I continue to see an enormous number of messages like this: (about 100 per second) 2019-11-01 17:59:51.777246+0100 0x29e2c Default 0x0 0 0 kernel: (kernel) VoodooI2CELANTouchpadDriver::ELAN0629 Invalid report (255) ( that's why I'd like to check the source code to remove above trace statement... ) Attaching a new send_me and plus panic log. Thanks. panic(cpu 2 caller 0xffffff8010662e0a): Kernel trap at 0xffffff7f93939977, type 14=page fault, registers: CR0: 0x000000008001003b, CR2: 0x0000000000000000, CR3: 0x000000002552c000, CR4: 0x00000000003626e0 RAX: 0xffffff80346927d8, RBX: 0xffffff80338d5090, RCX: 0xffffff8034692780, RDX: 0xffffff8034f32900 RSP: 0xffffff812c933e90, RBP: 0xffffff812c933e90, RSI: 0x0000000000000000, RDI: 0x0000000000000000 R8: 0xffffff8010ea4490, R9: 0x0000000000000001, R10: 0x00000000000000b4, R11: 0x0000000000000000 R12: 0xffffff80346927d0, R13: 0xffffff8034f32900, R14: 0xffffff8034f32900, R15: 0xffffff8034692780 RFL: 0x0000000000010246, RIP: 0xffffff7f93939977, CS: 0x0000000000000008, SS: 0x0000000000000000 Fault CR2: 0x0000000000000000, Error code: 0x0000000000000000, Fault CPU: 0x2, PL: 0, VF: 1 Backtrace (CPU 2), Frame : Return Address 0xffffff812c9338f0 : 0xffffff8010539a3b 0xffffff812c933940 : 0xffffff8010670fe5 0xffffff812c933980 : 0xffffff8010662a5e 0xffffff812c9339d0 : 0xffffff80104e0a40 0xffffff812c9339f0 : 0xffffff8010539127 0xffffff812c933af0 : 0xffffff801053950b 0xffffff812c933b40 : 0xffffff8010cd17f9 0xffffff812c933bb0 : 0xffffff8010662e0a 0xffffff812c933d30 : 0xffffff8010662b08 0xffffff812c933d80 : 0xffffff80104e0a40 0xffffff812c933da0 : 0xffffff7f93939977 0xffffff812c933e90 : 0xffffff8010c16405 0xffffff812c933ef0 : 0xffffff8010c1916b 0xffffff812c933f50 : 0xffffff8010c1b9cd 0xffffff812c933fa0 : 0xffffff80104e013e Kernel Extensions in backtrace: as.acidanthera.voodoo.driver.PS2Controller(2.0.4)[E2927F57-AEFE-372E-ACAD-19C77D1D69E9]@0xffffff7f93937000->0xffffff7f93946fff dependency: com.apple.iokit.IOACPIFamily(1.4)[4A40B298-87E0-373E-84A9-9A2227924F8F]@0xffffff7f91290000 BSD process name corresponding to current thread: kernel_task Mac OS version: Not yet set Kernel version: Darwin Kernel Version 19.0.0: Thu Oct 17 16:17:15 PDT 2019; root:xnu-6153.41.3~29/RELEASE_X86_64 Kernel UUID: 7503CD47-851F-321E-8747-50DB4299165F Kernel slide: 0x0000000010200000 Kernel text base: 0xffffff8010400000 __HIB text base: 0xffffff8010300000 System model name: MacBookPro15,2 (Mac-827FB448E656EC26) System shutdown begun: NO Panic diags file unavailable, panic occurred prior to initialization System uptime in nanoseconds: 1119201729 last loaded kext at 913624248: >!AFileSystemDriver 3.0.1 (addr 0xffffff7f90e95000, size 16384) loaded kexts: me.kishorprins.VoodooI2CELAN 1 org.hwsensors.driver.LPCSensors 1800 com.alexandred.VoodooI2C 2.2 org.coolstar.VoodooGPIO 1.1 org.hwsensors.driver.ACPISensors 1800 org.rehabman.driver.!ASmartBatteryManager 1.90.1 as.acidanthera.voodoo.driver.PS2!C 2.0.4 org.hwsensors.driver.SMMSensors 1800 org.hwsensors.driver.CPUSensors 1800 as.vit9696.!AALC 1.4.2 com.alexandred.VoodooI2CServices 1 as.vit9696.WhateverGreen 1.3.4 xyz.racermaster.NoTouchID 1.0.2 fish.goldfish64.SystemProfilerMemoryFixup 1.0.0 as.vit9696.Lilu 1.3.9 org.netkas.driver.FakeSMC 1800 >!AFileSystemDriver 3.0.1 >!AVirtIO 1.0 @filesystems.hfs.kext 522.0.9 @!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1 @BootCache 40 @!AFSCompression.!AFSCompressionTypeZlib 1.0.0 @private.KextAudit 1.0 >!AAHCIPort 341.0.2 >!AHPET 1.8 >!AACPIButtons 6.1 >!AACPIEC 6.1 >!ARTC 2.0 >!ASMBIOS 2.1 >!AAPIC 1.7 $!AImage4 1 @nke.applicationfirewall 303 $TMSafetyNet 8 @!ASystemPolicy 2.0.0 |EndpointSecurity 1 |IOSerial!F 11 |IOSurface 269.6 @filesystems.hfs.encodings.kext 1 |IOAHCI!F 290.0.1 >usb.!UHostPacketFilter 1.0 |IOUSB!F 900.4.2 >!AEFINVRAM 2.1 >!ASMCRTC 1.0 >usb.!UXHCIPCI 1.2 >usb.!UXHCI 1.2 >!A!ILpssGspi 3.0.60 >!AEFIRuntime 2.1 |IOSMBus!F 1.1 |IOHID!F 2.0.0 $quarantine 4 $sandbox 300.0 @kext.!AMatch 1.0.0d1 >DiskImages 493.0.0 >!AFDEKeyStore 28.30 >!AEffaceable!S 1.0 >!AKeyStore 2 >!UTDM 489.41.1 |IOSCSIBlockCommandsDevice 422.0.2 >!ACredentialManager 1.0 >KernelRelayHost 1 >!ASEPManager 1.0.1 >IOSlaveProcessor 1 |IOUSBMass!SDriver 157.40.7 |IOSCSIArchitectureModel!F 422.0.2 |IO!S!F 2.1 |IOUSBHost!F 1.2 >!UHostMergeProperties 1.2 >usb.!UCommon 1.0 >!ABusPower!C 1.0 |CoreAnalytics!F 1 >!AMobileFileIntegrity 1.0.5 @kext.CoreTrust 1 |IOTimeSync!F 810.1 |IONetworking!F 3.4 |IOReport!F 47 >!AACPIPlatform 6.1 >!ASMC 3.1.9 >watchdog 1 |IOPCI!F 2.9 |IOACPI!F 1.4 @kec.pthread 1 @kec.corecrypto 1.0 @kec.Libm 1 Send me PersonakdiMarco.station.zip
-
Done ( using the officially released kexts - may 2019 - taken from here: https://github.com/alexandred/VoodooI2C/releases ) Send me PersonakdiMarco.station.zip
-
[ref]onemanosx[/ref], so I can confirm that VoodooI2CELANkext you kindly provided above is working good for ELAN0629 - touchpad fluidity is more than acceptable (with some unexpected jump from time to time..) - multitouch working - Trackpad preferences working and this only works if I boot with "darkwake=0 -v", otherwise I get the kernel panic I posted earlier. I can suppose that darkwake option may have some impact, but I'm really surprised that "-v" is really needed? Trust me, I've tried all the combinations: without "-v" AND "darkwake=0" it will not boot. What about the source code of above kext? Is there a way to look at it? I've setup Xcode and compiled the latest official I2C and satellite kexts, but it looks like your experimental changes are not there yet. Can you provide your changes as a preview? I'm so curious to see how did you enable polling mode support for ELAN... Thank you, Marco
-
Hi [ref]onemanosx[/ref], here is the full stack trace when I use your debug I2CELAN kext (which is nice, when I don't get this panic). Is there a conflict with PS2 keyboard kext? panic(cpu 2 caller 0xffffff8014e689ca): Kernel trap at 0xffffff7f98134977, type 14=page fault, registers: CR0: 0x000000008001003b, CR2: 0x0000000000000000, CR3: 0x0000000029dda000, CR4: 0x00000000003626e0 RAX: 0xffffff80390ff658, RBX: 0xffffff8038217060, RCX: 0xffffff80390ff600, RDX: 0xffffff80398b7000 RSP: 0xffffff81284fbe90, RBP: 0xffffff81284fbe90, RSI: 0x0000000000000000, RDI: 0x0000000000000000 R8: 0xffffff80156a4490, R9: 0x0000000000000001, R10: 0x000000000000009b, R11: 0x0000000000000000 R12: 0xffffff80390ff650, R13: 0xffffff80398b7000, R14: 0xffffff80398b7000, R15: 0xffffff80390ff600 RFL: 0x0000000000010246, RIP: 0xffffff7f98134977, CS: 0x0000000000000008, SS: 0x0000000000000000 Fault CR2: 0x0000000000000000, Error code: 0x0000000000000000, Fault CPU: 0x2, PL: 0, VF: 1 Backtrace (CPU 2), Frame : Return Address 0xffffff81284fb8f0 : 0xffffff8014d3f98b 0xffffff81284fb940 : 0xffffff8014e76c15 0xffffff81284fb980 : 0xffffff8014e6861e 0xffffff81284fb9d0 : 0xffffff8014ce6a40 0xffffff81284fb9f0 : 0xffffff8014d3f077 0xffffff81284fbaf0 : 0xffffff8014d3f45b 0xffffff81284fbb40 : 0xffffff80154d2d89 0xffffff81284fbbb0 : 0xffffff8014e689ca 0xffffff81284fbd30 : 0xffffff8014e686c8 0xffffff81284fbd80 : 0xffffff8014ce6a40 0xffffff81284fbda0 : 0xffffff7f98134977 0xffffff81284fbe90 : 0xffffff8015417ae5 0xffffff81284fbef0 : 0xffffff801541a84b 0xffffff81284fbf50 : 0xffffff801541d0ad 0xffffff81284fbfa0 : 0xffffff8014ce613e Kernel Extensions in backtrace: as.acidanthera.voodoo.driver.PS2Controller(2.0.4)[E2927F57-AEFE-372E-ACAD-19C77D1D69E9]@0xffffff7f98132000->0xffffff7f98141fff dependency: com.apple.iokit.IOACPIFamily(1.4)[9BA2613C-A129-3EDD-8DC1-2CFF6B62B832]@0xffffff7f95e38000 BSD process name corresponding to current thread: kernel_task Mac OS version: Not yet set Kernel version: Darwin Kernel Version 19.0.0: Wed Sep 25 20:18:50 PDT 2019; root:xnu-6153.11.26~2/RELEASE_X86_64 Kernel UUID: 70EDD61F-86EE-3E1B-873F-98D909B78160 Kernel slide: 0x0000000014a00000 Kernel text base: 0xffffff8014c00000 __HIB text base: 0xffffff8014b00000 System model name: MacBookPro15,2 (Mac-827FB448E656EC26) System shutdown begun: NO Panic diags file unavailable, panic occurred prior to initialization System uptime in nanoseconds: 1244525054 last loaded kext at 1038473746: >!AFileSystemDriver 3.0.1 (addr 0xffffff7f95ac5000, size 16384) loaded kexts: com.alexandred.VoodooI2CHID 1 me.kishorprins.VoodooI2CELAN 1 org.hwsensors.driver.LPCSensors 1800 com.alexandred.VoodooI2C 2.2 org.rehabman.driver.!ASmartBatteryManager 1.90.1 org.hwsensors.driver.ACPISensors 1800 org.coolstar.VoodooGPIO 1.1 as.acidanthera.voodoo.driver.PS2!C 2.0.4 org.hwsensors.driver.SMMSensors 1800 org.hwsensors.driver.CPUSensors 1800 xyz.racermaster.NoTouchID 1.0.2 as.vit9696.!AALC 1.4.2 com.alexandred.VoodooI2CServices 1 as.vit9696.WhateverGreen 1.3.3 org.netkas.driver.FakeSMC 1800 fish.goldfish64.SystemProfilerMemoryFixup 1.0.0 as.vit9696.Lilu 1.3.8 >!AFileSystemDriver 3.0.1 >!AVirtIO 1.0 @filesystems.hfs.kext 522.0.9 @!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1 @BootCache 40 @!AFSCompression.!AFSCompressionTypeZlib 1.0.0 >!AAHCIPort 341.0.2 @private.KextAudit 1.0 >!AACPIEC 6.1 >!AACPIButtons 6.1 >!AHPET 1.8 >!ARTC 2.0 >!ASMBIOS 2.1 >!AAPIC 1.7 $!AImage4 1 @nke.applicationfirewall 302 $TMSafetyNet 8 @!ASystemPolicy 2.0.0 |EndpointSecurity 1 |IOSerial!F 11 |IOSurface 269.6 @filesystems.hfs.encodings.kext 1 |IOGraphics!F 558.3 |IOAHCI!F 290.0.1 >usb.!UXHCIPCI 1.2 >usb.!UXHCI 1.2 >!A!ILpssGspi 3.0.60 >!AEFINVRAM 2.1 >usb.!UHostPacketFilter 1.0 |IOUSB!F 900.4.2 >!AEFIRuntime 2.1 >!ASMCRTC 1.0 |IOSMBus!F 1.1 |IOHID!F 2.0.0 $quarantine 4 $sandbox 300.0 @kext.!AMatch 1.0.0d1 >DiskImages 493.0.0 >!AFDEKeyStore 28.30 >!AEffaceable!S 1.0 >!AKeyStore 2 >!UTDM 489.11.2 |IOSCSIBlockCommandsDevice 422.0.2 >!ACredentialManager 1.0 >KernelRelayHost 1 >!ASEPManager 1.0.1 >IOSlaveProcessor 1 |IOUSBMass!SDriver 157.11.2 |IOSCSIArchitectureModel!F 422.0.2 |IO!S!F 2.1 |IOUSBHost!F 1.2 >!UHostMergeProperties 1.2 >usb.!UCommon 1.0 >!ABusPower!C 1.0 |CoreAnalytics!F 1 >!AMobileFileIntegrity 1.0.5 @kext.CoreTrust 1 |IOTimeSync!F 800.14 |IONetworking!F 3.4 |IOReport!F 47 >!AACPIPlatform 6.1 >!ASMC 3.1.9 >watchdog 1 |IOPCI!F 2.9 |IOACPI!F 1.4 @kec.pthread 1 @kec.corecrypto 1.0 @kec.Libm 1 Added in 8 minutes 23 seconds: [ref]kuarahy@icloud.com[/ref], I am able to use the card reader by using your old DSDT (the one you gave me days ago from the other forum). However, I suspect card reader can be activated just applying the USB ports limit patches in Clover, as you did earlier. So it's not a matter of DSDT or kext, but of config.plist. To be confirmed. I'm actually patching your old DSDT with suggestions from onemanosx in order to activate my touchpad.
-
[ref]onemanosx[/ref], this kext is very interesting. In interrupt mode, touchpad not working at all (and with high CPU usage). In polling mode, when I'm able to boot the system, the touchpad is working great! Trackpad preferences are working too and I can use the multitouch too. The pointer movement is almost fluid. The problem: Boot crashes and I have to retry multiple times before I can reach the login screen. I'm still not 100% sure, but it seems that I can boot when using "-v darkwake=0" as boot options. Is this an experimental kext with additional debugging messages? Kernel log is flooded very quickly with messages like this: VoodooI2CELANTouchpadDriver::ELAN0629 Invalid report (255) Anyway, very good progress.
-
Will try as soon as possible, thank you!
-
My model is Lenovo IdeaPad S145 15IWL (model 81MV00DYIX) and in System Profiler, under NVMExpress, there is nothing. (empty) I think the provided SSD has a SATA PCI-E M.2 connector, it appears under SATA/SATA Express. I have opened the laptop and found a free SATA 2,5'' slot to add a second HHD (or better SSD) if needed.. Added in 24 minutes 8 seconds: [ref]onemanosx[/ref], in trackpad preference I can't do anything as the touchpad is not really recognized as a real touchpad, but as a mouse. I read somewhere that this is typical when using Polling Mode with VoodooI2CHID. Also, polling mode is only supported by VoodooI2CHID (as I read from the official VoodooI2C site). If I try to use voodooI2celan in polling mode, it is not loaded at all (under TPD0 of IO explorer there is nothing). Now, I'm sticking with VoodooI2CHID/Polling, but I hope someone will release a new voodooI2celan supporting ELAN0629 in Interrupt mode without the CPU issue... Thanks for the suggestion of using kextcache.. even if I only use CLOVER/kexts/Other, does it apply kextcache for that? Finally, just to confirm: here is how I changed my original DSDT to force I2C satellite kext to attach to the controller: (they were missing) and I use this final Return statement in _CRS method for Polling mode Return (ConcatenateResTemplate (SBFB, SBFI)) For IRQ mode I use this instead Return (ConcatenateResTemplate (SBFB, SBFG)) Is this correct or I'm missing something?
-
For touchpad you have ELAN0629 like me, good luck! So far, I only succeeded to use VoodooI2CHID.kext, with limited results... better than nothing. How about bluetooth? Did you install some kext or it was already working? My BT device is recognized but it hangs and cannot be disabled. Added in 2 minutes 36 seconds: My S145 has a 256 GB SSD, how can I check if NVME or not? I opened the laptop, it seems have a M.2 connector but not sure.. Added in 2 minutes 38 seconds:
-
Can I ask you how did you edit DSDT to make I2C device to fully loading? Did you follow a guide? I noticed three additional methods in your DSDT, where is documented this? Method (PKG3, 3, Serialized) { Name (PKG, Package (0x03) { Zero, Zero, Zero }) PKG [Zero] = Arg0 PKG [One] = Arg1 PKG [0x02] = Arg2 Return (PKG) /* \_SB_.PCI0.I2C0.PKG3.PKG_ */ } Method (SSCN, 0, NotSerialized) { Return (PKG3 (SSH0, SSL0, SSD0)) } Method (FMCN, 0, NotSerialized) { Return (PKG3 (FMH0, FML0, FMD0)) } TO SUMMARIZE: I’m trying to use this method to fully load my ELAN device, but I can’t use your version of DSDT because CPU is always at 100% and battery is discharged very quickly. When using VoodooI2CHID the trackpad is able to move the pointer, but it is totally unusable. (pointer moves too slow or too fast, and it continues to move forever). When using VoodooI2CELAN the trackpad is not working, but ELAN device is fully loaded. CPU is always 100% when Trackpad is not touched. If I touch/swipe the trackpad, the CPU activity can decrease to zero, but return to 100% as soon as I stop to move my finger on the touchpad.. very strange! Thank you for your help. Added in 22 minutes 55 seconds: Here are the pins I've used in interrupt mode 0x35 0x52 0x6e 0x42 0x17 0x1B 0x34 0x55 Here is the log (with errors) for one of them: 2019-10-28 19:25:04.763938+0100 0xb8 Default 0x0 0 0 kernel: (kernel) VoodooGPIOCannonLakeLP::Loading GPIO Data for CannonLake-LP 2019-10-28 19:25:04.764001+0100 0xb8 Default 0x0 0 0 kernel: (kernel) VoodooGPIOCannonLakeLP::VoodooGPIO Init! 2019-10-28 19:25:04.764003+0100 0xb8 Default 0x0 0 0 kernel: (kernel) VoodooGPIOCannonLakeLP::VoodooGPIO Initializing Community 0 2019-10-28 19:25:04.764051+0100 0xb8 Default 0x0 0 0 kernel: (kernel) VoodooGPIOCannonLakeLP::VoodooGPIO Initializing Community 1 2019-10-28 19:25:04.764088+0100 0xb8 Default 0x0 0 0 kernel: (kernel) VoodooGPIOCannonLakeLP::VoodooGPIO Initializing Community 2 2019-10-28 19:25:04.764219+0100 0x76 Default 0x0 0 0 kernel: (kernel) VoodooGPIOCannonLakeLP::GPIO Controller is already awake! Not reinitializing. 2019-10-28 19:25:04.855934+0100 0xe3 Default 0x0 0 0 kernel: (kernel) VoodooI2CPCIController::pci8086,9de8 Starting I2C controller 2019-10-28 19:25:04.855968+0100 0xe3 Default 0x0 0 0 kernel: (kernel) VoodooI2CPCIController::pci8086,9de8 Set PCI power state D0 2019-10-28 19:25:04.856008+0100 0xe3 Default 0x0 0 0 kernel: (kernel) VoodooI2CPCIController::pci8086,9de8 Publishing nub 2019-10-28 19:25:04.882775+0100 0xf2 Default 0x0 0 0 kernel: (kernel) VoodooI2CControllerDriver::pci8086,9de8 Probing controller 2019-10-28 19:25:04.882799+0100 0xf2 Default 0x0 0 0 kernel: (kernel) VoodooI2CControllerDriver::pci8086,9de8 Found valid Synopsys component, continuing with initialisation 2019-10-28 19:25:04.883112+0100 0xf2 Default 0x0 0 0 kernel: (kernel) VoodooI2CControllerNub::pci8086,9de8 SSCN not implemented in ACPI tables 2019-10-28 19:25:04.883118+0100 0xf2 Default 0x0 0 0 kernel: (kernel) VoodooI2CControllerNub::pci8086,9de8 FMCN not implemented in ACPI tables 2019-10-28 19:25:04.883121+0100 0xf2 Default 0x0 0 0 kernel: (kernel) VoodooI2CControllerDriver::pci8086,9de8 Warning: Error getting bus config, using defaults where necessary 2019-10-28 19:25:04.883146+0100 0xf2 Default 0x0 0 0 kernel: (kernel) VoodooI2CControllerDriver::pci8086,9de8 Publishing device nubs 2019-10-28 19:25:04.883153+0100 0xf2 Default 0x0 0 0 kernel: (kernel) VoodooI2CControllerDriver::pci8086,9de8 Found I2C device: ELAN0629 2019-10-28 19:25:04.883303+0100 0xf2 Default 0x0 0 0 kernel: (kernel) VoodooI2CDeviceNub::Got GPIO Controller! VoodooGPIOCannonLakeLP 2019-10-28 19:25:05.403091+0100 0x150 Default 0x0 0 0 kernel: (kernel) VoodooI2CELANTouchpadDriver::elan Touchpad probe 2019-10-28 19:25:05.403097+0100 0x150 Default 0x0 0 0 kernel: (kernel) VoodooI2CELANTouchpadDriver::elan ELAN device found (ELAN0629) 2019-10-28 19:25:05.403116+0100 0x150 Default 0x0 0 0 kernel: (kernel) VoodooGPIOCannonLakeLP::Registering hardware pin 82 for GPIO IRQ pin 110 2019-10-28 19:25:05.403258+0100 0x150 Default 0x0 0 0 kernel: (kernel) VoodooI2CControllerDriver::pci8086,9de8 I2C Transaction error details 2019-10-28 19:25:05.403262+0100 0x150 Default 0x0 0 0 kernel: (kernel) VoodooI2CControllerDriver::pci8086,9de8 slave address not acknowledged (7bit mode) 2019-10-28 19:25:05.403266+0100 0x150 Default 0x0 0 0 kernel: (kernel) VoodooI2CControllerDriver::pci8086,9de8 I2C Transaction error: 0x01800001 - aborting 2019-10-28 19:25:05.403270+0100 0x150 Default 0x0 0 0 kernel: (kernel) VoodooI2CELANTouchpadDriver::ELAN0629 Failed to write RESET cmd 2019-10-28 19:25:05.403272+0100 0x150 Default 0x0 0 0 kernel: (kernel) VoodooI2CELANTouchpadDriver::elan Failed to init device
-
Heeeelp! I have big problems by using your DSDT: - First, with VoodooI2CELAN TouchPad still not working - Second, with VoodooI2CHID.. for the first time the TouchPad is responding but pointer movement is strange (pointer will continue to move after the touch) - Third, CPU1 is almost 100%, the Power LED is flashing like when Laptop is in sleep. I have turned OFF, then turn ON, Power LED still flashing!!! How can I reset the Laptop? I think something has been corrupted in the BIOS
-
@onemanosx. Uploading here new sendme file, using your DSDT.aml + I2C/I2CELAN kexts ( Not sure where is I2C thread? ) Thank you! Send me MacBookldiMarco.station.zip
-
Just to clarify: I didn't test pin numbers 82 and 53 (0x52 and 0x35) because of this sentence in the Guide: So, by following the same Guide, I did the conversion as follows: 82 - 68 + 96 = 110 = 0x6e 53 - 51 + 64 = 66 = 0x42 Anyway, as you suggested, I have just tried those pin numbers without any conversion (0x52 and 0x35) with same results. One observation: I noticed that, without GPIO Pin Change, I see this for TPD0 While, after pin change the device has a different content (IOInterruptSpecifiers is gone!) Maybe the kext file are still not supporting this ELAN device?
-
Are you saying that the GPIO pinning guide is incorrect? I see that "hexadecimal APIC pin number" = 0x6e which is NOT less than 0x2F So I had to follow all the other steps before installing the I2C kext files in CLOVER/Kexts/Other And yes I used the CannonPointLP IRQ tables to calculate the new PIN (0x42, 0x6e) And yes I used the VoodooI2CELAN kext (after tried with VoodooI2CHID kext) My Touchpad is still not working
-
Assuming TPD0 is the device I have to look at, this is my initial _CRS method: Method (_CRS, 0, NotSerialized) // _CRS: Current Resource Settings { If ((OSYS < 0x07DC)) { Return (SBFI) /* \_SB_.PCI0.I2C0.TPD0.SBFI */ } Return (ConcatenateResTemplate (SBFB, SBFI)) } The GPIO pinning guide is a bit unclear at final step 2e, where it states: ------------------ Step 2e: Ensuring your DSDT notifies the system that your device is GPIO pinned Finally, make sure that there are no other Return statements in your _CRS method apart from the following at the end: Return (ConcatenateResTemplate (SBFB, SBFG)) ------------------ So, I did a couple of tests (both unsuccessfull): Test 1: just touch the final Return statement Method (_CRS, 0, NotSerialized) // _CRS: Current Resource Settings { If ((OSYS < 0x07DC)) { Return (SBFI) /* \_SB_.PCI0.I2C0.TPD0.SBFI */ } Return (ConcatenateResTemplate (SBFB, SBFG)) } Test 2: also, remove the IF which contain another Return statement Method (_CRS, 0, NotSerialized) // _CRS: Current Resource Settings { Return (ConcatenateResTemplate (SBFB, SBFG)) } Can I try something else? ref: https://voodooi2c.github.io/#GPIO%20Pinning/GPIO%20Pinning EDIT - As for the GPIO Pin, I first tried to leave this as is (assuming it is well-pinned) Name (SBFG, ResourceTemplate () { GpioInt (Level, ActiveLow, ExclusiveAndWake, PullDefault, 0x0000, "\\_SB.PCI0.GPI0", 0x00, ResourceConsumer, , ) { // Pin list 0x0000 } }) Then, I replaced 0x0000 with 0x6e and 0x42, no luck. (calculated as per above guide)
-
Here is the attachment.. Thanks. Send me MacBookldiMarco.station.zip