VMware ESXi and vSphere Cluster Management
Configure Default Boot Mode in Raspbian
Learn how to use sudo raspi-config to start a Raspberry Pi at a console, graphical desktop, or Scratch, and how to apply and troubleshoot the change.
Boot options determine the environment reached automatically after the operating system starts. On a historical Raspbian release, raspi-config can select a text-console login, the graphical desktop, or Scratch as the initial destination.
This setting changes the default startup experience. It does not replace the operating system, install software, change firmware boot order, or select a different boot device.
Default behavior in the referenced Raspbian release
The default behavior is startup to a text-console login. A console is a local text terminal, and a CLI, or command-line interface, is the text-based environment in which commands are entered at a shell.
Console startup does not launch a graphical session automatically. You must enter a username and password at the login prompt before using the shell.
Open raspi-config
raspi-config is Raspberry Pi's menu-driven system configuration utility. It changes system settings that require administrative privileges, so launch it with sudo:
sudo raspi-configRun the command in a local terminal or in an existing console session. sudo grants the command temporary administrative privileges. Enter your password if prompted.
Navigate the text interface
- Use the Up and Down arrow keys to move through menu entries.
- Use Left and Right, or Tab, to move between menus, buttons, and controls when the screen offers more than one area.
- Press Enter to open a highlighted item or activate a button.
- Follow the on-screen prompts for confirmation, Finish, or Cancel.
The interface is keyboard-based, so the mouse might not work as expected. If focus is on the wrong control, press Tab until the required button or field is highlighted.
Select the boot destination
In the historical Raspbian interface, locate the setting commonly described as boot to desktop/Scratch. Open it, choose the required destination, and confirm the selection before leaving the utility.
- Start
raspi-configwith administrative privileges. - Use the arrow keys to highlight the boot-to-desktop/Scratch setting.
- Press Enter to open the available modes.
- Select Console, Desktop, or Scratch.
- Accept or confirm the choice.
- Choose Finish only after the selection has been saved or accepted.
The exact wording may vary slightly, but the important action is to select the startup environment rather than a different system configuration category.
Historical Raspbian boot choices
Console mode
With Console selected, the Raspberry Pi starts at a text login prompt. After logging in, you can enter shell commands, run scripts, configure services, or administer the device.
This mode is useful when you do not need a graphical interface. It can reduce resource use and is convenient for command-line-focused systems. It is also a suitable local default for users who normally administer a Raspberry Pi remotely, although remote access itself is a separate configuration topic.
Console mode is not the same as an automatic graphical login. A login is required before the shell is available.
Desktop mode
With Desktop selected, the system starts the graphical desktop environment. A desktop environment provides windows, menus, a pointer, and graphical applications. In the historical setup, the graphical session starts under the default pi account.
This is appropriate for beginners and for users who want to open graphical tools immediately. It is different from manually logging in at a console and then starting a graphical session: automatic graphical login takes the user directly into the desktop at startup, while a console login first displays a text prompt and waits for credentials.
Scratch mode
Scratch is a visual programming environment in which programs are assembled from graphical blocks. It is commonly used to create interactive projects such as games, animations, and simple simulations.
In the historical Raspbian configuration, selecting Scratch starts the Raspberry Pi directly in the Scratch environment. This can be useful for a classroom workstation where learners should begin programming with minimal setup.
Apply the change by restarting
The selected boot behavior takes effect after the Raspberry Pi restarts. Some versions of raspi-config offer to reboot when you finish; accept that prompt if you are ready to restart.
If the utility does not reboot automatically, exit it and restart manually:
sudo rebootSave open work before running the command. After the next boot, verify the result:
- Console: You should see a text login prompt.
- Desktop: You should reach the graphical session, possibly through the configured login behavior.
- Scratch: You should enter the Scratch workspace directly when that historical option and its required software are available.
Historical and newer raspi-config terminology
Do not assume that a current menu must contain the historical boot-to-desktop/Scratch entry. The installed raspi-config version, operating system release, desktop components, and installed applications determine what is offered.
Practical examples
Command-line-focused Raspberry Pi
A user who runs scripts, practices shell commands, or administers the device locally selects Console. After rebooting, the device stops at a text login instead of opening the desktop.
Beginner using graphical applications
A new user selects Desktop to reach the graphical workspace immediately. This avoids requiring a console login before using graphical applications.
Classroom Scratch workstation
An educator with the historical Raspbian setup selects Scratch on a dedicated device. Pupils can begin block-based programming as soon as the device starts.
Restoring a preferred startup screen
If the wrong mode was selected, run sudo raspi-config again, choose the desired destination, confirm it, and restart the Raspberry Pi.
Troubleshooting
The boot-to-desktop/Scratch entry is missing
A newer Raspberry Pi OS release may have renamed the setting. Check System Options and the Boot or Boot/Auto Login area. The system may also be using a minimal image, may not have a desktop installed, or may not include Scratch.
The previous mode still appears
The choice might not have been confirmed, or the Raspberry Pi might not have restarted. Run raspi-config again, verify and save the desired selection, and then run sudo reboot if necessary. If the result still differs, a display manager or separate login configuration may be overriding the expected behavior.
A text login appears instead of the graphical desktop
First check whether Console remains selected. Then verify that a desktop environment is installed. If both are true, the issue may be a graphical startup failure rather than a boot-mode selection problem.
Scratch does not launch
The current operating system may not provide the historical Scratch boot option, Scratch may be missing, or the installed Scratch version may use a different startup arrangement. Select a desktop destination and launch the installed Scratch application manually, or use instructions appropriate to the installed operating system version.
Navigation or exiting does not work
Use the arrow keys to move through entries, press Tab to switch controls, and press Enter to activate a highlighted choice. Follow the on-screen instructions for Finish or Cancel; the utility is text-based and may not respond to mouse clicks as expected.
Key points
- Boot-mode configuration controls the first user environment shown after the operating system starts.
- The historical Raspbian default is a console login, not an automatically launched graphical session.
- Use
sudo raspi-configto select Console, Desktop, or Scratch when those historical choices are available. - Confirm the selection and reboot before judging whether the change worked.
- Newer Raspberry Pi OS releases commonly place related controls under System Options and Boot/Auto Login, with release-dependent choices.
For this topic, see Boot Options.