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.


  • Content count

  • Joined

  • Last visited

About timmy_pete

  • Rank
    InsanelyMac Protégé
  1. Firewire 800 bracket for Quo motherboard

    All valid points, but they advertised it prominently as being Firewire 800 compatible, when in fact it is not without considerably expensive or necessarily complicated workarounds. I'll keep an eye out to see if any more copies of this FW800 bracket appear, but it might be a while. Out of curiosity, does OS X's System Profiler list the speed of your HDD when connected? It should be under Hardware> Firewire.
  2. Firewire 800 bracket for Quo motherboard

    Thanks HesyRe for reviving a dormant project. Looks like this part is out of stock, but I'll see if ASUS support has service parts shippable for a reasonable rate to my country. My earlier efforts resulted in the two ports on my eBay sourced bracket working at FW400 speeds, and I was never able to get the 800 jack working at full native speed. I've since focussed on replacing Firewire gear instead, as it seemed a more simple course of action. As an aside, there is possibly now an easier option. After Quo shipped my Kickstarter board I asked for months on end about whether the bracket they'd promised to make was any closer to production. They ignored me outright on at least 10 occasions, so a friend emailed them as a new customer and said they were only interested in buying Quo if Firewire worked. The friend was told they sold a bracket and it was available for $12. They didn't reply to any emails I sent subsequent to this (to the same address) so it's pretty clear I'm on their ignore list. While this is nowhere near as abysmal as the outright theft from the folks who pledged $2,500-$3,000 for full systems which more than a year later haven't been delivered, or shipping boards to website customers before Kickstarter backers, it is a pretty awful approach to customers. I'm not willing to even risk another $12 with them to get a product delivered, but some people who want an easy option and are willing to gamble with Quo might well ask them more about this item.
  3. New OS X compatible motherboard -> QUO

    It might be worth seeing if the same behaviour happens with another keyboard as I've had some issues on that front in the past. In other news, I've confirmed the lack of scheduled shutdown was a Yosemite issue. It works fine on a Mavericks Macbook I checked as well as this board on my old Mavericks image.
  4. New OS X compatible motherboard -> QUO

    @IronManJFF - I've just tested and was able to remote boot while KB is plugged into a USB3 port on my front panel. My usual setup has a Yubikey 2 factor authentication device (which presents itself to the computer as a keyboard/HID) permanently plugged into a front USB3 port, and booting has been consistent across the various BIOSes. I think you might be onto something though. I've never been able to boot from USB install media plugged into the front panel USB3 ports, and I've got two differently-branded microSD card readers that won't work unless they're plugged into one of the IO plate's USB2 ports. I'm not sure quite what's happening, but this BIOS does seem to make some sort of distinction between the ports. I'm planning this evening to put my old Mavericks SSD back into the tower and see whether it will allow scheduled shutdowns from pmset on the desktop. Your experience, and mine testing with a 10.9 Macbook Pro suggest that the OS, not motherboard might be the root cause. Obviously the reboot instead of shutdown issue with WoL packets is the root cause, but if I have a workaround for remote shut down it really wouldn't bother me much. @IronManJFF - I forgot to ask if your keyboard at all special? Does it have a hub or memory card reader embedded?
  5. New OS X compatible motherboard -> QUO

    Thanks for checking @IronManJFF. Guess I'll have to troubleshoot a little more at this end. As we're both on 1479, its likely to either be something particular to my computer, or some difference between Mavericks and Yosemite (if your sig is current). Either way, that suggests the script I've got on the previous page of this forum should work for remote shutdown for folks experiencing the WoL reboot issue.
  6. New OS X compatible motherboard -> QUO

    Thanks. If possible could you check if it works on the login screen? Scheduled shutdown works when logged in for me (subject to a 10min countdown timer) but not when rebooted and sitting at login. I think this is an issue with the motherboard, as the below script works as expected on my Macbook Pro. #!/bin/sh # WoL reboot workaround # v1.0 # Must be run as root # # Calculate four minutes from now: FourMins=`date -v +4M "+%m/%d/%y %H:%M:%S"` # Alert user to time and schedule plan echo "It is `date`, shut down scheduled for $FourMins" # Schedule second/final shutdown pmset schedule shutdown "$FourMins" # Display schedule, allows for manual confirmation: echo "Scheduled power events:" pmset -g sched echo "10s to first shutdown" sleep 10s # Device will complete first shutdown and then reboot with a scheduled shutdown shutdown -h now # Following reboot, device will alert that it will power down in 10m.
  7. New OS X compatible motherboard -> QUO

    My output is above for your reference. Have never used hibernate or sleep, and the differences are from my customisation of energy saver preferences. As far as I know, only the WOMP flag should have any effect on WoL, and you've got the correct setting there. Out of curiosity, why are you using mode 3 (disk+RAM) for hibernate rather than the default desktop mode 1 (RAM only)? Separately, has any one had luck scheduling shut downs with this board? Mine never responds to events set with the pmset tool if the loginwindow is displayed. Scheduled power down only works while logged in once a 10min timer has elapsed. This stops an easy script led workaround for the WoL reboot issue (schedule a power off event with pmset, before shutting down).
  8. New OS X compatible motherboard -> QUO

    Have you turned on the feature within OS X, and are you trying it with wired ethernet or wifi? To enable, go to System Prefs> Energy Saver and click Wake for Network Access. If you have this set and are trying wired (AFAIK it doesn't work with WiFi), then I don't know what to say. On a broader note about the Wake-on-Lan issue where it subsequently powers on, I've made a few observations, but still haven't fixed the issue. A range of EFI boards (esp. Intel and Gigabyte models) seem to exhibit the same issues for Linux users. See here, here and here for eg. Some users reported fixes by tweaking ACPI settings, but no equivalent setting combination seems to work for me. Verbose boot confirms that OS X calls for a reboot when shutting down following a WoL boot. I'd therefore think the issue lies with the motherboard settings, or in the way its power management interacts with OS X.
  9. New OS X compatible motherboard -> QUO

    Does anyone have much experience with Wake on LAN and this board? While this BIOS is much better than prior versions (I used to only get successful power on intermittently, tested my WoL tool on other machines and it worked reliably with them), an issue I've had in the past still occurs: On all BIOSes (including H3C 1479) the machine turns on successfully, however after shutting down from a WoL boot, it reboots a second or two later. Subsequent shut downs nearly always work, but its a bit of a pain having to shut down twice.
  10. New OS X compatible motherboard -> QUO

    Wiki not up to date. Not sure why my InsanelyMac login won't work on the wiki. Regardless, first link in this thread points to Mediafire and is still online, and there is also a GitHub repo with copies of all earlier versions.
  11. New OS X compatible motherboard -> QUO

    I haven't had a chance to install the update BIOS yet, but am planning to do so when I get home. Does anyone know if it changes the situation with Wake on Lan? I've never been able to get it to work on my board, and so far as I can recall there were no answers to someone else's questions on this a few weeks back. On a second point: I've brought across a legacy Windows 7 HDD from before my Quo build, and have unsuccessfully tried to convert a cloned copy of this disk to UEFI. Are you aware of any easy way to convert to UEFI that I could try on another clone?
  12. Firewire 800 bracket for Quo motherboard

    Fantastic work finding the pinout and confirming the FW800 port presumably runs on 400 speeds iLeopod. I've been travelling and haven't had much time to work on this. With what I now know about the FW800 port things aren't ideal, but I'm hoping a dedicated port will be faster than the existing daisy-chain of devices off the board's single FW400 port. I'm now waiting on another bracket to come to cannibalise the headers (this was the cheapest I found) as the ones I ordered online were a mil to thick on each end and I couldn't seem to find them sold on their own.
  13. Firewire 800 bracket for Quo motherboard

    I've had some success but still have a few things to work out. Firstly, I've use continuity checks on my multimeter to determine the cable for each corresponding Firewire pin. The results I've put are below (please note most internet FW pinouts are of the cable view which is opposite to the jack view I am using): The first surprise was that the 6 wire cluster was for the Firewire 800 port, and the Firewire 400 port appears to be using the 9 cable cluster. The second surprise is that as far as I can tell FW800 pins 5,6,7 & 9 don't seem to have a corresponding pin. I don't understand the distinctions between FW400 and 800 enough to know if this is surprising, but as far as I know two of these should correspond with the shielding around each of the two sets of twisted pair. I'm confused by the manual's documentation of motherboard pins 7 (+12V) and 8 (+12V fused). If "fused" means an electrical fuse I can't see any indication of it on the motherboard or device side. If they mean fused as in "joined together" then I guess this is a reference to the two white cables that are paired. Either way, I wasn't able to get headers of the type I needed because I live in a small town. I therefore removed the USB2 header plug and wired up the FW400 port per annotations. It seems to work with an iSight and external drive - obviously only at FW400 speeds - but I didn't want to test too extensively given my confusion as to which of the Gigabyte Motherboard's power ports was appropriate. I'm hoping someone who understands the FW800 pinout better will be able to give more information. I'm presuming otherwise I'll be able to wire the port up like I've done with the Firewire 400, but that it might only run at the slower speed. Thanks for your help, all the advice is spot-on and I'm triple checking everything as I go. I haven't had much luck with Gigabyte thus far. Initially I'd tried to order a motherboard bracket or get access to a similar manual and their service department has flat out refused to assist because I don't own a motherboard available for purchase off the website. Reasoning that this was a general enquiry (not a warranty claim) fell on deaf ears, and as far as they're concerned any motherboard missing the Gigabyte logo (as ours is) is a counterfeit and therefore ineligible for service. Hopefully my additional headers come soon; I had to order from China - I live in a smallish town and my electronics shop only sells 5x2 IDC plugs suitable for use with ribbon cables.
  14. New OS X compatible motherboard -> QUO

    The FW400/FW800 bracket off eBay that I ordered earlier has arrived. Extracting the pins intact was easy and I'm going to experiment tomorrow to workout the exact pinout and put them on new headers. Photos and details in this forum post. I'd appreciate help from anyone who has done this already.
  15. After more than a year Quo still hasn't given a definitive answer when the promised Firewire bracket will be available, I've given up hope. I need it and can't wait any longer, so am going to try build one myself. I ordered this backplate on eBay on 28 March and it arrived from China today. The bag it comes in bears the Gigabyte part number 12CR1-1UBIE1-01. It has 2x USB ports terminating in a yellow 10 pin (2x5) IDC plug. There is also a FW400 and FW800 port. A 6 cable cluster and an 8 cable cluster terminate on a purple 16 pin (2x8) IDC plug. The good news: Seems very good quality and is seemingly from Gigabyte. With a magnifying glass and scalpel you can pull out plastic tabs on the plug, allowing easy removal of the pins intact. Cable length suitable for my mid sized case. The bad news: Wire colouring is inconsistent with what I expected (Missing purple, grey and brown cables on the 800 cluster) 9 pin layout is not as I expected (6 pin might be largely the same) 9 wire cluster has two wires fused on one pin (not per 1394B spec) The wiring pinout for an 8 wire and 6 wire bundle. The 16 pin IDC style plug header. The wires removed from the header. The other end is shielded and epoxied. It doesn't look like I will be able to access the wires easily, and my multimeter probes aren't fine enough to use on the ports directly. I'm hoping I'll still be able to use the FW400 port, but if that doesn't work I'll just use the 800 & USB ports and then rely on the motherboard's IO pane 400 port. At this stage because of the inconsistency in the pinouts I've seen and the ambiguity of colours, it looks like I'm going to have to cut up a FW800 cable (and possibly a FW400 cable too) and test with a multimeter to determine the correct pinout. I'm going to be guided by the wiring colours listed at this website (which does not mention motherboard ports at all) I don't know enough about the Firewire spec to know if the two fused wires are OK or if I'll need to splice one onto a new pin. Any help on this would be appreciated. This is the pinout of the current configuration: This is a diagram I've made from the motherboard page and an image I found on the net of the (apparently correct) colour spec (which follows afterwards). The Black and White cables with a dark background are thicker than the other black and white wires. The thick white wire is actually two terminating on the same pin. (the reference to manual means the Quo motherboard manual). Website means random image found on Google. Firewire 800 pin layout Firewire 400 pin layout. (NB - judging by colours, it is possible that the FW400 part of the 16Pin plug is in this format with only Black S-GND on the opposite side) I will hopefully get a chance tomorrow to pick up some 10 pin (5x2) IDC plugs, a battery for my multimeter and a Firewire cable I can take apart to test pinout. From there I'll test further. IF ANYONE HAS DONE THIS BEFORE I'D REALLY APPRECIATE YOUR GUIDANCE. I don't want to damage my Firewire controller.