Apple 30" Monitor

Les hlhowell at pacbell.net
Tue Jun 26 02:38:26 UTC 2007


On Mon, 2007-06-25 at 20:00 -0400, Michael J. McGillick wrote:
> Konstantin:
> 
> I played around with the Fonts applet as you suggested, but no real
> difference. It did clean them up a tiny bit in the current resolution,
> but as soon as I switched to a resolution like 1920x1200, it was
> unreadably fuzzy.
> 
> I also did as you suggested of placing the Modes line in my Display
> section, but no change after I restarted X.
> 
> I also looked at /var/log/Xorg.0.log and saw:
> 
> (II) VESA(0): Manufacturer: APP  Model: 9232  Serial#: 33584150
> (II) VESA(0): Year: 2006  Week: 32
> (II) VESA(0): EDID Version: 1.3
> (II) VESA(0): Digital Display Input
> (II) VESA(0): Max H-Image Size [cm]: horiz.: 64  vert.: 40
> (II) VESA(0): Gamma: 2.20
> (II) VESA(0): DPMS capabilities: Off; RGB/Color Display
> (II) VESA(0): First detailed timing not preferred mode in violation of
> standard!(II) VESA(0): redX: 0.640 redY: 0.343   greenX: 0.292 greenY:
> 0.611
> (II) VESA(0): blueX: 0.146 blueY: 0.074   whiteX: 0.313 whiteY: 0.331
> (II) VESA(0): Manufacturer's mask: 0
> (II) VESA(0): Supported additional Video Mode:
> (II) VESA(0): clock: 71.0 MHz   Image Size:  641 x 401 mm
> (II) VESA(0): h_active: 1280  h_sync: 1328  h_sync_end 1360 h_blank_end
> 1440 h_border: 0
> (II) VESA(0): v_active: 800  v_sync: 803  v_sync_end 809 v_blanking: 823
> v_border: 0
> (II) VESA(0): Supported additional Video Mode:
> (II) VESA(0): clock: 268.0 MHz   Image Size:  641 x 401 mm
> (II) VESA(0): h_active: 2560  h_sync: 2608  h_sync_end 2640 h_blank_end
> 2720 h_border: 0
> (II) VESA(0): v_active: 1600  v_sync: 1603  v_sync_end 1609 v_blanking:
> 1646 v_border: 0
> (II) VESA(0): Serial No: CY6321VNUG1
> (II) VESA(0): Monitor name: Cinema HD
> (II) VESA(0): Number of EDID sections to follow: 1
> (II) VESA(0): EDID (in hex):
> (II) VESA(0):   00ffffffffffff000610329216740002
> (II) VESA(0):   201001038040287828fe87a3574a9c25
> (II) VESA(0):   13505400000001010101010101010101
> (II) VESA(0):   010101010101bc1b00a0502017303020
> (II) VESA(0):   360081912100001ab06800a0a0402e60
> (II) VESA(0):   3020360081912100001a000000ff0043
> (II) VESA(0):   5936333231564e5547310a00000000fc
> (II) VESA(0):   0043696e656d612048440a00000001b7
> (II) VESA(0): Printing DDC gathered Modelines:
> (II) VESA(0): Modeline "1280x800"   71.00  1280 1328 1360 1440  800 803
> 809 823 -hsync +vsync
> (II) VESA(0): Modeline "2560x1600"  268.00  2560 2608 2640 2720  1600
> 1603 1609 1646 -hsync +vsync
> 
> And then much further down the file:
> 
> (II) VESA(0): Total Memory: 256 64KB banks (16384kB)
> (II) VESA(0): <default monitor>: Using hsync range of 49.31-98.53 kHz
> (II) VESA(0): <default monitor>: Using vrefresh range of 59.86-59.91 Hz
> (II) VESA(0): Not using mode "2560x1600" (no mode of this name)
> (II) VESA(0): Not using built-in mode "1920x1440" (no mode of this name)
> (II) VESA(0): Not using built-in mode "1856x1392" (no mode of this name)
> (II) VESA(0): Not using built-in mode "1600x1200" (no mode of this name)
> (II) VESA(0): Not using built-in mode "1400x1050" (no mode of this name)
> (II) VESA(0): Not using built-in mode "1280x1024" (no mode of this name)
> (II) VESA(0): Not using built-in mode "1280x1024" (no mode of this name)
> (II) VESA(0): Not using built-in mode "1280x1024" (no mode of this name)
> (II) VESA(0): Not using built-in mode "1152x864" (no mode of this name)
> (II) VESA(0): Not using built-in mode "1024x768" (no mode of this name)
> (II) VESA(0): Not using built-in mode "1024x768" (no mode of this name)
> (II) VESA(0): Not using built-in mode "800x600" (no mode of this name)
> (II) VESA(0): Not using built-in mode "800x600" (no mode of this name)
> (II) VESA(0): Not using built-in mode "640x480" (no mode of this name)
> (II) VESA(0): Not using built-in mode "640x480" (no mode of this name)
> (II) VESA(0): Not using built-in mode "720x400" (no mode of this name)
> (II) VESA(0): Not using built-in mode "640x400" (no mode of this name)
> (II) VESA(0): Not using built-in mode "640x400" (no mode of this name)
> (II) VESA(0): Not using built-in mode "640x350" (no mode of this name)
> (II) VESA(0): Not using built-in mode "512x384" (no mode of this name)
> (II) VESA(0): Not using built-in mode "320x240" (no mode of this name)
> (II) VESA(0): Not using built-in mode "320x200" (no mode of this name)
> (II) VESA(0): Not using built-in mode "320x200" (no mode of this name)
> (WW) VESA(0): No valid modes left.  Trying less strict filter...
> (II) VESA(0): <default monitor>: Using hsync range of 49.31-98.53 kHz
> (II) VESA(0): <default monitor>: Using vrefresh range of 59.86-59.91 Hz
> (II) VESA(0): Not using mode "2560x1600" (no mode of this name)
> (II) VESA(0): Not using built-in mode "1024x768" (hsync out of range)
> (II) VESA(0): Not using built-in mode "1024x768" (hsync out of range)
> (II) VESA(0): Not using built-in mode "800x600" (hsync out of range)
> (II) VESA(0): Not using built-in mode "800x600" (hsync out of range)
> (II) VESA(0): Not using built-in mode "640x480" (hsync out of range)
> (II) VESA(0): Not using built-in mode "640x480" (hsync out of range)
> (II) VESA(0): Not using built-in mode "720x400" (hsync out of range)
> (II) VESA(0): Not using built-in mode "640x400" (hsync out of range)
> (II) VESA(0): Not using built-in mode "640x400" (no mode of this name)
> (II) VESA(0): Not using built-in mode "640x350" (no mode of this name)
> (II) VESA(0): Not using built-in mode "512x384" (no mode of this name)
> (II) VESA(0): Not using built-in mode "320x240" (no mode of this name)
> (II) VESA(0): Not using built-in mode "320x200" (no mode of this name)
> (II) VESA(0): Not using built-in mode "320x200" (no mode of this name)
> (WW) VESA(0): No valid modes left.  Trying less strict filter...
> (II) VESA(0): <default monitor>: Using hsync range of 49.31-98.53 kHz
> (II) VESA(0): <default monitor>: Using vrefresh range of 59.86-59.91 Hz
> (II) VESA(0): Not using mode "2560x1600" (no mode of this name)
> (II) VESA(0): Not using built-in mode "1024x768" (hsync out of range)
> (II) VESA(0): Not using built-in mode "1024x768" (hsync out of range)
> (II) VESA(0): Not using built-in mode "800x600" (hsync out of range)
> (II) VESA(0): Not using built-in mode "800x600" (hsync out of range)
> (II) VESA(0): Not using built-in mode "640x480" (hsync out of range)
> (II) VESA(0): Not using built-in mode "640x480" (hsync out of range)
> (II) VESA(0): Not using built-in mode "720x400" (hsync out of range)
> (II) VESA(0): Not using built-in mode "640x400" (hsync out of range)
> (II) VESA(0): Not using built-in mode "640x400" (hsync out of range)
> (II) VESA(0): Not using built-in mode "640x350" (hsync out of range)
> (II) VESA(0): Not using built-in mode "512x384" (hsync out of range)
> (II) VESA(0): Not using built-in mode "320x240" (hsync out of range)
> (II) VESA(0): Not using built-in mode "320x200" (hsync out of range)
> (II) VESA(0): Not using built-in mode "320x200" (hsync out of range)
> (--) VESA(0): Virtual size is 1920x1440 (pitch 1920)
> (**) VESA(0):  Built-in mode "1920x1440"
> (**) VESA(0):  Built-in mode "1856x1392"
> (**) VESA(0):  Built-in mode "1600x1200"
> (**) VESA(0):  Built-in mode "1400x1050"
> (**) VESA(0):  Built-in mode "1280x1024"
> (**) VESA(0):  Built-in mode "1280x1024"
> (**) VESA(0):  Built-in mode "1280x1024"
> (**) VESA(0):  Built-in mode "1152x864"
> (**) VESA(0): Display dimensions: (640, 400) mm
> (**) VESA(0): DPI set to (76, 91)
> 
> Not sure if this points to an issue or not.
> 
> - Michael
> 
> 
> 
> 
> On Mon, 2007-06-25 at 16:23 -0700, Konstantin Svist wrote:
> > Not sure about the actual resolution, but as far as fuzzy fonts go, you 
> > should change anti-aliasing setting.
> > In Control Center go to Appearance & Themes -> Fonts. There's a 
> > Configure button next to "Use anti-aliasing for fonts". Play around with 
> > those settings and see which one works better for you. My favorite is 
> > Use sub-pixel hinting RGB and Hinting style set at Full.
> > Note that only newly-launched applications will use these settings.
> > Also, I'm using FC6 with KDE, so apologies if you don't have the applet 
> > in the same place.
> > 
> > 
> > 
> > As far as resolution, have you tried adding your resolution to Display 
> > subsection like so:
> > 
> >           SubSection "Display"
> >                   Viewport   0 0
> >                   Depth     24
> >                   Modes     "2560x1600"
> >           EndSubSection
> > 
> > 
> > 
> > 
> > 
> > 
> > Michael J. McGillick wrote:
> > > Hi:
> > > 
> > > I'm running Fedora 7 on a Mac Pro with an ATI Radeon X1900 XT and an Apple
> > > 30" HD Cinema LCD monitor. I've been doing a lot of reading on how to
> > > properly set up my xorg.conf file, however, I've not been able to get very
> > > far. I'd appreciate any help, or pointers in the right direction.
> > > 
> > > The problems I'm having are:
> > > 
> > >  - The highest resolution that the I can set through System > Administration
> > >> Display is 1920 x 1440 (This monitor supports 2560x1600).
> > > 
> > >  - In all resolutions, the font is incredibly fuzzy. I have to leave the
> > > monitor set at 1280x1024, as any higher resolution and the text is
> > > unreadable.
> > > 
> > >  - The background graphics and images are also fuzzy.
> > > 
> > > 
> > > To date, here is what I've done:
> > > 
> > >  - Installed Fedora - In the Gnome desktop, if I go to System >
> > > Administration > Display, on the Hardware tab, I'm told that the monitor
> > > type is Cinema HD (autoconfigured) and the Video Card is ATI Technologies
> > > Inc R580 [Radeon X1900 XT] (Primary). This leads me to believe that the
> > > Fedora installer recognized my hardware.
> > > 
> > >  - Examined xorg.conf - If I look in xorg.conf, I see a listing for vesa
> > > instead of the Radeon driver. I did some reading and apparently there is a
> > > problem with the current 8.37.6 version of the ATI driver in that it
> > > segfaults the X server. (Please correct me if my understanding is wrong)
> > > 
> > >  - Followed several different threads that talk about similar problems to
> > > mine, but never a solution posted. In many cases, the user had the same
> > > graphics card as mine, but not the same monitor.
> > > 
> > >  - Researched how to configure an LCD monitor in xorg.conf only to learn
> > > that most LCD monitors do not have a refresh rate in the traditional sense,
> > > and so you can leave the entire monitor section out of xorg.conf.
> > > Apparently it gets detected automatically.
> > > 
> > > I'm a new user and would really like to be able to get up and running.
> > > As with any new user, I'm frustrated that I haven't been able to figure it
> > > out on my own. At this point, I'm not sure what I'm doing wrong, and could
> > > really use some help.
> > > 
> > > The xorg.conf that got created was:
> > > 
> > > # Xorg configuration created by system-config-display
> > > 
> > > Section "ServerLayout"
> > >         Identifier     "single head configuration"
> > >         Screen      0  "Screen0" 0 0
> > >         InputDevice    "Keyboard0" "CoreKeyboard"
> > > EndSection
> > > 
> > > Section "InputDevice"
> > >         Identifier  "Keyboard0"
> > >         Driver      "kbd"
> > >         Option      "XkbModel" "pc105"
> > >         Option      "XkbLayout" "us"
> > > EndSection
> > > 
> > > Section "Device"
> > >         Identifier  "Videocard0"
> > >         Driver      "vesa"
> > > EndSection
> > > 
> > > Section "Screen"
> > >         Identifier "Screen0"
> > >         Device     "Videocard0"
> > >         DefaultDepth     24
> > >         SubSection "Display"
> > >                 Viewport   0 0
> > >                 Depth     24
> > >         EndSubSection
> > > EndSection
> > > 
> > > Any help or guidance would be greatly appreciated. Thanks.
> > > 
> > > - Michael
> > > 
> > > 
> > 
> 
I am not familiar with the hardware interface on this monitor, but if
possible do not use the analog cable type connection.  It is probably
too low a bandwidth for this many pixels.  Digital will go to much
higher resolutions.

Regards,
Les H




More information about the fedora-list mailing list