Does the dosdude1 patcher install the dev build or the public beta build? Would redownloading the patcher and downloading Mojave from there give me dB5 or still pB4? I’m curious how some people here are getting dB5.
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
Does the dosdude1 patcher install the dev build or the public beta build? Would redownloading the patcher and downloading Mojave from there give me dB5 or still pB4? I’m curious how some people here are getting dB5.
I've only worked on this for a few minutes so far, but as a start point I've been looking at some Console errors that I thought were relevant.
The error Unknown CGXDisplayDevice: [x] should be ignored. It happens in High Sierra.
The error Invalid surface [x] for window [y] only happens in Mojave and I traced it to SkyLight.framework/.../SkyLight. Could somebody with a supported Mac please use Mojave for 1/2 hour and see if this error appears for you? I feel this might be the cause of transparency glitches.
The error Unknown CGXDisplayDevice: [x] should be ignored. It happens in High Sierra.
The error Invalid surface [x] for window [y] only happens in Mojave and I traced it to SkyLight.framework/.../SkyLight. Could somebody with a supported Mac please use Mojave for 1/2 hour and see if this error appears for you? I feel this might be the cause of transparency glitches.
.air is in intermediate code format specific to .metal shaders.
If you're interested read https://developer.apple.com/documen...ing_a_library_with_metal_s_command_line_tools
(graphics) Shaders are used to optimize/accelerate all kinds of special effects (like transparency and translucency) This could still be a red herring though. Plus I don't (yet) have the code...
I know adobe air takes advantage of OpenGL for fast smooth rendering same with directx for windows
Your CPU is compatible with the SSE4.2 instruction and I see no need to use the mojave patch, because it's a hachintosh, just change the SMBios in config.plist to a version compatible with mojave, like iMac 14.2, for example.
I’ll try it for you.
[doublepost=1533408228][/doublepost]
Same issue on a Mid 2012 MacBook Pro.
I did encountered too: Invalid surface posted
I have a supported Mac but in these days can't really do any test on that machine.
I guess we need to patch a SkyLight unix exec from the High Sierra one, and keeping untouched the WindowServer exec from Mojave.
edit:
@ASentientBot since you are expert in this, try replacing only the SkyLight unix exec from HS in Mojave, then try to trace any logs why it stucks after the stage2 Apple Logo.
First time I replaced all the UserEventPlugins folder, I got exactly the same behavior of this I wrote before, then re-replaced 20 from Mojave it passed the stage2 Apple Logo, later discovered the telemetry.
The funny thing is if I want to replace all the entire UserEventPlugins folder from High Sierra, on MB7,1 without keeping the Mojave (or deleting completely) "com.apple.networkextension.plugin" I stayed too on black screen after stage2 Apple Logo.
I think of a correlation even between the UserEventPlugins folder with SkyLight unix exec from High Sierra that is the much closer in size and time of development of the Mojave one.
Last edited:
@ASentientBot
I get that only once switching back and forth from dark to light: Invalid surface 4145 for window [y] in Preferences:General.
I get that only once switching back and forth from dark to light: Invalid surface 4145 for window [y] in Preferences:General.
Thank you!
So much for my idea that this was the problem, then! On to something else...
Julian - I may have missed it, but do you have a screenshot of the Light mode glitch we are chasing?
when I successfully upgraded to DP5 on my internal hdd on my iMac 9,1 I had version b12 of dosdude's Mojave patcher which is version 14014 18A3363 DP4 so when DP5 came out I originally had Mojave enrolled in the public beta so I used SWU Switcher and switched to developers beta checked the software update and successfully updated from 14014 to 14015 DP5 I think the software update scans for a install macOS Mojave beta and which version it is so if you don't have a install macOS Mojave beta it downloads the full installer. Both my macOS Mojave patcher and install macOS Mojave beta are in my applications folder
I’ll get that for you.
[doublepost=1533412141][/doublepost]
Here we are. This is light mode without reduce transparency.
For testing purposes, I made (and by made, I mean cobbled together from StackOverflow posts -- I don't know Swift) a very simple program to display a semi-transparent window, like the Finder sidebar.
And it behaves just the same as the Finder sidebar! Normal behavior in dark mode, plain grey in light mode.
Not sure if anybody wants to help trace this, but if so, here it is. Run it with swift Transparent.swift from Terminal.
And it behaves just the same as the Finder sidebar! Normal behavior in dark mode, plain grey in light mode.
Not sure if anybody wants to help trace this, but if so, here it is. Run it with swift Transparent.swift from Terminal.
This is definitely related to Metal and unfortunately as the years go by Apple will most likely start using Metal for more and more things eventually phasing out the possibility of patching it for older devices as the work required would be too complicated and/or using old drivers and other system files would break the system and thus be impossible.
That is exactly right unfortunately- wonder why they didn't make metal for these systems
when I get a chance and find my copy of El Captain and installed will check to see if it has the same 5 kexts that high Sierra uses for the iSight to see if they work in Mojave on my MacBook 5,2 without breaking the system
I can get you the KEXTs from El Capitan. Which ones do you need and where are they located?
the ones I posted on page 136 those are from high Sierra except the kextutility see if El Captain has those 5 kexts I will look but I think they are from S/L/E Edit yes they are in the system/Library/Extensions folder
Last edited:
I believe that it downloads the public beta.
Edit: On my MacBook Pro 8,2, I successfully completed an in-place upgrade of an external USB HDD containing High Sierra to Mojave 10.14 Beta (18A347e) using the installer downloaded via @dosdude1's Mojave Patcher v1.1.1, so I may be mistaken in my belief that it only downloads the public beta.
Last edited:
I think dodsdude1 said the patcher downloads the developers beta yes PB4 and DP5 are the same
Oh yeah - for sure. My Light Mode on macpro 3,1 + GTX680 is fine without transparency. The mbp5,3 however requires it (I increased contrast too) and it has a GeForce 2400M 256MB. So it's GPU/acceleration/metal (shader?) related. I think @jackluke tried swapping out the entire Skylight framework but it doesn't boot correctly. No surprises there as Skylight is a critical private framework retooled between HS and Mojave (per my previous comment)
At this point, I think the only option is to trace through the code (as @ASentientBot) suggested and glean a patch.
If it occurs on supported systems, Apple may respond to a radar - but I don't think it does (unless I'm mistaken) so fat chance of that happening.
Peeling though the object code I did find symbols related to shaders associated with ui components in dark (like toolbar) and a new addition from the HS base :
00000000002d32f0 b __ZL34_placeholder_selection_system_dark
A class dump of the Skylight binary also indicates the offending code is probably in WindowServer or a lower level framework or dylib. The Skylight class-dump looks like this:
Code:
//
// Generated by class-dump 3.5 (64 bit).
//
// class-dump is Copyright (C) 1997-1998, 2000-2001, 2004-2013 by Steve Nygard.
//
#pragma mark -
//
// File: /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight
// UUID: 25DCE5F7-0737-301F-8A27-CAB3A1AA298C
//
// Arch: x86_64
// Current version: 600.0.0
// Compatibility version: 64.0.0
// Source version: 336.8.2.0.0
//
// Objective-C Garbage Collection: Unsupported
//
@protocol MTLResource <NSObject>
@property(readonly) unsigned long long allocatedSize;
@property(readonly) id <MTLHeap> heap;
@property(readonly) unsigned long long storageMode;
@property(readonly) unsigned long long cpuCacheMode;
@property(readonly) id <MTLDevice> device;
@property(copy) NSString *label;
- (BOOL)isAliasable;
- (void)makeAliasable;
- (unsigned long long)setPurgeableState:(unsigned long long)arg1;
@end
@protocol MTLResourceSPI <MTLResource>
@property(readonly) MTLResourceAllocationInfo *cachedAllocationInfo;
@property(readonly) MTLResourceAllocationInfo *sharedAllocationInfo;
@property int responsibleProcess;
- (BOOL)doesAliasAnyResources:(const id *)arg1 count:(unsigned long long)arg2;
- (BOOL)doesAliasAllResources:(const id *)arg1 count:(unsigned long long)arg2;
- (BOOL)doesAliasResource:(id <MTLResource>)arg1;
- (void)waitUntilComplete;
- (BOOL)isComplete;
- (BOOL)isPurgeable;
@end
@protocol NSObject
@property(readonly, copy) NSString *description;
@property(readonly) Class superclass;
@property(readonly) unsigned long long hash;
- (struct _NSZone *)zone;
- (unsigned long long)retainCount;
- (id)autorelease;
- (oneway void)release;
- (id)retain;
- (BOOL)respondsToSelector:(SEL)arg1;
- (BOOL)conformsToProtocol:(Protocol *)arg1;
- (BOOL)isMemberOfClass:(Class)arg1;
- (BOOL)isKindOfClass:(Class)arg1;
- (BOOL)isProxy;
- (id)performSelector:(SEL)arg1 withObject:(id)arg2 withObject:(id)arg3;
- (id)performSelector:(SEL)arg1 withObject:(id)arg2;
- (id)performSelector:(SEL)arg1;
- (id)self;
- (Class)class;
- (BOOL)isEqual:(id)arg1;
@optional
@property(readonly, copy) NSString *debugDescription;
@end
@interface SLSessionOwner : NSObject
{
unsigned int _port;
NSNumber *_auditSessionID;
NSNumber *_sessionID;
}
+ (id)sessionOwnerForNewSessionWithAuditSessionID:(id)arg1;
+ (id)sessionOwnerForNewSessionWithAuditSessionID:(id)arg1 launchData:(id)arg2;
+ (id)sessionOwnerBySettingLoginwindowConnection:(unsigned int)arg1;
+ (id)sessionOwnerWithXPCSerialization:(id)arg1;
+ (id)sessionOwnerWithPort:(unsigned int)arg1 auditSessionID:(int)arg2 cgSessionID:(unsigned int)arg3;
@property(retain, nonatomic) NSNumber *sessionID; // @synthesize sessionID=_sessionID;
@property(retain, nonatomic) NSNumber *auditSessionID; // @synthesize auditSessionID=_auditSessionID;
@property(nonatomic) unsigned int port; // @synthesize port=_port;
@property(readonly, nonatomic, getter=isValid) BOOL valid;
- (id)createXPCSerializationAndInvalidate;
- (id)initWithXPCSerialization:(id)arg1;
- (id)initWithPort:(unsigned int)arg1 auditSessionID:(int)arg2 cgSessionID:(unsigned int)arg3;
- (void)dealloc;
@endSo some higher level code that establishes connections and sessions...
Last edited:
Boot up on a "prohibitory or stop sign"
I have this current situation on an unsupported MacbookPro 15" mid-2009 (MacbookPro5,3)
Appreciate it.
I have this current situation on an unsupported MacbookPro 15" mid-2009 (MacbookPro5,3)
- Used @dosdude1's Mojave Patcher v1.1.1. Successfully installed and patched on an external USB bootable drive.
- Rebooted on my MBP5,3, and got the prohibitory sign after showing the apple logo (on gray screen).
- Tried the USB boot drive on my MBP5,5. Same failed result.
- Tried the USB boot drive on my unsupported MBAir4,2. This one worked (booted up fine).
- Additional note: my MBP5,3 does NOT have any internal drives (will install one later). My MBP5,5 does have an internal drive. But still failed result.
Appreciate it.