Jump to content

user748832

Members
  • Content Count

    29
  • Joined

  • Last visited

Community Reputation

0 Neutral

1 Follower

Hackintosh Specs

  • CPU
    i5-3550
  • Motherboard
    Asus P8B75
  • GPU
    RX570

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. [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.
  2. 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 (no
  3. 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
  4. 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...
  5. 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 w
  6. 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;
  7. [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"
  8. 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...
  9. 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
  10. 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!
  11. [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)
  12. Done ( using the officially released kexts - may 2019 - taken from here: https://github.com/alexandred/VoodooI2C/releases ) Send me PersonakdiMarco.station.zip
  13. [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
  14. 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
  15. [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? Ker
×
×
  • Create New...

:cap-Please Disable Your ADBlocker-:cap