Re: What part of X causes major display problems?

["Seneca Cunningham" <seneca@slemish.com>]

ben <benfoley@rcn.com> wrote:
> On Sunday 13 January 2002 02:11 pm, Seneca Cunningham wrote:
> [snip]
> >
> > > "X -configure" is...
> > >
> > > 	(==) CHIPS(0): Min pixel clock is  11.000MHz
> > > 	(--) CHIPS(0): Max pixel clock is  56.000MHz
> > >
> > > ... and from the "xf86cfg -textmode" method...
> > >
> > > 	(==) CHIPS(0): Min pixel clock is   5.500MHz
> > > 	(--) CHIPS(0): Max pixel clock is  28.000MHz
> > >
> i don't have a solution but have you noticed that the x-configure values
are
> exactly double the textmode values. i have no idea why this is but i
thought
> it might be useful to point that out.

And each of range includes, or almost includes, the working clocks value
from my old X3 config of 28.32. And both config files had to have a modeline
manually entered before I could get anything to appear, other than an error
message. The X3 xf86config program says _not_ to probe clocks, but X4 looks
like it is probing clocks.

> btw, are you running a 2.2 kernel? i couldn't get x4 to run on 2.2, and
went

I am running a 2.4 kernel.

> with the 2.4 kernels for that reason. don't know exactly why--i was more
> interested in the functionality than the detective work.

Detective work is how I survive computer science while forgetting to hand
anything in... I get some credit for testfiles that crash the same number of
(or sometimes more) programs than the teacher's (most of the caught problems
are null pointers), while my programs run unscathed.

Thanks for any help,

Seneca
seneca@slemish.com