BadAxe2 with GUID and EFI Tutorial

[BJMoose]

To get rid of the b0 error, install this way. First, partition your drive in GUID. Next, add efi 7.4 and reboot. Now add efi 8.0 and reboot. Now make your GUID partition active (you can do this before or after you actually install the OS). To make drive bootable do this in terminal:

 

sudo -s

password

fdisk -e /dev/rdiskX

update

f 2

w

answer yes

q

reboot

[tasc]

I struggled with the bootable issue as well. I tried the streamlined method from BJMoose (no reboots), but couldn't get that to work. I tried some of the guides from netkas and others with no luck. I finally got it working by just rebooting after about every step (like BJMoose has in his initial post). I must of tried 4 or 5 different times trying to get the GUID booting - I felt like Clark Griswold from Christmas vacation when he finally gets the house lit up - I got it working when I was just about to give up at 3:30am.

[The Baron]

Thanks for the encouragement BJMoose & tasc. I've set my iMac up in the same room as my pc so I can have the instructions in front of me (instead of on scraps of paper)

 

The one thing that I notice is that BJMoose refers to efi 7.4. With the latest from Netkas I get verrsion 8 and version boot_v7_guid_only. Does anyone have version 7.4 they could upload somewhere please?

 

Also, do you do this

dd if=./guid/boot1h of=/dev/rdiskXsY bs=512 count=1
dd if=./guid/boot0 of=/dev/diskX bs=400 count=1

for each efi install?

 

TIA,

 

The Baron.

[BJMoose]

Baron, in my v7.0, I'm missing the guid folder that contains boot0 and boot1h. That could be your problem also. Copy that guid folder from the v8.0 and see if that works for you. That folder (other than some gfx stuff) was the biggest difference between 7 and 7.4. Hope this helps.

[tasc]

Baron, I didn't have anything but the efi v8 package as well and just used the 'boot_v7_guid_only' for the v7.4 installation. I believe that may be the same thing, it worked for me anyways.

 

On a side note for people wondering whether it is worth it to get the GUID partition working, I haven't really noticed any difference compared to my old MBR install. I'm still getting the multiple ACL errors on diskutil repairPermissions that I was getting before (however, this seems to be fairly common even on real macs with Leopard). Also, my chain0 dual boot method doesn't work anymore, not sure if that is a result of the GUID partition or not.

 

Knowing what I know now, I probably wouldn't do it until there are some more definitive advantages of going to GUID.

[BJMoose]

Baron, I didn't have anything but the efi v8 package as well and just used the 'boot_v7_guid_only' for the v7.4 installation. I believe that may be the same thing, it worked for me anyways.

Yes, everything you need is in the v8 package. The boot_v7_guid_only is identical and both versions can access the same guid directory.

 

I've gotten a 10+ point jump in xbench using guid. This is using the exact same hard drive and software installed. How that translates into noticeable speed difference I don't know. One of the advantages for me is for backup images. I use copycatx for my hacks and my real mac pro. There's something it doesn't like about mbr partitions. I'm guessing it has to do with pc-efi. In mbr, the efi info is on the same partition as the OS. In guid, it's on its own hidden 200mb partition.

[Xeppo]

Ok, so I tried to get the installation working using the retail DVD method.

 

Everything installed properly, and the system seems to boot to the disk. Unfortunately, all I get is the gray apple logo screen and the spinning circle.

 

I've installed the dsmos and Natit ktexts. Other than that, it's a vanilla install. Anyone know why this won't boot?

[BJMoose]

Ok, so I tried to get the installation working using the retail DVD method.

 

Everything installed properly, and the system seems to boot to the disk. Unfortunately, all I get is the gray apple logo screen and the spinning circle.

 

I've installed the dsmos and Natit ktexts. Other than that, it's a vanilla install. Anyone know why this won't boot?

After installing dsmos and natit, did you repair all permissions?

[The Baron]

Still trying, hopefully I'll get it done some time next year...

 

One strange thing I've noticed is that my SATA HD has some strange behavior if I just format GUID with -ONLY- HFS partitions ie. diskutil list shows

/dev/disk1
  #:					   TYPE NAME					SIZE	   IDENTIFIER
  0:	  GUID_partition_scheme						*149.1 Gi   disk1
  1:						EFI						 200.0 Mi   disk1s1
  2:				  Apple_HFS Leopard				 20.0 Gi	disk1s2
  3:				  Apple_HFS Mac Data				128.6 Gi   disk1s3

So far so good. But then fdisk /dev/rdisk1 shows:

Disk: /dev/rdisk1	geometry: 19457/255/63 [312581808 sectors]
Signature: 0xAA55
	 Starting	   Ending
#: id  cyl  hd sec -  cyl  hd sec [	 start -	   size]
------------------------------------------------------------------------
1: EE 1023 254  63 - 1023 254  63 [		 1 -  312581807] <Unknown ID>
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

Now if I format the 2nd (Mac Data) partition FAT with Disk Utility, then diskutil list shows

/dev/disk1
  #:					   TYPE NAME					SIZE	   IDENTIFIER
  0:	  GUID_partition_scheme						*149.1 Gi   disk1
  1:						EFI						 200.0 Mi   disk1s1
  2:				  Apple_HFS Leopard				 20.0 Gi	disk1s2
  3:	   Microsoft Basic Data MAC DATA				128.5 Gi   disk1s3

but more interestingly, fdisk /dev/rdisk1 now shows

Disk: /dev/rdisk1	geometry: 19457/255/63 [312581808 sectors]
Signature: 0xAA55
	 Starting	   Ending
#: id  cyl  hd sec -  cyl  hd sec [	 start -	   size]
------------------------------------------------------------------------
1: EE 1023 254  63 - 1023 254  63 [		 1 -	 409639] <Unknown ID>
2: AF 1023 254  63 - 1023 254  63 [	409640 -   42036864] HFS+		
3: 0B 1023 254  63 - 1023 254  63 [  42708648 -  269610976] Win95 FAT-32
4: 00	0   0   0 -	0   0   0 [		 0 -		  0] unused

 

Any active partition changes then show up, where they didn't before. Ie

Disk: /dev/rdisk1	geometry: 19457/255/63 [312581808 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 -	 409639] <Unknown ID>
*2: AF 1023 254  63 - 1023 254  63 [	409640 -   42036864] HFS+		
3: 0B 1023 254  63 - 1023 254  63 [  42708648 -  269610976] Win95 FAT-32
4: 00	0   0   0 -	0   0   0 [		 0 -		  0] unused

 

I'm going to have another go, sorry for the long post but this weird behavior may be the reason this method hasn't worked for me before.

 

Fingers crossed.

[iceyone]

What about the badaxe?

 

My motherboard is a d975xbx (not xbx2) i have tried the iatkos installer (version 1.0ir2) and the kalaway installer.

 

The iatkos installer seems to install fine but then when it's time to load it sits there with an apple and a spinning icon.

 

The icon then stops spinning and nothing happens.

 

With the kalway installer it installs then when it comes time to boot, it hits a black screen and reboots, any help with this would be muchly appreciated.

[BJMoose]

Just to get familiar with things, have you tried installing Tiger on your BA board? It was very, very compatible with Tiger. I never owned that version, but there were several of the 'founding fathers/mothers' of the osx86 project who swore by that board.

[theotherone]

Sorry for crossposting this:

 

Thanks for this GUIDE BJMoose! I got this EFI-thing working on my badaxe2. I tried and succeeded with an external usb-install and with an internal sata-install (using Kalyway 10.5.1 but without letting kaly writing a bootblock which i wrote manually with your and zzaks method). EFI Install on an older internal 160 GB PATA-Drive failed...

 

After getting this to work so far i tried to install on an efi8-equipped drive from an original GM-Image of Leo. Install succeeded and i can start with that installation OK, but only up until the gray screen! Booting with -v gave me several errors of Type mDNS-Responder which i got eventually solved in some way but i never get the installation completely to boot (i only installed dsmos.kext and tried various other kextx's which usualy will be used if one installs with the BrazilMac/weaksauce-Method). I also tried with an apple.com.boot.plist for my XFX 7600 GT from this thread to no avail.

 

My goal was to get a naked Leo-Install DVD installed in an internal SATA-Drive with a minimum set of foreign kexts and then transfer this complete install with efi8 to a RAID which sits on an internal Highpoint RAID-Controllercard to boot from it. But i finally gave up on this because it was impossible to move efi8 bootable to the RAID0-HDs on the sata-controller in a form so that i can later boot from it. It stuck with a blinking cursor, no f8 possible, so EFI not found on RAID. So, goodbye efi8/GUID for install on my RAID HDs. Maybe i try this again at some time.

 

Now i switchback to the proofen weaksauce-install with EFI5.2 for Installation on my RAID0-Volume. After succesfully cloning a weaksauce-MBR-startvolume to my RAID i want now make this new install manually from within an 10.5.1-installed os, thats what i will do the next few hours:

 

- make RAID-Volume bootable with MBR and EFI5.2

- Install patched brazilmac-disc to the RAID-Volume.

- installing a few kexts a'la weaksauce

- repairing permissions

- [hopefully] boot from RAID..

 

So far my experiences and goals, maybe abit off topic, sorry.

 

Maybe you could expand your Bad-Axe 2 EFI-tutorial in a way that we could succeed with installing a original untouched Leo-Disk with as few foreign kexts as possible. This would be a good starting-point for me to try again getting my RAID finally to GUID & Efi 8.

 

Btw.: As i am on a kalyway-install with EFI8 and GUID now for 2 days, i would swear that the diskperformance seems weaker than under the weaksauce-brazilmac-Method with EFI 5.2 and MBR. I haven't wrote down the numbers but it feels like i lost a bit performance, looking into xbench seems 10 to 20 points lower than before..., i write down the numbers and will agin test under the new weaksauce-install. I know, everybody tells the other way round (GUID should give slightly better performance then MBR, but here it looks weaker, may have to do with the installation-method and the innards of the underlying brazilmac/Kalyway Techniques...).

[justvisiting]

For the original Kexts placed in /Backup by the kalyway installer, should any be placed back into /S/L/E for the BadAxe2 m/b?

[BJMoose]

For the original Kexts placed in /Backup by the kalyway installer, should any be placed back into /S/L/E for the BadAxe2 m/b?

The only kexts that this board actually needs is dsmos and a gfx kext. Some replace the appleSMBIOS.kext because it doesn't show the actual name of the processor in About This Mac. I prefer to do a simple edit to take care of that and keep my system as pure as possible.

[Mactastic]

Justvisiting did you ever solve the video corruption after sleep?

 

I have the exact same problem.

 

I'm also on a bad axe 2 and I'm using a eVGA 7600GT for my video card.

[justvisiting]

Justvisiting did you ever solve the video corruption after sleep?

 

I have the exact same problem.

 

I'm also on a bad axe 2 and I'm using a eVGA 7600GT for my video card.

 

no. foolishly i never know when to leave well enough alone.

 

i moved some /Backup kexts into /S/L/E and ps/2 kb stopped working.

 

got usb keyboard then decided to play with CPUthermo, eventually hak wouldn't boot and my kalyway dvd is at a friends and i tried iatkos for first time ever. 10 hours later i have a temporary install but major pain in butt

 

i think there are serious issues btwn leo and ba2 compared to tiger and ba2 when it comes to booting and settings active partitions and booting

 

1st time ever trying timemachine for restore - its not good enough: good for "file system level" restores but did not restore "complete" disk (ie no partition restoration, no efi or boot restoration)

 

now i'm downloading kalyway again...

 

memos to self:

if it works, don't funk with it

don't give away only booting copy of osx

keep using time machine; make dmg files of working systems as well

if it works. dont' funk with it. so important it has to be said again.

i am a moron

[BJMoose]

no. foolishly i never know when to leave well enough alone.

 

i moved some /Backup kexts into /S/L/E and ps/2 kb stopped working.

 

got usb keyboard then decided to play with CPUthermo, eventually hak wouldn't boot and my kalyway dvd is at a friends and i tried iatkos for first time ever. 10 hours later i have a temporary install but major pain in butt

 

i think there are serious issues btwn leo and ba2 compared to tiger and ba2 when it comes to booting and settings active partitions and booting

 

1st time ever trying timemachine for restore - its not good enough: good for "file system level" restores but did not restore "complete" disk (ie no partition restoration, no efi or boot restoration)

 

now i'm downloading kalyway again...

 

memos to self:

if it works, don't funk with it

don't give away only booting copy of osx

keep using time machine; make dmg files of working systems as well

if it works. dont' funk with it. so important it has to be said again.

i am a moron

Can you post as to whether your model of the BA2 is the KR or not? I think I can speak for most who don't have the KR model (and I really don't know what the difference is) that installation on the BA2 is pretty straightforward. It may be that KR makes the difference. The guid formatting is a bit more on the BA2, but once you understand that, it's just a matter of doing the extra steps. Do you have a working tiger installation? Have you tried installing from that with the retail disk? Very quick and it works well here.

[Mactastic]

I am on a KR version of the BA2, not sure what the difference is though. Personally I haven't tried installing from the retail disk, but I might give that shot today. However, sleep is the only thing that doesn't work for me right now, so maybe I should take justvisting's advice and not "funk" with it!

 

justvisiting did you try sleep with iAtkos? I'm wondering if it is an SMBIOS problem or something with efi v8?

[apooo]

Hi BJ!

 

sorry for my noob question!! :-) i´ve installed leopard on an active pc-efi 8 active partition ( man! it took the half sunday..)

 

my question:

 

how do i change dsmos.kext? can i just copy it into system/libarys/extensions, and repair permissions? was there something with the cleaning of the cache?....noob.....could you please give me a guide?

 

when i start, in verbose, i see "didn´t get hpet" 100 times-> deleted appleintelcpumanagement....no hpet anymore.

 

but! leo still doesn´t start. it stocks after negotiating ethernet with "noname mDNSResponder(37), using...b..." after this nothing happens..:.-(

 

I´ve took the dsmos from iatkos, copied it and repaired permissions...still nothing. any ideas? Is it enough to go to the diskutil and klick "verify permissions"?!?

It would be nice, if somebody posts a detailed guide how to "modify" leo after a clean Leo-GM install.

 

 

 

 

many thanx in advance

 

apoo

[Dense]

Is this trick still needed?

 

Looking at what BJMoose recommends its obvious hes falling back to a MBR compatibility layer which means he can use the normal darwin boot0 and boot1h files. This is why the OS X partition needs to be set active. Unfortunately to get a MBR compatibility table, you must have a FAT partition created by Disk Utility. If there are no FAT partitions, Disk Utility assumes you don't need a MBR synced table and just puts in the default protected entry.

 

I have debug enabled versions of boot0 and boot1h for GPT. I am looking for someone that has a problem with the original boot0 and boot1h supplied with the Netkas pc_efi files. The information this outputs will give me a very good idea why things are breaking.

[justvisiting]

ok. back. temporarily?

 

I am not sure what is the cause of our boot issues: 10.5, badaxe2, hackintosh EFI, disk utility/installer or some combination of these factors interacting.

 

solution from:

 

http://forum.insanelymac.com/index.php?sho...ic=73952&hl

http://forum.insanelymac.com/index.php?sho...c=76261&hl=

 

you need pc_efi on a USB stick. V8 works fine. You have to manually modify the boot code.

 

the "fdisk" solutions and "gparted" solutions will not always work -- i've spent the last 4 days solid booting various OSX and linux CDs and DVDs with no success.

 

I installed kalyway; one drive, GUID/GPT, pc_efi_guid, vanilla kernel + vanilla ACPI fix

 

I rebooted and OSX wouldn't start

 

I booted into kalyway and following the above links, i did the following in terminal:

 

cd /Volumes/USB_Stick

./startupfiletool /dev/rdisk0s2 ./boot_v8

dd if=./guid/boot1h of=/dev/rdisk0s2 bs=512 count=1

dd if=./guid/boot0 of=/dev/disk0 bs=400 count=1

 

rebooted and i was able to get into OSX

 

Make sure you take out your DVD

 

The better way would have been to create the partitions in disk utility, do the terminal commands, and THEN continue with the kalyway installer in the same session.

 

I still have problems that need resolving, but i think i'll try testing the "one session" solution first.

 

One thing with my ba2: when I reboot, i cannot always eject cd/dvd (only 5% of time it works). I have to manually power cycle to be able to eject a disk prior to the OS start. one i'm in an OS, all is fine.

 

 

 

Kalyway 10.5.1 leopard

motherboard: Intel D975XBX2KR

video: XFX 7600gs 256MB

optical: Pioneer DVR-212D

[justvisiting]

ok. so that wasn't it.

 

i'm back. again.

 

i'm trying to find a consistently known good process.

 

so in the past 3 or so hours, i used gparted to nuke my drive to "unallocated space" and then installed kalyway. tried using various "fixes" to get the system to boot, including the two links in my previous post.

 

the main issue is the MBR is not set correctly. the cause is currently unknown. the solution should require minimal CDs/USB keys/etc on the user part

 

current working solution:

 

a) using gparted: create one big fat32 (haha) partition

 

B ) boot kalyway, format GUID partitions, select vanilla kernel+ ACPI platform fixes, selet boot_efi_guid; install leopard; system reboots on completion

 

c) curse, "no com.apple.Boot.plist" error, remove DVD from drive,reboot

d) curse, system will not boot, tries booting from network card

 

e) boot kalyway; run the terminal commands from my above post for efi and boot block installation; reboot

 

[ code re-use ]

c) curse, "no com.apple.Boot.plist" error, remove DVD from drive,reboot

d) curse, system will not boot, tries booting from network card

 

f) boot gparted, run fdisk and NOTE that partition one is not active; make it active; reboot

 

c) curse, "no com.apple.Boot.plist" error, remove DVD from drive,reboot

 

g) system boots.

h) resolve to stop debugging this issue

 

now to fix video, ps2 vs usb keyboard, etc

 

Kalyway 10.5.1 leopard

motherboard: Intel D975XBX2KR

video: XFX 7600gs 256MB

optical: Pioneer DVR-212D

[apooo]

I´ve installed on my badaxe2, on a activated efi8.0 guid formatted partition, leopard from the gm dvd, everything managed fron a separate leo installation, but now, leo still doesn´t start. it stocks after negotiating ethernet with "noname mDNSResponder(37), using...b...

 

i´ve added dsmos.kext and natit.kext, deleted appleintelcpu..changed ionetworkingfamily.kext, also changed applesmbios....changed permissions and repaired permissions nothing helps!

 

when i start with -x -v, it always stocks at "noname mDNSResponder(37), using...b..."

 

can somebody help me!?

 

should i try, not to repair permissions in diskutil after changing kexts?

 

apoo

[apooo]

well, i finally did it! it works fine, but the marvell sata controller was not recognized, so I´ve changed the AppleAHCIPort.kext with the one from iatkos (where all drives are recognized, incl. marvell esata) and suddenly, i had all drives!!! i was so happy, until the next start. Using -v, there is written in yellow: couldn´t load AppleAHCIPort.kext.

 

Are there more dependencies? Do I have to change more kexts?

 

 

apoo

[Vinnie-The-Phoo]

Hi Guys,

 

I am working for Intel so I think I can answer the different version questions best

There are 2 versions of the BX2 , Workstation and Desktop,Workstation code : S975XBX2Desktop: D975XBX2

 

I am trying to get more intricate details in the North and South side busses and what are the exact differences so that we can put to rest which version of Leo will work best .

 

I will report back asap...

 

forgot to mention the BADAXE2 Desktop version Boxed mobo (bought from your local hardware outlet) code is : BOXD975XBX2KR and Workstation boxed mobo code is : S975XBX2these are single mobo's per box and not 5 mobo's to a OEM box (hope this makes sense?)