Jump to content

adrianjgsmith

Members
  • Content count

    12
  • Joined

  • Last visited

About adrianjgsmith

  • Rank
    InsanelyMac Protégé
  1. It's time to spring clean my system and I want to do a clean install of OS X 10.11.6. I've made an install USB using Diskmaker X, and managed to boot to it through Clover in Single User Mode. However it's going straight into an update, not giving me the option to Format the main drive using Disk Utility. Can anyone point me in the right direction? [EDIT] Solved it now. I'd been unable to format the SSD from the Recovery Partition's Disk Utility, as it wouldn't unmount. I've since tried it again and it worked, which has stopped the Installer from going into a straight update.
  2. adrianjgsmith

    Wifi dropping with memory error

    The wifi driver? Mediatek's site says it's good for 10.9/10.10/10.11. I had this problem with an older driver, as well.
  3. I've been experiencing wifi dropouts for some time now. When it goes, I can't reconnect to the router without shutting down first. At the moment it happens, I start getting endless "MT=>SYNC" memory errors in the console. These are repeated during shutdown and, if I restart instead of shutting down, at the next boot up as well. Here's what I'm seeing in the console: I have a load more of these errors, with a few other things thrown in, but you get the idea. OS: Yosemite 10.10.4 Motherboard: GA-Z77MX-D3H TH Wifi: Linksys AE6000 (MT7610U chipset, running Mediatek 5.0.1.25 driver and D-Link 2.6.4.0 Utility)
  4. adrianjgsmith

    Can't get Ultrawide resolution

    Thanks again for all your help, Allan. I was away for a few days but read up on the link you'd sent. In the end it was as simple as setting PatchVBios back to 'true'. I now have full 2560x1080 resolution in Clover GUI, Mavericks and Windows 7. Ta!
  5. adrianjgsmith

    Can't get Ultrawide resolution

    I tied inserting both 2560x1080 and 1920x1080 in the screen resolution (using Clover Configurator). Judging by my boot.log the resolutions are being spotted, but not utilised? Should I be injecting another EDID?
  6. adrianjgsmith

    Can't get Ultrawide resolution

    Just for Posterity's sake: Using a DisplayPort cable and Duckweed framebuffer has allowed me to get the full 2560x1080 resolution. Now I just have to get that resolution for the Clover GUI...
  7. adrianjgsmith

    Can't get Ultrawide resolution

    HDMI was my first go-to option, but I can't get over 1920x1080 with it. I have read of people with Macs unable to get beyond this down HDMI, but having success with DisplayPort. I've got a cable on order (along with a Dual Link DVI cable) so will see what that brings up when they arrive in the next day or so.
  8. adrianjgsmith

    Can't get Ultrawide resolution

    Thanks Allan. I tried it but just got black screen once it reached the login stage. What did you change, exactly? I've had a look at my cables and seen all my DVI cables are single link, so I'm sure that's not helping. I can get 2560x1080 over HDMI in windows, but I'm guessing that's not going to happen in OS X. I'll get hold of a Displayport cable and see if that changes anything.
  9. adrianjgsmith

    Can't get Ultrawide resolution

    I'm running a Radeon 6850, with Bulrushes framebuffer. I should also mention I can get the 2560x1080 resolution fine in Windows, just not Clover GUI or OS X.
  10. This evening I switched my pair of 1920x1080 monitors for a single LG Ultrawide 2560x1080. However I can't get this resolution selected in either the Clover GUI or OS X System Preferences (I'm running 10.9.5). System Preferences recognises the monitor as "LG Ultrawide" and in my boot.log there is a reference to "found detail timing 2560x1080" but I can't get higher than 1920x1080. Am I right in thinking that the EDID is being recognised correctly, but the VBIOS isn't providing the resolution? I've attached a boot log and my current config.plist. Help greatly appreciated! Config_Bootlog.zip
  11. adrianjgsmith

    Random reboots - USB kext conflict?

    Well, I removed GenericUSBXHCI.kext from EFI/CLOVER/kexts/10.9, tried some other kexts that didn't work went back to GenericUSBXHCI again for the hell of it, and.... the reboots have stopped. For the moment, at least. Whoever said the definition of madness was doing the same thing and expecting a different result?
  12. I've rebuilt my system lately, this time running Clover, and today's been the first stress testing day. I'm experiencing a lot of random reboots at the moment, and trying to get to the bottom of it. Things are running fine just now with a version of Chameleon (you know, the one we don't talk about here), but with Clover (r2482) I get about 10 minutes before black screen and an automatic restart. I'm running 10.9.1 on a Gigabyte Z77MX-D3H TH (rev 1.0 with F4 firmware) I've got a lot of drives plugged in at the moment: three USB 3.0 and one USB 2.0 connected to a an ORICO PFU-4P card; and one Firewire drive connected to the Thunderbolt port via an adapter. I'm wondering if this could be a kext conflict? I have a GenericUSBXHCI.kext in my EFI folder, but haven't taken anything out of System/Library/Extensions. I notice that the "last unloaded kext" always seems to be AppleUSBXHCI. Here's the crash log Mavericks generated,:
×