Yearly Umbongleton Comedy Swearing
Because awkwardness I've been running a Kumbongleton rig built from parts I found under the sofa where the ferrets had hidden them. It's been mostly working, and mostly working far better when given 8Gb of memory. And, since Umbongleton (they drink it in Congleton) the new-package-upgrade-reboot loop is about a week long.
Compare and contrast with XP which stayed up for months at a time.
Anyway.
Because it's bloody Umbongleton, the last set of updated packages seemed to cause the thing to crash after about half an hour. I left it running memtest86 while I was at work, which seemed to show that it wasn't a memory problem. However it was still expiring with a dead screen + keyboard.
Because it's been a full-on sort of a week, it took me a few days to realise that, actually, I could still ssh into the thing, but giving X a shoeing didn't do anything. Also, it would happily stay up if I kept working on the thing.
(The clever children will be waaay ahead of me by now..)
It transpires that Umbongleton (which they drink in Congleton) and ATI (or AMD or whoever) graphics drivers have had a nasty bug since 2012 which makes a bugger of the display power-management.
You can 'fix' it with some xset commands on startup, but really.
Compare and contrast with XP which stayed up for months at a time.
Anyway.
Because it's bloody Umbongleton, the last set of updated packages seemed to cause the thing to crash after about half an hour. I left it running memtest86 while I was at work, which seemed to show that it wasn't a memory problem. However it was still expiring with a dead screen + keyboard.
Because it's been a full-on sort of a week, it took me a few days to realise that, actually, I could still ssh into the thing, but giving X a shoeing didn't do anything. Also, it would happily stay up if I kept working on the thing.
(The clever children will be waaay ahead of me by now..)
It transpires that Umbongleton (which they drink in Congleton) and ATI (or AMD or whoever) graphics drivers have had a nasty bug since 2012 which makes a bugger of the display power-management.
You can 'fix' it with some xset commands on startup, but really.