mirror of
https://github.com/tiyn/wiki.git
synced 2025-08-04 20:47:45 +02:00
Compare commits
No commits in common. "d1269ac6583214efb006142f3a7bfd66c7c1400e" and "8cb32856e2777c61bc82a319c71897acc85ea63b" have entirely different histories.
d1269ac658
...
8cb32856e2
@ -1,39 +0,0 @@
|
|||||||
# Kernel
|
|
||||||
|
|
||||||
The [Linux](/wiki/linux.md) kernel is an open-source Unix-like computer operating system kernel.
|
|
||||||
|
|
||||||
## Versions
|
|
||||||
|
|
||||||
There are a few possible kernel version.
|
|
||||||
|
|
||||||
### Stable-Version: `linux`
|
|
||||||
|
|
||||||
The stable version of the [Linux](/wiki/linux.md) kernel can usually be found in a package called
|
|
||||||
`linux` and is usually installed from the start or in the recommended setup.
|
|
||||||
|
|
||||||
### Zen-Version: `linux-zen`
|
|
||||||
|
|
||||||
The zen kernel is a collaborative project of kernel hackers to provide the best
|
|
||||||
[Linux](/wiki/linux.md) kernel for everyday systems.
|
|
||||||
Especially the response time of the system under load
|
|
||||||
[is said to be better](https://github.com/zen-kernel/zen-kernel/wiki/Detailed-Feature-List#zen-kernel-improvements).
|
|
||||||
This will - for example - make the system less stuttery when something is compiled.
|
|
||||||
Desktop and gaming systems will benefit the most.
|
|
||||||
|
|
||||||
To setup the zen kernel do the following. Firstly install the packages `linux-zen` and
|
|
||||||
`linux-zen-header`.
|
|
||||||
Afterwards open the file `boot/loader/entries/arch.conf` and change the following lines.
|
|
||||||
|
|
||||||
```txt
|
|
||||||
linux /vmlinuz-linux
|
|
||||||
initrd /initramfs-linux.img
|
|
||||||
```
|
|
||||||
|
|
||||||
To look like the following lines.
|
|
||||||
|
|
||||||
```txt
|
|
||||||
linux /vmlinuz-linux-zen
|
|
||||||
initrd /initramfs-linux-zen.img
|
|
||||||
```
|
|
||||||
|
|
||||||
Afterwards the system should be rebooted for the change to take effect.
|
|
||||||
@ -131,17 +131,3 @@ pacman-key --refresh-keys
|
|||||||
The error `the following untracked working tree files would be overwritten` can happen when the
|
The error `the following untracked working tree files would be overwritten` can happen when the
|
||||||
cache features a changed version of the files used by yay to update the package.
|
cache features a changed version of the files used by yay to update the package.
|
||||||
This can easily be fixed by removing the cache of the corresponding package.
|
This can easily be fixed by removing the cache of the corresponding package.
|
||||||
|
|
||||||
#### Python `ModuleNotFoundError: No module named...`
|
|
||||||
|
|
||||||
This section is based on a
|
|
||||||
[StackOverflow post by Helen](https://stackoverflow.com/questions/55923868/how-to-fix-modulenotfounderror-no-module-named-setuptools).
|
|
||||||
|
|
||||||
In this case the error stems from a missing package.
|
|
||||||
Normally it can easily be fixed by installing that corresponding package.
|
|
||||||
But please note that `pyenv` can hide packages if the global Python version is set to something
|
|
||||||
other than `system`.
|
|
||||||
This is especially the case on [Arch Linux-systems](/wiki/linux/arch-linux.md) because Python
|
|
||||||
packages are also installed via [Pacman or Yay](#arch-linux-pacman-and-yay).
|
|
||||||
In this case the global Version has to be changed to `system` or the package installed to the
|
|
||||||
non-system Python version.
|
|
||||||
|
|||||||
@ -1,23 +0,0 @@
|
|||||||
# swayidle
|
|
||||||
|
|
||||||
swayidle is an idle manager for [Wayland](/wiki/linux/wayland.md).
|
|
||||||
|
|
||||||
## Setup
|
|
||||||
|
|
||||||
On most Linux distributions swayidle can be installed with the `swayidle` package.
|
|
||||||
|
|
||||||
## Usage
|
|
||||||
|
|
||||||
To run swayidle it has to be called - preferably after the boot process.
|
|
||||||
An example of this will look like the following.
|
|
||||||
This will [suspend-then-hibernate](/wiki/linux/systemd.md#change-suspend-and-hibernate-behaviour)
|
|
||||||
the system after 30 seconds.
|
|
||||||
Additionally a program [xss-lock](/wiki/linux/xss-lock.md) has to be used to let swayidle know to
|
|
||||||
use a specific lock command.
|
|
||||||
|
|
||||||
```sh
|
|
||||||
#!/bin/sh
|
|
||||||
|
|
||||||
exec swayidle -w \
|
|
||||||
timeout 30 'systemctl suspend-then-hibernate'
|
|
||||||
```
|
|
||||||
@ -64,39 +64,6 @@ This can be achieved by running the following command.
|
|||||||
journalctl -b-1
|
journalctl -b-1
|
||||||
```
|
```
|
||||||
|
|
||||||
### Change Suspend and Hibernate Behaviour
|
|
||||||
|
|
||||||
The behaviour of suspend and hibernation can be changed in the file `/etc/systemd/sleep.conf`.
|
|
||||||
One of the most important variables is the one to set the hibernation delay time.
|
|
||||||
This time will be used to determine the time that is taken from suspend to hibernation if
|
|
||||||
suspend-to-hibernate is called.
|
|
||||||
The following line will set this to 10 minutes.
|
|
||||||
|
|
||||||
```txt
|
|
||||||
HibernateDelaySec=10min
|
|
||||||
```
|
|
||||||
|
|
||||||
### Handle Power Key and Lid Seitch
|
|
||||||
|
|
||||||
The management of power keys and lid switches is handled in the file `/etc/systemd/logind.conf`.
|
|
||||||
The following line will set the behaviour of the power key to hibernate. The default for this would
|
|
||||||
be to shutdown the system.
|
|
||||||
|
|
||||||
```txt
|
|
||||||
HandlePowerKey=hibernate
|
|
||||||
```
|
|
||||||
|
|
||||||
The same can also be done to determine the action taken when the lid is closed.
|
|
||||||
By default the closing of the lid will result in suspending the system.
|
|
||||||
The following lines will change this to suspend-then-hibernate.
|
|
||||||
|
|
||||||
```txt
|
|
||||||
HandleLidSwitch=suspend-then-hibernate
|
|
||||||
```
|
|
||||||
|
|
||||||
For further behaviour of the suspend and hibernate actions check the
|
|
||||||
[corresponding section](#change-suspend-and-hibernate-behaviour).
|
|
||||||
|
|
||||||
## Troubleshooting
|
## Troubleshooting
|
||||||
|
|
||||||
This section focusses on errors that correspond to the SystemD software.
|
This section focusses on errors that correspond to the SystemD software.
|
||||||
|
|||||||
@ -1,18 +0,0 @@
|
|||||||
# Waydroid
|
|
||||||
|
|
||||||
[Waydroid](https://waydo.id) is a container-based approach to boot a full
|
|
||||||
[Android system](/wiki/android.md) on a regular [Linux system](/wiki/linux.md)
|
|
||||||
|
|
||||||
## Setup
|
|
||||||
|
|
||||||
On most [Linux distributions](/wiki/linux.md) Waydroid can be installed with the `waydroid`
|
|
||||||
package.
|
|
||||||
|
|
||||||
After setting up the system has to be initialized.
|
|
||||||
When running `waydroid status` it will also tell, if initialization is needed.
|
|
||||||
|
|
||||||
The initialization can easily be done by running the following command.
|
|
||||||
|
|
||||||
```sh
|
|
||||||
waydroid init
|
|
||||||
```
|
|
||||||
@ -1,4 +0,0 @@
|
|||||||
# Wayland
|
|
||||||
|
|
||||||
[Wayland](https://wayland.freedesktop.org/) is a replacement for the
|
|
||||||
[X11 window system](/wiki/linux/x_window_system.md).
|
|
||||||
@ -1,19 +0,0 @@
|
|||||||
# xss-lock
|
|
||||||
|
|
||||||
xss-lock is an external screen locker for [X11 Window Systems](/wiki/linux/x_window_system.md).
|
|
||||||
Using xwayland it can also be used for [Wayland](/wiki/linux/wayland.md) systems.
|
|
||||||
|
|
||||||
## Setup
|
|
||||||
|
|
||||||
On most Linux distributions swayidle can be installed with the `xss-lock` package.
|
|
||||||
|
|
||||||
## Usage
|
|
||||||
|
|
||||||
To run xss-lock it has to be called - preferably after the boot process.
|
|
||||||
An example of this will look like the following.
|
|
||||||
This command makes the system use `swaylock` if the system is put to
|
|
||||||
[sleep](/wiki/linux/systemd.md#change-suspend-and-hibernate-behaviour).
|
|
||||||
|
|
||||||
```sh
|
|
||||||
xss-lock -- swaylock
|
|
||||||
```
|
|
||||||
Loading…
x
Reference in New Issue
Block a user