Contribute
Register

Xiaomi Mi Notebook Pro announced!

RehabMan

Moderator
Joined
May 3, 2012
Messages
191,731
Motherboard
Intel DH67BL
CPU
Core i7-2600K
Graphics
Intel HD 3000
Mac
MacBook Air
Mobile Phone
iOS
My Dell does not allow me to choose the interface. Whether or not that option exists in hidden BIOS optionsI do not know since I haven't gone through the process of unlocking my BIOS.

Regardless, an option for choosing the protocol doesn't really matter for us: VoodooPS2 and VoodooI2C play nicely together so if someone has a PS2 Keyboard and a PS2/I2C trackpad then installing both VoodooPS2 and VoodooI2C will result in the keyboard working fine with VoodooPS2 and the trackpad working fine with VoodooI2C (this is exactly what I have).
Which laptop do you have that has I2C? Does the Haswell Dell Venue 11 Pro (the only hardware in your profile) have I2C?
 
Joined
Nov 8, 2014
Messages
152
Mac
Classic Mac
Mobile Phone
Which laptop do you have that has I2C? Does the Haswell Dell Venue 11 Pro (the only hardware in your profile) have I2C?
The DVP11 in my profile has only an I2C touchscreen. I've neglected to update my profile with the my newer one but I'll describe what's important here:

My other machine is a Dell XPS 15 9550 Skylake which has a rather interesting trackpad. It has a dual PS2 / I2C trackpad as outlined above. The I2C interface exposes a Precision Touchpad protocol (which can exist on both USB and I2C trackpads) using the I2C HID protocol. Interestingly, the trackpad also exposes a propriety Synaptics I2C protocol (of which there is no indication in the ACPI tables) which is usually implemented by the driver that Dell provides for Windows (which is often why disabling Dell's driver makes the trackpad work better on Windows due to shoddy Dell drivers). To top it off, the trackpad is Dell branded with an ACPI ID of DLL06E4. The PS2 manifestation of the trackpad has the same ID.

I've attached a copy of my IOReg incase you're interested (there is a handy VoodooI2C IORegistryPlane that I added for easier debugging and access to I2C related devices).
 

Attachments

RehabMan

Moderator
Joined
May 3, 2012
Messages
191,731
Motherboard
Intel DH67BL
CPU
Core i7-2600K
Graphics
Intel HD 3000
Mac
MacBook Air
Mobile Phone
iOS
The DVP11 in my profile has only an I2C touchscreen. I've neglected to update my profile with the my newer one but I'll describe what's important here:

My other machine is a Dell XPS 15 9550 Skylake which has a rather interesting trackpad. It has a dual PS2 / I2C trackpad as outlined above. The I2C interface exposes a Precision Touchpad protocol (which can exist on both USB and I2C trackpads) using the I2C HID protocol. Interestingly, the trackpad also exposes a propriety Synaptics I2C protocol (of which there is no indication in the ACPI tables) which is usually implemented by the driver that Dell provides for Windows (which is often why disabling Dell's driver makes the trackpad work better on Windows due to shoddy Dell drivers). To top it off, the trackpad is Dell branded with an ACPI ID of DLL06E4. The PS2 manifestation of the trackpad has the same ID.
Cool.
Someday, I'll upgrade to a laptop with I2C (then I can have some fun...)

I've attached a copy of my IOReg incase you're interested (there is a handy VoodooI2C IORegistryPlane that I added for easier debugging and access to I2C related devices).
Interesting... didn't know we could add custom planes.

Note: Your ioreg shows Dell SMBIOS truncation. You need config.plist/KernelAndKextPatches/DellSMBIOSPatch=true.
 
Joined
Jul 2, 2017
Messages
6
Mobile Phone
Android
Okay, I'm back (sorry for delay).
I solved the problem with audio using VoodooHDA (and removing AppleHDA). Now I have to switch manually from speaker to jack, but at least it works propely.
Touchpad sometime doesn't work at all...
Someone have some idea for solve HDMI (or Type C video output) and second display issue ?

Thank you in advance
 

Attachments

RehabMan

Moderator
Joined
May 3, 2012
Messages
191,731
Motherboard
Intel DH67BL
CPU
Core i7-2600K
Graphics
Intel HD 3000
Mac
MacBook Air
Mobile Phone
iOS
Joined
Dec 18, 2017
Messages
4
Motherboard
Mi Pro 15.6
CPU
i7-8550U
Graphics
NVIDIA GeForce MX150
Mac
MacBook Pro, Mac mini
Mobile Phone
iOS
Hi, I have the Mi pro, and High Sierra is working with the EFI on Github.
The problem is that the Intel intel 8265 bluetooth does not work if turn on the laptop and start directly to High Sierra.

bluetooth not working.png

But if I started windows 10 and then restart to High Sierra, it works.
bluetooth working.png

Attached zips are ioreg and clover files:

Thanks a lot.
 

Attachments

RehabMan

Moderator
Joined
May 3, 2012
Messages
191,731
Motherboard
Intel DH67BL
CPU
Core i7-2600K
Graphics
Intel HD 3000
Mac
MacBook Air
Mobile Phone
iOS
The problem is that the Intel intel 8265 bluetooth does not work if turn on the laptop and start directly to High Sierra.
It is as you should expect.
In cold boot (and wake from sleep), the BT controller will not have any firmware.
 
Joined
Jun 15, 2015
Messages
35
Motherboard
Xiaomi Mi Notebook Pro
CPU
Intel Core i7-8550U
Graphics
Intel UHD620/Nvidia MX150
Mobile Phone
Android
mini pci-e
Are you sure it's miniPCI-E? Give me link pls. I saw some things like M.2 > mSATA, but not M.2 > miniPCI-E. If it is, we have detachable antennas from Intel wireless and Key-B port marked "WLAN_LTE" on motherboard, so probably Broadcom cards should work, but I can't find right adapter...
 
Joined
Jun 15, 2015
Messages
35
Motherboard
Xiaomi Mi Notebook Pro
CPU
Intel Core i7-8550U
Graphics
Intel UHD620/Nvidia MX150
Mobile Phone
Android
In cold boot (and wake from sleep), the BT controller will not have any firmware.
I'm wondering - is there any plans in Clover development for Firmware Injection? Should *kinda* work, kext would be better, but nobody cares about Intel chips
 

RehabMan

Moderator
Joined
May 3, 2012
Messages
191,731
Motherboard
Intel DH67BL
CPU
Core i7-2600K
Graphics
Intel HD 3000
Mac
MacBook Air
Mobile Phone
iOS
I'm wondering - is there any plans in Clover development for Firmware Injection? Should *kinda* work, kext would be better, but nobody cares about Intel chips
It would require a complete USB stack to be implemented in Clover and appropriate firmware embedded for all supported devices.
Seems rather unlikely, and not practical.
 
Top