Bronya Posted September 17, 2013 Share Posted September 17, 2013 @bronya let's make a joint release since you helped out. Maybe . ) in the past you refused to give sources when requested, is there a reason? Sorry , my hard disk crashes . I should write new .xnu . But i have src . It is same that from AnV , but new cupid.c and tsc.c . But tsc.c no surprises . )) hey people, did you forget the decryption kext? FakeSMC or such.. ? I dont see DMOS! Maybe Single user mode? ----------------------------------- Need to patch dyld and .dylibs. fun fun. maybe we could bring back the opemu in the form of a kext. some dynamic linking voodoo would be needed for that.hmm. same don't working "singleuser" . Yes need patched *.dylibs )) Link to comment Share on other sites More sharing options...
Sinetek Posted September 17, 2013 Share Posted September 17, 2013 @Броня хорошо. here's a patched dyld http://philonlanguage.com/Sinetek/dyld_brotek Link to comment Share on other sites More sharing options...
Mohamed Khairy Posted September 17, 2013 Share Posted September 17, 2013 panic Link to comment Share on other sites More sharing options...
Sinetek Posted September 17, 2013 Share Posted September 17, 2013 ok try this one http://philonlanguage.com/Sinetek/dyld_brotek_dp1 Link to comment Share on other sites More sharing options...
Mohamed Khairy Posted September 17, 2013 Share Posted September 17, 2013 panic also as above Link to comment Share on other sites More sharing options...
Bronya Posted September 17, 2013 Share Posted September 17, 2013 Sinetek, i tested your dyld . Interesting . In vmware result: I tried on real amd , same . Link to comment Share on other sites More sharing options...
Sinetek Posted September 17, 2013 Share Posted September 17, 2013 Dooooooooohhhh of course. The code signing stuff fails now that i've changed bytes!!! Link to comment Share on other sites More sharing options...
DJ PhoeniX Posted September 17, 2013 Share Posted September 17, 2013 Can you pass it? Link to comment Share on other sites More sharing options...
Sinetek Posted September 17, 2013 Share Posted September 17, 2013 i'm not sure how anymore. gonna look into it later iirc its a simple fix Link to comment Share on other sites More sharing options...
Shaneee Posted September 17, 2013 Share Posted September 17, 2013 its patched http://philonlanguage.com/Sinetek/dyld_brotek_NOCS Link isn't available, Oops! That page can’t be found. Link to comment Share on other sites More sharing options...
Sinetek Posted September 17, 2013 Share Posted September 17, 2013 again http://philonlanguage.com/Sinetek/mv_brotek_NOCS Link to comment Share on other sites More sharing options...
Shaneee Posted September 17, 2013 Share Posted September 17, 2013 Still hanging after HFS Mount. Link to comment Share on other sites More sharing options...
Sinetek Posted September 17, 2013 Share Posted September 17, 2013 ok remains to be seen if vmware likes it Link to comment Share on other sites More sharing options...
Shaneee Posted September 17, 2013 Share Posted September 17, 2013 Same on vmware except with lots of USB messages. Link to comment Share on other sites More sharing options...
Sinetek Posted September 17, 2013 Share Posted September 17, 2013 USB is not the problem, that's just kext noise still error 13 or? Link to comment Share on other sites More sharing options...
theconnactic Posted September 17, 2013 Author Share Posted September 17, 2013 This mount HFS+ hangs baffles me. Either something changed a lot in how CPU topology and ID are defined in the commpage, or Apple developed an efficient updated way to prevent kernel binary patching (unlikely but not impossible). The same thing happens trying to boot Mavericks on my Atom netbook using the otherwise working Chameleon kernel patcher module. It would be a shame if kernel binpatching is not possible anymore: it's the only practical way we can get iCloud services, iMessage and FaceTime to work on unsupported hardware. All the best! still error 13 or? "Or". It mounts the root device and then hangs, just before launchd should appear. I think it's Mavericks' version of that annoying "Kernel is Long Point 64" hang we used to have back on Mountain Lion early kernel development days, Sinetek. All the best! Link to comment Share on other sites More sharing options...
Sinetek Posted September 17, 2013 Share Posted September 17, 2013 it's not protection, simply something fails on non intel hardware (atom has limited sse support i surmise). we had the same trouble in the good old 64bit snow leopard days. here's the lifecycle in a normal scenario: root mount (HFS messages), exec launchd ||| (kernel stops executing here). The exec portion seems to fail, so xnu goes into a loop doing nothing since it has nothing to do. during exec, a few things happen. All of this is outside kernel, which means that if an invalid opcode comes the cpu's way, we won't know as the machine will not reboot. What happens instead is exec() fails and nothing happens. Now, when the process launchd wants to start, dyld is also started (it takes care of many things relating to dynamic libraries, which any program can use). Then in turn dylibs are loaded as needed. If dyld fails to work, then the exec call fails. After dyld is loaded, dyld is called and does a memory copy operation. This memory copy operation is called _bcopy, and it has a second name, memmove. The reason is that SSE can be used to copy large amounts of data very fast. This memory copy operation takes the program on disk and populates the memory pages so that the program can be executed. If this fails, then the process will crash. Again, producing no output except perhaps an error code pointing to 'launchd'. what changed is dyld only supports ssse3 routines for memmove (there's a hack though, i tried it above). however normally the process should start by now, but the kernel can't execute it. ergo, either another .dylib needs a 'fix in or i'm missing something obvious 3 Link to comment Share on other sites More sharing options...
theconnactic Posted September 17, 2013 Author Share Posted September 17, 2013 Okay, Sinetek, but Atom fully supports ssse3. It works with Mountain Lion (by using the kernel patcher module) with no hassle at all. Link to comment Share on other sites More sharing options...
Sinetek Posted September 17, 2013 Share Posted September 17, 2013 I know, so does FX. I'm missing something obvious. you are right, it is precisely "Kernel is LP64" rearing its ugly head Link to comment Share on other sites More sharing options...
Sinetek Posted September 17, 2013 Share Posted September 17, 2013 what is this? Link to comment Share on other sites More sharing options...
spakk Posted September 18, 2013 Share Posted September 18, 2013 your last kernel does not work with my Phenom II X6, System just restart Link to comment Share on other sites More sharing options...
spakk Posted September 18, 2013 Share Posted September 18, 2013 hello spakk with phenom => ligne usb...........;bla..........bla.........bla with flag : mv -f with chameleon rev2 2252 option kernel patcher thank gils' Link to comment Share on other sites More sharing options...
carlo_67 Posted September 18, 2013 Share Posted September 18, 2013 Hello Guys I'm trying to install mavericks dp1, always having a USB lock, I'm using the kernel, mach_10_9_sinetek_by_bronzovka_fix.zip but I do not think it's the fault of the USB also tried inserting chameleon kernel patcher but nothing, goes on PS: I'm using Pandora, corecrypto changing and eliminating AppleIntelCPUPowerManagement Link to comment Share on other sites More sharing options...
carlo_67 Posted September 18, 2013 Share Posted September 18, 2013 Excuse my English Link to comment Share on other sites More sharing options...
carlo_67 Posted September 18, 2013 Share Posted September 18, 2013 Thank you, gils83 're trying, I'm confident Link to comment Share on other sites More sharing options...
Recommended Posts