[Software] Why is Debian not automatically upgraded to the new version?

[hack3rcon]

Hello,
I always use the following commands to update Debian:

Code: Select all

# apt update
# apt upgrade

But, my Debian version is 10 not 12. Why?


Thank you.

[Aki]

Because probably you are tracking Debian 10.

See release notes of Debian 10 for your instructions to upgrade to Debian 11 and so forth to Debian 12.

[Random_Troll]

Please follow https://www.debian.org/releases/bullsey ... ng.en.html & https://www.debian.org/releases/bookwor ... ng.en.html to upgrade from Debian 10 to Debian 12. Be sure to upgrade to bullseye first then bookworm.

Good luck and thanks for testing the new release

[kent_dorfman766]

Having the maintenance update process automatically jump to a new release would be a bad idea. It's not like new releases EVER have bugs, right? New releases introduce new features and sometimes config changes that may be subtly incompatible with older releases.

Updating to a new release should always be an deliberate and well planned process.

[Random_Troll]

If the OP wants to track stable automatically they can replace the codenames in /etc/apt/sources.list{,.d/*} with the distribution name (ie, "stable"). Not a good idea though, as kent_dorfman766 notes.

[hack3rcon]

Hello,
Thank you so much for all replies.
The contents of current source.list file is:

Code: Select all

# Contrib non-free

deb http://deb.debian.org/debian buster main contrib non-free
deb-src http://deb.debian.org/debian buster main contrib non-free

deb http://deb.debian.org/debian-security/ buster/updates main contrib non-free
deb-src http://deb.debian.org/debian-security/ buster/updates main contrib non-free

deb http://deb.debian.org/debian buster-updates main contrib non-free
deb-src http://deb.debian.org/debian buster-updates main contrib non-free

deb http://deb.debian.org/debian buster-backports main contrib non-free
deb-src http://deb.debian.org/debian buster-backports main contrib non-free


# Tor
deb https://deb.torproject.org/torproject.org buster main
deb-src https://deb.torproject.org/torproject.org buster main

If I change all the words from buster to the bullseye, then is it not a good idea?
Why doesn't Debian do this automatically? What is the usage of the apt dist-upgrade command?

[peer]

buster to bullseye:
1. sudo apt update && sudo apt full-upgrade
2. change"buster" to "bulseye" in /etc/apt/sources.list
3. sudo apt update && sudo apt full-upgrade
4. sudo apt autoremove
5 reboot
bullseye to bookworm:
1. sudo apt update && sudo apt full-upgrade
2. change "bullseye"to "bookworm" in /etc/apt/sources.list
3. add "non-free=firmware" to all lines in /etc/apt/sources.list
4. sudo apt update && sudo apt full-upgrade
5. sudo apt autoremove
5 reboot

[Hallvor]

Hello,
I always use the following commands to update Debian:

Code: Select all

# apt update
# apt upgrade

But, my Debian version is 10 not 12. Why?


Thank you.

I want to keep my laptop at work following Debian bullseye as long as it gets support. I'd be pretty annoyed if it suddenly was upgraded to bookworm.

[hack3rcon]

buster to bullseye:
1. sudo apt update && sudo apt full-upgrade
2. change"buster" to "bulseye" in /etc/apt/sources.list
3. sudo apt update && sudo apt full-upgrade
4. sudo apt autoremove
5 reboot
bullseye to bookworm:
1. sudo apt update && sudo apt full-upgrade
2. change "bullseye"to "bookworm" in /etc/apt/sources.list
3. add "non-free=firmware" to all lines in /etc/apt/sources.list
4. sudo apt update && sudo apt full-upgrade
5. sudo apt autoremove
5 reboot

Hello,
I did it, but during the update my screen turned black and... I rebooted my system, but not matters. I just see the mouse cursor for some seconds, but... .I pressed CTRL + ALT + F1, F2, F3, F4 etc., but nothing happened.
How to solve it?

[Random_Troll]

Restore your backup and follow the official upgrade guides instead. They have a lot of detail that's missing from peer's shortcut and that detail might be critical.

[hack3rcon]

Restore your backup and follow the official upgrade guides instead. They have a lot of detail that's missing from peer's shortcut and that detail might be critical.

Hello,
Thank you so much for your reply.
How can I see a terminal? Any trick? I don't like to fresh install.
Can I use a Debian bootable USB to fix my system?
How about editing the grub parameters?

[hack3rcon]

Hello,
I upgraded my Debian from Buster to Bullseye and I just see a black screen. I must add "nomodeset" to the grub and then use "startx" to use my Debian. Some information are:

Code: Select all

# dmesg --level=err
[   78.892963] snd_hda_intel 0000:00:03.0: HSW/BDW HD-audio HDMI/DP requires binding with gfx driver
[  408.815563] DMAR: DRHD: handling fault status reg 2
[  408.815576] DMAR: [DMA Read] Request device [05:00.0] PASID ffffffff fault addr ffbf9000 [fault reason 06] PTE Read access is not set
[  422.898367] DMAR: DRHD: handling fault status reg 2
[  422.898374] DMAR: [DMA Read] Request device [05:00.0] PASID ffffffff fault addr ffbe9000 [fault reason 06] PTE Read access is not set
[  424.351935] DMAR: DRHD: handling fault status reg 2
[  424.351956] DMAR: [DMA Read] Request device [05:00.0] PASID ffffffff fault addr ffb9f000 [fault reason 06] PTE Read access is not set
[  427.864401] DMAR: DRHD: handling fault status reg 2
[  427.864419] DMAR: [DMA Read] Request device [05:00.0] PASID ffffffff fault addr ffba3000 [fault reason 06] PTE Read access is not set
#
# dmesg --level=warn
[    0.032545] You have booted with nomodeset. This means your GPU drivers are DISABLED
[    0.032546] Any video related functionality will be severely degraded, and you may not even be able to suspend the system properly
[    0.032546] Unless you actually understand what nomodeset does, you should reboot without enabling it
[    0.117809] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
[    0.117809]  #5 #6 #7
[    0.146392] pmd_set_huge: Cannot satisfy [mem 0xf8000000-0xf8200000] with a huge-page mapping due to MTRR override.
[    1.042619] i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
[    1.258555] ACPI Warning: SystemIO range 0x0000000000001828-0x000000000000182F conflicts with OpRegion 0x0000000000001800-0x000000000000187F (\PMIO) (20200925/utaddress-204)
[    1.258566] ACPI Warning: SystemIO range 0x0000000000001C40-0x0000000000001C4F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20200925/utaddress-204)
[    1.258571] ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20200925/utaddress-204)
[    1.258574] ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20200925/utaddress-204)
[    1.258578] ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20200925/utaddress-204)
[    1.258581] ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20200925/utaddress-204)
[    1.258585] lpc_ich: Resource conflict(s) found affecting gpio_ich
[    1.272348] r8169 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
[    9.553904] systemd[1]: /lib/systemd/system/plymouth-start.service:16: Unit configured to use KillMode=none. This is unsafe, as it disables systemd's process lifecycle management for the service. Please update your service to use a safer KillMode=, such as 'mixed' or 'control-group'. Support for KillMode=none is deprecated and will eventually be removed.
[   12.416746] nvidia: loading out-of-tree module taints kernel.
[   12.416753] nvidia: module license 'NVIDIA' taints kernel.
[   12.416754] Disabling lock debugging due to kernel taint
[   12.440204] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  390.157  Wed Oct 12 09:19:07 UTC 2022 (using threaded interrupts)
[   14.319255] at24 0-0050: supply vcc not found, using dummy regulator
[   14.319850] at24 0-0051: supply vcc not found, using dummy regulator
[   14.320411] at24 0-0052: supply vcc not found, using dummy regulator
[   14.320934] at24 0-0053: supply vcc not found, using dummy regulator
[   26.047476] resource sanity check: requesting [mem 0x000e0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000e0000-0x000e3fff window]
[   26.047668] caller _nv027866rm+0x58/0x90 [nvidia] mapping multiple BARs
[   26.157020] resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000d0000-0x000d3fff window]
[   26.157255] caller _nv001015rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs
[   37.022022] VBoxNetFlt: Successfully started.
[   37.036577] VBoxNetAdp: Successfully started.
[   39.878736] kauditd_printk_skb: 11 callbacks suppressed
[   78.919524] resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000d0000-0x000d3fff window]
[   78.919714] caller _nv001015rm+0x1bf/0x1f0 [nvidia] mapping multiple BARs
#
# dmesg --level=debug
[    0.000591] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[    0.000593] e820: remove [mem 0x000a0000-0x000fffff] usable
[    0.000604] MTRR default type: uncachable
[    0.000605] MTRR fixed ranges enabled:
[    0.000606]   00000-9FFFF write-back
[    0.000607]   A0000-BFFFF uncachable
[    0.000607]   C0000-CFFFF write-protect
[    0.000608]   D0000-E7FFF uncachable
[    0.000609]   E8000-FFFFF write-protect
[    0.000609] MTRR variable ranges enabled:
[    0.000610]   0 base 0000000000 mask 7C00000000 write-back
[    0.000611]   1 base 0400000000 mask 7FE0000000 write-back
[    0.000612]   2 base 0420000000 mask 7FF0000000 write-back
[    0.000613]   3 base 00E0000000 mask 7FE0000000 uncachable
[    0.000613]   4 base 00D0000000 mask 7FF0000000 uncachable
[    0.000614]   5 base 00CC000000 mask 7FFC000000 uncachable
[    0.000614]   6 base 00CB800000 mask 7FFF800000 uncachable
[    0.000615]   7 base 042F000000 mask 7FFF000000 uncachable
[    0.000616]   8 base 042E800000 mask 7FFF800000 uncachable
[    0.000616]   9 base 042E600000 mask 7FFFE00000 uncachable
[    0.001567] e820: update [mem 0xcb800000-0xffffffff] usable ==> reserved
[    0.015952] ACPI: Local APIC address 0xfee00000
[    0.016318] On node 0 totalpages: 4156197
[    0.016319]   DMA zone: 64 pages used for memmap
[    0.016320]   DMA zone: 21 pages reserved
[    0.016320]   DMA zone: 3996 pages, LIFO batch:0
[    0.016321]   DMA32 zone: 12759 pages used for memmap
[    0.016322]   DMA32 zone: 816521 pages, LIFO batch:63
[    0.016323]   Normal zone: 52120 pages used for memmap
[    0.016323]   Normal zone: 3335680 pages, LIFO batch:63
[    0.028735] ACPI: Local APIC address 0xfee00000
[    0.028756] ACPI: IRQ0 used by override.
[    0.028757] ACPI: IRQ9 used by override.
[    0.032419] pcpu-alloc: s221184 r8192 d28672 u262144 alloc=1*2097152
[    0.032421] pcpu-alloc: [0] 0 1 2 3 4 5 6 7 
[    0.076618] spurious 8259A interrupt: IRQ7.
[    0.276541] PCI: pci_cache_line_size set to 64 bytes
[    0.276541] e820: reserve RAM buffer [mem 0x0009d800-0x0009ffff]
[    0.276541] e820: reserve RAM buffer [mem 0xb6048000-0xb7ffffff]
[    0.276541] e820: reserve RAM buffer [mem 0xb6980000-0xb7ffffff]
[    0.276541] e820: reserve RAM buffer [mem 0xc87c7000-0xcbffffff]
[    0.276541] e820: reserve RAM buffer [mem 0xc889c000-0xcbffffff]
[    0.276541] e820: reserve RAM buffer [mem 0xcb000000-0xcbffffff]
[    0.276541] e820: reserve RAM buffer [mem 0x42e600000-0x42fffffff]
[    0.289800] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
[    0.289963] system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.289983] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
[    0.290029] system 00:03: Plug and Play ACPI device, IDs INT3f0d PNP0c02 (active)
[    0.290131] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.290164] pnp 00:05: Plug and Play ACPI device, IDs PNP0303 PNP030b (active)
[    0.290326] pnp 00:06: [dma 0 disabled]
[    0.290356] pnp 00:06: Plug and Play ACPI device, IDs PNP0501 (active)
[    0.290499] pnp 00:07: [dma 0 disabled]
[    0.290524] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
[    0.290707] pnp 00:08: [dma 0 disabled]
[    0.290778] pnp 00:08: Plug and Play ACPI device, IDs PNP0400 (active)
[    0.290822] system 00:09: Plug and Play ACPI device, IDs PNP0c02 (active)
[    0.291132] system 00:0a: Plug and Play ACPI device, IDs PNP0c02 (active)
[    1.039371] intel_idle: MWAIT substates: 0x42120
[    1.039372] intel_idle: v0.5.1 model 0x3C
[    1.039741] intel_idle: Local APIC timer is reliable in all C-states
[    1.175836]   with arguments:
[    1.175836]     /init
[    1.175837]     2G
[    1.175837]     2G
[    1.175838]   with environment:
[    1.175838]     HOME=/
[    1.175839]     TERM=linux
[    1.175839]     BOOT_IMAGE=/boot/vmlinuz-5.10.0-22-amd64
[    1.175839]     chunk_size=
[    1.286730] libata version 3.00 loaded.
[    1.290260] ahci 0000:00:1f.2: version 3.0
[    2.667574] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    2.781235] sr 2:0:0:0: Attached scsi CD-ROM sr0
[    2.781512] sd 3:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[    4.819213] PM: Image not found (code -22)
[   36.558782] vboxdrv: Found 8 processor cores/threads
[   36.577391] vboxdrv: Successfully loaded version 7.0.8 r156879 (interface 0x00330004)

I guess this problem related to the Nvidia driver, but:

How to solve it?

Thank you.

---
Moderator EDIT (Aki) Mon Jun 12 07:45:43 UTC 2023: this post has been merged in the topic you already opened.

[Aki]

Hello,
Uninstall nvidia proprietary drivers, complete the operating system's upgrade and reinstall nvidia proprietary drivers (if you need them) after the OS's upgrade is complete. Please report the nvidia card model.

[hack3rcon]

Hello,
Uninstall nvidia proprietary drivers, complete the operating system's upgrade and reinstall nvidia proprietary drivers (if you need them) after the OS's upgrade is complete. Please report the nvidia card model.

Hello,
Thank you so much for your reply.
The Nvidia card model is GeForce GT 630. Why shouldn't I need this driver? What is the difference between the default Linux driver and the Nvidia driver?

[Aki]

Hello,

Sorry to bother you asking: have you completed the upgrade from Debian Buster to Debian Bullseye according to instructions from previous messages ?

The Nvidia card model is GeForce GT 630.

From the log you sent, your are using nvidia proprietary kernel drivers v. 390.157 :

Code: Select all

[   12.440204] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  390.157  Wed Oct 12 09:19:07 UTC 2022 (using threaded interrupts)

The version shipped with Debian Bullseye is 470.182.03-1 [1] (that supports your GeForce GT 630 according to nvidia). Therefore, it seems that you failed to upgrade part of the OS and this could be the reason why the screen is blank.

[..] The Nvidia card model is GeForce GT 630. Why shouldn't I need this driver? What is the difference between the default Linux driver and the Nvidia driver?

The kernel driver shipped by default with the kernel for nvidia graphic cards allows users not to depend on the manufacturer for software support. It's already compiled and shipped ready for use. It is less performant, it could miss some functions, but it works for supported graphic cards [2]. In any case, you have to get ready for when the manufacturer will drop support for your card, as it has always done in the past.

If you want to upgrade the proprietary driver, I could be easier to uninstall the older version and reinstall the newer one, anyway.

---
[1] https://packages.debian.org/bullseye/nvidia-driver
[2] https://nouveau.freedesktop.org/

[hack3rcon]

Hello,

Sorry to bother you asking: have you completed the upgrade from Debian Buster to Debian Bullseye according to instructions from previous messages ?

The Nvidia card model is GeForce GT 630.

From the log you sent, your are using nvidia proprietary kernel drivers v. 390.157 :

Code: Select all

[   12.440204] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  390.157  Wed Oct 12 09:19:07 UTC 2022 (using threaded interrupts)

The version shipped with Debian Bullseye is 470.182.03-1 [1] (that supports your GeForce GT 630 according to nvidia). Therefore, it seems that you failed to upgrade part of the OS and this could be the reason why the screen is blank.

[..] The Nvidia card model is GeForce GT 630. Why shouldn't I need this driver? What is the difference between the default Linux driver and the Nvidia driver?

The kernel driver shipped by default with the kernel for nvidia graphic cards allows users not to depend on the manufacturer for software support. It's already compiled and shipped ready for use. It is less performant, it could miss some functions, but it works for supported graphic cards [2]. In any case, you have to get ready for when the manufacturer will drop support for your card, as it has always done in the past.

If you want to upgrade the proprietary driver, I could be easier to uninstall the older version and reinstall the newer one, anyway.

---
[1] https://packages.debian.org/bullseye/nvidia-driver
[2] https://nouveau.freedesktop.org/

Hello,
Thank you again.
I did full-upgrade and removed all Nvidia packages and rebooted my system, but I must use "startx" command to see the Desktop.

[Aki]

I did full-upgrade and removed all Nvidia packages and rebooted my system, but I must use "startx" command to see the Desktop.

Probably it's missing the desktop manager: what is your desktop environment (gnome, kde, ...) ?
It could be useful if you can you send information about your configuration. You can use the following command (inxi package maust be installed):

Code: Select all

inxi -Fxxxza

You can paste the output og the previous command in the next message (include it in code tags).

[hack3rcon]

I did full-upgrade and removed all Nvidia packages and rebooted my system, but I must use "startx" command to see the Desktop.

Probably it's missing the desktop manager: what is your desktop environment (gnome, kde, ...) ?
It could be useful if you can you send information about your configuration. You can use the following command (inxi package maust be installed):

Code: Select all

inxi -Fxxxza

You can paste the output og the previous command in the next message (include it in code tags).

Hello,
Thank you again.
I use MATE Desktop.
The command output is:

Code: Select all

$ sudo inxi -Fxxxza
System:    Kernel: 5.10.0-23-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 
           parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-23-amd64 root=UUID=81f957de-2a93-4b9c-a07e-49f0fda0848b ro quiet 
           enable_mtrr_cleanup mtrr_gran_size= 2G chunk_size= 2G 
           Desktop: MATE 1.24.1 info: mate-panel wm: marco 1.24.1 dm: startx Distro: Debian GNU/Linux 11 (bullseye) 
Machine:   Type: Desktop Mobo: Gigabyte model: P85-D3 v: x.x serial: N/A BIOS: American Megatrends v: F9 date: 08/18/2014 
CPU:       Info: Quad Core model: Intel Core i7-4770 bits: 64 type: MT MCP arch: Haswell family: 6 model-id: 3C (60) 
           stepping: 3 microcode: 28 L1 cache: 256 KiB L2 cache: 8 MiB L3 cache: 7.8 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 54274 
           Speed: 898 MHz min/max: 800/3900 MHz base/boost: 3700/7000 volts: 1.0 V ext-clock: 100 MHz Core speeds (MHz): 
           1: 898 2: 899 3: 898 4: 899 5: 899 6: 898 7: 898 8: 899 
           Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
           Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable 
           Type: mds mitigation: Clear CPU buffers; SMT vulnerable 
           Type: meltdown mitigation: PTI 
           Type: mmio_stale_data status: Unknown: No mitigations 
           Type: retbleed status: Not affected 
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp 
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
           Type: spectre_v2 
           mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling, PBRSB-eIBRS: Not affected 
           Type: srbds mitigation: Microcode 
           Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics vendor: Gigabyte driver: i915 v: kernel 
           bus ID: 00:02.0 chip ID: 8086:0412 class ID: 0300 
           Device-2: NVIDIA GF108 [GeForce GT 630] vendor: Gigabyte driver: nouveau v: kernel bus ID: 01:00.0 
           chip ID: 10de:0f00 class ID: 0300 
           Display: server: X.Org 1.20.11 compositor: marco v: 1.24.1 driver: loaded: modesetting unloaded: fbdev,vesa 
           display ID: :0 screens: 1 
           Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.0x11.2") s-diag: 582mm (22.9") 
           Monitor-1: DVI-I-1 res: 1920x1080 hz: 60 dpi: 102 size: 477x268mm (18.8x10.6") diag: 547mm (21.5") 
           OpenGL: renderer: NVC1 v: 4.3 Mesa 20.3.5 direct render: Yes 
Audio:     Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio driver: snd_hda_intel v: kernel bus ID: 00:03.0 
           chip ID: 8086:0c0c class ID: 0403 
           Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: Gigabyte driver: snd_hda_intel v: kernel 
           bus ID: 00:1b.0 chip ID: 8086:8c20 class ID: 0403 
           Device-3: NVIDIA GF108 High Definition Audio vendor: Gigabyte driver: snd_hda_intel v: kernel bus ID: 01:00.1 
           chip ID: 10de:0bea class ID: 0403 
           Sound Server: ALSA v: k5.10.0-23-amd64 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte driver: r8169 v: kernel 
           port: d000 bus ID: 03:00.0 chip ID: 10ec:8168 class ID: 0200 
           IF: eth0 state: down mac: <filter> 
           Device-2: Realtek RTL8169 PCI Gigabit Ethernet driver: r8169 v: kernel port: c000 bus ID: 05:02.0 
           chip ID: 10ec:8169 class ID: 0200 
           IF: eth1 state: up speed: 1000 Mbps duplex: full mac: <filter> 
Drives:    Local Storage: total: 931.52 GiB used: 646.77 GiB (69.4%) 
           ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST500DM002-1BD142 family: Barracuda 7200.14 (AF) 
           size: 465.76 GiB block size: physical: 4096 B logical: 512 B sata: 3.0 speed: 6.0 Gb/s rotation: 7200 rpm 
           serial: <filter> rev: KC45 temp: 38 C scheme: GPT 
           SMART: yes state: enabled health: PASSED on: 2y 47d 3h cycles: 1918 read: 1.09 TiB written: 1.88 TiB Pre-Fail: 
           attribute: Spin_Retry_Count value: 100 worst: 100 threshold: 97 
           ID-2: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST500DM002-1BD142 family: Barracuda 7200.14 (AF) 
           size: 465.76 GiB block size: physical: 4096 B logical: 512 B sata: 3.0 speed: 6.0 Gb/s rotation: 7200 rpm 
           serial: <filter> rev: KC43 temp: 39 C scheme: MBR 
           SMART: yes state: enabled health: PASSED on: 3y 111d 8h cycles: 2299 read: 283.22 GiB written: 1.35 TiB Pre-Fail: 
           reallocated sector: 100 threshold: 36 attribute: Spin_Retry_Count value: 100 worst: 100 threshold: 97 
Partition: ID-1: / raw size: 84.19 GiB size: 82.69 GiB (98.22%) used: 26.55 GiB (32.1%) fs: ext3 block size: 4096 B 
           dev: /dev/sda2 maj-min: 8:2 
           ID-2: /home raw size: 372.53 GiB size: 366.49 GiB (98.38%) used: 196.57 GiB (53.6%) fs: ext4 block size: 4096 B 
           dev: /dev/sda3 maj-min: 8:3 
Swap:      Kernel: swappiness: 60 (default) cache pressure: 100 (default) 
           ID-1: swap-1 type: partition size: 8.39 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda4 maj-min: 8:4 
Sensors:   System Temperatures: cpu: 29.8 C mobo: 27.8 C gpu: nouveau temp: 41.0 C 
           Fan Speeds (RPM): N/A gpu: nouveau fan: 1950 
Info:      Processes: 274 Uptime: 43m wakeups: 0 Memory: 15.48 GiB used: 1.69 GiB (11.0%) Init: systemd v: 247 runlevel: 5 
           Compilers: gcc: 10.2.1 alt: 10/4.8/4.9/6 Packages: apt: 3541 lib: 2040 Shell: Bash (sudo) v: 5.1.4 
           running in: mate-terminal inxi: 3.3.01 

[Aki]

Hello,
As reported by the previous command ("dm: startx"), there's no "display manager" [1] (a program that launches the desktop graphical environment):

Code: Select all

 Desktop: MATE 1.24.1 info: mate-panel wm: marco 1.24.1 dm: startx Distro: Debian GNU/Linux 11 (bullseye) 

You can install a display manager of your choice (see [1]). You can use, for example, the following command to install a display manager named "LightDM":

Code: Select all

su -l -c "apt install LightDM"

After installation, a restart is required.

[1] https://wiki.debian.org/it/DisplayManager

[hack3rcon]

Hello,
As reported by the previous command ("dm: startx"), there's no "display manager" [1] (a program that launches the desktop graphical environment):

Code: Select all

 Desktop: MATE 1.24.1 info: mate-panel wm: marco 1.24.1 dm: startx Distro: Debian GNU/Linux 11 (bullseye) 

You can install a display manager of your choice (see [1]). You can use, for example, the following command to install a display manager named "LightDM":

Code: Select all

su -l -c "apt install LightDM"

After installation, a restart is required.

[1] https://wiki.debian.org/it/DisplayManager

Hello,
Thank you again.
It must be:

Code: Select all

su -l -c "apt install lightdm"