-
Posts
10027 -
Joined
-
Last visited
-
Days Won
561
Content Type
Profiles
Articles, News and Tips
Forums
Everything posted by Hervé
-
Choice is extremely limited as far as M.2 cards are concerned: DW1560 (BCM4352) -> patch required DW1830 (BCM4360) -> works OOB DW1820A (BCM4350) and related -> patch required but probably best avoided given the amount of headache & trouble it's given to users; no guarantee it'll work... I know of no other M.2 cards that are fully supported. There are Atheros cards of course but Mojave dropped support for those even though Atheros cards that worked up to High Sierra can be re-used under 10.14 once the Atheros40 kext from previous macOS release is re-installed. This being said, M.2 cards based on AR946x/AR9565/AR9485 chips are not supported to the full and only operate at limited rate. They require a re-written Atheros40 kext.
-
DW1830 is a 3 x antenna cards when most M.2 cards are 2 x antennas only. If you only connect 2 x antennas to the DW1830, it'll not run at full speed.
-
Optiplex 3046: trouble booting the USB installer (High Sierra / Mojave)
Hervé replied to Trunyce's topic in The Archive
There is a full Clover pack/instructions, stated as "fully working", available in post #2 of this Optiplex 3046 thread. Since you may not be using the same version of Clover, I would suggest you 1st install Clover on your UZB installer (whatever version) and then grab the ACPI folder + Config file + kexts folder from that thread and insert them in your own EFI folder. -
It's not a train I wanted to jump on but I've now experienced the issues reported by so many people; on a Latitude E7250 that I'm working on. None of my BCM4350 cards will work in it. I've tried: 2 x DW1820A 0VW3T3 (1028:0021) models that actually work 100% Ok in my Latitude 7490 1 x DW1820A 096JNT (1028:00xx) 1 x Foxconn T77H649.00 (17aa:075a) I believe I've tried everything that had been mentionned in this thread, including the pin masking (3 @front, 2 @rear); on all 4 cards; to no avail. Given that the 2 x 0VW3T3 run perfectly in the 7490, I suspect it's not just a matter of cards but, also or instead, an issue of M.2 slot and/or ACPI definition. I'm supposed to handover the E7250 to its owner by September 1st so I don't know if I'll have sussed out the issue by then. We'll see...
-
I don't think you need to place the had-verbs in /usr/bin; 'never done it myself on any of my Hacks and they all run with AppleALC these days. You repaired permissions and rebuilt your cache after installing CodecCommander in /L/E, right?
-
It's of course framebuffer related: your graphics are not initialising. Looking at Clover's listed layout-ids for mobile SKL, you'll see the following list: As such, I have doubts about your injected layout-id 19260000. I would have expected that a setup where you fake HD530 id 8086:191b and inject layout-id 19160000 would get you there. You need to use the correct SMBIOS profile of course.
-
How did you use it? It has to go to /L/E to be cached, not injected from E/C/k/O...
-
I believe I had explained in may guide that combining compatibility with 14e4:4353 injection + boot parameter brcmfx-driver=1 caused issues to me. Try without the boot parameter. What's interesting though -and that's probably key- is that your system runs Ok if you restrict the card to 40MHz. But is that on the 5GHz or, presumably, the 2.4GHz network band?
-
Last update: 29 Aug 2019 Specifications: BIOS A21 with HDD set to AHCI mode Intel Wildcat Point LP Series 9 chipset Intel dual-core Broadwell i5-5300U 2.30GHz CPU (Turbo boost to 2.7GHz (2 cores) or 2.9GHz (1 core)) Integrated Intel HD5500 graphics (300MHz/900MHz) (PCI ven id 0x8086, dev id 0x1616) 12.5" 1366x768 HD non-touch LCD 4GB DDR3L-1600 RAM Intel I218LM Gigabit Ethernet (PCI ven id 0x8086, dev id 0x15a2) Realtek ALC293 High Def audio (PCI ven id 0x10ec, dev id 0x0293) O2 Micro SD card reader (PCI ven id 0x1217, dev id 0x8520) Internal-USB Surplus Innovation Technology webcam (PCI ven id 0x1bcf, dev id 0x28ae) 3 x USB 3.0 ports (1 x with power share) 1 x mini DisplayPort 1 x HDMI v1.4 1 x 35mm combo headset/microphone jack 1 x SmartCard reader 1 x optional NFC/fingerprint reader 1 x internal mSATA slot for SSD 1 x internal M.2 2230 WLAN slot (key A/E) 1 x internal M.2 3042 WWAN slot (key B), supports M.2 NVME SSD (eg: PCIe Gen3 x2 Toshiba RC100) but not directly bootable E7250:~ admin$ lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation Broadwell-U Host Bridge -OPI [8086:1604] (rev 09) 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) 00:03.0 Audio device [0403]: Intel Corporation Broadwell-U Audio Controller [8086:160c] (rev 09) 00:04.0 Signal processing controller [1180]: Intel Corporation Broadwell-U Processor Thermal Subsystem [8086:1603] (rev 09) 00:14.0 USB controller [0c03]: Intel Corporation Wildcat Point-LP USB xHCI Controller [8086:9cb1] (rev 03) 00:16.0 Communication controller [0780]: Intel Corporation Wildcat Point-LP MEI Controller #1 [8086:9cba] (rev 03) 00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection (3) I218-LM [8086:15a2] (rev 03) 00:1b.0 Audio device [0403]: Intel Corporation Wildcat Point-LP High Definition Audio Controller [8086:9ca0] (rev 03) 00:1c.0 PCI bridge [0604]: Intel Corporation Wildcat Point-LP PCI Express Root Port #1 [8086:9c90] (rev e3) 00:1d.0 USB controller [0c03]: Intel Corporation Wildcat Point-LP USB EHCI Controller [8086:9ca6] (rev 03) 00:1f.0 ISA bridge [0601]: Intel Corporation Wildcat Point-LP LPC Controller [8086:9cc3] (rev 03) 00:1f.2 SATA controller [0106]: Intel Corporation Wildcat Point-LP SATA Controller [AHCI Mode] [8086:9c83] (rev 03) 00:1f.3 SMBus [0c05]: Intel Corporation Wildcat Point-LP SMBus Controller [8086:9ca2] (rev 03) 01:00.0 SD Host controller [0805]: O2 Micro, Inc. SD/MMC Card Reader Controller [1217:8520] (rev 01) E7250:~ admin$ For recommended BIOS settings, see here.
-
New pack #3 posted with the missing kext added. Sorry about that.
- 4 replies
-
- dell latitude e6230
- e6230 mojave
-
(and 6 more)
Tagged with:
-
For P530, did you try faking the iGPU id of a regular HD530 instead? I have not looked but there's a chance P530's id is not included for cover by the SKL framebuffer...
-
First of all, no double post on the forum please! Did I forget or remove the USBPorts or USBInjectAll from the booptack? If so my mistake and my apologies, I'll add it later once I'm back on my E6230 Hackintosh. Meantime what you can do is download Rehabman's USBInjectAll and install it in /L/E. Repair permissions, rebuild your cache and reboot. You'll then be able to generate the USBPorts kext from Hackintool app. Regarding what you call "stock Bluetooth", I guess you mean the optional internal DW380 module, right? If you look in the earlier guides like El Capitan or Sierra, you'll see how these can be fully enabled, knowing that it is not BT 4.x but older. Mine is disabled in BIOS because I run with an Apple BCM4360CD in a mini-PCIe adapter in the WWAN slot. DW380 will work with the good old Bluetooth Transport patch + Rehabman's firmware patching kexts. I used to include the transport patch in FakeSMC (it's a little and simple injection) and you'd have to adjust it to Mojave since Apple were in the habit of changing those transport kexts every time a new OS X/macOS version came out.
- 4 replies
-
- dell latitude e6230
- e6230 mojave
-
(and 6 more)
Tagged with:
-
EDID cannot be injected "elsewhere"; it's either properly injected or not at all. But given that your wake issues also affect mouse, wireless networking and the Finder, I very much doubt that it's all EDID related.
-
-
Those BIOS settings would indeed NOT influence anything. This being said, I wrote the BIOS parameters thread when running BIOS 1.8.0; I now run with BIOS 1.11.0 and those parameters are still present, at least on my 7490... At this point of time, 1.11.0 is the lastest version posted by Dell for this model. I slightly modified the bootpack late yesterday. Install Clover as per the guide and then, afterwards, transfer the files and folder of the bootpack to the EFI/CLOVER folder of your mounted EFI partition.
-
'bit of old news but as identified here by @Sherlocks back in March, the above AppleRTC patch is no longer applicable to Mojave from version10.14.4. The code has changed even if the kext's version remained set to v2.0. The new patch to be used from 10.14.4 is: Find: 75 33 0F B7 Replace by: EB 33 0F B7 This was included to Clover's AppleRTC patch from version r4911. Patched_AppleRTC_10.14.6.kext.zip
-
The guide clearly illustrates the card's properties injection. Obviously, injecting the card's own id is useless and totally voids the desired effect which is to bypass AirPortBrcmNIC kext to load AirPortBrcm4360 instead. Can't say if your other diversions from my guide are the cause of your issue. There are many posts in the previous 14pages of this thread relating to other id reference re: compatibility and/or pin masking. Please refer to those. So many people have reported issues with those DW1820A cards by now, I feel sorry I ever recommended the model and tried to work things out.
-
dell latitude 7490 [Solved] Dell Latitude 7490 under Mojave: no webcam
Hervé replied to Eiskalt71's topic in The Archive
Well that explains a few things! -
Sure but that's not what any follower of my guide should do. In fact I was careful to be very specific on that matter: "open this EFI partition and transfer the files & folders from the Latitude 7490 Mojave Clover pack below to the EFI/Clover folder" Granted there could be confusion so I've just modified it so that there should no longer be any. All the files and folders included in the pack go to EFI/Clover folder as stated in the guide.
-
Oh that's correct, I removed it since I can not assume everyone will use a DW1820A or have one already fitted. It could be useless and, worse, conflict with a different card fitted into the slot. As such, I indeed removed the properties injection from pack #6's Clover config. I never include the CLOVERX64.efi file since it's normally installed by the Clover installation package once it's run and it may differ from one Clover version to another...
-
Can you please post your zipped copy of pack #5? I've deleted it here... I'll try and compare them in order to find out the mistake I may have made in pack #6. Thanks.
-
Hmm... I think I remember experiencing this before... from memory under Mojave... The USBPorts injector may not have been generated under the correct running conditions. Get rid of it (rebuild your cache if you installed it in /L/E or /S/L/E) and replace it byRehabman's USBInjectAll and reboot. Then try and re-generate USBPorts again. Your Clover setup and/or kexts arrangement could be incorrect too. You know the drill by now...