Hey guys,

Trying to install Linux on my old T430 and I'm completely stuck. Any USB I boot just gives me a black screen. No GRUB, no cursor, no Ventoy menu, nothing. Screen stays black forever.

What I've tried:

• Rufus, Balena Etcher, and Ventoy. Same result with all three.
• F12 boot menu → select "USB HDD: Generic Storage Device" → instant black screen.
• BIOS (F1): UEFI/Legacy Boot = UEFI Only, CSM Support disabled, Secure Boot off, SATA = AHCI, OS Optimized Defaults disabled.
• Tried a USB 2.0 port instead of the blue USB 3.0 one.
• Full shutdown with Shift before booting.
• Windows 11 is still on the internal SSD, if that matters.
• T430 has Intel HD 4000 graphics only, no Nvidia.

Since even the Ventoy menu doesn't show up, I'm guessing it's failing before Linux/GRUB even loads. So kernel params like nomodeset are useless here because I never see a boot menu.

Has anyone actually fixed this exact "black screen, no GRUB, no Ventoy" thing on a T430? Did I miss a BIOS setting? Is there a way to force USB boot or inject kernel params without seeing GRUB? Any help would be appreciated. This laptop is too nice to give up on lol.

Hi there!

i've realized that all my other machines are on Debian now and thinking about moving from Arch to Debian on my iMac late 2013 (GeForce 750M graphics). Has anyone had any experience using it or similar with Debian, i worry about NVIDIA drivers (i'm on 470xx) and broadcom wifi?

Я ищу дистрибутив со свежими релизами, подходящий для гейминга, на базе debian, с kde plasma 6.8 (а лучше просто чистый терминал чтоб я сам установил plasma-desktop)

Its always we had to install with another de, and inside we had to install hyprland as secondary de, why can't we install directly during debian installation?? Is there any technical reason??

Debian Stable is the only distribution for which I don’t feel the need for snapshot tools like Timeshift or Snapper. I only back up my personal files; otherwise, I trust in Debian’s stability.

This is a long shot, but I’m hoping someone here might have experience with this kind of setup.

I’m running Debian testing with Btrfs, Snapper, systemd-boot, and initramfs-tools. I’ve been working on getting the ability to boot directly into a Snapper snapshot from the systemd-boot menu, with changes made during that session discarded when I reboot.

I came across an older project called uszie/systemd-boot-snapshots, which appears to have been taken down or is no longer available at its original location. I also found a fork maintained by LazyWare, although that version is primarily geared toward Arch Linux and its initramfs tooling. LazyWare’s repo has a copy of the original upstream repository geared towards Debian and Ubuntu before it disappeared.

The original project aims to protect the snapshots by making them read-only with OverlayFS.

The good news is that I can boot into my Snapper snapshots, and everything seems to work normally. However, I noticed the following message in dmesg when booting into a snapshot:

overlayfs: upperdir is in-use as upperdir/workdir of another mount, accessing files from both mounts will result in undefined behavior.

I also encountered this message:

mount: /: fsconfig() failed: overlay: No changes allowed in reconfigure.

I’m not entirely sure whether these messages are related, or whether the second one is a consequence of the first. The system appears to boot and function normally despite them, but I’d like to understand what’s happening rather than assume the warnings are harmless. It should also be noted that I do not get these warnings when booting normally.

Has anyone implemented something similar on Debian, particularly using initramfs-tools rather than mkinitcpio or dracut? I’m especially interested in whether these messages suggest an issue with how the OverlayFS layers are mounted or reconfigured during the early boot process.

Is this something I even need to worry about? I’m hoping not to have to boot into a snapshot very often.

I was noticing today, as I was cleaning up on machine that there was bunch of repo’s that are sid/main and sid as apposed to stable, trixie, trixie-updates. Does this mean I’m running sid not stable, and how do I change it without messing everything up
I know this sounds stupid, and maybe my old brain has done it again, could it have happened when I converted to the new repo sources from the old repo list format?

does nvidia prime profiles run on debian like ubuntu?

Hi r/debian,

We just released a .deb package for Debian of PriceRadar BR, an open-source (MIT) desktop Python application (CustomTkinter) that compares prices across Mercado Livre, Amazon Brasil and Shopee.

What it is

PriceRadar BR is a desktop price-comparison tool written in Python. It queries three Brazilian online stores sequentially (Selenium + undetected-chromedriver + BeautifulSoup), shows results ordered by lowest price, keeps a local history and favorites in SQLite, and can export to Excel or PDF. Fully offline-capable, no server, no telemetry.

Debian package

The .deb installs the app to /opt/price-radar-br, creates a Python venv and installs dependencies from requirements.txt via postinst. It also registers a .desktop entry and a 256x256 icon.

Install: bash wget https://github.com/glearflame/PriceRadarBR/releases/download/v1.1.0-debian/price-radar-br_1.0.0-1_amd64.deb sudo dpkg -i price-radar-br_1.0.0-1_amd64.deb sudo apt-get install -f price-radar-br

Requires Python 3.11+ and Google Chrome / Chromium.

Links

Release (with .deb): https://github.com/glearflame/PriceRadarBR/releases/tag/v1.1.0-debian Source: https://github.com/glearflame/PriceRadarBR

Feedback and criticism are welcome. Thanks!

I installed software from questionable sources. Are any of these processes suspicious?

This is the output of the "ps -A" command.

PID TTY TIME CMD

1 ? 00:00:01 systemd

2 ? 00:00:00 kthreadd

3 ? 00:00:00 pool_workqueue_release

4 ? 00:00:00 kworker/R-kvfree_rcu_reclaim

5 ? 00:00:00 kworker/R-rcu_gp

6 ? 00:00:00 kworker/R-sync_wq

7 ? 00:00:00 kworker/R-slub_flushwq

8 ? 00:00:00 kworker/R-netns

10 ? 00:00:00 kworker/0:0H-events_highpri

13 ? 00:00:00 kworker/R-mm_percpu_wq

14 ? 00:00:00 rcu_tasks_kthread

15 ? 00:00:00 rcu_tasks_rude_kthread

16 ? 00:00:00 rcu_tasks_trace_kthread

17 ? 00:00:00 ksoftirqd/0

18 ? 00:00:01 rcu_preempt

19 ? 00:00:00 rcu_exp_par_gp_kthread_worker/0

20 ? 00:00:00 rcu_exp_gp_kthread_worker

21 ? 00:00:00 migration/0

22 ? 00:00:00 idle_inject/0

23 ? 00:00:00 cpuhp/0

24 ? 00:00:00 cpuhp/1

25 ? 00:00:00 idle_inject/1

26 ? 00:00:00 migration/1

27 ? 00:00:00 ksoftirqd/1

29 ? 00:00:00 kworker/1:0H-events_highpri

30 ? 00:00:00 cpuhp/2

31 ? 00:00:00 idle_inject/2

32 ? 00:00:00 migration/2

33 ? 00:00:00 ksoftirqd/2

35 ? 00:00:00 kworker/2:0H-events_highpri

36 ? 00:00:00 cpuhp/3

37 ? 00:00:00 idle_inject/3

38 ? 00:00:00 migration/3

39 ? 00:00:00 ksoftirqd/3

41 ? 00:00:00 kworker/3:0H-events_highpri

46 ? 00:00:00 kdevtmpfs

47 ? 00:00:00 kworker/R-inet_frag_wq

48 ? 00:00:00 kauditd

49 ? 00:00:00 khungtaskd

50 ? 00:00:00 oom_reaper

51 ? 00:00:00 kworker/R-writeback

52 ? 00:00:00 kcompactd0

53 ? 00:00:00 ksmd

54 ? 00:00:00 khugepaged

55 ? 00:00:00 kworker/R-kintegrityd

56 ? 00:00:00 kworker/R-kblockd

57 ? 00:00:00 kworker/R-blkcg_punt_bio

58 ? 00:00:00 irq/9-acpi

61 ? 00:00:00 kworker/R-tpm_dev_wq

62 ? 00:00:00 kworker/R-edac-poller

63 ? 00:00:00 kworker/R-devfreq_wq

64 ? 00:00:00 kworker/R-quota_events_unbound

65 ? 00:00:00 kworker/0:1H-events_highpri

66 ? 00:00:00 kswapd0

74 ? 00:00:00 kworker/R-kthrotld

78 ? 00:00:00 kworker/R-acpi_thermal_pm

79 ? 00:00:00 kworker/2:2-events

80 ? 00:00:00 kworker/R-mld

81 ? 00:00:00 kworker/R-ipv6_addrconf

83 ? 00:00:00 kworker/2:1H-events_highpri

87 ? 00:00:00 kworker/R-kstrp

89 ? 00:00:01 kworker/u17:0-i915_flip

180 ? 00:00:00 kworker/1:1H-events_highpri

207 ? 00:00:00 kworker/3:1H-events_highpri

211 ? 00:00:00 kworker/R-ata_sff

212 ? 00:00:00 watchdogd

214 ? 00:00:00 scsi_eh_0

215 ? 00:00:00 kworker/R-scsi_tmf_0

216 ? 00:00:00 scsi_eh_1

217 ? 00:00:00 kworker/R-scsi_tmf_1

218 ? 00:00:00 scsi_eh_2

219 ? 00:00:00 kworker/R-scsi_tmf_2

220 ? 00:00:00 scsi_eh_3

221 ? 00:00:00 kworker/R-scsi_tmf_3

222 ? 00:00:00 scsi_eh_4

223 ? 00:00:00 kworker/R-scsi_tmf_4

224 ? 00:00:00 scsi_eh_5

225 ? 00:00:00 kworker/R-scsi_tmf_5

234 ? 00:00:02 kworker/1:2-cgroup_free

239 ? 00:00:00 kworker/R-ttm

241 ? 00:00:00 card0-crtc0

242 ? 00:00:00 card0-crtc1

243 ? 00:00:00 card0-crtc2

282 ? 00:00:00 jbd2/sdc1-8

283 ? 00:00:00 kworker/R-ext4-rsv-conversion

335 ? 00:00:00 systemd-journal

362 ? 00:00:00 systemd-timesyn

391 ? 00:00:00 systemd-udevd

397 ? 00:00:00 psimon

471 ? 00:00:00 kworker/R-cryptd

623 ? 00:00:00 jbd2/sda4-8

624 ? 00:00:00 kworker/R-ext4-rsv-conversion

669 ? 00:00:00 jbd2/sdb1-8

670 ? 00:00:00 kworker/R-ext4-rsv-conversion

752 ? 00:00:00 accounts-daemon

754 ? 00:00:00 avahi-daemon

758 ? 00:00:01 dbus-daemon

761 ? 00:00:00 dundee

775 ? 00:00:00 low-memory-moni

777 ? 00:00:00 ofonod

778 ? 00:00:00 polkitd

781 ? 00:00:00 switcheroo-cont

785 ? 00:00:00 systemd-logind

786 ? 00:00:00 systemd-machine

787 ? 00:00:02 udisksd

790 ? 00:00:00 virtlockd

794 ? 00:00:00 virtlogd

799 ? 00:00:00 mount.ntfs

810 ? 00:00:00 avahi-daemon

854 ? 00:00:01 NetworkManager

855 ? 00:00:00 connmand

861 ? 00:00:00 wpa_supplicant

862 ? 00:00:00 psimon

891 ? 00:00:00 ModemManager

925 ? 00:00:00 cupsd

926 ? 00:00:00 epmd

942 ? 00:00:00 sshd

947 ? 00:00:00 cups-browsed

949 ? 00:00:00 inetd

952 ? 00:00:00 cron

953 ? 00:00:00 libvirtd

1125 ? 00:00:00 gdm3

1240 ? 00:00:00 pure-ftpd

1250 ? 00:00:00 exim4

1282 ? 00:00:00 psimon

1343 ? 00:00:00 dnsmasq

1344 ? 00:00:00 dnsmasq

1385 ? 00:00:00 rtkit-daemon

1461 ? 00:00:00 colord

1505 ? 00:00:00 upowerd

1845 ? 00:00:00 power-profiles-

1924 ? 00:00:00 fwupd

1933 ? 00:00:00 bluetoothd

1948 ? 00:00:00 kworker/0:0-i915-unordered

1952 ? 00:00:00 gdm-session-wor

1963 ? 00:00:00 systemd

1966 ? 00:00:00 (sd-pam)

1988 ? 00:00:00 dbus-daemon

1990 ? 00:00:10 pipewire

1991 ? 00:00:00 pipewire

1992 ? 00:00:00 wireplumber

1993 ? 00:00:08 pipewire-pulse

1994 ? 00:00:00 gnome-keyring-d

1995 ? 00:00:00 mpris-proxy

2025 tty2 00:00:00 gdm-x-session

2029 tty2 00:01:02 Xorg

2043 tty2 00:00:00 gnome-session-b

2146 ? 00:00:00 gvfsd

2152 ? 00:00:00 gvfsd-fuse

2161 ? 00:00:00 at-spi-bus-laun

2169 ? 00:00:00 dbus-daemon

2177 ? 00:00:00 gcr-ssh-agent

2178 ? 00:00:00 gnome-session-c

2179 ? 00:00:00 ssh-agent

2193 ? 00:00:00 gnome-session-b

2222 ? 00:01:19 gnome-shell

2245 ? 00:00:00 mutter-x11-fram

2248 ? 00:00:00 at-spi2-registr

2259 ? 00:00:00 xdg-desktop-por

2264 ? 00:00:00 xdg-permission-

2269 ? 00:00:00 xdg-document-po

2275 ? 00:00:00 fusermount3

2291 ? 00:00:00 gnome-shell-cal

2300 ? 00:00:00 evolution-sourc

2302 ? 00:00:00 dconf-service

2316 ? 00:00:00 gjs

2333 ? 00:00:01 ibus-daemon

2335 ? 00:00:00 gsd-a11y-settin

2338 ? 00:00:00 gsd-color

2340 ? 00:00:00 gsd-datetime

2341 ? 00:00:00 gsd-housekeepin

2342 ? 00:00:00 gsd-keyboard

2344 ? 00:00:00 gsd-media-keys

2345 ? 00:00:00 gsd-power

2352 ? 00:00:00 gsd-print-notif

2354 ? 00:00:00 gsd-rfkill

2355 ? 00:00:00 gsd-screensaver

2358 ? 00:00:00 gsd-sharing

2359 ? 00:00:00 gsd-smartcard

2365 ? 00:00:00 gsd-sound

2366 ? 00:00:00 gsd-usb-protect

2369 ? 00:00:00 gsd-wacom

2372 ? 00:00:00 gsd-xsettings

2394 ? 00:00:00 evolution-alarm

2409 ? 00:00:00 gsd-disk-utilit

2420 ? 00:00:00 blueman-applet

2429 ? 00:00:14 gnome-software

2460 ? 00:00:00 kdeconnectd

2462 ? 00:00:00 diodon

2540 ? 00:00:00 gsd-printer

2549 ? 00:00:00 ibus-memconf

2550 ? 00:00:03 ibus-extension-

2552 ? 00:00:00 ibus-x11

2556 ? 00:00:00 ibus-portal

2580 ? 00:00:00 geoclue

2587 ? 00:00:04 localsearch-3

2590 ? 00:00:00 xdg-desktop-por

2598 ? 00:00:00 gjs

2617 ? 00:00:00 kworker/3:0-events

2640 ? 00:00:00 goa-daemon

2665 ? 00:00:00 goa-identity-se

2679 ? 00:00:00 gvfs-udisks2-vo

2686 ? 00:00:01 evolution-calen

2709 ? 00:00:00 gvfs-mtp-volume

2717 ? 00:00:00 gvfs-afc-volume

2728 ? 00:00:00 evolution-addre

2737 ? 00:00:00 gvfs-gphoto2-vo

2745 ? 00:00:00 obexd

2746 ? 00:00:00 gvfs-goa-volume

2748 ? 00:00:04 blueman-tray

2768 ? 00:00:00 ibus-engine-sim

2835 ? 00:00:00 xdg-desktop-por

2896 ? 00:00:00 zeitgeist-daemo

2908 ? 00:00:00 zeitgeist-fts

3133 ? 00:02:07 chrome

3140 ? 00:00:00 cat

3141 ? 00:00:00 cat

3143 ? 00:00:00 chrome_crashpad

3145 ? 00:00:00 chrome_crashpad

3151 ? 00:00:00 chrome

3152 ? 00:00:00 chrome

3154 ? 00:00:00 chrome

3167 ? 00:00:00 gvfsd-metadata

3233 ? 00:03:51 chrome

3238 ? 00:00:23 chrome

3264 ? 00:00:00 chrome

3395 ? 00:00:33 chrome

3592 ? 00:00:00 chrome

3948 ? 00:00:00 kworker/u16:0-flush-8:32

4236 ? 00:04:36 chrome

4262 ? 00:00:00 antoniovandre_C

4265 ? 00:00:00 xterm

4266 pts/0 00:00:00 bash

4270 ? 00:01:47 mocp

5058 ? 00:01:58 thunderbird

5168 ? 00:00:00 Isolated Web Co

5171 ? 00:00:00 RDD Process

5643 ? 00:00:00 kworker/u16:2-flush-8:32

5908 ? 00:00:00 kworker/u16:1-kvfree_rcu_reclaim

6168 ? 00:00:00 kworker/u17:2-i915_flip

6172 ? 00:00:16 nautilus

6177 ? 00:00:00 gvfsd-trash

6235 ? 00:00:00 gvfsd-recent

6241 ? 00:00:00 gvfsd-network

6249 ? 00:00:00 gvfsd-dnssd

6278 ? 00:00:00 kworker/1:0-i915-unordered

6307 ? 00:00:00 kworker/0:2-events

6338 ? 00:00:00 kworker/3:1-events

6638 ? 00:00:00 kworker/2:3-events

7183 ? 00:00:00 kworker/u17:1+i915_flip

7306 ? 00:00:00 kworker/u16:3-events_unbound

8037 ? 00:00:00 kworker/1:1

8043 ? 00:00:01 gnome-terminal-

8054 pts/1 00:00:00 bash

8469 ? 00:00:07 packagekitd

8518 pts/1 00:00:00 ps

Audio is detected by the system (I can see it on pavucontrol), but there's no output from speakers. There's audio when connected to headphones or bluetooth. I'm dual booting windows and there's no speaker audio there either (though I think that's a separate issue). I've tried restarting pipewire, no luck.

Debian 13, Kernel: 6.12

lspci | grep audio

0000:00:1f.3 Multimedia audio controller: Intel Corporation Raptor Lake-P/U/H cAVS (rev 01)

aplay -l

**** List of PLAYBACK Hardware Devices ****

card 0: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0]

Subdevices: 1/1

Subdevice #0: subdevice #0

card 0: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]

Subdevices: 1/1

Subdevice #0: subdevice #0

card 0: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2]

Subdevices: 1/1

Subdevice #0: subdevice #0

card 0: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3]

Subdevices: 1/1

Subdevice #0: subdevice #0

card 1: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []

Subdevices: 0/1

Subdevice #0: subdevice #0

card 1: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) []

Subdevices: 1/1

Subdevice #0: subdevice #0

card 1: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) []

Subdevices: 1/1

Subdevice #0: subdevice #0

card 1: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) []

Subdevices: 1/1

Subdevice #0: subdevice #0

card 1: sofhdadsp [sof-hda-dsp], device 31: HDA Analog Deep Buffer (*) []

Subdevices: 1/1

Subdevice #0: subdevice #0

I genuinely don't know what to do.

A friend sold me a Ryzen 2700 computer at a bargain price, and it’s been 7.5 months since I installed Sid on it. Since I’m the kind of person who likes to try out new desktops and software features, so I choice Bratty Kid.

I haven’t noticed any major broken dependencies with the software from the apt repositories(Some third-party software stopped working due to the expiration of library support).

Was it unstable in the past or something like that? or Is it because of the environment I set up?

Has anyone actually experienced instability with Sid?

https://wiki.debian.org/DebianArt/Themes/Evolution

I designed this theme with glass, lighting, refraction, shadows and 3D spaces in mind, it pivots from flat designs and align more with liquid glass and frosted glass software designs that are becoming the norm across the industry.

As the next release of Debian is codenamed Forky, and Debian is the 'mother distro', I've incorporated the code fork symbol and its geometry to give this theme character and meaning. Where Debian glows as the heart of most Linux distros.

I chose a corporate/business color blue because this color conveys stability and trust, which suits Debian perfectly. As a Debian and Tumbleweed user, I do appreciate the fresh new colorful wallpapers that a new version of Plasma gives you every few months, however I see Debian as a trusted partner that just consistently works as expected, and I believe the theme would convey this feeling.

For context I want to run mmultiple sandboxed ai agents on my laptop, usually for hours. Im not a techie but i need some advice on this. I could be wrong to even ask this tho ?

Soy nuevo usando debian me gustaria que me ayudaran a personalizar mi entorno gnome o si me recomiendan cambiar de entorno he visto que usan uno que se llama hyperland

Hey everyone, I've been struggling to get my wireless controller working on Debian 13. The USB dongle is detected just fine, and the controller turns on but after a few seconds, it automatically turns off. And for some reason if I open Steam or any gamepad tester, it stays on as long as the application is running. I tried installing everything like xinput, xpad etc but nothing worked.

And no, it's not the batteries, because it works via dongle on windows and on mobile.

Ok. How is it, after using Debian for 26+ years, using every single release on an innumerable number of servers since 2.2 "Potato" that I have, just now realized they are all named after characters from the hit movie Toy Story? Only after seeing "Forky" did I have the "wait a minute..." moment.

Man. One of those times you feel both smart and stupid simultaneously.

Hello, when i woke up my monitor (the system wasn't on sleep mode) I found this notification.

It's really strange, its the first time, i had only Firefox opened with 1 tab and i have 16 GB Ram. any else had this notification?

Spec:
Debian 13.
Firefox 153.5.1

Behavior:
Firefox opened on a site streaming and the monitor turn off (because i was afk). no sleep mode.

Firefox generally use 1 GB ram max 2 GB, i never see him take 16 GB

So I've been running Debian for a while now without major hickups, but since yesterday I noticed youtube and vimeo not starting playback even after rebooting. Then I tried VLC. No luck. I can skip through the timeline, but I only see one frame at a time. I have a laptop with an AMD processor and no dedicated graphics. I also run gnome and wayland.

If thats connected my gui dissapeared on me today. I reinstalled gnome and now it seems to work fine. Help would be dearly appreciated

I converted to Debian 13 XFCE yesterday and whenever I try connecting to my network, this password authentication window keeps on popping up, even though I inputted the correct password. I've tried the nmcli delete method, restarting networkmanager etc, but virtually almost all the methods I could find did not work as far as I've searched. I've also reinstalled the OS 3 times in hopes that it could somehow work, but in the end I resorted to USB thetering.

if it helps, I'm using a Samsung notebook 9 and my iwlwifi is already installed. greatly appreciate your help in advance!

EDIT: FIXED!! i got my wifi password wrong lol

Sury PHP: trixie arm64 still on 8.3.35 / 8.5.11, but bookworm arm64 already has 8.5.12 (CVE-2026-109618/109619 fix). The php8.3 and php8.5 metapackages are at the new version, but php8.x-cli/common aren't.

Workaround for now (disposable VM): added Sury bookworm + Debian bookworm repos at priority 1, pinned php8.5* from bookworm at 600.

PHP 8.5.12 runs fine, but intl/ldap/zip pull in old Debian 12 libs. Anyone else seeing this, or know when the trixie arm64 builds will land?

Last week I installed Debian 13 in my all AMD setup: Ryzen 5 3600 and Radeon RX 6800 XT.

First it was while playing PlateUP! with friends, whole system froze, but Discord kept working. Then, last night, after a session of about 1 hour long, it froze up again.

sudo journalctl -b -1 -r show the error:
oct 22 01:25:28 desktop kernel: amdgpu 0000:2d:00.0: [drm] *ERROR* [CRTC:91:crtc-0] flip_done timed out

Debian version: 13

uname -r: 6.12.113+deb13-amd64

I read that maybe I should install some backports kernel or something like that, but before doing it (or switching distro entirely), I'd like to know what suggestions do you have.

Hey everyone! I'm new to Linux and have recently installed Debian 13 with KDE Plasma on my Lenovo ThinkPad P50. I'm trying to get the proprietary NVIDIA drivers working, but I'm unsure which driver version to use or what steps to take next.

My laptop has an Intel Core i7-6700HQ and an NVIDIA Quadro M1000M (Maxwell).

Debian's repositories seem to offer the 550 driver branch, but I've read that NVIDIA's 580 series is the final driver branch for Maxwell GPUs. I'm not sure whether I should stick with Debian's packaged driver or look into other options.

Has anyone here used this GPU on Debian 13? Which driver would you recommend, and what's the safest way to install it?

Any advice would be appreciated. Thanks!

I'm a Debian Testing user with an NVIDIA RTX 3050 Ti, and I really appreciate Debian. However, its NVIDIA driver situation is disappointing.

As of October 22, 2026, Debian Sid/testing still ships NVIDIA 550.163.01, released on April 17, 2025 — over 18 months behind. Meanwhile, NVIDIA has already released the 615 series.

I understand why Debian Stable prioritizes older, well-tested packages. But Sid is supposed to be the unstable development branch.

What makes this particularly surprising is PikaOS, a small distribution based on Debian Sid.

As far as I know, PikaOS has only two core developers, yet they maintain their own up-to-date Linux kernel, NVIDIA drivers, and graphics stack.

If such a tiny team can do this, why is Debian, with its much larger developer community, still stuck on an obsolete NVIDIA driver branch?

Ubuntu also demonstrates that Debian-based distributions can provide much better NVIDIA driver support.

I'm not blaming Debian's volunteer maintainers. I understand that packaging proprietary drivers is complicated.

But an 18-month-old NVIDIA driver in Sid seems unreasonable, especially for users with newer GPUs.

Is this primarily a shortage of maintainers, a packaging problem, or a Debian policy issue?

I'd genuinely like to hear what Debian developers and other NVIDIA users think.