[GUIDE] Scripted Yosemite/Mavericks Install on Gigabyte Mobos

[digital_dreamer]

(sorry for the PM dd, able to post now)

 

I can't update to 10.6.7. I've been using this script for about 2 years or so and always have some kind of issue when updating but usually it's fixable. When I update I get the "Still waiting for root device error". I reinstalled from 10.6.0 and it works fine until I update and get the same issue.

 

I'm running a different motherboard, (MSI X58 Platinum) I know it's not the usual but I would appreciate some feedback as what I can do. I'm just trying to play Portal 2 ANY help is appreciated thank you.

For some reason the BIOS is not loading the bootloader or accessing the correct partition where the system is located.

I'm confused as to why this is working for you in 10.6, but not after a update.

 

Questions:

How are your hard drives set up in the BIOS?

Does your boot drive have priority in the BIOS?

Do you have more than one partition on the drive where your system is installed?

Have you tried reinstalling the bootloader after updating your system?

 

A casual look at your Install.log may reveal some issues.

 

best of wishes,

MAJ

[AppleIIGuy]

I don't understand I took the graphics card from the latest iMacs (my goal was to build a hack as close as possible from an iMac).

 

Yes but Apple ATI video cards have different Id's then off the shelf ati cards

[jhrfc]

Success! I now have a working install of DP2, including network, sound, graphics, and sleep (thanks to CruiSar for tip to set startup automatically after power failure in system prefs).

The only problems I can see now, apart from the pesky double fault KP, is the system will not restart and resets the bios when you hit reset, these are I guess both bootloader related? (I'm using the chameleon build from DDs latest script.)

 

 

Cheers

Jon

[digital_dreamer]

Success! I now have a working install of DP2, including network, sound, graphics, and sleep (thanks to CruiSar for tip to set startup automatically after power failure in system prefs).

The only problems I can see now, apart from the pesky double fault KP, is the system will not restart and resets the bios when you hit reset, these are I guess both bootloader related? (I'm using the chameleon build from DDs latest script.)

 

Cheers

Jon

Congrats!

 

RE: BIOS reset

Have you installed a patched DSDT file from the script or copied the SL version to Lion?

If that's not working, let me know. As an alternative, you can try the ElliottForceLegacyRTC.kext from the 10.6 kexts in Misc_Patches/_repository.

 

best regards,

MAJ

[digital_dreamer]

Just wanted to know if anyone else gets a kernel panic on Lion DP2 (430e) when they install voodoohda 2.7.2? Haven't been able to install voodoohda without getting an kernel panic immediately (when the script was creating the kernelcache I already got a kernel panic)...

I did more tests and have not been able to run into any KPs when installing VoodooHDA 2.7.2. I reinstalled with no KP, uninstalled, rebooted, and reinstalled again with no issues. Perhaps, you may have other audio related kexts installed? VoodooHDA is very sensitive to the presence of other audio kexts that can conflict. What about a modded DSDT with audio-related patches?

 

MAJ

[CruiSAr]

Congrats!

 

RE: BIOS reset

Have you installed a patched DSDT file from the script or copied the SL version to Lion?

If that's not working, let me know. As an alternative, you can try the ElliottForceLegacyRTC.kext from the 10.6 kexts in Misc_Patches/_repository.

 

best regards,

MAJ

I think Jon is using a patched DSDT and is missing a restart shutdown kext. With Snow Leopard, the shutdown was incorporated into the DSDT but restart was handled by the bootLoader.

 

I have the same issue when I restart from Lion DP1 and DP2, the board resets itself.

[digital_dreamer]

Lion users:

 

Andy and developers have released a PC-EFI chameleon bootloader version that will boot Lion without the DF KP. Yay!

Just un-compress and drop this boot file into /~extra/Bootloaders/PC-EFI_v10.6_Lion/i386 and replace the existing one in the script. Install using the script.

(I assume this stage-2 booter file is all that's needed. The other stage-0 and stage-1 booters in the directory can remain the same. However, let me know if this isn't working!)

 

Note that this is a non-GUI version and supports both Lion and Snow Leopard. It supposedly supports kext loading in /Extra for Lion, either via cache or whole kext, just like SL. I'm only using it for Lion, as it doesn't support the many new features in RC5.

 

The script currently won't recognize this boot file - it'll just say, "Bootloader based on Chameleon v2.0-RC3 r installed."

I'll get around to adding support for these changes in the next script update.

 

MAJ

[tsunoo]

Lion users:

 

Andy and developers have released a PC-EFI chameleon bootloader version that will boot Lion without the DF KP. Yay!

 

 

MAJ

 

Yes! It works!!!

Well done : you, andy and cruisar

 

[digital_dreamer]

The Chameleon trunk has been updated to revision 752, which includes all the new patches.

So, put this boot file in "Chameleon_2.0_RC5/i386" and delete the custom "PC-EFI v10.6 Lion" version, as we don't need it any more.

 

This works for both Snow and Lion, and includes all that was in RC5. It will work with a GUI for Snow, but revert to non-GUI in Lion.

I'll get a script update out that will allow building a boot cache in /Extra for Lion, so we can install our kexts back into /Extra.

 

MAJ

[digital_dreamer]

Just a heads-up regarding the updated Chameleon RC5 Lion bootloader:

I mistakenly said that the Lion boot was non-GUI, but realized I'm using the no-GUI flag for it.

So, the GUI does work for Lion. However, it will be a long wait as you wait for all the kexts to load. The bootloader acts like the "ignore cache" flag is set and will always load the kexts from S/L/E, because there is no boot cache. It apparently ignores the kernelcache. So, I suggest using the "GUI"="No" flag or turning verbose off to speed things up.

 

In the meantime, I will have the script create a boot cache, just like we had in Snow.

Now, I got to go comment out/change all my Lion modifications back to where they were. Now, if I had just left everything alone, instead of rushing in and making those changes. I was afraid of this.

 

Looking at the new RC5 diff (source code changes), they have done a tremendous amount of work on this. Rewriting lots of code.

All credits go to the Chameleon team, Andy Vandijck, cparm, netkas, and all involved in the development in any way.

 

MAJ

[ClemsonJeeper]

I was wondering if anyone had experience with using an internal SATA 3 (6.0GB/s) card with a drive attached to it as the boot drive for OSX on this motherboard?

 

I'm currently running with a SSD (3GB/s interface) tied into the on-board SATA connectors, but am wanting to upgrade to a faster SSD this season and it seems all the new ones are 6GB/s interface drives, which means I need to get an add-on card to control them.

 

I was just wondering if there is any issue with getting OSX to boot up off a drive attached to a external add-on SATA card.

 

Likely the card I'm going to get is the Highpoint Rocket 620 PCI express card which (supposedly) is fully supported under OSX.

 

Anyone happen to have any experience with this? Never got a response.

[veddernick]

The new Bootloader of lion its here http://netkas.org/ netkas and cparm did it everything now it's fixed for Lion dp thanks to them and you. And the boot file and sources here

Files.zip

[jhrfc]

Congrats!

 

RE: BIOS reset

Have you installed a patched DSDT file from the script or copied the SL version to Lion?

If that's not working, let me know. As an alternative, you can try the ElliottForceLegacyRTC.kext from the 10.6 kexts in Misc_Patches/_repository.

 

best regards,

MAJ

 

 

Thanks! i've now moved to the new chameleon bootloader but still had the bios reset problem, however ElliottForceLegacyRTC.kext as above fixes the problem for me.

 

The Lion install is now pretty much good to go for me. I'll now play around with my apps etc, to see how they fare.

Cheers

Jon

 

 

Edit: must have been a one off, the bios still resets itself

[fruitbat04]

I thought I'd give Lion DP2 another crack and the new bootloader has helped as I can now get all the way into the installed from a boot disk.

 

However I now get a message before the installer allows me to do anything saying "Lion cannot be installed on this computer".

 

This isn't a kernel message or anything, just one from the Lion installer.

 

Is there any way round this?

 

I used by DSDT from my 10.6 install which is perfect but the latest Netkas boot loader and FakeSMC kext.

[digital_dreamer]

I thought I'd give Lion DP2 another crack and the new bootloader has helped as I can now get all the way into the installed from a boot disk.

 

However I now get a message before the installer allows me to do anything saying "Lion cannot be installed on this computer".

 

This isn't a kernel message or anything, just one from the Lion installer.

 

Is there any way round this?

 

I used by DSDT from my 10.6 install which is perfect but the latest Netkas boot loader and FakeSMC kext.

Look into /System/Library/CoreServices on your installer disk and you'll find the PlatformSupport.plist that should be deleted.

The Boot Disk routine in the script should be deleting this plist, if found, so I wonder how this was installed or ignored.

 

MAJ

[CruiSAr]

Thanks! i've now moved to the new chameleon bootloader but still had the bios reset problem, however ElliottForceLegacyRTC.kext as above fixes the problem for me.

 

The Lion install is now pretty much good to go for me. I'll now play around with my apps etc, to see how they fare.

Cheers

Jon

 

 

Edit: must have been a one off, the bios still resets itself

ElliottForceLegacyRTC.kext is used when you do not have a DSDT present. Remove that kext and install EvoReboot To S/L/E

[raymondh]

Here's my specs:

 

GIGABYTE GA-EX58-UD4P

Intel Core i7 920 2.66GHz

Corsair TR3X6G1600C9 XMS3 12 GB

eVGA e-GeForce 9800GTX+

 

Installed following DD's script currently at 10.6.6

 

This build has been running perfectly since Leopard but recently it has started randomly (I think) locking up where the screen freezes except for the mouse cursor (but I can't click anything). I can't ssh in, all the shared network drives drop from my other systems, etc.

 

I have to hit the reset button then everything is okay.

 

I have 4 internal SATA hard drives, a SATA BD, and a Drobo S running off a SATA to eSATA cable. The drobo is new and I had the freezes prior to installing it. I also have USB WD 1tb drive for Time Machine.

 

It isn't overheating and I've done a mem test and didn't find any problems.

 

Any ideas what could cause this?

[digital_dreamer]

raymondh,

Are you getting the beachball or just a movable cursor?

I'd put money on a dying hard drive.

 

Check your logs.

 

MAJ

[raymondh]

raymondh,

Are you getting the beachball or just a movable cursor?

I'd put money on a dying hard drive.

 

Check your logs.

 

MAJ

 

No beachball, just a movable pointer.

 

I have smartreporter set up on all the drives except the WD external. I'm not sure what logs to check or what to check them for. Any pointers?

[digital_dreamer]

No beachball, even after clicking? That's interesting.

Doesn't sound like hard drive, then. A GPU freeze would affect your mouse, too, so that's out of the picture.

I'm thinking this is network related. Do you have network drives on the desktop? I wonder if they are dropping off the network and the OS is trying to locate them? How long have you waited? I bet if long enough it may timeout and unmount your shared drive(s).

Do the lockups still happen if you are not connected to the network or you don't have any shared devices connected? Are all devices connected to a single switch/router? How about trying a different switch or port?

 

I'd keep an eye on the time of the freeze event, then check the Console "All messages" for a log around that time after rebooting. After several events, look for a pattern.

 

Do you get any GUI updates on the screen, like clock, etc. If so, see if keeping the Console window open reveals anything.

 

MAJ

[raymondh]

No beachball, even after clicking? That's interesting.

Doesn't sound like hard drive, then. A GPU freeze would affect your mouse, too, so that's out of the picture.

I'm thinking this is network related. Do you have network drives on the desktop? I wonder if they are dropping off the network and the OS is trying to locate them? How long have you waited? I bet if long enough it may timeout and unmount your shared drive(s).

Do the lockups still happen if you are not connected to the network or you don't have any shared devices connected? Are all devices connected to a single switch/router? How about trying a different switch or port?

 

I'd keep an eye on the time of the freeze event, then check the Console "All messages" for a log around that time after rebooting. After several events, look for a pattern.

 

Do you get any GUI updates on the screen, like clock, etc. If so, see if keeping the Console window open reveals anything.

 

MAJ

 

 

I just did a verify disk on the USB drive and it was fine. I then did a verify on the boot drive and it froze (could still move the mouse). I had activity monitor opened at the time and nothing was using much CPU.

 

I unplugged the USB Time Machine drive and everything came back but Disk Utility had a pop up that said I needed to boot from a different drive and repair the boot disk.

 

I booted to my backup drive and ran verify on the drive and got the attached errors.

 

 

 

I ran repair and it said it was successful and I also repaired permissions.

 

I've now rebooted into the system and we'll see how it does. I was also noticing the mouse seemed a bit jumpy today as well but I haven't had that happen since booting back into the repaired drive.

[digital_dreamer]

raymondh,

Do you have journaling enabled for your boot disk? You can see it under file system or format in Disk Utility.

Directory issues should be a bit rare with a journaled file system, but can happen under specific conditions and if the drive is experiencing hardware failure.

 

If you have DiskWarrior 4 on a maintenance drive, I'd do a check with that, as Disk Utility is very basic.

 

MAJ

[jhrfc]

ElliottForceLegacyRTC.kext is used when you do not have a DSDT present. Remove that kext and install EvoReboot To S/L/E

 

Thanks! That has done the trick. I can now restart without reset of the bios.

Jon

[raymondh]

raymondh,

Do you have journaling enabled for your boot disk? You can see it under file system or format in Disk Utility.

Directory issues should be a bit rare with a journaled file system, but can happen under specific conditions and if the drive is experiencing hardware failure.

 

If you have DiskWarrior 4 on a maintenance drive, I'd do a check with that, as Disk Utility is very basic.

 

MAJ

 

Journaling is enabled. I don't have diskwarrior but it looks like I should go ahead and buy it. The boot drive is a 1TB WD black that is about 9-months old.

 

Do you think that if I use CCC to clone the drive to update my backup boot drive I could cause the problem to be copied to my backup drive? I just don't want to take a big step back if this drive dies.

 

 

------Another question--------

 

Sometimes (often) when I boot right after "verifying DMI pool" the spinning line in the upper left of the screen doesn't spin, it just hangs and I have to reset. Sometimes I have to reset a couple of times before it makes it past that and gives me the chameleon screen.

 

Is there a way I can tell it to not scan the drives and just boot from my boot drive?

[jhrfc]

Been playing with Lion to see what works, and I found my nvidia gtx285 cinebench score was about half what it was under snow leopard.

I found I had to edit AppleGraphicsPowerManagement.kext/Contents/Info.plist as in doods thread.

 

d00d's DSDT mod thread.

 

I also reinstalled the mods linked to there about setting my GPU fan speeds to auto on boot and wake from sleep.

This now all seems to work, and in fact I seem to get slightly higher score in lion the SL now e.g. 35fps verus 29fps.

 

I also got istat menus to work as detailed here:

istat menus under lion

 

One thing I've noticed is that even though the boot plist says arch=i386, my system boots the 64bit kernel, any ideas?

Cheers

Jon