 |
|
|
|
#1
12-01-2010, 09:59 PM
|
|||
|
|||
|
Hey everyone. I'm putting together a new build for a friend based on an eVGA X58, so thanks for 30+ pages of good info. I've read through a lot of it and tried to retain as much as possible, but still have a couple questions. I just started really working on getting things up and running (hadn't found a good thread like this till today), so I haven't tried a whole lot yet.
The build is: X58 FTW3, i7 920, AMD 5870 Ignoring the GPU for now, because I know most people in here are using NV cards, here are my questions. 1. LAN, For the SLI or Classified most people have, does eth work out of the box? Maybe I missed what everyone is using for a fix there, but I haven't seen anyone mention the RLT811xx driver that I've been using. I need to reread the DSDT patches more carefully, so maybe it's in there. That driver is actually working perfectly for me, but it needs to be installed to /s/l/e and I'd prefer to go another route if there is one. 2. Audio, seems like HDEF in the DSDT and a patched AppleHDA is working well, but some people are still using Voodoo. I'm more used to patching HDA, so planing on doing that unless there's a strong reason not to. 3. USB, I tried upgrading to 10.6.5 once already, but lost USB entirely like some other people did, but I haven't seen anyone report that in this thread. Is that a problem unique to the FTW3? Or will it not be an issue once I get a DSDT built? 4. DSDT, Does anyone know how similar the FTW3 actually is to the SLI or Classified in terms of the DSDT. Those two boards are clearly the most popular here, but maybe I missed someone saying they'd had success with similar patches on an FTW3. I like making mine by hand anyway, so I'll find out soon enough, but just figured I'd ask if it could save me some trouble. Thanks again for all the work you've already done, and any help you can provide. 
|
|
#2
12-02-2010, 06:28 PM
|
|||
|
|||
|
YES! Farski, I believe the FTW3 is going to be very similar to my SLI3. I have to use the same ethernet driver. For sound I have to use VoodooHDA because I have ALC892, which won't work with AppleHDA even if you patch it. I think the FTW3 has ALC892 as well. I took the AZAL/HDEF section out of my dsdt so I don't have to delete AppleHDA to prevent KPs from VoodooHDA. I didn't have any usb problems with 10.6.5, aside from the fact that if I booted with the iBoot CD I had, my USB didn't work, so I'm wondering if you're using any tonymacx86 related usb kexts somewhere. I got a new iBoot CD and now that works fine when I need to boot from it. I have everything working including USB3, but excluding SATA3 and speedstep. If you can get speedstep working you're my hero. No one with an EVGA X58 has gotten it to work on bios 44 or newer. You and I are limited to like 76 or 77 since our boards are so new, so we can't use the versions older than 44 that are known to work. I've been trying for months with no luck, so I may switch to a Gigabyte eventually.
|
|
#3
12-03-2010, 05:26 PM
|
|||
|
|||
|
cool, good to know about the audio/LAN. Not perfect fixes but certainly easy enough to live with. I'm not too concerned about speedstepping, because I think this machine's either going to be off, or on and gaming or crunching photos. If it's not an easy fix I won't have enough time probably to do any real work on it before I need to ship it off to the owner; sorry I couldn't be more help there.
Looking back I bet I still was booting off iBoot when I had those USB issues in 10.6.5. Once I got an actual install of chameleon going I never even bothered to try again. I had actually also gotten USB3 working in 10.6.4, but can't remember which patched driver I used; do you remember which you're using? I'm going to read through the thread again this weekend probably to get through most of the DSDT stuff, but are there any notable changes you made for the SLI3 besides HDEF I should know about? Thanks
|
|
#4
12-03-2010, 06:30 PM
|
|||
|
|||
|
I just followed the guides for gigabyte boards. There's a basic one on tonymacx86, and then some more really detailed ones on insanelymac. I have a post a few posts back that has mine with some other things I'm using attached, so you can take a look. The one I'm using now differs slightly from that one, but it's nothing major.
You're really bumming me out on the speedstep though. 
|
|
#5
12-11-2010, 12:43 AM
|
|||
|
|||
|
Okay so I just want to check to confirm, is the panic that everyone else gets with bioses newer than SZ2Z when trying to load AppleIntelCPUPowerManagement at boot a type 13? Mine is, and I want to make sure everyone else is getting the same one.
|
|
#6
12-20-2010, 08:53 PM
|
|||
|
|||
|
Great. Thanks for all the help guys. I'm giving up now and buying an ASUS or Gigabyte even though I don't like the design. At least it will work better.
|
|
#7
12-22-2010, 01:01 AM
|
|||
|
|||
|
i just updated mine. no problems at all. all vanilla kext, except for some GPU files for my GTX480 which supports CUDA now and no more vsync issue.
Code:
|
|
#8
12-22-2010, 01:42 AM
|
|||
|
|||
|
You should make a note in the first post about speedstep not working on the X58 SLI3 or X58 FTW3, and how it only works on the other models if you use the bios version before version 44, which is of course SZ2Z. I changed my mind and haven't completely given up yet, but if I like the Gigabyte X58 G1 when it comes out I'll probably get that.
|
|
#9
12-23-2010, 10:02 AM
|
|||
|
|||
|
sure thing. ill just quote you
Code:
|
|
#10
12-23-2010, 10:58 AM
|
|||
|
|||
|
I've been looking into it more. I'm wondering if I replaced the CPU microcode in bios version 77 from EVGA with the microcode from a Gigabyte X58 board's bios if that would fix it, but I'm not sure if that's really the problem. This is a copy of my post on insanelymac:
On EVGA's website, they list these differences between bios 44, which breaks AppleIntelCPUPM support, and SZ2Z, which enables it: Quote:
1. The CPU microcode 2. The "Turbo Performance" option 3. Notice how the naming conventions of the bioses change from SZxx to just two digits. Does this mean that perhaps they did a complete rewrite and that the cause of our problem could be something unrelated to the added features in version 44?
|
Hybrid Mode