Jump to content

[GUIDE] Scripted Yosemite/Mavericks Install on Gigabyte Mobos

digital_dreamer

By digital_dreamer,
in Tutorials (The Genius Bar)

 Share
4,696 posts in this topic

Recommended Posts

AndreaM
AndreaM
Posted
Posted

Hi all,

anyone has installed 10.6.2 succesfully on this hw ?

I've insanely started a combo update (not systemUpdate, downloaded the 500 MB pack and installed), and KP ! (what emotion, my first ! ;) "... CPU id does not match ..." )

So, i've started a new install and TimeMachine restore ... and i am coming back to 10.6.

Thereafter i read some post and 10.6.2 upgrade seem not so simple.

 

Any advice ?

Link to comment
Share on other sites
MasterLen
MasterLen
Posted
Posted
By audio interfaces, I am assuming you are referring to external firewire connected interfaces, not the integrated sound card, or USB card based interface.

 

On the internal sound, using the emilo DSDT/EFI method, no sound glitches are heard while transferring data via firewire.

 

There were issues using the voodoo kext with the mouse,firewire and audio using the RC3 method.

 

 

I don't speek about DATA TRANSFER from a Hard Drive.....

 

I am speaking about firewire AUDIO interfaces for making music with logic for example.....

Link to comment
Share on other sites
VirusX
VirusX
Posted
Posted
Hi all,

anyone has installed 10.6.2 succesfully on this hw ?

I've insanely started a combo update (not systemUpdate, downloaded the 500 MB pack and installed), and KP ! (what emotion, my first ! ;) "... CPU id does not match ..." )

So, i've started a new install and TimeMachine restore ... and i am coming back to 10.6.

Thereafter i read some post and 10.6.2 upgrade seem not so simple.

 

Any advice ?

 

common... please read through the last few pages... you have to update your sleepenabler..

Link to comment
Share on other sites
Phil Marlowe
Phil Marlowe
Posted
Posted
But there are issues with audio interfaces(glitches and distortions)!

 

Hi,

my presonus firebox, connected via Firewire 400 works like a charm without glitches and distortions. Perhaps it's not an issue related to firewire but to the I/O Buffersize you can specify in Logic. I assume you use an Buffersize about 32 Samples. Try it with 64 Samples, it just has an minimal effect on the resulting roundtrip latency and often resolves glitching and distorsion....

Does it help?

Link to comment
Share on other sites
MasterLen
MasterLen
Posted
Posted
Hi,

my presonus firebox, connected via Firewire 400 works like a charm without glitches and distortions. Perhaps it's not an issue related to firewire but to the I/O Buffersize you can specify in Logic. I assume you use an Buffersize about 32 Samples. Try it with 64 Samples, it just has an minimal effect on the resulting roundtrip latency and often resolves glitching and distorsion....

Does it help?

 

 

Hi,

 

It doesnt help...I can set the I/O Buffersize to 256, there is no effect.

There is another issue with firewire for me...

If I boot with my Interface(Audiofire 4) plugged the boot time is the twice or more....

 

In Win 7 there is no issue like this... I can set the buffersize to 32 Samples without any issues!

 

And there is no issues in a real mac!

 

What now?

Link to comment
Share on other sites
Phil Marlowe
Phil Marlowe
Posted
Posted
Hi,

 

It doesnt help...I can set the I/O Buffersize to 256, there is no effect.

There is another issue with firewire for me...

If I boot with my Interface(Audiofire 4) plugged the boot time is the twice or more....

 

In Win 7 there is no issue like this... I can set the buffersize to 32 Samples without any issues!

 

And there is no issues in a real mac!

 

What now?

Damn, i hoped that i could help you to solve the problem. But it seems that you need the help of the Pro's in this forum, sorry. I just can say that my presonus works fine. Sorry dude und Grüße aus dem P'berg!

Link to comment
Share on other sites
MikeBuzzsaw
MikeBuzzsaw
Posted
Posted
Thank you Mike... your a lifesaver..!!!!

 

Problem with ATI 4870 hd card. (You can imagine how badly I want to get this working!)

 

Had this card in my initial build and it wouldn't boot all the way to snow leopard (froze on the last line of script)....

 

Took it out and put in an nvidia which allowed me to enter snow leopard.

 

Now that I can get into Snow Leopard.... can I install Natit's package or a kext for the ati card in the extra folder ..shut down..pull the nvidia and put the ATI card back in or isn't it that simple?

 

Thanks everyone...appreciate some input on this!

 

Was the kext installed before? Keep the nvidia in the extras folder and add the ati kext. Run the DD script and boot caches. Insert the ati card and see if it works. If it doesn't you might have the wrong kext. Put back the nvidia in, it should work still.

Link to comment
Share on other sites
rabbit74
rabbit74
Posted
Posted
Firewire Just Works Booth SL and SL Server.

 

What bootloader did you use in your instalation?

 

Which Kext install did you choose? ie. n-Normal, c-Combo, s-Super-Combo - to "system" or to "extra" or both?

 

I actually did get the firewire working once but have not been able to recreate the successful steps on a second machine.

 

I have had the most general success with bootloader "PC-EFI_v10.3" then "n-Normal Cache build to extra"

 

This gets me a working bootable system every time but no firewire. The one time I got firewire working was a few days after having the system up and running I changed the bootloader to "chameleon_2.0_RC3" and then on reboot the firewire just appeared and started working. Trying to repeat this process has yielded no success so I believe I must also build cached to "System" or something else.

 

If your firewire "Just works" I would really appreciated it if you could detail your install steps for me with specific interest in your boot loader and where you are installing the Kext to in "step 4" and the further specifics of details of "step 5" where are you updating your boot caches to?

 

Appreciate the feedback.

 

Powel

Link to comment
Share on other sites
mrycar
mrycar
Posted
Posted
What bootloader did you use in your instalation?

 

Which Kext install did you choose? ie. n-Normal, c-Combo, s-Super-Combo - to "system" or to "extra" or both?

 

I actually did get the firewire working once but have not been able to recreate the successful steps on a second machine.

 

I have had the most general success with bootloader "PC-EFI_v10.3" then "n-Normal Cache build to extra"

 

This gets me a working bootable system every time but no firewire. The one time I got firewire working was a few days after having the system up and running I changed the bootloader to "chameleon_2.0_RC3" and then on reboot the firewire just appeared and started working. Trying to repeat this process has yielded no success so I believe I must also build cached to "System" or something else.

 

If your firewire "Just works" I would really appreciated it if you could detail your install steps for me with specific interest in your boot loader and where you are installing the Kext to in "step 4" and the further specifics of details of "step 5" where are you updating your boot caches to?

 

Appreciate the feedback.

 

Powel

 

Am using one drive with Chamelen RC3

Other drive using PC-EFI 10.5

 

PC-EFI method am able to run with less kexts, and am DSDT from emilio's post on page 34

Am running super combo and kexts are as follows

fakesmc -Extra

LegacyHDA-System

NullCPU-extra

Openhalt-extra

sleep6.2-extra

Platformuuid-extra

 

Everything works in 32/64

 

Nothing special for Firewire, am using FW for mass of disk storage, so no issues doing that

Link to comment
Share on other sites
rabbit74
rabbit74
Posted
Posted
Am using one drive with Chamelen RC3

Other drive using PC-EFI 10.5

 

PC-EFI method am able to run with less kexts, and am DSDT from emilio's post on page 34

Am running super combo and kexts are as follows

fakesmc -Extra

LegacyHDA-System

NullCPU-extra

Openhalt-extra

sleep6.2-extra

Platformuuid-extra

 

Everything works in 32/64

 

Nothing special for Firewire, am using FW for mass of disk storage, so no issues doing that

 

Files to be installed from
the script's folders to snow500 - EFI:

ATA					VERSION	 ARCH	 SIZE  DESTINATION
1) AppleIntelPIIXATA.kext		  2.5.1	 x86_64	 280K	   /Extra
2) IOAHCIBlockStorageInjector.kext 1.1.1		N/A	   4K	   /Extra
3) JMicronATA.kext				 1.0.0	 x86_64	 180K	   /Extra

Audio
4) AppleHDA.kext				   1.4.0a23	i386	 1.2M	   /Extra
5) HDAEnabler.kext				 1.0.0d1	 i386	  36K	  /System

Graphics
6) ATY_Init.kext				   1.0.0d1	 i386	 520K	   /Extra

Networking
7) AppleRTL8169Ethernet.kext	   1.1.4a5	 i386	 1.3M	   /Extra

Misc Patches
8) fakesmc.kext					2		 x86_64	 124K	   /Extra
9) NullCPUPowerManagement.kext	 1.0.0d2   x86_64	 116K	   /Extra
10) OpenHaltRestart.kext			1.0.3	 x86_64	 100K	   /Extra
11) PlatformUUID.kext			   1.0.0	 x86_64	 104K	   /Extra
12) SleepEnabler.kext			   1.0.0	 x86_64	 112K	   /Extra

Kernel & matching kext
(No files present to install)


Key in kext number to change its destination.
Run kext installer and update boot cache using the following options:
N) Normal cache build (separate caches)
C) Combo cache build to /Extra
S) Super combo cache build to /Extra
E) Exit

Your choice?:

 

So I tried running this step as Super combo to EFI - /Extra and as you said and everything works but still no firewire.

 

What am I doing wrong?

 

Powel

Link to comment
Share on other sites
mrycar
mrycar
Posted
Posted
What am I doing wrong?

 

Powel

 

I see nothing in your setup that would prevent firewire from operating.

 

I would recommend checking bios settings or the connection/power status of the device.

 

You may want to launch with -v in from the bootloader and catch what the status of firewire is while it is booting, or check the logs for your firewire status.

Link to comment
Share on other sites
rabbit74
rabbit74
Posted
Posted

I have 2 separate drives one with firewire working and one with firewire not working.

 

I plug in one and boot and firewire works, I plug in the other and firewire doesn't work. I have reinstalled on the drive that it doesn't work on several times with different configurations but no dice. so I am pretty sure it ain't BIOS.

 

My system boots Verbose as default, when I boot the system that works I just get "Firewire configured - max 400Mps"

 

On the other I get "Firewire not configured"

 

That make any sense?

 

Is there a firewire kext I can try?

 

Thanks for the feedback.

 

Powel

 

I see nothing in your setup that would prevent firewire from operating.

 

I would recommend checking bios settings or the connection/power status of the device.

 

You may want to launch with -v in from the bootloader and catch what the status of firewire is while it is booting, or check the logs for your firewire status.

Link to comment
Share on other sites
Vasto
Vasto
Posted
Posted

Hey guys, I have an issue.

I upgraded to 10.6.2 without deleting sleepenabler.kext (I know, I should have read first). Then I got Snow Leopard install disk to boot, used the terminal to delete /Volumes/EFI/Extra/sleepenabler.kext, /Volumes/EFI/Extra/Extensions.mkext, and /Volumes/Main/System/Library/Caches/Extensions.mkext (This is from memory so the exact paths/file names may be a little off). Now, when I try to boot into either my HDD or the Installation DVD I get a panic.

 

panic(cpu 0 caller 0x77b6df60): "No HPETS available...CPU(s) configured incorrectly\n"@/SourceCache/AppleIntelCPUPowerManagement/AppleIntelCPUPowerManagement-90/pmThread.c:148

 

Any clues on how to fix this? I'm guessing I'm going to need to borrow someone's mac and drop a kext into my EFI and rebuild. But what kext is needed to fix this?

Link to comment
Share on other sites
d00d
d00d
Posted
Posted
Hey guys, I have an issue.

I upgraded to 10.6.2 without deleting sleepenabler.kext (I know, I should have read first). Then I got Snow Leopard install disk to boot, used the terminal to delete /Volumes/EFI/Extra/sleepenabler.kext, /Volumes/EFI/Extra/Extensions.mkext, and /Volumes/Main/System/Library/Caches/Extensions.mkext (This is from memory so the exact paths/file names may be a little off). Now, when I try to boot into either my HDD or the Installation DVD I get a panic.

 

panic(cpu 0 caller 0x77b6df60): "No HPETS available...CPU(s) configured incorrectly\n"@/SourceCache/AppleIntelCPUPowerManagement/AppleIntelCPUPowerManagement-90/pmThread.c:148

 

Any clues on how to fix this? I'm guessing I'm going to need to borrow someone's mac and drop a kext into my EFI and rebuild. But what kext is needed to fix this?

NullCPUPowerManagement.kext or similar has been removed?

Instead of moving it back, you could fix the HPET section of your DSDT so that AppleHPET, AppleIntelCPUPowerManagement and AppleIntelCPUPowerManagementClient kexts load without having to use NullCPUPowerManagement.

See the topic linked in my signature for more information.

Link to comment
Share on other sites
digital_dreamer
digital_dreamer
Posted
  • Author
Posted
Noticed that some drives that I have, would not run the DD script properly. They were not releasing the EFI partition after copying the boot and extras stuff to it. When the partition was being made active in the script all files would vanish and the EFI partition would not be able to be eject or beunmounted. A reboot would unmount the efi partition, but it would be empty.
Same issue here on a SSD drive. Unmounting fails because of a 'device busy' error.

 

The problem occurs in the buildcache script (installed into /var/root/Library/Scripts).

After unmounting it executes 'rm -rf /Volumes/EFI', which deletes all the data on the EFI volume instead of removing just the mount point directory because it did not unmount successfully.

 

I just removed that specific line for now. For functionality sake it does not matter if the volume gets unmounted or not, next reboot the /Volumes/EFI will have disappeared anyways.

Yeah, I've been aware of this bug for awhile. As darkvoid already noted, the first attempt at formatting the EFI partition will leave the partition busy and will fail to unmount, thus causing the partition to be erased when the directory is removed.

 

However, in my experience, an immediate second attempt to install the bootloader will succeed. Why it'll work the second time and not the first, I don't know. So, run the bootloader install twice if installing for the EFI partition.

I'll find a clean, elegant way to get around this issue soon. AFAIK (at least in Leo), it does need to be cleanly unmounted to allow it to be mountable and viewable. However, if errors appear on a mount attempt, the script will perform a file system check, anyway.

 

best of wishes,

MAJ

 

EDIT: Have any of you who are using a EFI boot setup on 10.6.2 and my script noticed the Finder crashing when accessing the EFI partition, like during "Modify Plists"? If so, you'll need to comment out or delete the "sync" command in the unmount_EFI routine of the script.

Link to comment
Share on other sites
LocusOfControl
LocusOfControl
Posted
Posted
Firewire doesn't work properly on this board!!!!

This error for example: "FireWire runtime power conservation disabled. (2)"

 

There are many threads with firewire issues!

 

Here for example: http://www.insanelymac.com/forum/index.php?showtopic=191029

 

Or here: http://www.insanelymac.com/forum/index.php...8920&st=340

(from page 13)

Master Chief is trying to find a solution for this issue!

 

Firewire works fine on my board, I use it to connect a Nikon Coolscan 4000ED slide scanner.

The native Leopard nikon driver doesn't work properly in SL but vuescan has a SL update

 

steve

Link to comment
Share on other sites
pbj
pbj
Posted
Posted
You can use Apple's own MacBook 32/64bit Airport N mini card with MP2W-2458 or MP2W-2400 adapter.

Here are the links:

 

http://cgi.ebay.com/Apple-Macbook-Airport-...1018136002r6149

 

It fits perfectly in short and hard to use (because of the heat sink) PCIE x1 slot on the motherboard.

 

Hey!

 

This one just arrived from china and doesn't fit into my PCIE x1 slot on my UD5.. The left connector of this card is around 2mm to long for the slot.. :D

Link to comment
Share on other sites
Emilo
Emilo
Posted
Posted
Hey!

 

This one just arrived from china and doesn't fit into my PCIE x1 slot on my UD5.. The left connector of this card is around 2mm to long for the slot.. ^_^

 

AR5BXB72 300M mini card is installed inside MP2W adapter which goes into PC-E x1 slot.

It fits like a glove. I know 3 more users in this thread which use this solution.

 

Link to comment
Share on other sites
pbj
pbj
Posted
Posted
AR5BXB72 300M mini card is installed inside MP2W adapter which goes into PC-E x1 slot.

It fits like a glove. I know 3 more users in this thread which use this solution.

 

 

you are perfectly right! i missed the link to the adapter... thx!

 

e.:/ do you know a good alternative to HWtools, since both adapters are out of stock...

Link to comment
Share on other sites
BlueSky2000
BlueSky2000
Posted
Posted

Hi guys, I need help with updating to 10.6.2 from 10.6.1. These are the steps that I took.

1. Replaced sleepenabler.kext in /Extra/Stored_Kexts with new SleepEnabler.

2. Updated build cache

3. Applied 10.6.2

4. Rebooted

And I get KP. What am I doing wrong?

From reading it should update w/o any error.

I don't have any special Kext. Thanks all.

Link to comment
Share on other sites
fade2nada
fade2nada
Posted
Posted
Hi guys, I need help with updating to 10.6.2 from 10.6.1. These are the steps that I took.

1. Replaced sleepenabler.kext in /Extra/Stored_Kexts with new SleepEnabler.

2. Updated build cache

3. Applied 10.6.2

4. Rebooted

And I get KP. What am I doing wrong?

From reading it should update w/o any error.

I don't have any special Kext. Thanks all.

 

The process if followed correctly is pretty easy:

 

How to update to 10.6.2:

- Delete existing SleepEnabler.kext located in /Extra, update caches and restart

- Install 10.6.2 update and restart.

- After booting into OSX 10.6.2, install attached SleepEnabler_10.6.2_.kext to /Extra and update caches.

 

POST #661

 

It seems to me that you messed up the sequence. Delete your original sleepenabler kext first > install update > install new sleepenabler kext ( using script or KEXT tool/app ) exactly like above and you should be OK.

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...