Create_boot_multiple_kernel.md #795
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,90 @@ | ||
| # Using Multiple Kernels on SBC with Armbian via SD Cards | ||
|
|
||
| A common and effective way to use multiple kernels on a single-board computer (SBC) running Armbian is to use separate SD cards. This method is especially useful for testing new kernels, different versions of a kernel, or different Linux distributions without risking your primary, stable system. It also simplifies the process by leveraging the standard SBC boot sequence, which typically checks for a bootable SD card first. | ||
|
|
||
| This tutorial will walk you through the process of setting up multiple SD cards with different Armbian kernels. | ||
|
|
||
| --- | ||
|
|
||
| ## Prerequisites | ||
|
|
||
| Before you begin, you'll need a few things: | ||
|
|
||
| - **Your SBC**: A compatible single-board computer (e.g., Orange Pi, Rock Pi, Odroid). | ||
| - **Multiple SD cards**: One for each kernel or system you want to run. Use reliable, high-speed cards from a reputable brand. | ||
| - **A computer** to write the images to the SD cards. | ||
| - **A reliable power supply** for your SBC. | ||
| - **Armbian images**: The specific Armbian images for your board, each with the desired kernel version (`current`, `edge`, or `legacy`). You can download these from the [official Armbian website](https://www.armbian.com/download/). | ||
|
|
||
| --- | ||
|
|
||
| ## Step 1: Prepare the SD Cards 💾 | ||
|
|
||
| Each SD card must be flashed with a different Armbian image. | ||
|
|
||
| 1. **Download the Images** | ||
| Go to the official Armbian download page and find the images for your specific SBC model. | ||
| Example: one with the `current` kernel and another with the `edge` kernel. | ||
|
|
||
| 2. **Flash the SD Cards** | ||
| Use a flashing tool like **BalenaEtcher** or the `dd` command-line utility. | ||
|
|
||
| ### Using BalenaEtcher | ||
| - Insert an SD card into your computer. | ||
| - Open Etcher, select the downloaded Armbian image file. | ||
| - Select your SD card from the list of drives. | ||
| - Click **Flash!** to start the process. | ||
| - Repeat for each SD card and image. | ||
|
|
||
| ### Using `dd` (Linux/macOS users) | ||
| - Unzip the Armbian image file (`.xz`). | ||
| - Identify your SD card's device name with `lsblk` or `diskutil list`. | ||
| - Run: | ||
| ```bash | ||
| sudo dd if=/path/to/armbian-image.img of=/dev/sdX bs=1M status=progress && sync | ||
| ``` | ||
| Replace `/path/to/armbian-image.img` and `/dev/sdX` with the correct path and device name. | ||
| - **Be extremely careful** to select the right device to avoid data loss. | ||
|
Comment on lines
+39
to
+47
There was a problem hiding this comment. Fix dd instructions for macOS compatibility; split Linux/macOS with correct flags and steps The current dd example won’t work on macOS (BSD dd doesn’t support status=progress and typically uses bs=1m; device is /dev/rdiskN). Also, “Unzip” is inaccurate for .xz images—use “decompress”. Propose a precise, safe rewrite. - ### Using `dd` (Linux/macOS users)
- - Unzip the Armbian image file (`.xz`).
- - Identify your SD card's device name with `lsblk` or `diskutil list`.
- - Run:
- ```bash
- sudo dd if=/path/to/armbian-image.img of=/dev/sdX bs=1M status=progress && sync
- ```
- Replace `/path/to/armbian-image.img` and `/dev/sdX` with the correct path and device name.
- - **Be extremely careful** to select the right device to avoid data loss.
+ ### Using `dd` (advanced)
+ - Decompress the image first if using `dd` (Etcher can flash `.xz` directly):
+ ```bash
+ unxz /path/to/armbian-image.img.xz
+ ```
+ - Identify your SD card device:
+ - Linux: `lsblk` (device looks like `/dev/sdX` or `/dev/mmcblkX`)
+ - macOS: `diskutil list` (device looks like `/dev/diskN` and raw `/dev/rdiskN`)
+ - Linux (GNU dd):
+ ```bash
+ sudo dd if=/path/to/armbian-image.img of=/dev/sdX bs=4M conv=fsync status=progress
+ ```
+ - macOS (BSD dd):
+ ```bash
+ diskutil unmountDisk /dev/diskN
+ sudo dd if=/path/to/armbian-image.img of=/dev/rdiskN bs=1m ; sync
+ # Tip: press Ctrl+T to see progress on macOS, or install coreutils and use `gdd ... status=progress`
+ ```
+ Replace `/path/to/armbian-image.img`, `/dev/sdX`, `/dev/diskN`, and `/dev/rdiskN` with your actual paths/devices.
+ - Double-check the device path to avoid data loss.🧰 Tools🪛 LanguageTool[style] ~47-~47: As an alternative to the over-used intensifier ‘extremely’, consider replacing this phrase. (EN_WEAK_ADJECTIVE) 🪛 markdownlint-cli2 (0.17.2)39-39: Headings should be surrounded by blank lines (MD022, blanks-around-headings) 43-43: Fenced code blocks should be surrounded by blank lines (MD031, blanks-around-fences) 45-45: Fenced code blocks should be surrounded by blank lines (MD031, blanks-around-fences) 🤖 Prompt for AI AgentsThere was a problem hiding this comment. @leggewie Thank you for confirming! The suggested changes will help make the dd instructions much more accurate and usable for both Linux and macOS users. The split approach with platform-specific commands, proper device naming conventions, and the correction about decompressing .xz files (rather than "unzipping") will definitely improve the documentation quality. /_________\ If you found this review helpful, would you consider giving us a shout-out on X? Thank you for using CodeRabbit! |
||
|
|
||
| --- | ||
|
|
||
| ## Step 2: Initial Boot and Configuration ⚙️ | ||
|
|
||
| After flashing, each SD card is a self-contained, bootable system. | ||
|
|
||
| 1. **Insert and Boot** | ||
| Insert one SD card into your SBC and connect power. The SBC’s bootloader (usually U-Boot) will detect and boot from it. | ||
|
|
||
| 2. **Initial Setup** | ||
| On first boot, Armbian will: | ||
| - Resize the filesystem | ||
| - Prompt for a root password | ||
| - Prompt to create a new user | ||
|
|
||
| Complete these steps for each SD card. | ||
|
|
||
| 3. **Shut Down and Swap** | ||
| - Power down the SBC. | ||
| - Remove the first SD card. | ||
| - Insert the second SD card. | ||
| - Repeat the boot and setup process. | ||
|
|
||
| --- | ||
|
|
||
| ## Step 3: Managing and Using Different Kernels 🧑💻 | ||
|
|
||
| Now you have multiple independent systems on separate SD cards. | ||
|
|
||
| - **Swapping SD Cards** | ||
| To switch kernels, power down, swap SD cards, and power back up. The bootloader handles everything automatically. | ||
|
|
||
| - **Testing and Development** | ||
| - Use one SD card for a stable, “production” kernel. | ||
| - Use another for experimental or development kernels. | ||
| - If something fails, swap back to your stable card instantly. | ||
|
|
||
| - **Kernel Version Management** | ||
| While Armbian’s `armbian-config` tool allows kernel management inside a single installation, using separate SD cards gives **full isolation**. | ||
| This prevents conflicts between kernel versions and ensures a clean test environment. | ||
|
|
||
| --- | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛠️ Refactor suggestion
Fix list rendering: de-indent and use standard Markdown bullets instead of a 4‑space indented "•".
As written, each line starts with 4 spaces and the "•" glyph, which most Markdown renderers interpret as a code block, not a list. This will render poorly (monospace block), break wrapping, and impair navigation. Use "-" (or "*") without the 4-space indent, and keep one item per line.
Apply this pattern across lines 10–105 (sample shown for the first few items):
Optionally, convert the trailing “in #NNNN” to proper links (see separate comment).
📝 Committable suggestion
🤖 Prompt for AI Agents