Skip to content

Improve NVIDIA tools for auto-configuration #9

Merged
merged 3 commits into from
Mar 29, 2017

Conversation

pmenzel
Copy link
Contributor

@pmenzel pmenzel commented Mar 28, 2017

With these changes, the X.org X server is able to automatically configure the driver with just the snippet
below.

$ more /etc/X11/xorg.conf.d/nvidia-drm-outputclass.conf 
# This xorg.conf.d configuration snippet configures the X server to
# automatically load the nvidia X driver when it detects a device driven by the
# nvidia-drm.ko kernel module.  Please note that this only works on Linux kernels
# version 3.9 or higher with CONFIG_DRM enabled, and only if the nvidia-drm.ko
# kernel module is loaded before the X server is started.

Section "OutputClass"
    Identifier     "nvidia"
    MatchDriver    "nvidia-drm"
    Driver         "nvidia"
EndSection

From `nvidia-drm-outputclass.conf` shipped by the NVIDIA Installer.

> This xorg.conf.d configuration snippet configures the X server to
> automatically load the nvidia X driver when it detects a device driven
> by the nvidia-drm.ko kernel module.  Please note that this only works
> on Linux kernels version 3.9 or higher with CONFIG_DRM enabled, and
> only if the nvidia-drm.ko kernel module is loaded before the X server
> is started.

Therefore load that Linux Kernel module so that the configuration works
automatically.

From Aaron Plattner in #nvidia@irc.freenode.net:

> 16:31 < aaronp> PaulePanter, by default, nvidia-drm.ko provides the X
>       auto-load behavior and also assists in wiring up PRIME
>       configurations to the integrated GPU's display.
> 16:31 < aaronp> If you load it with the 'modeset=1' parameter, then it
>       provides a complete drm driver that can be used by drm/eglstream
>       clients such as mutter or patched versions of weston.
@donald donald merged commit 311c1ae into master Mar 29, 2017
@donald donald deleted the improve-nvidia-tools-for-auto-configuration branch March 14, 2018 09:36
pmenzel added a commit that referenced this pull request May 17, 2021
From [issues #9 (*Document ERL_EPMD_ADDRESS and ERL_EPMD_PORT*)][1]:

> === ERL_EPMD_ADDRESS ===
>
> On eturnal startup, an Erlang Port Mapper Daemon (epmd) service is spawned (if
> not running already). This service listens on all available interfaces by
> default. Setting the `ERL_EPMD_ADDRESS' environment variable tells epmd to
> listen on the specified comma-seperated list of IP addresses instead. Note that
> the IPv4 and IPv6 loopback addresses are implicitly added to this list if not
> specified. It's usually recommended to set `ERL_EPMD_ADDRESS' to `127.0.0.1'
> (e.g., by calling `systemctl edit eturnal' and adding an
> `Environment="ERL_EPMD_ADDRESS=127.0.0.1"' line to the `[Service]' section).

[1]: https://github.com/processone/eturnal/issues/9
Sign in to join this conversation on GitHub.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants