Bug#369167: DRI probably broken: where to reportbug
On Sun, Jun 04, 2006 at 05:33:04PM +0200, Wolfgang Pfeiffer wrote:
> On Tue, May 30, 2006 at 08:32:32AM +0200, Michel Dänzer wrote:
> > On Tue, 2006-05-30 at 01:57 +0200, Wolfgang Pfeiffer wrote:
> > > On Mon, May 29, 2006 at 09:53:39AM +0200, Michel Dänzer wrote:
> > > BTW: Is it possible to ssh into such a crashed system/machine and shut
> > > it down cleanly instead of stupidly pressing the power button I was
> > > doing so far after these crashes?
> > Depends how hard the crash is. Would be interesting to know at any rate.
> > [ ... ]
> It's possible :)
.. as long as I have this line in
As soon as I have that line in the file above:
I risk a complete crash, without the chance to shutdown the system via
SSH from a 2nd machine:
In one instance the machine was simply switched off, after trying to
start KDM (with 'ServerCmd=/usr/bin/X -br'), and on reboot date was
set to 1904, plus the login greeter on the console said it was 2004
(yes, 2004, IIRC).
So: no chance for the time coming to start /usr/bin/X on that
BTW: Is it necessary to reset PRAM/NVRAM after such a crash where the
time was reset to 1904? Or is it enough to simply run something like
ntpdate to set the time?
Wolfgang Pfeiffer: /ICQ: 286585973/ + + + /AIM: crashinglinux/
Key ID: E3037113