Bootloader Chameleon 2.4svn Official PKG Installer

Micky1979 · March 30, 2015

thank you for your reply.

i'm sorry for not giving credit where credit is due. i just found that trick on TM's site.

Thanks to people who found out that trick.

Sorry, nothing against you, but give credit to those who can not pisses me off! :dev:

Ok, if you want to give credit see at some links (look at the date, but I can find older too):

https://www.youtube.com/watch?v=rPEXR1NfgwI

http://www.insanelymac.com/forum/topic/278198-boot0error-easiest-way-to-fix-it/

As memory allocation error is related to r2602 commit and AF Hard drive problem is solved, i have one issue left here that is related to package installer. its same for r2625 and r2588. Didnt try other revs, but i expect same result.

let me explain the problem

- i've run official package installer to install chameleon bootloader into usb flash disk.

- After that, rebooted pc to boot into newly installed usb boot loader. But it stuck at POST screen. Seems BIOS couldnt recognise new USB booter disk or something. It stuck there forever. if i remove the new USB booter disk, it went ok and boots. So i guess something is happened during package installer.

- if i install chameleon manually using tools (fdisk440, dd, cp) , it went ok and boots

- So i retrieved MBR of new USB disk after package installer installation and manual installation. then compared them

- Only difference is like below
maveas-Mac-Pro:Desktop mavea$ diff hex.MBR.Package hex.MBR.Manual
29c29

---

> 00001c0 ff ff ee fe ff ff 01 00 00 00 47 6c 78 00 00 00

You can see value "80" at 00001ce in MBR for Package Installer installation and "00" for manual installation.

is this related to setting active paritition? i notified package installer sets active partition. other than that its mostly same as maual installation.

thanks

Boot0 is changed (now supports ExFat +fat32 on ESP ) credit Zenith432, new variant of boot1h (from Clover...and from some time ago..so is compatible with him), new boot1x (Zenith432)...

The procedure to install stage0, 1 and 2 is a little changed:

boot0x use fdisk440 (no changes)

boot1x (no more dd, we use boot1-install by Zenith432. Non root Volumes will be always umounted to install the stage 1, the key to the success)

boot2 (is a copy procedure, no matter)

To activate the partition.... well this depend by the boot0x chosen, *not always is required:

- The new installer installs boot0hfs if the target partition is hfs and Windows is present on the disk (otherwise boot0) or bootmd if the partition is fat32 and windows is present on the disk (otherwise boot0) and always boot0 if the partition is Exfat formatted.

- If the boot0x used is boot0hfs the partition will not be activated because is not required *(correct me if I'm wrong), + will protect your Windows installation if any.

- If the partition is already set as active, then the installer will skip the activation process (no need to do again no?)

- If Windows is detected on the same disk, never the partition will be activated!

What the installer did... I don't know, I ask for the log.... that I never see .

Anyway you can format your USB stick in Fat32 or ExFat and re-try again with r2625 Installer to see if the problem is boot0hfs related or in hfs if already tried? (because in the first case boot0 is used and the partition surely will be activated, in the second the partition will not activated... and some thing can be different...).

Can also try the installation on the ESP if you cannot format this drive...

Thanks

EDIT

it might be interesting to activate partition although stage 0 is boot0hfs?

ea dd · March 30, 2015

...

What the installer did... I don't know, I ask for the log.... that I never see .

Anyway you can format your USB stick in Fat32 or ExFat and re-try again with r2625 Installer to see if the problem is boot0hfs related or in hfs if already tried? (because in the first case boot0 is used and the partition surely will be activated, in the second the partition will not activated... and some thing can be different...).

Can also try the installation on the ESP if you cannot format this drive...

...

ok

i had installed chameleon boot loader using official package installer on USB disk formatted with 4 combinations of partitions and filesystems

1. GPT + HFS it stuck at POST screen

2. GPT + exFAT it passed thru

3. MBR + HFS it passed thru

4. MBR + FAT32 it passed thru

it seems the problem occurs when USB disk is partitioned with GUID partition and formatted with Mac OS extended (Journaled) file system

i wanted to attached a zip file which includes chameleon installer log files and sector1 data of each combinations. but couldnt find way to upload it.

so here is just log file of installer for Usb disk with GPT+HFS.

==============================================================================

SYSTEM INFO:

ProductName: Mac OS X

ProductVersion: 10.9.5

BuildVersion: 13F1066

==============================================================================

Pre-Install Script

------------------------------------------------------------------------------

Creating /Volumes/CHM/EXTRAROOTDIR symlink targeting /Volumes/BOOTRAMDISK

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: FDisk_partition_scheme *82.0 GB disk0

1: Windows_NTFS 82.0 GB disk0s1

/dev/disk1

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *500.1 GB disk1

1: EFI EFI 209.7 MB disk1s1

2: Apple_HFS MVD 150.0 GB disk1s2

3: Apple_HFS XD 349.6 GB disk1s3

/dev/disk2

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *4.0 GB disk2

1: EFI EFI 209.7 MB disk2s1

2: Apple_HFS CHM 3.7 GB disk2s2

/dev/disk3

#: TYPE NAME SIZE IDENTIFIER

0: BOOTRAMDISK *209.7 MB disk3

------------------------------------------------------------------------------

END - Pre-Install Script

==============================================================================

Main Standard Post-Install Script

Chameleon installer log - Mon Mar 30 19:12:24 ULAT 2015

Darwin/x86 boot v5.0.132 - Chameleon v2.3svn r2625

==============================================================================

BACKUP CHAMELEON FILES:

No stage 2 (boot) was found, nothing to be saved.

No Extra folder was found, nothing to be saved.

==============================================================================

EXTRA FOLDER:

Extra not found on /Volumes/CHM, creating..

File Doesn't Exist, Will Create: /Volumes/BOOTRAMDISK/Extra/org.chameleon.Boot.plist

==============================================================================

First Check Passed (not Fat16)!

Windows installation not found on /dev/disk2.

/dev/disk2s2 is HFS formatted

==============================================================================

WRITING STAGE 0:

boot0 writed to /dev/disk2

==============================================================================

WRITING STAGE 1 hfs:

boot1h (hfs) writed to /dev/rdisk2s2.

==============================================================================

WRITING STAGE 2:

Stage 2 (boot) writed to /Volumes/CHM.

==============================================================================

SET PARTITION ACTIVE:

Setting /Volumes/CHM partition active.

Enter 'help' for information

fdisk: 1> Disk: /dev/rdisk2 geometry: 978/128/63 [7892040 sectors]

Offset: 0 Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec [ start - size]

------------------------------------------------------------------------

1: EE 1023 254 63 - 1023 254 63 [ 1 - 7892039]

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

fdisk: 1> Partition 2 marked active.

fdisk:*1> Device could not be accessed exclusively.

A reboot will be needed for changes to take effect. OK? [n] Writing MBR at offset 0.

fdisk: 1>

==============================================================================

END - Standard Post-Install Script

==============================================================================

Installing Theme Bullet

------------------------------------------------------------------------------

Theme Bullet installed

------------------------------------------------------------------------------

==============================================================================

Installing Theme Default

------------------------------------------------------------------------------

Theme Default installed

------------------------------------------------------------------------------

==============================================================================

Installing Theme Embed

------------------------------------------------------------------------------

Theme Embed installed

------------------------------------------------------------------------------

==============================================================================

Installing Theme Legacy

------------------------------------------------------------------------------

Theme Legacy installed

------------------------------------------------------------------------------

==============================================================================

Running Post postinstall script

Target volume = /Volumes/CHM

------------------------------------------------------------------------------

Moving Extra folder to /Volumes/CHM

------------------------------------------------------------------------------

Post postinstall script complete

==============================================================================

NOTE: any Themes or modules you have must be there since this now

is the boot partition. ACPI tables, SMBios.plist and the

org.chameleon.Boot.plist (with custom settings for the target

OSX must be in each partition that contain it.)

==============================================================================

thanks

CooSee · March 30, 2015

@ Ermac

forgot to mention that i tried to update from Enoch r2588 to Enoch r2644.

thx for your time and support

greetings

ErmaC · March 30, 2015

Pls guys test this:

"original" 2433 - i386-2643-pure.zip (No changes here build directly from the SVN)

"Partial revert commit 2602" - i386-2643-Part-rev_2602.zip (Revert almost of commit 2602)

Let me know if the "i386-2643-Part-rev_2602" work for your "old" motherboard.

ErmaC

Micky1979 · March 30, 2015

ok

i had installed chameleon boot loader using official package installer on USB disk formatted with 4 combinations of partitions and filesystems

1. GPT + HFS it stuck at POST screen

2. GPT + exFAT it passed thru

3. MBR + HFS it passed thru

4. MBR + FAT32 it passed thru

it seems the problem occurs when USB disk is partitioned with GUID partition and formatted with Mac OS extended (Journaled) file system

i wanted to attached a zip file which includes chameleon installer log files and sector1 data of each combinations. but couldnt find way to upload it.

so here is just log file of installer for Usb disk with GPT+HFS.

==============================================================================

SYSTEM INFO:

ProductName: Mac OS X

ProductVersion: 10.9.5

BuildVersion: 13F1066

==============================================================================

Pre-Install Script

------------------------------------------------------------------------------

Creating /Volumes/CHM/EXTRAROOTDIR symlink targeting /Volumes/BOOTRAMDISK

/dev/disk0

#: TYPE NAME SIZE IDENTIFIER

0: FDisk_partition_scheme *82.0 GB disk0

1: Windows_NTFS 82.0 GB disk0s1

/dev/disk1

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *500.1 GB disk1

1: EFI EFI 209.7 MB disk1s1

2: Apple_HFS MVD 150.0 GB disk1s2

3: Apple_HFS XD 349.6 GB disk1s3

/dev/disk2

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *4.0 GB disk2

1: EFI EFI 209.7 MB disk2s1

2: Apple_HFS CHM 3.7 GB disk2s2

/dev/disk3

#: TYPE NAME SIZE IDENTIFIER

0: BOOTRAMDISK *209.7 MB disk3

------------------------------------------------------------------------------

END - Pre-Install Script

==============================================================================

Main Standard Post-Install Script

Chameleon installer log - Mon Mar 30 19:12:24 ULAT 2015

Darwin/x86 boot v5.0.132 - Chameleon v2.3svn r2625

==============================================================================

BACKUP CHAMELEON FILES:

No stage 2 (boot) was found, nothing to be saved.

No Extra folder was found, nothing to be saved.

==============================================================================

EXTRA FOLDER:

Extra not found on /Volumes/CHM, creating..

File Doesn't Exist, Will Create: /Volumes/BOOTRAMDISK/Extra/org.chameleon.Boot.plist

==============================================================================

First Check Passed (not Fat16)!

Windows installation not found on /dev/disk2.

/dev/disk2s2 is HFS formatted

==============================================================================

WRITING STAGE 0:

boot0 writed to /dev/disk2

==============================================================================

WRITING STAGE 1 hfs:

boot1h (hfs) writed to /dev/rdisk2s2.

==============================================================================

WRITING STAGE 2:

Stage 2 (boot) writed to /Volumes/CHM.

==============================================================================

SET PARTITION ACTIVE:

Setting /Volumes/CHM partition active.

Enter 'help' for information

fdisk: 1> Disk: /dev/rdisk2 geometry: 978/128/63 [7892040 sectors]

Offset: 0 Signature: 0xAA55

Starting Ending

#: id cyl hd sec - cyl hd sec [ start - size]

------------------------------------------------------------------------

1: EE 1023 254 63 - 1023 254 63 [ 1 - 7892039]

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

fdisk: 1> Partition 2 marked active.

fdisk:*1> Device could not be accessed exclusively.

A reboot will be needed for changes to take effect. OK? [n] Writing MBR at offset 0.

fdisk: 1>

==============================================================================

==============================================================================

END - Standard Post-Install Script

==============================================================================

Installing Theme Bullet

------------------------------------------------------------------------------

Theme Bullet installed

------------------------------------------------------------------------------

==============================================================================

Installing Theme Default

------------------------------------------------------------------------------

Theme Default installed

------------------------------------------------------------------------------

==============================================================================

Installing Theme Embed

------------------------------------------------------------------------------

Theme Embed installed

------------------------------------------------------------------------------

==============================================================================

Installing Theme Legacy

------------------------------------------------------------------------------

Theme Legacy installed

------------------------------------------------------------------------------

==============================================================================

Running Post postinstall script

Target volume = /Volumes/CHM

------------------------------------------------------------------------------

Moving Extra folder to /Volumes/CHM

------------------------------------------------------------------------------

Post postinstall script complete

==============================================================================

NOTE: any Themes or modules you have must be there since this now

is the boot partition. ACPI tables, SMBios.plist and the

org.chameleon.Boot.plist (with custom settings for the target

OSX must be in each partition that contain it.)

==============================================================================

thanks

Thanks a lot, this is much more than what I asked for!

It all seems ok by the installer understood as mechanical installation (boot0 -> boot1h -> boot). Basically it seems that stage 2 (the bootloader) has been reached (even if it cannot go ahead), as I understand it (it stuck at POST screen). Confirm?

thanks again

Hi Fabio and all others,

by the way is intresting an option to install only the stage 2 in the installer w/o rewriting stage 0 and stage 1 (of course, activation) every time??

....It seems like Advanced Formatted (4k) drives can thank ... (Because You do not run the risk of invalidating already working bootsectors)... my 2 cents

luxinhaus · March 31, 2015

Pls guys test this:

"original" 2433 - i386-2643-pure.zip (No changes here build directly from the SVN)

"Partial revert commit 2602" - i386-2643-Part-rev_2602.zip (Revert almost of commit 2602)

Let me know if the "i386-2643-Part-rev_2602" work for your "old" motherboard.

ErmaC

i386-2643-pure.zip = :thumbsdown_anim: allocmem error (same error in my post #2794)

i386-2643-Part-rev 2602.zip = :thumbsdown_anim: early instant restart before chameleon prompt

ea dd · March 31, 2015

Thanks a lot, this is much more than what I asked for!

It all seems ok by the installer understood as mechanical installation (boot0 -> boot1h -> boot). Basically it seems that stage 2 (the bootloader) has been reached (even if it cannot go ahead), as I understand it (it stuck at POST screen). Confirm?

i mean Power On Self Test screen.

its just right after power is on and seems BIOS is recognising/checking cpu,mem,hdd etc...

so i doubt stage 2 (/Volume/mydisk/boot) loader is reached in this case. i guess it cant even reach to stage 1 (boot1h) or stage 0 (boot0) loaders.

it just stuck at recognising usb disk.

attached is screenshot where it stuck.

thanks.

luxinhaus · March 31, 2015

@ea dd

no issue on "stuck at post screen" if you installed it manually?

ErmaC · March 31, 2015

i386-2643-pure.zip = allocmem error (same error in my post #2794)

i386-2643-Part-rev 2602.zip = early instant restart before chameleon prompt

Thx for the test...

Here the full revert, if not work.. then the problem is elsewhere...(I mean not in 2602 commit)

i386-2643-Full-rev_2602.zip

ErmaC

ea dd · March 31, 2015

@ea dd

no issue on "stuck at post screen" if you installed it manually?

yes.

there is no problem if i install chameleon manually using tools (fdisk44, dd, cp).

Using official package installer, to install chameleon on GPT+HFS formatted disk, is getting that problem.

Using official package installer for other kind of partition/file system (MBR+HFS, MBR+FAT32, GPT+exFAT ) is working without stuck-problem.

is it only me or any1 experienced this?

thanks.

Thx for the test...

Here the full revert, if not work.. then the problem is elsewhere...(I mean not in 2602 commit)

i386-2643-Full-rev_2602.zip

ErmaC

it works, no "allocation error" now.

since its only boot file, i used boot0 and boot1h from r2588.

thanks.

luxinhaus · March 31, 2015

@ErmaC

too bad im no longer in the office to test. but if ea dd says that it worked on him, then probably will work on me too.

I will verify it tomorrow

@ea dd

im not having the "stuck on post screen" issue on my stick with GPT+HFS

Micky1979 · March 31, 2015

rev 2643 downloaded from the trunk, script just modified to use dd istead of boot1-install (like was before):

Can you try please on the GPT+hfs?

Thanks

EDIT

package removed

bug appeare to be in the user bios

luxinhaus · March 31, 2015

@Mickey1979

could it be that the trunk is using older source of boot1-install that might causing the issue on some system (specially on him) as i dont have the issue? just my thought

ea dd · March 31, 2015

rev 2643 downloaded from the trunk, script just modified to use dd istead of boot1-install (like was before):

Can you try please on the GPT+hfs?

Thanks

thanks for your effort.

its same. it stuck there.

but i think the reason of that "stuck at post screen" problem is "80" at 00001ce of first boot sector.

OPI (Official Package Installer) installs boot0, boot1h, boot to chosen disk. (USB stick, hdd,...)

And OPI sets "80" at 00001ce of first sector for somewhat reason.

MI (Manual Installation) installs boot0, boot1h, boot to chosen disk, but doesnt set "80" at 00001ce of first sector.

i checked like below

1. Run OPI to install chameleon on USB stick (GPT+HFS)

2. Checked 1st sector and it has "80" at 00001ce

3. Rebooted and it stuck at POST screen

4. Run only fdisk440 to reinstall boot0 to the stick. Didnt touch boot1h and boot.

5. Checked 1st sector and it has "00" at 00001ce

6. Rebooted and it passed thru

here is 1st sector from OPI

0000000 fa 31 c0 8e d0 bc f0 ff fb 8e c0 8e d8 be 00 7c
0000010 bf 00 e0 fc b9 00 01 f3 a5 ea 1e e0 00 00 66 31
0000020 c0 66 a3 00 e4 b0 02 bb 00 10 e8 1d 01 72 06 be
0000030 be 11 e8 09 00 bf ae e1 e8 42 01 f4 eb fd 81 7c
0000040 40 55 aa 75 4e 31 db fe c7 b9 04 00 66 8b 44 08
0000050 66 a3 00 e4 80 7c 04 00 74 26 80 7c 04 ee 75 05
0000060 c6 04 00 b3 01 80 ff 01 75 09 f6 04 80 74 11 30
0000070 f6 eb 08 80 7c 04 af 75 07 b6 01 e8 98 00 74 14
0000080 83 c6 10 e2 c7 fe cb 75 03 e8 11 00 fe cf be be
0000090 11 74 b6 c3 bf a9 e1 e8 e3 00 e9 63 9b 53 be 00
00000a0 12 66 81 3c 45 46 49 20 75 6a 66 81 7c 04 50 41
00000b0 52 54 75 60 66 8b 44 48 66 a3 00 e4 8b 4c 50 8b
00000c0 5c 54 53 b0 20 bb 00 14 53 e8 7e 00 5e 5b 0f 82
00000d0 63 ff bf a5 e1 e8 a5 00 66 8b 44 0c 66 3d 65 43
00000e0 ec ac 74 10 66 3d c9 3e c9 3b 74 08 66 3d b7 26
00000f0 99 c7 75 1c 66 8b 44 20 66 a3 00 e4 b6 01 e8 15
0000100 00 75 0d be be 11 66 89 44 08 c6 44 04 af eb 84
0000110 01 de e2 c4 5b c3 60 b0 03 bb 00 7c e8 2b 00 0f
0000120 82 12 ff 08 f6 74 1b a1 00 80 3d 48 2b 74 13 3d
0000130 48 58 74 0e 81 7f 03 45 58 74 07 81 7f 5a 42 4f
0000140 75 06 81 3e fe 7d 55 aa 61 c3 51 b9 05 00 e8 06
0000150 00 73 02 e2 f9 59 c3 66 60 89 e5 1e 1e 66 8b 0e
0000160 00 e4 66 51 06 53 30 e4 50 6a 10 89 e6 b4 42 cd
0000170 13 73 05 31 c0 cd 13 f9 89 ec 66 61 c3 60 57 be
0000180 9b e1 e8 06 00 5e e8 02 00 61 c3 bb 01 00 fc ac
0000190 3c 00 74 06 b4 0e cd 10 eb f5 c3 0a 0d 62 6f 6f
00001a0 74 30 3a 20 00 47 50 54 00 64 6f 6e 65 00 65 72
00001b0 72 6f 72 00 00 00 00 00 00 00 00 00 00 00 00 fe
00001c0 ff ff ee fe ff ff 01 00 00 00 47 6c 78 00 80 00
00001d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*
00001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa
0000200

here is 1st sector from MI

0000000 fa 31 c0 8e d0 bc f0 ff fb 8e c0 8e d8 be 00 7c
0000010 bf 00 e0 fc b9 00 01 f3 a5 ea 1e e0 00 00 66 31
0000020 c0 66 a3 00 e4 b0 02 bb 00 10 e8 1d 01 72 06 be
0000030 be 11 e8 09 00 bf ae e1 e8 42 01 f4 eb fd 81 7c
0000040 40 55 aa 75 4e 31 db fe c7 b9 04 00 66 8b 44 08
0000050 66 a3 00 e4 80 7c 04 00 74 26 80 7c 04 ee 75 05
0000060 c6 04 00 b3 01 80 ff 01 75 09 f6 04 80 74 11 30
0000070 f6 eb 08 80 7c 04 af 75 07 b6 01 e8 98 00 74 14
0000080 83 c6 10 e2 c7 fe cb 75 03 e8 11 00 fe cf be be
0000090 11 74 b6 c3 bf a9 e1 e8 e3 00 e9 63 9b 53 be 00
00000a0 12 66 81 3c 45 46 49 20 75 6a 66 81 7c 04 50 41
00000b0 52 54 75 60 66 8b 44 48 66 a3 00 e4 8b 4c 50 8b
00000c0 5c 54 53 b0 20 bb 00 14 53 e8 7e 00 5e 5b 0f 82
00000d0 63 ff bf a5 e1 e8 a5 00 66 8b 44 0c 66 3d 65 43
00000e0 ec ac 74 10 66 3d c9 3e c9 3b 74 08 66 3d b7 26
00000f0 99 c7 75 1c 66 8b 44 20 66 a3 00 e4 b6 01 e8 15
0000100 00 75 0d be be 11 66 89 44 08 c6 44 04 af eb 84
0000110 01 de e2 c4 5b c3 60 b0 03 bb 00 7c e8 2b 00 0f
0000120 82 12 ff 08 f6 74 1b a1 00 80 3d 48 2b 74 13 3d
0000130 48 58 74 0e 81 7f 03 45 58 74 07 81 7f 5a 42 4f
0000140 75 06 81 3e fe 7d 55 aa 61 c3 51 b9 05 00 e8 06
0000150 00 73 02 e2 f9 59 c3 66 60 89 e5 1e 1e 66 8b 0e
0000160 00 e4 66 51 06 53 30 e4 50 6a 10 89 e6 b4 42 cd
0000170 13 73 05 31 c0 cd 13 f9 89 ec 66 61 c3 60 57 be
0000180 9b e1 e8 06 00 5e e8 02 00 61 c3 bb 01 00 fc ac
0000190 3c 00 74 06 b4 0e cd 10 eb f5 c3 0a 0d 62 6f 6f
00001a0 74 30 3a 20 00 47 50 54 00 64 6f 6e 65 00 65 72
00001b0 72 6f 72 00 00 00 00 00 00 00 00 00 00 00 00 fe
00001c0 ff ff ee fe ff ff 01 00 00 00 47 6c 78 00 00 00
00001d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*
00001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa
0000200

only difference is that values at 00001ce and rests are same.

thanks.

Micky1979 · March 31, 2015

Understood, and I agreed with you. I'm not at Home atm, later I'll see if something is wrong in the script.... even if I cant understad why is working for me (my tests was done by formatting the entire disk. ....almost always)

ea dd · March 31, 2015

Understood, and I agreed with you. I'm not at Home atm, later I'll see if something is wrong in the script.... even if I cant understad why is working for me (my tests was done by formatting the entire disk. ....almost always)

setting active partition chnages value at 00001ce.

i just tested using "fdisk -e /dev/rdiskX" and flagging second slice as active.

then checked 1st sector and there is "80" at 00001ce.

but i could not really understand why my pc stuck at POST screen, but yours (you and luxinhaus confirmed) are ok.

if its only me, maybe i have something wrong configs in BIOS. i dunno.

thanks.

Micky1979 · March 31, 2015

@Mickey1979

could it be that the trunk is using older source of boot1-install that might causing the issue on some system (specially on him) as i dont have the issue? just my thought

Seem ok.

setting active partition chnages value at 00001ce.

i just tested using "fdisk -e /dev/rdiskX" and flagging second slice as active.

then checked 1st sector and there is "80" at 00001ce.

but i could not really understand why my pc stuck at POST screen, but yours (you and luxinhaus confirmed) are ok.

if its only me, maybe i have something wrong configs in BIOS. i dunno.

thanks.

mmmh, another test (if you want):

please destroy the partition map on your USB stick and recreate a new one...

Edited April 4, 2015 by Micky1979
package removed, bug appeare to be in the user bios

ea dd · March 31, 2015

Seem ok.

mmmh, another test (if you want):Chameleon-2.3svn-r2643_test2.pkg.zip

please destroy the partition map on your USB stick and recreate a new one...

same again. stuck at POST screen.

created new USB stick with new GPT partition and HFS.

OPI still sets active partition ("80" at 00001ce).

thanks.

Micky1979 · March 31, 2015

I cant imagine what the problem is.. the code is that:

PARTITION_ACTIVE_IF() {

if [ $InstallBootloader = "1" ];then

echo -e "${mainLine}\nSET PARTITION ACTIVE:"

# if Windows was detected, don't activate the partition..

# if the stage 0 loader is boo0hfs, don't activate the partition

if [ WINDOWS_EXIST = "0" ] || [ "${stage0Loader}" != "boot0hfs" ];then

partitionactive=$( fdisk -d ${targetDiskRaw} | grep -n "*" | awk -F: '{print $1}')

if [ "${partitionactive}" ] && [ "${partitionactive}" = "${targetSlice}" ]; then

echo "${targetDiskRaw#/dev/r}, slice "${targetSlice}" is already set active. No need to change it."

else

echo "Setting ${choicedVolume} partition active."

# BadAxe requires EFI partition to be flagged active.

# but it doesn't' hurt to do it for any non-windows partition.

# leave left aligned the follow code:

fdisk -e ${targetDiskRaw}

print

flag ${targetSlice}

write

y

quit

MAKEACTIVE

fi

else

echo "Partition will not activate when Windows is detected or stage 0 is boot0hfs"

fi

echo ""

echo "$mainLine"

fi

}

I cant see errors... Anyway the target slice is corretct in the log?

EDIT

I can place some " around the variables .... mmmh --> ("${targetDiskRaw}", "${targetSlice}")... but it seem working looking at the your log.. :wacko: .

Edited April 4, 2015 by Micky1979
bug appeare to be in the user bios

ea dd · March 31, 2015

I cant imagine what the problem is.. the code is that:

PARTITION_ACTIVE_IF() {

if [ $InstallBootloader = "1" ];then

echo -e "${mainLine}\nSET PARTITION ACTIVE:"

# if Windows was detected, don't activate the partition..

# if the stage 0 loader is boo0hfs, don't activate the partition

if [ WINDOWS_EXIST = "0" ] || [ "${stage0Loader}" != "boot0hfs" ];then

partitionactive=$( fdisk -d ${targetDiskRaw} | grep -n "*" | awk -F: '{print $1}')

if [ "${partitionactive}" ] && [ "${partitionactive}" = "${targetSlice}" ]; then

echo "${targetDiskRaw#/dev/r}, slice "${targetSlice}" is already set active. No need to change it."

else

echo "Setting ${choicedVolume} partition active."

# BadAxe requires EFI partition to be flagged active.

# but it doesn't' hurt to do it for any non-windows partition.

# leave left aligned the follow code:

fdisk -e ${targetDiskRaw} <<-MAKEACTIVE

print

flag ${targetSlice}

write

y

quit

MAKEACTIVE

fi

else

echo "Partition will not activate when Windows is detected or stage 0 is boot0hfs"

fi

echo ""

echo "$mainLine"

fi

}

I cant see errors... Anyway the target slice is corretct in the log?

yeah. me, too, see no error here. the OPI correctly installs chameleon and correctly sets active partition.

my issue is my BIOS and USB stick with GPT+HFS+active_partition conflicts somewhere during pc starts.

my question is possible to build OPI without setting active partition feature?

i had always installed chameleon binaries manually and without setting active partition. but it had always worked.

any good reason to include setting active partition feature?

thanks

Micky1979 · March 31, 2015

because this part of code (that I have put in a function) is the same that you can find in all old installers since 2010 (and Clover too).

a stage 0 "can" work by simply searching for active partitions

EDIT

But as I suggested at previous page I can introduce the "only" copy of stage 2 w/o writing stage 0/1 and activation..

dmazar is the creator of boo0md (and other things).

In the last installer I've revert back the boot0 to the old one, but the test fail (ok by the way this assure me that the problem is not the new boot0 )

Edited April 4, 2015 by Micky1979
bug appeare to be in the user bios

fusion71au · March 31, 2015

setting active partition chnages value at 00001ce.

i just tested using "fdisk -e /dev/rdiskX" and flagging second slice as active.

then checked 1st sector and there is "80" at 00001ce.

but i could not really understand why my pc stuck at POST screen, but yours (you and luxinhaus confirmed) are ok.

if its only me, maybe i have something wrong configs in BIOS. i dunno.

thanks.

It's not only you and its not only the Chameleon installer .

I've also noticed that behaviour on my legacy BIOS desktop rig with legacy Clover - a Gigabyte P55aUD3/Intel i5 750/ATI HD5770 system.

If I install Clover on a GPT partitioned USB with the "boot0af in MBR" option, the installer sets an active partition ---> system will hang on boot with the USB plugged in:

Some workarounds

1. Installing Clover with the "Install boot0ss in MBR" option ---> installer does not set an active partition ---> system boots normally

2. Partitioning the USB with MBR layout instead of GPT

The issue does not appear when the bootloader is installed on the hard disk with boot0af option & active partition (only USB). Also not all legacy BIOS machines have the problem - my Dell laptop XPS M1530 happily boots from a GPT USB with active partition set and boot0af :surprised: .

luxinhaus · April 1, 2015

Thx for the test...

Here the full revert, if not work.. then the problem is elsewhere...(I mean not in 2602 commit)

i386-2643-Full-rev_2602.zip

ErmaC

Confirmed working :thumbsup_anim:

ea dd · April 1, 2015

It's not only you and its not only the Chameleon installer .

I've also noticed that behaviour on my legacy BIOS desktop rig with legacy Clover - a Gigabyte P55aUD3/Intel i5 750/ATI HD5770 system.

nice to hear i'm not alone in a boat.

thanks for sharing your experience.

so, i take that "stuck at POST screen" problem as solved.

also thanks to Micky1979, luxinhaus, Ermac.

Micky1979 · April 1, 2015

well. As soon I have time I'll made a package with a sub options (always enabled by default) to disable the choices and skip the install of stage 0, stage 1 and activation. This way you can chose what to do. just to test...

Bootloader Chameleon 2.4svn Official PKG Installer

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites