On Mon, Sep 13, 2004 at 12:51:30PM -0500, Branden Robinson wrote: > On Tue, Aug 31, 2004 at 08:13:23PM -0700, Daniel Stone wrote: > > On Tue, Aug 31, 2004 at 02:32:49PM -0500, Branden Robinson wrote: > > > My only concern about that approach is we'd better be damn sure starting X > > > doesn't lock up people's machines, especially on our more exotic > > > architectures. discover and mdetect don't, and read-edid only seems to > > > hurt x86 users with buggy hardware. > > > > If you have an i855 or such, try running 'X :1 -probeonly -ac' some day, > > when you have an X session already running. > > I don't own any x86 hardware and do not have access to a box with this > chipset. > > Please describe what happens when this is done.
Your current X session dies, and there's a kernel message from the DRM module about how it tried to allocate 64MB of ram and only got 58, or such. Doing a simple DDC probe doesn't seem to do any damage. -- Daniel Stone <[EMAIL PROTECTED]> Debian: the universal operating system http://www.debian.org
signature.asc
Description: Digital signature
