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

Translation

(itstool) path: sect2/para
English
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:
0/3280 · 328
Context English Persian State
<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.
When I run the command to start <application>Compiz Fusion</application>, the X server crashes and I am back at the console. What is wrong?
If you check <filename>/var/log/Xorg.0.log</filename>, you will probably find error messages during the X startup. The most common would be:
(EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X
(EE) NVIDIA(0): log file that the GLX module has been loaded in your X
(EE) NVIDIA(0): server, and that the module is the NVIDIA GLX module. If
(EE) NVIDIA(0): you continue to encounter problems, Please try
(EE) NVIDIA(0): reinstalling the NVIDIA driver.
This is usually the case when you upgrade <application>Xorg</application>. You will need to reinstall the <package>x11/nvidia-driver</package> package so glx is built again.
Common Tasks
Now that the basics have been covered, this part of the book discusses some frequently used features of FreeBSD. These chapters:

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: sect2/para
Source string location
book.translate.xml:13092
String age
11 months ago
Source string age
a year ago
Translation file
books/fa/handbook.po, string 2245