Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Nov 25 12:11
    gvkt commented #474
  • Nov 25 11:40
    gvkt closed #485
  • Nov 21 17:45
    usr-sse2 commented #445
  • Nov 15 02:28
    sqlsec commented #474
  • Nov 14 04:17
    Xiashangning closed #447
  • Nov 14 04:17
    Xiashangning commented #447
  • Nov 14 04:15
    Xiashangning commented #447
  • Nov 13 21:33

    kprinssu on master

    Revert f0c868d, add IOMatchCate… (compare)

  • Nov 13 21:33
    kprinssu closed #56
  • Nov 13 19:06
    gvkt commented #474
  • Nov 13 19:05
    gvkt commented #474
  • Nov 13 18:49
    gvkt commented #485
  • Nov 13 18:41
    gvkt commented #485
  • Nov 13 17:14
    1Revenger1 ready_for_review #56
  • Nov 13 17:14
    1Revenger1 commented #56
  • Nov 13 13:59
    ben9923 commented #458
  • Nov 13 13:55
    ben9923 commented #469
  • Nov 13 13:50
    ben9923 commented #447
  • Nov 13 13:40
    ben9923 commented #445
  • Nov 13 13:33
    ben9923 commented #474
Peam269
@Peam269
@jman985 @tmbt78 I've found Something interesting here too: VoodooI2C/VoodooI2C#435 but the part "worrying" me is this one: "When putting either/both in polling mode, both of them work properly." That means it can't be this exact issue as we did try using the polling mode for my Touchpad and it was still completely dead :/
Josh
@jman985
@Peam269 no I get the same errors when using the SSDTs. TPDX shows up in IOReg but nothing underneath.
rexmakro
@rexmakro
Hello there!! Absolutely new to Hackintoshing I managed to complete my first working one. Everything works just fine on Mojave 10.14.6, connections, audio, etc, but the touchscreen is another issue. I tried to follow the VoodooI2C guide, but somehow I am not sure how exactly to proceed with DSDTs. Here are my files extracted from (F4) clover. The device is a Lattepanda Alpha SBC (CPU: m3-8100Y) unit and the touchscreen is named as ".GDIX" on win10 device manager, or <GDIX1001>. It is a 7" eDP 1024x600 touchscreen paired to the SBC. Any help? Is that possible to add the touchscreen to this device? VoodooI2C and VoodooI2CHID are already installed in my kexts folder. On win10, shipped with the device, the touchscreen works absolutely fine paired with a Goodix HID driver.
Peam269
@Peam269
Well, I have tested everything I could possibly think of right now. Without any help, I don't think that I will be able to resolve my issue. I can't get anything to work, only the fake TPXX touchpad shows up in IOREG when using the Razer Blade 15 SSDT.
zilchulant
@zilchulant
I would try to disable all unnecessary I2C Connections, which are not used, so voodoo would only find your Trackpad. But I am interested in such a SSDT myself.
Peam269
@Peam269
Well, I don't even know how to disable those connections xD
I am still wondering if my touchscreen might be causing some issues too... I would like to disable it too if it would bring any adventages with it, because tbh I don't really use it on macOS.
Peam269
@Peam269
Hey, I just realized that GPI0 is located at _SB.GPI0 and not at _SB.PCI0.GPI0 , which seems strange to me... Is this something to care about?
Peam269
@Peam269

Okay, so now I think I got a bit further. Under GPI0, something about VoodooI2C shows up (which I don't think it did before)

But what is definitely different is that under I2C1, there shows something up about VoodooI2C now too (but not my TPD0 touchpad :( )

GPI0.png
I2C1.png
maybe @tmbt78 , could you take a look at it? That would be very awesome :-)
I was using this SSDT-GPI0 to achieve this:
(which I modified by myself). I found it in another razer-15 github guide!
Chicchi7393
@Chicchi7393
Hi, i got the trackpad to work with a polling kext (i did not do the EFI) but if i drag and drop, when i release the left click sometimes it keeps dragging for some seconds, and then releases
how can i fix this?
Roger Carvalho
@rogerdcarvalho
Is there any way to disable screen rotation? On my device, whenever the screen would rotate 90 degrees it just shows a black screen.....
Josh
@jman985
@Peam269 @tmbt78 I think this might be our issue w/the Blade Stealth.
VoodooI2C/VoodooI2C#171
As mentioned by @1Revenger1 it appears to be an issue with the DSDT, which is fixed in Windows by an OS patch.
Peam269
@Peam269
@jman985 hm, sadly they said that they added a fix for this in the guide. Actually, im absolutely tired of trying to make this damn Touchpad to work. Right now, I am just waiting for some magic to happen or somebody to know how to fix our issue, because Testing stuff from other EFIs didn't do anything (yet) and I by myself am too dumb to look at logs & try to fix the errors xD. What I will do though is taking a look at the Issue in the linux Forum (linked in the #171 issue), maybe we can get some helpful Information using linux...
Peam269
@Peam269
@jman985 @tmbt78 Hm, maybe our Touchpad isn't the ELAN 0406... Look at the picture below:
touchpad-bus.PNG
tmbt78
@tmbt78
@Peam269 Hi and sorry for the delay in my answer! I already tried injecting SSCN and FCMN using the files i gave you at first because i already saw #171 issue
but this seems to have solved nothing
Could you try this new EFI and report back as usual with logs etc
Josh
@jman985
@tmbt78 yeah that's what I thought... @Peam my tpad is also the CUST0001..also not sure if this matters or not, but if I re-install Windows via USB boot drive, the tpad also does not work during installation - only when I install the drivers via Windows Updates does it start to work in Windows.
tmbt78
@tmbt78
well it matters a lot the HID name because until now i've always tried to make it works as ELAN0604 and that was simply impossibile if the HID Descriptor is another name
Peam269
@Peam269
@jman985 jup... I recognized that too. You need to Install all Windows Updates before the Touchpad starts to work (Windows Updates automatically installs the Touchpad drivers too). Razer hasn't got any Tochpad Drivers, so the only way to get it working is using Windows Updates (which worrys me a bit actually - considering support for Future Windows Versions) @tmbt78 thanks a lot for the EFI :) will test it right away and report :)
Peam269
@Peam269
@tmbt78 Okay, I tried it - didn't work yet (ofcourse I am always testing the trackpad functionality before taking logs :D)
but here are the debugging files (patchmatic, IOREG and dmesg of "Voodoo"):
tmbt78
@tmbt78
Ok , let's try something different
Peam269
@Peam269
@tmbt78 hm strange, I can't even boot to OpenCore. It says failed to read configuration. I will recreate the USB, maybe that's the issue!
Peam269
@Peam269
@tmbt78 Well, opencore not booting was my fault (something went wrong in the copying process I guess)
Here are the debugging files as usual :)
And sorry for the late answer :/
Oh and btw, the TPDXX (fake-touchpad) doesn't appear anymore in IOREG. But I guess that's correct because you told that you want to try something different
Josh
@jman985
@Peam269 you also mentioned user @schwxr was able to get his ICL Blade Stealth tpad working. I found his comment on this post here:
VoodooI2C/VoodooI2C#342
Peam269
@Peam269
@jman985 yeah, he mentions a CometLake fix he applied to get it working. I am wondering if that has been added to upstream already (I would think so, because IceLake has a lot more documentation nowadays). Maybe it's still worth it to try & apply the patch and see if our TPD0 tochpad appears in IOReg, but I don't really know how to do it ':D
Okay it seems like we don't need to add the IceLake pci ID for sure, because that post has been merged. But maybe trying to add the CML Patch will help...
m0d16l14n1
@m0d16l14n1
that CML patch was actually merged in master later, so you don't need to add it or "apply"
pci ids are good too
your problem with touchpad is probably that:
[ 5.600368]: VoodooI2CControllerNub::pci8086,34e8 SSCN not implemented in ACPI tables
[ 5.645561]: VoodooI2CControllerNub::pci8086,34e8 FMCN not implemented in ACPI tables
Some ASUS laptops for example need that to get touchpad working
Peam269
@Peam269
@m0d16l14n1 hm, the issue you posted here seems like missing pci id, doesn't it?
m0d16l14n1
@m0d16l14n1
nope
Peam269
@Peam269
oh, sorry i didn't read the "SSCN" and "FMCN" part, sorry xD
tmbt78
@tmbt78
@Peam269 The SSCN and FMCN shouldn't be there something in the SSDT i created is not working.
Apart from that most of the issues you have found as been already closed and merged so are not relevant anymore
Try this