Search results

@danilovitch Have you checked if your touch screen is a I2C device? Does it show up as a I2C HID device in windows device manager? Both VoodooPS2Controller and VoodooI2C include VoodooInput and they clash. If you use Propertree to edit your config.plist it will warn you and offer to disable in...

The GPIO controller to attach to your GPI0 is in VoodooI2C.kext. So, without it you are not going to get anything attaching. You need to solve why it is not booting with Voodoo kexts. Do a verbose boot and see where it hangs or if you get any messages. Do the same without the kexts and see where...

MacOS 12.1. After that initial message, not getting it anymore and no instability. Did a ‘sudo purge’ as mentioned in one of the threads. Using the WD SSD it came with. This is compatible with MacOS. Won’t worry about it unless it happens again. I disabled the Intel card bluetooth in USB...

Updated to Monterey in-place with no problem (except no bluetooth built-in or dongle). But running into this message (but no instability so far) that appears to be unfixed in Apple hardware with much more disastrous results. https://developer.apple.com/forums/thread/684276

CPUFriendFriend does the same thing more conveniently and I tried experimenting with that. Right now I am on entirely power saving parameters for all and the CPU monitor is not showing any difference. I will try without CPUFriend entirely. May be CPUFriend is not working for this CPU at all. If...

For comparison, here is the laptop power usage at idle under Windows The idle package power usage is around 1W, Dram Power around 0.65. Hackintosh at idle is about 3-4 times higher which explains the battery drain. The Dram Power usage is also higher at 1+W at idle. Granted it depends on how...

Here is some interesting insights from using the Intel Power Gadget for Mac (free download from Intel) that monitors power and frequency usage. This could be useful for configuring CPU friend. 1. Idle state after bootup 2. Graphics test with loading iGPU to max 3. CPU test with all cores at...

I have the smartpad turned off as display by disabling the connector, so no power being used there. So, the power usage is unrelated to backlight in that display. OLED screen has no backlight. Power used is simply whatever is the composite value that reaches each element. Not some brightness...

I have also been looking at the insane battery usage that appears to be common with these Zenbook laptops with discrete GPU chips that aren’t used while on MacOS. I am coming to the conclusion that it has a lot to do with the inefficient use of integrated graphics on the chip thermally but also...

What is the status of Monterey compatibility relative to Big Sur for this machine? Any diffs positive or negative? I have kept my UX535 in Big Sur because of bluetooth issues with a dongle on Monterey. Don’t know if this is still the case.

This has to do with the way Voodoo code is architected which predates multiple touch display devices. Touch drivers can work in two different modes - Touch screen mode: The cursor position is absolute. In other words, the cursor moves to where the finger touches and the movement is one-one...

There has been sporadic reports in the Linux world of trackpads stopping working if a 5 finger or a palm touch happens on the trackpad (that might trigger a multi-finger report). Voodoo code is derived from Linux drivers. Just pointing a possibility. Haven’t had any such problems with my Zenbook...

Interesting. You could try changing those values especially the first one as a hidden setting using offsets. Pin 74 is locked full. IF (and a big IF) the problem is with Voodoo not being able to configure the pin correctly to get interrupts because it is set wrongly by the BIOS, then unlocking...

The problem is in the BIOS firmware. I have verified with Linux that the APIC interrupt 0x5F is firing for the trackpad. In Linux you can see this interrupt tied to pin 74. Have run Linux with noapic to force GPIO but no GPIO interrupts come in on the pin because the firmware seems to be...

Use this kext and add to boot argument as explained there https://github.com/acidanthera/DebugEnhancer After boot, sudo dmesg | grep Voodoo to see if you get the built in messages for doing polling

According to the DSDT posted earlier, his laptop has APIC interrupt of 0x51. The above formula would then require 265 or 169 neither of which are 0x6D. My guess is that the latter is an incorrect pin that has fallen back to polling silently like in your case.

No, sorry. It is polling. If you have extended debugging on you will see a message like this in dmesg for your Elan device. Same thing could be happening with @sqlsec as well for all I know. The Voodoo code updates the IORegistry before the GPIO pinning is known to have succeeded. [...

After much experimenting with recompiled Linux kernel, it appears that we are out of luck with the BIOS/firmware on our machines. The correct Interrupt to get hardware events is 0x5f. This works on both Windows and Linux OOB as they use their IOAPIC handlers. It corresponds to GPIO pin 74. But...

Thanks. No much different other than setting an addr in _Y38 for the serial bus specification in mine that isn't in yours. Removing that makes no difference. How did you arrive at 0x6D as your GPIO pin starting from the 0x51 in your interrupt specifiers? Formula or trial and error?

The DSDT for ETPD is same as mine. As in the guide, you have to introduce a GPIO interrupt configuration for SBFG definition inside the ETPD scope as below (the compiled SSDT attached) Change the pin number above to try all 3 and see if any of them work. And have a rewrite rule to change in...