luxinhaus Posted March 5, 2015 Share Posted March 5, 2015 @ErmaC Tried the 2584_v2 and it works, no KP Sorry for the late reply. had to prepare for work 1 Link to comment Share on other sites More sharing options...
Micky1979 Posted March 5, 2015 Share Posted March 5, 2015 Urrà! Link to comment Share on other sites More sharing options...
luxinhaus Posted March 5, 2015 Share Posted March 5, 2015 (edited) What i mean by "after 2510" was another issue "AllocateKernelMemory error" by a user posted here Going back to the 2nd issue... Its also happening "randomly". new boot boot0 boot1h installed Could it be this #2540 ? I see that it was fixed in commit 2554 but later on rolled back in commit 2565 I will test and give you feedback by changing the value again... hold on since the issue occurs "randomly" Edited March 5, 2015 by luxinhaus Link to comment Share on other sites More sharing options...
ErmaC Posted March 5, 2015 Author Share Posted March 5, 2015 The rollback was made because is not safe. Zenith432 point me out on this potentials problem... Here the snippet explanations The change to memory.h in commit r2554 is not safe. The ZALLOC area (used for malloc) now overlaps the LOAD_ADDR area, which is used as a buffer for loading files. If you shift LOAD_ADDR and PREBOOT_ADDR up - there's another problem. The memory layout is planned for using 512MB, and the code does not consult the BIOS memory map (retrieved with getMemoryMap()) to see that it's only using free memory. So the code should not be loosely expanding its use of memory without consulting bios memory map... ErmaC Link to comment Share on other sites More sharing options...
luxinhaus Posted March 5, 2015 Share Posted March 5, 2015 (edited) hmmmm , guess il investigate more This is FUN Let me explain what i mean by "randomly"...installed the new 3 boot files and it works on the first restart, but will fail on the 2nd restart.To fix it, i have to boot from a stick (old revision) then install again the same new 3 boot files then restart and it will work, but the issue will accur again on the 2nd restart.Thinking that maybe its only my HD, I made a fresh install on one of my spare unit and still the issue persist.Note: Revision 2510 doesn't have this issue New Pic: *********************************************************************** Update: I found it! 2560 = Good 2561 = Instant restart after kexts are being force loaded by the bootloader ( i don't have -f ) 2561 = AllocateKernelMemory error starts in this revision all the way to the latest (2584 / 2587) 2562 = AllocateKernelMemory error starts in this revision all the way to the latest (2584 / 2587) Edited March 5, 2015 by luxinhaus 2 Link to comment Share on other sites More sharing options...
ErmaC Posted March 5, 2015 Author Share Posted March 5, 2015 Update: I found it! 2560 = Good 2561 = Instant restart after kexts are being force loaded by the bootloader ( i don't have -f ) 2561 = AllocateKernelMemory error starts in this revision all the way to the latest (2584 / 2587) 2562 = AllocateKernelMemory error starts in this revision all the way to the latest (2584 / 2587) Nice! Pls try this precompiled binaries 2560 (include the fake_efi.c fix and ZALLOC_LEN in memory.h set again to 0x10000000) --> 2561 (same fix as for 2560 and correct the logic how chameleon match the finded version of OS X) --> 2562 (same fix as for 2561) --> 2584 (Current/latest trunk from SVN with same fix as 2561) --> let me know ErmaC Link to comment Share on other sites More sharing options...
luxinhaus Posted March 5, 2015 Share Posted March 5, 2015 (edited) @ErmaC No changes 2560 = 2561 = kexts are being force loaded ( -f ) by the bootloader then instant reboot. Its like a CPU not supported by kernel that gives you instant reboot 2562 = AllocateKernelMemory error 2584 = AllocateKernelMemory error Edited March 5, 2015 by luxinhaus Link to comment Share on other sites More sharing options...
ErmaC Posted March 5, 2015 Author Share Posted March 5, 2015 @ErmaC No changes 2560 = 2561 = kexts are being force loaded ( -f ) by the bootloader then instant reboot. Its like a CPU not supported by kernel that gives you instant reboot 2562 = AllocateKernelMemory error 2584 = AllocateKernelMemory error 2561_V2 (change again the logic about the version of OS X is checked) --> ErmaC Link to comment Share on other sites More sharing options...
luxinhaus Posted March 5, 2015 Share Posted March 5, 2015 (edited) @ErmaC 2561_V2 reboots instantly. it doesnt even try to read or load the kexts This might help since i have most of the OS setup in here. SnowLeopard = Mountain Lion = reboots instantly Mavericks = reboots instantly Yosemite = reboots instantly Edited March 5, 2015 by luxinhaus Link to comment Share on other sites More sharing options...
ErmaC Posted March 5, 2015 Author Share Posted March 5, 2015 @ErmaC 2561_V2 reboots instantly. it doesnt even try to read or load the kexts This might help since i have most of the OS setup in here. SnowLeopard = Mountain Lion = reboots instantly Mavericks = reboots instantly Yosemite = reboots instantly (OS X check again...) 2561_V3 -> ErmaC Link to comment Share on other sites More sharing options...
luxinhaus Posted March 5, 2015 Share Posted March 5, 2015 (edited) @ErmaC V3 now works ************************************************ Next and last issue is AllocateKernelMemory Im definitely sure that AllocateKernelMemory error live in 2562 As commit says "Added ability to auto-select last booted partition as the boot volume" and thats what i was saying about 2nd restart issue in here: Let me explain what i mean by "randomly"...installed the new 3 boot files and it works on the first restart, but will fail on the 2nd restart.To fix it, i have to boot from a stick (old revision) then install again the same new 3 boot files then restart and it will work, but the issue will accur again on the 2nd restart. Il take a break first.. be back later Thank you so much for the patience Ermac Edited March 5, 2015 by luxinhaus 1 Link to comment Share on other sites More sharing options...
ErmaC Posted March 5, 2015 Author Share Posted March 5, 2015 V3 now works Good! Next and last issue is AllocateKernelMemory Im definitely sure that AllocateKernelMemory error live in 2562 As commit says "Added ability to auto-select last booted partition as the boot volume" and thats what i was saying about 2nd restart issue in here: 2562_V1 (same OS X check as for 2561_V3) -> If the problem described still "alive" maybe I add a keyFlag or need a better implementation. ErmaC 1 Link to comment Share on other sites More sharing options...
Micky1979 Posted March 5, 2015 Share Posted March 5, 2015 @ErmaC V3 now works My new Friend, I love you Link to comment Share on other sites More sharing options...
luxinhaus Posted March 6, 2015 Share Posted March 6, 2015 Good! 2562_V1 (same OS X check as for 2561_V3) -> i386_2562_V1.zip If the problem described still "alive" maybe I add a keyFlag or need a better implementation. ErmaC 2562_V1 = AllocateKernelMemory error My new Friend, I love you Hey Mickey1979, Thanks for accepting 1 Link to comment Share on other sites More sharing options...
ErmaC Posted March 9, 2015 Author Share Posted March 9, 2015 2562_V1 = AllocateKernelMemory error Not too bad... expected problem... Here other version with "some" of the 2562 changes are been removed... 2562_V2 --> ErmaC Link to comment Share on other sites More sharing options...
Micky1979 Posted March 9, 2015 Share Posted March 9, 2015 Hi Guys, good to see you all again ...and good work! Link to comment Share on other sites More sharing options...
luxinhaus Posted March 9, 2015 Share Posted March 9, 2015 Not too bad... expected problem... Here other version with "some" of the 2562 changes are been removed... 2562_V2 --> i386_2562_V2.zip ErmaC We are back! I missed you alll!!! 2562_V2 = Good! Link to comment Share on other sites More sharing options...
chris1111 Posted March 10, 2015 Share Posted March 10, 2015 Really proud to present my BUILD I compile and build with Xcode my own Chameleon-2.3svn-r2587 Special Edition.pkg Support OS X USB installer and Kernel Extractor Its a Standard Package No EFI I have boot on the Installation in my first attempt Chameleon Install Log Chameleon installer log - Mon Mar 9 22:35:03 EDT 2015Installer version: 2.3svn 2587======================================================/dev/disk0#: TYPE NAME SIZE IDENTIFIER0: GUID_partition_scheme *120.0 GB disk01: EFI EFI 209.7 MB disk0s12: Apple_HFS SSD_OCZ 119.7 GB disk0s2/dev/disk1#: TYPE NAME SIZE IDENTIFIER0: GUID_partition_scheme *240.1 GB disk11: EFI EFI 209.7 MB disk1s12: Apple_HFS Macintosh HD 239.2 GB disk1s23: Apple_Boot Recovery HD 650.0 MB disk1s3/dev/disk2#: TYPE NAME SIZE IDENTIFIER0: GUID_partition_scheme *1.0 TB disk21: EFI EFI 209.7 MB disk2s12: Apple_HFS BACKUP 999.9 GB disk2s2/dev/disk3#: TYPE NAME SIZE IDENTIFIER0: GUID_partition_scheme *500.1 GB disk31: EFI EFI 209.7 MB disk3s12: Apple_HFS HDD 500 499.8 GB disk3s2/dev/disk4#: TYPE NAME SIZE IDENTIFIER0: GUID_partition_scheme *500.1 GB disk41: EFI EFI 209.7 MB disk4s12: Apple_HFS HDD 499.8 GB disk4s2======================================================Backup Chameleon files======================================================Clearing options...======================================================Running Standard postinstall scriptTarget volume = /Volumes/HDD on /dev/disk4s2======================================================Written boot0 to /dev/disk4.Written boot1h to /dev/rdisk4s2.Written boot to /Volumes/HDD on /dev/disk4s2.======================================================Preparing to check target disk for previous installations.Going to check the EFI system partition also.Mounting /dev/disk4s1 as /Volumes/EFI.Checking disk4.Nothing found that could cause any problems.======================================================Disk: /dev/rdisk4 geometry: 60801/255/63 [976769024 sectors]Signature: 0xAA55Starting Ending#: id cyl hd sec - cyl hd sec [ start - size]------------------------------------------------------------------------1: EE 1023 254 63 - 1023 254 63 [ 1 - 976769023]2: 00 0 0 0 - 0 0 0 [ 0 - 0] unused3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused4: 00 0 0 0 - 0 0 0 [ 0 - 0] unusedSetting /Volumes/HDD partition active.======================================================Standard script complete======================================================Added boot option: Instant Menu=YesAdd: ":Instant Menu" Entry Already ExistsAdded boot option: ShowInfo=YesAdd: ":ShowInfo" Entry Already ExistsAdded boot option: Kernel Flags=-vAdded boot option: Kernel Flags=darkwake=0Added boot option: Kernel Flags=dart=0Added boot option: Graphics Mode=1024x768x32Add: ":Graphics Mode" Entry Already Exists======================================================Running Post postinstall scriptTarget volume = /Volumes/HDD==============================================="/Volumes/EFI" unmounted successfully.boot file hidden /Volumes/HDD/boot13786138 blocks"disk5" unmounted."disk5" ejected.======================================================Extracting kernelRemove Extractor======================================================Post postinstall script complete Thanks to ErmaC / Andy / Minuzwei / / Pike / meklort / Mickey1979 and all of devs for contributing to this amazing Project 1 Link to comment Share on other sites More sharing options...
bundpard Posted March 10, 2015 Share Posted March 10, 2015 I get instant reboot with 2562_V2 For filenvram, are we using just the dylib or does the kext have to be installed too? Link to comment Share on other sites More sharing options...
luxinhaus Posted March 10, 2015 Share Posted March 10, 2015 (edited) I get instant reboot with 2562_V2 For filenvram, are we using just the dylib or does the kext have to be installed too? Are you sure its a bootloader and not your CPU that having the reboot issue? Because the reboot issue that we just fixed was caused by a bad commit made some time ago and not CPU related. Can you try the file in post #2742 Opps attachment is broken... here 2561.zip Edited March 10, 2015 by luxinhaus Link to comment Share on other sites More sharing options...
bundpard Posted March 10, 2015 Share Posted March 10, 2015 It works soon as I remove the filenvram.dylib from modules... will try again with above version Link to comment Share on other sites More sharing options...
luxinhaus Posted March 10, 2015 Share Posted March 10, 2015 It works soon as I remove the filenvram.dylib from modules... will try again with above version You have different issue then. Fill up your Signature Link to comment Share on other sites More sharing options...
ErmaC Posted March 10, 2015 Author Share Posted March 10, 2015 2562_V2 = Good! Could you try the trunk revision 2605 from the SVN? ErmaC Link to comment Share on other sites More sharing options...
luxinhaus Posted March 10, 2015 Share Posted March 10, 2015 (edited) @ErmaC 2605 from the SVN = On a side note on compiling: xcode 6 = old xcode = ( starts at 2588 up to 2605) [CC] interrupts.c interrupts.c:162:43: error: unexpected directive .code16 __asm__ volatile ("calll __prot_to_real\n\t" ^ <inline asm>:2:2: note: instantiated into assembly here .code16 ^ interrupts.c:162:43: error: .code16 not supported yet __asm__ volatile ("calll __prot_to_real\n\t" ^ <inline asm>:2:9: note: instantiated into assembly here .code16 ^ interrupts.c:150:31: error: unexpected directive .code16 "calll __prot_to_real\n\t" ^ <inline asm>:3:2: note: instantiated into assembly here .code16 ^ interrupts.c:150:31: error: .code16 not supported yet "calll __prot_to_real\n\t" ^ <inline asm>:3:9: note: instantiated into assembly here .code16 ^ 4 errors generated. make[3]: *** [/Users/Batman/Desktop/trunk2605/obj/i386/libsa/interrupts.o] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Edited March 10, 2015 by luxinhaus Link to comment Share on other sites More sharing options...
Zenith432 Posted March 10, 2015 Share Posted March 10, 2015 You can update the assembler by downloading latest cctools, build 'as' and install over existing assembler. old xcode = ( starts at 2588 up to 2605) 1 Link to comment Share on other sites More sharing options...
Recommended Posts