Jump to content
InsanelyMac Forum

bgd

Members
  • Content count

    17
  • Joined

  • Last visited

  1. It depends on your application. The i7 is significantly faster, and is capable of more serious overclocking than the Core2Quad. If you're doing video editing, image processing, or running lots of audio plugins, the extra speed is definitely worth it. Otherwise the Core2Quad board will do do you well, and it's a bit less finnicky about running OSX than the i7 board. best bgd
  2. Chris - Are you using the same setup? (Details in my signature). Does the driver show up in System Preferences? (You should see a list of outputs as "Internal Speakers", "Headphones" etc. Likewise a list of inputs beginning with "Internal Microphone")
  3. I found this fix on another thread which I applied to the problem on the HDA.kext for the DS4. http://www.insanelymac.com/forum/index.php?showtopic=127877 Attached are the patched kexts that fix the problem with weak bass and distortion. These are modified from the ones that Fiat sent earlier today. HDA888__works_with_EX58_DS4__weak_bass_fixed_.zip
  4. I've now had some time to inspect the audio output of the DS4 a little more carefully and determined that there is something wrong, or at least, less than optimal. Using the 'Internal Speaker" option, which is the only one which sends a signal to the back panel connectors, there is a definite weakness in the bass (about -10 db at 100 hz). It drops off about the same at 10 khz. These are significant. This output also starts distorting severely when the signal rises above about -12db. I suspect that the "Internal Speaker" pathway has some shelving filters on it to eq the signal for a tiny builtin computer speaker. The headphone output is actually flatter in frequency response, and doesn't distort, but has a lot more noise. The digital output works fine, and using the D-A converters in my 20 year-old Panasonic DAT machine sounds fantastic. I guess this is what I'll have to use. It sounds way better than my $200 Tascam USB audio card. The question then becomes - what happened to the Line Out pathway? I suspect that this is the one pathway that would have a flat frequency response and not be prone to distortion and noise. Unfortunately, when I select that option from the list in System preferences, no signal appears at any of the various audio jacks. I believe that there is some mixup in the details of this driver. Does anyone know enough about HDA audio drivers to suggest a fix? thanks bgd
  5. I've run Final Cut Pro 5.1 on the EX58-DS4. Not a very thorough test, but I launched the applicatin, loaded an old file, played a few seconds, etc. It all seemed to be working fine. bgd I've run Final Cut Pro 5.1 on the EX58-DS4. Not a very thorough test, but I launched the application, loaded an old file, played a few seconds, etc. It all seemed to be working fine. bgd
  6. Thanks, Fiat, those work great! I've checked only outputs so far, but the following all seem to be OK: EX58-DS4 w/OSX 10.5.2 (installed via Kalyway) Internal Speaker - OK, but appears on back panel Digital out - OK Headphone out - OK The only thing that threw me a bit was that "Line Out" doesn't send the signal to the back panel as expected, but ""Internal Speaker" does. So how did you do it? I've tried at least a dozen kexts and made at least that many more myself without even getting one to show up in Preferences. best bgd
  7. Based on my experience with the EX58-DS4, yes, all cores are being used. Check your Geekbench score. Also, prime95 knows that it should run 8 threads for doing its torture tests. The audio is another matter. There seems to be a lack of success here in getting the ALC888 to work on this line of boards. I've been trying for several days - at least 10-12 different 888 versions of AppleHDA, but none of them even get as far as being recognized buy the OS. bgd re: Gigabyte EX58-DS4 - lack of audio : There is no device indicated in the the Sound Control Panel, so I'm wondering if the ALC888 problem might be as simple as an incorrect identifier in the modified drivers? Evidently the OS doesn't match up the information it receives from querying the chip with the device_id embedded in the driver. I'll look into Intel's HDA specification regarding chip 'discovery' by the OS. In the meantime, perhaps someone who understands the HDA startup procedure could comment? bgd
  8. Thanks MAJ, I'll try them out. I've tried at least 6 others so far, but those ones don't look familiar. Question: Should I delete ALCInject.kext if I'm using HDAEnabler, and vice-versa? Also, are the files AppleAzaliaAudio.kext and Apple02Audio.kext required or are they left-overs from previous attempts? LATER: I've tried all three of the options you pointed me to, but without success. But I've now got both HDAEnabler and ALCInject in the extensions folder, along with the modified AppleHDA. A clear list of required audio extensions would be nice. I can check my MacBookPro, but it's running Tiger, and I think the extension configuration is a bit different. bgd
  9. I'm still trying to get the ALC888 Audio working on Gigabyte's EX58-DS4 - Digital_dreamer, do you think it might be possible to modify the relevant files in your EX58-UD5 package? It looks to me like the files n question are: AppleHDA.kext HDAEnabler.kext I am willing to explore this possibility, but I thought I would ask you first for your opinion, based with your experience with the ALC889 on the UD5. thanks bgd
  10. Thanks np_, I will try your more detailed method and see if I can bring that UD5 back to life. bgd
  11. OK here's the good news: I've got Kalyway 10.5.2 running on the Gigabyte EX58-DS4, with GeForce 8400, QE/CI. I've also had a more limited success using iPC 10.5.6 combined with digital_dreamer's kexts from his tutorial on the genius bar. Question: Has anyone here had success with getting audio to work on this board? It uses the ALC 888 codec. I know several people were experimenting with it earlier but I don't recall seeing any reports of a positive success. Any help or suggestions would be appreciated. thanks bgd
  12. np_, I followed your instructions as follows: 1. I disconnected PSU, unplugged all cables from the motherboard, including power cables. 2. I removed the battery and shorted the terminals with a screwdriver for >30 seconds. 3. I took out all RAM, then put a single stick of RAM (2G, 1600, 1.65v) in slot #1 4. I re-inserted the battery and plugged in the power cables. 5. I reconnected the PSU and attempted to restart. The above had no effect on the problem. ======================== FYI, Here is the exact sequence of events that led to the problem. 1. Following the manufacturer's instructions, I installed the CPU (i7 920), Stock Cooling Fan, and RAM (3 x 2G OCZ-1600). 2. Connected front panel cables for power and reset, and connected both PSU (500w) cables, i.e the 24-pin and 8-pin cables . Also connected GeForce 8400 card into PCIe 16x slot#1. 3. Booted fine several times with no HDD or DVD connected. I watched the Manufacturer's color logo screen, followed by BIOS check on a connected monitor. I was also able to go into the BIOS (using the DEL key) where I experimented briefly with setting the bClk to 160mHz. That gave me a CPU speed of 3.2 gHz. BIOS still ran fine, so I shut down and connected the HDD and DVD. 4. Using F12 key, I booted from DVD (OSX 10.5.6 installer running on iPC disk) and got as far as the Darwin prompt. Memory showed as 6091 megabytes. After a moment however, the Darwin loader crashed at error message, "Cannot find apple.com.boot.plist". 5. After a minute or two I pressed the reset button on the case. From that point the board never booted again - no POST, no error codes, just a brief spin of the CPU fan, a flash of LEDs, then off, in an endless loop. ==================== I've researched this on various other lists including Tom's Hardware and the customer reviews on newegg.com It seems that many people have had similar problems, but there is no consensus on a fix. Most people just return the board for a replacement, but then sometimes receive a 2nd board with the same or related problem. Others claim to have fixed it by replacing RAM or PSU. I spent most of the day yesterday trying all the usual fixes - reset BIOS - remove battery - single memory stick in slots 1, 3, or 5 (and various combinations thereof) - reseat CPU - alternate PSU (a 300w unit however, which is all that was available to me) Today I will try another PSU (I have a 500W unit at another location), and alternate RAM, which I will have to buy. If that doesn't work I guess that I've got no choice but to RMA the board, CPU and RAM. The system worked fine after the initial build for at least 3 boots. Then,with no change of hardware at all, it ceased to boot. Here is my theory. As described above, after several faultless boots I experimented with overclocking by raising the bClk to 160 mHz. This seemed to work fine, at least for the next boot. But after forcing a hardware reset, the BIOS re-adjusted the "AUTO" voltage to CPU and RAM, sending it into unsafe or inoperable levels. Hence the flashing of all twelve CPU loading LEDs when the board attempts to power-up. This may have happened because the RAM is 1.65v, which is the maximum allowed for this CPU. This is pure speculation of course, but it would seem to fit the facts. Any suggestions would be welcome. bgd
  13. Thanks np_, I tried that but no luck. The machine still gets stuck in a loop immediately on power-up. There is no indication that the BIOS is even loading. One clue is perhaps that the CPU phase LEDs light up all the way to red on the attempt to power up. Maybe someone with a UD5 could take a look - it's the row of 12 leds located right next to the onboard power switch. Do they all flash for a moment on startup? bgd
  14. Has anyone here had reliability problems with the Gigabyte EX58-UD5? I assembled a system today, which booted twice into the BIOS. On my third reboot, it spins the CPU fan for 3-4 seconds, flashes the board LEDs, then stops and tries it al again- stuck in a loop. It never gets to the BIOS screen again. I've tried resetting the CMOS, reseating & re-arranging the RAM, pulling out the graphics card, disconnecting HDD and DVD, etc. Nothing will now bring the board back. I don't think it's a board issue, since it twice booted fine. Personally, I suspect the RAM. Anyway, back to my quesiton - has anyone had similar problems and perhaps found a solution? - BD
  15. Apologies if this is obvious, but is there a clear explanation somewhere for the "Boot-132 method"? I have done Kalyway, iatkos and iPC-OSX installs succesfully on Gigabyte hardware, but I'm not familiar with Boot-132. thanks Bruno
×