[NBLUG/talk] X11, Xinerama, and Kernel Updates -dual monitors and redhat

[Dave Rohling]

Couldn't find much useful. Keep in mind, this is after I booted to the
working kernel. I looked at it mefore and found nothing either. There's
arent my resolutions, so I assume it used other resolutions.

grep WW /var/log/XFree86.0.log

/var/log/XFree86.0.log:         (WW) warning, (EE) error, (NI) not
implemented, (??) unknown.
/var/log/XFree86.0.log:(WW) (1400x1050,Monitor0) mode clock 122MHz exceeds
DDC maximum 110MHz
/var/log/XFree86.0.log:(WW) NVIDIA(1): Not using mode "576x384":
/var/log/XFree86.0.log:(WW) NVIDIA(1):   horizontal sync start (589) not a
multiple of 8
/var/log/XFree86.0.log:(WW) NVIDIA(1): Not using mode "360x200":
/var/log/XFree86.0.log:(WW) NVIDIA(1):   horizontal sync start (378) not a
multiple of 8
/var/log/XFree86.0.log:(WW) NVIDIA(1): OpenGL is not fully supported in
Xinerama
/var/log/XFree86.0.log:(WW) I810(0): xf86AllocateGARTMemory: allocation of
1024 pages failed
/var/log/XFree86.0.log:(WW) NVIDIA(1): Failed to verify AGP usage
/var/log/XFree86.1.log:         (WW) warning, (EE) error, (NI) not
implemented, (??) unknown.
/var/log/XFree86.1.log:(WW) (1400x1050,Monitor0) mode clock 122MHz exceeds
DDC maximum 110MHz
/var/log/XFree86.1.log:(WW) I810(0): xf86AllocateGARTMemory: allocation of
1024 pages failed

grep EE /var/log/XFree86.0.log
         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(II) Loading extension MIT-SCREEN-SAVER
(--) NVIDIA(1): MMIO registers at 0xEE000000

- Dave 

-----Original Message-----
From: talk-admin at nblug.org [mailto:talk-admin at nblug.org] On Behalf Of troy
Sent: Tuesday, August 12, 2003 12:22 PM
To: talk at nblug.org
Subject: Re: [NBLUG/talk] X11, Xinerama, and Kernel Updates -dual monitors
and redhat


On Tue, Aug 12, 2003 at 11:41:53AM -0700, Dave Rohling wrote:
> When I ran the up2date on my Redhat 9.0 box, which was properly 
> configured for dual monitors, the update broke my dual monitor 
> configuration. My video driver and XF86Config file are still there, 
> and when I boot into the previous kernel, it works. Any idea what 
> could have changed? Does this mean it is something in the Kernel 
> itself?

Take a look at /var/log/XFree86*log
I find it easier to look at this big file with grep:
	grep WW /var/log/XFree86.0.log
will show you warnings, while
	grep EE /var/log/XFree86.0.log
will show you errors.

Your log might be named slightly differently.

If you don't spot anything useful yourself, post the output of the above
command to the list.

-troy



_______________________________________________
talk mailing list
talk at nblug.org
http://nblug.org/mailman/listinfo/talk