> The old one is moved to Xorg.0.log.old
I should have mentioned that I do not have xdm/gdm/kdm installed, so
if any log output was actually getting to the disk, it would still be
in Xorg.0.log after the reboot. Unfortunately, it looks like disk
caching (lazy-writing) is preventing the log output
On Mon, Oct 13, 2008 at 20:45:03 -0400, Graham wrote:
> > without at least a config and log file, we really cannot do anything...
>
> The config file is no problem. See attached.
>
> The log file, on the other hand, is not so simple. It seems to be lost
> when the reboot occurs; i.e. /var/log/Xo
> I will set up a null modem cable shortly, and see whether the kernel
> has anything to say about this.
Done; no messages from the kernel when the reboot occurs.
Is there a way to redirect the X server's log output to a serial port?
-- graham
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
wi
> without at least a config and log file, we really cannot do anything...
The config file is no problem. See attached.
The log file, on the other hand, is not so simple. It seems to be lost
when the reboot occurs; i.e. /var/log/Xorg.0.log contains log output
from the last time that X was started
Graham wrote:
> Package: xserver-xorg-video-nv
> Version: 1:2.1.10-1
>
> On a fresh Lenny installation, my system reboots almost immediately
> after X starts. Switching to the closed-source "nvidia" driver seems
> to solve the problem. I can reproduce this even by starting plain "X"
> from a termin
Package: xserver-xorg-video-nv
Version: 1:2.1.10-1
On a fresh Lenny installation, my system reboots almost immediately
after X starts. Switching to the closed-source "nvidia" driver seems
to solve the problem. I can reproduce this even by starting plain "X"
from a terminal. The hatched background
6 matches
Mail list logo