Hi,
we have some compact PCs with integrated i845G graphics. When running
the 4.3.0 server, it might lockup when switching VTs. A reliable way to
reproduce the behaviour is
# X :0
# xterm -display :0
# switch to X VT
in xterm:
# startkde
# switch back to inital vt while startkde is whacking
Hi,
On Fri, Apr 04, 2003 at 12:09:10PM +0200, Enrik Berkhan wrote:
A log is attached to
this mail.
Grmpf, never never never write this before actually attaching.
Sorry,
Enrik
200304041108.log.gz
Description: Binary data
smime.p7s
Enrik Berkhan [EMAIL PROTECTED] wrote:
we have some compact PCs with integrated i845G graphics.
Is it possible to get details on the hardware you use ? We're currently
rolling out some 'compact' PCs from MSI with the same chipset and I would
love to know what I have to fear _before_ it happens
I was under the impression that it wasn't. Certainly, the driver's
LeaveVT doesn't get called when exiting.
Mark.
On Fri, 4 Apr 2003, Frank Giessler wrote:
Hi,
Short question: is xf86VTSwitch() supposed to be called on server shutdown? The
lines
#ifdef
On Thu, 3 Apr 2003, Peter Gervais wrote:
Date: Thu, 03 Apr 2003 15:30:47 -0500
From: Peter Gervais [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
Content-Type: text/plain; charset=us-ascii; format=flowed
Subject: Re: Colormap Problems in Matrox G450 under FreeBSD 4.8
Thank
On Thu, 27 Mar 2003, Robert Woerle Paceblade/Support wrote:
who is maintaining the XRANR extension ???
i need contact since i want to enhance it
Keith Packard is.
--
Mike A. Harris
___
Devel mailing list
[EMAIL PROTECTED]
I'm a little confused about the status of the SiS drivers as described by
the release notes for = 4.2.99. It says:
Major SiS driver updates for some of the latest chipsets. Unfortunately
the SiS 3D driver has had to be disabled because no one has yet taken up
the challenge to port it to
DaemonSerj wrote (in a message from Saturday 5)
Hi!
I have a special pointer-type device and need to implement
functionality like mouse.
Its work through COM port ,but it have own internal
protocol and specific hardware.
How to start?
Write a new input driver for your device.
