Jump to content
Welcome to InsanelyMac Forum

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

It's Phobos!

  • Content count

  • Joined

  • Last visited

About It's Phobos!

  • Rank
    InsanelyMac Protégé
  1. New OS X compatible motherboard -> QUO

    Pins 1 and 6 on the main bios chip. Pin 1 is marked with an arrow, the rest of the numbering goes clockwise around the chip (pin 8 is across from pin 1). This is possibly the page you're referring to. I had to restore the backup bios on my quo-aos last night actually, which is how I came across this post. What you'll want to do is seat a stick of RAM in the slot nearest the CPU, Press the power button to turn on, release and immediate press and hold the power button until the computer shuts down. Press the power button again to start, the bios restoration process should start. This is Method 1 on the page I linked above.
  2. New OS X compatible motherboard -> QUO

    That was my experience getting it to work again.
  3. New OS X compatible motherboard -> QUO

    Considering what some of us know about this board, here are Gigabyte's instructions for invoking the backup BIOS. 1. Shut off the power supply using the switch on the back of the PSU, wait 10-15 seconds. 2. Press and hold the case Power On swtich, then while still holding turn on the power supply from the switch on the rear. 3. Still holding the case power on switch, the board will start, once it does release the case power on switch and shut off the power supply via the switch on the read of the unit. (Do the latter two parts as quickly as you can once the board starts) 4. The board will shut down. 5. Turn the power supply back on using the switch on the rear of the unit. 6. Turn on the motherboard by pressing the case power on button.
  4. New OS X compatible motherboard -> QUO

    My Messages didn't want to log in either, even with the baseboardserial set correctly. I found that it was only doing it with my ID, others could log in fine. I went into ~/Library/Preferences and deleted everything with imessage in it. Working flawlessly again.
  5. New OS X compatible motherboard -> QUO

    10.8.5? 10.9 is out and it's free.
  6. New OS X compatible motherboard -> QUO

    Finally got my sound issue sorted with 816M. I took a look through the output from bdmesg, looking for anything useful, and determined that it was looking for /EFI/QUO etc on the first FAT32 partition is encountered. On the boot for the first export I made, that was on a thumb drive, so I removed it and rebooted. The next boot it was looking at the ESP on my Users drive (GPT partitioned so it has a ESP as well). I could have deleted the partition, but I got curious so I mounted it up, made sure it was formatted FAT32 (the ESP on my System drive was FAT16 for an unknown reason. I must have messed with it long ago.) and dumped the DSDT.aml that I made into it for giggles and rebooted. I now have sound and this line in bdmesg 08:069 00:000 Insert DSDT 0x5D828200 r2 0x9D1F 0x47 "ALASKA" "A M I " 0x12 0x4C544E49 0x20100331 DSDT.aml So, with this done thanks go to bs0d for pointing out the format issue, and to THe KING for trying to help with the aml file itself, even if it ultimately wasn't the root of the problem.
  7. New OS X compatible motherboard -> QUO

    I went through and put the file in the correct directory on the ESP as mounted by the the process joe75 wrote up, and still no HDMI audio out of the graphics card. I also keep looking through bdmesg after it boots and I don't see any sign of the .aml file actually being read like it does when I boot it with Chameleon. The DSDT I posted before I think may have been made with MaciASL set to ACPI 4.0 instead of 5.0. I've not had to even use a DSDT until this build because I was fortunate enough to have a rig that worked with two additional kexts. I don't know if there's something I'm doing wrong here, or what. For now I'm to go back to F3A and load with Chameleon and my DSDT that may be all wrong, but at least works.
  8. New OS X compatible motherboard -> QUO

    I need to learn quite a lot on this side of things, not a lot of useful documentation to be found concerning this combination of HW and SW.
  9. New OS X compatible motherboard -> QUO

    the ioreg makes the board screw up, so attached ioreg.txt
  10. New OS X compatible motherboard -> QUO

    Here's a zip with my DSDT, and the SSDT that I tried. And here is my bdmesg output after reapplying H3A 816M AML files.zip
  11. New OS X compatible motherboard -> QUO

    By ESP I assume you're referring to the FAT16 EFI partition that's ~200MB in size located @ disk0s1. So far, no luck. I've put my DSDT in there, I've made a SSDT and put it in there, and I've tried Toleda's SSDT in there. Nothing I do gets me HDMI audio from my GTX 660Ti on Oz 816M.
  12. New OS X compatible motherboard -> QUO

    I've honestly only vaguely read through these comments, but I do have a question. I have a patch DSDT.aml to get HDMI audio working through my GTX 660Ti. Because of this, I'm currently stuck using the non Oz firmware. Is there a guide or anything anywhere that I can use to get my change into the firmware itself so that I can be like the cool kids?
  13. New OS X compatible motherboard -> QUO

    I may or may not have already seen a revision of this BIOS, does the GTX660Ti work on this revision (since on H3A.705 it did not) with HDMI audio, any progress on fixing the Messages bug? That Jeff Carnell is such a loser
  14. G5 to ATX Front I/O Cables

    Alohacab, I have one of your cables and it's great, but do you know what the pin arrangement needs to be for it to work on a 1394b header, or if that will even work?
  15. New OS X compatible motherboard -> QUO

    I have asked quite simply if I could change my shipping address to my work address since he's shipping by USPS (seriously? how cheap can you be after all the delays?). I've asked this in three emails, both to rashantha directly, and to the sales email. I've asked on facebook. I've asked via twitter. And it has been all for nothing. The statement about that shipping would take place at week's end (I'll believe it when I see it) wasn't even made on kickstarter or the website. I had to find out from a third party forum post. What kind of company did I give my money to? Shouldn't this be pretty straight forward stuff? You could probably manage 509 backers, their names, backing order, amount billed, shipping address, and any other details pretty well with just a spreadsheet. Or is tweeting about the NBA finals and keeping up with Sri Lankan politics more vital than updating the people who gave you $190K? EDIT: Three emails, a tweet, and three facebook messages later, we have a response!