Brice,
I installed the xorg packages from unstable as you suggested.
Actually I had to purge the old ones first as there was a weird problem
with fonts (Display was fine but no chars showed anywhere)
Problem still exists.
Display switching between X and console also still broken, but that's ano
Brice,
I installed the xorg packages from unstable as you suggested.
Actually I had to purge the old ones first as there was a weird problem
with fonts (Display was fine but no chars showed anywhere)
Problem still exists.
Display switching between X and console also still broken, but that's ano
Re:I forgot to mention that using the display background it stretched
suggesting that X and/or KDE thinks that the second display is working
correctly. The monitor twitches when X starts but then looses sync.
xorg.conf
--
Section "ServerLayout"
Identifier "Default Layout"
that this is a problem in 2.6.20 kernel?
>
> Regards,
>
> // Ola
>
> On Fri, Aug 03, 2007 at 10:33:53AM +0100, Jan H Eringa wrote:
> > Hiya guys,
> >
> > I've just run vserver-stat on the machine under the 2.6.18 vserver kernel
> > vserver-stat
> &
Package: util-vserver
Version: 0.30.213-1
Severity: important
Use of /etc/vservers//sched/ causes vsched to blow up
|my-server# vsched --xid 4 --dir /etc/vservers/test-1/sched
|vsched: readdir(): Bad address
Which I suspect is the cause of
|my-server# /etc/init.d/util-vserver start
|
Package: util-vserver
Version: 0.30.213-1
Severity: important
-snip-
my-server# vserver-stat
CTX PROCVSZRSS userTIME sysTIMEUPTIME NAME
my-server#
-snip-
Even though two vservers are running.
my-server# ls -al /proc/virtual/
total 0
dr-xr-xr-x 4
Package: syslog-ng
Version: 1.9.11-1
Hey guys,
The problems is that this machine is being fed logs from various remote
sources.
One source in particular a firewall is generating a fairly large amount of
syslog traffic but nothing unusual (a couple of other firewalls seem to
generate the same
Guys,
I've managed to fix the problem!
It seems that the i8k kernel module was the culprit
The kernel rev is 2.6.12. I just renamed the i8k kernel module out of the way
and the problem dissapeared.
Should I open a new bug against the kernel package I used?
Or will someone your end talk to the ker
8 matches
Mail list logo