Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 53540 Details for
Bug 85355
I have just finished some translations.
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
[patch]
nvidia-guide.xml korean translation
nvidia-guide.xml.diff (text/plain), 12.28 KB, created by
Park, Jin Hyung
on 2005-03-15 08:08:46 UTC
(
hide
)
Description:
nvidia-guide.xml korean translation
Filename:
MIME Type:
Creator:
Park, Jin Hyung
Created:
2005-03-15 08:08:46 UTC
Size:
12.28 KB
patch
obsolete
>--- en/nvidia-guide.xml 2005-03-14 02:54:19.000000000 +0000 >+++ ko/nvidia-guide.xml 2005-03-15 13:56:41.000000000 +0000 >@@ -1,102 +1,104 @@ > <?xml version='1.0' encoding="UTF-8"?> >-<!-- $Header: /home/cvs/gentoo/ko/en/nvidia-guide.xml,v 1.1.1.1 2005/03/14 02:54:19 jenix Exp $ --> >+<!-- $Header: /home/cvs/gentoo/ko/ko/nvidia-guide.xml,v 1.2 2005/03/15 13:56:41 prdd Exp $ --> > <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> > >-<guide link="/doc/en/nvidia-guide.xml"> >-<title>Gentoo Linux nVidia Guide</title> >+<guide link="/doc/ko/nvidia-guide.xml"> >+<title>Gentoo Linux nVidia ê°ì´ë</title> > > <author title="Author"> > <mail link="swift@gentoo.org">Sven Vermeulen</mail> > </author> >+<author title="ë²ì"> >+ <mail link="prdd79@gmail.com">ê¹ ëì</mail> >+</author> > > <abstract> >-Many Gentooists have an nVidia chipset on their system. nVidia provides specific >-Linux drivers to boost the performance of your card. This guide informs you how >-to install and configure these drivers. >+ë§ì ì í¬ ì¬ì©ìë¤ì nVidia 칩ì ì ì¬ì©íë ìì¤í ì ê°ì§ê³ ììµëë¤. nVidia ë ì¹´ëì ì±ë¥ì >+í¥ììì¼ì£¼ê¸° ìí í¹íë 리ë ì¤ í¸ë¼ì´ë²ë¥¼ ì ê³µí©ëë¤. ì´ ë¬¸ìë ì¬ë¬ë¶ìê² ì´ë¬í ëë¼ì´ë²ë¥¼ >+ì¤ì¹íê³ , ì¤ì íë ë°©ë²ì ì¤ëª í ê²ì ëë¤. > </abstract> > > <license/> > > <version>1.8</version> > <date>2005-02-25</date> >+<!-- Original revision: 1.8 --> > > <chapter> >-<title>Configuring your Card</title> >+<title>ì¹´ë ì¤ì í기</title> > <section> >-<title>Installing the Appropriate Drivers</title> >+<title>ì ì© ëë¼ì´ë² ì¤ì¹í기</title> > <body> > > <p> >-The nVidia drivers include kernel modules that must integrate in your current >-kernel. To accomplish this, your kernel must support the loading of kernel >-modules. If you used <c>genkernel</c> to configure the kernel for you then >-you're all set. If not, double check your kernel configuration so that this >-support is enabled: >+nVidia ëë¼ì´ë²ë íì¬ ì»¤ëì íµí©ëì´ì¼ íë 커ë 모ëì´ í¬í¨ëì´ ììµëë¤. ì´ ëë¼ì´ë²ë¥¼ >+ì¬ì©í기 ìí´ìë, 커ëì´ ì»¤ë 모ë ë¡ë©ì ì§ìí´ì¼ í©ëë¤. ë§ì½ <c>genkernel</c> ì 커ë >+ì¤ì ì ì´ì©íë¤ë©´, ì¤ë¹ë ëì´ ìì ê²ì ëë¤. ê·¸ë ì§ ìë¤ë©´, ì´ ì´ë¬í ì§ìì´ íì±í ëì´ ìëì§ >+ë¤ì íë² íì¸í´ 주ììì: > </p> > >-<pre caption="Enabling the Loading of Kernel Modules"> >+<pre caption="커ë 모ë ë¡ë© ì¼ê¸°"> > Loadable module support ---> > [*] Enable loadable module support > </pre> > > <p> >-You also need to enable <e>Memory Type Range Register</e> in your kernel: >+<e>Memory Type Range Register</e> ìì 커ëìì íì±íí íìê° ììµëë¤: > </p> > >-<pre caption="Enabling MTRR"> >+<pre caption="MTRR íì±í"> > Processor and Features ---> > [*] MTRR (Memory Type Range Register) support > </pre> > > <p> >-nVidia's modules and libraries are combined in two packages: <c>nvidia-glx</c> >-and <c>nvidia-kernel</c>. The former are the X11 GLX libraries while the latter >-are the kernel modules. Since <c>nvidia-glx</c> depends on <c>nvidia-kernel</c>, >-installing <c>nvidia-glx</c> is sufficient: >+nVidia ì 모ëê³¼ ë¼ì´ë¸ë¬ë¦¬ë ë¤ì ëê°ì í¨í¤ì§ë¡ 구ì±ëì´ ììµëë¤: <c>nvidia-glx </c> ì >+<c>nvidia-kernel</c> ì ëë¤. íëë X11 GLX ë¼ì´ë¸ë¬ë¦¬ì´ê³ , ë¤ìì 커ë 모ëì ëë¤. >+<c>nvidia-glx</c>ë <c>nvidia-kernel</c>ê³¼ ìì¡´ì± ê´ê³ê° ì¤ì ëì´ ì기 ë문ì >+<c>nvidia-glx</c>ë§ ì¤ì¹íë©´ ë©ëë¤: > </p> > >-<pre caption="Installing the nVidia modules"> >+<pre caption="nVidia 모ë ì¤ì¹"> > # <i>emerge nvidia-glx</i> > </pre> > > <p> >-Once the installation has finished, run <c>modprobe nvidia</c> to load the >-kernel module into memory. >+ì¤ì¹ê° ìë£ëë©´, 커ë 모ëì ë©ëª¨ë¦¬ì ì¬ë¦¬ê¸° ìí´ <c>modprobe nvidia</c> ëª ë ¹ì ì¤íí©ëë¤. > </p> > >-<pre caption="Loading the kernel module"> >+<pre caption="커ë 모ë ë¡ë©"> > # <i>modprobe nvidia</i> > </pre> > > <p> >-You probably want to have this done each time you boot your system, so edit >-<path>/etc/modules.autoload.d/kernel-2.6</path> (or <path>kernel-2.4</path>) and >-add <c>nvidia</c> to it. Don't forget to run <c>modules-update</c> afterwards! >+ìì¤í ì´ ë¶í í ëë§ë¤ ìëì¼ë¡ ì¤ííê³ ì¶ë¤ë©´, >+<path>/etc/modules.autoload.d/kernel-2.6</path> (ëë <path>kernel-2.4</path>) 를 >+ì´ê³ <c>nvidia</c> 를 ì¶ê°í©ëë¤. ê·¸ íì <c>modules-update</c> ëª ë ¹ì ì¤ííë ê²ì ìì§ >+ìëë¡ í©ëë¤. > </p> > >-<pre caption="Running modules-update"> >+<pre caption="modules-update ì¤í"> > # <i>modules-update</i> > </pre> > > </body> > </section> > <section> >-<title>Configuring the X Server</title> >+<title>X ìë² ì¤ì </title> > <body> > > <p> >-Once the appropriate drivers are installed you need to configure your X Server >-(XFree86 or Xorg) to use the <c>nvidia</c> driver instead of the default >-<c>nv</c> driver. >+ëë¼ì´ë²ë¥¼ ì¬ë°ë¥´ê² ì¤ì¹í íì, ì¬ë¬ë¶ì 기본ì¼ë¡ ì¬ì©ëë <c>nv</c> ëë¼ì´ë² ëì >+<c>nvidia</c> ëë¼ì´ë²ë¥¼ ì´ì©íëë¡ X ìë²(XFree86 ëë Xorg)를 ì¤ì í´ì¼ í©ëë¤. > </p> > > <p> >-Open <path>/etc/X11/XF86Config</path> (or <path>/etc/X11/xorg.conf</path>) with >-your favorite editor (such as <c>nano</c> or <c>vim</c>) and go to the >-<c>Device</c> section. In that section, change the <c>Driver</c> line: >+<path>/etc/X11/XF86Config</path> (ëë <path>/etc/X11/xorg.conf</path>) 를 >+ë§ìì ëë í¸ì§ê¸°(<c>nano</c> ëë <c>vim</c> ê°ì)ë¡ ì´ê³ , <c>Device</c> ë¶ë¶ì >+ì°¾ìµëë¤. ì´ê³³ìì <c>Driver</c> ì¤ì ë¤ìê³¼ ê°ì´ í¸ì§í©ëë¤: > </p> > >-<pre caption="Changing nv to nvidia in the X Server configuration"> >+<pre caption="X ìë² ì¤ì ìì nv 를 nvidia ë¡ ë°ê¾¸ê¸°"> > Section "Device" > Identifier "nVidia Inc. GeForce2" > <i>Driver "nvidia"</i> >@@ -105,11 +107,11 @@ > </pre> > > <p> >-Then go to the <c>Module</c> section and make sure the <c>glx</c> module gets >-loaded while the <c>dri</c> module doesn't: >+ê·¸ë¦¬ê³ , <c>Module</c> ë¶ë¶ì ì°¾ìì <c>glx</c> 모ëì´ ì¬ë¼ì¤ëë¡ íê³ <c>dri</c> ë >+ì¬ë¼ì¤ì§ ìëë¡ í©ëë¤: > </p> > >-<pre caption="Updating the Module section"> >+<pre caption="Module section ìì "> > Section "Module" > <comment>(...)</comment> > <i># Load "dri" >@@ -119,70 +121,69 @@ > </pre> > > <p> >-Run <c>opengl-update</c> so that the X Server uses the nVidia GLX libraries: >+<c>opengl-update</c> 를 ì¤íí´ì X ìë²ê° nVidia GLX ë¼ì´ë¸ë¬ë¦¬ë¥¼ ì¬ì©íëë¡ í©ëë¤. > </p> > >-<pre caption="Running opengl-update"> >+<pre caption="opengl-update ì¤í"> > # <i>opengl-update nvidia</i> > </pre> > > </body> > </section> > <section> >-<title>Adding your Users to the video Group</title> >+<title>vidia 그룹ì ì¬ì©ì ì¶ê°</title> > <body> > > <p> >-You have to add your user to the <c>video</c> group so he has access to the >-nvidia device files: >+nvidia ì¥ì¹ì ì ê·¼ ê¶íì ê°ì§ê¸° ìí´ìë ì¬ì©ì를 <c>video</c> 그룹ì ì¶ê°í´ì¼ í©ëë¤: > </p> > >-<pre caption="Adding your user to the video group"> >-# <i>gpasswd -a youruser video</i> >+<pre caption="video 그룹ì ì¬ì©ì ì¶ê°"> >+# <i>gpasswd -a ì¬ì©ìëª video</i> > </pre> > > <p> >-This might not be totally necessary if you aren't used <c>udev</c> but it >-doesn't hurt either and makes your system future-proof :) >+ì¬ë¬ë¶ì´ <c>udev</c> 를 ì¬ì©íì§ ìì¼ë©´ ì í íìíì§ ìì§ë§, ì´ê²ì í´ê° ëì§ë ìì ë¿ëë¬, >+ìì¼ë¡ì ìì¤í ì ëí ì¤ë¹ê° ë©ëë¤. :) > </p> > > </body> > </section> > <section> >-<title>Testing your Card</title> >+<title>Card í ì¤í¸</title> > <body> > > <p> >-To test your nVidia card, fire up X and run the <c>glxinfo | grep direct</c> >-command. It should say that direct rendering is activated: >+ì¬ë¬ë¶ì nVidia ì¹´ë를 í ì¤í¸íë ¤ë©´, X 를 ììíê³ , <c>glxinfo | grep direct</c> ëª ë ¹ì >+ì¤íí©ëë¤. ë¤ì´ë í¸ ë ëë§ì´ íì±í ëì´ ìëì§ë¥¼ ìë ¤ì¤ëë¤: > </p> > >-<pre caption="Checking the direct rendering status"> >+<pre caption="ë¤ì´ë í¸ ë ëë§ ìí íì¸"> > $ <i>glxinfo | grep direct</i> > direct rendering: Yes > </pre> > > <p> >-To monitor your FPS, run <c>glxgears</c>. >+FPS 측ì í기 ìí´ìë, <c>glxgears</c> 를 ì¤íí©ëë¤. > </p> > > </body> > </section> > <section> >-<title>Enabling nvidia Support</title> >+<title>nvidia ì§ì íì±í</title> > <body> > > <p> >-Some tools, such as <c>mplayer</c> and <c>xine-lib</c>, use a local USE flag >-called "nvidia" which enables XvMCNVIDIA support, useful when watching high >-resolution movies. Add in "nvidia" in your USE variable in >-<path>/etc/make.conf</path> or add it as USE flag to <c>media-video/mplayer</c> >-and/or <c>media-libs/xine-lib</c> in <path>/etc/portage/package.use</path>. >+<c>mplayer</c> ë <c>xine-lib</c> ê°ì, ëªëª ë구ë¤ìì, "nvidia" ë¼ë ë¡ì»¬ USE íë그를 >+ì¬ì©íëë°, ì´ê²ì XvMCNVIDIA ì§ìì íì±ííì¬ ê³ í´ìë ëììì ë³¼ ë í¨ê³¼ì ì¼ë¡ ì¬ì©ë©ëë¤. >+<path>/etc/make.conf</path> íì¼ì USE ë³ìì "nvidia" 를 ì¶ê°íê±°ë, >+<path>/etc/portage/package.use</path> íì¼ì <c>media-vidia/mplayer</c> ë >+<c>media-libs/xine-lib</c> ì USE íëê·¸ë¡ ì¶ê°í©ëë¤. > </p> > > <p> >-Then, run <c>emerge -uD --newuse world</c> to rebuild the applications that >-benefit from the USE flag change. >+ê·¸ í, ë°ë USE íë그를 ë°ìí기 ìí´ì, <c>emerge -uD --newuse world</c> ëª ë ¹ì ì¤ííì¬ >+ì´í리ì¼ì´ì ì ë¤ì ë¹ëí©ëë¤. > </p> > > </body> >@@ -190,45 +191,43 @@ > </chapter> > > <chapter> >-<title>Troubleshooting</title> >+<title>문ì í´ê²°</title> > <section> >-<title>Getting 2D to work on machines with 4Gb or more memory</title> >+<title>4G ë³´ë¤ í° ë©ëª¨ë¦¬ë¥¼ ì¬ì©íë ì¥ë¹ìì 2D ì¬ì©í기</title> > <body> > > <p> >-If you are having troubles with the nVidia 2D acceleration it is likely that you >-are unable to set up a write-combining range with MTRR. To verify, check the >-contents of <path>/proc/mtrr</path>: >+nVidia 2D ê°ìì 문ì ê° ìë¤ë©´, ëê² MTRR ì write-combining ì¤ì ì í ì ìë¤ë ë§ì ëë¤. >+íì¸íë ¤ë©´, <path>/proc/mtrr</path> ì ë´ì©ì íì¸íì¸ì: > </p> > >-<pre caption="Checking if you have write-combining enabled"> >+<pre caption="write-combining íì±í ì¬ë¶ íì¸"> > # <i>cat /proc/mtrr</i> > </pre> > > <p> >-Every line should contain "write-back" or "write-combining". If you see a line >-with "uncachable" in it you will need to change a BIOS setting to fix this. >+모ë ì¤ìë "write-back" ëë "write-combining" ì´ í¬í¨ëì´ ìì ê²ì ëë¤. "uncachable" ì´ >+ë¤ì´ìë ì¤ì ë°ê²¬íë¤ë©´, BIOS ì¤ì ì ë³ê²½í íìê° ììµëë¤. > </p> > > <p> >-Reboot and enter the BIOS, then find the MTRR settings (probably under "CPU >-Settings"). Change the setting from "continuous" to "discrete" and boot back >-into Linux. You will now find out that there is no "uncachable" entry anymore >-and 2D acceleration now works without any glitches. >+리ë¶í¸ í BIOS ë¡ ë¤ì´ê°, MTRR (ìë§ë "CPU Settings" í목ì ì ìì ê²ì ëë¤) ì¤ì ì >+ì°¾ìµëë¤. "continuous" ë¼ê³ ë ê²ì "discrete" ë¡ ë°ê¾¸ê³ , ë¤ì 리ë ì¤ë¡ ë¶í íì¸ì. >+ì¬ë¬ë¶ì "uncachable" í목ì ëì´ì ì°¾ì ì ìì ê²ì´ë©°, 2D ê°ìì´ ë¬¸ì ìì´ ìëíë ê²ì >+íì¸í ì ìì ê²ì ëë¤. > </p> > > </body> > </section> > <section> >-<title>I receive warnings about unsupported 4K stack sizes</title> >+<title>ì§ìíì§ ìë 4K ì¤í í¬ê¸°ë¼ë ê²½ê³ ë©ìì§</title> > <body> > > <p> >-<c>nvidia-kernel</c> packages older than 1.0.6106 only support kernels using an >-8K stack size. More recent kernels (2.6.6 and higher) have support for 4K stack >-size's as well. Do not select 4K stack size in your kernel configuration if you >-are using such an <c>nvidia-kernel</c> package. You can find this option in the >-section <c>Kernel Hacking</c>. >+1.0.6106 ì´ì ì <c>nvidia-kernel</c> í¨í¤ì§ë 8K ì¤í í¬ê¸°ë§ ì§ìíìµëë¤. ìµê·¼ì 커ëì >+(2.6.6 ì´ì) ì 4K ì¤íì ì§ìí©ëë¤. ì´ì ê°ì <c>nvidia-kernel</c> í¨í¤ì§ë¥¼ ì¬ì©íê³ >+ìì¼ì ë¶ì, 커ë ì¤ì ìì 4K ì¤íì ì ííì§ ìëë¡ í©ëë¤. <c>Kernel Hacking</c> >+ë¶ë¶ìì í´ë¹ ìµì ì ì°¾ì ì ììµëë¤. > </p> > > </body>
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Diff
View Attachment As Raw
Actions:
View
|
Diff
Attachments on
bug 85355
:
53530
|
53531
|
53532
|
53533
|
53534
|
53535
|
53536
|
53537
|
53538
|
53540