With my graduation approaching and my system getting cluttered with digital junk, I decided it was time for a clean OS reinstallation. I’ve been wanting to dive deeper into Linux while still keeping a reliable environment for computer games in my spare time. Therefore, a dual-boot configuration was the perfect solution. My target setup includes Legion Custom (Windows) and Debian 13.

💡 Pro Tip: If you are planning a dual-boot setup, I highly recommend using two separate physical hard drives. Managing a dual-boot configuration on a single physical SSD is notoriously tricky.

Preparation

You will need either two separate USB flash drives or a single drive that you rewrite twice for each OS installation. Make sure to install Legion Custom (Windows) first, as the Windows installer tends to overwrite the boot configurations of other drives.

Note on Windows Installation: Windows 11 may insist on installing to the internal disk by default, even after you have physically swapped the disk slots. The exact reason remains unknown, but the solution is to manually modify the system disk assignment inside Windows.

Legion Custom

For a detailed walkthrough of the Legion Custom installation, you can watch this video:

It works beautifully out of the box, and it is worth mentioning that you don’t need to download any extra device drivers.

Debian

⚠️ Attention: Turn off NVIDIA GPU Direct Connect (Discrete GPU Only mode) in your BIOS prior to starting the Debian installation!

To get started with the dual-boot process, you can watch this video which teaches how to install dual-boot with Windows and Ubuntu; it perfectly applies to Debian as well:

For a deep dive into Debian-specific steps, check out this comprehensive installation video:

You can safely ignore most of the post-installation software he introduces later.

My Partition Layout (512GB Dedicated SSD):

• ESP (EFI System Partition): 512 MB

• Swap: 16 GB

• / (Root): 100 GB

• /home: All remaining free space

Key Points for Manual Partitioning:

• Confirm your target disk: Triple-check to ensure you do not select the wrong drive and wipe your Windows data.

• Double-check the EFI partition: Decide whether to reuse the existing EFI partition or create a dedicated new one.

• Pause if you are unsure: Partitioning is the exact step where data is most easily deleted by mistake. Take your time.

I chose KDE as my desktop environment because its layout is highly similar to Windows, and it offers an unparalleled degree of customization.

Problem

Dim Screen / Broken Brightness Control

The screen brightness cannot be adjusted and remains stuck on dim. This is usually caused by incorrect kernel backlight parameters.

The solution is to edit GRUB:

sudo nano /etc/default/grub

Locate the corresponding line （Different systems may vary）

GRUB_CMDLINE_LINUX_DEFAULT="acpi_backlight=native"

change it to

GRUB_CMDLINE_LINUX_DEFAULT="acpi_backlight=native"

then update GRUB and reboot:

sudo update-grub
sudo reboot

NVIDIA Proprietary Driver Installation

I have to say: fuck NVIDIA. Most graphical or system stability issues encountered afterward are inevitably tied to the NVIDIA drivers.

Watch this video/document for the proper setup steps:

Once the drivers are fully installed and configured, you can reboot and safely turn NVIDIA GPU Direct Connect back on.

There are other problems and I will update them in the futuer.

内核自动更新导致无法进入桌面

1.重启系统选择没更新前的内核版本

2.安装新内核的头文件（确保包名完整正确）：

sudo apt update
sudo apt install linux-headers-6.12.95+deb13-amd64//根据自己的内核版本号

3.编译新内核的显卡驱动

sudo dkms autoinstall

4.将新驱动打包进开机镜像

sudo update-initramfs -u -k all

5.刷新引导菜单

sudo update-grub

6.重启

7.直接锁死内核版本

sudo apt-mark hold linux-image-amd64 linux-headers-amd64

如果更新解锁

sudo apt-mark unhold linux-image-amd64 linux-headers-amd64

别忘了锁定回去和编译新驱动

This PDF shows my problem in English.

KDE 动态壁纸插件 Waywallen 无法使用（NVIDIA GBM 兼容性问题）

从 KDE 商店安装的 Waywallen

壁纸插件设置壁纸后桌面始终黑屏，终端启动后端守护进程后报错：

[ERROR] waywallen-image-renderer: ww_bridge_pool_create failed: -95

async error: spawn failed: spawn failed: recv Ready: peer closed connection

该问题与电脑硬件无关，根本原因有两个层面：

1. NVIDIA 550 驱动的 Optimus Vulkan 隐式层（VK_LAYER_NV_optimus）与 Waywallen

的 Vulkan 渲染器冲突，导致渲染进程启动时 SIGSEGV 崩溃。

2. 修复崩溃后，渲染器通过 GBM + DMA-BUF 创建 GPU 缓冲区池时，NVIDIA 专有驱动的

GBM 实现不支持 Waywallen 请求的缓冲区修饰符（modifier），返回 ENOTSUP（错误码

-95）。

此问题属于 Waywallen 的已知 bug，已在 GitHub 上登记为 issue #131

(https://github.com/waywallen/waywallen/issues/131)。修复需要 Waywallen

开发者在代码层面适配 NVIDIA GBM，无法通过环境变量或驱动配置绕过。

临时替代方案：使用 KDE 内置的动态壁纸插件

luisbocanegra.smart.video.wallpaper.reborn，它不依赖 GBM/DMA-BUF，在 NVIDIA

专有驱动下可以正常工作。

诊断过程记录（供后续参考）

# 确认显卡和驱动信息

lspci | grep -E "VGA|3D"

# → NVIDIA GA107BM [GeForce RTX 3050 Mobile]

nvidia-smi

# → Driver Version: 550.163.01

# 确认 Waywallen 渲染器崩溃

coredumpctl list | grep waywallen

# → SIGSEGV: /app/bin/waywallen-image-renderer

# 确认崩溃发生在 NVIDIA Vulkan 层内

coredumpctl gdb <PID>

# → #0 0x00007efeba7f1bc0 in ?? () (地址落在 libGLX_nvidia.so)

# 尝试过但无效的修复手段：

# flatpak override --user --env=DISABLE_LAYER_NV_OPTIMUS_1=1

org.waywallen.waywallen

# → 解决了 SIGSEGV，但 -95 错误仍然存在

# flatpak override --user --env=LD_PRELOAD=.../libnvidia-egl-gbm.so.1

org.waywallen.waywallen

# → 强制使用 NVIDIA EGL-GBM，-95 仍然存在

# flatpak override --user --env=GBM_BACKEND=.../nvidia-drm_gbm.so

org.waywallen.waywallen

# → 指定 NVIDIA GBM 后端，-95 仍然存在

# 清除所有临时配置（如果之前尝试过上述修复）

flatpak override --user --reset org.waywallen.waywallen

rm -f ~/.config/autostart/org.waywallen.waywallen.desktop

如果将来 NVIDIA 驱动升级至 555+ 版本，GBM 兼容性会有所改善，届时可以重新尝试

Waywallen。