FreeBSD Doc/books_handbook — Persian @ Weblate: <primary><trademark class="registered">Intel</trademark> i810 graphic chipset</primary>

Translation

Content

Source change

~~Teach~~ <primary><trademark class="registered">~~UNIX~~Intel</trademark> ~~basics and fundamentals.~~i810 graphic chipset</primary>

Source string comment (itstool) path: sect2/indexterm

English

<primary><trademark class="registered">Intel</trademark> i810 graphic chipset</primary>

Persian

74/870

Needs editing

Context	English	Persian	State
	The <filename>xorg.conf.new</filename> configuration file may now be tuned to taste. Open the file in a text editor such as <citerefentry vendor="ports"><refentrytitle>emacs</refentrytitle><manvolnum>1</manvolnum></citerefentry> or <citerefentry><refentrytitle>ee</refentrytitle><manvolnum>1</manvolnum></citerefentry>. If the monitor is an older or unusual model that does not support autodetection of sync frequencies, those settings can be added to <filename>xorg.conf.new</filename> under the <literal>"Monitor"</literal> section:
	Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName "Monitor Model" HorizSync 30-107 VertRefresh 48-120 EndSection
	Most monitors support sync frequency autodetection, making manual entry of these values unnecessary. For the few monitors that do not support autodetection, avoid potential damage by only entering values provided by the manufacturer.
	X allows DPMS (Energy Star) features to be used with capable monitors. The <citerefentry vendor="xfree86"><refentrytitle>xset</refentrytitle><manvolnum>1</manvolnum></citerefentry> program controls the time-outs and can force standby, suspend, or off modes. If you wish to enable DPMS features for your monitor, you must add the following line to the monitor section:
	Option "DPMS"
	<primary><filename>xorg.conf</filename></primary>
	While the <filename>xorg.conf.new</filename> configuration file is still open in an editor, select the default resolution and color depth desired. This is defined in the <literal>"Screen"</literal> section:
	Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes "1024x768" EndSubSection EndSection
	The <literal>DefaultDepth</literal> keyword describes the color depth to run at by default. This can be overridden with the <option>-depth</option> command line switch to <citerefentry vendor="xorg"><refentrytitle>Xorg</refentrytitle><manvolnum>1</manvolnum></citerefentry>. The <literal>Modes</literal> keyword describes the resolution to run at for the given color depth. Note that only VESA standard modes are supported as defined by the target system's graphics hardware. In the example above, the default color depth is twenty-four bits per pixel. At this color depth, the accepted resolution is 1024 by 768 pixels.
	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: