Arch Linux折腾笔记
发表更新 xeonds 1 小时读完 (大约10104个字)0次访问

Arch Linux折腾笔记

安装

参考 Arch Wiki 或者参考这个简化版教程：https://arch.icekylin.online/。过程按照教程一步步折腾就ok，只要注意区分清楚各个分区，别不小心把数据分区给格式化了就行。联网是安装Arch的必须项，所以请保持网络畅通。另外，建议安装镜像最好在安装完成后继续保留着，应急情况下（比如滚挂了）可以用arch-chroot来应急重装内核之类的。

至于Arch经常被吐槽滚挂了的原因，主要是源自Arch的更新策略比较激进，更新完成后，会直接删除老内核，比起一般的更新策略更容易出现依赖问题造成“滚挂了“。

桌面环境、cn源、透明代理之类的配置，也可以参考上面的教程。关于透明代理，也可以参考这篇文章。

美化

这点上因人而异。我装了layan主题之后，再换个壁纸，装个latte就差不多了。我的原则是，美化差不多就行，但是前提是别影响到系统性能。

显示适配

单显示器的配置很简单，改下dpi缩放就基本ok。如果是多显示器的话，就会复杂一些。参考下面的公式：

1
2
3
# 假设HiDPI显示器的分辨率是AxB，普通分辨率显示器的分辨率是CxD 
# 并且外置显示器的缩放比率是ExF
xrandr --output eDP-1 --auto --output HDMI-1 --auto --panning [C*E]x[D*F]+[A]+0 --scale [E]x[F] --right-of eDP-1

根据上面的公式来设置，基本上能搞定。当然，如果想调整的是内置HiDPI显示器分辨率，就得调整最后panning的A为Ax[A的缩放比率]。

参考链接

pacman入门

问了问GPT，大概做了下笔记如下：

1
2
3
4
5
6
7
8
9
sudo pacman -Sy                     # 更新软件包数据库
sudo pacman -S package_name         # 安装软件包，可批量安装
sudo pacman -R package_name         # 删除软件包但保留配置
sudo pacman -Rn package_name        # 删除包和配置
sudo pacman -Syu                    # 升级所有已安装的包
sudo pacman -Sc                     # 清理pacman缓存的旧包
sudo pacman -Ss search_term         # 查找软件包
sudo pacman -Si package_name        # 查找软件包信息
sudo pacman -Rns $(pacman -Qdtq)    # 删除未使用依赖包

另外，Syu和Syyu的区别在于后者强制刷新了软件仓库缓存。后者虽然更新比较及时，但是用得多对于软件源仓库并不友好，而且浪费资源，不宜过于频繁使用。

最底下那个移除孤儿包的操作少用，用的时候手动确认是否包括重要依赖。

另外还有个操作，就是完整备份安装过的包列表，然后在新的系统上重新安装，这个用pacman可以做到。

1
2
pacman -Qqe > installed_packages.txt                # 备份当前系统上所有已经明确安装的包
sudo pacman -S --needed - < installed_packages.txt  # 只安装其中没有安装过的包

不过使用这个操作的时候，记得得保证清单的实时性，因为arch滚动更新，系统一直是新的，备份列表太久没更新的话在新系统上安装会有依赖，兼容等等问题。

启用外部ssh连接

如果想从外部连接到Arch的电脑上，只要安装了openssh就行。Arch默认不会启动sshd，所以我们得手动开启：

1
systemctl start sshd

在命令行连接Wi-Fi

在完成安装后，启动NetworkManager：

1
sudo systemctl enable --now NetworkManager

然后使用nmcli来连接Wi-Fi：

1
2
3
nmcli dev wifi list
# 后面的password部分不指定的话，会自动要求输入
nmcli dev wifi connect "SSID" password "password"

使用TimeShift备份系统

TimeShift是一个很好用的系统备份软件，特别是结合了btrfs之后，备份的体积比借助rsync时更小。

折腾系统时不时可能滚挂，这种时候有个定期创建的映像就很有用了。

1
2
sudo timeshift --list # 获取快照列表
sudo timeshift --restore --snapshot '20XX-XX-XX_XX-XX-XX' --skip-grub # 选择一个快照进行还原，并跳过 GRUB 安装，一般来说 GRUB 不需要重新安装

如果恢复后无法使用，用安装盘通过arch-chroot进去系统，然后手动更改subvolid来手动修复，或者直接删除subvolid：

1
2
3
4
# 获取subvolid
sudo btrfs sub list -u /
# 编辑,根据自己情况，修复
vim /etc/fstab

重启显示管理器（Xorg/Wayland）

1
sudo systemctl restart display-manager

Vim

装上Arch之后我很快就把Vim装上了。结果发现没法和系统剪贴板联动。在Vim里边检查has(clipboard)之后发现，好像这个Vim不支持剪贴板。

解决方法：装gvim：sudo pacman -S gvim。会提示你是否卸载Vim，选是，配置不会删除所以放心删。安装完了之后你就会发现Vim还能用，而且剪贴板功能好了：

桌面目录映射

今天看到群里一个老哥家目录下的文件都堆到桌面了，顺便了解了一下关于桌面目录映射的问题。因为有时候中文模式创建的家目录下的文件夹都是中文，那个老哥就是改成英文目录的时候遇到了这个问题。

XDG_DESKTOP_DIR这个环境变量的介绍，在archWiki上也能翻到。

XDG_DESKTOP_DIR是一个环境变量，用于指定用户的桌面文件夹的位置。它是XDG Base Directory规范1的一部分，该规范定义了一些标准的用户目录，如音乐、图片、下载等，以及一些用于存储配置、缓存、数据和状态的目录。XDG_DESKTOP_DIR的默认值是$HOME/Desktop，但用户可以通过编辑~/.config/user-dirs.dirs文件或使用xdg-user-dirs-update命令来修改它2。

KDE桌面环境遵循XDG Base Directory规范，并使用XDG_DESKTOP_DIR变量来确定桌面文件夹的位置。如果用户更改了XDG_DESKTOP_DIR的值，KDE会自动更新桌面设置，并将桌面文件夹更改为新的位置。这样，用户可以灵活地管理自己的桌面文件夹，而不影响其他应用程序或桌面环境3。

所以出问题的话看看.config底下配置炸没炸就行。

添加多系统启动项

在安装Arch的时候，会发现中间有一步是sudo vim /etc/default/grub然后grub-mkconfig -o /boot/grub/grub.cfg。这一步就是先编辑grub的配置，然后生成grub文件到/boot/grub/下的配置文件中。因此，我们如果突然心血来潮想装个Windows玩玩谁装啊，就可以改改grub配置让它为我们添加启动项。

因为最终的配置项是由grub-mkconfig生成的，所以并不推荐直接修改这个文件。更好的做法是安装os-prober，然后挂载其他系统的分区，并编辑grub配置文件启用os探测，最后再用grub-mkconfig生成新的grub启动项文件。

至于为啥grub现在默认禁用掉了os-prober，注释里边说的是因为安全问题所以禁用掉了。

代理配置

既然都上Arch了，那代理软件不得整个自由点的？直接扔了cfw，拥抱clash-core。具体配置教程参考这篇，我给个简洁版的：

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
# 实在懒得sudo了
# 不过记得看清命令再回车
sudo su
pacman -S clash
mkdir -p /etc/clash

# 然后从provider那里下载yaml配置文件
# 假设文件名为config.yaml
mv ./config.yaml /etc/clash/
# 设置控制面板路径
# 我这里的控制面板路径在/etc/clash/clash-dashboard
echo 'external-ui: clash-dashboard' >> /etc/clash/config.yaml

# 配置环境变量，配完了记得重启/重新登陆一下
cat << EOF >> /etc/environment
https_proxy=http://127.0.0.1:7890
http_proxy=http://127.0.0.1:7890
all_proxy=http://127.0.0.1:7890
EOF

# 配置systemd服务项
# 配完了就能开机自启动了哦
cat << EOF > /etc/systemd/system/clash.service
[Unit]
Description=Clash daemon, A rule-based proxy in Go.
After=network.target

[Service]
Type=simple
Restart=always
ExecStart=/usr/bin/clash -d /etc/clash # /usr/bin/clash 为绝对路径，请根据你实际情况修改

[Install]
WantedBy=multi-user.target
EOF

###############
# clash，启动！
###############
systemctl enable --now clash.service

里边比较重要的一步是配置环境变量env，上回配置的时候忘了加http前缀，结果系统里边啥玩意都不认我的代理设置。

哦对，配置完成之后还得在系统里边设置好代理：

悲：cfw跑路之后clash-core也跑路了
然后所有client都跑路了
为clash家族 + 1s
以及我的评价是：

以及某作者的睿频：
最适合这个民族的其实是一群小
白围着大大转，大大通过小白的夸奖获得自我满足，然后小白的吃喝拉撒都包给大大解决的模式。通过这个项目我感觉我已经彻底认识到这个民族的前面为什么会有一堵墙了。没有墙哪来的大大。所以到处都是什么附件回帖可见，等级多少用户组可见，一个论坛一个大大供小白跪舔，不需要政府造墙，网民也会自发造墙。这尼玛连做个翻墙软件都要造墙，真是令人叹为观止。这是一个造了几干年墙的保守的农耕民族，缺乏对别人的基本尊重，不愿意分享，喜欢遮遮掩掩，喜欢小圈子抱团，大概这些传统是改不掉了吧。

另外还有一个，就是切换节点必须得使用clash的控制端口（在config.yaml中给出，一般是9090），所以还必须得有个控制面板。一般Windows平台都是用已经似了的Clash For Windows作为控制面板的，而Linux这边使用https://clash.razord.top/也就是也已经似了的Clash的官方控制面板作为控制面板的。实在不行了可以用命令行下的TUI工具clashctl来手动切换节点，应该也能用。

RDP连接Windows

用Arch多了，有时候得偶尔远程一下Windows。配置了半天Remmina+freerdp，可能这玩意和我风水不合吧，半天跑不起来。遂尝试了下rdesktop，秒连（也不知道为啥）：

1
2
sudo pacman -S rdesktop
rdesktop 114.5.1.4

然后输账号密码登陆就行了。因为暂时这样就够用所以就没咋折腾。

X11迁移Wayland

主要动机：支持一下双屏不同缩放的功能，不然一个高分屏+一个普通1080p的组合太痛苦了。

1
2
3
4
5
6
pacman -Qi wayland  # 已安装则继续，否则安装
sudo pacman -S --needed wayland
yay -S sddm-git     # 必须得是sddm-git，其他版本好像没完善的Wayland支持
pacman -S --needed xorg-xwayland xorg-xlsclients qt5-wayland glfw-wayland
pacman -S --needed plasma kde-applications
pacman -S --needed plasma-wayland-session

按照这里给出的流程，装完上面的包之后，Logout之后应该就能在左下角看到登陆Plasma(Wayland)的提示了。

你还能通过查看 $XDG_SESSION_TYPE 变量来 核实你是否在运行 Wayland。

先去装了，一会回来记录。

装完了，兼容性没啥大问题，我甚至没重启，只是重新登陆了下。就是latte-dock的图标缩放看着怪怪的，而且桌面小组件也乱飞了。以及，输入法好像不太对劲，在firefox以外的地方皮肤会丢失。

刚重新设置了下屏幕排列，现在能单独设置两块屏幕的缩放了，爽。就是高分屏看着有点糊，以及字体缩放问题，还有这个fcitx也不太对劲。

关于fcitx，系统给了一段报错：

1
Fcitx should be launched by KWin under KDE Wayland in order to use Wayland input method frontend. This can improve the experience when using Fcitx on Wayland. To configure this, you need to go to "System Settings" -> "Virtual keyboard" and select "Fcitx 5" from it. You may also need to disable tools that launches input method, such as imsettings on Fedora, or im-config on Debian/Ubuntu. For more details see https://fcitx-im.org/wiki/Using_Fcitx_5_on_Wayland#KDE_Plasma

先重启下看看吧。

草了，重启回来变回x11 seession了。找找默认值在哪保存着吧。

找到了，在/usr/lib/sddm/sddm.conf.d/default.conf里边，有一个DisplayServer=x11的项，把x11改为wayland应该就行了。重启看看。

好像不太行，而且现在切不过去Wayland了，坏。

把设置都改回去了，现在好像能进去了。但是还是默认进入x11的plasma桌面。

哎，把用户空间的那个sddm configuration改了一下，删了里边的[Autologin]底下的session=的值，重启下试试。以及又得到了一段关于fcitx的建议：

1
Detect GTK_IM_MODULE and QT_IM_MODULE being set and Wayland Input method frontend is working. It is recommended to unset GTK_IM_MODULE and QT_IM_MODULE and use Wayland input method frontend instead. For more details see https://fcitx-im.org/wiki/Using_Fcitx_5_on_Wayland#KDE_Plasma

好好好搞定了。按照上面的设置先屏蔽了俩环境变量，然后删除了默认值，现在系统已经处于完全可用的状态。回头有时间了整理整理过程。

Fri 22 Dec 2023 05:14:55 PM CST

编辑：这个选项不用在命令行里修改，直接去系统设置里边的Startup nad shutdown->Login Screen->Behavior里边修改...with session = 的选项就行了。

又出问题了

小笔记本上的arch的kde以至于其中的所有程序突然都变得特别卡。最奇怪的是这会的系统资源专用状况完全没有多高，CPU%，MEM37.4%的占用率应该很健康了吧。

觉得的卡顿是因为我发现就连tmux里边开个vim写文档都卡得不行了才觉得不对劲。

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
systemd-+-NetworkManager
        |-bluetoothd
        |-clash
        |-dbus-daemon
        |-polkitd
        |-rtkit-daemon
        |-sddm-+-Xorg
        |      `-sddm-helper---startplasma-x11
        |-systemd-+-(sd-pam)
        |         |-adb
        |         |-agent
        |         |-at-spi-bus-laun---dbus-daemon
        |         |-at-spi2-registr
        |         |-chrome_crashpad
        |         |-dbus-daemon
        |         |-dconf-service
        |         |-fcitx5
        |         |-gmenudbusmenupr
        |         |-gvfs-udisks2-vo
        |         |-gvfsd-+-gvfsd-dnssd
        |         |       |-gvfsd-network
        |         |       `-gvfsd-trash
        |         |-gvfsd-fuse
        |         |-gvfsd-metadata
        |         |-kaccess
        |         |-kactivitymanage
        |         |-kded5
        |         |-kglobalaccel5
        |         |-konsole---bash---tmux: client
        |         |-krunner---qq-+-qq---qq
        |         |              |-qq---2*[qq]
        |         |              `-qq
        |         |-kscreen_backend
        |         |-ksmserver---DiscoverNotifie
        |         |-ksystemstats
        |         |-kwalletd5
        |         |-kwin_x11
        |         |-latte-dock
        |         |-linuxqq
        |         |-obexd
        |         |-org_kde_powerde
        |         |-pipewire
        |         |-pipewire-media-
        |         |-plasmashell---crow
        |         |-polkit-kde-auth
        |         |-pulseaudio---gsettings-helpe
        |         |-tmux: server-+-2*[bash---vim]
        |         |              `-bash---sudo---sudo---pstree
        |         |-2*[xdg-desktop-por]
        |         |-xdg-document-po---fusermount3
        |         |-xdg-permission-
        |         `-xembedsniproxy
        |-systemd-journal
        |-systemd-logind
        |-systemd-udevd
        |-udisksd
        |-upowerd
        `-wpa_supplicant

上面是sudo pstree -T的输出，感觉这种卡顿可能就是de内存溢出了。理论上我感觉只要重启一下sddm马上就能变流畅。但是在这之前我想知道更详细的信息。

先把qq关了试试。不出所料还是很卡。上google搜一下吧。

草了，看到一个哥们系统偶尔卡顿最后发现是SSD挂掉的前兆。想起来这个本子用的是三星的老固态，系统盘的文件系统是btrfs；前几天还看群里某群u吐槽说btrfs在他那边对于固态寿命损伤挺严重的。也不知道是不是btrfs的问题。不过好在重要数据都有备份，丢了也不心疼，全从服务器上sync下来就行了。

不过应该这次不是固态的问题，应该还是sddm本身的问题，不然很难解释怎么所有gui里边的东西都开始卡顿了

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
TIME                           PID  UID  GID SIG     COREFILE EXE                           SIZE
Sun 2023-10-29 23:52:21 CST   2030 1000 1000 SIGBUS  missing  /chrome_crashpad_handler         -
Thu 2023-11-02 13:07:56 CST   3084    0    0 SIGABRT none     /usr/bin/fcitx5-remote           -
Thu 2023-11-02 17:15:49 CST  36261 1000 1000 SIGABRT missing  /usr/bin/clashctl                -
Thu 2023-11-02 23:44:53 CST   1795 1000 1000 SIGTRAP missing  /tmp/.mount_linuxqFrCYKS/qq      -
Sat 2023-11-04 18:43:36 CST   1640 1000 1000 SIGABRT missing  /usr/bin/clashctl                -
Sat 2023-11-04 18:45:41 CST   2255    0    0 SIGABRT none     /usr/bin/fcitx5-remote           -
Sat 2023-11-04 18:46:34 CST   2300    0    0 SIGABRT none     /usr/bin/fcitx5-remote           -
Sun 2023-11-05 18:16:28 CST  19274 1000 1000 SIGABRT missing  /opt/vscodium-bin/codium         -
Sun 2023-11-05 18:16:30 CST  19330 1000 1000 SIGABRT missing  /opt/vscodium-bin/codium         -
Sun 2023-11-05 22:13:13 CST  14279 1000 1000 SIGBUS  missing  /chrome_crashpad_handler         -
Thu 2023-11-09 23:30:51 CST  14724 1000 1000 SIGTRAP missing  /qq                              -
Thu 2023-11-09 23:38:16 CST  15804 1000 1000 SIGABRT missing  /usr/bin/clashctl                -
Fri 2023-11-10 01:08:53 CST  14773 1000 1000 SIGBUS  missing  /chrome_crashpad_handler         -
Tue 2023-11-14 09:04:45 CST   5996 1000 1000 SIGABRT missing  /usr/bin/clashctl                -
Tue 2023-11-14 09:47:58 CST  10033 1000 1000 SIGABRT missing  /usr/bin/clashctl                -
Tue 2023-11-14 10:15:41 CST  75599 1000 1000 SIGABRT missing  /usr/bin/clashctl                -
Tue 2023-11-14 10:30:25 CST  13990 1000 1000 SIGABRT missing  /usr/bin/clashctl                -
Tue 2023-11-14 17:47:23 CST    575 1000 1000 SIGABRT missing  /usr/bin/plasmashell             -
Tue 2023-11-14 21:00:24 CST  18347 1000 1000 SIGABRT missing  /usr/bin/plasmashell             -
Wed 2023-11-15 00:34:08 CST  26489 1000 1000 SIGABRT missing  /usr/bin/clashctl                -
Wed 2023-11-15 01:14:11 CST  28479 1000 1000 SIGABRT missing  /usr/bin/clashctl                -
Wed 2023-11-15 11:34:37 CST  19955 1000 1000 SIGSEGV missing  /usr/bin/plasmashell             -
Wed 2023-11-15 23:54:02 CST  36282 1000 1000 SIGSEGV missing  /opt/visual-studio-code/code     -
Fri 2023-11-17 00:45:55 CST  16467 1000 1000 SIGBUS  missing  /chrome_crashpad_handler         -
Fri 2023-11-17 00:45:56 CST  40168 1000 1000 SIGTRAP missing  /qq                              -
Sat 2023-11-18 01:12:06 CST  17969 1000 1000 SIGABRT missing  /usr/bin/ccze                    -
Sat 2023-11-18 01:12:06 CST  15257 1000 1000 SIGABRT missing  /usr/bin/ccze                    -
Sat 2023-11-18 01:12:06 CST  17286 1000 1000 SIGABRT missing  /usr/bin/ccze                    -
Sat 2023-11-18 01:12:56 CST  19088 1000 1000 SIGABRT missing  /usr/bin/ccze                    -
Sat 2023-11-18 01:12:56 CST  19770 1000 1000 SIGABRT missing  /usr/bin/ccze                    -
Sat 2023-11-18 01:12:56 CST  18906 1000 1000 SIGABRT missing  /usr/bin/ccze                    -
Sat 2023-11-18 01:12:56 CST  19731 1000 1000 SIGABRT missing  /usr/bin/ccze                    -
Sat 2023-11-18 01:12:56 CST  19689 1000 1000 SIGABRT missing  /usr/bin/ccze                    -
Sat 2023-11-18 01:12:57 CST  19591 1000 1000 SIGABRT missing  /usr/bin/ccze                    -
Sat 2023-11-18 01:13:10 CST  25066 1000 1000 SIGABRT missing  /usr/bin/ccze                    -
Sat 2023-11-18 01:13:11 CST  25053 1000 1000 SIGABRT missing  /usr/bin/ccze                    -
Sat 2023-11-18 01:13:11 CST  20320 1000 1000 SIGABRT missing  /usr/bin/ccze                    -
Sat 2023-11-18 01:13:11 CST  24308 1000 1000 SIGABRT missing  /usr/bin/ccze                    -
Sat 2023-11-18 01:13:13 CST  25240 1000 1000 SIGABRT missing  /usr/bin/ccze                    -
Sat 2023-11-18 01:13:13 CST  25205 1000 1000 SIGABRT missing  /usr/bin/ccze                    -
Sat 2023-11-18 01:13:14 CST  25646 1000 1000 SIGABRT missing  /usr/bin/ccze                    -
Sat 2023-11-18 22:14:12 CST    576 1000 1000 SIGABRT missing  /usr/bin/plasmashell             -
Sat 2023-11-18 23:37:15 CST   2175 1000 1000 SIGABRT missing  /usr/bin/plasmashell             -
Sun 2023-11-19 12:59:47 CST   4430    0    0 SIGABRT none     /usr/bin/fcitx5-remote           -
Sun 2023-11-19 13:00:33 CST   4459    0    0 SIGABRT none     /usr/bin/fcitx5-remote           -
Sun 2023-11-19 13:00:34 CST   4469    0    0 SIGABRT none     /usr/bin/fcitx5-remote           -
Sun 2023-11-19 13:06:05 CST   5821    0    0 SIGABRT none     /usr/bin/fcitx5-remote           -
Mon 2023-11-20 20:53:13 CST    588 1000 1000 SIGSEGV missing  /usr/bin/plasmashell             -
Mon 2023-11-20 20:56:33 CST   6077 1000 1000 SIGABRT missing  /usr/bin/clashctl                -
Mon 2023-11-20 22:56:05 CST   5427 1000 1000 SIGABRT missing  /usr/bin/plasmashell             -
Mon 2023-11-20 22:59:54 CST  18385    0    0 SIGABRT none     /usr/bin/fcitx5-remote           -
Tue 2023-11-21 23:30:23 CST  12137 1000 1000 SIGBUS  missing  /qq                              -
Tue 2023-11-21 23:30:25 CST  12093 1000 1000 SIGBUS  missing  /qq                              -
Tue 2023-11-21 23:30:26 CST  17572 1000 1000 SIGBUS  missing  /qq                              -
Tue 2023-11-21 23:30:26 CST  12015 1000 1000 SIGBUS  missing  /qq                              -
Tue 2023-11-21 23:30:26 CST  12016 1000 1000 SIGBUS  missing  /qq                              -
Tue 2023-11-21 23:30:27 CST  12459 1000 1000 SIGBUS  missing  /qq                              -
Tue 2023-11-21 23:30:27 CST  12003 1000 1000 SIGBUS  missing  /qq                              -
Tue 2023-11-21 23:30:28 CST  12043 1000 1000 SIGBUS  missing  /chrome_crashpad_handler         -
Fri 2023-11-24 00:01:53 CST  14600 1000 1000 SIGBUS  missing  /chrome_crashpad_handler         -
Sat 2023-11-25 02:40:58 CST  32138 1000 1000 SIGBUS  missing  /chrome_crashpad_handler         -
Tue 2023-11-28 23:33:11 CST  41077 1000 1000 SIGTRAP missing  /qq                              -
Wed 2023-11-29 11:43:44 CST  43973 1000 1000 SIGABRT missing  /usr/bin/adb                     -
Wed 2023-11-29 11:44:06 CST  45189 1000 1000 SIGABRT missing  /usr/bin/adb                     -
Wed 2023-11-29 23:29:56 CST  53151 1000 1000 SIGABRT missing  /usr/bin/clashctl                -
Wed 2023-11-29 23:45:58 CST  55228 1000 1000 SIGSEGV missing  /opt/visual-studio-code/code     -
Thu 2023-11-30 00:13:43 CST  42637 1000 1000 SIGBUS  missing  /chrome_crashpad_handler         -
Sat 2023-12-02 01:12:16 CST  56991 1000 1000 SIGBUS  missing  /chrome_crashpad_handler         -
Mon 2023-12-04 10:28:09 CST  77126 1000 1000 SIGABRT missing  /usr/bin/clashctl                -
Mon 2023-12-04 15:18:23 CST  99034    0    0 SIGABRT none     /usr/bin/fcitx5-remote           -
Mon 2023-12-04 15:19:05 CST  99068    0    0 SIGABRT none     /usr/bin/fcitx5-remote           -
Mon 2023-12-04 15:20:45 CST  99231    0    0 SIGABRT none     /usr/bin/fcitx5-remote           -
Mon 2023-12-04 15:54:13 CST 104472 1000 1000 SIGSEGV missing  /home/xeonds/code/pizip/pi       -
Mon 2023-12-04 15:54:45 CST 104495 1000 1000 SIGSEGV missing  /home/xeonds/code/pizip/pi       -
Mon 2023-12-04 15:55:06 CST 104521 1000 1000 SIGSEGV missing  /home/xeonds/code/pizip/pi       -
Mon 2023-12-04 15:55:36 CST 104541 1000 1000 SIGSEGV missing  /home/xeonds/code/pizip/pi       -
Mon 2023-12-04 17:28:20 CST 104920 1000 1000 SIGBUS  missing  /chrome_crashpad_handler         -
Mon 2023-12-04 23:36:35 CST 119295 1000 1000 SIGSEGV missing  /opt/visual-studio-code/code     -
Wed 2023-12-06 11:18:53 CST  16426    0    0 SIGABRT none     /usr/bin/fcitx5-remote           -
Mon 2023-12-11 19:56:40 CST  97572 1000 1000 SIGTRAP missing  /tmp/.mount_linuxqSV6RFp/qq      -
Tue 2023-12-12 01:01:33 CST 123670 1000 1000 SIGTRAP missing  /opt/visual-studio-code/code     -
Fri 2023-12-15 14:50:41 CST  17039 1000 1000 SIGTRAP missing  /tmp/.mount_linuxqkQn53G/qq      -
Sat 2023-12-16 23:55:13 CST  19892 1000 1000 SIGTRAP missing  /opt/visual-studio-code/code     -
Mon 2023-12-18 13:16:16 CST  28074    0    0 SIGABRT none     /usr/bin/fcitx5-remote           -
Mon 2023-12-18 15:08:22 CST  41701 1000 1000 SIGABRT missing  /usr/bin/clashctl                -
Tue 2023-12-19 21:37:06 CST  17530 1000 1000 SIGFPE  missing  /home/xeonds/code/c4/a.out       -
Tue 2023-12-19 23:39:47 CST  20684 1000 1000 SIGTRAP missing  /tmp/.mount_linuxqllS3Xz/qq      -
Wed 2023-12-20 12:31:27 CST  23806 1000 1000 SIGABRT missing  /usr/bin/clashctl                -
Sun 2023-12-24 19:26:26 CST   5873 1000 1000 SIGTRAP present  /qq                           1.6M
Mon 2023-12-25 01:59:52 CST   5951 1000 1000 SIGBUS  present  /chrome_crashpad_handler     42.5K

上面是coredumpctl的输出。好像sddm还没崩溃呢。再看看journal：

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
Dec 24 02:28:08 ark-station-breeze systemd[1]: Started Simple Desktop Display Manager.
░░ Subject: A start job for unit sddm.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit sddm.service has finished successfully.
░░ 
░░ The job identifier is 108.
Dec 24 02:28:08 ark-station-breeze sddm[407]: Initializing...
Dec 24 02:28:08 ark-station-breeze sddm[407]: Starting...
Dec 24 02:28:08 ark-station-breeze sddm[407]: Logind interface found
Dec 24 02:28:08 ark-station-breeze sddm[407]: Adding new display...
Dec 24 02:28:08 ark-station-breeze sddm[407]: Loaded empty theme configuration
Dec 24 02:28:08 ark-station-breeze sddm[407]: Xauthority path: "/run/sddm/xauth_bDCTVn"
Dec 24 02:28:08 ark-station-breeze sddm[407]: Using VT 2
Dec 24 02:28:08 ark-station-breeze sddm[407]: Display server starting...
Dec 24 02:28:08 ark-station-breeze sddm[407]: Writing cookie to "/run/sddm/xauth_bDCTVn"
Dec 24 02:28:08 ark-station-breeze sddm[407]: Running: /usr/bin/X -dpi 120 -background none -seat seat0 vt2 -auth /run/sddm/xauth_bDCTVn -noreset -displayfd 16
Dec 24 02:28:09 ark-station-breeze sddm[407]: Setting default cursor
Dec 24 02:28:09 ark-station-breeze sddm[407]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Dec 24 02:28:09 ark-station-breeze sddm[407]: Display server started.
Dec 24 02:28:09 ark-station-breeze sddm[407]: Reading from "/usr/local/share/xsessions/plasma.desktop"
Dec 24 02:28:09 ark-station-breeze sddm[407]: Reading from "/usr/share/xsessions/plasma.desktop"
Dec 24 02:28:09 ark-station-breeze sddm[407]: Session "/usr/share/xsessions/plasma.desktop" selected, command: "/usr/bin/startplasma-x11" for VT 2
Dec 24 02:28:09 ark-station-breeze sddm-helper[433]: [PAM] Starting...
Dec 24 02:28:09 ark-station-breeze sddm-helper[433]: [PAM] Authenticating...
Dec 24 02:28:09 ark-station-breeze sddm-helper[433]: pam_kwallet5(sddm-autologin:auth): pam_kwallet5: pam_sm_authenticate
Dec 24 02:28:09 ark-station-breeze sddm-helper[433]: [PAM] Preparing to converse...
Dec 24 02:28:09 ark-station-breeze sddm-helper[433]: pam_kwallet5(sddm-autologin:auth): pam_kwallet5: Couldn't get password (it is empty)
Dec 24 02:28:09 ark-station-breeze sddm-helper[433]: [PAM] Conversation with 1 messages
Dec 24 02:28:09 ark-station-breeze sddm-helper[433]: pam_kwallet5(sddm-autologin:auth): pam_kwallet5: Empty or missing password, doing nothing
Dec 24 02:28:09 ark-station-breeze sddm-helper[433]: [PAM] returning.
Dec 24 02:28:09 ark-station-breeze sddm[407]: Authentication for user  "xeonds"  successful
Dec 24 02:28:09 ark-station-breeze sddm-helper[433]: pam_kwallet5(sddm-autologin:setcred): pam_kwallet5: pam_sm_setcred
Dec 24 02:28:09 ark-station-breeze sddm-helper[433]: pam_unix(sddm-autologin:session): session opened for user xeonds(uid=1000) by xeonds(uid=0)
Dec 24 02:28:10 ark-station-breeze sddm-helper[433]: pam_kwallet5(sddm-autologin:session): pam_kwallet5: pam_sm_open_session
Dec 24 02:28:10 ark-station-breeze sddm-helper[433]: pam_kwallet5(sddm-autologin:session): pam_kwallet5: open_session called without kwallet5_key
Dec 24 02:28:10 ark-station-breeze sddm-helper[433]: Writing cookie to "/tmp/xauth_XpVcsc"
Dec 24 02:28:10 ark-station-breeze sddm-helper[433]: Starting X11 session: "" "/usr/share/sddm/scripts/Xsession \"/usr/bin/startplasma-x11\""
Dec 24 02:28:10 ark-station-breeze sddm[407]: Session started true

哦还有xorg的：

1
-- No entries --

好吧空的。那看看top

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26

[?1h=[?25ltop - 15:10:25 up 1 day, 12:42,  1 user,  load average: 1.40, 1.33, 1.29
任务: 204 total,   3 running, 201 sleeping,   0 stopped,   0 zombie
%Cpu(s): 28.6 us,  0.0 sy,  0.0 ni, 71.4 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st 
MiB Mem :   7835.3 total,    584.1 free,   3807.3 used,   4760.9 buff/cache     
MiB Swap:      0.0 total,      0.0 free,      0.0 used.   4028.0 avail Mem 

 进程号 USER      PR  NI    VIRT    RES    SHR    %CPU  %MEM     TIME+ COMMAND  
    411 root      20   0  859280  87628  30916 R  90.9   1.1 248:56.68 Xorg     
  19316 xeonds    20   0 4028616 892492 271492 R  72.7  11.1   0:17.50 firefox  
  19461 xeonds    20   0 2713128 171852  88252 S  18.2   2.1   0:06.27 WebExte+ 
  19901 xeonds    20   0   15440   5760   3584 R   9.1   0.1   0:00.01 top      
      1 root      20   0   22220  10228   7028 S   0.0   0.1   0:02.61 systemd  
      2 root      20   0       0      0      0 S   0.0   0.0   0:00.04 kthreadd 
      3 root      20   0       0      0      0 S   0.0   0.0   0:00.00 pool_wo+ 
      4 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+ 
      5 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+ 
      6 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+ 
      7 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+ 
      9 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+ 
     12 root       0 -20       0      0      0 I   0.0   0.0   0:00.00 kworker+ 
     14 root      20   0       0      0      0 I   0.0   0.0   0:00.00 rcu_tas+ 
     15 root      20   0       0      0      0 I   0.0   0.0   0:00.00 rcu_tas+ 
     16 root      20   0       0      0      0 I   0.0   0.0   0:00.00 rcu_tas+ 
     17 root      20   0       0      0      0 S   0.0   0.0   0:30.95 ksoftir+ [?1l>
[?25h

抽象是抽象了点，但是能看出来好像是Xorg在发电，试试去tty重启xorg看看。

最后发现Xorg是sddm启动的，没办法直接重启了下sddm，问题解决，但是最不爽的是不知道问题到底是咋解决的。

找到一个博客，发现好像不是xorg的问题，而是kwin的问题：暂停恢复合成时，会导致kwin卡顿，这时候重启一下kwin_x11就行了。

这就好说了：

1
systemctl --user restart plasma-kwin_x11

或者这个

1
setsid kwin_x11 --replace &

ref:律回彼境

试了试，问题完美解决，CPU占用也正常了。

参考：KDE解决GUI界面卡顿的问题

组合键

其实主要是KDE Plasma的相关组合键。偶尔会意外发现一些组合键，就记录在这里了。

  • 切换桌面：ctrl+F*
  • 无极缩放：win+ctrl+鼠标滚轮，真的好丝滑QAQ

莫得休眠Hibernate选项

找了半天发现是系统安装的时候没设置swap交换分区。不过暂时默认的睡眠也够用了，之后再考虑吧。

备份

ref:现代化的 Archlinux 安装，Btrfs、快照、休眠以及更多。

其一就是软件列表备份。pacman -Qe >> installed.txt就可以备份已安装软件列表

其二就是备份根目录数据。其中的-avrh用于保留文件权限。以及似乎必须得注意路径末尾的斜杠问题，rsync好像会区分这两个路径。sudo rsync -avrh --progress /home/ /mnt/backup/

关机等待时间

一直忘了改这个东西了。有时候等待一些服务停止的时候等到倒计时结束才会停止。可以适当减少倒计时的时长环节这个问题。

对应的参数在/etc/systemd/system.conf，更改DefaultTimeoutStopSec=90s为你想要的等待时间，我改成10s了。

记一次内核卡死

挺草的说起来。征兆是先是firefox崩了，然后把kwin也爆了。第二次是kwin自己爆炸了，然后玩mc java的时候就OOM+CPU 100%了。问了下群里老哥，发现没开SysRq，不然的话就能在内核卡死的时候使用一些组合键来让内核执行一些有限操作。

等待了大概40min，无果，只能以>2min的不规律时间响应键盘中断，老哥推测可能是活锁，而且OOM也没来得及出动。所以就含泪重启，跟自己tmux里边一堆窗口告别了。

重启，看看内核日志：sudo journalctl -k -b-1查看上次启动的日志：

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
Jan 16 10:43:33 ark-station kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Jan 16 10:43:33 ark-station kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0040-4150.ddc
Jan 16 10:43:33 ark-station kernel: Bluetooth: hci0: Applying Intel DDC parameters completed
Jan 16 10:43:33 ark-station kernel: Bluetooth: hci0: Firmware timestamp 2023.42 buildtype 1 build 73111
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: Transport status: 0x0000004A, valid: 6
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: Loaded firmware version: 83.e8f84e98.0 so-a0-hr-b0-83.ucode
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL    
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x000002F0 | trm_hw_status0
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status1
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x004D9024 | branchlink2
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x004CF2F2 | interruptlink1
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x004CF2F2 | interruptlink2
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00015346 | data1
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00000010 | data2
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00000000 | data3
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x0022F89E | beacon time
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x001E1C6F | tsf low
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00000000 | tsf hi
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00000000 | time gp1
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x001ED6DD | time gp2
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00000001 | uCode revision type
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00000053 | uCode version major
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0xE8F84E98 | uCode version minor
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00000370 | hw version
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00C80002 | board version
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x80DDFC04 | hcmd
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00020000 | isr0
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00000000 | isr1
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x48F00002 | isr2
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00C3000C | isr3
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00000000 | isr4
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x001C0103 | last cmd Id
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00015346 | wait_event
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00000010 | l2p_control
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00000020 | l2p_duration
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x0000003F | l2p_mhvalid
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00000000 | l2p_addr_match
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00000009 | lmpm_pmg_sel
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00000000 | timestamp
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00004870 | flow_handler
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: Transport status: 0x0000004A, valid: 7
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x2010190E | ADVANCED_SYSASSERT
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink1
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x804703E0 | umac branchlink2
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0xC0081500 | umac interruptlink1
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00000000 | umac interruptlink2
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x0101971C | umac data1
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0xDEADBEEF | umac data2
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0xDEADBEEF | umac data3
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00000053 | umac major
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0xE8F84E98 | umac minor
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x001ED6D7 | frame pointer
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0xC0886BE0 | stack pointer
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x0024010D | last host cmd
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00000000 | isr status reg
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: IML/ROM dump:
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00000B03 | IML/ROM error/state
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x0000518C | IML/ROM data1
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00000090 | IML/ROM WFPM_AUTH_KEY_0
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: Fseq Registers:
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x60000000 | FSEQ_ERROR_CODE
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00350002 | FSEQ_TOP_INIT_VERSION
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00150001 | FSEQ_CNVIO_INIT_VERSION
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x0000A482 | FSEQ_OTP_VERSION
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00000003 | FSEQ_TOP_CONTENT_VERSION
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x4552414E | FSEQ_ALIVE_TOKEN
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00080400 | FSEQ_CNVI_ID
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x01300504 | FSEQ_CNVR_ID
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00080400 | CNVI_AUX_MISC_CHIP
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x01300504 | CNVR_AUX_MISC_CHIP
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00150001 | FSEQ_PREV_CNVIO_INIT_VERSION
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00350002 | FSEQ_WIFI_FSEQ_VERSION
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x00350002 | FSEQ_BT_FSEQ_VERSION
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: 0x000000DC | FSEQ_CLASS_TP_VERSION
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: UMAC CURRENT PC: 0x8048f214
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: LMAC1 CURRENT PC: 0xd0
Jan 16 10:43:33 ark-station kernel: iwlwifi 0000:00:14.3: WRT: Collecting data: ini trigger 4 fired (delay=0ms).
Jan 16 10:43:33 ark-station kernel: ieee80211 phy0: Hardware restart was requested
Jan 16 10:43:34 ark-station kernel: iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
Jan 16 10:43:34 ark-station kernel: Bluetooth: MGMT ver 1.22
Jan 16 10:43:34 ark-station kernel: Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
Jan 16 10:43:34 ark-station kernel: iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x20
Jan 16 10:43:34 ark-station kernel: iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
Jan 16 10:43:34 ark-station kernel: iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
Jan 16 10:43:34 ark-station kernel: iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
Jan 16 10:43:34 ark-station kernel: iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 5
Jan 16 10:43:38 ark-station kernel: wlan0: authenticate with e2:cb:4f:01:72:a7
Jan 16 10:43:38 ark-station kernel: wlan0: send auth to e2:cb:4f:01:72:a7 (try 1/3)
Jan 16 10:43:38 ark-station kernel: wlan0: authenticated
Jan 16 10:43:38 ark-station kernel: wlan0: associate with e2:cb:4f:01:72:a7 (try 1/3)
Jan 16 10:43:38 ark-station kernel: wlan0: RX AssocResp from e2:cb:4f:01:72:a7 (capab=0x1511 status=0 aid=1)
Jan 16 10:43:38 ark-station kernel: wlan0: associated
Jan 16 10:47:20 ark-station kernel: kwin_wayland[901]: segfault at 0 ip 0000561fd234c33f sp 00007fff916f35c0 error 4 in kwin_wayland[561fd2348000+110000] likely on CPU 13 (core 25, socket 0)
Jan 16 10:47:20 ark-station kernel: Code: 8b 47 58 48 8b 58 10 48 01 c3 48 63 40 04 4c 8d 24 c3 49 39 dc 75 0d eb 2a 66 90 48 83 c3 08 49 39 dc 74 1f 48 8b 3b 48 89 ee <48> 8b 07 ff 50 60 84 c0 74 e7 48 83 c4 08 5b 5d 41 5c 41 5d c3 0f
Jan 16 10:49:41 ark-station systemd-fstab-generator[2389003]: Failed to create unit file '/run/systemd/generator/-.mount', as it already exists. Duplicate entry in '/etc/fstab'?
Jan 16 11:15:18 ark-station kernel: wlan0: deauthenticating from e2:cb:4f:01:72:a7 by local choice (Reason: 3=DEAUTH_LEAVING)
Jan 16 11:15:18 ark-station kernel: wlan0: authenticate with f0:9b:b8:16:62:30
Jan 16 11:15:18 ark-station kernel: wlan0: 80 MHz not supported, disabling VHT
Jan 16 11:15:18 ark-station kernel: wlan0: send auth to f0:9b:b8:16:62:30 (try 1/3)
Jan 16 11:15:18 ark-station kernel: wlan0: authenticated
Jan 16 11:15:18 ark-station kernel: wlan0: associate with f0:9b:b8:16:62:30 (try 1/3)
Jan 16 11:15:18 ark-station kernel: wlan0: RX AssocResp from f0:9b:b8:16:62:30 (capab=0x1421 status=0 aid=2)
Jan 16 11:15:18 ark-station kernel: wlan0: associated
Jan 16 11:15:18 ark-station kernel: wlan0: Limiting TX power to 20 (20 - 0) dBm as advertised by f0:9b:b8:16:62:30
Jan 16 11:21:36 ark-station kernel: wlan0: disconnect from AP f0:9b:b8:16:62:30 for new auth to f0:9b:b8:16:62:40
Jan 16 11:21:36 ark-station kernel: wlan0: authenticate with f0:9b:b8:16:62:40
Jan 16 11:21:36 ark-station kernel: wlan0: send auth to f0:9b:b8:16:62:40 (try 1/3)
Jan 16 11:21:36 ark-station kernel: wlan0: authenticated
Jan 16 11:21:36 ark-station kernel: wlan0: associate with f0:9b:b8:16:62:40 (try 1/3)
Jan 16 11:21:36 ark-station kernel: wlan0: RX ReassocResp from f0:9b:b8:16:62:40 (capab=0x1501 status=0 aid=4)
Jan 16 11:21:36 ark-station kernel: wlan0: associated
Jan 16 11:21:36 ark-station kernel: wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by f0:9b:b8:16:62:40
Jan 16 11:22:44 ark-station kernel: i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=282494 end=282495) time 187 us, min 1579, max 1599, scanline start 1564, end 1602
Jan 16 11:41:50 ark-station kernel: wlan0: disconnect from AP f0:9b:b8:16:62:40 for new auth to f0:9b:b8:16:5c:40
Jan 16 11:41:50 ark-station kernel: wlan0: authenticate with f0:9b:b8:16:5c:40
Jan 16 11:41:50 ark-station kernel: wlan0: send auth to f0:9b:b8:16:5c:40 (try 1/3)
Jan 16 11:41:50 ark-station kernel: wlan0: authenticated
Jan 16 11:41:50 ark-station kernel: wlan0: associate with f0:9b:b8:16:5c:40 (try 1/3)
Jan 16 11:41:50 ark-station kernel: wlan0: RX ReassocResp from f0:9b:b8:16:5c:40 (capab=0x1501 status=0 aid=2)
Jan 16 11:41:50 ark-station kernel: wlan0: associated
Jan 16 11:41:50 ark-station kernel: wlan0: Limiting TX power to 23 (23 - 0) dBm as advertised by f0:9b:b8:16:5c:40
Jan 16 18:00:05 ark-station kernel: wlan0: deauthenticating from f0:9b:b8:16:5c:40 by local choice (Reason: 3=DEAUTH_LEAVING)
Jan 16 18:00:05 ark-station kernel: wlan0: authenticate with e2:cb:4f:01:72:a7
Jan 16 18:00:05 ark-station kernel: wlan0: send auth to e2:cb:4f:01:72:a7 (try 1/3)
Jan 16 18:00:05 ark-station kernel: wlan0: authenticated
Jan 16 18:00:05 ark-station kernel: wlan0: associate with e2:cb:4f:01:72:a7 (try 1/3)
Jan 16 18:00:05 ark-station kernel: wlan0: RX AssocResp from e2:cb:4f:01:72:a7 (capab=0x1511 status=0 aid=3)
Jan 16 18:00:05 ark-station kernel: wlan0: associated
Jan 16 18:41:38 ark-station kernel: i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=2487239 end=2487240) time 230 us, min 1579, max 1599, scanline start 1566, end 1613
Jan 16 19:34:40 ark-station kernel: i915 0000:00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=2869004 end=2869005) time 158 us, min 1579, max 1599, scanline start 1570, end 1602
Jan 16 20:01:05 ark-station kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0x8b on isa0060/serio0).
Jan 16 20:01:05 ark-station kernel: atkbd serio0: Use 'setkeycodes e00b <keycode>' to make it known.
Jan 16 20:01:05 ark-station kernel: atkbd serio0: Unknown key released (translated set 2, code 0x8b on isa0060/serio0).
Jan 16 20:01:05 ark-station kernel: atkbd serio0: Use 'setkeycodes e00b <keycode>' to make it known.
Jan 16 20:01:07 ark-station kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0x8a on isa0060/serio0).
Jan 16 20:01:07 ark-station kernel: atkbd serio0: Use 'setkeycodes e00a <keycode>' to make it known.
Jan 16 20:01:07 ark-station kernel: atkbd serio0: Unknown key released (translated set 2, code 0x8a on isa0060/serio0).
Jan 16 20:01:07 ark-station kernel: atkbd serio0: Use 'setkeycodes e00a <keycode>' to make it known.
Jan 16 20:02:39 ark-station kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0x8b on isa0060/serio0).
Jan 16 20:02:39 ark-station kernel: atkbd serio0: Use 'setkeycodes e00b <keycode>' to make it known.
Jan 16 20:02:39 ark-station kernel: atkbd serio0: Unknown key released (translated set 2, code 0x8b on isa0060/serio0).
Jan 16 20:02:39 ark-station kernel: atkbd serio0: Use 'setkeycodes e00b <keycode>' to make it known.
Jan 16 20:02:51 ark-station kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0x8a on isa0060/serio0).
Jan 16 20:02:51 ark-station kernel: atkbd serio0: Use 'setkeycodes e00a <keycode>' to make it known.
Jan 16 20:02:51 ark-station kernel: atkbd serio0: Unknown key released (translated set 2, code 0x8a on isa0060/serio0).
Jan 16 20:02:51 ark-station kernel: atkbd serio0: Use 'setkeycodes e00a <keycode>' to make it known.
Jan 16 20:18:46 ark-station kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: GUC: Engine reset failed on 0:0 (rcs0) because 0x00000000
Jan 16 20:18:46 ark-station kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 12:1:84dffffb, in Render thread [3009924]
Jan 16 20:18:46 ark-station kernel: i915 0000:00:02.0: [drm] Resetting chip for GuC failed to reset engine mask=0x1
Jan 16 20:18:46 ark-station kernel: i915 0000:00:02.0: [drm] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
Jan 16 20:18:46 ark-station kernel: i915 0000:00:02.0: [drm] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
Jan 16 20:18:46 ark-station kernel: i915 0000:00:02.0: [drm] Render thread[3009924] context reset due to GPU hang
Jan 16 20:18:46 ark-station kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.13.1
Jan 16 20:18:46 ark-station kernel: i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
Jan 16 20:18:46 ark-station kernel: i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads
Jan 16 20:18:46 ark-station kernel: i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
Jan 16 20:18:46 ark-station kernel: i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
Jan 16 20:45:01 ark-station kernel: i915 0000:00:02.0: [drm] *ERROR* GT0: GUC: Engine reset failed on 0:0 (rcs0) because 0x00000000
Jan 16 20:45:01 ark-station kernel: i915 0000:00:02.0: [drm] GPU HANG: ecode 12:1:84dffffb, in Render thread [3009924]
Jan 16 20:45:01 ark-station kernel: i915 0000:00:02.0: [drm] Resetting chip for GuC failed to reset engine mask=0x1
Jan 16 20:45:01 ark-station kernel: i915 0000:00:02.0: [drm] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
Jan 16 20:45:01 ark-station kernel: i915 0000:00:02.0: [drm] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
Jan 16 20:45:01 ark-station kernel: i915 0000:00:02.0: [drm] Render thread[3009924] context reset due to GPU hang
Jan 16 20:45:01 ark-station kernel: i915 0000:00:02.0: [drm] GT0: GuC firmware i915/adlp_guc_70.bin version 70.13.1
Jan 16 20:45:01 ark-station kernel: i915 0000:00:02.0: [drm] GT0: HuC firmware i915/tgl_huc.bin version 7.9.3
Jan 16 20:45:01 ark-station kernel: i915 0000:00:02.0: [drm] GT0: HuC: authenticated for all workloads
Jan 16 20:45:01 ark-station kernel: i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
Jan 16 20:45:01 ark-station kernel: i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
Jan 16 20:49:08 ark-station kernel: INFO: task IPC Launch:2387456 blocked for more than 122 seconds.
Jan 16 20:49:16 ark-station kernel:       Not tainted 6.6.10-arch1-1 #1
Jan 16 20:49:27 ark-station kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 16 20:49:32 ark-station kernel: task:IPC Launch      state:D stack:0     pid:2387456 ppid:870    flags:0x00004002
Jan 16 20:49:38 ark-station kernel: Call Trace:
Jan 16 20:49:48 ark-station kernel:  <TASK>
Jan 16 20:50:00 ark-station kernel:  __schedule+0x3e7/0x1410
Jan 16 20:50:16 ark-station kernel:  schedule+0x5e/0xd0
Jan 16 20:50:28 ark-station kernel:  schedule_preempt_disabled+0x15/0x30
Jan 16 20:50:36 ark-station kernel:  rwsem_down_write_slowpath+0x203/0x690
Jan 16 20:50:43 ark-station kernel:  ? prealloc_shrinker+0x6a/0xd0
Jan 16 20:50:51 ark-station kernel:  ? __pfx_set_anon_super_fc+0x10/0x10
Jan 16 20:50:57 ark-station kernel:  down_write+0x5b/0x60
Jan 16 20:51:04 ark-station kernel:  __prealloc_shrinker+0x70/0x350
Jan 16 20:51:11 ark-station kernel:  ? kvasprintf+0x82/0xd0
Jan 16 20:51:17 ark-station kernel:  ? __pfx_set_anon_super_fc+0x10/0x10
Jan 16 20:51:23 ark-station kernel:  prealloc_shrinker+0x7b/0xd0
Jan 16 20:51:28 ark-station kernel:  alloc_super+0x272/0x2e0
Jan 16 20:51:35 ark-station kernel:  sget_fc+0x63/0x330
Jan 16 20:51:41 ark-station kernel:  ? __pfx_mqueue_fill_super+0x10/0x10
Jan 16 20:51:55 ark-station kernel:  get_tree_nodev+0x27/0x90
Jan 16 20:52:02 ark-station kernel:  vfs_get_tree+0x26/0xf0
Jan 16 20:52:07 ark-station kernel:  ? refcount_dec_and_lock+0x11/0x70
Jan 16 20:52:12 ark-station kernel:  fc_mount+0x12/0x40
Jan 16 20:52:17 ark-station kernel:  mq_init_ns+0x10f/0x1b0
Jan 16 20:52:21 ark-station kernel:  copy_ipcs+0x134/0x270
Jan 16 20:52:26 ark-station kernel:  create_new_namespaces+0xa1/0x2e0

看了一圈最后找到个issue，看样子我应该是drm/i195受害者咯。

SysRq: Keyboard Shortcuts

systemd has the SysRq permissions bitmask set to 0x10 by default, which does not allow process signalling or rebooting, among other things. To allow full use of the SysRq key on your system, add kernel.sysrq = 1 to your sysctl configuration. Values greater than 1 can be used to selectively enable SysRq functions; see the Linux kernel documentation for details. If you want to make sure it will be enabled even before the partitions are mounted and in the initrd, then add sysrq_always_enabled=1 to your kernel parameters.

Note that changing the setting through these methods will cause the changes to persist across reboots. If you want to try changing the SysRq settings for just your current session, you can run either sysctl kernel.sysrq=1 or echo “1” > /proc/sys/kernel/sysrq.

There are some obvious security risks involved in fully enabling the SysRq key. In addition to forcing reboots and the like, it can be used to dump the contents of the CPU registers, which could theoretically reveal sensitive information. Since using it requires physical access to the system (unless you go out of your way), most desktop users will probably consider the level of risk acceptable. That said, make sure you fully understand the implications of enabling it and the dynamics of the larger context in which your system is operating before you turn SysRq all the way on.

上边是arch wiki的资料链接，可以参考下开开这玩意。这玩意的快捷键可以这么记：Reboot Even If System Utterly Broken。用法就是Alt+SysRq+这六个单词首字母缩写，功能分别是

  • Unraw：切换键盘输入到ASCII模式，
  • Terminate：给所有进程发送SIGTERM，
  • Kill：发送SIGKILL给所有进程，
  • Sync：写入数据到磁盘，
  • Unmount：卸载然后挂载所有文件系统为只读模式，
  • Reboot：重启。

另外还可以用f来触发OOM Killer。

开机时间优化

ref: 律回彼境

使用sudo systemd-analyze blame可以查看系统开机时间详情。

自动mount分区（也就是直接在/etc/fstab里边进行配置）会导致启动时间增大，所以更推荐写成一个脚本，在用户登录后自动执行挂载。脚本放置在 ~/.config/autostart/ 即可在用户登录后执行。

又被Firefox爆了

虽然后来看日志发现是Firefox被kwin爆了

这几天频繁出现桌面所有进程炸掉的情况，恢复后Firefox的Crash Report自己会跳出来。。不知道为啥，但是根据群u从about:crashes里边提交的崩溃报告来看，应该是kwin把Firefox爆了。

根据老哥的建议，关闭了系统的自适应同步（Adaptive Sync）选项，按照他的惊叹，问题可能会少一些。

传文件的姿势

什么姿势，还真没见过
-转自archlinux-cn-依云

1
tar C -c ~tmp/makepkg/wayfire-lily-git/src/build/src wayfire | ssh root@kvm-archkde tar xvU -C /usr/bin/

文件系统迁移

有条件的话，建议还是全新安装最好。

Reference:

参考了几个博客，跟着感觉走最后总算是有惊无险整好了。

本来是想用btrfs-convert给直接原地转换的，但是奈何superblock大小太小，转换失败。没办法，自己动手丰衣足食。

首先先是把原来的系统备份好：

1
dd if=/dev/nvme0n1p5 of=/path/to/another/disk/backup.img bs=4M status=progress

有备份了，开整。

发现手边没有U盘，但是有个root的手机。于是就用DriveDroid+一个Arch的LiveISO让它发挥余热了。

启动挺顺利，记得把ArchISO挂载为只读USB存储设备。进去之后确保确实备份了之后格式化设备（一定要多确认几遍，）：

1
mkfs.btrfs -L arch-driver /dev/nvme0n1p5    # 这里务必多确认几遍

然后创建子卷，布局我用的适合timeshift的默认方案：

1
2
3
4
5
6
7
8
9
10
mount -t btrfs -o compress=zstd /dev/nvme0n1p5 /mnt
btrfs subvolume create /mnt/@ # 创建 / 目录子卷
btrfs subvolume create /mnt/@home # 创建 /home 目录子卷
umount /mnt

mount -t btrfs -o subvol=/@,compress=zstd /dev/nvme0n1p5 /mnt
mkdir /mnt/home
mount -t btrfs -o subvol=/@home,compress=zstd /dev/nvme0n1p5 /mnt/home
mkdir -p /mnt/boot
mount /dev/nvme0n1p2 /mnt/boot

创建完成之后，准备迁移数据：

1
2
3
4
mkdir ~/old-fs
monut /path/to/your/backup/backup.img ~/old-fs
rsync -av ~/old-fs/home/ /mnt/home/
rsync -av --exclude={"/proc","/dev"} ~/old-fs/ /mnt/

等复制完成之后，就可以着手修复系统引导了。这里先用iwctl连上网。之后就该开始修复GRUB了：

1
2
3
4
5
6
7
8
genfstab -U /mnt > /mnt/etc/fstab
# 此时手动检查下结果是否正确
# 可以cat /mnt/etc/fstab看看
arch-chroot /mnt
pacman -S grub-btrfs    # 安装支持btrfs版本的GRUB
grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=ARCH
sed -i 's/loglevel=3 quiet/loglevel=5 nowatchdog/g' /etc/default/grub
echo "GRUB_DISABLE_OS_PROBER=false" >> /etc/default/grub

然后理论上就OK了。此时ctrl+d退出chroot然后umount -R /mnt && reboot，重启，进入新系统看看吧。

反正解决完一堆问题，成功进系统之后，我惊悚地发现，磁盘可用空间从8G变成了30G而且btrfs balance /之后还又多出来1G。根据rx所说，btrfs对于文本的压缩效果特别好。那指不定是给我一堆node_modules压缩干净了？

谁知道，大概是透明压缩确实顶吧。经过测试，timeshift和其他的btrfs特性都能正常使用。

Arch Linux折腾笔记

https://mxts.jiujiuer.xyz/2023/09/05/arch-linux折腾笔记/

作者

xeonds

发布于

2023-09-05

更新于

2024-05-13

许可协议

#

评论

关注我

链接

最新文章

归档

×