The translation is temporarily closed for contributions due to maintenance, please come back later.

Translation

(itstool) path: listitem/para
English
1680x1050
Context English Persian State
Finally, write the configuration file and test it using the test mode given above.
One of the tools available to assist you during troubleshooting process are the <application>Xorg</application> log files, which contain information on each device that the <application>Xorg</application> server attaches to. <application>Xorg</application> log file names are in the format of <filename>/var/log/Xorg.0.log</filename>. The exact name of the log can vary from <filename>Xorg.0.log</filename> to <filename>Xorg.8.log</filename> and so forth.
If all is well, the configuration file needs to be installed in a common location where <citerefentry vendor="xorg"><refentrytitle>Xorg</refentrytitle><manvolnum>1</manvolnum></citerefentry> can find it. This is typically <filename>/etc/X11/xorg.conf</filename> or <filename>/usr/local/etc/X11/xorg.conf</filename>.
<prompt>#</prompt> <userinput>cp xorg.conf.new /etc/X11/xorg.conf</userinput>
The <application>Xorg</application> configuration process is now complete. <application>Xorg</application> may be now started with the <citerefentry vendor="xfree86"><refentrytitle>startx</refentrytitle><manvolnum>1</manvolnum></citerefentry> utility. The <application>Xorg</application> server may also be started with the use of <citerefentry vendor="xfree86"><refentrytitle>xdm</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
Configuration with <trademark class="registered">Intel</trademark> <literal>i810</literal> Graphics Chipsets
<primary><trademark class="registered">Intel</trademark> i810 graphic chipset</primary> اصول پایه <trademark class="registered">UNIX</trademark> را آموزش می‌دهند.
Configuration with <trademark class="registered">Intel</trademark> i810 integrated chipsets requires the <filename>agpgart</filename> AGP programming interface for <application>Xorg</application> to drive the card. See the <citerefentry><refentrytitle>agp</refentrytitle><manvolnum>4</manvolnum></citerefentry> driver manual page for more information.
This will allow configuration of the hardware as any other graphics board. Note on systems without the <citerefentry><refentrytitle>agp</refentrytitle><manvolnum>4</manvolnum></citerefentry> driver compiled in the kernel, trying to load the module with <citerefentry><refentrytitle>kldload</refentrytitle><manvolnum>8</manvolnum></citerefentry> will not work. This driver has to be in the kernel at boot time through being compiled in or using <filename>/boot/loader.conf</filename>.
Adding a Widescreen Flatpanel to the Mix
<primary>widescreen flatpanel configuration</primary>
This section assumes a bit of advanced configuration knowledge. If attempts to use the standard configuration tools above have not resulted in a working configuration, there is information enough in the log files to be of use in getting the setup working. Use of a text editor will be necessary.
Current widescreen (WSXGA, WSXGA+, WUXGA, WXGA, WXGA+, et.al.) formats support 16:10 and 10:9 formats or aspect ratios that can be problematic. Examples of some common screen resolutions for 16:10 aspect ratios are:
2560x1600
1920x1200
1680x1050
1440x900
1280x800
At some point, it will be as easy as adding one of these resolutions as a possible <literal>Mode</literal> in the <literal>Section "Screen"</literal> as such:
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1680x1050"
EndSubSection
EndSection
<application>Xorg</application> is smart enough to pull the resolution information from the widescreen via I2C/DDC information so it knows what the monitor can handle as far as frequencies and resolutions.
If those <literal>ModeLines</literal> do not exist in the drivers, one might need to give <application>Xorg</application> a little hint. Using <filename>/var/log/Xorg.0.log</filename> one can extract enough information to manually create a <literal>ModeLine</literal> that will work. Simply look for information resembling this:
(II) MGA(0): Supported additional Video Mode:
(II) MGA(0): clock: 146.2 MHz Image Size: 433 x 271 mm
(II) MGA(0): h_active: 1680 h_sync: 1784 h_sync_end 1960 h_blank_end 2240 h_border: 0
(II) MGA(0): v_active: 1050 v_sync: 1053 v_sync_end 1059 v_blanking: 1089 v_border: 0
(II) MGA(0): Ranges: V min: 48 V max: 85 Hz, H min: 30 H max: 94 kHz, PixClock max 170 MHz
This information is called EDID information. Creating a <literal>ModeLine</literal> from this is just a matter of putting the numbers in the correct order:
ModeLine &lt;name&gt; &lt;clock&gt; &lt;4 horiz. timings&gt; &lt;4 vert. timings&gt;
So that the <literal>ModeLine</literal> in <literal>Section "Monitor"</literal> for this example would look like this:
Section "Monitor"
Identifier "Monitor1"
VendorName "Bigname"
ModelName "BestModel"
ModeLine "1680x1050" 146.2 1680 1784 1960 2240 1050 1053 1059 1089
Option "DPMS"
EndSection
Now having completed these simple editing steps, X should start on your new widescreen monitor.
Troubleshooting Compiz Fusion
I have installed <application>Compiz Fusion</application>, and after running the commands you mention, my windows are left without title bars and buttons. What is wrong?
You are probably missing a setting in <filename>/etc/X11/xorg.conf</filename>. Review this file carefully and check especially the <literal>DefaultDepth</literal> and <literal>AddARGBGLXVisuals</literal> directives.

Loading…

No matching activity found.

Browse all component changes

Glossary

English Persian
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: listitem/para
Source string location
book.translate.xml:13059
String age
11 months ago
Source string age
a year ago
Translation file
books/fa/handbook.po, string 2239