Ivy Bridge and older SMBus Devices do not respond

[loctran016]

Excuse me. Can you help me with this, please. I'm using OpenCore 0.5.9 DEBUG for my Ivy Bridge laptop. Although I’ve tried to used the VoodooRMI.kext, VoodooSMBus.kext but my synaptic trackpad didn’t work (Even I’ve tried disable VoodooPS2Mouse,Trackpad and then VoodooInput inside VoodooPS2 as wel, it can’t movel). I had used the troubleshoot page, too. As you see, there aren’t any SMBus-related SSDT and I’ve modified the VoodooSMBus.kext, too. Here is my EFI as well if you want. Thanks a lot for reading my message.
P/S: I also tried to add these patch from here: https://github.com/leo-labs/macOS-ThinkPad-T480s/blob/master/EFI/CLOVER/config.example.plist#L500-L535 but my mouse still can’t move
EFI.zip

Edit

My laptop is a Ivy Bridge:
DELL INSPIRON 3421:
Core i5 3337U-HD4000
7 Series/C216 Chipset Family SMBus Controller
PS2SmartTouchpad.kext and Rehabman VoodooPS2.kext work with some 2 fingers feature (exclude zoom in, out,...)

Update for version 1.0.1 by @loctran016

I don't know if this is a bug or may be that kind of thing but when I inject VoodooSMBus.kext and VoodooRMI.kext (involves the plug-in as well) but I can't do anything in my laptop (include moving the mouse and shut down) because my laptop just keep loading with a rainbow circle, I haven't had the ability to click on the apple icon for shutting down, too. It just keep loading for very long time so I did force turn off my laptop. I don't know if this is a bug in my laptop only or with some other laptops, too. What do you think about this, then. @1Revenger1 (The 1.0.0 has the same problem like this)
P/S: This hadn't occurred before I inject the kext through OpenCore

Update regarding to VoodooPS2

I have just found a interesting link about VoodooPS2 (don't know if your kexts have the same issues): here. I don't know if you can take a look at that link. I've used the SSDT-Enable_DynamicEWMode.dsl to fix my trackpad with the VoodooPS2 grabbed from acidanthera. It work quite good with force touch but physic buttons don't work. Thanks for reading my message, then (If this is off-topic, just leave a comment and I will delete the update as soon as possibe)

[1Revenger1]

What bootloader? If it's OC, make sure that the order of kext loading is VoodooSMBus.kext, then VoodooRMI.kext, then finally RMISMBus.kext. Make sure that VoodooInput from RMI is being injected as well.
If that doesn't work, can you show what your SMBus looks like in IORegistryExplorer, and get the output from kextstat in terminal.

[loctran016]

@1Revenger1 Maybe the issues is because ProperTree put them in wrong order. One more thing before trying your advice, can RMISMBus.kext be after Whatevergreen like this

[1Revenger1]

Yeah that's fine. The main important thing is that VoodooRMI and VoodooSMBus are before RMISMBus. Doesn't really matter what the order is between the two or if anything is before it/mixed in.

[loctran016]

Well, Although I've set everything like what you say, it can't work, ask for what my SMBus looks like in IORegistryExplorer, and get the output from kextstat in terminal, I'll try to get them to you as soon as possible because I don't have any usb mouse and I can't use my built-in mouse so sorry a lot for that. I'll try to send them to you soon.
P/S: Here is my SMBUS hardward ID if you want:

EFI.zip

[loctran016]

@1Revenger1 ,By the way, my bootloader is OpenCore and I don't know why but if I use the VoodooPS2.kext from Acidanthera my mouse won't work but if i use Rehabman's VoodooPS2 from here: https://github.com/RehabMan/OS-X-Voodoo-PS2-Controller, my trackpad can work with 1 finger and some 2 fingers features (not all of them, scrolling is OK but I can zoom in/out). And here is my full specs by AIDA64 Engineer (a *.txt and *htm in the zip)
Report.zip
Report.txt

[loctran016]

For the others things I will try my best for them

[1Revenger1]

I haven't gotten this to run succesfully on any Ivy Bridge laptops - I'm not entirely sure why. It may be a different version of RMI? Not entirely sure on that, especially since RMI4 goes back to around ~2012. You may have better luck loading it in manually once within the OS just using the keyboard.

sudo chown -R root:wheel *.kext
sudo kextutil -vvvv -d VoodooSMBus.kext -d VoodooRMI.kext VoodooRMI.kext/Contents/PlugIns/VoodooSMBus.kext

Then getting a log by doing

log show --last boot | grep -i voodoo > ~/Desktop/log.txt

[1Revenger1]

The paths need to be accurate, if you are in the same directory as them then the above command should work. But if you aren't, then yes you need to make sure the path is correct to them all.

[loctran016]

There is a problem that you don't have VoodooRMI.kext/Contents/PlugIns/VoodooSMBus.kext so I think that I should change it into this:
sudo chown -R root:wheel *.kext
sudo kextutil -vvvv -d VoodooSMBus.kext -d VoodooRMI.kext VoodooRMI.kext/Contents/PlugIns/RMISMBus.kext

[loctran016]

@1Revenger1 Well, I've tried both but couldn't work. Anyway, all the necessary file is here, sorry if is there anything is miss, just tell me and I'll give it to you.
Fixing trackpad.zip

[gimdh]

https://www.rockbox.org/wiki/pub/Main/SansaFuzePlus/Synaptics_RMI3_Specification.pdf

I guess older touchpads with RMI3 use F10.

[gimdh]

@loctran016 You have to cd into the downloaded and unzipped VoodooRMI folder. Also, make sure to use Debug kext for detailed log information.

For example, running cd ~/Downloads/VoodooRMI-1.0-Debug prior to 1Rvenger1's command should work if you downloaded file with Safari.

[1Revenger1]

It may be that it is RMI3, I haven't seen any way to detect which RMI version it is. It does look programmed very similarly to RMI4 though.

[gimdh]

Log should be located under Downloaded kext folder.
However, it seems you need to remove kext from OC bootloader first. (Just delete two Kext files.)
You can load kext after boot, and in this way you can test kext without reboot.

BTW, you may want to edit post for minor extra informations rather than posting new comment, as an issue board is somewhat different from chat.

//Edit.
Never mind about log file. That command always outputs log to Desktop.

[1Revenger1]

So, what I've noticed is that testing with another person is that on Ivy Bridge, when we ask for the SMBus version, it gets stuck and doesn't get any sort of response, so no attempts are logged to try and get the version. It may be that some sort of timeout may be needed.

Edit: So as far as I can tell with other testing, we're getting stuck in RMISMBus

[Red1860]

I am also on an ivy bridge laptop, Inspiron 14z 5423 and my trackpoint is also not working properly. I edited the VoodooSMBus info.plist file and entered my vender id and device id. All the gestures are working but the trackpoint is very laggy. Btw I am using Clover.

[loctran016]

@Rohan200220 , I've tried that but didn't work, though

[Red1860]

@loctran016 Sometimes it works for me, sometimes it doesn't. When I restart my laptop the trackpad doesn't even respond.

[1Revenger1]

Does someone mind testing out these new versions of VoodooRMI and VoodooSMBus?
https://files.gitter.im/5e938b02d73408ce4fe02f4f/H2AL/VoodooRMI.kext.zip
https://files.gitter.im/5e938b02d73408ce4fe02f4f/66yp/VoodooSMBus.kext.zip

This should hopefully fix the freezing, and give better errors. You may need to add your device id again.

If you are injecting these kexts rather than loading it manually within macOS, better way to get logs it to add msgbuf=1048576 to your boot args, and use sudo dmesg to get logs, as log show --last boot is pretty atrocious for early boot logs.

[Red1860]

My trackpad is still not responding with the above kexts, and I am using clover

[1Revenger1]

I can't do anything without logs. Please reread my last message.

[Red1860]

Log.txt

Sorry, here it is

[1Revenger1]

I'd double check which VoodooSMBus kext your using. It looks like it's trying to probe for an Elans trackpad, when all of the Elans stuff should've been taken out in the above VoodooSMBus download.

Edit: And I'm not finding any logging for published nubs which should be seen in recent versions at address 0x2c. Should be seeing something similar to Publishing nub for slave device at address 0x2c

[Red1860]

I used voodoosmbus from the above link, and how to take out elen stuff from voodoosmbus?

[1Revenger1]

There isn't any Elans stuff in the above link. If you check the Info.plist for the kext you have injected, it should be version 3.0, and not have any Elans stuff within it. Additionally, should have a place to put different addresses.
This is currently what I see

[Red1860]

When I write vrmi, nothing is shown
when I write voodoormi, I get this

[1Revenger1]

Oh - try searching for RMISMbus as well, forgot that is technically a different kext from VoodooRMI.

[Red1860]

I get this when I write rmismbus

[1Revenger1]

that's really weird. Try unloading and then loading it up again a couple times and see if you get an output. I've seen it not output anything before, though usually sudo dmesg is pretty reliable.

[Red1860]

it says unable to unload

[1Revenger1]

You can only unload it once you've loaded it. When you reboot macOS, it automatically unloads. Make sure your grabbing logs after you load it, and are not restarting.

Past that, I'm not really sure what could be wrong, it doesn't seem like the kext is actually attempting to boot up.

[Red1860]

Ok, I loaded and unloaded it a couple of times, and I am sending you the loaded kexts log.
log 7.txt

[1Revenger1]

Hmm, If you check IOReg, is VoodooSMBus attaching to SBUS (or whatever ACPI name your SMBus chip has).
You should be able to have VoodooSMBus still injected by Clover/OpenCore. It's only VoodooRMI/RMISMBus that we're wanting to load within macOS itself.

[Red1860]

No I was injecting voodoosmbus also in macOS, I'll put voodoosmbus in clover and will send you the log

[Red1860]

Yes voodoosmbus is attaching and I also loaded the voodoormi kext within macOS.

log8.txt

[1Revenger1]

Hmm, where did VoodooSMBus and VoodooRMI come from? I recently updated the version of VoodooSMBus needed - so if you got VoodooRMI recently, it needs VoodooSMBus version 3.0

[loctran016]

I've tried to load manually but received this issue. I've run this in terminal:

LocTran@locs-macbook-air ~ % cd /Users/LocTran/Documents/Kext 
LocTran@locs-macbook-air Kext % sudo chown -R root:wheel *.kext
Password:
LocTran@locs-macbook-air Kext % sudo kextutil -vvvv -d VoodooRMI.kext -d VoodooSMBus.kext VoodooRMI.kext/Contents/PlugIns/RMISMBus.kext

But didn't help. Here is my NVRAM then:

Log.txt

[1Revenger1]

It rejected VoodooSMBus and RMISMBus for invalid file permissions (i.e. the kexts weren't owned by root). I usually need to restart if it keeps saying their incorrect even after running chown multiple times, it's weird.

[Red1860]

I tried the latest VoodooRMI 1.1.0 Release, I just put the kexts in my EFI folder and deleted the Trackpad and Mouse kext from VoodooPS2Controller kext, rebooted and my trackpad started to work. But the trackpad is very sluggish and slow, but the gestures are working very well.
log new.txt

[Red1860]

This is what I am getting in Ioreg

The Trackpad is pretty much unusable

[1Revenger1]

If you click on F11, how big does it say the trackpad is in millimeters?

Also, have you tested this across multiple reboots to see if it consistently works?

[Red1860]

Its not working when i rebooted :p
Also it doesn’t do anything when i click on F11

[1Revenger1]

Mind trying this build out? https://github.com/VoodooSMBus/VoodooRMI/runs/1097732807
Should be under artifacts and be built in High Sierra so it should work in Mojave.

[Red1860]

Mouse not working, I tried the debug version.
new log 2.txt

[1Revenger1]

Hmm, can you try using the Ps2 kext from above and using VoodooPS2Trackpad, plus manually loading VoodooRMI from within macOS?

Edit: if you need help with it, I don't mind walking through it in the gutter, might be a bit faster than doing multiple posts in here.

[Red1860]

yeah its better, where can I contact you?

[1Revenger1]

oops, I meant gitter (not gutter). There should be a badge for it at the top of the README.

[proektus123]

Tested latest voodooSMBus 2.2 and VoodooRMI 1.1.0
It works fine on hp9470m

[proektus123]

[1Revenger1]

Moved to #83

[lslqtz]

Same issue, I believe I have a Synaptics trackpad.
macOS 11.6.7, VoodooPS2 2.2.8, VoodooRMI 1.3.4.
Edit: If I don't inject VoodooSMBus, AppleSMBus will be attached to it