[doublepost=1547710316][/doublepost]Yes the APFS firmware patch has been applied.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS 10.14 Mojave on Unsupported Macs Thread
- Thread starter dosdude1
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
If it´s still a model with CCFL backlight instead of later LED models, it might be a failing inverter.
Had this on several occasions on older MacBooks and it could be solved by replacing the small PCB in the space between the hinges of the display. In one case, temporarily and spontaneous loss of backlight was caused by a failed insulation of the high voltage cable solder joint on the CCFL tube. All the issues were similar to the ones you describe: Short backlight periods after restarting or when re-enabling backlight, flickering, dropouts.
The firmware patch on the efi chip or the efi partition?
Microsoft office can't show dark theme? it shows light theme only even selected in dark mode
You mean, you didn't use the power button trick and just hit to continue, right?
Managed to get my MacBook 4,1 (white early 2008) controlled by remote keyboard and mouse running on 10.14.3 beta.
Recap: Have not yet made progress with the broken USB (internal/external) functionality, still fumbling around with the 10.10.5 kexts to no avail.
As I´ve been very curious about finally seeing performance on such an un-accelerated machine (GPU), I tried some different approach:
- booted the 4,1s internal drive on a machine that Mojave works on
- installed Teleport 1.2.2 (special Mojave build)
- set Auto-Login to prevent password entry
- added Teleport to user login startup items and set Teleport to auto-accept incoming remote requests
then
rebooted the MB 4,1 with this setup, connected my 17" MB Pro, started Teleport there also and hooked up both machines per ethernet cable.
The result is astonishing. The x3100 intel GPU is fully recognized, full frame buffer (144MB) is used and at least the normal GUI/window/dock/side panel stuff is absolutely fluid. Lauchpad is much slower as it heavily relies on accelerated GPU usage, but once onscreen it is still usable.
See screenshot as a proof of concept - I hope that it triggers some more enthusiasm in the patcher community now (help greatly appreciated for more ideas what could be done to get onboard USB controller working...)
Edit: Anyone interested in the Mojave build of Teleport: Link here https://github.com/abyssoft/teleport/files/2414046/teleport_1.2.2.zip
Recap: Have not yet made progress with the broken USB (internal/external) functionality, still fumbling around with the 10.10.5 kexts to no avail.
As I´ve been very curious about finally seeing performance on such an un-accelerated machine (GPU), I tried some different approach:
- booted the 4,1s internal drive on a machine that Mojave works on
- installed Teleport 1.2.2 (special Mojave build)
- set Auto-Login to prevent password entry
- added Teleport to user login startup items and set Teleport to auto-accept incoming remote requests
then
rebooted the MB 4,1 with this setup, connected my 17" MB Pro, started Teleport there also and hooked up both machines per ethernet cable.
The result is astonishing. The x3100 intel GPU is fully recognized, full frame buffer (144MB) is used and at least the normal GUI/window/dock/side panel stuff is absolutely fluid. Lauchpad is much slower as it heavily relies on accelerated GPU usage, but once onscreen it is still usable.
See screenshot as a proof of concept - I hope that it triggers some more enthusiasm in the patcher community now (help greatly appreciated for more ideas what could be done to get onboard USB controller working...)
Edit: Anyone interested in the Mojave build of Teleport: Link here https://github.com/abyssoft/teleport/files/2414046/teleport_1.2.2.zip
Last edited:
Amazing work!! While I doubt it'll be useful in real-world situations, it's awesome that you managed to get it booting and with usable framebuffer! If I remember correctly, the full graphical drivers are 32-bit only except in a certain build of Snow Leopard, I believe. I don't know if you'll ever get that working, though, and I don't know the details. I've just seen it mentioned in passing in the Hackintosh world.
What have you tried for USB so far? I would obviously try bringing over 64-bit kexts from Lion/Mavericks/Yosemite/whatever OS version you most recently had functioning USB on. Have you done that? Do they load? If not, what is the output of kextutil when you try to load them? -- might just need to copy dependencies or create something like NDRVShim.
Again, awesome work! Even if it's not super practical, it's cool as heck!
[doublepost=1547770439][/doublepost]Also -- silly question -- I've been trying to archive every beta update's associated software catalog files, but I missed beta 3. Beta 4 came out before I got a chance to grab the files. If anyone has a copy, I'd really appreciate a PM. I figure that having a complete collection in one place may turn out to be useful. Thanks!
Has anyone upgrading their Airport Card run into this issue? I purchased an Airport BCM94360CS2 card on an PCI-E adapter card...
https://www.ebay.com/itm/802-11AC-B...390688?hash=item3afea5ef20:g:qnUAAOSw-RhaY2u5
and am unable to get either the MacPro 3,1's antenna connectors or the ones that shipped with the card to attach. Am I correct to assume that these MacBook Air Airport cards use smaller antenna connectors than those on the PCI-E size cards? If so, is there such a thing as an adapter cable for changing sizes?
I suspect this might be what I need...
https://www.ebay.com/itm/IPX-MHF4-p...=item282cef53c6:g:vvUAAOSwTuJYtDMn:rk:13:pf:0
https://www.ebay.com/itm/802-11AC-B...390688?hash=item3afea5ef20:g:qnUAAOSw-RhaY2u5
and am unable to get either the MacPro 3,1's antenna connectors or the ones that shipped with the card to attach. Am I correct to assume that these MacBook Air Airport cards use smaller antenna connectors than those on the PCI-E size cards? If so, is there such a thing as an adapter cable for changing sizes?
I suspect this might be what I need...
https://www.ebay.com/itm/IPX-MHF4-p...=item282cef53c6:g:vvUAAOSwTuJYtDMn:rk:13:pf:0
Last edited:
Good work, apparently you have done all the possible attempts and it seems there is no way to use IOUSB HID (no Webcam, no USB ports, no BT and so on) on those machines (with at least an ethernet port) fully supported until 32 bit Lion, I didn't knew teleport, amazing app, and of course you need to use it through RJ45 cable since you can't use neither any USB Wifi dongle, but it's better than using a remote desktop to that "Mojave machine", so again good work.
Thanks. I still have a slight hope that the right combination and fix of dependencies of the right kexts could still get USB running - based on the fact and experience that 10.10.5 does indeed run on this machine with the patches from the MacPostFactor era. My mistake until now could be that I tried to get the original Yosemite kexts to work on the MB 4,1 instead of the already modified ones from a "MB 4,1 / Yosemite" setup. Will have another look into that as soon as I have a second 4,1 running Yosemite again...
Other ideas and participants with MB 4,1 machines more than welcome! ;-)
In the meantime I fixed Wifi by using a supported AirPort PCIe card, so real Ethernet cable is not necessary any longer, as Teleport also works in the same Wifi network.
Edit:
Another small progress: Got audio up and running with the old two kexts from OSXhackers.
Last edited:
Hi, sorry to hear your upgrade is not going smoothly. Just checked the card (BCM 94360CD) in my mp3.1 and it has U.Fl connectors. So the Mac Pro's antenna are fitted with U.FL. As you rightly suspect, the MD air's use MHF4 mini connectors so they are different. Both are a fiddle to get on! Strange that the supplied antenna do not fit. I had a quick look at the links to the card. I see it only has 2 aerial connectors (1 x BT ,1 x wifi). You may consider a card with 4 connectors such as the BCM 94360CD ( 1 x BT, 3 x wifi) as the old Mac Pros thick aluminium case has been blamed for some BT/wifi issues so using all the aerials would be advisable in the upgrade. The 94360 also has U.Fl connectors. Here is a link to one like I used. Expensive but I got one much cheaper on eBay. https://www.osxwifi.com/product/mac...94360cd-802-11-a-b-g-n-ac-with-bluetooth-4-0/
Last edited:
I believe Mojave core extensions are more similar to El Capitan than Yosemite, so I guess it will be hard to support those IOUSB kexts.
Instead would be interesting if there is an Airport Combo BT/Wifi all-in-one that fits in shape/size connector so that BT is detected through PCIEx Wifi interface and not internal USB, in that case you could avoid even teleport app, using BT mouse/keyboard.
Technically you can already avoid teleport using some Remote mouse/keyboard app through Wifi, there are many apps around letting you to control through smartphone connected on the same wifi network.
Good ideas, had the PCIe USB card thought also, but it would mean to re-route the USB jacks internally. Feasible, but quite a hack.
El Cap kexts did not work (seemed to have loaded, but no connection to MB 4,1 hardware it seemed), that´s why I tried to go for the Yosemite kexts. I´ll have to go further back, I assume... (or see, with what kexts Yosemite runs on the MB4,1 - which it actually does by the OSXhackers patches).
What happens if you kextutil the kexts from the OS X Hackers? Perhaps you can figure out what are their dependencies and resolve that.
The funny thing is that the antenna connectors that shipped with the kit don't even seem to fit. So either I am lousy at attaching the connectors or they shipping MHF3 connectors on the antenna by accident.
Strange. I've gotten Macbooks from 2,1 to 4,1 running El Cap, and all hardware is supported with the exception of graphics acceleration (framebuffer is working on all three). The kexts must be tied to the kernel somehow, so maybe Apple has removed support for the older hardware in the Mojave kernel, and attempting to load older kexts just pukes out due to this support removal.
Regardless, impressive work!
(All pre-coffee musing here, so take it for what it is...)
Yes it can! But you need the latest Office v16.20, 2019 version, since it has native support for dark theme.
Theorically the "main" required kexts to load legacy USB devices are two: IOUSBHostFamily.kext and IOUSBFamily.kext
but don't forget that inside their Contents there is an important Plugins folder that contain dozens of other USB related kexts.
Maybe on a working patched Mojave I would check which other dependencies are required for kext loading for example:
sudo kextlibs /System/Library/Extensions/IOUSBFamily.kext
And as you stated earlier this one involved is strictly dependent: IOPCIFamily.kext, but it's very tricky to handle with, I think.
Last edited:
I've come to the conclusion that the MHF4 connectors are just to fragile to my taste so I plan on just soldering a lead with female U.FL connectors onto two MHF4 sockets on the card.
Impressed with your efforts on this. Let me know how it is when you get it working. Would be interested if Mojave plays straight with the new card. Most of us who have upgraded to a Wifi/BT combo card have found that the BT is not recognised properly. Be prepared to use HS 13.6 kexts - In my case IOBluetoothFamily.kext and IOBluetoothHIDDriver.kext worked for 14.0 but for 14.1 and 14.2 both these kexts and IOACPIFamily were needed get BT fully up and running. Whilst you are delving inside the Mac try to find the 3rd wifi aerial lead. Follow the other leads and it will be be behind the hard drive splines. The connector will be covered in insulation tape to stop it shorting on the main board. Remember to do this for your unused aerial leads. If using one aerial gives you a poor wifi performance try swapping the aerial leads. Not sure which one goes where in the Mac Pro but one may work better for you than the others.
it's supported since v.16.20 and it changes automatically when you switch to dark mode in system preferences.
Edit: @Sveto has been faster
Hi,
I've installed Mojave on a Macbook Pro late 2011 and a Mac Pro 2008 (3.1). It works like a charm on my MacBook Pro but I got a lot of issues on my Mac Pro. Graphic issues even if I have a compatible Nvidia graphic card. Applications crashes (Logic Pro 10.4.2), wifi not working anymore. I had High Sierra running perfectly before trying to install Mojave on my Mac Pro 3.1.
Also, know that I took out the SSD of the Mac Pro and installed the Mojave Patch from my MacBook Pro, but I choose Mac Pro 3.1 when I got the configuration window.
Any Idea ? Also, is it possible to downgrade to High Sierra ?
Thanks for any help.
I've installed Mojave on a Macbook Pro late 2011 and a Mac Pro 2008 (3.1). It works like a charm on my MacBook Pro but I got a lot of issues on my Mac Pro. Graphic issues even if I have a compatible Nvidia graphic card. Applications crashes (Logic Pro 10.4.2), wifi not working anymore. I had High Sierra running perfectly before trying to install Mojave on my Mac Pro 3.1.
Also, know that I took out the SSD of the Mac Pro and installed the Mojave Patch from my MacBook Pro, but I choose Mac Pro 3.1 when I got the configuration window.
Any Idea ? Also, is it possible to downgrade to High Sierra ?
Thanks for any help.
Logic might need to access your microphone within the security pane in system preferences. It's a common issues with other DAW in Mojave. Even if it just says 'microphone' other audio inputs are included.
(I don't use Logic but see the screenshot attached)