[GUIDE] Retail OS X Install (10.5.8) on Gigabyte GA-EX58-UD5 (Core i7) Mobo

[tsunoo]

A guy called "trauma23", french member (like me ) of this forum, explained me once how to make them hotplugable, and sent me kexts and everything, but I didn't understood a word he was writing and decided to forget it. But I know he has been successful with fixing this problem. Maybe you can PM him or make a search on the forum...I'm sure he can manage with english conversation.

 

 

Firewire issues

 

I guess I have to buy first and try then. I let you know.

moi je vais voir ce qu'a écrit trauma23. Peut-être le comprendrais-je... [edit] bon j'n'ai rien trouvé

 

About Firewire: I could control my video camera to import via firewire my movies.

But you ask about firewire hard drive and I don't have any idea if it works.. but it should.

[digital_dreamer]

Ok, here's what my EFI installation looks like:

 

And here is the boot.plist:

 

I WAS able to Quicklook the info.plist of each kext so I guess they're alright. In order to replace the old kext with the new ones do I have to redo the partition and add the kext before wolienuke's script?

 

Is there a way to see the entire boot log? because all I see at the end are things like:

 

extension "com.apple.iokit.IONetworkingFamily" cannot be found

can't determine immediate dependencies for extension com.psystar.driver.RealtekR1000

can't determine immediate dependencies for extension com.apple.driver.AppleRTL8169Ethernet

couldn't alloc com.psystar.driver.RealtekR1000

couldn't alloc com.apple.driver.AppleRTL8169Ethernet

As mentioned previously, you can look into /Volumes/YOURHARDDRIVE/private/var/log

There may be a total of 8 system logs, with system.log being the most recent, system.log.0.bz2 being older, down to system.log.7.bz2 being the oldest.

I know you got the system running now, but I'm curious to find if in any of those system logs that you have a few lines saying, "Can't parse plist.." or something like it. If you find them, let us know. That would confirm a theory I have regarding wolfienuke's script and what must be done to fix it.

 

Brief update/question on my struggle.

 

So I got Kalyway installed on one drive, yay...

 

Tried to install 10.5.4, but as that DVD is not structured the same way as the mentioned Retail DVD's I have yet to manage to force it to install.

BUT I do think that most of my issues might be related to the following:

 

On boot after setting up the bios according to the first post the post screen flashes very quickly and does not respond to the keyboard (a few tenth of a second) After this I can boot to the Kalaway installed disk with no problem. But if I remove the kalaway drive and tries to do it from scratch the board reboots shortlyafter DARWIN starts to load it just goes trough a few lines...

 

Clearing the cmos only changes this for one boot sequence, as soon as I reboot again the bios wierdness is back.

 

Any ideas for a possible fix, or would this be normal behaviour?

Are you saying the path to the installer on the 10.5.4 DVD is not the same as older DVDs? Would be helpful to know and confirm.

The BIOS POST screen is visible only very briefly and doesn't respond to input? Is USB keyboard and Mouse enabled in BIOS?

After removing Kalaway disk, you say system reboots after DARWIN starts to load... do you mean system reboots after the DARWIN prompt has appeared and bootloader attempts to boot into OS?

 

Hi, I can boot from Chamaleon but I feel with EFI I have more control over the kext I can pre load.

 

my disk0 have 3 partitions:

 

disk0s1 (EFI) not 100% sure but I select this when I use "EFI MOUNTTER"

disk0s2 (RAID SLICE)

disk0s3 (chamaleon)

 

When I start the computer the system select the disk0s3 partition to start but I would like to boot from the (EFI disk0s1)

 

How can I change this? I think is with FDISK but not sure about the comands that I need to use.

 

Many thanks

Try this in Terminal, assuming disk0s1 is what you want as active:

sudo ./Volumes/YOURBOOTDRIVE/usr/sbin/fdisk -e /dev/disk0
fdisk: 1> p		 (Type "p"  - Print loaded MBR partition table)
fdisk: 1> f 1	   (Type "f 1" notice space after "f"  - Flag given partition as bootable)
fdisk:*1> w		(Type "w" - Write loaded MBR to disk)

Device could not be accessed exclusively.
A reboot will be needed for changes to take effect. OK? [n] y	   (Type "y")

Writing MBR at offset 0.
fdisk: 1> q		 (Type "q" to quit)

 

 

Erased my previous text...

 

It looked like it was going smooth during the install, and I finally figured out the proper paths to the installers so I could install without a reboot. BUT

 

I've now tried installing bot 10.5.4 retail and 10.5.6 torrent and neither comes up as a bootable alternative after the installer says it was a succesfull install. I'm sure I'm missing something here, but cant seem to find it.

 

I have tried using wolfenukies 3.1 scripts, the log reports no errors and seems to mount and unmount the efi partition as it should, but still after a reboot Istill cant choose that disk as a bootable osx system drive...

 

I have also no tried Chamelion as well, llokied like a nice enough installer but then what? It didnt imrprove much since...

 

Now I cant get the {censored} to boot... Now it hangs after showing five rows o numbers and then a row with a "J" and a flashing cursor after it.

 

I Really feel im just fumbling around in the dark...

The BIOS is unable to find any bootable files. It may be looking at the wrong drive or partition.

Make sure the BIOS is not set up to look at any unbootable drives. Give your bootable drive/partitions priority.

 

Hi all,

 

To MAJ concerning eSATA ports

Hotplugable eSATA Drives

 

On my current workstation (P5K, Kalyway 10.5.6) my eSATA ports are also not hotplugable. It's no big deal considering these are my working video disks : I only decide to plug them when I'm working on the projects they contain. As you say, it's depending on every one uses and what is a pain in the a** for some, is not a problem for others. A guy called "trauma23", french member (like me ) of this forum, explained me once how to make them hotplugable, and sent me kexts and everything, but I didn't understood a word he was writing and decided to forget it. But I know he has been successful with fixing this problem. Maybe you can PM him or make a search on the forum...I'm sure he can manage with english conversation.

 

Unmounting eSATA Drives

 

I didn't experienced any problems when trying to unmount them. I just tried right now, to be sure, and no "beachball hell" appears. I'm using the Jmicron controller and the standar onboard ports.

 

When you say you don't mess with Jmicron, does that mean that you plug your eSATA devices on the motherboard SATA ports with an adapter ?

 

I'm sorry I can only give you my experience but no solutions. Same thing altought, Trauma23 is very knowledgeable on this matters.

Thanks for that information. Appreciated.

 

Firewire issues

 

I guess I have to buy first and try then. I let you know.

 

Thank you for anwsering so fast. I'll maybe out of network for the the next two weeks, going on a shooting, but I'll be up then and ready to take action...

Cool.

 

New question about graphic cards (to anyone)[/b]

 

Just wondering :

 

-If ATI 4870 is the better option, regarding it's an Apple reference ?

-If ATI 4890 is or will be supported ?

-If newer Nvidia like the GF 260 GTX are supported ?

 

-What is the best way to have a graphic card (any) working on an EFI boot method ?

-With the DD retail DVD method ?

I don't have a EFI boot script, so wolfienuke's script is the only game in town for the time being. That's a project I hope to complete in a couple weeks.

 

Understanding those installs include Natit.kext, do I have to replace it with Nvinject to have Nvidia cards working ?

 

When several injectors are included in the DD method (like the ones in the "_repository" and "_to install" folders) wich one is finally used ? Does that mean I have to move the one I'm want to use in the right folder ?

Yes.

The two NVIDIA injectors (NVinject and NVkush) shouldn't be used together - just one or the other. They contain two different implementations of gathering video card data from NVIDIA cards.

 

I know, but then, why getting a mac ?

If the hackintosh were a real mac, then you'd be right!

 

kind regards,

MAJ

 

Well I think I've got a success story!

 

Just trying things, I reformatted the EFI partition using Wolfienuke's script, but this time I added all the new kext that were just uploaded. At first it didn't work, but after enabling AHCI it booted up for the first time.

 

I haven't had much of a chance to mess with it. Sleep doesn't work at all. Sound seems to be working. Ram (6GB triple channel) and graphics card (ATI 4870) are recognized. Although I noticed in system profiler that the video ram says 700-something MB instead of 1GB. Any idea why?

 

Also, the biggest issue right now seems to be mass storage devices. I have it enabled in bios. The system profiler even recognizes my external and my flash drive correctly, but they don't mount anywhere on the computer. Any idea why?

 

I really appreciate the help so far. Hopefully I can get everything running smooth, but this was a big step for me.

Welcome, Sumrall! All your efforts have paid off.

 

Do you have CI/QE for your GPU? I wouldn't think you have the new drivers installed, yet.

The USB hot-plugging is usually a symptom of a mismatched kernel and System.kext. I just realized that I included the System.kext for the Voodoo-based 9.6 kernel, but didn't include that kernel. You probably are using the older 9.5 kernel from wolfienuke's script.

I'll throw that 9.6 kernel in the package, so that this issue is resolved.

 

EDIT: Download package for EFI boot has been updated on front page to include 9.6 kernel.

 

MAJ

[bastardizer]

DigitalDreamer

 

I do hope that you might actually be what the forum implies you to be...

A Genious In A Bar!

 

I'll try to recap my problems and please disregard everything prior to this as I have been frustrated and probably made some wrong turns here and there actually causing some of the issues...

 

Installed Kalyway 10.5.2 on drive A

Basic functionality

Installed Retail 10.5.4 on drive B (structure IS same as on normal discs, disregard that)

Installed Chamelion RC1 on drive B

-Reboot-

Bios post page passes quickly (Still need to clear cmos to be able to get to it)

Chamelion GUI appears

 

IF I select Kalyway on drive A, then it starts Darwin and boots to disk A

 

IF I select 10.5.4 on drive B, (with-v to be able to see what goes on) then it reboots after the first line that says "Starting Darwin x86" (just after the lines mentioning loading hfs+ files and "No DSDT replacment found...". (thank god for a webcam, it flashes by pretty quickly).

 

Any ideas where to go from here?

Bios settings are the same as the ones in your first post in this thread.

 

 

OTOH. Perhaps I just should follow your instructions in post 1 or 2...

I just reead it like the chamelion RC1 could replace it all. That might have been wrong on my part... Probobly...

[arthur655]

First I would like to thank Digital dreamer and wolfienuke for their great works and I managed to install a clean 10.5.6 osx based on digital dreamer scripts. It works fine for some months now.

 

But I was not able to install on raid 0 on the ich10 controler. So I used the gigabyte JMB322 instead but it is not that stable.

 

Can you help me to install it on a ich10 controler. Everytime i try, disk utility is not able to create the apple raid software. I have looked around for an answer but haven't found yet.

 

Ps - "I used to be a windows power user but now I have definitevy switched..."

 

Hi all,

 

First I would like to thank Digital dreamer and wolfienuke for their great works and I managed to install a clean 10.5.6 osx based on digital dreamer scripts. It works fine for some months now.

 

But I was not able to install on raid 0 on the ich10 controler. So I used the gigabyte JMB322 instead but it is not that stable.

 

Has anyone succeed ? Can you help me to install it on a ich10 controller ?

 

Everytime i try, disk utility is not able to create the apple raid software. I have looked around for an answer but haven't found any yet.

 

Ps - "I used to be a windows power user but now I have definitevy switched..."

 

Hi all,

 

 

First I would like to thank Digital dreamer and wolfienuke for their great works and I managed to install a clean 10.5.6 osx based on digital dreamer scripts. It works fine for some months now.

 

But I was not able to install on raid 0 on the ich10 controler. So I used the gigabyte JMB322 instead but it is not that stable.

 

Can you help me to install it on a ich10 controler. Everytime i try, disk utility is not able to create the apple raid software. I have looked around for an answer but haven't found yet.

 

Ps - "I used to be a windows power user but now I have definitevy switched..."

[bastardizer]

Remember to READ folks!!!

 

Since appearantly I have just learnt how to do that, I now have a (on the way to) working version of vanilla 10.5.6.

 

While I could only get one of the ethernet ports to work (not an issue really but frustrating as they both worked on kalyway) I'm now downloading the upgrades from apple. I still have to get grafics to work propperly.

As soon as my upgrades are done I'll read up on the 8500GT, I did try osxtools bumping a string in there, but nothing changed... Anyone?

[darkenedreality]

Hey Everyone,

 

First off i would like to thank MAJ and Wolfienuke for their tremendous work on getting OSX on UD5 and x58 in general! ! ! Not to mention responding to every problem that came up in this topic. Simply amazing work, I tip my hat off to both of you!

 

 

I used Wolfie's script and it worked flawlessly....... the first time. Everything worked up to the point of installing OpenBSD on my second HDD. In my second install of OSX, everything is working except the onboard Ethernet. The system log shows:

 

localhost configd[45]: InterfaceNamer: no network interfaces, could not update platform UUID

 

I have tried the IONetworkingFamily and RealrekR1000 kexts and varified the EFI partition but still nothing. I've checked my BIOS and reformatted countless number of times but cannot duplicate the configuration of my first install (even though it was just the default kexts that came with Wolfie's script).

 

Any help would be greatly appreciated,

 

Dark D

[darkenedreality]

NVM, It would seem that this is a issue with the UD5 boards. After booting off a live-usb key, I found that it could not find the LAN adapter as well yet my switch could find the layer 2 address. Unhooked the power for 5 seconds and booted and everything is fine now.

 

Thanks again to MAJ and Wolfie for a great guide and EFI scripts!

 

Dark D

[digital_dreamer]

NVM, It would seem that this is a issue with the UD5 boards. After booting off a live-usb key, I found that it could not find the LAN adapter as well yet my switch could find the layer 2 address. Unhooked the power for 5 seconds and booted and everything is fine now.

 

Thanks again to MAJ and Wolfie for a great guide and EFI scripts!

 

Dark D

Yeah, the UD5 on-board LAN can be flaky at times. You're not alone. Fortunately, Once you stop messing with the system, it appears more stable.

 

MAJ

[andycorleone]

Digital Dreamer Thanks for you help in this matter:

 

I'm almost sure I'm i nthe right drive in this case disk1

 

WHEN I TYPE : fdisk: 1> p

I GET:

 

Disk: /dev/disk1 geometry: 60801/255/63 [976773168 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 - 976773167] <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

 

WHEN I TYPE: f 1

I GET: Partition 1 marked active.

 

after that is all the same as you instruction but it does seen to work, still booting in the s3 partitiom any idea why?

 

Thanks

 

 

Try this in Terminal, assuming disk0s1 is what you want as active:

sudo ./Volumes/YOURBOOTDRIVE/usr/sbin/fdisk -e /dev/disk0
fdisk: 1> p		 (Type "p"  - Print loaded MBR partition table)
fdisk: 1> f 1	   (Type "f 1" notice space after "f"  - Flag given partition as bootable)
fdisk:*1> w		(Type "w" - Write loaded MBR to disk)

Device could not be accessed exclusively.
A reboot will be needed for changes to take effect. OK? [n] y	   (Type "y")

Writing MBR at offset 0.
fdisk: 1> q		 (Type "q" to quit)

 

MAJ

[tsunoo]

after that is all the same as you instruction but it does seen to work, still booting in the s3 partitiom any idea why?

 

Thanks

 

because you're probably analyse the wrong hd!?!?

[bastardizer]

YAY Removed old post!!!

 

It seems to be working!!!

 

I had to do it the manual way, copying the com.apple.boot.plist file to another volume so I could edit it and then deleted the original and then replaced it!

 

But why did I need to, none of the mentioned programs work on my efi volumes...

 

Wohoo, Sleeps works as well! I just cant get it to see my Corsair USB stick. Not a major issue though, will est with external usb and fw stuff to make sure they work.

Almost time to start installing programs!!! :-)

[tstm]

Wohoo, Sleeps works as well! I just cant get it to see my Corsair USB stick. Not a major issue though, will est with external usb and fw stuff to make sure they work.

Almost time to start installing programs!!! :-)

You have working S3 sleep? Give me the details! Which BIOS version? You're using UD5?

Are you booting via EFI or boot-1-2-3? Which bootloader do you use? Which kernel are you running?

 

It would really be nice to get sleep to work.

[bastardizer]

I spoke to soon, the first few times it worked as I was sitting there, both the very first where it just shut down the screen, and the second one where it went down in "full sleep mode". Since then I have rebooted and now it hangs after wake...

 

Is the other (non S3 mode cant remember what its called) working better?

[tstm]

Is the other (non S3 mode cant remember what its called) working better?

I don't know.

 

From wikipedia:

S1: All processor caches are flushed, and the CPU(s) stop executing instructions. Power to the CPU(s) and RAM is maintained; devices that do not indicate they must remain on may be powered down.

S2: The CPU is powered off.

S3: Commonly referred to as Standby or Sleep. RAM is still powered.

S4: Hibernation. All content of main memory is saved to non-volatile memory such as a hard drive, and is powered down.

 

UD5 supports S1 and S3 (and S4, too, but that's not a BIOS feature), you can switch between the modes in the BIOS. S1 is useless though, it still uses almost as much power as it does when the computer is on.

 

So, even if S1 worked, it doesen't matter since it's not useful for anything.

[beboy]

My IDE DVD Drive is not recognized in OS X with this mobo, anyone knows how i can fix it ?

[digital_dreamer]

Digital Dreamer Thanks for you help in this matter:

 

after that is all the same as you instruction but it does seen to work, still booting in the s3 partitiom any idea why?

 

Thanks

Are you saying the first partition that is selected when the bootloader comes up is the 0s3 partition?

Chameleon 2 might be a little confused here.

Try adding this in your boot.plist and report back:

<key>Default Partition</key>
<string>hd(0,1)</string>

 

Make sure the hd ID is correct. I don't like this setup, because if you get it wrong or add another drive, the wrong partition will be selected. Make sure you don't have Silent Boot enabled, so that you can always select the proper partition in the bootloader, particularly when the default selection is invalid or non-bootable.

 

regards,

MAJ

 

I don't know.

 

From wikipedia:

S1: All processor caches are flushed, and the CPU(s) stop executing instructions. Power to the CPU(s) and RAM is maintained; devices that do not indicate they must remain on may be powered down.

S2: The CPU is powered off.

S3: Commonly referred to as Standby or Sleep. RAM is still powered.

S4: Hibernation. All content of main memory is saved to non-volatile memory such as a hard drive, and is powered down.

 

UD5 supports S1 and S3 (and S4, too, but that's not a BIOS feature), you can switch between the modes in the BIOS. S1 is useless though, it still uses almost as much power as it does when the computer is on.

 

So, even if S1 worked, it doesen't matter since it's not useful for anything.

I just updated to the F7a BIOS yesterday and still find S3 (Suspend to RAM) sleep unpredictable. I only tried it a few times and twice I was able to wake without a KP. I should note that I was testing out some sleep enabler kexts like OpenHaltRestart.kext, so I really don't know how much of this was due to the BIOS update or the kexts under test, or a combination of the two. My conclusion at the end of the tests was that it wasn't working and was to be abandoned until fixed.

 

The general consensus is that the bootloader is at fault. Unless my memory is failing me, I don't recall having sleep issues until I upgraded the bootloader from PC-EFI v8 to v9, and now to Chameleon v2 RC. Are there any using the old v8 bootloader on the boot-132 setup having sleep issues? I wouldn't think so. Please note what BIOS you are running, as well.

 

regards,

MAJ

[Sumrall]

Do you have CI/QE for your GPU? I wouldn't think you have the new drivers installed, yet.

The USB hot-plugging is usually a symptom of a mismatched kernel and System.kext. I just realized that I included the System.kext for the Voodoo-based 9.6 kernel, but didn't include that kernel. You probably are using the older 9.5 kernel from wolfienuke's script.

I'll throw that 9.6 kernel in the package, so that this issue is resolved.

 

EDIT: Download package for EFI boot has been updated on front page to include 9.6 kernel.

 

MAJ

 

I got my ATI 4870 fully working thanks to this nice little thread!

 

However, I'm having a problem with hot-plugging. Currently, if I boot up with the device plugged in, then it works and I can even sometimes unplug and reconnect it to the same usb port. Mostly, though I can't just plug in a device after boot up.

 

You mentioned a mismatched kernal and System.kext, but when I switched to the mach.kernal you uploaded I couldn't boot up I tried a few combinations, but thing only thing that lets me boot up successfully are the new kext and the kernal that wolfienuke uploaded. Maybe I did it wrong, am I not supposed to replace the kernal that's in the script with the new one? Let me know what you think.

[mac kid from jersey]

Hey guys. I'd like to thank digital dreamer and wolfnuke for an excellent guide. I was able to get my system set up without a hitch. One question though:

 

I've been having some apps crash on EXC_BAD_ACCESS. Is this a problem with the voodoo kernel?

[airwalk776]

Hey guys. I'd like to thank digital dreamer and wolfnuke for an excellent guide. I was able to get my system set up without a hitch. One question though:

 

I've been having some apps crash on EXC_BAD_ACCESS. Is this a problem with the voodoo kernel?

 

 

Which motherboard you running on?

[Sumrall]

I figured out why I couldn't load the 9.6 kernel. Some people had issues with the wrong seatbelt kext. All I had to do was change the name of the kernel reference in the boot.plist from mach_kernal.voodoo to just mach_kernal. Maybe this was obvious to others but I'm still learning. So for fellow noobs, if you're trying to update wolfienuke's fantastic script with the latest kext and kernel, don't forget to edit the boot.plist.

 

Now...if only I could get my wireless adapter working I'd be in great shape!

[m_mckinlay]

Hi there,

Will this guide work just as well with the other Gigabyte x58 motherboards?

[mac kid from jersey]

My IDE DVD Drive is not recognized in OS X with this mobo, anyone knows how i can fix it ?

 

I had the same problem using the wolfnuke's EFI method (luckily I have a SATA drive as well). Try using digital dreamers install scripts. That worked for me. And make an ISO of the retail disk. It's soooo worth it.

 

Honestly, your are probably better off using a SATA Optical drive and just using the Intel controller (the blue ports). JMicron causes so many KPs for me.

[mac kid from jersey]

Which motherboard you running on?

 

I'm using the Gigabyte GA-EX58-UD5.

 

Here is my config:

 

1 x Intel Core i7 920 Nehalem 2.66GHz

2 x mushkin 6GB (3 x 2GB) 240-Pin DDR3 SDRAM DDR3 1333 (PC3 10666) for a total of 12 GB of ram (all mem slots filled)

1 x Gigabyte GA-EX58-UD5

1 x COOLER MASTER V8 RR-UV8-XBU1-GP 120mm Rifle CPU Cooler - Retail

1 x EVGA GeForce 9800 GT 512MB PCI Express 2.0 x16 in PCIe slot 1

 

 

3 x Western Digital Caviar Green WD10EADS 1TB Hard Drive in ICH10R slots 0, 2 and 4 (the back most slots ... the ones closets to the chasis

1 x Western Digital Raptop SATA v1 1.5 GB/s in the ICH10R slot 1

1 x Sony Optiarc Black 2X BD-ROM SATA Model BR-5100S - OEM in ICH10R slot 3

 

I installed using the 10.5.2 kalyway distro onto the digital raptor. boots fine with modbinkernel -f legacy -x kernel flags.

 

I tried to use wolfnukes script but it kept hanging at boot during the mdnsresponder portion.

 

I reformatted the drive and then did digital dreamers installation script using a retail 10.5.4 disk, did the combo update and then did the post patch. I had to do the post patch after the security updates as well. I changed the Ram speed in the boot string as well as my memory is 1333 and not 1600 ... i'm not sure if that matters.

 

I've done the bios updates as well. I first had version f4 and then upgraded to f6b. No over clocking at this time.

 

I'm running the voodoo 9.6.0 kernel. EFI String for graphics card via OSX Tool.

 

http://browse.geekbench.ca/geekbench2/view/122157

 

Apart from iphoto and apreture crashing on import, I must say that it's quite stable.

 

EDIT: I've run memtest86 from the fedora cd for a few hours with 0 errors.

[tstm]

Apart from iphoto and apreture crashing on import, I must say that it's quite stable.

Oh {censored}. I tried Aperture too, and it crashes on startup. =(

 

Exception Type: EXC_BAD_ACCESS (SIGBUS)

Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000

Crashed Thread: 30

 

I'm assuming this happens to everyone using voodoo/X58/i7 combo? Or could it be only some configuration/kext issue?

[tsunoo]

Oh {censored}. I tried Aperture too, and it crashes on startup. =(

 

Exception Type: EXC_BAD_ACCESS (SIGBUS)

Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000

Crashed Thread: 30

 

I'm assuming this happens to everyone using voodoo/X58/i7 combo? Or could it be only some configuration/kext issue?

You're assuming wrong

We don't have any problem with our Ram. Perharps do you have too much

I've already imported more than 20000 photos without problems (using iPhoto).

The only problem I've got was with some RAW files.

 

My advices:

1)

There is known probleme with 32 bits OS... which can address only 4 gig.

Remove some RAMs (<= 4 gig) and try again.

2) remove the raw files from your photo directory