The first is that hwclock could not be accessed with any known method (error -22) and so the year was in the beginning on 19xx. This caused secondary errors later.That sounds like a kernel issue again. Would you agree with that?
Yes.
I've seen this mentioned before. IMO it is an important issue. Could you please check if this is resolved or still present in the version of X currently in unstable? This should be possible by installing in expert mode using a businesscard image and selecting "unstable" during mirror selection.
OK, will try when I go there. -- Meelis Roos (mroos@ut.ee) http://www.cs.ut.ee/~mroos/