Jump to content

Chameleon 2.4svn Official PKG Installer


ErmaC
4,261 posts in this topic

Recommended Posts

What i mean by "after 2510" was another issue "AllocateKernelMemory error" by a user posted here

Going back to the 2nd issue...

 

post-1406307-0-37207900-1425515380_thumb.jpg

post-1406307-0-64761500-1425515399_thumb.jpg

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 by luxinhaus
Link to comment
Share on other sites

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

hmmmm , guess il investigate more :)
This is FUN :D

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:

post-1406307-0-67853900-1425526731_thumb.jpg

 

***********************************************************************

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 by luxinhaus
  • Like 2
Link to comment
Share on other sites

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

@ErmaC

 

No changes

 

2560:thumbsup_anim:

2561:thumbsdown_anim:  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:thumbsdown_anim: AllocateKernelMemory error

2584:thumbsdown_anim: AllocateKernelMemory error

Edited by luxinhaus
Link to comment
Share on other sites

@ErmaC

 

No changes

 

2560:thumbsup_anim:

2561:thumbsdown_anim:  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:thumbsdown_anim: AllocateKernelMemory error

2584:thumbsdown_anim: AllocateKernelMemory error

 

2561_V2 (change again the logic about the version of OS X is checked) -->

 

ErmaC

Link to comment
Share on other sites

@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 =  :thumbsup_anim:

Mountain Lion =  :thumbsdown_anim: reboots instantly

Mavericks =   :thumbsdown_anim: reboots instantly

Yosemite =    :thumbsdown_anim: reboots instantly

Edited by luxinhaus
Link to comment
Share on other sites

@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 =  :thumbsup_anim:

Mountain Lion =  :thumbsdown_anim: reboots instantly

Mavericks =   :thumbsdown_anim: reboots instantly

Yosemite =    :thumbsdown_anim: reboots instantly

 

(OS X check again...)

2561_V3 ->

 

ErmaC

Link to comment
Share on other sites

@ErmaC

 

V3 now works  :thumbsup_anim:

 

************************************************

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 by luxinhaus
  • Like 1
Link to comment
Share on other sites

V3 now works  :thumbsup_anim:

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

  • Like 1
Link to comment
Share on other sites

2562_V1 =  :thumbsdown_anim: 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

Really proud to present my BUILD  :D
:moil:  :moil:
I compile and build  with Xcode my own Chameleon-2.3svn-r2587 Special Edition.pkg
 
Support OS X USB installer and Kernel Extractor  :lol:  :thumbsup_anim: 
 
Its a Standard Package  :yes:  No EFI  ;)
 
I have boot on the Installation in my first attempt   :w00t:  :thumbsup_anim: 
  :yoji:
 
137.png
 
Chameleon Install Log  :)

 

 

Chameleon installer log - Mon Mar 9 22:35:03 EDT 2015
Installer version: 2.3svn 2587
======================================================
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *120.0 GB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_HFS SSD_OCZ 119.7 GB disk0s2
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *240.1 GB disk1
1: EFI EFI 209.7 MB disk1s1
2: Apple_HFS Macintosh HD 239.2 GB disk1s2
3: Apple_Boot Recovery HD 650.0 MB disk1s3
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk2
1: EFI EFI 209.7 MB disk2s1
2: Apple_HFS BACKUP 999.9 GB disk2s2
/dev/disk3
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk3
1: EFI EFI 209.7 MB disk3s1
2: Apple_HFS HDD 500 499.8 GB disk3s2
/dev/disk4
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.1 GB disk4
1: EFI EFI 209.7 MB disk4s1
2: Apple_HFS HDD 499.8 GB disk4s2
======================================================
Backup Chameleon files
======================================================
Clearing options...
======================================================
Running Standard postinstall script
Target 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: 0xAA55
Starting 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] unused
3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused

Setting /Volumes/HDD partition active.
======================================================
Standard script complete
======================================================
Added boot option: Instant Menu=Yes
Add: ":Instant Menu" Entry Already Exists
Added boot option: ShowInfo=Yes
Add: ":ShowInfo" Entry Already Exists
Added boot option: Kernel Flags=-v
Added boot option: Kernel Flags=darkwake=0
Added boot option: Kernel Flags=dart=0
Added boot option: Graphics Mode=1024x768x32
Add: ":Graphics Mode" Entry Already Exists
======================================================
Running Post postinstall script
Target volume = /Volumes/HDD
===============================================
"/Volumes/EFI" unmounted successfully.
boot file hidden /Volumes/HDD/boot
13786138 blocks
"disk5" unmounted.
"disk5" ejected.
======================================================
Extracting kernel
Remove Extractor
======================================================
Post postinstall script complete

 

 

Thanks to ErmaC  / Andy / Minuzwei /  / Pike  / meklort / Mickey1979  and  all of devs for contributing to this amazing Project  :lol:  :D 

  • Like 1
Link to comment
Share on other sites

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 by luxinhaus
Link to comment
Share on other sites

@ErmaC

 

2605 from the SVN =  :thumbsup_anim:

 

On a side note on compiling:

xcode 6 = :thumbsup_anim:  

old xcode =  :thumbsdown_anim: ( 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 by luxinhaus
Link to comment
Share on other sites

×
×
  • Create New...