I want Chameleon Team to hear me. Up for now it doesn't happen.
I am present at this forum to not support users and not for claim that I created my own bootloader.
I need a help to make it working. Any info will be useful.
It is not my project, it is not my sources, it is not my logics. I just not understanding what is what.
This bug I consider as a most terrible.
Bug N1.
I created a bootable CD with cdboot, boot.plist and smbios.plist, also modules and themes. No kernel, no system.
Booted into Chameleon GUI. Now I can choose a partition to load system from. Look:
Why "still waiting..."? In the photo you can see that kernel is loaded, and some kexts loaded. Why next stop?
Other one.
The differencies that in the first case I press F10 and change CD to another. Why CD? I booted hard drive where I have good working system!
In the picture you may see disk1s1s2 - this is CD partition where kernel is decided to look non-root kexts.
So, even we boot HDD, we inform kernel wrong boot device. It must be disk0s3 as bootArgs.
This is a place into sources
if (!uuidSet && gBootVolume->fs_getuuid && gBootVolume->fs_getuuid (gBootVolume, uuidStr) == 0) {
verbose("Setting boot-uuid to: %s\n", uuidStr);
copyArgument(kBootUUIDKey, uuidStr, strlen(uuidStr), &argP, &cntRemaining);
uuidSet = true;
}
What is gBootVolume? Is it a volume to boot or a volume from boot? As I see from the photo UUID is VOLUME FROM BOOT but kernel needs to know his own volume. VOLUME TO BOOT.