> > The fact that drivers don't get fixed should be a big hint. The hint I get is that (a) not many developers know how to fix both (a1) drivers, and (a2) suspend or resume bugs; and that (b) even those which can do both suffer because of debuggability issues like $SUBJECT or, equivalently: > The main reason is the video problem (chips not coming back on resume > and needing a POST). This has always been the main issue and that's what > is causing STR not to work for a lot of people. Plus, related -- that ACPI is not generally debuggable. I've seen many systems come back well enough to produce new video output (text console), but fail almost immediately in what _seems_ to be ACPI codee. I tend to agree with Ben that the model is not the worst problem here. Not that it's perfect! - Dave