SOLVED-if anyone else is having this issue I can post my solution!

Hello everyone! I’m on D13 and I am having trouble mounting a HDD that I brought from my windows PC. I’m trying to use it for Jellyfin and it does already have its own folders (movies/shows/subtitles. I feel completely lost as to what to do as I don’t know any commands or lingo since I’m totally new to Linux. Any help would be greatly appreciated!

I'm trying to draw on my Surface Book 2, but it keeps detecting my palm as input. The kernel I'm using is "Linux 6.19.8-surface-3". I'll attach a fetch screenshot if I can in the comments.

But I'm having some issues, I often need to take screenshots, and the default software doesn't work properly and has many glitches. Is there a fix, or is there better software for screenshots?

Where would I find the change log for the upgrade for Rsync ?

When trying to boot normally now (using the 6.12.111+deb13-amd64 kernel), all I get is a black screen with some horizontal lines scattered across the page. I get the same result when selecting an older kernel from the GNU advanced settings screen. However, I'm able to boot up normally when selecting one of the (recovery mode) options instead.

It seems like it could be an issue with the AMD graphics drivers, but in that case I don't really understand why the recovery mode boot still works. All that being said, I'm not entirely sure how to troubleshoot this so any help would be appreciated.

Only getting connections to things I've already connected to and resolved.

Ping www.google.com works,, ping 8.8.8.8 doesn't.

I don't even know what to do or how to phrase this in a manner that's understandable.

I've tried moving to Other than Avahi, I've loged in, out, restarted, unplugged and replugged making sure it seated with a good around positive click + the light coming back on.

I am on Debian Trixie and yesterday I updated the kernel to 6.12.111

When I booted in the kernel and I did not have any desktop I dropped to the tty and tried to manually start X, it didn't work, the server connection was refused. So I have tried starting Wayland, and it worked. Unfortunately I wasn't able to start plasmashell. Next I ran update-initramfs and I was able to rebuild the Nvidia drivers for kernel 6.12.107 and 6.12.111. I thought I solved the problem, but I did not. Booting in 6.12.107 worked, so I downloaded the 615 version (which is the latest) of the Nvidia driver and installed that. The installation was successful but kernel 6.12.111 still doesn't work.

Anyone has the same issue?

Edit: I don't think it's the Nvidia driver because I can see it starting without errors during boot

Spoiler: it was the Nvidia driver.

I managed to fix everything by installing dkms and reinstalling the kernel with apt

Wow, so many CVEs!!!!!!

I used Debian for more than 15 years and moved to a Linux only setup about 5 years back. I always wanted to contribute back but never had the time or appropriate ways. I remember thinking at one time to become a DD or at least a DM, but I could not or cannot put that much consistent effort.

My selfish reason in this is more about maintaining and improving skills while I give back. And if I can make that a habit and a routine doing whatever, I may even think about a DM eventually.

But first, I would like to defer to the community on this. What else I can do realistically either online or offline? I am not super skilled at the moment as I became comfortable with my simple tiling setups. I maintain my two workstations and do some shell scripting apart from my day job. I am very comfortable on the command line, configuration, technical documentation, reading shell scripts, Python and some C.

hello guys, i wanna share my problem with nvidia drviers which is happening for some reason to me. im just tired dealing with that bullshit because i tried everything i could and it helped but not for so long. curse you flatpak

first time it happend on sep 20-21 and if fixed it on 22 septmer or smth like this.

i was just playing sober in the morning but i decided to run "flatpak update" and updated sober and other apps, but once i laucned it all its processes becomes D and Z state (deadlock and zombie processes) and the only option to stop overheating my cpu was to turn off the laptop using power button. after i boot my laptop again my drivers are arleady fucked up, even when everything seems very normal, because when i launch ANY flatpak app or any app/game that reqers nvidia gpu it just doing the same problem. so i had to UPGRADE (not just reinstall) my nvidia driver to make it work again but if i launch any flatpak app it give me the same problem and i have to upgrade/downgrade my drviers again

second fcking time it happend today when i booted my laptop as usuall

I have not launched any Flatpak app since removing it. I only customized my terminal prompt yesterday (look at a screenshot) and it looked cool so i went to bed and after i woke up and turned my laptop on i instantly saw that Vitals (gnome extension) shown ... instead of C and %. and i opened my terminal and realised i cant type there at all! not even ctrl + c helped so i removed changes that i did and after that termninal started working but my drivers was still on a fkcn potato and giving the same issue as it was in previos ancident. so now i have broken drivers again.

quick answers

NO i did NOT updated my kernel or anything like that
YES i deleted flatpak comleptly from my pc
NO i did NOT updated drivers/something important between two ancidents

logs for nerds (logs of today)

pwnedxd@debian:~$ sudo dmesg | grep -i nvidia | tail -40
[sudo] пароль для pwnedxd:
[ 242.299851] ? _nv000242kms+0x10/0x10 [nvidia_modeset]
[ 242.299866] ? _nv003206kms+0x16/0x40 [nvidia_modeset]
[ 242.299891] ? __pfx_nv_linux_drm_init+0x10/0x10 [nvidia_drm]
[ 242.299899] ? __pfx_nv_drm_register_drm_device+0x10/0x10 [nvidia_drm]
[ 242.299904] ? _nv000219kms+0x3b/0x180 [nvidia_modeset]
[ 242.299931] ? __pfx_nv_linux_drm_init+0x10/0x10 [nvidia_drm]
[ 242.299935] ? nv_drm_probe_devices+0x59/0x70 [nvidia_drm]
[ 242.299971] INFO: task nvidia-powerd:1001 blocked for more than 120 seconds.
[ 242.299975] task:nvidia-powerd state:D stack:0 pid:1001 tgid:1001 ppid:1 flags:0x00004002
[ 242.299991] os_acquire_rwlock_write+0x2b/0x40 [nvidia]
[ 242.300226] _nv051241rm+0x10/0x40 [nvidia]
[ 242.300721] _nv052727rm+0x27c/0x370 [nvidia]
[ 242.301006] _nv039836rm+0x167d/0x2610 [nvidia]
[ 242.301568] _nv000740rm+0x1279/0x2220 [nvidia]
[ 242.301873] rm_init_adapter+0x15d/0x180 [nvidia]
[ 242.302180] nv_start_device+0x102/0x7b0 [nvidia]
[ 242.302407] nv_open_device+0x9d/0x260 [nvidia]
[ 242.302632] nvidia_open+0x212/0x490 [nvidia]
[ 242.302952] INFO: task nvidia-persiste:1092 blocked for more than 120 seconds.
[ 242.302956] task:nvidia-persiste state:D stack:0 pid:1092 tgid:1092 ppid:1 flags:0x00000006
[ 242.302971] nvidia_open+0x1f7/0x490 [nvidia]
[ 242.303282] INFO: task nvidia-settings:2940 blocked for more than 120 seconds.
[ 242.303286] task:nvidia-settings state:D stack:0 pid:2940 tgid:2940 ppid:2936 flags:0x00000002
[ 242.303300] nvidia_unlocked_ioctl+0x6fe/0xa20 [nvidia]
[ 242.303563] INFO: task nvidia-smi:3210 blocked for more than 120 seconds.
[ 242.303566] task:nvidia-smi state:D stack:0 pid:3210 tgid:3210 ppid:2688 flags:0x00000006
[ 242.303579] nvidia_unlocked_ioctl+0x6fe/0xa20 [nvidia]
[ 242.303842] INFO: task nvidia-smi:3211 blocked for more than 120 seconds.
[ 242.303845] task:nvidia-smi state:D stack:0 pid:3211 tgid:3211 ppid:2688 flags:0x00000002
[ 242.303857] ? nvidia_unlocked_ioctl+0x151/0xa20 [nvidia]
[ 242.304086] nvidia_unlocked_ioctl+0x6fe/0xa20 [nvidia]
[ 242.304357] INFO: task nvidia-smi:3369 blocked for more than 120 seconds.
[ 242.304359] task:nvidia-smi state:D stack:0 pid:3369 tgid:3369 ppid:2688 flags:0x00000002
[ 242.304373] nvidia_unlocked_ioctl+0x6fe/0xa20 [nvidia]
[ 242.304645] INFO: task nvidia-smi:3370 blocked for more than 120 seconds.
[ 242.304648] task:nvidia-smi state:D stack:0 pid:3370 tgid:3370 ppid:2688 flags:0x00000002
[ 242.304661] nvidia_unlocked_ioctl+0x6fe/0xa20 [nvidia]
[ 242.304948] nvidia_unlocked_ioctl+0x6fe/0xa20 [nvidia]
[ 242.305189] ? nvidia_unlocked_ioctl+0x20f/0xa20 [nvidia]
[ 242.305456] nvidia_unlocked_ioctl+0x6fe/0xa20 [nvidia]

i aint dealing with that bs can anyone help me solve me this?

Years ago I bought a Pogoplug and loved having scaleable storage. Then the company went under and the device was useless.

Around the same time is was setup up Slackware and saw someone put Linux on their Pogo and ran a LAMP stack. I thought that would be cool to try, then packed my pogo and went about life.

This week all our computers started asking for more space and I remembered the pogo. 24 hours later with a lot of research on 13 year old chat forms and this thing lives again!

It’s running a custom Debian built for the hardware, I think is bookworm. I have Apache2, MariaDB, & PHP installed and I’m taking a victory lap a decade in the making!

Should be fun with the next steps of what I load on it

Hello, I have some Linux experience, and this is my first time running Debian.

When i go to themes, go to simplified settings, I can't change it from anything other then custom and the dark mode is grayed out.

Right now I have things set with applications as blackmate, and that seems to have solved most of the problems, but not necessary all of them, as there are a few dialogue boxes that occasionally pop up in white.

So I wanted to ask, is there a way to set up dark mode in Debian 13 with the Cinnamon Desktop Environment? or is this the best i can hope for?

Thank you

I have been using Linux entirely for about a year and a half now, and it feels incredible to use. I started with beginner-friendly distributions like Zorin and Mint, and eventually discovered Debian back in late December. I immediately loved it because it felt like the perfect middle ground: stable, secure, and configurable without being unnecessarily difficult.

Lately, though, something feels different. I have been trying to get the absolute most out of LXDE, but I feel like I am running up against its limits. I am considering Arch because I want to build a system from the ground up, but I am hesitant. I am not sure if a rolling release model or switching terminal commands will be a steep adjustment, or if Arch might simply be too much maintenance for me.

For those who made a similar jump (or decided to stay on Debian), how was your experience?

(btw, this is what i got lxde to look like after some ricing)

Olá a todos!

Com a prorrogação do prazo para criação de ilustrações para o Debian 14 (Forky), estou trabalhando em um conceito de papel de parede para a área de trabalho, criado no Inkscape, e adoraria receber o feedback de vocês antes de enviá-lo para a wiki/lista de discussão.

Conceito:

Uma cena limpa, em estilo vetorial, com uma pipa ostentando o logotipo do Debian voando em um céu claro. A ideia é simbolizar liberdade, leveza e o alcance do sistema operacional universal.

Perguntas para a comunidade:

• O que vocês acham do tom visual geral para um papel de parede padrão?
• Vocês acham que o contraste e os elementos (como o sol e a linha da pipa) funcionariam bem com ícones da área de trabalho ou painéis do GNOME/KDE?
• Vocês prefeririam uma variante mais escura/noturna ("Modo Escuro") para este conceito?

Qualquer crítica construtiva ou sugestão é muito bem-vinda!

---

UPDATE / EDIT:

Thank you all so much for the feedback! Based on your suggestions, I will be making the following adjustments:

• Cloud refinements: Improving the shape and distribution of the clouds.
• Deeper Dark Mode: Darkening the night variant significantly for better usability.

I’ll post the updated images here as soon as they are ready.

Thanks again for helping improve this concept!

Hi folks,

For the past couple of months, I've been making Debian.tips - a site all about Linux tips, tricks, troubleshooting, how-to guides and so on, with a particular focus on how things are done on Debian.

I've been wanting to build this site for about a decade, but just haven't gotten round to it until now. But, I got laid off recently and now have enough time on my hands to give it some attention. My main goal for it is to teach myself more about Debian and Linux in general. Back when I bought the domain, I was doing some Debian sysadmin work as part of my job as a software engineer, and although my work has moved away from that over the years, thanks to the rise of cloud platforms and DevOps engineers, I've always maintained a personal interest.

But I'd also like it to be useful to other people too. So, if you have any feedback about the site, I'd love to hear it - what works, what doesn't, what can I do to make it more useful/interesting/accessible/etc?

NB: I'm not trying to sell anything, or serve ads, or collect data (outside of simple aggregated usage metrics). This project will earn me zero revenue. The only personal benefit is that it gives me something to talk about during interviews while I look for my next job. And to teach myself more about Debian, of course!

AI disclosure

I've used AI to help me build the site and author the content. Without it, progress would have been much slower and poorer quality, because, quite frankly, AI knows a lot more than I do about how Linux works. I've gone to great lengths to ensure that what's on the site is accurate with a rather convoluted CI/build pipeline, discussed below.

I'm aware of rule #4, but I sought permission from the mod team before posting. I hope that's ok!

How it works behind the scenes

Each page lists a bunch of example commands and the output you can expect from them. In order to keep it 100% accurate, all of those commands are actually run in a sandbox Debian container as part of the CI/build process, and the outputs are checked against what will appear on the site. If anything differs*, the build fails and any new-but-incorrect content does not make it onto the site.

(* = most output is checked exactly, but there are some less restrictive methods - e.g. some outputs are checked by shape if, e.g., numbers or dates differ slightly, and sometimes line ordering is ignored if it's non-deterministic)

Each page also lists the sample data it works on at the top (if applicable) and links through to GitHub for any setup script and the code behind the page from the footer. Each page also provides the command to run the checks for that page on your own machine.

There's more detail about this on the About page

The build process outputs a bunch of static HTML that's then deployed to GitHub Pages, so the site itself ought to load really fast.

Here's the list of all the dedicated command pages. Here's pages for Troubleshooting, Concepts and Recipes (to name but a few of the page types under the "Guides" menu).

And finally, here's a link to the whole thing on GitHub: https://github.com/Synchronium/Debian.tips/

What's next

I have a bit of a plan I'm following, documented here: https://github.com/Synchronium/Debian.tips/blob/main/docs/plans/PLAN-CONTENT.md

Some interesting open questions at the mo:

• What the hell do I do when Debian 14 is released? Do I re-test everything and update the content for just that version? Or maybe pin the content to specific versions? Maybe I could add a table at the bottom of each page to show which specific versions the content works on?
• Similarly, should I think about similar systems to Debian, e.g. Raspberry Pi OS, or even Ubuntu? Maybe just a "This also works on Ubuntu" badge or something like that?

But any useful feedback you have will be prioritised ahead of this! At the end of the day, I'm building this for people, and you are the first bunch of people I've shown it to. I'd like to make this better for all of us (me included!)

Thanks for reading. I hope you find the site helpful. Please do let me know if you have any feedback - good or bad.

I run a 1st gen Lenovo P17 with 2 nvme drives and recently switched back to Debian after i needed something stable for an AI project. Since i have an nvidia GPU, my first try was kubuntu and Ubuntu due to the alleged proprietary driver support. Both had a lot of boot related issues and after half a day of troubleshooting, i gave up and installed Debian. Now running x11 KDE without any issues what so ever. The "boring" distro is the one that just delivers without endless bugs and weird issues that seem to be the standard with most distros nowadays. Anyways, thanks Debian team for building "the Toyota under the the distros".

Recently I bought a gaming keyboard from Razer (BlackWidow v4), but run into an issue when I only use the default HID keyboard driver from Linux. So I tried to install the official driver package (openrazer-driver-dkms)from Debian 13 . But the installation fails because DKMS can't successful build the driver sources.

Here the log from the failed build:

DKMS (dkms-3.2.2) make.log for openrazer-driver/3.10.2 for kernel 6.12.111+deb13-amd64 (x86_64)
Tue Sep 29 09:28:31 PM CEST 2026

Building module(s)
# command: make -j4 KERNELRELEASE=6.12.111+deb13-amd64 driver KERNELDIR=/lib/modules/6.12.111+deb13-amd64/build
-e  
:: Compiling OpenRazer kernel modules
========================================
make -C /lib/modules/6.12.111+deb13-amd64/build M=/var/lib/dkms/openrazer-driver/3.10.2/build/driver modules
make[1]: Entering directory '/usr/src/linux-headers-6.12.111+deb13-amd64'
 CC [M]  /var/lib/dkms/openrazer-driver/3.10.2/build/driver/razerkbd_driver.o
 CC [M]  /var/lib/dkms/openrazer-driver/3.10.2/build/driver/razercommon.o
 CC [M]  /var/lib/dkms/openrazer-driver/3.10.2/build/driver/razerchromacommon.o
 CC [M]  /var/lib/dkms/openrazer-driver/3.10.2/build/driver/razermouse_driver.o
/var/lib/dkms/openrazer-driver/3.10.2/build/driver/razerkbd_driver.c: In function ‘razer_raw_event_bitfield’:
/var/lib/dkms/openrazer-driver/3.10.2/build/driver/razerkbd_driver.c:3729:29: error: too few arguments to function ‘hi
d_report_raw_event’
3729 |                             hid_report_raw_event(hdev, HID_INPUT_REPORT, xdata, sizeof(xdata), 0);
     |                             ^~~~~~~~~~~~~~~~~~~~
In file included from /var/lib/dkms/openrazer-driver/3.10.2/build/driver/razerkbd_driver.c:11:
/usr/src/linux-headers-6.12.111+deb13-common/include/linux/hid.h:1247:5: note: declared here
1247 | int hid_report_raw_event(struct hid_device *hid, enum hid_report_type type, u8 *data,
     |     ^~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/openrazer-driver/3.10.2/build/driver/razerkbd_driver.c:3733:29: error: too few arguments to function ‘hi
d_report_raw_event’
3733 |                             hid_report_raw_event(hdev, HID_INPUT_REPORT, xdata, sizeof(xdata), 0);
     |                             ^~~~~~~~~~~~~~~~~~~~
/usr/src/linux-headers-6.12.111+deb13-common/include/linux/hid.h:1247:5: note: declared here
1247 | int hid_report_raw_event(struct hid_device *hid, enum hid_report_type type, u8 *data,
     |     ^~~~~~~~~~~~~~~~~~~~
make[3]: *** [/usr/src/linux-headers-6.12.111+deb13-common/scripts/Makefile.build:234: /var/lib/dkms/openrazer-driver/
3.10.2/build/driver/razerkbd_driver.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[2]: *** [/usr/src/linux-headers-6.12.111+deb13-common/Makefile:1992: /var/lib/dkms/openrazer-driver/3.10.2/build/
driver] Error 2
make[1]: *** [/usr/src/linux-headers-6.12.111+deb13-common/Makefile:236: __sub-make] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-6.12.111+deb13-amd64'
make: *** [Makefile:38: driver] Error 2

# exit code: 2
# elapsed time: 00:00:04
----------------------------------------------------------------

Seems the used driver sources (v3.10.2) in the official package are too old. I have tried to build the newer driver ( v3.12.4) from the officially GitHub repository which can be successful built.

I have an older workstation with a Xeon W-2295 and 256GB DDR4-2933 RAM. I am fortunate enough to have two 960GB PM9A3 M.2 22110 for booting. Bulk storage is accessed over 10Gb and NFS.
By far the most complicated experience setting up Debian is installing on a redundant boot drive. I get why ZFS has to be complicated because Linux. But why is it also complicated to mirror root with btrfs? I have ran an EFI partition on each drive and mdadm for root in the past as well.
Today you can just select ZFS on both TrueNAS and Proxmox. Both of which are based on Debian.
I think this is way more complicated than it needs to be.
What is your take on this? Do you boot from a ZFS mirror? How did you get there?

Im not a Noob at linux, I have tried --> Mint, Fedora, Zorin OS, Arch

And i wanna try debian. Im downloading the gnome iso Any tips?

[And im a dev btw]
UPDATE : AFTER RECONSIDERATION IM SWITCHING TO FEDORA.
I haven't installed debian yet sooo....

I won't waste your time and ramble on but installing Debian was probably one of the best decisions I've ever made.

I bought my laptop online for peanuts because I needed something cheap and the specs on are, well, not great. It came pre-installed with Windows 10 when I got it. It was somewhat manageable but the CPU was screaming even when no other programs were running. So I decided to try Linux. At first I wanted to try Ubuntu but I couldn't even get the installer to boot before it froze, threw a bunch of errors on screen and then dipped out. So I did a little more research and I tried Debian Trixie. To say that I was shocked at how well everything was running is an understatement. I had successfully turned a piece of e-waste (even at the time the laptop was released) into a usable machine.

So if you've got an old decrepit computer lying around, try Debian. I've been a Windows user my whole life but until "Microslop" decides to get rid of all the useless features they keep making (cough cough Copilot) I dont think I'll change back.

(I included a picture of my specs in case you're curious. Sorry if it looks bad, the screen is super reflective)

Hi,

Please I need to download libarchive13_3.4.3-2+deb11u5_arm64.deb but official repository is not working

System Configuration: · CPU: AMD Ryzen 7 5700G (Stock settings, no overclock) · Motherboard: MSI B450 Pro (BIOS version updated for 5000G series support) · Power Supply: Gamdias Aura GP450 Pro - 450W (80 Plus White) · UPS: Digital X 850VA · OS: Debian Linux (Latest stable) and later tried Fedora (Latest stable)

I purchased my PC 3 months ago with all brand-new parts. It worked flawlessly for the first 90 days with zero issues. Using Debian.

The trigger: I went on a 1-week trip and left the PC completely unplugged. Upon my return, after one month the problems began immediately.

Detailed progression of failures: · Day 1: Was using Chrome for about 30 minutes. PC suddenly powered off instantly (like a power cord was pulled). No UPS beep, no error logs in Debian (journalctl showed nothing—it didn't even boot far enough to log). · Day 2: Powered on the PC and it worked perfectly for 7-8 hours without a single crash. Shut it down normally at night. · Day 3: Tried to boot the PC. It booted to the login screen, but instantly died while I was typing my password (very low load). Ai night Powered it on again and it worked for 2 hours before I shut it down normally.

Specific Symptoms & Observations: 1. Instant Power Loss: When it crashes, it is an absolute, instant blackout. No blue screen, no freeze, no kernel panic—just a hard cutoff. 2. No UPS Involvement: The Digital X UPS makes no beep and does not trigger its overload circuit when the PC shuts off. 3. No OS Logs: Debian has absolutely no crash logs. This indicates the power is being cut at the hardware level before the CPU can even execute code to write a log. 4. Temperature Dependent: The PC seems to work perfectly fine once it has been running for a while (e.g., 7-8 hours on Day 2). The failures are most prominent on a "cold start" (first boot of the morning) or when a sudden load spike occurs (like opening Chrome + updating). 5. Bypass Test: I bypassed the UPS and plugged the PC directly into the wall socket. The issue persists, ruling out the UPS.

Then I take it to the service centre they said they can’t provide support for linux. Installed Windows 11. The problem was solved. I used windows for 2 weeks there was no problem all was fine. But windows is not for me. So I downloaded Fedora gnome. 3-4 days later same problem happens. Boot up pc 1-2 minutes later shutdown. Full black screen and power off. Just like Debian. Now I am just back to windows 11. I used Linux for 5-6 years in my old laptop which is now used by my brother. I miss the linux.

Hardware (desktop PC, not a laptop):

- CPU: Intel Pentium Gold G6400 (Comet Lake), integrated Intel UHD 610 graphics (device ID 9ba8)

- 8GB RAM, Kingston SA400S37240G SSD

- Debian 13 (trixie), fresh install

- XanMod kernel 7.2.7-x64v2-xanmod1 (I use XanMod because on both Mint and Debian, audio sounded like a scratched/broken CD with the stock kernel, and this was the only fix I found for that; also tested Debian's stock 6.12 kernel to rule it out as the cause of the suspend issue, same result on both)

The problem:

After suspending manually (or via idle timeout) and waking up, the system doesn't recover the display. It stays completely black and unresponsive to anything (not even Ctrl+Alt+F2/F1). The machine is otherwise clearly "alive" (fans, LEDs, disk activity), but there's no way to get control back except a hard power-off.

What I've already ruled out:

- Not the kernel: tested both XanMod and Debian's stock kernel, exact same result. Also tried downgrading kernel versions, no change.

- Already updated the BIOS to the latest available version, no change.

- Not the current install or something I installed: did a completely clean reinstall of Debian (fresh partitions, no third-party apps) and it still happens.

- Not Debian-specific: had the exact same issue on Linux Mint before (both the suspend problem and the broken audio) — actually switched to Debian thinking it might be a Mint-specific problem, but both issues are identical on both distros.

- Confirmed with a Debian live USB that suspend/resume works fine there — which is bizarre because it seems to rule out pure hardware/BIOS causes.

- Ruled out a spurious wakeup from automatic hibernation (had the default ~2h HibernateDelaySec triggering a phantom resume midway; already neutralized it with HibernateDelaySec=1000000000 in sleep.conf.d).

Kernel parameters already tried (no luck, combined):

- pci=noaer (this did fix an unrelated 100% CPU issue from PCIe AER errors, but doesn't touch suspend)

- i915.enable_psr=0

- i915.enable_fbc=0

- i915.enable_dc=0

- mem_sleep_default=s2idle (also tried deep, this board's default, same result either way)

- Disabled RP06 and RP08 in /proc/acpi/wakeup (PCIe ports) just in case, no change

What stands out most is that the live USB suspends/resumes perfectly, but the real install (same hardware, same kernel when tested, updated BIOS) always fails — and this repeats identically across two different distros (Mint and Debian). That seems to rule out pure hardware/BIOS, but I can't figure out what differs between a live environment and a normal install that could be interfering with the i915 resume path.

Has anyone seen a similar pattern with Comet Lake + UHD 610 on a desktop build? Is there something specific to a regular install (some service, a loaded module, something in systemd-logind) that a live session wouldn't have, that could be interfering with i915's resume?

Thanks in advance, genuinely out of ideas at this point.

It is no different than the non-graphical install. Only if you want to install primarily through text or with graphics. I actually found I prefer the non-graphical. Ive installed Debian on my entire ecosystem from servers, laptops, and even converted my gaming desktop a while ago with graphical install. I had to reinstall Debian on one of my main laptops and decided I would try out the non-graphical installation.

The graphical install always has me squinting looking for the right options or checking if my root or encryption keys match before setting them. It also takes much longer to completely wipe and reinstall Debian with LUKS encryption.

What's the purpose of the graphical installer? I understand making it easier for people who are not very "tech-saavy" but its the same exact options as the non-graphical without the headache...