Jump to content

valiant

Members
  • Content Count

    125
  • Joined

  • Last visited

About valiant

  • Rank
    InsanelyMac Geek

Profile Information

  • Gender
    Male
  1. valiant

    OS X compatible motherboard -> QUO

    Well, I confirmed that it was something in the Other Files category that caused the audio and video glitches. No idea what, but at this point it's easier to re-register apps than to troubleshoot a Mojave-over-Yosemite install. It seems that somewhere in the Other Files category are also the licensing files for my registered software. To be clear, this is a -me- problem -- there's no reason to believe anyone else would have the same problems installing Mojave over a working Yosemite install. I just recommend to anyone doing it that they have a good solid backup in place.
  2. valiant

    OS X compatible motherboard -> QUO

    I did not know that, thanks. Although the first hit I got searching on Kepler and Mojave included this caveat: - Kepler NVIDIA GPUs (GT 640/740, GTX 670/680/780, Quadro K5000) note: If you have a supported NVIDIA Kepler GPU like GTX 680 Mac Edition card, GTX 680 flashed with the Mac Edition firmware, GT 640/740, GTX 670/770/780 or a Quadro K5000 you can't do a USB clean install with it at the moment. The USB installer don't detect that the GPU is a Metal supported card and don't continue the install, it's a bug with Nvidia Kepler GPUs. To do a clean install, do from macOS with two drives - just select your empty one when doing the install. So it looks like it's not quite as straightforward as with a Radeon card.
  3. valiant

    OS X compatible motherboard -> QUO

    What worked for me was to run the OS installer from the Applications folder of the boot Mac* (I had it copied elsewhere as well in case it self-deleted) and choose the attached SSD as the target disk. The Mac then booted to the new install and I created an admin user. I then removed all the other drives from the QUO and attached the SSD to SATA 0, and a thumb drive with the XMAX-E ROM in one of the USB ports, and rebooted to the UEFI GUI interface (hold down DEL). Then I used the Q-Flash utility to flash the new ROM, which also created the correct file structure on the SSD in the EFI partition. I then removed the SSD from the QUO, put it back on the Mac, and copied over the KernextPatch.plist and defaults.plist into the proper location.** I took a look and you've got this: GPU: GTX 760 Part of your problem may be that Mojave and Catalina do not work with Nvidia GPU (that's why QUO mobo integrated graphics also won't work). You probably need to buy a Radeon card. There are assorted lists out there of what works. I have Radeon Vega 56, a cheaper option is RX580, and there are others that work. The mac type is defined in the defaults.plist file. BE CAREFUL with the defaults.plist on page 166 -- the forum software inserts weird invisible characters so you can't just copy and paste, it won't work. Copy it then paste it into a text editor (e.g. BBEdit in free mode) and clean up any spurious invisibles before saving it. Search out a tutorial on how to use Clover Configurator to create the serial number and baseboard serial he refers to. You may be able to use the ones you already have, but I didn't know if the serial number I had for my macpro3,1 would work for an imac13,2, so I generated new ones. - - - * In other words NOT booting from the USB drive, booting from the Mac itself. Also, I connected the external drive with the SSD in it directly to a Mac USB port, not through a hub. On my macbookpro9,2 it didn't work unliess connected directly. ** Like this: /EFI ← This is a separate partition, not the Efi folder on your boot drive you may have left over /Efi /Oz ← This will probably eventually be joined by an /APPLE directory KernextPatcher.plist ← May be optional, @IronManJFF put basic functionality into ROM /Acpi /Dump /Load /Darwin /Extensions /Common ← Put Lilu.kext & Whatevergreen.kext here if needed*** defaults.plist ← Declare Mac type here and add generated s/n. *** So far I have not needed them with my Vega 56 GPU since HDMI sound is working on my "clean" SSD install. That may change because my working install is having problems.
  4. valiant

    OS X compatible motherboard -> QUO

    Mojave and Catalina don't like Nvidia cards, Radeon is preferred. High Sierra can use either. I'm on Mojave and since I wanted to run dual 4k monitors I went with a Radeon Vega 56. The Radeon RX580 seems to be pretty popular and is available from around US$160 on Amazon. I can't tell from the specs if it will run more than one 4k monitor at once, but it may meet your needs, and it has DVI-D if you have an older monitor. I went with Gigabyte. There's plenty of options out there - good luck!
  5. valiant

    OS X compatible motherboard -> QUO

    I feel you, man. I was in exactly the same position when it came time to upgrade from Yosemite to Mojave.
  6. valiant

    OS X compatible motherboard -> QUO

    Ah! That makes sense. OK, I won't worry about it. The one advantage I saw to the flashing service was that it allowed the PCI bus to operate at full speed. When installed in a Mac Pro a stock PC GPU will only be able to utilize the outdated PCIe 1.0 format. A card flashed with a Mac BIOS will be able to work at PCIe 2.0 speeds, supporting twice the data rate. But as I reread that it refers specifically to a Mac Pro - I don't know if that applies to the QUO also. Calgary, in the Beltline. 11 minute walk from the Ship and Anchor pub. I wiped the fusion drive and cloned a working boot from the reference SSD, then first used MA to install the Application and System Files, which seemed to work. I have been moving over the users one at a time, starting with the least important ones. Last night I moved my second-most important user, with a user folder size of 1.55 TB. It was nominally successful (things like desktop preferences did not copy, which may be indicative of deeper problems, but the software I checked launched without asking to be re-registered, so that's good). That's a good idea! I'm pretty sure I ran First Aid on the backup drive while it was attached to my laptop, but there's no harm in running it again. And... "Operation Successful." So far HDMI sound and online video (e.g. the InsanelyMac video that pops up in lower right hand corner) are working just fine, which is something I appreciate.
  7. valiant

    OS X compatible motherboard -> QUO

    Well, the Carbon Copy Cloner restoration did not do what I hoped it would. User folders copied over, but not user accounts (i.e. the files are there, but when I reboot the users are not)*. Neither did the Applications folder come over from the backup, so I don't have to worry about licensing because there's nothing to license. I think I'm going to have to start Migration Assistant all over again with a wiped fusion drive. This time maybe I'll try copying over 1 account at a time? Does MA even support that - can I do one account at a time and not screw things up? Any other suggestions? Keep in mind it took 48 hours using MA, which failed and only copied 400 GB out of 5.7 TB, and it took 24 hours using CCC which copied user files but not functionality. * By default I always create an Admin account when I set up a "new" Mac. I used to always call them "admin", but there's a certain security risk there because it's so obvious, so lately I've called them something else just for variety (and it turns out when I'm booting into so many different volumes trying to figure this out, having different admin names helps me figure out which drive grabbed the boot sequence even before I log in). In this case I seem to have created 2 admin accounts, and I have 2 user accounts, so that's 4 accounts to migrate over from the backup. And I guess it's not surprising the users are not "bootable" - that would require messing with the System installation and CCC explicitly says it doesn't do that in this scenario. But I'm surprised the Applications folder did not copy over.
  8. valiant

    OS X compatible motherboard -> QUO

    Yeah. I paid CAD$360 for it on Black Friday sale. At current exchange US$175 is CAD$235. USPS shipping is another US$65 / CAD$87. Add import duties, the 2.5% PayPal exchange fee, 5% GST and it comes to around CAD$340. That's $700 total for the card and I'm not convinced it's worth it. That being said, do you find value in having a flashed card?
  9. valiant

    OS X compatible motherboard -> QUO

    Hmm. There's a company that offers to flash my Vega 56 for US$175 to make it a "real" Mac GPU. Right now I'm booting in verbose mode, which is occasionally entertaining (there's a line that includes the phrase "relaxed DAD" for instance). but I would eventually like to turn that off. The flashing service doesn't do a very good job of explaining why I would want to flash my card, and at that price, once I factor in shipping, tariffs and exchange, it's nearly as much as I paid for it. Does Whatevergreen address the same problem, but in plugin software rather than at the GPU level?
  10. valiant

    OS X compatible motherboard -> QUO

    So... While I'm waiting for the restore to finish, a couple of questions. As i understand it, the Macs that were built using the Core i7-37XX series CPUs were the imac13,2, the macmini6,2 and the macbookpro10,1. Is there a difference or advantage of declaring one over another in the defaults.plist? What about declaring as a macpro5,1? They're all dated 2012. Does the OS default to different functionality depending on the one you choose? Or does it just affect the model number in About This Mac? Also, I have been running pretty much a QUO-AOS vanilla install, with just the Kernext and default .plists. Is there an advantage or improved functionality by running Lilu and Whatevergreen? I understand that Lilu is kind of a plugin framework that doesn’t really do anything on its own without plugins, and that Whatevergreen is a common plugin used with it, however I'm not quite certain of what Whatevergreen actually does. Thanks.
  11. valiant

    OS X compatible motherboard -> QUO

    I was using Migration Assistant to restore from a CCC bootable backup of Mojave-over-Yosemite. In my experience Time Machine restores are even slower, and 48 hours was already really long. And Time Machine backups are not bootable... Right now I am doing a "live" CCC restore from the same backup. CCC has a feature where you can restore to the boot drive and it'll restore everything except for system files. I started that last night, and it looks like it'll be running until about midnight today (provided there's no weirdness with speeding up and slowing down). Although that's 24 hours, it's still twice as fast as Migration Assistant, and I'm more confident it will actually transfer over data. Yeah, I have been using CCC since before OSX, I think. I am resigned to having to set some things up from scratch: hopefully the software registrations will "take", otherwise I'll have to dig out all the old license codes and re-register stuff.
  12. valiant

    OS X compatible motherboard -> QUO

    Ah well. Better part of 48 hours, it finally completed with the innocuous remark that there were some errors and some.files were not copied over. The reality is most files were not copied. The backup drive has 5.7 TB of data on it. 0.4 copied over. 48 hours and less than 10% success rate. Very frustrating. I don't know where to try next.
  13. valiant

    OS X compatible motherboard -> QUO

    In for a penny, in for a pound. At this point I'm going to let it keep going. I look in on it every couple of hours. This morning it said 15 hours, but I looked just now and it said 1 hour 21 minutes at 11 MB/s, so I've pretty much stopped believing the predictions and will just wait it out. Thanks for you advice, by the way. I took it when you made it, but I had also reached out to Bombich Software (makers of Carbon Copy Cloner) and they got back to me more slowly than you, but with the same advice.
  14. valiant

    OS X compatible motherboard -> QUO

    Well, this is frustrating. When I went to bed Migration Assistant said "7 hours left at 38 MB/s." When I woke up it said "15 hours left at 18 MB/s." Argh. It's been running for over 48 hours now. Maybe I would have been better off trying to triage the screwed up Mojave-over-Yosemite installation after all...
  15. valiant

    OS X compatible motherboard -> QUO

    I keep checking on Migration Assistant and I’ve noticed the progress text says file transfer is somewhere between 40 and 60 MB/s. I’ve also come across posts talking about macOS USB port limits and speed, but didn’t pay attention at the time. I’ve got a usb 3 drive plugged into one of the usb 3 ports on the back of the mobo. Is 60 MB/s a typical transfer speed to expect from a spinny HD? Or is it possible I have the USB 3 ports not configured properly for full speed? How would I test that? Thanks. EDIT: Well, I’ve seen speed announcements as low as 11 MB/s and as high as 87 MB/s, so I think it’s the software not the port speed.
×