-
Posts
5778 -
Joined
-
Last visited
-
Days Won
124
Content Type
Profiles
Articles, News and Tips
Forums
Everything posted by Bronxteck
-
latitude 7490 Dell lattitude 7490: method to install Catalina
Bronxteck replied to Tubardus's topic in The Archive
but injection is a mandatory evil for installations as the install dmg does not have a cache. if using C/K/O path make sure you have clover injection set to true not detect and that you have FSINJECT.efi driver from the clover driver installer selection menu -
github cloverhackycolor is the new home of clover. SVN has been demoted did's clover branch is a repository collection of svn clover builds all new development to clover will be from now on hosted on github.
-
i dont know it might be a bug in there code you would have to troubleshoot with the kext developer or try older or other versions
-
i had a similar experience with acidanthera version of vooodoops2 last night. my trackpad was super sensitive and the click buttons did not respond
-
your missing Aptiofix.efi in clover driver or you need to update it
-
i know on other trackpad kexts there are options within the kext info.plist that can be adjusted like finger z values.
-
https://www.insanelymac.com/forum/topic/339175-brcmpatchram2-for-1015-catalina-broadcom-bluetooth-firmware-upload/
-
yeah a lot has changed since 2015 when the guide was started
-
you do not need to use the *.dSYM files remove them. you might be having cache issues with the kexts maybe that's why it is intermittent. what bootloader are you using? where are your kexts located.
-
you can look through this thread
-
if Herve's DSDT did not work for you then you are most likely on a different bios revision then the DSDT he supplied in the boot pack was made with.
-
DW1820a - the general troubleshooting thread
Bronxteck replied to muttonhead411's topic in The Archive
51/53/55 are tied together to ground so probably device / manufacture specific key functions 54- is usb_otg_oc# (this looks to be USB on control) 3.3v input signal from motherboard to socket turns usb off 56- is w_disable# (this looks like wlan control) 3.3v input signal from motherboard to socket turns wlan off -
DW1820a - the general troubleshooting thread
Bronxteck replied to muttonhead411's topic in The Archive
the pins should conform to the socket spec. http://advdownload.advantech.com/productfile/Downloadfile5/1-1KJUZ5Q/M2 COM Board Design Guide V1.1.pdf -
is there anything plugged into the USB ports when this happens?
- 52 replies
-
- sleep/wakeup
- mojave
-
(and 3 more)
Tagged with:
-
did you disable the stuff in the apple power saver prefpane?
- 52 replies
-
- sleep/wakeup
- mojave
-
(and 3 more)
Tagged with:
-
https://developer.apple.com/library/archive/navigation/#section=Topics&topic=Drivers%2C Kernel%2C %26amp%3B Hardware apple's own documentation would be a good start as its from "the horses mouth" as they say.
-
DW1820a - the general troubleshooting thread
Bronxteck replied to muttonhead411's topic in The Archive
maybe compare the SSDT tables between the 50 and the 90 it is possible one has hard coded values that interfere. could probably use clover and drop tables to narrow down a suspect. -
welcome to the forum.
-
tried copying the part of the kext you need to your kext
-
update all your kexts to latest releases and if you have any patches in your clover config you probably need to update those as well
-
looks like your using smc sensor plugins remove them
-
DW1820a - the general troubleshooting thread
Bronxteck replied to muttonhead411's topic in The Archive
if it is the same physical pin connector format card then yes you would mask the pins the same way -
DW1820a - the general troubleshooting thread
Bronxteck replied to muttonhead411's topic in The Archive
usually the BT firmware gets uploaded on a cold boot and unloaded during shutdown. if you just use restart to go from OS to OS then it will not unload the previous firmware. whatever the first OS that was booted from a cold boot its BT firmware will still be loaded. that is why you should probably do a full shutdown when switching OS's. unless you desire this behavior to keep lets say the windows firmware resident for when booting OSX. but that does not mean it will like it.