Upcoming Intel X58 Mobos & Core i7 CPUs

[digital_dreamer]

Digital_Dreamer,

 

I'm interested in the AHCI knocking out your LAN... My lan has gone kapput also, but the only modification I have done was to update the BIOS!!!!!!

 

Nothing seems to bring the lan back up unfortunately, i'm going to have to re-install from scratch and try and troubleshoot from there - Machine was performing very well prior to this...

 

Well, what it took for me was clearing the CMOS - several times. Shutdown, turn off the PSU, and press that CMOS button on the back. In my case, I had to remove the offending kext, before there was any life on the LAN. This is why it took several attempts. It's helpful to have another working install (like Kalyway, in my case) to verify that the LAN is okay. When the LAN wasn't working in my other install, I knew it was a hardware issue. Once that was fixed, then I could move on to the project install (EFI boot).

 

Reinstalling the entire OS would be a bit of overkill. If you have another working install, verify your troubleshooting results with that.

 

Best of wishes,

MAJ

 

below is the content of a kextstat from my machine. im using the gigabyte board, and have not been able to get ethernet working. this time for the hell of it i used the script, thinking it must be something i was doing wrong. as you can see from the kextstat ionetworking family is being loaded from my actual hd not from the efi partition. i did use the script to bump up the version value even though i still think its just the probe score that should be upped as changing the version can upset dependencies.

 

i also kextloaded the driver from the actual hd and it loads but it gave some warnings that i have never seen before, and i have been in this situation for many days now, kextload -t has become second nature to me

 

Last login: Mon Dec 29 09:44:52 on ttys000
joe-booths-somemodel:~ Joe$ sudo kextstat
Password:
Index Refs Address    Size       Wired      Name (Version) <Linked Against>
   1    1 0x0        0x0        0x0        com.apple.kernel (9.5.0)
   2   34 0x0        0x0        0x0        com.apple.kpi.bsd (9.5.0)
   3    3 0x0        0x0        0x0        com.apple.kpi.dsep (9.5.0)
   4   48 0x0        0x0        0x0        com.apple.kpi.iokit (9.5.0)
   5   53 0x0        0x0        0x0        com.apple.kpi.libkern (9.5.0)
   6   47 0x0        0x0        0x0        com.apple.kpi.mach (9.5.0)
   7   27 0x0        0x0        0x0        com.apple.kpi.unsupported (9.5.0)
   8    1 0x0        0x0        0x0        com.apple.iokit.IONVRAMFamily (9.5.0)
   9    1 0x0        0x0        0x0        com.apple.driver.AppleNMI (9.5.0)
  10    1 0x0        0x0        0x0        com.apple.iokit.IOSystemManagementFamily (9.5.0)
  11    1 0x0        0x0        0x0        com.apple.iokit.ApplePlatformFamily (9.5.0)
  12   21 0x0        0x0        0x0        com.apple.kernel.6.0 (7.9.9)
  13    1 0x0        0x0        0x0        com.apple.kernel.bsd (7.9.9)
  14    1 0x0        0x0        0x0        com.apple.kernel.iokit (7.9.9)
  15    1 0x0        0x0        0x0        com.apple.kernel.libkern (7.9.9)
  16    1 0x0        0x0        0x0        com.apple.kernel.mach (7.9.9)
  17   12 0x76fc4000 0x10000    0xf000     com.apple.iokit.IOPCIFamily (2.4) <7 6 5 4>
  18    6 0x76fda000 0x4000     0x3000     com.apple.iokit.IOACPIFamily (1.2.0) <12>
  19    2 0x77029000 0x3d000    0x3c000    com.apple.driver.AppleACPIPlatform (1.2.1) <18 17 12 7 5 4>
  20    0 0x770e0000 0x3000     0x2000     com.apple.driver.decrypt (2.0.3) <7 5 4>
  21    0 0x770f9000 0x5000     0x4000     com.apple.BootCache (28) <7 6 5 4 2>
  22    4 0x771b9000 0x38000    0x37000    com.apple.iokit.IOHIDFamily (1.5) <7 6 5 4 2>
  23    0 0x7721f000 0x3000     0x2000     com.apple.security.TMSafetyNet (2) <7 6 5 3 2>
  24    0 0x77239000 0x8000     0x7000     com.apple.nke.applicationfirewall (1.0.70) <7 6 5 4 2>
  25    0 0x77279000 0x18000    0x17000    com.apple.security.seatbelt (107.1) <7 6 5 3 2>
  26    0 0x773fb000 0x3000     0x2000     com.apple.driver.AppleAPIC (1.2.0) <12>
  27    0 0x7ff76000 0x4000     0x3000     com.apple.driver.AppleSMBIOS (1.0.12) <12>
  28    0 0x8011a000 0x4000     0x3000     com.apple.driver.AppleACPIButtons (1.2.1) <22 19 18 7 6 5 4 2>

  29    0 0x801b7000 0x3000     0x2000     com.apple.driver.AppleACPIPCI (1.2.1) <19 18 17 12>
  30    0 0x8023a000 0x5000     0x4000     com.apple.driver.AppleRTC (1.0.5) <18 6 5 4 2>
  31    1 0x80247000 0x3000     0x2000     com.apple.driver.AppleEFIRuntime (1.1.0) <7 5 4>
  32   11 0x802f8000 0x28000    0x27000    com.apple.iokit.IOUSBFamily (3.0.3) <7 6 5 4>
  33    0 0x80347000 0xe000     0xd000     com.apple.driver.AppleUSBUHCI (3.0.3) <32 17 7 6 5 4>
  34    3 0x8039c000 0x6000     0x5000     com.apple.iokit.IOAHCIFamily (1.0.4) <6 5 4 2>
  35    0 0x80436000 0xa000     0x9000     com.apple.driver.AppleAHCIPort (1.5.1) <34 17 6 5 4 2>
  36    0 0x80515000 0x12000    0x11000    com.apple.driver.AppleUSBEHCI (3.0.3) <32 17 7 6 5 4>
  37    2 0x80680000 0x3f000    0x3e000    com.apple.iokit.IOFireWireFamily (3.3.8) <6 5 4 2>
  38    0 0x806f2000 0x1f000    0x1e000    com.apple.driver.AppleFWOHCI (3.3.5) <37 17 7 6 5 4 2>
  39    0 0x8072f000 0x6000     0x5000     com.apple.driver.AppleEFINVRAM (1.1.0) <31 7 6 5 4>
  40    0 0x8078d000 0x2000     0x1000     com.apple.iokit.IOUSBUserClient (3.0.3) <32 6 5 4>
  41    0 0x80875000 0xb000     0xa000     com.apple.driver.AppleUSBHub (3.0.3) <32 6 5 4>
  42   11 0x8091e000 0x18000    0x17000    com.apple.iokit.IOStorageFamily (1.5.2) <7 6 5 4 2>
  43    0 0x80974000 0x3000     0x2000     com.apple.driver.AppleFileSystemDriver (1.1.0) <42 5 4>
  44    0 0x80a10000 0x4000     0x3000     com.apple.driver.AppleUSBComposite (3.0.0) <32 5 4>
  45    6 0x80b1b000 0x18000    0x17000    com.apple.iokit.IOSCSIArchitectureModelFamily (2.0.0) <6 5 4 2>
  46    0 0x80b44000 0xa000     0x9000     com.apple.iokit.IOUSBMassStorageClass (2.0.0) <45 42 32 12>
  47    2 0x80c27000 0x16000    0x15000    com.apple.iokit.IOSCSIBlockCommandsDevice (2.0.0) <45 42 6 5 4 2>
  48    0 0x80c44000 0x3000     0x2000     com.apple.driver.iTunesPhoneDriver (1.0) <47 45 12>
  49    0 0x80cb2000 0x6000     0x5000     com.apple.iokit.SCSITaskUserClient (2.0.0) <45 42 6 5 4 2>
  50    0 0x80d31000 0x11000    0x10000    com.apple.iokit.IOAHCIBlockStorage (1.1.0) <42 34 6 5 4 2>
  51    0 0x80dae000 0x2000     0x1000     com.apple.driver.AppleUSBMergeNub (3.0.3) <32 5 4>
  52    0 0x80e74000 0x5000     0x4000     com.apple.driver.XsanFilter (2.7.91) <42 12>
  53    1 0x810b0000 0x37000    0x36000    com.apple.iokit.IOBluetoothFamily (2.0f20) <12 6 5 4 2>
  54    0 0x810f2000 0x7000     0x6000     com.apple.driver.AppleUSBBluetoothHCIController (2.0f20) <53 32 12>
  55    0 0x81156000 0x6000     0x5000     com.apple.iokit.IOAHCISerialATAPI (1.0.1) <45 34 6 5 4 2>
  56    2 0x81237000 0x5000     0x4000     com.apple.iokit.IOUSBHIDDriver (3.0.3) <32 22 6 5 4>
  57    0 0x81242000 0x2000     0x1000     com.apple.driver.AppleHIDKeyboard (1.0.5f1) <56 22 12>
  58    3 0x812ee000 0x8000     0x7000     com.apple.iokit.IOCDStorageFamily (1.5) <42 6 5 4 2>
  59    2 0x8132d000 0x6000     0x5000     com.apple.iokit.IODVDStorageFamily (1.5) <58 42 6 5 4 2>
  60    1 0x81363000 0x5000     0x4000     com.apple.iokit.IOBDStorageFamily (1.5) <59 58 42 6 5 4 2>
  61    0 0x8138f000 0x16000    0x15000    com.apple.iokit.IOSCSIMultimediaCommandsDevice (2.0.0) <60 59 58 47 45 42 6 5 4 2>
  62    1 0x81482000 0x3000     0x2000     com.apple.driver.AppleHIDMouse (1.2.0b3) <22 12>
  63    0 0x8148d000 0x3000     0x2000     com.apple.driver.AppleUSBHIDMouse (1.2.0b3) <62 56 32 12>
  64    1 0x76ef5000 0x9000     0x8000     com.apple.driver.AppleSMC (2.0.0d5) <18 7 6 5 4>
  65    1 0x76efe000 0xe000     0xd000     com.apple.driver.IOPlatformPluginFamily (3.0.0d11) <12>
  66    0 0x76f0c000 0xa000     0x9000     com.apple.driver.ACPI_SMC_PlatformPlugin (3.0.0d11) <65 64 18 17 12 7 6 5 4>
  67    1 0x76f16000 0x3000     0x2000     com.apple.kext.OSvKernDSPLib (1.1) <6 5>
  68    1 0x76f19000 0x17000    0x16000    com.apple.iokit.IOAudioFamily (1.6.4b7) <67 6 5 4 2>
  69    0 0x76f30000 0x4000     0x3000     com.apple.driver.AudioIPCDriver (1.0.4) <68 6 5 4 2>
  70    1 0x76f34000 0x16000    0x15000    com.apple.iokit.IONetworkingFamily (1.6.0) <7 6 5 4 2>
  71    0 0x76f4a000 0x9000     0x8000     com.apple.iokit.IOFireWireIP (1.7.0) <70 37 6 5 4 2>
  72    3 0x76f53000 0x1c000    0x1b000    com.apple.iokit.IOGraphicsFamily (1.5) <17 7 6 5 4>
  73    2 0x76f6f000 0xe000     0xd000     com.apple.iokit.IONDRVSupport (1.5) <72 17 7 6 5 4>
  74    2 0x8b996000 0x22d000   0x22c000   com.apple.NVDAResman (5.1.6) <73 72 17 12 6 5 4 2>
  75    0 0x8bbc3000 0x1b8000   0x1b7000   com.apple.nvidia.nv40hal (5.1.6) <74 17 12>
  76    0 0x80f61000 0x82000    0x81000    com.apple.GeForce (5.1.6) <74 73 72 17 12 6 5 4 2>
  77    0 0x770e3000 0x10000    0xf000     com.apple.driver.DiskImages (191.1) <42 7 6 5 4 2>
  78    0 0x80255000 0xb000     0xa000     com.apple.filesystems.autofs (2.0.0d1) <7 6 5 4 2>
  79    2 0x8028e000 0x9000     0x8000     com.apple.iokit.IOSerialFamily (9.1) <7 6 5 4 2>
  80    0 0x80297000 0x9000     0x8000     com.apple.iokit.IOBluetoothSerialManager (2.0f20) <79 12>
  81    0 0x802af000 0x4000     0x3000     com.apple.driver.InternalModemSupport (2.4.0) <79 32 12>
  82    0 0x80359000 0xc000     0xb000     com.apple.filesystems.msdosfs (1.5) <7 6 5 2>
  83    0 0x80527000 0x1b000    0x1a000    com.apple.filesystems.ntfs (2.0) <7 6 5 2>
joe-booths-somemodel:~ Joe$ sudo kextload -t /System/Library/Extensions/RealtekR1000.kext 
kextload: extension /System/Library/Extensions/RealtekR1000.kext appears to be loadable
/System/Library/Extensions/System.kext/PlugIns/IOKit.kext/IOKit: Undefined in symbol set: __Z19IODTMapOneInterruptP15IORegistryEntryPmPP6OSDataPPK8OSSymbol
/System/Library/Extensions/System.kext/PlugIns/IOKit.kext/IOKit: Undefined in symbol set: __Z23IODTFindInterruptParentP15IORegistryEntry
kextload: /System/Library/Extensions/RealtekR1000.kext loaded successfully
joe-booths-somemodel:~ Joe$ 

 

EDIT: just deleted the ionetworking family from my hd (getting desparate now) and it still refuses to load the version on my efi partition.....

 

EDIT2: installing the kext from my efi partition onto my installation hd works but the realtek driver is not loaded at boot, and manually loading still does not recognise my ethernet hardware

 

ѕӎѳѳ, thanks for all that info. Insightful.

The error on the driver kextload is interesting. But, I don't have any answers at this time.

Are you saying that in all these tests that the LAN has never worked? If so, have you cleared the CMOS? I find the LAN on that Gigabyte board to be rather flakey and easily upset.

 

regards,

MAJ

 

Hi Maj,

 

First off, sleep problem solved! Thank you. I tried both kexts you provided and it miraculous solved the Sleep > Wake > Shutdown > KP problem I had previously and of course TM works with both kexts. Now on to the difference between the two:

 

1. First one with the old Lan driver. The network panel doesn't report a speed, it defaults to half duplex and a MTU of 1500. This one doesn't have any problem reconnecting to the Lan after sleep. I tried a speed test with my laptop and it peaked at 26MB/s via ftp. Think this is limited by the HD of the laptop though. Again I can try modifying the settings with manual but they won't stick. For some reasons, I tried both leaving the settings untouched and changing them to full duplex and mtu 8000 etc but the speed remains the same at 26MB/s. Again given the test is limited by the HD, not sure if this tells us anything.

 

2. Second one with new Lan driver. Network panel reports 1000BaseT, full duplex and 1500MTU. Tried the same test. Again peaked at 26MB/s. Tried changing MTU to 8000. No luck. Settings will not stick. This one, as you suggested earlier, will not reconnect after sleep.

 

Given the above, i.e. no speed difference (at least for practical purposes), and that the sleep problem is now fixed, I am better off stick with the 1st kext above.

 

Thank you once again.

 

Now on to my next project: dual booting with Vista x64. Any one has experience? It seems like the tutorials lurking around on the forum is tailored for dual booting on 1 single HD. I would like to put Vista on a separate disk. Now of course, I can just install it and change the booting priority through F12 whenever I want to boot Vista but give how fxxxing slow the Gigabyte BIOS is, I really want to avoid doing that if possible.

 

Michael

 

Thanks for doing all that work. We are better informed now.

Actually, both of those drivers are basically the same open source drivers, but the first one had been slightly updated by Psystar to improve link detection. It would seem obvious that would affect sleep ability. Those of us with the Realtek LAN driver are stuck with this open source derivative. I do have in my files another Realtek driver someone had worked on if you want to try it out. Let me know.

The 26MB/s transfer rate sounds about right for a 5400 RPM laptop drive. I'd do some tests on my end but I only have a 100BASE-T switch/router. I could just plug the Macs in directly with autosensing and reconfigure the network (It's currently on DHCP).

 

And, no, I don't have any experience with dual booting into Windows. I'm sure I'm going to, as I have a VISTA 64 coming my way, as well.

 

Thanks, again, for these tests.

 

regards,

MAJ

[ѕӎѳѳ₮ңӌ]

ѕӎѳѳ, thanks for all that info. Insightful.

The error on the driver kextload is interesting. But, I don't have any answers at this time.

Are you saying that in all these tests that the LAN has never worked? If so, have you cleared the CMOS? I find the LAN on that Gigabyte board to be rather flakey and easily upset.

 

regards,

MAJ

 

it looks as though my lan hardware has died. i cannot perform the cable test from the bios and a fresh install of vista 64 does not pick them up either..... f*cking stupid thing

[mauriciomoura]

Hi there, first post here... reading for a long time though...

Got myself a UD5, i7 920, but as I have a ATI HD4850 I'm waiting for drivers to try osx86.

 

it looks as though my lan hardware has died. i cannot perform the cable test from the bios and a fresh install of vista 64 does not pick them up either..... f*cking stupid thing

ѕӎѳѳ, did you update you firmware recently? I did update to F4 and my lan seemed dead. Reverted back to F4F and it worked again. Maybe it's worth a shot.

[digital_dreamer]

<SNIP> i cannot perform the cable test from the bios<SNIP>

 

Well, that's revealing. Obviously hardware or even a corrupted BIOS. When I cleared the CMOS, I got in a habit of loading my saved CMOS settings. When that didn't work, I decided NOT to load any settings and reset everything from scratch. Then, everything was well. Worth a shot if you've been loading your saved CMOS settings after each clear.

 

regards,

MAJ

 

EDIT: Michael,

This is the Sourceforge.net project page for the LAN driver you are using now. It's based on the Linux driver, but modified for Mac OS X, currently at version 1.0.4 (The previous one that had sleep problems is actually a more recent version from here.)

This thread is by the guy actually working on the driver (back in 2006).

This is what he had to say:

Now I\'m planing to add such features:

- Manual MTU control (now it fixed at 1500).

- Jumbo frame support.

- Wake on magic packet.

So, he had planned to address three of your complaints, but progress must have stalled. Such is the case with open source if there is a lack of interest or support.

 

Realtek has their official version here. (Man, their site slow!) It's supposed to offer higher bandwidth, but lacks bonjour support. I'm going to try it tonight.

 

regards,

MAJ

[PoloBear]

I had the same problems with lan, just after I updated to F4 bios. But the german forum jzelectronic told me always to load optimized defaults after flashing. What i did not...at first.

 

But after that, all is fine and stable.

 

Running Iatkos 10.5.5 with ToH Kernel 9.2.0 without limitations right now, overclocked to 3.2GHz, sleep, internet, no sound (I have a Xfi-USB)

[mikeylam]

Well, that's revealing. Obviously hardware or even a corrupted BIOS. When I cleared the CMOS, I got in a habit of loading my saved CMOS settings. When that didn't work, I decided NOT to load any settings and reset everything from scratch. Then, everything was well. Worth a shot if you've been loading your saved CMOS settings after each clear.

 

regards,

MAJ

 

EDIT: Michael,

This is the Sourceforge.net project page for the LAN driver you are using now. It's based on the Linux driver, but modified for Mac OS X, currently at version 1.0.4 (The previous one that had sleep problems is actually a more recent version from here.)

This thread is by the guy actually working on the driver (back in 2006).

This is what he had to say:

 

So, he had planned to address three of your complaints, but progress must have stalled. Such is the case with open source if there is a lack of interest or support.

 

Realtek has their official version here. (Man, their site slow!) It's supposed to offer higher bandwidth, but lacks bonjour support. I'm going to try it tonight.

 

regards,

MAJ

 

Wow Maj, you really did some research on this. I think worst case, we can always get a PCI-e x1 card for Lan.

 

Separately, I was trying to install Vista x64 yesterday with some major troubles. Vista will not install on any of the hard disks even if I reformat / repartition them into FAT 32 first. It will give an error of 0x80300001 and say it "cannot install into the selected location". Have searched for this eror on the net but none seems related to either my motherboard or the use of osx86. I even tried XP (32bit) and its installer also refused to install to these disks. Anyone encountered this problem before?

 

Michael

[JaE-V]

Ordered a cooler master V8 for my i7. Hear its an amazing cooler.

[digital_dreamer]

Wow Maj, you really did some research on this. I think worst case, we can always get a PCI-e x1 card for Lan.

 

Separately, I was trying to install Vista x64 yesterday with some major troubles. Vista will not install on any of the hard disks even if I reformat / repartition them into FAT 32 first. It will give an error of 0x80300001 and say it "cannot install into the selected location". Have searched for this eror on the net but none seems related to either my motherboard or the use of osx86. I even tried XP (32bit) and its installer also refused to install to these disks. Anyone encountered this problem before?

 

Michael

 

Michael,

• Is the drive partitioned as MBR (Master Boot Record) under options in Disk Utility? Although it may be formated as FAT32, the partition itself needs to be MBR, not GUID or APM, my guess.
  
• I'm not sure, but does the Vista installer have the SATA drivers already included for that motherboard? If not, it won't be able to communicate with the drives. Can it really see the drives? If it's like XP, you'll have to slipstream them into the installer or install them separately during the install. Can anybody confirm this?
  

Thanks for testing the waters for us.

 

regards,

MAJ

 

Ordered a cooler master V8 for my i7. Hear its an amazing cooler.

 

Awesome cooler. It's right up there with the TRUE, but even quieter, from what I've read.

 

regards,

MAJ

[mattrb]

Wow Maj, you really did some research on this. I think worst case, we can always get a PCI-e x1 card for Lan.

 

Separately, I was trying to install Vista x64 yesterday with some major troubles. Vista will not install on any of the hard disks even if I reformat / repartition them into FAT 32 first. It will give an error of 0x80300001 and say it "cannot install into the selected location". Have searched for this eror on the net but none seems related to either my motherboard or the use of osx86. I even tried XP (32bit) and its installer also refused to install to these disks. Anyone encountered this problem before?

 

Make sure your other OSX hard drive is not plugged in when opening that vista/xp partition program.

[mikeylam]

Make sure your other OSX hard drive is not plugged in when opening that vista/xp partition program.

 

Thanks Maj and Mattrb. I tried to make them both GUID and MBR and neither one works. I also tried unplugging all drives, leaving only the drive for XP connected and it still gives me that 0x80300001 error. Very weird. The drive works in OSX so I am (pretty) sure it's not a hardware issue. I eve ntried using some old dos partitioning programme from the Ultimate Boot CD project to repartition the thing and it still doesn't work. Tried changing the HD controller to IDE in the BIOS, no luck. Tried loading the AHCI driver coming with the board, still no luck. Really don't know what's going on here. I suspect I am just missing something silly but I can't figure it out.

 

On cooler, I currently have a cooler master cosmo 1000 case so naturally I am also looking at cooler master heat sinks. I thikn the Hyper Z 600 is even better than the V8. If I don't overclock, I think i can even get by without a cpu fan. Any thought?

 

Michael

[digital_dreamer]

Hi there, first post here... reading for a long time though...

Got myself a UD5, i7 920, but as I have a ATI HD4850 I'm waiting for drivers to try osx86.

ѕӎѳѳ, did you update you firmware recently? I did update to F4 and my lan seemed dead. Reverted back to F4F and it worked again. Maybe it's worth a shot.

 

Welcome!

I believe you can still install OS X with that 4850, but there just won't be any graphics acceleration. Someone at the beginning of this thread installed OS X with the 4870 and was fine. He just didn't have CI/QE and 3D acceleration. We're hoping, like you, that Apple will release a update for those cards in a few weeks.

 

regards,

MAJ

 

Thanks Maj and Mattrb. I tried to make them both GUID and MBR and neither one works. I also tried unplugging all drives, leaving only the drive for XP connected and it still gives me that 0x80300001 error. Very weird. The drive works in OSX so I am (pretty) sure it's not a hardware issue. I eve ntried using some old dos partitioning programme from the Ultimate Boot CD project to repartition the thing and it still doesn't work. Tried changing the HD controller to IDE in the BIOS, no luck. Tried loading the AHCI driver coming with the board, still no luck. Really don't know what's going on here. I suspect I am just missing something silly but I can't figure it out.

 

On cooler, I currently have a cooler master cosmo 1000 case so naturally I am also looking at cooler master heat sinks. I thikn the Hyper Z 600 is even better than the V8. If I don't overclock, I think i can even get by without a cpu fan. Any thought?

 

Michael

 

From everything I've read, the best success comes from deleting the partitions and let Vista handle the drives. One guy put in his XP disk and deleted the partition, then was able to install Vista. Something about the partition tables not being what Vista expects.

 

I can't believe a modern OS install has to be that complicated. I was surprised that XP still requires a floppy during the install to load SATA drivers (if they are not included for your motherboard). Hello?! A floppy? What's that? I felt like I went back in time.

 

Hope you find an answer.

 

regards,

MAJ

[mauriciomoura]

Welcome!

I believe you can still install OS X with that 4850, but there just won't be any graphics acceleration. Someone at the beginning of this thread installed OS X with the 4870 and was fine. He just didn't have CI/QE and 3D acceleration. We're hoping, like you, that Apple will release a update for those cards in a few weeks.

 

regards,

MAJ

Thanks,

We'll, I really wouldn't like to try again without video acceleration. I already tried osx86 once a couple years ago, and that was the one thing that held me back. Besides that, I'm patient

I can't believe a modern OS install has to be that complicated. I was surprised that XP still requires a floppy during the install to load SATA drivers (if they are not included for your motherboard). Hello?! A floppy? What's that? I felt like I went back in time.

Hey, don't beat XP too hard on that... Think that it was out in 2001, and SATA specification is from 2003. No excuses for Vista though...

mikeylam, did you try to set IDE emulation over SATA on BIOS, to see if you at least get it to install? Then you will be sure it's a lack of SATA driver... I've installed Vista 64 with the UD5 board without a hitch... think I was using IDE emulation when I installed, but now I'm running in AHCI mode.

[digital_dreamer]

Thanks,

We'll, I really wouldn't like to try again without video acceleration. I already tried osx86 once a couple years ago, and that was the one thing that held me back. Besides that, I'm patient

 

Hey, don't beat XP too hard on that... Think that it was out in 2001, and SATA specification is from 2003. No excuses for Vista though...

mikeylam, did you try to set IDE emulation over SATA on BIOS, to see if you at least get it to install? Then you will be sure it's a lack of SATA driver... I've installed Vista 64 with the UD5 board without a hitch... think I was using IDE emulation when I installed, but now I'm running in AHCI mode.

 

Ah. So, you have the Vista drive plugged into the white SATA slots, with it configured to IDE or PATA mode in the BIOS for installation. Correct?

 

regards,

MAJ

[mikeylam]

Thanks,

We'll, I really wouldn't like to try again without video acceleration. I already tried osx86 once a couple years ago, and that was the one thing that held me back. Besides that, I'm patient

 

Hey, don't beat XP too hard on that... Think that it was out in 2001, and SATA specification is from 2003. No excuses for Vista though...

mikeylam, did you try to set IDE emulation over SATA on BIOS, to see if you at least get it to install? Then you will be sure it's a lack of SATA driver... I've installed Vista 64 with the UD5 board without a hitch... think I was using IDE emulation when I installed, but now I'm running in AHCI mode.

 

Thanks all for the input.

 

mauriciomoura, I did try to use IDE mode from within BIOS, but no luck. Deleting partition from another partition manager (tried 3 of them, OSX, XP and a dos era partition manager) doesn't get me there either. Kinda stuck. This evening, I will try to put one of the disks into another an existing XP machine, partition and format it there, maybe even clone the existing system on to the drive and put it back into the hackintosh see if I can get it to work.

[mauriciomoura]

Ah. So, you have the Vista drive plugged into the white SATA slots, with it configured to IDE or PATA mode in the BIOS for installation. Correct?

 

regards,

MAJ

 

Nope... It's in one of the blue slots. Not the gigabyte controller, the other one. Never tried to plug it in the white slots. I have also an eSATA drive, that works nicely too... also plugged in a blue slot.

But you're correct about the IDE mode. I've installed it in IDE mode, and after that changed to AHCI mode. Vista detected the SATA controller in the next boot and installed it automatically.

 

Thanks all for the input.

 

mauriciomoura, I did try to use IDE mode from within BIOS, but no luck. Deleting partition from another partition manager (tried 3 of them, OSX, XP and a dos era partition manager) doesn't get me there either. Kinda stuck. This evening, I will try to put one of the disks into another an existing XP machine, partition and format it there, maybe even clone the existing system on to the drive and put it back into the hackintosh see if I can get it to work.

 

Well, sad to hear that. I installed Vista before anything else. So the disk was blank and I used the tool inside the vista install to create just the vista partition. I know that vista can be picky about partition tables created by other tools. Oh, and just for the records... I used a Vista DVD with SP1 slipstreamed. Don't know if that would make a difference, or if it's your case already.

[mikeylam]

OK guys, after some more struggles, got Vista x64 to work. A combination of issues actually:

 

1. Installation disc was bad! This was the primary issue. Once I changed to another one, it worked.

 

2. As pointed out earlier, unplug the osx drive first otherwise, Vista "can't find a suitable system volume" (duh...)

 

3. GUID actually works. I repartition the drive in osx into 2 partitions, one in FAT32 and one in HFS+, but set it to use GUID

 

4. In Vista, I reformat the FAT32 partition to NTFS, then Vista will install

 

Now trying to figure out how to use EasyBCD to dual boot between the two.

 

Michael

[digital_dreamer]

OK guys, after some more struggles, got Vista x64 to work. A combination of issues actually:

 

1. Installation disc was bad! This was the primary issue. Once I changed to another one, it worked.

 

2. As pointed out earlier, unplug the osx drive first otherwise, Vista "can't find a suitable system volume" (duh...)

 

3. GUID actually works. I repartition the drive in osx into 2 partitions, one in FAT32 and one in HFS+, but set it to use GUID

 

4. In Vista, I reformat the FAT32 partition to NTFS, then Vista will install

 

Now trying to figure out how to use EasyBCD to dual boot between the two.

 

Michael

 

 

Good to know!

 

regards,

MAJ

[M J]

I run several more tests, after the previous "waiting for boot device" error.

 

I do have to run voodoo kernel, or the system will reboot before install. And as you guys suggested it's not necessary to specify the rd=diskXsY part.

 

It looks like the problem was a wrong version number in the Info.plist file of IOAHCIBlockStorage, a plugin inside IOAHCIFamily.kext.

 

I asked for a second Boot-132 CD with correct plist, and will give it a new try as soon as i get it.

 

Er... it is in fact necessary to specify rd=diskXsY, in my case rd=disk2s3. 2 refers to my dvd drive (0 and 1 are my two 500GB HDD), and 3 specifies the third partition on the Retail DVD. 1 and 2 will not work with a retail DVD.

 

So well... Road to success here!!!

 

Now I get to boot the system up to where it asks where to install Leopard, and I have a small problem here. The thing is that I'd like to put my HDD's in RAID1, but when I create it I get a RAID not found error at the end of the procedure, right after Waiting for new RAID to come online. Any thought on this?

[ѕӎѳѳ₮ңӌ]

im trying to dual boot vista x64 too. however i want to do it just with the efi partition bootloader and darwin. got vista installed but now i get a waiting for root disk error.... in all of my hackintoshes and their have been a few, dual booting was always the pig for me. although this time, so has ethernet! lol.

[Shadowlaw]

Another success story here!!

 

Gigabyte GA-EX58-DS4

Core i7 920

3x2GB Kingston 1333MHz

Nivida 8800GTS 320MB

 

Thanks for your guide MAJ, I have followed it and got everything up and running without problems, even for the DS4 board. Only the audio requires special treatment (ALC888 iso ALC889). Next up for me is installing an EFI partition using wolfie's scripts. The great thing now is that I have two functional installs, so I can experiment without too much trouble on the EFI part.

 

Too bad about the virtualization though, I hope the Voodoo guys manage to find a fix for that soon. Also the LAN stories are scaring me a bit here, hope mine stays alive.

[M J]

Install is stuck at 70% while checking DVD integrity. I went for lunch leaving it there, and when I was back it had rebooted: kernel panic.

 

I'm sick of it, so I'm going with iDeneb v1.3, which should be way easier to set up, then I will maybe try again with retail install.

[wolfienuke]

Er... it is in fact necessary to specify Now I get to boot the system up to where it asks where to install Leopard, and I have a small problem here. The thing is that I'd like to put my HDD's in RAID1, but when I create it I get a RAID not found error at the end of the procedure, right after Waiting for new RAID to come online. Any thought on this?

If you intend to use RAID, you will need to purchase a hardware RAID card supported by OSX. The RAID functions that are built in to the motherboard are not supported by OSX.

 

You can use Disk Utility to create a Soft-RAID, but this RAID will only be visible by OSX. There are some other forums here about installing OS X on a Soft RAID. There are a few more steps involved, but is not much more complex than a normal install.

[NeXtor]

a question:

 

The MSI already on some pre-x58 chipset, and also on this, has implemented the upgrade of the normal bios in EFI ...

 

someone tried this with leopard?

 

it is wrong to think about installing leopard without emulation efi on these motherboards by updating the BIOS in efi?

 

thanks

[mikeylam]

OK guys, after some more struggles, got Vista x64 to work. A combination of issues actually:

 

1. Installation disc was bad! This was the primary issue. Once I changed to another one, it worked.

 

2. As pointed out earlier, unplug the osx drive first otherwise, Vista "can't find a suitable system volume" (duh...)

 

3. GUID actually works. I repartition the drive in osx into 2 partitions, one in FAT32 and one in HFS+, but set it to use GUID

 

4. In Vista, I reformat the FAT32 partition to NTFS, then Vista will install

 

Now trying to figure out how to use EasyBCD to dual boot between the two.

 

Michael

 

OK. Semi success here.

 

For those who are like me, Windows and OSX on separate disks, it is actually fairly easy to dual boot (duh... having spent at least 3 hours searching for an easy answer):

 

1. At the darwin boot prompt, press ESC

2. You get to then choose another physical disk, select 80, 81, 82, wherever your Vista or XP install resides

3. You will then see "Foreign OS" pops up, choose it and you boot into that!

 

Very simple. Why is it a semi success then for me? I have partitioned that Windows disk into a NTFS partition and a HFS+ partition, intending to use that HFS+ partition as additional storage under OSX. If I do that, the darwin bootloader doesn't see the NTFS partition, even if I have it set as active. If I delete that HFS+ partition or even make it a FAT32 partition, the darwin bootloader will see the NTFS partition and allow me to boot to it.

 

Very weird. Any one has similar experience or better yet, an explanation?

 

Michael

[Shadowlaw]

So my LAN has died too, just like I was afraid of. I've been away all day (the machine was off), and upon first boot it suddenly didn't get recognized anymore. Also couldn't perform test from BIOS (it would do nothing in the screen). First tried a CMOS clear with power cable connected, that didnt fix it. Then unplugged power for a minute, put it back in, clear CMOS, that did fix it luckily.

 

But since so many of us are having this problem, we ought to start wondering where it's coming from. If it's a board/BIOS issue, then sooner or later an update will fix it anyway, and we don't have to worry. But possibly the R1000 driver is killing our LAN EEPROM - in that case, we'd better find out quick. This has actually happened before, there was some linux driver that killed E1000 cards not too long ago.

 

This was on a GA-EX58-DS4 btw, bord is very similar to the UD5.