Contribute
Register

VoodooI2C Help and Support

Status
Not open for further replies.
I don't see any KP this time and it's not in the console. Where to find the KP?
You can find kernel panics in /Library/Logs/DiagnosticReports with a .panic extension.
 
You can find kernel panics in /Library/Logs/DiagnosticReports with a .panic extension.

I still don't see the KP in console
Screen Shot 2019-10-23 at 3.14.32 AM.png
 
Hello, i cant´t get my Touchpad (ELAN0626) to work on Lenovo L340. I have followed the GPIO Pinning Guide
and applied the Windows 10 and the GPI0 enable Patch for Skylake+ in my DSDT.aml. My APIC Pin is 53.


Thanks in Advance
 

Attachments

  • debug.zip
    2.6 MB · Views: 82
Last edited:
So display rotation after a sleep/wake cycle remains an issue altough not so important one. I barely need it. However occcasional KPs while starting up and during sleep kept bugging me until I changed the Clover option InjectKexts to Yes. I also removed the I2C kexts from /L/E. Now it's more stable I think.

The logs show kernel: (VoodooI2C) VoodooI2CControllerDriver::VoodooI2CDeviceNub Warning: Incompatible APIC interrupt pin (0x33 > 0x2f) and no GPIO interrupts found; if your chosen satellite implements polling then VoodooI2CDeviceNub will run in polling mode. which probably means I didn't pick the right interrupt. Will have to look into the DSDT again...

Is there a way to find the right interrupt without this try-and-error procedure without guarantee for success?
 
I still don't see the KP in consoleView attachment 432148
Do you have NVRAM working properly?

So display rotation after a sleep/wake cycle remains an issue altough not so important one. I barely need it. However occcasional KPs while starting up and during sleep kept bugging me until I changed the Clover option InjectKexts to Yes. I also removed the I2C kexts from /L/E. Now it's more stable I think.

The logs show kernel: (VoodooI2C) VoodooI2CControllerDriver::VoodooI2CDeviceNub Warning: Incompatible APIC interrupt pin (0x33 > 0x2f) and no GPIO interrupts found; if your chosen satellite implements polling then VoodooI2CDeviceNub will run in polling mode. which probably means I didn't pick the right interrupt. Will have to look into the DSDT again...

Is there a way to find the right interrupt without this try-and-error procedure without guarantee for success?
You should patch for GPIO interrupts
 
I believe so, if not how can I check?
Set an NVRAM variable, reboot and see if it's still there
Make sure it's not emulated NVRAM (i.e using EmuVariableUefi).

Are you sure it's a kernel panic? Are you seeing a panic log?
Boot verbose and set "Don't reboot on panic" in the Clover boot options, you'll see the log on your screen once it panics.
 
Hi , here's my device list,and I uncertain whether it can be support.
CPU: i5-6300HQ
I2CHID device:
bios device name
\_SB.PCI0.I2C0.TPD1
hardware id
ACPI\VEN_ELAN&DEV_1010
PCI\VEN_8086&DEV_A160&SUBSYS_07061028&REV_31\3&11583659&0&A8

I just read the Installation note, as it said:
'pci8086,9d60', 'pci8086,9d61', 'pci8086,9d62' and 'pci8086,9d63' - Skylake era
does it mean's I can not get it work by voodooi2c control?
Many thanks.
 

Attachments

  • device.pdf
    244.9 KB · Views: 143
Last edited:
You should patch for GPIO interrupts
Yes I tried to follow that guide and from the log I see my devices run in the polling mode which actually works good enough but on the other hand I'm not quite sure if that may be causing those casual kernel panics. Sometimes the boot process stalls at initializing the SHUB device. So it's I2C making my system unstable.

Bottom line, my efforts were only partly successful.

Also I missed to consider that my Yoga has three I2C devices: the touchscreen, trackpad and the positions sensor. Are they all using the same interrupt? Is there anything that needs to be done with that regard or how is that? I'm afraid I didn't understand all the details yet...:confused:

Cheers
 
Status
Not open for further replies.
Back
Top