On 9:53 am 09/18/06 Craig FALCONER <[EMAIL PROTECTED]> wrote: > It's a cheap KVM. > > What its doing is not passing the DDC info from the monitor to the > PC, so the PC is starting up in some lower resolution or refresh. > Exactly how that impacts on fonts I'm not sure, but likely your font > manager is making a decision based on the refresh/resolution that X > is running in. >
It is definitely running at the same resolution, but the refresh rate might be different. Here is the diff between the log from an earlier session and one with the KVM. It certainly supports that the EDID info is not being read. > (WW) NVIDIA(0): Unable to read EDID for display device CRT-0 327,328c324,325 < (--) NVIDIA(0): AOC LM726 (CRT-0) < (--) NVIDIA(0): AOC LM726 (CRT-0): 350.0 MHz maximum pixel clock --- > (--) NVIDIA(0): CRT-0 > (--) NVIDIA(0): CRT-0: 350.0 MHz maximum pixel clock 333c330,332 < (--) NVIDIA(0): DPI set to (95, 96); computed from "UseEdidDpi" X config option --- > (WW) NVIDIA(0): Unable to get display device CRT-0's EDID; cannot compute > DPI > (WW) NVIDIA(0): from EDID. > (==) NVIDIA(0): DPI set to (75, 75); computed from built-in default 422a422 > (II) 3rd Button detected: disabling emulate3Button Maybe I need to se something to force 96 (or 100) DPI as it looks like that may be the cause. Any quick ideas on how I do that? > Good luck! I have ~20 spare CRTs if you want some. I have some too, but I don't have room on my desk at home. Never mind, most of what i do on the desktop involves firefox and a scroll mouse makes it easy to enlarge the fonts. Once I get an OS installed on the headless box I will ditch the KVM.
