A Linux installation ends, the USB key is removed, and then the M17x does not boot from its disk. The key may have been launched in UEFI while you expected a Legacy boot, or GRUB was installed on the wrong target. Before any writing, check the active mode and identify the disk by its model and serial number.
This procedure aims at a fresh installation of Debian 13 amd64 on a SATA disk dedicated to Linux, empty or backed up and intended to be erased. It uses an MBR table, an ext4 root, and GRUB for BIOS. It does not cover dual-booting, converting an existing disk, LVM, encryption, RAID, or SLI/Optimus. Ubuntu 24.04 is addressed later, in a separate branch dedicated to NVIDIA drivers.
Identify the M17x, the disk, and the GPU
Before starting, plan for a recoverable backup, a complete amd64 live media, power supply, and network access if needed during installation. Note the laptop revision, firmware version, disk state, and the GPU actually installed. Menus vary by revisions, and a graphics card may have been replaced. Check that the live system sees the disk before launching the installer:
uname -m
lsblk -o NAME,PATH,SIZE,MODEL,SERIAL,TYPE,PTTYPE,FSTYPE,MOUNTPOINTS
sudo fdisk -l
lspci -nnk
swapon --show
sudo dmidecode -s system-product-name
sudo dmidecode -s bios-version
uname -m should return x86_64 for Debian amd64. lsblk links devices to models, serial numbers, and partitions. lspci -nnk displays PCI IDs and the loaded driver. swapon --show detects an active swap. dmidecode may miss or provide an inaccurate name: confirm the revision on the hardware or in the firmware.
Note the boot mode of the already installed system and the current SATA setting. Switching from RAID to AHCI may prevent this system from booting. Do not choose a proprietary driver until you have noted the PCI ID of the GPU.
Boot the key in Legacy and check the mode
On the M17x R4 documented by Dell, the BIOS instructions indicate switching from UEFI to Legacy in F2, then selecting the key with F12. This does not guarantee the same menus on other revisions. Read the labels on your machine and do not flash the BIOS to follow this guide.
A key may appear twice in the menu, with a UEFI entry and a USB/Legacy entry. Choose Legacy explicitly, then check the current boot from the live system:
test -d /sys/firmware/efi && printf 'UEFIn' || printf 'BIOS/Legacyn'
The expected result is BIOS/Legacy. The absence of /sys/firmware/efi describes the current boot, not all firmware capabilities. If the command indicates UEFI, restart and select the Legacy entry before installation.
BIOS does not impose MBR. Linux and GRUB can also boot in BIOS on GPT, with a reserved bios_grub partition. For this simple installation on a dedicated disk, we keep MBR (msdos). Do not convert an existing disk to apply this scheme.
Prepare MBR without erasing the wrong disk
Replacing a partition table can make data unrecoverable. Proceed only if the disk is dedicated to Linux, backed up, and explicitly meant to be erased. If you need to keep its content, stop.
Preferably identify the disk by its stable path under /dev/disk/by-id/, then read its target again before any writing:
printf 'Checked full disk path: '
read -r DISK
test -b "$DISK"
readlink -f "$DISK"
lsblk -o NAME,PATH,SIZE,MODEL,SERIAL,TYPE,PTTYPE,FSTYPE,MOUNTPOINTS "$DISK"
sudo parted "$DISK" unit MiB print free
test -b only confirms that it is a block device, not a full disk. In lsblk, check that the target is the parent of type disk, that the model and serial numbers match, and that it is neither the USB key nor a partition. Stop if the target remains ambiguous. No partition of the disk should be mounted or active as swap at the time of writing.
If a table exists, back up its description on another mounted media. This copy does not contain the files from the disk and does not replace a data backup or a recoverable image:
printf 'Backup directory on another mounted media: '
read -r BACKUP_DIR
test -d "$BACKUP_DIR"
findmnt -T "$BACKUP_DIR"
sudo sfdisk --dump "$DISK" > "$BACKUP_DIR/table-before-linux.sfdisk"
test -s "$BACKUP_DIR/table-before-linux.sfdisk"
Verify that findmnt indicates a media different from the target and that the file does not overwrite a previous backup. On a new disk without a table, failure of sfdisk --dump does not prove a malfunction.
The manual partitioning of Debian allows you to review changes before committing. Choose an msdos table, an ext4 root partition starting at 1 MiB and mounted on /. Reject the summary if the installer plans to write to another disk or erase a partition to be kept.
From a complete live session, Parted can also create the table. The mklabel command is immediately destructive. Use this variant only on the dedicated, backed-up, and confirmed disk:
sudo parted "$DISK"
In the interactive prompt, review the target one last time:
unit MiB
print free
mklabel msdos
mkpart primary ext4 1MiB 100%
print
align-check optimal 1
quit
mkpart creates a partition but does not format it as ext4. This variant uses all the space for root, with no dedicated swap partition and no guarantee of hibernation. BIOS and MBR are not synonymous: bios_grub relates to the BIOS alternative on GPT, not an EFI partition.
After creation, review the table with lsblk and parted. If the displayed disk or partition does not match what you expected, do not proceed to formatting.
For disk identification and table creation, consult identify the disk before creating the partition table.
Install Debian and GRUB for BIOS
In the Debian 13 installer, select the confirmed SATA disk and manual partitioning. Review the msdos table, the ext4 root mounted on /, and all operations to apply. You can choose a lightweight desktop, without deducing a measurable performance gain.
Let the installer configure GRUB for BIOS boot on the entire disk, for example, the parent device, never a partition like /dev/sda1. The GRUB target i386-pc designates the x86 BIOS platform. Debian remains on amd64; it is not a 32-bit Linux installation.
After the installation, remove the key and try normal booting. If GRUB needs to be diagnosed from Debian, first check the installed system:
findmnt /
findmnt /boot
test -d /usr/lib/grub/i386-pc
dpkg-query -W grub-pc grub-pc-bin grub2-common
sudo grub-probe --target=device /boot/grub
findmnt / should show the installed root. The absence of a separate mount for /boot is normal if this directory belongs to /. If a check fails, diagnose before any package installation. After rebooting, confirm the target again: the variable DISK of the live system no longer exists.
Only in the installed Debian, with its root and /boot available and the target verified, reinstall the loader if necessary:
sudo grub-install --target=i386-pc "$DISK"
sudo update-grub
test -s /boot/grub/grub.cfg
grub-install writes the boot files and the loader to the BIOS target. update-grub regenerates the menu, without reinstalling the boot sector. Do not add --force and do not run these commands from a live session where the installed system is not properly mounted. In case of failure, check the boot mode before repairing GRUB rather than converting the table or forcing the installation.
Diagnose a black screen and identify the driver
A black screen can come from graphical support, the disk, or GRUB. If the freeze appears during graphical loading, try nomodeset for a one-time boot: temporarily edit the kernel line in the boot entry. The keys vary by media. Do not modify /etc/default/grub to make this parameter permanent. nomodeset disables kernel modesetting; it is used for troubleshooting, does not provide graphical acceleration, and is not a gaming configuration.
Once the session is accessible, note the PCI ID, the active driver, and the kernel messages:
cat /proc/cmdline
lspci -nnk
sudo journalctl -b -k --no-pager
/proc/cmdline confirms the use of nomodeset. lspci -nnk identifies the GPU and its driver; the journal helps to spot DRM or firmware errors. The choice depends on the PCI ID and the maintained branch for this hardware. Nouveau, radeon, or amdgpu may fit depending on the family, but the laptop name alone is not enough to guarantee it.
For NVIDIA, consult the official lists by identifier. A historical branch does not prove either its current maintenance or its compatibility with the installed kernel. Do not use a .run installer, a PPA, Catalyst/fglrx, or --force to bypass an incompatibility.
Separate branch: NVIDIA on Ubuntu 24.04
The following commands apply only to Ubuntu 24.04 amd64, with an identified NVIDIA GPU. They do not apply to Debian. First, list the available drivers and verify that a branch corresponds to the PCI ID:
sudo ubuntu-drivers list
If the repositories offer an appropriate branch and you choose it:
sudo ubuntu-drivers install
After rebooting, check the driver with lspci -nnk. nvidia-smi and the NVIDIA version file are only relevant if the proprietary driver is installed and supported. If no valid branch is offered, stop before proceeding with proprietary installation. Do not make nomodeset permanent without a separate diagnosis.
Check booting without key
Remove the USB key and boot from the internal disk in Legacy. In Debian, check the mode, the root, the table, and the driver:
test -d /sys/firmware/efi && printf 'UEFIn' || printf 'BIOS/Legacyn'
findmnt /
lsblk -o NAME,PATH,SIZE,MODEL,TYPE,PTTYPE,FSTYPE,MOUNTPOINTS
cat /proc/cmdline
lspci -nnk
The expected result is a Legacy boot, a root from the intended disk, a dos table, and a driver corresponding to the observed GPU. If you had used nomodeset, reboot without this parameter and check the display. The absence of this parameter alone does not prove that 3D acceleration is working.
On your revision, also check the external display, brightness, network, suspend and resume, as well as cooling under a reasonable load. No level of compatibility or performance is guaranteed without identifying the GPU and controlling the machine.