On Thu, Feb 3, 2011 at 5:40 PM, Stuart Henderson <s...@spacehopper.org>wrote:
> >> 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. Actually with 4.8 -current it happened 5-10% of times. With 4.9 -current it happened all the times but once: yesterday :))))) Today I did the hardware job and till now it's working. What compelled me to do it, besides the previous answer, was that yesterday , for the first time, it did the same mess also in linux :O So, up to now, the drama is back to normality ;) Btw, I must have seen (but two or three months ago) that "pmsattach" error as well. Happened when typed keys got repeated by themselves till some further different keypress took place. Looks like that this is a double layer problem: problematic emulation on top of poor hardware ;) My personal advice is to deoxydate keyboard contacts for all those who have problems before further analysis.
