mining custom_top_html:no
default debug random = 0 / type = READ / detected = READ
리눅스
2018-02-21 03:08:36

ubuntu 채굴 오버클럭 리셋 방법 질문

 

 ethminer 님의 글로 다행히 우분투 서버에 채굴 세팅을 완료했습니다. (1060 3GB x 6 way)

  - https://www.ddengle.com/board_FAQ/2395534

  - https://www.ddengle.com/board_FAQ/2719454

 

 

 

ubuntu server로 설치 후에 필수 패키지만 설치하는 방식으로

처음 ubuntu 설치시 제외하고 ssh 활성화 이후 모든 작업은 터미널로만 작업을 했습니다.

 

조만간 세팅 방법에 공유하겠습니다.

 

 

마지막으로 적당한 오버클럭 값을 찾다보니 궁금한 점이 생겼습니다.

 

Windows에서의 오버클럭이라면 Afterburner를 이용하는데, 만약 불안정한 상태라면 단순히 reset만 눌러주면 되었습니다.

 

ubuntu에서는 불안정한 값을 다시 낮추기 위해서

`nvidia-settings -a [gpu:0]/GPUGraphicsClockOffset[3]=0 -a [gpu:0]/GPUMemoryTransferRateOffset[3]=0` 으로 주어도 

 

ERROR: Error assigning value 0 to attribute 'GPUGraphicsClockOffset' (miner01:1[gpu:0]) as specified in

       assignment '[gpu:0]/GPUGraphicsClockOffset[3]=0' (Unknown Error).

 

ERROR: Error assigning value 0 to attribute 'GPUMemoryTransferRateOffset' (miner01:1[gpu:0]) as specified in

       assignment '[gpu:0]/GPUMemoryTransferRateOffset[3]=0' (Unknown Error).

 

이렇게 못알아 먹고 nvidia-smi 에서는 fan / power 가 ERR! 으로 나타네요.

 

Windows에서는 단순히 Afterbuner에서 reset만 해주면 되었는데,

ubuntu에서는 매번 재부팅을 해줘야하는 번거로움이... 

 

혹시 오버를 리셋하는 방법이 있을까요?

 

3
댓글 3
  • man 명령어로 메뉴얼을 봐도 리셋하는 건 없는 듯 한데요.
    아래 메뉴얼 내용입니다. 참고하세요.

    nvidia-settings(1) General Commands Manual nvidia-settings(1)

    NAME
    nvidia-settings - configure the NVIDIA graphics driver

    SYNOPSIS
    nvidia-settings [options]
    nvidia-settings [options] --no-config
    nvidia-settings [options] --load-config-only
    nvidia-settings [options] {--query=attr | --assign=attr=value} ...
    nvidia-settings [options] --glxinfo

    Options: [-vh] [--config=configfile] [-c ctrl-display]
    [--verbose={none | errors | deprecations | warnings | all}]
    [--describe={all | list | attribute_name}]

    attr has the form:
    DISPLAY/attribute_name[display_devices]

    DESCRIPTION
    The nvidia-settings utility is a tool for configuring the NVIDIA graphics driver. It operates by communicating with the NVIDIA X driver, querying and updating state as appro‐
    priate. This communication is done via the NV-CONTROL, GLX, XVideo, and RandR X extensions.

    Values such as brightness and gamma, XVideo attributes, temperature, and OpenGL settings can be queried and configured via nvidia-settings.

    When nvidia-settings starts, it reads the current settings from its configuration file and sends those settings to the X server. Then, it displays a graphical user interface
    (GUI) for configuring the current settings. When nvidia-settings exits, it queries the current settings from the X server and saves them to the configuration file.

    OPTIONS
    -v, --version
    Print the nvidia-settings version and exit.

    -h, --help
    Print usage information and exit.

    --config=CONFIG
    Use the configuration file CONFIG rather than the default ~/.nvidia-settings-rc

    -c CTRL-DISPLAY, --ctrl-display=CTRL-DISPLAY
    Control the specified X display. If this option is not given, then nvidia-settings will control the display specified by '--display' ; if that is not given, then the
    $DISPLAY environment variable is used.

    -l, --load-config-only
    Load the configuration file, send the values specified therein to the X server, and exit. This mode of operation is useful to place in your xinitrc file, for example.

    -n, --no-config
    Do not load the configuration file. This mode of operation is useful if nvidia-settings has difficulties starting due to problems with applying settings in the configu‐
    ration file.

    -r, --rewrite-config-file
    Write the X server configuration to the configuration file, and exit, without starting the graphical user interface. See EXAMPLES section.

    -V VERBOSE, --verbose=VERBOSE
    Controls how much information is printed. Valid values are 'none' (do not print status messages), 'errors' (print error messages), 'deprecations' (print error and dep‐
    recation messages), 'warnings' (print error, deprecation, and warning messages), and 'all' (print error, deprecation, warning and other informational messages). By
    default, 'deprecations' is set.

    -a ASSIGN, --assign=ASSIGN
    The ASSIGN argument to the '--assign' command line option is of the form:

    {DISPLAY}/{attribute name}[{display devices}]={value}

    This assigns the attribute {attribute name} to the value {value} on the X Display {DISPLAY}. {DISPLAY} follows the usual {host}:{display}.{screen} syntax of the DISPLAY
    environment variable and is optional; when it is not specified, then it is implied following the same rule as the --ctrl-display option. If the X screen is not speci‐
    fied, then the assignment is made to all X screens. Note that the '/' is only required when {DISPLAY} is present.

    {DISPLAY} can additionally include a target specification to direct an assignment to something other than an X screen. A target specification is contained within brack‐
    ets and consists of a target type name, a colon, and the target id. The target type name can be one of screen , gpu , framelock , vcs , gvi , fan , thermalsensor , svp
    , or dpy ; the target id is the index into the list of targets (for that target type). The target specification can be used in {DISPLAY} wherever an X screen can be
    used, following the syntax {host}:{display}[{target_type}:{target_id}]. See the output of

    nvidia-settings -q all

    for information on which target types can be used with which attributes. See the output of

    nvidia-settings -q screens -q gpus -q framelocks -q vcs -q gvis -q fans -q thermalsensors -q svps -q dpys

    for lists of targets for each target type.

    The [{display devices}] portion is also optional; if it is not specified, then the attribute is assigned to all display devices.

    Some examples:

    -a FSAA=5
    -a localhost:0.0/DigitalVibrance[CRT-0]=0
    --assign="SyncToVBlank=1"
    -a [gpu:0]/DigitalVibrance[DFP-1]=63

    -q QUERY, --query=QUERY
    The QUERY argument to the '--query' command line option is of the form:

    {DISPLAY}/{attribute name}[{display devices}]

    This queries the current value of the attribute {attribute name} on the X Display {DISPLAY}. The syntax is the same as that for the '--assign' option, without '=
    {value}' ; specify '-q screens', '-q gpus', '-q framelocks', '-q vcs', '-q gvis', '-q fans' , '-q thermalsensors', '-q svps', or '-q dpys' to query a list of X screens,
    GPUs, Frame Lock devices, Visual Computing Systems, SDI Input Devices, Fans, Thermal Sensors, 3D Vision Pro Transceivers, or Display Devices, respectively, that are
    present on the X Display {DISPLAY}. Specify '-q all' to query all attributes.

    -t, --terse
    When querying attribute values with the '--query' command line option, only print the current value, rather than the more verbose description of the attribute, its valid
    values, and its current value.

    -d, --display-device-string
    When printing attribute values in response to the '--query' option, if the attribute value is a display device mask, print the value as a list of display devices (e.g.,
    "CRT-0, DFP-0"), rather than a hexadecimal bit mask (e.g., 0x00010001).

    -g, --glxinfo
    Print GLX Information for the X display and exit.

    -e DESCRIBE, --describe=DESCRIBE
    Prints information about a particular attribute. Specify 'all' to list the descriptions of all attributes. Specify 'list' to list the attribute names without a
    descriptions.

    -p PAGE, --page=PAGE
    The PAGE argument to the '--page' commandline option selects a particular page in the nvidia-settings user interface to display upon starting nvidia-settings. Valid
    values are the page names in the tree view on the left side of the nvidia-settings user interface; e.g.,

    --page="X Screen 0"

    Because some page names are not unique (e.g., a "PowerMizer" page is present under each GPU), the page name can optionally be prepended with the name of the parent X
    Screen or GPU page, followed by a comma. E.g.,

    --page="GPU 0 - (Quadro 6000), PowerMizer"

    The first page with a name matching the PAGE argument will be used. By default, the "X Server Information" page is displayed.

    -L, --list-targets-only
    When performing an attribute query (from the '--query' command line option) or an attribute assignment (from the '--assign' command line option or when loading an
    ~/.nvidia-settings-rc file), nvidia-settings identifies one or more targets on which to query/assign the attribute.

    The '--list-targets-only' option will cause nvidia-settings to list the targets on which the query/assign operation would have been performed, without actually perform‐
    ing the operation(s), and exit.

    -w, --write-config, --no-write-config
    Save the configuration file on exit (enabled by default).

    -i, --use-gtk2
    Force nvidia-settings to use the GTK+ 2 library for the graphical user interface if a user interface is required. This option is only available on systems where
    nvidia-settings supports both the GTK+ 2 and GTK+ 3 user interfaces.

    -I GTK-LIBRARY, --gtk-library=GTK-LIBRARY
    Specify the graphical user interface library to use if a nvidia-settings user interface is required. This value may be the exact location of the library or it may be the
    directory containing the appropriately named library. If this is the exact location, the 'use-gtk2' option is ignored.

    USER GUIDE
    Contents
    1. Layout of the nvidia-settings GUI
    2. How OpenGL Interacts with nvidia-settings
    3. Loading Settings Automatically
    4. Command Line Interface
    5. X Display Names in the Config File
    6. Connecting to Remote X Servers
    7. Licensing
    8. TODO

    1. Layout of the nvidia-settings GUI
    The nvidia-settings GUI is organized with a list of different categories on the left side. Only one entry in the list can be selected at once, and the selected category con‐
    trols which "page" is displayed on the right side of the nvidia-settings GUI.

    The category list is organized in a tree: each X screen contains the relevant subcategories beneath it. Similarly, the Display Devices category for a screen contains all the
    enabled display devices beneath it. Besides each X screen, the other top level category is "nvidia-settings Configuration", which configures behavior of the nvidia-settings
    application itself.

    Along the bottom of the nvidia-settings GUI, from left to right, is:

    1) a status bar which indicates the most recently altered option;

    2) a Help button that toggles the display of a help window which provides a detailed explanation of the available options in the current page; and

    3) a Quit button to exit nvidia-settings.

    Most options throughout nvidia-settings are applied immediately. Notable exceptions are OpenGL options which are only read by OpenGL when an OpenGL application starts.

    Details about the options on each page of nvidia-settings are available in the help window.

    2. How OpenGL Interacts with nvidia-settings
    When an OpenGL application starts, it downloads the current values from the X driver, and then reads the environment (see APPENDIX E: OPENGL ENVIRONMENT VARIABLE SETTINGS in
    the README). Settings from the X server override OpenGL's default values, and settings from the environment override values from the X server.

    For example, by default OpenGL uses the FSAA setting requested by the application (normally, applications do not request any FSAA). An FSAA setting specified in nvidia-set‐
    tings would override the OpenGL application's request. Similarly, the __GL_FSAA_MODE environment variable will override the application's FSAA setting, as well as any FSAA
    setting specified in nvidia-settings.

    Note that an OpenGL application only retrieves settings from the X server when it starts, so if you make a change to an OpenGL value in nvidia-settings, it will only apply to
    OpenGL applications which are started after that point in time.

    3. Loading Settings Automatically
    The NVIDIA X driver does not preserve values set with nvidia-settings between runs of the X server (or even between logging in and logging out of X, with xdm(1), gdm, or kdm ).
    This is intentional, because different users may have different preferences, thus these settings are stored on a per-user basis in a configuration file stored in the user's
    home directory.

    The configuration file is named ~/.nvidia-settings-rc. You can specify a different configuration file name with the --config command line option.

    After you have run nvidia-settings once and have generated a configuration file, you can then run:

    nvidia-settings --load-config-only

    at any time in the future to upload these settings to the X server again. For example, you might place the above command in your ~/.xinitrc file so that your settings are
    applied automatically when you log in to X.

    Your .xinitrc file, which controls what X applications should be started when you log into X (or startx), might look something like this:

    nvidia-settings --load-config-only &
    xterm &
    evilwm

    or:

    nvidia-settings --load-config-only &
    gnome-session

    If you do not already have an ~/.xinitrc file, then chances are that xinit(1) is using a system-wide xinitrc file. This system wide file is typically here:

    /etc/X11/xinit/xinitrc

    To use it, but also have nvidia-settings upload your settings, you could create an ~/.xinitrc with the contents:

    nvidia-settings --load-config-only &
    . /etc/X11/xinit/xinitrc

    System administrators may choose to place the nvidia-settings load command directly in the system xinitrc script.

    Please see the xinit(1) man page for further details of configuring your ~/.xinitrc file.

    4. Command Line Interface
    nvidia-settings has a rich command line interface: all attributes that can be manipulated with the GUI can also be queried and set from the command line. The command line syn‐
    tax for querying and assigning attributes matches that of the .nvidia-settings-rc configuration file.

    The --query option can be used to query the current value of attributes. This will also report the valid values for the attribute. You can run nvidia-settings --query all for
    a complete list of available attributes, what the current value is, what values are valid for the attribute, and through which target types (e.g., X screens, GPUs) the
    attributes can be addressed. Additionally, individual attributes may be specified like this:

    nvidia-settings --query Overlay

    An attribute name may be prepended with an X Display name and a forward slash to indicate a different X Display; e.g.:

    nvidia-settings --query localhost:0.0/Overlay

    An attribute name may also just be prepended with the screen number and a forward slash:

    nvidia-settings --query 0/Overlay

    in which case the default X Display will be used, but you can indicate to which X screen to direct the query (if your X server has multiple X screens). If no X screen is spec‐
    ified, then the attribute value will be queried for all valid targets of the attribute (eg GPUs, Displays X screens, etc).

    Attributes can be addressed through "target types". A target type indicates the object that is queried when you query an attribute. The default target type is an X screen,
    but other possible target types are GPUs, Frame Lock devices, Visual Computing Systems, SDI Input Devices, fans, thermal sensors, 3D Vision Pro Transceivers and display
    devices.

    Target types give you different granularities with which to perform queries and assignments. Since X screens can span multiple GPUs (in the case of Xinerama, or SLI), and mul‐
    tiple X screens can exist on the same GPU, it is sometimes useful to address attributes by GPU rather than X screen.

    A target specification is contained within brackets and may consist of a target type name, a colon, and the target id. The target type name can be one of screen, gpu, frame‐
    lock, vcs, gvi, fan, thermalsensor, svp, or dpy; the target id is the index into the list of targets (for that target type). Target specifications can be used wherever an X
    screen is used in query and assignment commands; the target specification can be used either by itself on the left side of the forward slash, or as part of an X Display name.

    For example, the following queries address X screen 0 on the localhost:

    nvidia-settings --query 0/VideoRam
    nvidia-settings --query localhost:0.0/VideoRam
    nvidia-settings --query [screen:0]/VideoRam
    nvidia-settings --query localhost:0[screen:0]/VideoRam

    To address GPU 0 instead, you can use either of:

    nvidia-settings --query [gpu:0]/VideoRam
    nvidia-settings --query localhost:0[gpu:0]/VideoRam

    Note that if a target specification is present, it will override any X screen specified in the display name as the target to process. For example, the following query would
    address GPU 0, and not X screen 1:

    nvidia-settings --query localhost:0.1[gpu:0]/VideoRam

    A target name may be used instead of a target id, in which case all targets with matching names are processed.

    For example, querying the DigitalVibrance of display device DVI-I-1 may be done like so:

    nvidia-settings --query [dpy:DVI-I-1]/DigitalVibrance

    When a target name is specified, the target type name may be omitted, though this should be used with caution since the name will be matched across all target types. The above
    example could be written as:

    nvidia-settings --query [DVI-I-1]/DigitalVibrance

    The target name may also simply be a target type name, in which case all targets of that type will be queried.

    For exmple, querying the BusRate of all GPUs may be done like so:

    nvidia-settings --query [gpu]/BusRate

    The target specification may also include a target qualifier. This is useful to limit processing to a subset of targets, based on an existing relationship(s) to other targets.
    The target qualifier is specified by prepending a target type name, a colon, the target id, and a period to the existing specification. Only one qualitfer may be specified.

    For example, querying the RefreshRate of all DFP devices on GPU 1 may be done like so:

    nvidia-settings --query [GPU:1.DPY:DFP]/RefreshRate

    Likewise, a simple target name (or target type name) may be used as the qualifier. For example, to query the BusType of all GPUs that have DFPs can be done like so:

    nvidia-settings --query [DFP.GPU]/BusType

    See the output of

    nvidia-settings --query all

    for what targets types can be used with each attribute. See the output of

    nvidia-settings --query screens --query gpus --query framelocks --query vcs --query gvis --query fans --query thermalsensors --query svps --query dpys

    for lists of targets for each target type.

    To enable support for the "GPUGraphicsClockOffset" and "GPUMemoryTransferRateOffset" attributes, ensure that the "Coolbits" X configuration option includes the value "8" in the
    bitmask. For more details, refer to the documentation of the "Coolbits" option in the NVIDIA driver README. Query the "GPUPerfModes" string attribute to see a list of the
    available performance modes:

    nvidia-settings --query GPUPerfModes

    Each performance mode is presented as a comma-separated list of "token=value" pairs. Each set of performance mode tokens is separated by a ";". The "perf" token indicates the
    performance level. The "*editable" tokens indicate which domains within the performance level can have an offset applied. The "GPUGraphicsClockOffset" and "GPUMemoryTransfer‐
    RateOffset" attributes map respectively to the "nvclock" and "memtransferrate" tokens of performance levels in the "GPUPerfModes" string.

    Note that the clock manipulation attributes "GPUGraphicsClockOffset" and "GPUMemoryTransferRateOffset" apply to the offsets of specific performance levels. The performance
    level is specified in square brackets after the attribute name. For example, to query the "GPUGraphicsClockOffset" for performance level 2:

    nvidia-settings --query GPUGraphicsClockOffset[2]

    The --assign option can be used to assign a new value to an attribute. The valid values for an attribute are reported when the attribute is queried. The syntax for --assign
    is the same as --query, with the additional requirement that assignments also have an equal sign and the new value. For example:

    nvidia-settings --assign FSAA=2
    nvidia-settings --assign [CRT-1]/DigitalVibrance=9
    nvidia-settings --assign [gpu:0]/DigitalVibrance=0
    nvidia-settings --assign [gpu:0]/GPUGraphicsClockOffset[2]=10

    Multiple queries and assignments may be specified on the command line for a single invocation of nvidia-settings. Assignments are processed in the order they are entered on
    the command line. If multiple assignments are made to the same attribute or to multiple attributes with dependencies, then the later assignments will have priority.

    If either the --query or --assign options are passed to nvidia-settings, the GUI will not be presented, and nvidia-settings will exit after processing the assignments and/or
    queries. In this case, settings contained within the ~/.nvidia-settings-rc configuration file will not be automatically uploaded to the X server, nor will the ~/.nvidia-set‐
    tings-rc configuration file be automatically updated to reflect attribute assignments made via the --assign option.

    5. X Display Names in the Config File
    In the Command Line Interface section above, it was noted that you can specify an attribute without any X Display qualifiers, with only an X screen qualifier, or with a full X
    Display name. For example:

    nvidia-settings --query FSAA
    nvidia-settings --query 0/FSAA
    nvidia-settings --query stravinsky.nvidia.com:0/FSAA

    In the first two cases, the default X Display will be used, in the second case, the screen from the default X Display can be overridden, and in the third case, the entire
    default X Display can be overridden.

    The same possibilities are available in the ~/.nvidia-settings-rc configuration file.

    For example, in a computer lab environment, you might log into any of multiple workstations, and your home directory is NFS mounted to each workstation. In such a situation,
    you might want your ~/.nvidia-settings-rc file to be applicable to all the workstations. Therefore, you would not want your config file to qualify each attribute with an X
    Display Name. Leave the "Include X Display Names in the Config File" option unchecked on the nvidia-settings Configuration page (this is the default).

    There may be cases when you do want attributes in the config file to be qualified with the X Display name. If you know what you are doing and want config file attributes to be
    qualified with an X Display, check the "Include X Display Names in the Config File" option on the nvidia-settings Configuration page.

    In the typical home user environment where your home directory is local to one computer and you are only configuring one X Display, then it does not matter whether each
    attribute setting is qualified with an X Display Name.

    6. Connecting to Remote X Servers
    nvidia-settings is an X client, but uses two separate X connections: one to display the GUI, and another to communicate the NV-CONTROL requests. These two X connections do not
    need to be to the same X server. For example, you might run nvidia-settings on the computer stravinsky.nvidia.com, export the display to the computer bartok.nvidia.com, but be
    configuring the X server on the computer schoenberg.nvidia.com:

    nvidia-settings --display=bartok.nvidia.com:0 \
    --ctrl-display=schoenberg.nvidia.com:0

    If --ctrl-display is not specified, then the X Display to control is what --display indicates. If --display is also not specified, then the $DISPLAY environment variable is
    used.

    Note, however, that you will need to have X permissions configured such that you can establish an X connection from the computer on which you are running nvidia-settings
    (stravinsky.nvidia.com) to the computer where you are displaying the GUI (bartok.nvidia.com) and the computer whose X Display you are configuring (schoenberg.nvidia.com).

    The simplest, most common, and least secure mechanism to do this is to use 'xhost' to allow access from the computer on which you are running nvidia-settings.

    (issued from bartok.nvidia.com)
    xhost +stravinsky.nvidia.com

    (issued from schoenberg.nvidia.com)
    xhost +stravinsky.nvidia.com

    This will allow all X clients run on stravinsky.nvidia.com to connect and display on bartok.nvidia.com's X server and configure schoenberg.nvidia.com's X server.

    Please see the xauth(1) and xhost(1) man pages, or refer to your system documentation on remote X applications and security. You might also Google for terms such as "remote X
    security" or "remote X Windows", and see documents such as the Remote X Apps mini-HOWTO:

    http://www.tldp.org/HOWTO/Remote-X-Apps.html⟩

    Please also note that the remote X server to be controlled must be using the NVIDIA X driver.

    7. Licensing
    The source code to nvidia-settings is released as GPL. The most recent official version of the source code is available here:

    ⟨ftp://download.nvidia.com/XFree86/nvidia-settings/⟩

    Note that nvidia-settings is simply an NV-CONTROL client. It uses the NV-CONTROL X extension to communicate with the NVIDIA X server to query current settings and make changes
    to settings.

    You can make additions directly to nvidia-settings, or write your own NV-CONTROL client, using nvidia-settings as an example.

    Documentation on the NV-CONTROL extension and additional sample clients are available in the nvidia-settings source tarball. Patches can be submitted to linux-bugs@nvidia.com.

    8. TODO
    There are many things still to be added to nvidia-settings, some of which include:

    - different toolkits? The GUI for nvidia-settings is cleanly abstracted from the back-end of nvidia-settings that parses the configuration file and command line, communi‐
    cates with the X server, etc. If someone were so inclined, a different front-end GUI could be implemented.

    - write a design document explaining how nvidia-settings is designed; presumably this would make it easier for people to become familiar with the code base.

    If there are other things you would like to see added (or better yet, would like to add yourself), please contact linux-bugs@nvidia.com.

    FILES
    ~/.nvidia-settings-rc

    EXAMPLES
    nvidia-settings
    Starts the nvidia-settings graphical interface.

    nvidia-settings --load-config-only
    Loads the settings stored in ~/.nvidia-settings-rc and exits.

    nvidia-settings --rewrite-config-file
    Writes the current X server configuration to ~/.nvidia-settings-rc file and exits.

    nvidia-settings --query FSAA
    Query the value of the full-screen antialiasing setting.

    nvidia-settings --assign RedGamma=2.0 --assign BlueGamma=2.0 --assign GreenGamma=2.0
    Set the gamma of the screen to 2.0.

    AUTHOR
    Aaron Plattner
    NVIDIA Corporation

    SEE ALSO
    nvidia-xconfig(1), nvidia-installer(1)

    COPYRIGHT
    Copyright © 2010 NVIDIA Corporation.

    nvidia-settings 390.25 2018-01-29 nvidia-settings(1)
  • ?
    너무 오버 많이 하신거에요 리부팅 하면 됩니다
  • ?
    저 에러는 윈도우에서도 마찬거지입니다 문제가 생기면 재부팅전에는 에러가 떨어지는게 정상입니다 문제발생시 재부팅옵션을 두능것도 방법입니다
default debug random = 0 / type = READ / detected = READ

채굴

코인 채굴에 관한 게시판입니다.

List of Articles
번호 분류 제목 추천 수 조회 수 글쓴이 날짜
공지 채굴 새로 들어오시는분들! - 땡글 이용시 지켜지면 좋은 것 91 311 77837
김광부
2017.06.25
58557 채굴 프리쉽? 이용해보신분들 있으신가요?     470 이가격에 팔길래..                       2 file 0 362
Ssu1
2021.03.18
58556 채굴 1060 6g, 6way 로 하루에 이더 몇개 가져오나요.         안녕하세요. 코린이입니다.    1060 6g, 6way로  집에서 위 사양으로 1대 굴릴때,    1. 이더 한달에 몇개 캐지나요??   2. 전기세는 어떻게 될까요?                   3 0 1056
부자짱
2021.03.18
58555 채굴 채굴 선배님들 환풍 시설에 대해서 여쭤봅니다 일단 10대를 돌리구 있구요  지금까지는 어느정도 열빼고 하는데 크게 문제는 없는데요  이제 여름되면 열관리가 힘들거같아 환풍기 + 흡기용환풍기 하나 추가 하려고해요               첫번째 사진에 대걸레 봉잇는... file 0 467
김팔라
2021.03.18
58554 질문 유난히 해시 안뽑히는 3070   3070 7개를 돌리고있습니다.   다른것들은 제품에따라 다르긴하지만 메모리오버값 1000이상은뽑아주는데 유독 한개만 950까지내려도 incorrect가 발생하네요... 이건 카드불량인가요?? 혹시 뭐 해결방안이나 뭐 없... 7 0 1738
crp
2021.03.18
58553 채굴 Rx470.480.570.580 4g.8g     Rx470 480 4기가. 또는 8기가 Rx570 580 4기가. 또는 8기가   570.580이 그냥 470 480 다음 모델인건가요? 성능은 비슷한지 4기가는 이더채굴 가능한지? 레이븐 채굴하려면 굳이 8기가 사야한다면 좋은이유? 8기... 3 0 627
Ssu1
2021.03.18
58552 채굴 hive에서도 4기가 그래픽카드 이더 종료되엇나요?   하이브에서 4기가 캐진다는 애기있던데 amd 쪽만 되나요? 엔비디아 종료되엇나요?                     0 361
푸른꿈
2021.03.18
58551 채굴 꾸역꾸역 1셋트 구성했네요..     2060슈퍼1개 1660슈퍼 2개 2070 1개 1060 2개 혼자 투닥투닥하면서 만들었네요... 모든 채굴러분들 화이팅 입니다!                   12 file 0 816
꾸구
2021.03.18
58550 채굴 3060 한대분 세팅했습니다   엔비디아 드라이버는 470.05버젼 파워 65 코어-200 메모리 1100 세팅하니 48.1에서48.2왔다갔다거리네요                     11 file 0 1904
카잇호
2021.03.18
58549 채굴 산업용 전기 채굴장 관련하여. 링크 #1 : https://trustcoinmining.com/bbs/board.php?bo_table=blockchain&wr_id=64 [정보공유] | 산업용 전기 채굴장 관련하여.     아래 산업용 전기 채굴장 게시글, https://www.ddengle.com/mining/1289391... 38 19 6270
안씨아저씨
2021.03.18
58548 질문 하이브에서 그래픽카드 뺀거 어떻게 삭제하나요? 7웨이 하려다가 그냥 6웨이 쓸라고 하는데 저 7번째꺼가 자꾸 에러로 표시되서 없애고 싶은데 도저히 못찾겠네요.   다시 안건들이고 싶어서 그러는데 일꾼 새로 만드는 방법 말고 없나요?                       3 file 1 380
제로포스
2021.03.18
58547 채굴 채굴장 흡배기 질문드립니다. 채굴장은 20~30평쯤 되며 50대가 돌아가고있습니다. 환풍기는 EK-2500 각 4개씩 총 8개 달려있고  선풍기는 5대 전부 돌아갑니다    채굴장 맨 앞쪽 환풍기 근처로 가보면 열기가 머물러있고 빠져나가는 느낌이 안납... 13 file 0 586
비트1만원
2021.03.18
58546 질문 선배님들 채굴기 켜고 끄실때 파워스위치로 강제종료 하시나요?? 모니터 연결안해놔서 껏다켤때 파워스위치 꾹누르면서 (강제종료?) 시키는데   이거 잘못하면 컴터 문제생기지 않나요~~??                   5 0 570
채굴왕블로
2021.03.18
58545 채굴 채굴장 IOT 설비에 관련해서   채굴장을 오랫동안 운영하다보니 여러가지 노하우가 생겼습니다. 땡글에는 주로 전력에 대한 애기만 올라와서 제가 사용하고 있는 IOT 장비들을 소개할까 합니다.   이제 점점 더워지는데 겨울에는 채굴장 온도 신... 5 file 2 797
wkh0920
2021.03.18
58544 채굴 윈도우 재 설치 후에도 부팅이 엄청 느리고 특히 채굴시 배치 파일 나오고  그래픽 확인 한 이후에 깜박 거리다가 약 10분이 지나야 그래픽 사용 알려주고 채굴을 시작 합니다.  분명히 윈도우 문제 인것 같은데요.  윈도우 설치 uefi 로 해야 할까요? 보드는 그 유명한 바... 4 1 392
자전거나라
2021.03.18
58543 채굴 이더리움 'EIP-1559' 대응하는 채굴자 "채굴 보상 늘린다" 오는 7월 런던 하드포크에 적용되는 이더리움 개선 제안 'EIP-1559'에 대응해 채굴자들이 채굴 보상 확대 기능 도입에 나선다. 이더리움 최대 채굴풀 이더마인(Ethermine)의 운영사 비트플라이(Bitfly)는 18일(한국시... 5 2 1415
npc
2021.03.18
58542 질문 채린이 듀얼파워 구성시 전원선 궁금합니다 드디어 6way 완성해서 설치중인데요 1.보조파워쪽 사진인데 저부분에도 돼지코 케이블 연결해서 콘센트에 꼽아줘야하나요?? 2.듀얼파워커넥터사진인데 스위치는 on에다 해놓으면될까요??                               20 file 0 646
난다래
2021.03.18
58541 채굴 밀폐형 채굴기 연속운전은 얼마나 하시나여?     24시간 쉬지않고 돌리니까 혹시나 팬에 무리가 되지 않을까 좀 걱정이 됩니다.   가끔씩 30분씩이라도 휴식(?)을 주는게 장비에 이로울지??   아님 그냥 연속으로 한달이상 돌려두 문제가 없는지??   밀폐형 채굴... 16 0 660
달라랑
2021.03.18
58540 채굴 레이븐 채굴은 이더리움 채굴처럼 전력소모를 최소화할수 없나요? 제가 알기로는 레이븐 채굴이 이더리움처럼 애프터버너를 통해서 전력을 최저 수준으로 조절 못한다고 들었는데 그렇다면 레이븐채굴은 전성비가 이더리움보다 훨씬 안좋겟네요?                          4 0 936
방의표
2021.03.18
58539 채굴 산업용전기 채굴장           안녕하세요    고수님들 답변좀 부탁드려요!   채굴장 운영을 하려고 알아보는중에    4층짜리 건물에 3층이 나와서요    가보니 여러 업체가 같이쓰는 건물이더라고요   한전에 전화하니 산업전기이고 통... 44 0 1722
웅이당
2021.03.18
58538 질문 6800 5way 해시출렁임은 해결했는데 컴터가 다운되네요 ㅠ       선배님들 도움으로 해시출렁임도 잡고 해시값도 더 올릴 수 있었습니다. 감사합니다ㅠ   근데 이번엔 몇시간 돌리다가 첫번째 사진처럼 뜨면서 컴터가 멈춰버립니다.    마우스도 안되고 리셋버튼 눌러야 재부... 8 file 0 618
스타님
2021.03.18
목록
Board Pagination Prev 1 ... 839 840 841 842 843 844 845 846 847 848 ... 3771 Next
/ 3771
default debug random = 0 / type = READ / detected = READ