Voodooprojects
Chameleon => General Discussion => Topic started by: screwedx on April 26, 2010, 06:10:15 PM
-
Hello,
i've followed the guide for manual instal of cham on EFI.
I've used also scripts from the insanlywind forum to update kext etc.
But i get always the same error after restart:
boot0: GPT
boot0: testing
boot0: testing
boot0: error
I'm trying and reading and trying and reading and trying and... for over two weeks now.
Install and everything is fine, just the bootloader don't want to install properly.
Maybe someone can help me.
-
hum.. take a look at this topic: http://forum.voodooprojects.org/index.php/topic,1353.0.html
Raid related but, same problem.
-
hello,
i read this. but i think my problem is quite different.
i get as last line a boot0: error and not a boot0: done.
also i followed the official manual for installation of Cham 2 RC4 and used the shipped fdisk and also installed the boot1h to my efi partition.
-
Ok, that was just to see if you were paying attention :P
Well, let me ask you this: why are you installing Chameleon to EFI partition?
Yeah, it's a nice exercise and it's a shame to have all that space wasted; besides that it's plain masochism, to say the least.
This is my opinion but, i'm here to help so if you still want to go that way, more info is needed!
Which guide did you used? + the usual stuff you should have already mentioned on first post...
-
hello, thank you for your answer.
why i install cham to the EFI? Because everybody says it is nicer there. for me it doesn't matter, just want to have the macosx running like before.
ok, which guide did i used? these all to mention would be a huge list. not, just kidding.
the normal install i took a guide from insanelywind.com for a vanilla install. and since the boot was not working i took the guide from here to install the cham manually.
ok, the the whole story:
i have a wind u100 with dual boot win7 pro and macosx based on netbookinstaller. (all were running with easybcd and cham, no problem so far).
i changed 2 weeks ago the hdd in miy u100 to a samsung 640 gb. and with that i want to have my system back. since the netbookinstaller was mainly designed for dell, i got to insanleywind and the idea of the vanilla install sounds nice to me.
i have a macosx install running, a retail dvd, made my usb hdd with bootloader and the snow install...
everything went fine. but booting has never been possible. I took some installer scripts, efi_finisher, updateEFI but nothing works for me. win7 is not on my netbook or doesn't bother because it just stands in the back and doesn't claim the boot table for himself.
so i have now on my hdd an EFI partition with 200 mb, a macosx partition and a ntfs partition. and i can't boot right from hdd. when i plug in my install usb hdd with the bootloader then i can get into both systems and both are working fine.
maybe someone might say this is enhanced security (you can only boot with an external usb as a key for the system) but i think it would be nicer to just boot from the internal hdd.
do you need something else?
-
Ok, the fact that you can boot from the stick only proves the point about EFI partition. Leave it alone for now!
And if you do it, don't trust scripts.. type it your self on Terminal from some guide.
Boot the system, mount the EFI partition and clean it. Then install Cham to the OS X partition. Use the instructions on the README and check here (http://forum.voodooprojects.org/index.php/topic,754.0.html) for more help. If you do it right, you should be able to boot from HDD, wit no need for EasyBCD.
-
ok, i've done it and marked partition 2 (macosx) as active.
same procedure...
i really have no clue. maybe i should wipe my hdd and start new.
-
First, you shouldn't need to make OS X partition active on a HD partitioned with GUID scheme. At least, i don't need to do it, with Cham installed to second partition (OS X), just like you.
Second, i'm not familiar with netbookinstaller, or any other installer/helper app around. I just make my booters, installed to USB stick or pre-boot disc and boot retail restored to a partition or directly from the DVD. Never fails!
Then there's Windows on GUID.. i'm a complete stranger to that stuff. If you really need to dual-boot with windows, i'd do it on a MBR scheme.
So, assuming you're doing everything "by the book" and the new HDD is of the same type as the previous, i'm bit lost too?!
Wait a bit to see if someone else posts...
Or start all over.
-
thank you.
windows is the smallest problem... just the question which bootloader starts first. and win7 is installing without problems on guid partitions.
what i meant was that i did so much stuff to this installation right now so maybe a clean system is helpful. i will give that a try.
but thank you for your help.
-
Hello,
i've followed the guide for manual instal of cham on EFI.
I've used also scripts from the insanlywind forum to update kext etc.
But i get always the same error after restart:
boot0: GPT
boot0: testing
boot0: testing
boot0: error
I'm trying and reading and trying and reading and trying and... for over two weeks now.
Install and everything is fine, just the bootloader don't want to install properly.
Maybe someone can help me.
I can say the same here: You don't have boot1h installed on any of your HFS partitions. Can you send me your partition layout please (diskutil list)?
-
yeah.. i know Win7 installs fine to GUID, with some tweaks (gptsync, etc...). Ootb always refuses install to GPT disks. As space is not a problem here and i don't like to mess with my GPT, windows stays on MBR.
Hope you didn't went starting all over before waiting a bit.. look who as dropped in :)
-
no, i have waited... :) :)
ok, here's the output you asked for:
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *640.1 GB disk0
1: EFI 209.7 MB disk0s1
2: Apple_HFS osx 150.0 GB disk0s2
3: Microsoft Basic Data 489.8 GB disk0s3
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *320.1 GB disk1
1: Windows_NTFS Transcend 320.1 GB disk1s1
second disk is a disk for transferring the logfile to my second pc for posting here ;-)
if you need something else just ask.
yeah.. i know Win7 installs fine to GUID, with tricks (gptsync, etc...). Ootb always refuses install to GPT disks. As space is not a problem here and i don't like to mess with my GPT, windows stays on MBR.
but how to install macosx on mbr? the last installation went fine and i don't know why i can't booting. that's really weird.
-
I suppose disk1 is an external HD so, it should be a matter of:
sudo fdisk -f boot0 -u -y /dev/rdisk0; sudo dd if=boot1h of=/dev/rdisk0s2; cp boot /
If that's what you've been doing, i'm out of ideas.
p.s.: installing OS X to MBR needs some patching to the DVD. If it comes to that i'll point the patches for you.
-
i've done just these three commands a lot of times and it didn't work. but i've done it normally to disk0s1 - but now i've done it to disk0s2 and it didn't help. maybe there is really something wrong in the bootsector after so many tries with so different ideas and tools. (i tried everything...)
the patching of the DVD would be no problem. as far as i know you must eliminate one line in os[xxx - don't know the right name].mpkg. is that correct? (i never could use a mbr partition to install osx after the patching)
-
Yep, OSInstall.mpkg. For Leo install DVD that's all that's needed. For Snow you also need patched OSInstall framework.
You can find both here (http://osx86.sojugarden.com/downloads/#osinstall).
But, let's wait for Zef's opinion. Even if something is screwed on the boot sector, usually there's a way to fix it... we just tend to go the easy way (reinstall) and end up not knowing how to fix this kind of stuff.
Going for lunch... back later.
-
i've done just these three commands a lot of times and it didn't work. but i've done it normally to disk0s1 - but now i've done it to disk0s2 and it didn't help. maybe there is really something wrong in the bootsector after so many tries with so different ideas and tools. (i tried everything...)
Ok, i need your mbr and both hfs partition's boot sectors:
dd if=/dev/rdisk0 of=screwedxMBR bs=512 count=1
dd if=/dev/rdisk0s1 of=screwedxs1 bs=512 count=2
dd if=/dev/rdisk0s2 of=screwedxs2 bs=512 count=2
Please attach the screwedxMBR, screwedxs1, screwedxs2 files.
the patching of the DVD would be no problem. as far as i know you must eliminate one line in os[xxx - don't know the right name].mpkg. is that correct? (i never could use a mbr partition to install osx after the patching)
Editing the OSInstall.mpkg doesn't work anymore in Snow Leopard, you need a modified OSInstall.framework, google for "OSInstall.framework MBR".
-
yeah i will sure wait. after two weeks of minimum 2 installations per day i can wait a little bit longer. ;)
Lunch, oh, where do you come from? i have now 3:30 pm, so you are not too much away...
-
ok, sorry for the long time, was on a meeting.
-
Screwedx,
If you take a look at the attached screwedxs1 or screwedxs2 files they're both contain zeros which means that the boot1h code was not installed correctly. Please 'cd' to the folder where boot1h resides, then run the dd command posted above.
What output do you get after dd'ing the boot1h code?
-
Ok, i've been in the directory where the boot1h comes from (original Chameleon 2 rc4 folder).
when i type cat boot1h then i see the file is not empty.
so i used the 2 commands to bring back boot0 and boot1h to rdisk0 / rdisk0s2
before i did a restart i used your command and i did see the same results as before as i use the cat command.
after reboot the file is empty.
file screwedxs2 is before restart
file screwedxs2new is after restart.
-
after reboot the file is empty.
file screwedxs2 is before restart
file screwedxs2new is after restart.
Really strange...
Try to boot in single user mode (type -s at the boot prompt), repeat installing boot1h, then reboot.
-
ok. that works. where's the difference
i want to understand what was / is there.
-
ok. that works. where's the difference
i want to understand what was / is there.
No idea, maybe it can be something service which isn't loaded in single user mode. Btw i never experienced such issues when updating the HFS+ fs leading sectors.
-
Screwedx, after lunch lazyness caught me.. it's now 18:30 in Lusitânia ;)
I see the problem is solved.. installing in -s mode wouldn't cross my mind so soon. Really strange problem..!? i was starting to think you were not changing dir to the booter folder, before installing.
Never got such problem my self either!!
-
Hello zef,
i've played a little bit around to see if i can come behind the unsolved mystery.
i can now say which process kills my boot1h sector:
Everytime i umount the hfs(EFI) partition (i've mounted it to copy kext and boot) the boot1h is empty after...
so i think that's the problem. after umount i just write the boot1h again and everything is fine.
-
Yooh Screwedx,
how is it going? Did you go for MBR or..?
Had to test EFI partition install yesterday; refreshed my memory here (http://forum.voodooprojects.org/index.php/topic,649.0.html) (seems to me the most up to date guide) and everything went fine.. almost fell in love with it again :P But, one more time, circumstances prevailed and win7 ended up the passion. When i went to boot it after install, it started treating the partitions on the GPT HDD like if they were external ones being mounted at the moment and Autoplay kicked in. This probably has also to do with the way MacDrive works; i have it installed set to "read only" and with icon/notifications hidden, it's really just to have read access like Mac has for ntfs.
It was time to revert the situation to confirm, but how? I finally had this idea: copy/paste the EFI partition from my external USB drive with Gparted Live and that did the trick.. no more Autoplay on the GPT partitions ;)
I don't know if the EFI partition file system is ok, because gParted complained about not being able to extend the file system to the whole partition; people tend to say it's just a FAT32 file system but that's not what Apple says:
http://developer.apple.com/mac/library/technotes/tn2006/tn2166.html (http://developer.apple.com/mac/library/technotes/tn2006/tn2166.html)
Anyway, everything looks fine...
See ya later.