-
Posts
10013 -
Joined
-
Last visited
-
Days Won
560
Content Type
Profiles
Articles, News and Tips
Forums
Everything posted by Hervé
-
A few comments... a) IORegistryExplorer screenshot you attached shows info leading to believe you've not implemented the settings recommended in the guide: name + device-type show being set to "Airport" model shows being set to "AppleWifi Card" which is indicative of Clover "FixAirport" remaining enabled. You don't need this and I did ask you to remove this from your Clover config no kext loaded for your card which is indicative of a highly likelihood that some non-vanilla kexts remain on your system. b) But it's a red herring because on looking into your attached debug pack, I can see that: Clover config is now 100% Ok IOReg output shows all properties correctly injected but no kext loaded for the card Kextcache shows you kept an older and inappropriate IO80211Family kext in /S/L/E despite being specifically told to revert to the vanilla kext Revert to a full vanilla installation as requested before by re-instating the original IO80211Family kext in /S/L/E. Once you've done that, you card will work perfectly. NB: Kextcache log also shows how much you messed up with kexts: you've installed some add-on kexts in /S/L/E, some in /L/E, some in both. That's the best recipe for disaster! Only install add-on kexts to /L/E. Remove all those you installed in /S/L/E, repair permissions and rebuild you cache. Lilu -> LE + SLE AppleALC -> SLE ACPIBatteryManager -> LE + SLE BrcmPatchRAM2 -> LE + SLE BrcmFirmwareRepo -> LE + SLE And that's on top of injecting those same kexts through Clover (where you've also added unnecessary or competing kexts: AtherosE2200Ethernet / IntelMausiEthernet / RealtekRTL8111, ACPIBatteryManager / SMCBatteryManager, etc.). You really ought to use the correct add-on kexts and decide what you want to do with them: cache them (from /L/E) -which is recommended- or inject them (from E/C/k/O). Just don't duplicate or triplicate stuff...
-
You should use Cover Configurator app; the guide is quite clear on that matter... Anyway, remove the FixAirport Clover option (your initial IOReg text output shows the card under RP05@1c->PXSX@0) remove that old IO80211Family kext you were trying to inject remove AirportBrcmFixup and post a new debug package with an IORegistryExplorer saved output (IOReg text output is no pleasant read). If DPCIManager app sees the card in IOReg, IORegistryExplorer will too! You're either missing it or doing something wrong. I assume that Wireless + Bluetooth are enabled in BIOS.
-
Yes, partitions are usually reduced or increased from their end not their beginning. Unless there are specific tools that allow to basically "move" a partition, it's impossible to free-up disk space ahead of a given partition to give the recovered disk space to that partition. What you'd have to do now is clone your existing partition onto the 1st/new one and then, you'd be able to delete that initial 2nd partition to recover the disk space and re-allocate it to the 1st one on disk.
-
Look at our BCM4350 guide in Wireless section. But 1st check the model you have...
-
I've no idea then. Nothing looks wrong on the Clover setup. That leaves the question of a full vanilla installation or not...
-
If you're using latest Lilu + WEG, you don't need to set "Inject Intel" + "ig-platform-id 0x01660003" in Clover->Graphics section. Also, remove Drop OEM SSDT from ACPI section.
-
DW1510 remains fully supported in Mojave. But it's a half-size mini-PCie card and the E5470 WLAN slot is NGFF/M.2... Pray that yours comes with the correct DW1820A...
-
Ok, so you're caching some kexts from /L/E and injecting most add-on kexts from Clover E/C/k/O. You should probably cache all your add-on kexts from /L/E, knowing that you can then keep exising kexts in Clover's Other folder and set kext injection to "Detect". In that mode, Clover only injects kexts if FakeSMC is not in /L/E. You appear to run audio with AppleALC so get rid of that AppleHDA-IDT kext you've installed in /L/E. Once you've copied all your kexts to /L/E, repair permissions and rebuild your cache.
-
[Solved] MC7710 on mojave 10.14 can't connect
Hervé replied to antizo's topic in Modems/WWAN modules
Sorry, 'never heard of it. -
Setting kexts injection to "Detect" is fine. The question is: do you know what this does/do you know how kext injecton works? Hence the need to know where you placed FakeSMC... Did you install any kexts in /L/E?
-
[Solved] MC7710 on mojave 10.14 can't connect
Hervé replied to antizo's topic in Modems/WWAN modules
So the main change was the uninstallation of the SierraWireless drivers. The WWAN icon may simply refer to a different piece of previously registered hardware from when you had the SierraWireless drivers installed. It may be like when you choose show the Bluetooth icon in the menu bar and then remove or disable the Bluetooth hardware: the icon stays there but is unusable. Try and uncheck the box used to display the icon, then recheck it afterwards. -
Ok but do you inject or cache kexts (latter recommended)? Where is FakeSMC?
-
That difference in "About this Mac" is just language related and is totally irrelevant to your DRM predicament. If you switched to English you'd have the "graphics" word in the report. The DRM/green screen issue was normally solved by Shiki kext, which is now integrated in WEG Lilu PlugIn, so all should be ok on that front.
-
[Solved] MC7710 on mojave 10.14 can't connect
Hervé replied to antizo's topic in Modems/WWAN modules
That "Key" field is just like a title, so if that's the only thing you modified, it's not possible that it made a change in terms of operations; you must have changed something else. In addition if you opted to modify the vendor id of your dedicated entry from 0x1199 (i.e. 4505 in decimal) to 0x(0)199 (i.e. 409 in decimal), then your dedicated entry no longer applies to your hardware (its ids obviously will not change!) and another profile is being used instead... -
Dell Latitude E6530 Mojave(10.14.4) did not detect Trackpad
Hervé replied to npyadav1's topic in The Archive
Really? I found no particular issue on that front but maybe I have a more masculin touch on the TrackPad! You can always try to adjust the Info.plist parameters (tresholds, ZLimit, etc.) of the VoodooPS2TrackPad PlugIn of the kext. You may also compare them with Rehabman's kext and see if there is an obvious difference somewhere. Do not forget you can also adjust some settings through the... TrackPad PrefPane of course! -
Not the best choice of DW1820A unfortunately. You probably won't get wireless working with that one...
-
May be your ought to have a much closer look at the properties you're injecting...
-
Mojave on the Precision m6700 - Need some help with sleep and Nvidia GPU
Hervé replied to katana9x99's topic in The Archive
Sleep is not only affected by hibernation mode, it also heavily relies on fully working CPU power management; you don't have that at the moment. Proceed as follows: generate your CPU-specific power management SSDT with Pike R Alpha's well-known generator script (you can Google for it) and place the resulting ssdt.aml file in Clover's ACPI/patched folder. using Clover Configurator app, drop SSDT CpuPm + SSDT Cpu0Ist tables. using Clover Configurator app, select an appropriate quad-core i7 IvyBridge MacBookPro9,x/10,x SMBIOS instead of that incorrect desktop iMac14,2 you currently use and, of course, remove that NullCPUPowerManagement kext you've added to your Clover kexts folder since that completely kills off CPU power management and will prevent Sleep. -
Lite-On WCBN808B: According to Wikidevi, DW1820A are manufactured by Lite-On with part # WCBN808B. I was not able to verify this for certain and could not find any specific info for a Lite-On WCBN808B card but this number is printed at the back of my Dell DW1820A 0VW3T3 cards. I also found a Lenovo card (FRU 00JT493) carrying that WCBN808B reference on its front label. That card is definitely based on BCM4350 chipset. Afaik, it's not been tested yet but I'll try to get one too. Untested So, as it turns out so far, WCBN808B reference is printed on: Dell's CN-0VW3T3 Dell's CN-096JNT Dell's CN-08PKF4 Lenovo's 00JT493 It is not printed on: Foxconn's T77H649
-
Last Update: 6th Jan 2020 Foxconn T77H649.00: Ok Foxconn T77H649.00 appears mostly offered with Lenovo laptops and carries Lenovo FRU (i.e. part #) 00JT494. The cards carries the usual Broadcom PCI id 14e4:43a3 and subsystem id 17aa:075a. - - - - - - - - - - Edit: 06 Jan 2020 This Foxconn T77H649 works perfectly with ASPM disabled through bootloader property injection under the associated device address: Key = pci-aspm-default | Value = 0 | Type = NUMBER ASPM disabling appears mandatory with this card to avoid CPU overloading and system freeze after a few minutes.
-
Dell Latitude E6530 Mojave(10.14.4) did not detect Trackpad
Hervé replied to npyadav1's topic in The Archive
It will if you install or inject Dr Hurt's VoodooPS2Cntroller R6 compiled by Bronxteck. Look it up on p1 of Dr Hurt's PS2 controller kext thread in R&D->Kexts section. -
Your kexts set is incorrect: you're injecting AppleALC (for audio) and that's all you need. Get rid of those VoodooHDA + patched AppleHDA kexts you're trying to inject too. Re: USB, I did not see any ACPI folder in that Clover folder of yours so it's difficult to know if you are injecting a patched DSDT + a CPUPM SSDT for your CPU. If your USB ports are not all working, proceed as follows: Download latest Clover Configurator app Edit your config.plist with CC Properly inject MBP9,2 SMBIOs (right now it's an empty shell) In ACPI section, addd renaming of EHC01/EHC02 to EH01/EH02
-
For BT, just install Rehabman's BrcmFirmwareRepo + BrcmPatchRAM2 kexts. Nothing else. I've specified the model of Webcam fitted to my 7490 in my guide and yours clearly is a different model.
-
Tap to click option is not enabled by default in the TrackPad PrefPane; you have to set it manually. DW1560 is probably the best alternative if you cannot get a DW1820A 0VW3T3 model. Latitude 7490 only has 2 x antennas cables going to the WLAN slot. Any other M.2 cards based on Broadcom BCM4352 chipset should work too: AzureWave AW-CB162NF, Foxconn T77H543.00, Lite-On WCBN802B.
-