mirror of
https://github.com/tiyn/wiki.git
synced 2026-04-15 16:54:48 +02:00
Structure: Fixed typos and sentences
This commit is contained in:
@@ -1,35 +1,30 @@
|
||||
# Arch Linux
|
||||
|
||||
[Arch Linux](https://archlinux.org/) is a rolling-release, general-purpose
|
||||
[Linux](/wiki/linux.md)
|
||||
[Arch Linux](https://archlinux.org/) is a rolling-release, general-purpose [Linux](/wiki/linux.md)
|
||||
distribution.
|
||||
The package manager of Arch Linux is generally
|
||||
[Pacman and various possible AUR ones](/wiki/linux/package_manager/pacman_and_aur.md).
|
||||
|
||||
## Package Manager and AUR
|
||||
|
||||
Arch Linux uses the
|
||||
[pacman](/wiki/linux/package_manager/pacman_and_aur.md) package
|
||||
manager.
|
||||
Arch Linux uses the [pacman](/wiki/linux/package_manager/pacman_and_aur.md) package manager.
|
||||
An additional repository for user made software exists.
|
||||
It is called Arch User Repository (AUR).
|
||||
The Arch User Repositories (AUR) features community-made packages that can be
|
||||
installed with different
|
||||
[package manager for that purpose](/wiki/linux/package_manager/pacman_and_aur.md).
|
||||
The Arch User Repositories (AUR) features community-made packages that can be installed with
|
||||
different [package manager for that purpose](/wiki/linux/package_manager/pacman_and_aur.md).
|
||||
|
||||
## Installation
|
||||
|
||||
The installation of a basic Arch Linux system is described in the
|
||||
[installation entry](/wiki/linux/arch-linux/installation.md).
|
||||
The entry features a guide to install a system with a X server setup aswell as
|
||||
programs for the most used tasks on a system.
|
||||
The entry features a guide to install a system with a X server setup as well as programs for the
|
||||
most used tasks on a system.
|
||||
|
||||
### Create Installation Medium
|
||||
|
||||
For the installation usage of a simple USB key is advised.
|
||||
This has to be flashed with the Arch ISO.
|
||||
The ISO file can be found on the
|
||||
[official website](https://www.archlinux.org/download/).
|
||||
The ISO file can be found on the [official website](https://www.archlinux.org/download/).
|
||||
The iso can be written on an USB-stick using the command
|
||||
`dd bs=4M if=<path to ISO> of=/dev/sdx conv=fsync oflag=direct status=progress`.
|
||||
`<path to ISO>` points the command to the location of the ISO file.
|
||||
@@ -39,21 +34,21 @@ Alternatively a [Ventoy stick can be created](/wiki/ventoy.md) which can contain
|
||||
|
||||
## Usage
|
||||
|
||||
The following section describes various ways to use and improve the usage of
|
||||
the Arch Linux operating system.
|
||||
The following section describes various ways to use and improve the usage of the Arch Linux
|
||||
operating system.
|
||||
|
||||
### Recommended Practices
|
||||
|
||||
The following articles describe steps to undertake to harden the system security
|
||||
or setups and installation that are recommended for Arch Linux.
|
||||
The following articles describe steps to undertake to harden the system security or setups and
|
||||
installation that are recommended for Arch Linux.
|
||||
|
||||
#### Enable Microcode Updates
|
||||
|
||||
The microcode of Intel and AMD CPUs can be automatically updated by installing
|
||||
the `amd-ucode` or `intel-ucode` package depending on your CPU.
|
||||
The microcode of Intel and AMD CPUs can be automatically updated by installing the `amd-ucode` or
|
||||
`intel-ucode` package depending on your CPU.
|
||||
Not all processors are supported, especially old ones can lead to problems.
|
||||
It has to be confirmed that the processor is supported, if this is not the case
|
||||
is possible for the next steps to break the functionality of the bootloader.
|
||||
It has to be confirmed that the processor is supported, if this is not the case is possible for
|
||||
the next steps to break the functionality of the bootloader.
|
||||
|
||||
The following part assumes the system is installed with
|
||||
[UEFI bootloader](/wiki/linux/arch-linux/installation.md#10-install-and-configure-uefi-bootloader)
|
||||
@@ -87,8 +82,8 @@ On some systems there are home or boot file system that have to be mounted on `/
|
||||
`/mnt/home` after mounting the root file system.
|
||||
Afterward, use `arch-chroot /mnt` to get into the not bootable system.
|
||||
Now the command line of the system can be accessed for troubleshooting.
|
||||
After troubleshooting `exit` the system and [unmount](/wiki/linux/disk-management.md#mounting) all previously
|
||||
mounted file systems and try to boot back into the system.
|
||||
After troubleshooting `exit` the system and [unmount](/wiki/linux/disk-management.md#mounting) all
|
||||
previously mounted file systems and try to boot back into the system.
|
||||
|
||||
If the system broke during an update then the easiest way to fix it, is by running the same update
|
||||
command again.
|
||||
@@ -112,11 +107,11 @@ To fix this generate the initial ramdisk manually as described in
|
||||
There is a known problem described in the Arch Linux forums by
|
||||
[TheRealNubby](https://bbs.archlinux.org/viewtopic.php?id=300292) where the system goes into a
|
||||
perceived freeze after the boot process.
|
||||
This problem seems to be most prevalent on systems that use an [Nvidia](/wiki/nvidia.md) GPU
|
||||
since its only known occurences were found on Nvidia GTX 1080 GPUs.
|
||||
This problem seems to be most prevalent on systems that use an [Nvidia](/wiki/nvidia.md) GPU since
|
||||
its only known occurences were found on Nvidia GTX 1080 GPUs.
|
||||
The boot screen will not show any errors and when
|
||||
[troubleshooting using a installation medium](#troubleshooting-setup-for-not-bootable-systems)
|
||||
logs like [the ones of SystemD](/wiki/linux/systemd.md#retrieving-the-systemd-logs) will look
|
||||
logs like [the ones of systemd](/wiki/linux/systemd.md#retrieving-the-systemd-logs) will look
|
||||
normal and won't show any errors.
|
||||
|
||||
In this case there is the possibility that logging into Arch Linux blindly will work.
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
# Arch installation with LUKS encryption and LVM
|
||||
|
||||
This guide is based upon a
|
||||
[german arch wiki article](https://wiki.archlinux.de/title/Installation_mit_UEFI_und_Verschl%C3%BCsselung).
|
||||
[German arch wiki article](https://wiki.archlinux.de/title/Installation_mit_UEFI_und_Verschl%C3%BCsselung).
|
||||
For encryption [dm-crypt](/wiki/linux/dm-crypt.md) is used.
|
||||
Inside the encrypted partition a logical volume will be created with
|
||||
[LVM](/wiki/linux/lvm.md).
|
||||
@@ -25,9 +25,9 @@ Ahead of the installation an Arch boot-stick has to be created as described in
|
||||
After that the USB can be plugged in the system on which Arch should be installed.
|
||||
Boot the target system and select `Boot Arch Linux (x86_64)`.
|
||||
|
||||
If you need to set the keyboard layout to anything other than english you can
|
||||
If you need to set the keyboard layout to anything other than English you can
|
||||
temporarily do so by using the `loadkeys` command.
|
||||
This has to be followed by your country id (for example a german keyboard layout
|
||||
This has to be followed by your country id (for example a German keyboard layout
|
||||
would be `de`,`de-latin1` or `de-latin1-nodeadkeys`).
|
||||
|
||||
## 2. Formatting of the target drive
|
||||
@@ -137,7 +137,7 @@ Exit `iwctl`.
|
||||
## 7. Set Region and Language
|
||||
|
||||
- `echo LANG=en\_US.UTF-8 > /etc/locale.conf` - Assign system Language to be
|
||||
english (you can use other languages, look into the `/etc/locale.gen` for a list of all available languages)
|
||||
English (you can use other languages, look into the `/etc/locale.gen` for a list of all available languages)
|
||||
- `vim /etc/locale.gen` - Assigning system language by uncomment the lines
|
||||
depending on your needs.
|
||||
In this example:
|
||||
@@ -151,7 +151,7 @@ en_US.UTF-8 UTF-8
|
||||
- `ln -sf /usr/share/zoneinfo/Europe/Berlin /etc/localtime` - set your timezone
|
||||
(select the first file accordingly to your location)
|
||||
- `ntpdate -q 0.de.pool.ntp.org` - sync the time and date with
|
||||
[NTP](/wiki/linux/ntp.md) (note that a german time server is used and
|
||||
[NTP](/wiki/linux/ntp.md) (note that a German time server is used and
|
||||
depending on the needs a adjustments should be made)
|
||||
|
||||
## 8. Configure and create kernel-image
|
||||
@@ -254,8 +254,8 @@ partition, take a look at the according section in
|
||||
[the dm-crypt article](/wiki/linux/dm-crypt.md).
|
||||
|
||||
After installing [xorg windows system](/wiki/linux/x_window_system.md) the language of it will be
|
||||
english by default.
|
||||
To change it - in this example to german - run the following command.
|
||||
English by default.
|
||||
To change it - in this example to German - run the following command.
|
||||
|
||||
```sh
|
||||
localectl --no-convert set-x11-keymap de pc105 deadgraveacute
|
||||
|
||||
@@ -33,9 +33,9 @@ easyeffects --gapplication-service
|
||||
```
|
||||
|
||||
The two former commands will only work if called on each startup.
|
||||
The easiest way to do this is by using [SystemD](/wiki/linux/systemd.md).
|
||||
The easiest way to do this is by using [systemd](/wiki/linux/systemd.md).
|
||||
The following will work analogously to the path explained in
|
||||
[the corresponding section of the SystemD entry](/wiki/linux/systemd.md#run-command-on-boot).
|
||||
[the corresponding section of the systemd entry](/wiki/linux/systemd.md#run-command-on-boot).
|
||||
|
||||
Run the following command to edit the configuration file for the newly created EasyEffect service.
|
||||
|
||||
@@ -88,8 +88,8 @@ By default, EasyEffects processes all input and output streams.
|
||||
This includes [loopback devices](/wiki/linux/pipewire.md#virtual-devices) with which it may lead to
|
||||
some problems - for example
|
||||
[problems with virtual devices](/wiki/linux/pipewire.md#problems-with-input-an-output-of-loopback-devices).
|
||||
It can be disabled and re-enabled in the `Preferences` under `Audio` by deselecting or selecting the
|
||||
switches for `Process all output streams` and `Process all input streams`.
|
||||
It can be disabled and re-enabled in the `Preferences` under `Audio` by deselecting or selecting
|
||||
the switches for `Process all output streams` and `Process all input streams`.
|
||||
|
||||
#### Recommended Presets
|
||||
|
||||
@@ -97,4 +97,4 @@ The following is a list of presets that have been tested and only need slight co
|
||||
adjust them to the specific system.
|
||||
|
||||
- [tiyns voice input preset](https://github.com/tiyn/dotfiles/blob/master/.config/easyeffects/input/voice.json)
|
||||
is a list of different effects to achieve an enhanced quality of microphone sound for speach.
|
||||
is a list of different effects to achieve an enhanced quality of microphone sound for speech.
|
||||
|
||||
@@ -8,4 +8,4 @@ The init process is given to a init system that manages various services.
|
||||
|
||||
The following is a list of available init services.
|
||||
|
||||
- [SystemD](/wiki/linux/systemd.md) is most common among linux systems.
|
||||
- [systemd](/wiki/linux/systemd.md) is most common among linux systems.
|
||||
|
||||
@@ -6,11 +6,11 @@ It is available for both [X](/wiki/linux/x_window_system.md) and Wayland.
|
||||
|
||||
## Setup
|
||||
|
||||
On most linux distributions LightDM can be installed with the `lemurs` package.
|
||||
On most [Linux](/wiki/linux.md) distributions LightDM can be installed with the `lemurs` package.
|
||||
|
||||
This setup needs an `xsession`.
|
||||
An alternative to this is using `xinitrc` as an `xsession`.
|
||||
The process of this is desribed in the
|
||||
This setup needs a `xsession`.
|
||||
An alternative to this is using `xinitrc` as a `xsession`.
|
||||
The process of this is described in the
|
||||
[display manager entry](/wiki/linux/display_managers.md#use-xinitrc-as-xsession).
|
||||
Make sure to have a working `xsession` or `xinitrc`.
|
||||
If you are not sure about it, use the tests provided in the penultimate step.
|
||||
@@ -22,7 +22,7 @@ This can be done by using one or both of the following commands.
|
||||
systemctl start lemurs.service
|
||||
```
|
||||
|
||||
Finally, the [SystemD](/wiki/linux/systemd.md) lightdm service needs to be enabled and reboot the
|
||||
Finally, the [systemd](/wiki/linux/systemd.md) `lightdm` service needs to be enabled and reboot the
|
||||
system.
|
||||
|
||||
```sh
|
||||
|
||||
@@ -2,11 +2,11 @@
|
||||
|
||||
[LightDM](https://github.com/canonical/lightdm/) is a lightweight GUI
|
||||
[display manager](/wiki/linux/display_managers.md).
|
||||
It is available for both [X](/wiki/linux/x_window_system.md) and Wayland.
|
||||
It is available for both [X](/wiki/linux/x_window_system.md) and [Wayland](/wiki/linux/wayland.md).
|
||||
|
||||
## Setup
|
||||
|
||||
On most linux distributions LightDM can be installed with the `lightdm` package.
|
||||
On most [Linux](/wiki/linux.md) distributions LightDM can be installed with the `lightdm` package.
|
||||
Additionally, `lightdm-gtk-greeter` and `xorg-server-xephyr` are recommended.
|
||||
This setup will work with [LightDM-GTK-Greeter](#lightdm-gtk-greeter) which is the default greeter.
|
||||
If another greeter is to be chosen `lightdm-gtk-greeter` does not have to be installed, but an
|
||||
@@ -15,9 +15,9 @@ For a guide on how to set the greeter navigate to the [greeter section](#greeter
|
||||
This section will also discuss various other greeters like the
|
||||
[LightDM-Mini-Greeter](#lightdm-mini-greeter).
|
||||
|
||||
This setup needs an `xsession`.
|
||||
An alternative to this is using `xinitrc` as an `xsession`.
|
||||
The process of this is desribed in the
|
||||
A system with [the X window system](/wiki/linux/x_window_system.md) setup needs a `xsession`.
|
||||
An alternative to this is using `xinitrc` as a `xsession`.
|
||||
The process of this is described in the
|
||||
[display manager entry](/wiki/linux/display_managers.md#use-xinitrc-as-xsession).
|
||||
Make sure to have a working `xsession` or `xinitrc`.
|
||||
If you are not sure about it, use the tests provided in the penultimate step.
|
||||
@@ -26,9 +26,26 @@ Then edit the config file `~/.dmrc` and edit the file to the following contents.
|
||||
|
||||
```txt
|
||||
[Desktop]
|
||||
Session=xinitrc
|
||||
Session=default
|
||||
```
|
||||
|
||||
Then create a symbolic link for a default session.
|
||||
|
||||
```sh
|
||||
ln -s /usr/share/xsessions/xinitrc.desktop /usr/share/xsessions/default.desktop
|
||||
```
|
||||
|
||||
For a [Wayland](/wiki/linux/wayland.md) do the same for your compositor and replace `<session>`
|
||||
with it.
|
||||
For example in case the system is set up with [the DWL compositor](/wiki/linux/suckless.md)
|
||||
`<session>` has to be removed with `dwl.desktop` and for Sway it will be `sway.desktop`.
|
||||
Check which session is created by your compositor.
|
||||
|
||||
```sh
|
||||
ln -s /usr/share/wayland-sessions/<session> /usr/share/wayland-sessions/default.desktop
|
||||
```
|
||||
|
||||
|
||||
Before finishing the setup the functionality should be tested.
|
||||
This can be done by using one or both of the following commands.
|
||||
|
||||
@@ -37,7 +54,7 @@ lightdm --test-mode --debug
|
||||
systemctl start lightdm.service
|
||||
```
|
||||
|
||||
Finally, the [SystemD](/wiki/linux/systemd.md) lightdm service needs to be enabled and reboot the
|
||||
Finally, the [systemd](/wiki/linux/systemd.md) `lightdm` service needs to be enabled and reboot the
|
||||
system.
|
||||
|
||||
```sh
|
||||
@@ -48,7 +65,7 @@ reboot
|
||||
## Greeters
|
||||
|
||||
LightDM features the option to choose between many different greeters.
|
||||
This section focusses on various greeters.
|
||||
This section focuses on various greeters.
|
||||
|
||||
The greeter can be set with the option `greeter-session` under the section `[Seat:*]` in the file
|
||||
`/etc/lightdm/lightdm.conf`.
|
||||
@@ -67,7 +84,7 @@ If no `greeter-session` is set the default will fall back to the
|
||||
|
||||
The [LightDM-GTK-Greeter](https://github.com/Xubuntu/lightdm-gtk-greeter) is the default greeter
|
||||
for LightDM.
|
||||
This is the default [greeter](#greeters) of [GTK](/wiki/linux/gtk.md) but others may be chosen.
|
||||
This is the default [greeter](#greeters) of [GTK](/wiki/linux/gtk.md), but others may be chosen.
|
||||
|
||||
### LightDM-Mini-Greeter
|
||||
|
||||
@@ -79,8 +96,7 @@ For the LightDM-Mini-Greeter to work correctly some settings have to be set in t
|
||||
The following lines show an example of this file.
|
||||
The most important changes have been done to set the `user` under `[greeter]`
|
||||
and `background-image` under `[greeter-theme]`.
|
||||
The background image path can vary, but lightdm has to be able to access the
|
||||
image.
|
||||
The background image path can vary, but LightDM has to be able to access the image.
|
||||
|
||||
```txt
|
||||
# LightDM Mini Greeter Configuration
|
||||
@@ -179,5 +195,5 @@ This section will focus on errors and the fixing of errors of LightDM.
|
||||
|
||||
### Bypass LightDM on Error
|
||||
|
||||
If it comes to problems that deny the login it can be useful to switch to another tty.
|
||||
If it comes to problems that deny the login it can be useful to switch to another TTY.
|
||||
This can be done by hitting the key combination `CTRL+ALT+F2`.
|
||||
|
||||
@@ -17,7 +17,7 @@ This can be done by using one or both of the following commands.
|
||||
systemctl start ly.service
|
||||
```
|
||||
|
||||
Finally, the [SystemD](/wiki/linux/systemd.md) Ly service needs to be enabled and reboot the
|
||||
Finally, the [systemd](/wiki/linux/systemd.md) Ly service needs to be enabled and reboot the
|
||||
system.
|
||||
|
||||
```sh
|
||||
|
||||
@@ -36,13 +36,13 @@ priority, `1` being the next highest and so on.
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
This section focusses on the troubleshooting of situations where the system does not connect
|
||||
This section focuses on the troubleshooting of situations where the system does not connect
|
||||
correctly.
|
||||
|
||||
### Restarting and Reenabling Wi-Fi
|
||||
|
||||
A useful chain of commands is the following.
|
||||
It will restart the [SystemD](/wiki/linux/systemd.md) service and enable the Wi-Fi device.
|
||||
It will restart the [systemd](/wiki/linux/systemd.md) service and enable the Wi-Fi device.
|
||||
|
||||
```sh
|
||||
systemctl restart NetworkManager
|
||||
|
||||
@@ -19,7 +19,7 @@ For one time synchronization of the time and date the `ntpdate` command can be
|
||||
used.
|
||||
The following command is an example for a one time sync.
|
||||
Note that the server has to be changed for different time zones.
|
||||
In this case a german time server is used.
|
||||
In this case a German time-server is used.
|
||||
|
||||
```sh
|
||||
ntpdate ptbtime1.ptb.de
|
||||
|
||||
@@ -37,7 +37,7 @@ and select either `Force Composition Timeline` or
|
||||
|
||||
On some operating systems like [Arch Linux](/wiki/linux/arch-linux.md) the newer versions of
|
||||
drivers are not compatible with Pascal GPUs anymore as explained in
|
||||
[the german Arch forum](https://www.archlinux.de/news/35689-Nvidia-Treiber-ab-Version-590-stellen-den-Support-fuer-Pascal-GPUs-ein).
|
||||
[the German Arch forum](https://www.archlinux.de/news/35689-Nvidia-Treiber-ab-Version-590-stellen-den-Support-fuer-Pascal-GPUs-ein).
|
||||
This is due to the drop of support for these cards from Nvidias site.
|
||||
If Pascal-GPUs are still used some minor changes need to be performed and some packets need to be
|
||||
replaced.
|
||||
|
||||
@@ -209,7 +209,7 @@ AbortOnFail
|
||||
|
||||
The following hook will use [reflector](https://xyne.dev/projects/reflector/) to update the pacman
|
||||
mirrorlist.
|
||||
It will use german mirrors (`-c de`), will list the fastest 15 mirrors (`-n 15`) and only do so if
|
||||
It will use German mirrors (`-c de`), will list the fastest 15 mirrors (`-n 15`) and only do so if
|
||||
the mirror was online in the last 24 hours (`-a 24`).
|
||||
It was found in a
|
||||
[reddit post by IBNash](https://www.reddit.com/r/archlinux/comments/dsnu81/hear_ye_archers_share_your_pacman_hooks/)
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# SystemD
|
||||
# systemd
|
||||
|
||||
SystemD is an [init system](/wiki/linux/init.md) for Linux systems.
|
||||
systemd is an [init system](/wiki/linux/init.md) for Linux systems.
|
||||
It is used for service configuration and startup.
|
||||
|
||||
## Usage
|
||||
@@ -54,9 +54,9 @@ Logs of the last start of the service can be found by running `systemctl status
|
||||
|
||||
Additionally, the `--user` flag can be set to start the service only for the current user.
|
||||
|
||||
### Retrieving the SystemD Logs
|
||||
### Retrieving the systemd Logs
|
||||
|
||||
SystemD logs can easily be found using the `journalctl` command.
|
||||
systemd logs can easily be found using the `journalctl` command.
|
||||
One of the most notable usages of the command is for checking the logs of the previous boot.
|
||||
This can be achieved by running the following command.
|
||||
|
||||
@@ -117,7 +117,7 @@ sudo systemctl restart systemd-logind
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
This section focusses on errors that correspond to the SystemD software.
|
||||
This section focusses on errors that correspond to the systemd software.
|
||||
|
||||
### Timed Out Waiting for Device `/dev/tpmrm0`
|
||||
|
||||
|
||||
@@ -11,19 +11,17 @@ Additionally, the installation of `tlp-rdw` is recommended, which is used to get
|
||||
radio devices.
|
||||
Afterward, the TLP [service](/wiki/linux/systemd.md#startstopenabledisable-a-service) needs to be
|
||||
started and enabled.
|
||||
In contrast to other
|
||||
[SystemD services](/wiki/linux/systemd.md#startstopenabledisable-a-service) this
|
||||
can be done by running `sudo tlp start` and running `systemctl enable tlp.service`.
|
||||
In contrast to other [systemd services](/wiki/linux/systemd.md#startstopenabledisable-a-service)
|
||||
this can be done by running `sudo tlp start` and running `systemctl enable tlp.service`.
|
||||
|
||||
## Configure Battery Charge Thresholds
|
||||
|
||||
There are two battery charge thresholds.
|
||||
The first is `START_CHARGE_THRESH` this threshold contains the battery charge
|
||||
level below which charging will begin.
|
||||
The first is `START_CHARGE_THRESH` this threshold contains the battery charge level below which
|
||||
charging will begin.
|
||||
`STOP_CHARGE_TRESH` is the second threshold.
|
||||
It describes up to which level the battery will be charged.
|
||||
Battery charge thresholds are used to limit the charging of the battery to
|
||||
extend the battery life.
|
||||
Battery charge thresholds are used to limit the charging of the battery to extend the battery life.
|
||||
|
||||
Thresholds can be set in the file `/etc/tlp.conf`.
|
||||
Search and edit the following lines according to your needs.
|
||||
@@ -33,4 +31,4 @@ START_CHARGE_THRESH_BAT0=75
|
||||
STOP_CHARGE_THRESH_BAT0=80
|
||||
```
|
||||
|
||||
This can also be achieved by using [tp-battery-mode](/wiki/linux/battery_saving.md#programs)
|
||||
This can also be achieved by using [tp-battery-mode](/wiki/linux/battery_saving.md#programs).
|
||||
|
||||
@@ -32,8 +32,7 @@ v4l2loopback can be manually started by running the following command.
|
||||
modprobe v4l2loopback card_label='V4L2 Loopback' video_nr=7 exclusive_caps=1
|
||||
```
|
||||
|
||||
`video_nr=7` states the device path to use with v4l2loopback - in this case
|
||||
`/dev/video7`.
|
||||
`video_nr=7` states the device path to use with v4l2loopback - in this case `/dev/video7`.
|
||||
This can be changed according to the needs.
|
||||
It is important that the device is not already in use by another application.
|
||||
|
||||
@@ -46,8 +45,8 @@ modprobe v4l2loopback card_label='OBS Virtual Camera','IP Webcam' video_nr=7,8 e
|
||||
|
||||
### Create Permanent V4L2 Devices
|
||||
|
||||
For an automatic start at boot via [SystemD](/wiki/linux/systemd.md) a service can be created - as
|
||||
described in [the SystemD entry](/wiki/linux/systemd.md#run-command-on-boot).
|
||||
For an automatic start at boot via [systemd](/wiki/linux/systemd.md) a service can be created - as
|
||||
described in [the systemd entry](/wiki/linux/systemd.md#run-command-on-boot).
|
||||
For v4l2loopback create the file `/etc/systemd/system/v4l2loopback.service` containing the
|
||||
following lines.
|
||||
|
||||
|
||||
@@ -26,7 +26,7 @@ correctly.
|
||||
### Restarting WPA Supplicant
|
||||
|
||||
Most of the problems regarding WPA Supplicant can be fixed by restarting the
|
||||
[SystemD](/wiki/linux/systemd.md) service with the following command.
|
||||
[systemd](/wiki/linux/systemd.md) service with the following command.
|
||||
|
||||
```sh
|
||||
systemctl restart wpa_supplicant
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
# X Window System
|
||||
|
||||
X Window System - also called X and X11 according to the current version - is a protocoll for
|
||||
handling the display of the most unix-like operating systems.
|
||||
[Xorg](https://www.x.org/wiki/) is the most used implementation of the X protocoll.
|
||||
X Window System - also called X and X11 according to the current version - is a protocol for
|
||||
handling the display of the most Unix-like operating systems.
|
||||
[X.Org](https://www.x.org/wiki/) is the most used implementation of the X protocol.
|
||||
It is maintained by the [X.Org Foundation](https://x.org/wiki/).
|
||||
|
||||
## Usage
|
||||
@@ -26,7 +26,7 @@ The screen can be run by simply running the following command.
|
||||
slock
|
||||
```
|
||||
|
||||
By default this will not be run automatically when the computer goes into sleep.
|
||||
By default, this will not be run automatically when the computer goes into sleep.
|
||||
This can be changed by installing and using `xss-lock` like the following example shows.
|
||||
|
||||
```sh
|
||||
@@ -43,7 +43,7 @@ For this navigate to the [corresponding section](#turning-off-the-screen).
|
||||
|
||||
Windows can be killed with the utility `xkill`.
|
||||
Depending on the [distribution](/wiki/linux.md#distributions) used it maybe has to be installed.
|
||||
It often is bundled in a package named `xorg-xkill`.
|
||||
It is often bundled in a package named `xorg-xkill`.
|
||||
By running `xkill` the mouse cursor will turn into an x.
|
||||
With the mouse the window to close can then be selected.
|
||||
|
||||
@@ -87,7 +87,7 @@ EndSection
|
||||
|
||||
This section describes the handling of keyboards by X.
|
||||
|
||||
##### Change Keyboardlayout
|
||||
##### Change Keyboard Layout
|
||||
|
||||
To temporarily change the layout of the keyboard just run `setxkbmap <your preferred layout>`.
|
||||
For a permanent change run `localectl set-x11-keymap <your preferred layout>`.
|
||||
@@ -107,7 +107,7 @@ layouts.
|
||||
|
||||
In many languages there are ligatures (for example `œ`) and diacritics (for example `ç`).
|
||||
An easy way to write them is by using the compose button.
|
||||
Using the compose button these special symbols can be composed from their parts.
|
||||
Using the compose button these special symbols can be composed of their parts.
|
||||
The `ç` can be written by chaining compose with `,` and `c`.
|
||||
The `œ` can be written by chaining compose with `o` and `e`.
|
||||
There are many other diacritics and ligatures that can be written this way.
|
||||
@@ -115,8 +115,8 @@ There are many other diacritics and ligatures that can be written this way.
|
||||
To temporarily set up a compose key the following command can be used.
|
||||
It will set the given key `<compose>` (for example the right control key with `rctrl`) to act as
|
||||
the compose key when tapped.
|
||||
`<layout>` specifies the layout of the keymap (for example german with `de`).
|
||||
If it is omitted the english `en` layout will be set.
|
||||
`<layout>` specifies the layout of the keymap (for example German with `de`).
|
||||
If it is omitted the English `en` layout will be set.
|
||||
|
||||
```sh
|
||||
setxkbmap -layout <layout> -option compose:<compose>
|
||||
@@ -158,7 +158,7 @@ EndSection
|
||||
```
|
||||
|
||||
Another option to do this is by using the command `xset`.
|
||||
An example for this are the follwing commands which will enable the screensaver to act upon 10
|
||||
An example for this are the following commands which will enable the screensaver to act upon 10
|
||||
minutes of inactivity.
|
||||
|
||||
```sh
|
||||
@@ -166,7 +166,7 @@ xset s on
|
||||
xset s 600
|
||||
```
|
||||
|
||||
For more informations on this visit the
|
||||
For more information on this visit the
|
||||
[Arch wiki](https://wiki.archlinux.org/title/Session_lock#DPMS).
|
||||
|
||||
##### Adjust DPI and UI Scale
|
||||
@@ -181,7 +181,7 @@ Xft.dpi: 100
|
||||
```
|
||||
|
||||
Afterward, `~/.config/xorg/xpcspec` needs to be sourced in the `~/.xinitrc` file.
|
||||
For this to work the following line needs to be added into the `~/.xinitrc` file .
|
||||
For this to work the following line needs to be added into the `~/.xinitrc` file.
|
||||
|
||||
```sh
|
||||
[ -f "$HOME/.config/xorg/xpcspec" ] && xrdb -merge "$HOME/.config/xorg/xpcspec"
|
||||
@@ -205,7 +205,7 @@ As written by
|
||||
there are two ways to change this property.
|
||||
If the change is only needed temporarily
|
||||
`xinput set-prop <id> "libinput Middle Emulation Enabled" <flag>` can be run.
|
||||
`<id>` is the identifier of the mouse and <flag> is `0` for disabling and `1` for enabling the
|
||||
`<id>` is the identifier of the mouse and `<flag>` is `0` for disabling and `1` for enabling the
|
||||
middle mouse button.
|
||||
For permanent change of the property a change or addition to
|
||||
`/etc/X11/xorg.conf.d/40-libinput.conf` can be made.
|
||||
@@ -241,7 +241,7 @@ For that search for the package `xdg-desktop-portal` or a similar named one usin
|
||||
[package manager](/wiki/linux/package_manager.md).
|
||||
If it is installed check if it starts up correctly by using the command
|
||||
`systemctl --user status xdg-desktop-portal` as described in the
|
||||
[SystemD entry](/wiki/linux/systemd.md#startstopenabledisable-a-service-and-retrieve-its-logs).
|
||||
[systemd entry](/wiki/linux/systemd.md#startstopenabledisable-a-service-and-retrieve-its-logs).
|
||||
|
||||
A possible error is `cannot open display` as it was described and fixed by rockzombie2 and V1del in
|
||||
an [Arch Linux](/wiki/linux/arch-linux.md)
|
||||
@@ -253,7 +253,7 @@ systemctl --user import-environment DISPLAY XAUTHORITY
|
||||
systemctl --user restart xdg-desktop-portal
|
||||
```
|
||||
|
||||
If that works make sure the Xorg configs are sourced for users aswell.
|
||||
If that works make sure the X configs are sourced for users as well.
|
||||
It is possible that the following code block is missing in the local `.xinitrc`.
|
||||
This would create similar errors to the ones experienced.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user