←back to thread

361 points robenkleene | 1 comments | | HN request time: 0s | source
Show context
mokus ◴[] No.23283932[source]
I guess the list of things keeping me off catalina (and, by extension, new Mac hardware) just got one item longer.

I recently bought a new System76 laptop as a stopgap, but it might end up becoming permanent. Kind of a sad end for 25+ years of Mac use.

replies(10): >>23284197 #>>23284366 #>>23284643 #>>23284871 #>>23285038 #>>23285254 #>>23285313 #>>23285345 #>>23285555 #>>23286897 #
rayiner ◴[] No.23284643[source]
My 16” is a huge disappointment. After swearing off Intel PCs after a disaster ours X1 Carbon, I switched back to a 2013 15” until this month. Figured after six months bugs would be ironed out. Wrong. I’m seeing two major glitches that have macrumors threads dozens of pages long: 1) with an external display connected, dGPU utilization shoots up to 20W at idle. (The rest of machine draws well under 10W at idle.) That wouldn’t be a big deal if the CPU and GPU didn’t share a tight 70W power budget. 2) when connected to an external monitor or dock—I’ve tried two different TB3 docks—the machine kernel panics regularly, usually waking up from sleep.

I’m torn. I don’t want to return the machine because everything else is crap. At least the 16” works well as a laptop so long as you don’t plug anything into the ports. But Apple’s Q&A has seriously gone down the toilet ever since Steve Jobs died. Clearly him throwing staplers at people was the glue holding Apple together.

replies(5): >>23284696 #>>23284992 #>>23285033 #>>23286942 #>>23288233 #
1. reaperducer ◴[] No.23284696[source]
when connected to an external monitor or dock—I’ve tried two different TB3 docks—the machine kernel panics regularly, usually waking up from sleep.

I had a similar problem, and it turned out that the dock needed a driver. I don't think I've installed a driver for an external device since I switched to Macs years ago, so it never occurred to me that something like a dock would need a driver.

But it turns out that once I installed the vendor's driver, the problems all went away. I'm not sure who's fault that is.