Jump to content


  • Content count

  • Joined

  • Last visited

About TheBloke

  • Rank
    InsanelyMac Geek

Profile Information

  • Gender
  • Location
    Brighton, UK

Recent Profile Visitors

597 profile views
  1. For me the forum seems reasonably OK, except whenever I see the word 'LOADING' - like when clicking another page of a thread - when it just stops completely and never returns. I use an adblocker, so adverts aren't slowing me down. Browsing the forum indexes is not too bad, as is clicking to view any thread. Ditto clicking a link in an email notification to go to a particular post in a thread. Sometimes it takes maybe five seconds to load a page, which is a bit too long. But it's not terrible. But then whenever I click on any other thread page, which tries to do the in-page content load (without a full page refresh), I see LOADING and then nothing further happens, even after minutes. It's definitely not related to which content is loaded, but rather how it is loaded. For example if I go to the index for this forum, then click directly to page 11 of this thread, it loads in 1-5 seconds. But if I click the link to page 11 within the thread, it never comes back. I just see this, forever: This stuck issue seems to me likely something broken (code or configuration?) rather than a general slowdown. But maybe there's also a general slowdown, especially for those who are seeing adverts.
  2. TheBloke

    (pre-release) macOS High Sierra 10.13.5

    Has anyone noticed anything different yet in 10.13.5 vs .4? I couldn't spot a single thing different in DP1. Haven't upgraded to DP2 yet. Are there any official notes published by Apple about what's meant to be different in these Developer Previews? I guess they only go to official members of the Beta programme, but maybe someone here is a member? Thanks
  3. TheBloke

    (pre-release) macOS High Sierra 10.13.5

    No problems installing on X58 Legacy with AMD 7970. Not noticed anything different or new yet, either. I'm hoping they're using this surprisingly quick new beta to fix the damage they did with implementing eGPU support. Since they did that in 10.13.4, all other external display types (eg via USB) have been broken. For example USB DisplayLink adapters no longer work, and nor does Duet - an app that enables using an iPad as another display via a USB-to-Lightning cable. I was using that, so am hoping this will be fixed soon.
  4. Yes, this is the last important missing feature in my view.
  5. Just to update to say I put in different PSU and added PCIe power adapters so I could use NVidia 760. Now HS 10.13.3 installed easily, and on this second machine I have working sleep/wake, working USB 2 & 3, working network, working graphics, working onboard audio and onboard SATA. Working, working, working Thanks so much for all your help and this amazing thread. Beer sent
  6. OK thanks. On my Radeon 7970 / R9 280X I found WEG fixed HDMI/DP audio in 10.13.4 - I don't get that OOB. But on DP5 and DP6 it also stopped me reaching login screen 75% of the time. No doubt there's some other way of fixing the audio, I haven't really tried to fix it yet as I have a USB soundcard. I don't really need it, just wondering.
  7. No problems upgrading on X58 legacy, pretty fast upgrade too. Can't really see anything different so far, although my GeekBench 4 Metal score was about 1% higher than I saw in earlier DPs. Within margin of error of course. Is WEG working again, do you know? It was broken for me in DP5 and DP6 (never reached login screen), but I haven't tried DP7 yet.
  8. I've stumbled into another period of remission.. this time lasting a couple of hours and still going. The MBP is currently performing exactly as it should, with no slowdown and sleep/wake/startup all fine. What changed? Well, I picked it up! Maybe it's just really lonely and needs to be held? Perhaps. Anyway, for the first time in a couple of days I picked it up off the desk and carried it with me to the other side of the room so I could copy down the serial number into a Clover config.plist I was creating on my Hack. With it still on my lap I started it up, and noticed it started immediately. Since that point it's been running fine. I'm pretty sure that the first time it worked (when I only got 30 minutes) I had also recently moved it around a bit. This could be coincidence, but it might suggest that the problem could trigger according to physical motion - maybe there's a damaged or loose solder connection that sometimes gets pushed into the right position when the laptop is moved about. That's potentially good news, as it might prove that there's a single cause to all the sensor failures. I don't know if I can repair a bad solder joint on tiny surface mount components, but it's not impossible. As long as it's not one of those ball-grid-array things, I'm pretty sure that's impossible to fix without the right equipment (reflow ovens and the like.) With it working I tried again the SMC reset, and that showed me that I had not managed to do that before. I had wondered if that might be the case - because it doesn't startup properly, it wasn't processing my holding Shift+Control+Option+Power. I know it worked this time because the light on the MagSafe connector changed colour after I did it. I don't hold out any hope that this SMC reset will actually fix things of course. It seems certain it must be a HW issue, and quite likely something like a loose connection or bad solder connection. Still, it hasn't failed again yet, despite my moving it about quite a bit, and even tapping all around the case to see if I could trigger it shutting down (and thus maybe roughly locate the position of the bad component.) LATER: OK after about four hours it reverted to the fail state. It didn't actually reboot, just the kernel CPU usage suddenly went sky high. It actually happened when I was away from the machine, so there wasn't any physical movement associated with it as far as I can tell. That somewhat contradicts my earlier thought of it being related to movement. It was running properly long enough for me to install some software - XCode, finally, so I can later DTrace to work out which kernel module is responsible for the high CPU 'safety measure'. And also iStat Menus which gives me some monitoring. And that now allows me to see the nature of the problem - all those sensors that report as failed in ASD are showing as their max values in iStat Menus. So something is pulling those sensor lines to the maximum. Going back to the Apple repair 'beginners guide' I mentioned, Louis Rossman says: Sometimes the data line on which the sensor is communicating is being brought down by something – dirt in a webcam connector, a bad webcam, a bad chip. Check if the line is topping out at the max spec'd voltage of that data line. I do see the sensors going to maximum. So there's still some hope it could be a simple fix, like dirt in a connector - that would also fit with it intermittently working. Or of course it could be a bad chip, which is likely to be much harder to repair. I miss the days of when chips were in sockets.. SLIGHTLY LATER AGAIN (last one tonight I promise): I wiggled the laptop around a lot and the CPU usage disappeared and those sensors changed values. Interestingly, they didn't all seem to revert to normal levels, but I guess they came down enough to be considered 'OK'. So movement definitely is important. This more strongly suggests bad connection or dirt than a bad chip - as does the fact that the movement lowered the value of the bad sensors, but not down to what (I think) is normal levels. Or it could still be a bad solder joint. Or even still a bad chip I guess, but hopefully less likely. This coming week I really do need to take it apart completely
  9. Yeah the X5670s are awesome - perfect balance of price and performance. They overclock really nicely too. I had an i7 930 originally and it took me far too long to realise I could replace it with a Xeon in this X58, but I'm really glad I finally did. I have two in my server as well. The thing that really surprised me about X58 is that the 24GB RAM 'limit' is untrue. It can take up to 48GB. I still don't understand why the mobo manufacturers never publicised that. Maybe Intel wouldn't let them support that config. I didn't know that about NVMe, that's interesting to know, thanks. Unfortunately I have no free PCIe slots so I wouldn't be able to add the necessary port. I put all my data on my server which has lots of disks and which I access over 2 x 10GB NICS, so that gives me pretty good performance.
  10. Yeah that is an option. She's actually already using Linux on her existing Asus laptop. I moved her from Windows a couple of years ago because the laptop only had 4GB RAM and it was pretty slow, and Ubuntu is much faster with limited resources. At the moment she literally only uses Chrome, she doesn't know the rest of the OS exists or even understands what it is. That was a reason I was hoping to get her on macOS - I think I can maybe finally get her to use a little more than just Chrome, because everything is both easy and smooth/polished on macOS. I thought I'd have Chrome always in Full Screen, then she can learn to use the three-finger-swipe left/right to go back and forth between Chrome and the Desktop, where maybe she'd at least use the Calendar and Notes and maybe Maps now and then. She uses her iPad and Android phone relatively well, so she's aware of the concept of apps and moving between them etc. I personally hate the macOS Dock, but for someone like my Mum it's a nice and friendly way to find and open apps, with very few 'sharp edges' on which she can get lost/confused. I especially wanted a MacBook for the multi-touch trakpad - I can definitely get her using two fingers to scroll up/down and go back/forward a page, etc, and probably zoom-in/out, rotate etc as well. Some of that works on Linux as well, but not as nicely, and it's too easy for her to get into a situation she doesn't understand on Linux - on Linux she'd have to stay Chrome-only. Anyway, worst case yeah I probably would leave her using Linux on the new MBP. Not having sleep is still a bit of a downer, but she never takes the laptop out of the house so she's never far from a charger, so hopefully I can just have her leave it on permanently and hope that screen sleep is enough to give a reasonable battery life. Still, I'm definitely going to take the thing apart and see if there's any chance of repairs. I like a challenge!
  11. Sadly not. A working replacement board can cost twice as much as I already paid for the laptop. I can't afford that. I either need to repair it, or else I'll re-sell it for hopefully at least the price I bought it - or hopefully a little more now I've fully diagnosed it and can advertise it better than the original seller. I re-ran the ASD this morning and this time it was four sensors instead of seven that showed up bad. So it's definitely variable, which may or may not be a good sign. At least I can be fairly sure it's unlikely there's anything wrong with the individual sensors, or the components they monitor. It's probably a data path or component that they all share. I'll likely spend the $29 to ask questions of the Louis Rossman group. There's also the iFixIt forums where people ask technical questions - and I'll be using their pictures to work out how to get the board out in the first place.
  12. Already did that and no luck. Also tried various different CSM options. OK don't worry, I will do more tests once I can boot OK with working graphics. Worst case I will just use Syba card. Thanks.
  13. D'oh! OK thanks. I also have a 760 but the PSU in this desktop does not have PCI-E power connectors. So I need to buy some molex->PCIe 6 & 8-pin adapters before I can use that GPU (or put in different PSU). So I will need to wait a couple of days before I can try boot again. Any thoughts on why SSD is not detected on the internal SATA? It is not big issue because Syba PCIe SATA card does work, but it would be nice not to need to use it. Thanks again.
  14. OK I know what's going on. First some general updates: EFI/SMC firmware: The EFI firmware wouldn't install, saying the installer was only for 10.8.5 and 10.9.5. I suppose this means it's definitely not required any more. The SMC firmware did install, but did not help; same symptoms. Boot with battery disconnected: no help, same symptoms. Safe mode: No high cpu usage. After boot, Activity Monitor shows 98% Idle, as it should be. Wake from sleep still does not work, no surprise as this is surely HW related. And of course Safe Mode is not really something that's going to be usable as a real solution. But yes, whatever kext it is that causes the 95+% System usage is not loaded in safe mode, and that might be helpful. Good call, @PPCnostalgic So then I ran ASD 3S148, and this tells me exactly what's wrong: I did some googling on some of these sensors, and found my way to a forum created by popular YouTube technican/iThings Fixer, Louis Rossman. He has a long "beginner's guide" to Apple fixing, which includes a couple of slides on sensors. One slide mentions: Running slow is often due to a sensor issue. Not slow as in slow hard drive, I mean slow as in the mouse stutters as it moves across the screen with no activity. The SMC likes to sense voltage levels, current usage, and temperatures from various different parts of the machine. If it receives information that is out of whack, it will turn the machine off, or make it run very slow as a means to protect itself from damage. This exactly describes my issue. So where to go from here? I suppose I will start investigations on whether I can possibly fix those sensors. There are so many of them that I hope there is one single cause. But looking at the rest of Louis' guide, most fixes are very technical. He's talking about checking things under a microscope at 45x, lots of oscilloscope probing, re-routing motherboard traces and all sorts. This is way above my level of electronis expertise (which is not hard as my level is very low.) I do actually have an oscilloscope, so I could give it a go. But I am not at all hopeful. What I can do is basic things like re-seating and cleaning connectors - he does mention that occasionally sensor failures can be caused by for example a bad webcam connection (because some sensors use the same data path as the webcam.) Alternatively/in parallel, I can investigate the path of just ignoring the issue. Clearly macOS has code to check the sensors and kill the system performance if irregularities are detected. This does not happen in Linux. So if I can find the kext that does it (assuming it is just one kext) and disable it, that could work. It won't fix sleep, but it might give a usable laptop. I'd love to post on Louis' forum but he charges $29/month to ask questions (since he started his YouTube he has been flooded with enquiries by other professonal fixers who want him to do their job for them.) $29 isn't so much to fix a MBP and maybe I will sign up. I just hesitate because there's a good chance they can't help me much without me needing to do complex electronics stuff. I guess tomorrow I wil take the MBP completely apart and see if I can find any easy fix like cleaning everything and disconnecting the webcam Thanks everyone for all your ideas and help!
  15. Another good thing to test, thanks a lot. It didn't occur to me that battery could affect things even with external power connected, but I guess it always goes through the battery even with power plugged in. I know the battery does hold charge for some time, but yes it could still have problems. Thanks again.