alpine/alpine-wiki
1
0
Fork 0
mirror of https://codeberg.org/alpine/alpine-wiki.git synced 2023-08-25 13:53:16 +02:00
Code Issues Projects Releases Wiki Activity

teh bios and uefi status for alpine and links related to

Browse Source 
* migrate the wiki page from outdated alpine site
* fix linked and made a minimal version for the tutorials directory
* complete information at the alpine directory
* fix requirements sections about UBOOT and UEFI/BIOS
This commit is contained in:
mckaygerhard 2023-05-07 23:03:22 -04:00
parent 5c1ea50adb
commit d696c6c06c
6 changed files with 430 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

291
alpine/alpine-boot-uefi-bios.md Normal file
View File

@ -0,0 +1,291 @@
# UEFI and BIOS support on Alpine
UEFI replaces the BIOS firmware interface originally present in all IBM
PC-compatible personal computers, early modern computer's UEFI firmware
implementations provide legacy support for BIOS services.
This document is the most up to date, the oficial wiki page from Alpine
is currently outdated, please check the [Licensing clarifications](#licensing-clarifications)
section of this document for any copyright issue.
## Table of Contents
- [About BIOS and UEFI](#about-bios-and-uefi)
- [The history so far](#the-history-so-far)
- [Alpine UEFI support](#alpine-uefi-support)
- [Minimum Alpine partition scheme](#minimum-alpine-partition-scheme)
- [Notes about the boot flags and boot partition](#notes-about-the-boot-flags-and-boot-partition)
- [Alpine disk layout for UEFI](#alpine-disk-layout-for-uefi)
- [UEFI/GPT minimal layout](#uefigpt-minimal-layout)
- [BIOS/MBR minimal layout](#biosmbr-minimal-layout)
- [BIOS/GPT minimal layout](#biosgpt-minimal-layout)
- [BIOS boot process for newbies](#bios-boot-process-for-newbies)
- [UEFI boot process explained](#uefi-boot-process-explained)
- [UEFI mandatory partition mechanics](#uefi-mandatory-partition-mechanics)
- [What's this infamous "Secure Boot"?](#whats-this-infamous-secure-boot)
- [How to boot unsigned code?](#how-to-boot-unsigned-code)
- [Overall notes and conclusions](#overall-notes-and-conclusions)
- [Licensing clarifications](#licensing-clarifications)
- [See also](#see-also)
## About BIOS and UEFI
In the old days, **BIOS**(for **B**asic **I**nput **O**utput **S**ystem)
was how computers booted from the 1980s onwards. But now in newer
hardware for devices, servers, laptops and desktops computers the
**UEFI**(for **U**nified **E**xtensible **F**irmware **I**nterface) defines a
software interface between an operating system and platform firmware
into the vendor hardware.
## The history so far
All this was driven by a problem in the most extensive and used
architecture: x86 32-bit, inclusivelly a new 2020's Skylake i7-6700k
still has an 80286 embedded in it **because all x86 BIOS strictly only
supports 16-bit 8088-derivative processors**.
Due newer incoming 64-bit incoming processors the older computers boot
process are not more possible. **It started life on Itanium (Intel's first
64-bit processor) systems. Itanium had no support for 32-bit, and
certainly no embedded 80286**, so they had to come up with a different
system.
So then Intel developed the original Extensible Firmware Interface (EFI)
specification. Some of the EFI's practices and data formats mirror those
from M$ Redmon's OS. In 2005, UEFI deprecated EFI 1.10 (the final
release of EFI). The Unified EFI Forum is the industry body that (seems)
"manages" the UEFI specification.
# Alpine UEFI support
Currently are enought for boot most systems, not all the architectures are complete
supported.
The **support for [EFI System Partition](https://en.wikipedia.org/wiki/EFI_system_partition) was
started in the [Alpine 3.7.0 new mayor release](https://alpinelinux.org/posts/Alpine-3.7.0-released.html)**,
preliminary support in that version does not create the [EFI Partition](https://en.wikipedia.org/wiki/EFI_system_partition),
only was support for existing ones or manually created so you can integrate dual boot for Alpine.
Started **in the [Alpine 3.8.0 new mayor release](https://alpinelinux.org/posts/Alpine-3.8.0-released.html)
support in the installer for the GRUB boot loader was added** so now
Linux experimental users can play with combinations of solutions and
proper [UEFI](https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface)
complete installations. Please refer to [UEFI_and_BIOS section of this page](#UEFI_and_BIOS_definitions_and_introduction)
first.
Started in [Alpine 3.15 is able to setup UEFI and Secure Boot](https://wiki.alpinelinux.org/wiki/Release_Notes_for_Alpine_3.15.0#UEFI_Secure_Boot)
only with grub install flavor, syslinux can able to install UEFI but only with few devices.
Some users need to setup non grub to work.
**[EFI System Partition](https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface#EFI_system_partition)
are not the complete overall of the [UEFI](https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface),
it's just the need minimal infrastructure to property boot by and [UEFI modern machine](https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface#Implementation_and_adoption)..**
> **Warning** check at the [UEFI mandatory partition mechanics](#uefi-mandatory-partition-mechanics) section of this document.
## Minimum Alpine partition scheme
Alpine Linux requires a root partition, but on UEFI systems an EFI, a
"System Partition" is also required. So a minimun of 3 partitions will be required.
The **EFI System Partition** will be the `/boot` one, it must contain a bootloader
program in. The current status of that mechanics to boot **in Alpine Linux are still
in development and has good basic support**. See [UEFI mandatory partition mechanics](#uefi-mandatory-partition-mechanics)
and [UEFI/GPT minimal layout](#uefi-gpt-minimal-layout) for details.
## Notes about the boot flags and boot partition
**UEFI booting does not involve any "boot" flag, that's it's a need only
for BIOS booting**. The UEFI booting relies solely on the boot entries in
NVRAM. Parted and its front-ends use a "boot" flag on GPT to indicate
that a partition is an "EFI system partition".
**A BIOS "boot partition for EFI" is only required when using GRUB for BIOS
booting from a GPT disk**. The partition has nothing to do and it must not be
formatted with a file system or mounted.
## Alpine disk layout for UEFI
You will need a disk layout that your system firmware is capable of
booting, you **will need a boot partition and a root partition**. Other
architectures may have different requirements and not all are supported,
please read next sections for details.
If you don't already know what filesystem format you want your boot
partition, choose **ext2**. The **root partition, and any additional
partitions or LVM volume groups, may be in any format that the kernel is
capable of reading**.
#### UEFI/GPT minimal layout
| Mount point | Partition | Partition type Purpose | Recommended minimum size | Formats |
|---------------|-----------|-------------------------------|--------------------------|---------|
| /boot or /efi | /dev/sda1 | GPT UEFI Boot partition | 260 MiB | ext2/3/4 |
| / | /dev/sda2 | Alpine Linux root system OS | 1–32 GiB | btreefs,ext2/3/4,xfs |
| none | /dev/sda3 | Linux swap memory | 1-2Gb | swap |
#### BIOS/MBR minimal layout
| Mount point | Partition | Partition type Purpose | Recommended minimum size | Formats |
|-------------|-----------|--------------------------------|--------------------------|---------|
| /boot | /dev/sda1 | Boot partition **(optional)** | 100 MiB | btreefs,ext2/3/4,xfs |
| / | /dev/sda2 | Alpine Linux root system OS | 1–32 GiB | btreefs,ext2/3/4,xfs |
| none | /dev/sda3 | Linux swap memory | 1-2Gb | swap |
#### BIOS/GPT minimal layout
| Mount point | Partition | Partition type Purpose | Recommended minimum size | Formats |
|-------------|-----------|-----------------------------|--------------------------|---------|
| None | /dev/sda1 | GPT BIOS boot partition | 20 MiB | ext2/ext3 |
| / | /dev/sda2 | Alpine Linux root system OS | 1–32 GiB | btreefs,ext2/3/4,xfs |
| none | /dev/sda3 | Linux swap memory | 1-2Gb | swap |
# BIOS boot process for newbies
BIOS mainly supports two methods of booting - loading approximately 448
bytes of 8088 machine code from the start of a floppy disk, or the same
from the start of a fixed IDE disk.
BIOS can only assume one boot loader occupying the start of hard drive.
So each OS overwrites it with its own boot loader. This is very messy.
There's also the 2 TiB issue with MBR.
In order to make your drive more useful, it's split up into partitions -
chunks of disk space which can be treated as independent drives from
inside your OS. Windows (following on from MS-DOS) only supports one
method for partitioning its boot drive on BIOS systems, which is MBR.
MBR cannot handle disks larger than 2 TiB (2<sup>32</sup> × 512 bytes).
Therefore, it is impossible to use any drive space beyond 2 TiB using
MBR layout. So if you're booting from it and use BIOS, you MUST use
MBR - and you simply can't use any space beyond that if your boot drive
is 2TB or bigger.
Modern motherboards (since approximately 2011 onwards) are using UEFI
natively, but most can emulate BIOS through the CSM (Compatibility
Support Module) to maintain support for BIOS-style booting.
# UEFI boot process explained
Well, let's start with installers. It'll read a UDF or FAT32-formatted
USB drive or DVD, and look for the file /efi/boot/bootx64.efi and run
it. An app, written in the UEFI "OS". It can be anything! Here's classic
text adventure Zork, as a UEFI app.
It's possible to make boot media which is valid for both UEFI and BIOS.
Unfortunately, in a slightly user-unfriendly twist, you (the user) need
to pick the right boot entry. For example, on the wife's PC, a USB stick
gets listed as both "UEFI: Sandisk Cruzer Edge" and "USB: Sandisk Cruzer
Edge". Just... make sure you pick the right entry. It's impossible to
change mode after this point.
It uses a different partitioning system called GPT instead of MBR, and
secondly it creates an extra \~100 meg partition called the "EFI System
Partition" - a FAT32 partition where the boot loader apps get installed
to (no more boot sectors).
Each OS will stick its boot loader somewhere in the ESP, then send a
signal to the firmware to write this new loader's location into the
CMOS. Each entry installed in this manner will get its own listing in
your "boot devices" list on the firmware - so if you installed MACOSX,
you'll have "MACOSX Boot Manager" as an entry next to your DVD drive and
hard drive after you reboot. This is why you don't do the old "unplug
drive A when installing a different OS to drive B" thing, or swap
cables, or anything like that. You should only have one ESP, the one on
drive A.
## UEFI mandatory partition mechanics
Regular UEFI boot has several lists of possible boot entries, stored in
UEFI config variables (normally in NVRAM), and boot order config
variables stored alongside them. Unfortunately, a lot of PC UEFI
implementations have got this wrong and so don't work properly.
The correct way for this to work when booting off local disk is for a
boot variable to point to a vendor-specific bootloader program in
`\EFI\$bootloader.efi` on the EFI System Partition (ESP), a specially
tagged partition (Some OS's formatted as Fat32.. that's are unnecessary
due it's just to able to poor OS's to boot like M$ Redmond OS's). The
current status of that mechanics to boot in Alpine Linux are still in
development and only basic support to existing made are provided.
## What's this infamous "Secure Boot"?
It's a way for your motherboard to prevent tampering of your OS (seems
stupidity of boot-sector viruses??? please!). The UEFI/BIOS provide a
list of certificates to trust that signed the OS kernels, then the firmware
enforces that everything involved with the boot process (not just the boot
loader, but the OS kernel itself, and all your device firmware like your
GPU BIOS) are signed with a trusted key.
It works using cryptographic checksums and signatures. It **stops your
system from booting unsigned code**. You can sign your own, and trust
the certificate you used to do that signing. Or you can get the boot
code signed by Microsoft - every motherboard has a small list of
pre-trusted certificates which almost (always) includes Microsoft's
certificates, which they currently let anyone use for a small fee.
Most of the programs that are expected to run in the UEFI environment
are boot loaders, but others exist too. There are also programs to deal
with firmware updates before operating system startup (like fwupdate and
fwupd), and other utilities may live here too.
Support **for [secure boot are since Alpine 3.15](https://wiki.alpinelinux.org/wiki/Release_Notes_for_Alpine_3.15.0#UEFI_Secure_Boot)
realized by package `secureboot-hook` and `efi-mkkeys`, this means
that you must load a own signed kernel and put a own certificate** to the UEFI/BIOS.
Due the "Unsigned code curse", Alpine linux [EFI System Partition](https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface#EFI_system_partition)
**are not the complete overall of the [UEFI](https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface),
it's just the need minimal infrastructure to property boot** it!
## How to boot unsigned code?
**Alpine users have to first disable Secure Boot to be able to install
Alpine Linux, cos since supported, it not handle their own certificate**
and the methods for doing this vary massively from one system to another,
making this potentially quite difficult for users.
This is due to Microsoft's actions as a Certification Authority (CA) for
Secure Boot. They sign programs/bootloaders on behalf of other trusted
organizations so that their programs will run, but at great cost.. and
there's nothing related to free software but affects to.. There's no
Alpine Linux Certification like are with other enterprise related Linux.
Support **for [secure boot are since Alpine 3.15](https://wiki.alpinelinux.org/wiki/Release_Notes_for_Alpine_3.15.0#UEFI_Secure_Boot)
realized by package `secureboot-hook` and `efi-mkkeys`, this means
that you must load a own signed kernel and put a own certificate** to
the UEFI/BIOS and **not a real direct boot from fresh UEFI/BIOS list.**.
# Overall notes and conclusions
Currently Alpine UEFI and Secure Boot are very basic and enought to work,
but are just implementations and **not official UEFI listed so Secure Boot must be
disabled at first install**.
BIOS computers or **UEFI computers with Compatibility Support BIOS are
the easiest and most reliable way to install**, they do not need the
new EFI partition to boot nor new special files.
## Licensing clarifications
This document were started at oficial Alpine wiki, but was over 22:22, 18 August 2019,
so the wiki licence was pretty simple "are owned by creator" so cannot be redistribute
without the following license:
**CC BY-NC-SA**: the project allows reusers to distribute, remix, adapt, and build upon the material
in any medium or format for noncommercial purposes only, and only so long as attribution is given
to the creators involved. If you remix, adapt, or build upon the material, you must license the modified
material under identical terms, includes the following elements:
* **BY** – Credit must be given to the creator of each content respectivelly, starting at the first contributor.
* **NC** – Only noncommercial uses of the work are permitted, with exceptions if you fill an issue here!
* **SA** – Adaptations must be shared under the same terms, you must obey this terms and do not change it.
Complete license at: https://codeberg.org/alpine/alpine-wiki/src/branch/main#license
Original started at: https://wiki.alpinelinux.org/w/index.php?title=Alpine_and_UEFI&oldid=16188
## See also
* [README.md](README.md)

16
alpine/requirementes.md
View File

@ -114,7 +114,7 @@ Note that bluetooth adapter, while on the same card as your wifi will
have a seperate hardware ID but both will be reconiced always as USB devices. have a seperate hardware ID but both will be reconiced always as USB devices.
Mostly mayor of those are not well suported unless you use kernel 5.10 and up, Mostly mayor of those are not well suported unless you use kernel 5.10 and up,
so the recommendations for recent hybrits devices are Alpine v3.15 and up. so the recommendations for recent hybrits devices are Alpine v3.16 and up.
the only problem are few modules like Broadcom (that some not matter if the only problem are few modules like Broadcom (that some not matter if
are older or newer will require compilation and firmware) and the are older or newer will require compilation and firmware) and the
Realtek Semiconductor only if your device are so so recent. Realtek Semiconductor only if your device are so so recent.
@ -158,20 +158,28 @@ to do the same task as any recent version of same.
## Booting ## Booting
**Means support for kind of BIOS setup of machine, and where can be **Means support for kind of BIOS/UEFI/OEM setup of machine, and where can be
media downloaded will be boot**, please for more info check [Alpine and UEFI](alpine-and-uefi.md)) wiki page media downloaded will be boot**.
| Supported Arch | Supported BIOS | Supported Types | Media Boot Recommended | | Supported Arch | Supported BIOS | Supported Types | Media Boot Recommended |
| -------------- | ---------------------- | --------------- | ---------------------------- | | -------------- | ---------------------- | --------------- | ---------------------------- |
| x86\_64 | Coreboot, Vendor/OEM | BIOS, UEFI | **USB**, CD/DVD (ISO) | | x86\_64 | Coreboot, Vendor/OEM | BIOS, UEFI | **USB**, CD/DVD (ISO) |
| x86 | Coreboot, Vendor/OEM | BIOS, UEFI | **USB**, CD/DVD (ISO) | | x86 | Coreboot, Vendor/OEM | BIOS, UEFI | **USB**, CD/DVD (ISO) |
| ppc64le | Coreboot, Vendor/OEM | BIOS, UEFI | **USB**, CD/DVD (ISO) | | ppc64le | Coreboot, Vendor/OEM | BIOS, UEFI | **USB**, CD/DVD (ISO) |
| armhf | Uboot, Vendor/OEM | BIOS, UEFI | **NET**, MINIROOTFS (TAR.GZ) | | armhf | Uboot, Vendor/OEM | BIOS | **NET**, MINIROOTFS (TAR.GZ) |
| armv7 | Uboot, Vendor/OEM | BIOS, UEFI | **NET**, MINIROOTFS (TAR.GZ) | | armv7 | Uboot, Vendor/OEM | BIOS, UEFI | **NET**, MINIROOTFS (TAR.GZ) |
| aarch64 | ?Coreboot?, Vendor/OEM | BIOS, ?UEFI? | **USB**, CD/DVD (ISO) | | aarch64 | ?Coreboot?, Vendor/OEM | BIOS, ?UEFI? | **USB**, CD/DVD (ISO) |
| mips64 | Vendor/OEM | ? | v3.14.0 end of support | | mips64 | Vendor/OEM | ? | v3.14.0 end of support |
| s390x | Vendor/OEM | BIOS, ?UEFI? | **USB**, CD/DVD | | s390x | Vendor/OEM | BIOS, ?UEFI? | **USB**, CD/DVD |
#### Boot process
The boot process for most common computer are described at
the [alpine-boot-uefi-bios.md](alpine-boot-uefi-bios.md) document.
The Uboot process for most common devices are described at
the [apine-boot-uboot.md](alpine-boot-uboot.md) except for Odroid-C2 devices..
If the computer does not automatically boot from the desired device, one If the computer does not automatically boot from the desired device, one
needs to bring up the boot menu selection for choosing the media to boot needs to bring up the boot menu selection for choosing the media to boot
from. Depending on the computer the menu may be accessed by quickly from. Depending on the computer the menu may be accessed by quickly

121
tutorials/Alpine_and_UEFI.md Normal file
View File

@ -0,0 +1,121 @@
# UEFI and BIOS support on Alpine
UEFI replaces the BIOS firmware interface originally present in all IBM
PC-compatible personal computers, early modern computer's UEFI firmware
implementations provide legacy support for BIOS services.
UBOOT are a boot process for embebed devices and minidevices, pretty
mostly present at the single board computers and some phones.
The complete information is at the [alpine/requirementes.md booting](../alpine/requirementes.md#booting) section.
This document is the most up to date, the oficial wiki page from Alpine
is currently outdated, please check the [Licensing clarifications](#licensing-clarifications)
section of this document for any copyright issue.
## About BIOS and UEFI
In the old days, **BIOS**(for **B**asic **I**nput **O**utput **S**ystem)
was how computers booted from the 1980s onwards. But now in newer
hardware for devices, servers, laptops and desktops computers the
**UEFI**(for **U**nified **E**xtensible **F**irmware **I**nterface) defines a
software interface between an operating system and platform firmware
into the vendor hardware.
> **Note** Consult more at [../alpine/alpine-boot-uefi-bios.md](../alpine/alpine-boot-uefi-bios.md)
# Alpine UEFI support
Currently are enought for boot most systems, not all the architectures are complete
supported. Since 3.16 Alpine is able to setup UEFI only with grub install flavor, syslinux
can able to install UEFI but only with few devices. Some users need to setup non grub to work.
> **Warning** Mayor information is at [alpine/requirementes.md booting](../alpine/requirementes.md#booting) section document.
## Minimum Alpine partition scheme
Alpine Linux requires a root partition, but on UEFI systems an EFI, a
"System Partition" is also required. So a minimun of 3 partitions will be required.
**UEFI booting does not involve any "boot" flag, that's it's a need only
for BIOS booting**.
**A BIOS "boot partition for EFI" is only required when using GRUB for BIOS
booting from a GPT disk**. The partition has nothing to do and it must not be
formatted with a file system or mounted.
#### UEFI/GPT minimal layout
| Mount point | Partition | Partition type Purpose | Recommended minimum size | Formats |
|---------------|-----------|-------------------------------|--------------------------|---------|
| /boot or /efi | /dev/sda1 | GPT UEFI Boot partition | 260 MiB | ext2/3/4 |
| / | /dev/sda2 | Alpine Linux root system OS | 1–32 GiB | btreefs,ext2/3/4,xfs |
| none | /dev/sda3 | Linux swap memory | 1-2Gb | swap |
#### BIOS/MBR minimal layout
| Mount point | Partition | Partition type Purpose | Recommended minimum size | Formats |
|-------------|-----------|--------------------------------|--------------------------|---------|
| /boot | /dev/sda1 | Boot partition **(optional)** | 100 MiB | btreefs,ext2/3/4,xfs |
| / | /dev/sda2 | Alpine Linux root system OS | 1–32 GiB | btreefs,ext2/3/4,xfs |
| none | /dev/sda3 | Linux swap memory | 1-2Gb | swap |
#### BIOS/GPT minimal layout
| Mount point | Partition | Partition type Purpose | Recommended minimum size | Formats |
|-------------|-----------|-----------------------------|--------------------------|---------|
| None | /dev/sda1 | GPT BIOS boot partition | 20 MiB | ext2/ext3 |
| / | /dev/sda2 | Alpine Linux root system OS | 1–32 GiB | btreefs,ext2/3/4,xfs |
| none | /dev/sda3 | Linux swap memory | 1-2Gb | swap |
## Secure Boot Support
Support **for [secure boot are since Alpine 3.15](https://wiki.alpinelinux.org/wiki/Release_Notes_for_Alpine_3.15.0#UEFI_Secure_Boot)
realized by package `secureboot-hook` and `efi-mkkeys`, this means
that you must load a own signed kernel and put a own certificate** to the UEFI/BIOS.
Due the "Unsigned code curse", Alpine linux [EFI System Partition](#uefi-gpt-minimal-layout)
**are not the complete overall of the [Secure Boot](https://en.wikipedia.org/wiki/Unified_Extensible_Firmware_Interface),
it's just the need minimal infrastructure to property boot** it!
Is **recommended to disable Secure Boot. Alpine has no own certificate,
the process only permit to load your own certificate to your UEFI BIOS,
it does not have a certificate** which some other Linux distributions
(mostly enterprise-related) have.
> **Warning** for more information about please check [alpine/alpine-boot-uefi-bios.md Secure Boot](../alpine/alpine-boot-uefi-bios.md#secure-boot) section document.
# Overall notes and conclusions
Currently Alpine UEFI and Secure Boot are very basic and enought to work,
but are just implementations and **not official UEFI listed so Secure Boot must be
disabled at first install**.
BIOS computers or **UEFI computers with Compatibility Support BIOS are
the easiest and most reliable way to install**, they do not need the
new EFI partition to boot nor new special files.
## Licensing clarifications
This document were started at oficial Alpine wiki, but was over 22:22, 18 August 2019,
so the wiki licence was pretty simple "are owned by creator" so cannot be redistribute
without the following license:
**CC BY-NC-SA**: the project allows reusers to distribute, remix, adapt, and build upon the material
in any medium or format for noncommercial purposes only, and only so long as attribution is given
to the creators involved. If you remix, adapt, or build upon the material, you must license the modified
material under identical terms, includes the following elements:
* **BY** – Credit must be given to the creator of each content respectivelly, starting at the first contributor.
* **NC** – Only noncommercial uses of the work are permitted, with exceptions if you fill an issue here!
* **SA** – Adaptations must be shared under the same terms, you must obey this terms and do not change it.
Complete license at: https://codeberg.org/alpine/alpine-wiki/src/branch/main#license
Original started at: https://wiki.alpinelinux.org/w/index.php?title=Alpine_and_UEFI&oldid=16188
## See also
* [README.md](README.md)
* [alpine-newbie-install.md](../../newbie/alpine-newbie-install.md)
* [alpine/alpine-boot-uefi-bios.md](../alpine/alpine-boot-uefi-bios.md)

2
tutorials/alpine-install-from-cd-to-disk-pc-single-boot-only.md
View File

@ -191,6 +191,8 @@ your hard drive as follows:
In a few minutes everything will be ready to use ofering a console when boot new system. In a few minutes everything will be ready to use ofering a console when boot new system.
![](https://venenux.github.io/alpine-espanol/instalar/install-alpine-alpine-setup-3-setup-scripts.png)
#### custom setup boot loader #### custom setup boot loader
If the new local system was configured to run in `diskless` or `data` mode, or if you If the new local system was configured to run in `diskless` or `data` mode, or if you

2
tutorials/alpine-install-from-cd-to-pcengine-apu-single-boot.md
View File

@ -120,6 +120,8 @@ This will start some questions, these are in the following order:
* NTP Options: Use chronythe packet already in the middle. * NTP Options: Use chronythe packet already in the middle.
* Mode: Select `sys` to install the system on disk. * Mode: Select `sys` to install the system on disk.
![](https://venenux.github.io/alpine-espanol/instalar/install-alpine-alpine-setup-3-setup-scripts.png)
## After reboot ## After reboot
1. **Before** rebooting, edit /boot/extlinux.conf. 1. **Before** rebooting, edit /boot/extlinux.conf.

2
tutorials/alpine-install-from-usb-to-disk-pc-single-boot-only.md
View File

@ -198,6 +198,8 @@ your hard drive as follows:
In a few minutes everything will be ready to use ofering a console when boot new system. In a few minutes everything will be ready to use ofering a console when boot new system.
![](https://venenux.github.io/alpine-espanol/instalar/install-alpine-alpine-setup-3-setup-scripts.png)
#### custom setup boot loader #### custom setup boot loader
If the new local system was configured to run in `diskless` or `data` mode, or if you If the new local system was configured to run in `diskless` or `data` mode, or if you