>> I was running -current (dated some days before Christmas 2010, maybe 24th) >> on my aspire one A110, and running smooth. >> I decided, having one month passed to upgrade to latest -current, which is >> now 4.9 (dated 20 Jan).
Every boot? > [...] > > Built-in keyboard support on the Aspire One is known to be broken, but > this is the first time I hear that it has been working at all at some > point. A110 may of course be totally different, but Aspire One A150 (a.k.a. ZG5) works most of the time. Sometimes (for me, maybe one boot out of ten or twenty), it fails with "pmsattach: disable error" logged, when that happens I hold the power button to force it to power down, and it's almost always OK next boot. There was a time when it happened more often, but it's rare enough not to be too annoying nowadays.
