Atualizando do Debian 12 (Bookworm) para o Debian 13 (Trixie) de forma simples

Fri, 08 May 2026 12:21:31 +0000

Recentemente precisei atualizar uma máquina rodando Debian 12 e decidi registrar o processo em formato de guia para outras pessoas que querem fazer o upgrade de maneira objetiva, com o mínimo possível de intervenção manual.

Importante: esse post não substitui o guia oficial do Debian. A ideia aqui é mostrar um caminho enxuto e funcional — ideal para casos em que você não utiliza repositórios customizados nem pacotes externos sensíveis.

Pré-Requisito: Sistema atualizado

Antes de iniciar o upgrade, atualizei todos os pacotes da minha instalação atual do Bookworm:

sudo apt update
sudo apt upgrade
sudo apt --purge autoremove

Depois disso, reiniciei a máquina:

sudo reboot

Atualizando para o Debian 13

Após o reboot, a única alteração necessária foi atualizar os repositórios APT para apontarem para a nova versão trixie.
Editei manualmente o arquivo /etc/apt/sources.list e troquei todas as ocorrências de bookworm por trixie.

Meu /etc/apt/sources.list ficou assim:

deb http://deb.debian.org/debian trixie main non-free-firmware
deb-src http://deb.debian.org/debian trixie main non-free-firmware

deb http://deb.debian.org/debian-security/ trixie-security main non-free-firmware
deb-src http://deb.debian.org/debian-security/ trixie-security main non-free-firmware

deb http://deb.debian.org/debian trixie-updates main non-free-firmware
deb-src http://deb.debian.org/debian trixie-updates main non-free-firmware

Em seguida, rodei novamente os comandos padrão:

sudo apt update
sudo apt full-upgrade
sudo apt --purge autoremove

E finalizei com mais um reboot:

sudo reboot

Resultado

A máquina voltou normalmente, já rodando Debian 13 (Trixie) — sem necessidade de reinstalações, reinstalação de aplicações ou ajustes adicionais.

Você pode confirmar a nova versão com:

lsb_release -a

Se você utiliza somente os repositórios oficiais do Debian e não possui pacotes externos sensíveis, atualizar do Debian 12 para o 13 pode ser tão simples quanto trocar a palavra bookworm por trixie nos repositórios e executar os comandos clássicos do APT.

Para casos mais complexos e com uso de softwares e repositórios externos, recomendo seguir o passo a passo completo da documentação e validar os repositórios externos individualmente.

Referência:
Upgrades from Debian 12 (bookworm)

Release Notes Debian 13 (Trixie)

Rescuing Legacy Hardware: Installing Linux on Early UEFI Systems (Debian 13 Case Study)

Sat, 31 Jan 2026 03:04:36 +0000

TL;DR

Modern Linux installers increasingly assume fully compliant UEFI firmware. On early-generation UEFI systems (circa 2011–2013), this assumption often breaks. This article documents a real-world case where Debian 13, installed in Legacy (MBR + GRUB i386-pc) mode, proved to be the most reliable solution.

Context: When a Simple Reinstall Fails

A Lenovo QiTian M435E (2012), equipped with a Kingston SV300S3 SSD and early-generation UEFI firmware, suffered an OS corruption after an electrical incident. The expected fix — reinstalling Linux — turned into a multi-distro debugging session.

Several modern distributions completed installation successfully but failed to boot afterward, even when configuration steps appeared correct.

Early UEFI Is Not Modern UEFI

The QiTian M435E provides firmware options labeled "UEFI Only" and "Legacy Only". However, this system uses an early UEFI implementation common in pre-2014 corporate hardware.

Characteristics of this class of firmware include:

Partial or unstable EFI variable (NVRAM) support
Inconsistent handling of GPT + EFI System Partitions
Unreliable interaction with modern GRUB EFI targets

As a result, systems may technically support UEFI while failing to boot reliably with contemporary Linux installers.

Why Several Modern Distros Failed

Ubuntu 24.04 / Linux Mint 22 / Zorin OS 17

These distributions:

Default to GPT partitioning
Assume a functional EFI System Partition
Install GRUB primarily in x86_64-efi mode

On early UEFI systems, this results in:

Missing or ignored boot entries
Firmware failing to locate EFI binaries
Systems reporting "No operating system found"

This behavior is not a bug but a consequence of architectural assumptions.

Why Debian 13 Worked

Debian 13 (Trixie) maintains robust support for legacy boot paths:

Honors MBR (msdos) partition tables when disks are clean
Installs GRUB using the i386-pc target when booted in Legacy mode
Does not require an EFI System Partition in BIOS/Legacy setups
Explicitly asks where GRUB should be installed

This results in a predictable, firmware-compatible boot chain.

Tested Installation Procedure (Legacy Mode)

Prerequisites

debian-13.x-amd64-netinst.iso
Firmware set to Legacy Only
Secure Boot and UEFI disabled

Disk Preparation

Ensure the disk uses MBR, not GPT:

sudo wipefs -a /dev/sda
sudo parted /dev/sda mklabel msdos

Installation

Choose: Guided – use entire disk
Filesystem: ext4
Avoid separate /boot partitions
Confirm GRUB installation to /dev/sda (not /dev/sda1)

Internally, Debian executes:

grub-install --target=i386-pc --boot-directory=/boot /dev/sda

Key Technical Takeaway

Component	Debian 13	Modern Ubuntu-based Distros
Partition table	Respects MBR	Defaults to GPT
GRUB target	i386-pc	x86_64-efi
EFI requirement	Not required	Assumed
Firmware tolerance	High	Low on early UEFI

Conclusion

Legacy and early-UEFI systems are not obsolete — they are underserved. Debian 13 remains one of the few mainstream distributions that still treats non-modern firmware as a first-class scenario rather than an edge case.

For environments with pre-2014 hardware, predictability often matters more than novelty.

Coder Legion - Recent posts tagged debian