Leah Rowe
parent
cf6a54bca2
commit
36559120eb
|
|
@ -16,12 +16,12 @@ system](docs/maintain/)
|
|||
for [compiling coreboot ROM images](docs/build/), that are [easy to
|
||||
install](docs/install/) for non-technical
|
||||
users. The emphasis is placed upon ease of use, and optional [security
|
||||
features](docs/gnulinux/grub_hardening.md).
|
||||
features](docs/linux/grub_hardening.md).
|
||||
|
||||
Users take this automation for granted today, but Libreboot was the first such
|
||||
project to implement this. It, like Canoeboot, is
|
||||
a *[coreboot distro](docs/maintain/)* in the
|
||||
same way that *Debian* is a GNU+Linux distro. Similar projects now exist, today,
|
||||
same way that *Debian* is a Linux distro. Similar projects now exist, today,
|
||||
inspired by Libreboot's example. Coreboot is notoriously difficult to configure and install
|
||||
for most non-technical users, but Libreboot and Canoeboot make it easier.
|
||||
|
||||
|
|
|
|||
|
|
@ -26,8 +26,8 @@ On x86 platforms, Canoeboot provides the choice of GRUB and/or
|
|||
SeaBIOS payload. GRUB can technically boot BSD kernels, but the code is
|
||||
poorly maintained and unreliable for this use-case scenario; on BIOS systems,
|
||||
GRUB can chainload BSD bootloaders, but on bare metal (as coreboot payload),
|
||||
GRUB can only chainload other coreboot payloads or boot GNU+Linux/BSD kernels
|
||||
directly (but direct booting is only really reliable for GNU+Linux, in GRUB).
|
||||
GRUB can only chainload other coreboot payloads or boot Linux/BSD kernels
|
||||
directly (but direct booting is only really reliable for Linux, in GRUB).
|
||||
|
||||
It is recommended that you boot in text mode, with SeaBIOS. You can literally
|
||||
just follow the official installation guides for your BSD system, whether it
|
||||
|
|
@ -91,7 +91,7 @@ boot in text mode, you can't set VESA modes from BSD. However, you're in luck:
|
|||
At least OpenBSD and FreeBSD (possibly others) all have excellent KMS
|
||||
support nowadays; short for `Kernel Mode Setting`. This avoids the inefficiency
|
||||
of BIOS/UEFI methods, by having the kernel set modes directly. It is based on
|
||||
KMS drivers that the BSD projects ported over from the GNU+Linux kernel. With this,
|
||||
KMS drivers that the BSD projects ported over from the Linux kernel. With this,
|
||||
you can use X11/Wayland in FreeBSD (and just X11 in OpenBSD, for now).
|
||||
|
||||
For example: on FreeBSD, you can install `graphics/drm-kmod` as a package
|
||||
|
|
@ -117,7 +117,7 @@ ALWAYS READ THE MANUAL
|
|||
----------------------
|
||||
|
||||
All of the BSDs have *excellent* documentation; it's one of the defining
|
||||
characteristics, versus typical GNU+Linux distros.
|
||||
characteristics, versus typical Linux distros.
|
||||
|
||||
Aside from this quirk in coreboot, regarding *BIOS* video modes, the BSDs
|
||||
otherwise work in exactly the same way as you would expect, and you can
|
||||
|
|
@ -164,7 +164,7 @@ The reason to use KMS is because it's more efficient. The INT10H service can
|
|||
only be called in Real Mode or Virtual 8086 mode; v8086 is unavailable in
|
||||
long mode (x86\_64) and switching into Real Mode just to set VGA modes is
|
||||
extremely expensive computationally speaking. This is why modern kernels
|
||||
(GNU+Linux and BSD one) do mode setting themselves.
|
||||
(Linux and BSD kernels) do mode setting themselves.
|
||||
|
||||
You can learn more about INT10H text/VGA modes here:
|
||||
|
||||
|
|
|
|||
|
|
@ -100,7 +100,7 @@ First, install build dependencies
|
|||
Check `config/dependencies/` for list of supported distros.
|
||||
|
||||
Canoeboot includes a script that automatically installs build dependencies
|
||||
according to the selected GNU+Linux distro.
|
||||
according to the selected Linux distro.
|
||||
|
||||
For example:
|
||||
|
||||
|
|
@ -127,7 +127,7 @@ use the dedicated configuration file:
|
|||
|
||||
./mk dependencies ubuntu2004
|
||||
|
||||
Technically, any GNU+Linux distribution can be used to build canoeboot.
|
||||
Technically, any Linux distribution can be used to build canoeboot.
|
||||
However, you will have to write your own script for installing build
|
||||
dependencies.
|
||||
|
||||
|
|
|
|||
|
|
@ -8,8 +8,8 @@ documentation, but there are aspects of Canoeboot that deserve special
|
|||
treatment. Canoeboot provides the option to boot GRUB directly, running on
|
||||
bare metal (instead of using BIOS or UEFI services).
|
||||
|
||||
[The GNU+Linux section](../gnulinux/) also has canoeboot-specific guides for
|
||||
dealing with GNU+Linux distributions when using GRUB directly, in this
|
||||
[The Linux section](../linux/) also has canoeboot-specific guides for
|
||||
dealing with Linux distributions when using GRUB directly, in this
|
||||
setup. [A similar section exists for BSD operating systems](../bsd/)
|
||||
|
||||
GRUB keyboard layouts
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ Documentation related to operating systems
|
|||
============================
|
||||
|
||||
- [How to install BSD operating systems](bsd/)
|
||||
- [How to install GNU+Linux](gnulinux/)
|
||||
- [How to install Linux](linux/)
|
||||
|
||||
Information for developers
|
||||
==========================
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ article titled [What is Canoeboot?](../about.md).
|
|||
============================
|
||||
|
||||
- [Як встановити BSD на x86 хостову систему](bsd/)
|
||||
- [Керівництва GNU+Linux](gnulinux/)
|
||||
- [Керівництва Linux](linux/)
|
||||
|
||||
Інформація для розробників
|
||||
==========================
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ article titled [What is Canoeboot?](../about.md).
|
|||
============================
|
||||
|
||||
- [如何在 x86 机器上安装 BSD](bsd/)
|
||||
- [Linux 指南](gnulinux/)
|
||||
- [Linux 指南](linux/)
|
||||
|
||||
开发者信息
|
||||
==========================
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ x-toc-enable: true
|
|||
...
|
||||
|
||||
This is similar to Gigabyte GA-G41M-ES2L but uses an Intel NIC rather than
|
||||
Realtek. Some problems with GNU+Linux on this NIC, on this board, with Canoeboot,
|
||||
Realtek. Some problems with Linux on this NIC, on this board, with Canoeboot,
|
||||
were observed; see (NOTE: Libreboot issue tracker, not Canoeboot):
|
||||
|
||||
<https://notabug.org/libreboot/lbmk/issues/125>
|
||||
|
|
@ -14,7 +14,7 @@ That page (on notabug) has some notes about workarounds. It links to this:
|
|||
<https://superuser.com/questions/1104537/how-to-repair-the-checksum-of-the-non-volatile-memory-nvm-of-intel-ethernet-co/1106641#1106641>
|
||||
|
||||
This page has some guidance on how to either correct the checksum (in GbE
|
||||
config) or skip checksum validation in GNU+Linux, to get the onboard NIC working.
|
||||
config) or skip checksum validation in Linux, to get the onboard NIC working.
|
||||
Although it's talking about different hardware, the steps should be the same.
|
||||
|
||||
TODO: factory BIOS on this board works fine with the onboard NIC. study what
|
||||
|
|
|
|||
|
|
@ -69,7 +69,7 @@ to flash firmware internally. To back up stock firmware you can run:
|
|||
Keep the resulting `depthcharge.rom` file safe and properly backed up on
|
||||
another device.
|
||||
|
||||
If you can already boot a conventional GNU+Linux distro on your Chromebook,
|
||||
If you can already boot a conventional Linux distro on your Chromebook,
|
||||
you may be able to use `flashrom -p linux_mtd` on that system instead.
|
||||
|
||||
Check external flashability
|
||||
|
|
@ -154,7 +154,7 @@ To flash the entire ROM image internally, run within ChromeOS:
|
|||
sudo flashrom -p host -w canoeboot.rom
|
||||
sudo flashrom -p host -v canoeboot.rom
|
||||
|
||||
If you can already boot a conventional GNU+Linux distro on your Chromebook,
|
||||
If you can already boot a conventional Linux distro on your Chromebook,
|
||||
you may be able to use `flashrom -p linux_mtd` on that system instead.
|
||||
|
||||
Install an operating system (experimental research)
|
||||
|
|
|
|||
|
|
@ -142,7 +142,7 @@ Here is an image of the flash chip:\
|
|||
|
||||
|
||||
Internal flashing is possible. Boot with the proprietary BIOS and
|
||||
GNU+Linux. There are 2 flash chips (one is backup).
|
||||
Linux. There are 2 flash chips (one is backup).
|
||||
|
||||
Flash the first chip:
|
||||
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ Before actually reading the installation guides, please ensure that your
|
|||
system is fully supported by Canoeboot. More information about the Canoeboot
|
||||
build system can be found in the [cbmk maintenance manual](../maintain/).
|
||||
|
||||
With x86 machines, you can use the SeaBIOS or GNU GRUB payloads. On ARM
|
||||
With x86 machines, you can use the SeaBIOS or GRUB payloads. On ARM
|
||||
systems, you can use the U-Boot payload (coreboot still initialises hardware).
|
||||
|
||||
Canoeboot currently supports the following systems:
|
||||
|
|
@ -166,7 +166,7 @@ flashing instructions. Internal flashing is when you flash the target machine
|
|||
from the target machine, inside an operating system running on it.
|
||||
|
||||
Some boards require special steps, even if Canoeboot is already running,
|
||||
for example if you [locked down the flash](../gnulinux/grub_hardening.md).
|
||||
for example if you [locked down the flash](../linux/grub_hardening.md).
|
||||
|
||||
Therefore, before following generic guides, make sure to check first whether
|
||||
your board has special instructions, otherwise use the generic guide at the
|
||||
|
|
@ -200,7 +200,7 @@ an Intel PHY module and the onboard NIC is usable).
|
|||
Install via host CPU (internal flashing)
|
||||
========================================
|
||||
|
||||
See: [GRUB hardening / Secure canoeBoot](../gnulinux/grub_hardening.md)
|
||||
See: [GRUB hardening / Secure canoeBoot](../linux/grub_hardening.md)
|
||||
|
||||
If you already did this, it's possible that you may no longer be able to
|
||||
flash internally. If that is the case, you must [flash externally](spi.md).
|
||||
|
|
@ -426,7 +426,7 @@ Install via host CPU (internal flashing)
|
|||
NOTE: This mainly applies to the x86 machines.
|
||||
|
||||
Please check other sections listed above, to see if there is anything
|
||||
pertaining to your mainboard. Internal flashing means that you boot GNU+Linux or
|
||||
pertaining to your mainboard. Internal flashing means that you boot Linux or
|
||||
BSD on the target machine, and run `flashprog` there, flashing the machine
|
||||
directly.
|
||||
|
||||
|
|
|
|||
|
|
@ -29,7 +29,7 @@ Flashing instructions can be found at
|
|||
[../install/](../install/) - note that external
|
||||
flashing is required (e.g. RPi), if the proprietary (ASUS) firmware is
|
||||
currently installed. If you already have Canoeboot or coreboot, by default
|
||||
it is possible to re-flash using software running in GNU+Linux on the kcma-d8,
|
||||
it is possible to re-flash using software running in Linux on the kcma-d8,
|
||||
without using external hardware.
|
||||
|
||||
If you currently have the ASUS firmware, please ignore the above link and
|
||||
|
|
@ -121,8 +121,8 @@ Flash chips {#flashchips}
|
|||
2MiB flash chips are included by default, on these boards. It's on a
|
||||
P-DIP 8 slot (SPI chip). The flash chip can be upgraded to higher sizes:
|
||||
4MiB, 8MiB or 16MiB. With at least 8MiB, you could feasibly fit a
|
||||
compressed linux+initramfs image (BusyBox+GNU+Linux system) into CBFS and
|
||||
boot that, loading it into memory (and nowadays there is GNU+LinuxBoot, for which
|
||||
compressed linux+initramfs image (BusyBox+Linux system) into CBFS and
|
||||
boot that, loading it into memory (and nowadays there is LinuxBoot, for which
|
||||
we would recommend a 16MiB boot flash)
|
||||
|
||||
*DO NOT hot-swap the chip with your bare hands. Use a P-DIP 8 chip
|
||||
|
|
@ -140,7 +140,7 @@ framebuffer display (if it has KMS - kernel mode setting).
|
|||
|
||||
NOTE: This section relates to the onboard ASpeed GPU. You *can* use an add-on
|
||||
PCI-E GPU in one of the available slots on the mainboard. Nvidia GTX 780 cards
|
||||
are what Canoeboot recommends; it has excellent support in Nouveau (free GNU+Linux
|
||||
are what Canoeboot recommends; it has excellent support in Nouveau (free Linux
|
||||
kernel / mesa driver for Nvidia cards) and generally works well; however, the
|
||||
performance won't be as high in Nouveau, compared to the non-free Nvidia driver
|
||||
because the Nouveau driver can't increase the GPU clock (it doesn't know how,
|
||||
|
|
@ -173,7 +173,7 @@ considerations:
|
|||
NOTE: SeaBIOS can load PCI-E option ROMs, and by default it will do so in
|
||||
Canoeboot, so you could use it. However, you could *also* simply
|
||||
install 16MiB NOR flash with linuxboot payload in it, and use linuxboot
|
||||
which has the GNU+Linux kernel, which can use SAS drives without needing that
|
||||
which has the Linux kernel, which can use SAS drives without needing that
|
||||
option ROM; then it can kexec another linux kernel, which in turn also can
|
||||
can use those drives. Or just put a standard linux kernel and initramfs
|
||||
in cbfs and chainload that from GRUB, with the right parameters.
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ x-toc-enable: true
|
|||
...
|
||||
|
||||
All of the Dell Latitude models can be flashed internally, which means that
|
||||
you do not need to disassemble them. You can do it from GNU+Linux or BSD, using
|
||||
you do not need to disassemble them. You can do it from Linux or BSD, using
|
||||
the instructions on this page.
|
||||
|
||||
Disable security before flashing
|
||||
|
|
@ -16,7 +16,7 @@ flashing.
|
|||
|
||||
Please also disable SecureBoot, if you're using a UEFI-based mainboard.
|
||||
Note that Canoeboot does not currently implement UEFI on x86 platforms, but
|
||||
you can set up [Secure canoeBoot](../gnulinux/grub_hardening.md) after flashing.
|
||||
you can set up [Secure canoeBoot](../linux/grub_hardening.md) after flashing.
|
||||
|
||||
MAC address
|
||||
===========
|
||||
|
|
@ -46,12 +46,12 @@ require binary blobs which are not allowed in Canoeboot.
|
|||
Internal flashing
|
||||
=================
|
||||
|
||||
You can simply boot GNU+Linux or BSD, on the Dell Latitude you wish to flash,
|
||||
You can simply boot Linux or BSD, on the Dell Latitude you wish to flash,
|
||||
and run `flashprog` from there, for Canoeboot installation. Certain other steps
|
||||
are also required, documented in the steps below:
|
||||
|
||||
You can flash Canoeboot directly from the vendor (Dell) BIOS, without taking
|
||||
the machine apart. It can be done entirely from GNU+Linux or BSD.
|
||||
the machine apart. It can be done entirely from Linux or BSD.
|
||||
|
||||
**NOTE (15 October 2023): The util is now called `dell-flash-unlock`, but it
|
||||
was previously called `e6400-flash-unlock`. Links have been updated.**
|
||||
|
|
|
|||
|
|
@ -129,10 +129,10 @@ motherboard](https://www.ifixit.com/Guide/MacBook+Core+2+Duo+PRAM+Battery+Replac
|
|||
Refer to the following guide:\
|
||||
[Externally rewrite 25xx NOR flash via SPI protocol](../install/spi.md)
|
||||
|
||||
OSes using GNU+Linux on Apple EFI firmware
|
||||
OSes using Linux on Apple EFI firmware
|
||||
======================================
|
||||
|
||||
You have 2 choices for booting up OSes using GNU+Linux as their kernel
|
||||
You have 2 choices for booting up OSes using Linux as their kernel
|
||||
on the MacBook:
|
||||
|
||||
* Boot via USB ;
|
||||
|
|
@ -297,7 +297,7 @@ to the file /etc/vconsole.conf and then restart the computer.
|
|||
Make touchpad more responsive
|
||||
-----------------------------
|
||||
|
||||
GNU+Linux kernels of version 3.15 or lower might make the touchpad
|
||||
Linux kernels of version 3.15 or lower might make the touchpad
|
||||
extremely sluggish. A user reported that they could get better
|
||||
response from the touchpad with the following in their xorg.conf:
|
||||
|
||||
|
|
|
|||
|
|
@ -113,7 +113,7 @@ does not modify or manipulate these in any way.
|
|||
The final word in the NVM section is the *checksum*; all words
|
||||
must add up, truncated, to the value `0xBABA`. The hardware
|
||||
itself does not calculate or validate this, and will in
|
||||
fact work nicely, but software such as GNU+Linux will check
|
||||
fact work nicely, but software such as Linux will check
|
||||
that this is correct. If the checksum is invalid, your
|
||||
kernel will refuse to make use of the NIC.
|
||||
|
||||
|
|
@ -315,7 +315,7 @@ cbmk repository. A makefile is included there, for you to build an
|
|||
executable.
|
||||
|
||||
The nvmutil programs will work just fine, on any modern BSD Unix operating
|
||||
system, or unix-like system such as GNU+Linux.
|
||||
system, or unix-like system such as Linux.
|
||||
|
||||
You must be sure to have toolchains installed, for
|
||||
building; a normal libc, C compiler and linker should be enough.
|
||||
|
|
@ -560,6 +560,6 @@ used. Also, the `setmac` command will only operate on
|
|||
parts that already have a valid checksum, so you could
|
||||
run `brick` before running `setmac` (or run it afterwards).
|
||||
|
||||
The GNU+Linux kernel's `e1000` driver will refuse to initialise
|
||||
The Linux kernel's `e1000` driver will refuse to initialise
|
||||
Intel gigabit NICs that don't have a valid checksum. This
|
||||
is software-defined, and not enforced by the hardware.
|
||||
|
|
|
|||
|
|
@ -322,4 +322,4 @@ You should see something like this:
|
|||
|
||||
 
|
||||
|
||||
Now [install GNU+Linux](../gnulinux/).
|
||||
Now [install Linux](../linux/).
|
||||
|
|
|
|||
|
|
@ -36,7 +36,7 @@ Canoeboot is running.
|
|||
|
||||
*Internal* flashing means that the host CPU on your system can re-program the
|
||||
SPI flash, using an on-board SPI programmer (which all boards have). You do this
|
||||
from GNU+Linux, with flashprog.
|
||||
from Linux, with flashprog.
|
||||
|
||||
*This* guide that you're reading now is for using an *external* programmer. It
|
||||
is called *external* because it's not the *internal* one on your mainboard.
|
||||
|
|
@ -354,7 +354,7 @@ Rasberry Pi (RPi)
|
|||
SSH into your Raspberry Pi. You will run `flashprog` from your Raspberry Pi.
|
||||
|
||||
You must configure `spidev` on your Raspberry Pi. This is a special driver in
|
||||
the GNU+Linux kernel; technically, the driver name is `spi-bcm2835`.
|
||||
the Linux kernel; technically, the driver name is `spi-bcm2835`.
|
||||
|
||||
This page has info:\
|
||||
<https://www.raspberrypi.org/documentation/hardware/raspberrypi/spi/README.md>
|
||||
|
|
@ -436,7 +436,7 @@ the problem here is that it gave Microsoft free reign to define whatever
|
|||
dependencies they liked (as per apt-get rules), and every time you updated,
|
||||
you would be pinging Microsoft servers. Do you think that is strange?
|
||||
|
||||
Microsoft shouldn't have *any* access to your GNU+Linux system! This was the
|
||||
Microsoft shouldn't have *any* access to your Linux system! This was the
|
||||
commit that Raspbian added to their distro, which added this what should rightly
|
||||
be called a security vulnerability, intentionally:
|
||||
|
||||
|
|
@ -482,7 +482,7 @@ script is also applicable to newer ubuntu versions
|
|||
If the `ubuntu2004` script complains about missing dependencies, just modify
|
||||
the dependencies config to remove those dependencies. The script is located
|
||||
at `config/dependencies/ubuntu2004` and it is written for
|
||||
Ubuntu 20.04, but it should work fine in other GNU+Linux distributions that use
|
||||
Ubuntu 20.04, but it should work fine in other Linux distributions that use
|
||||
the `apt-get` package manager.
|
||||
|
||||
A `flashprog/` directory will be present, with a `flashprog` executable inside
|
||||
|
|
|
|||
|
|
@ -46,7 +46,7 @@ Connecting via ethernet is generally easier than doing so with WiFi.
|
|||
Check your distro's docs if you wish to connect with WiFi only.
|
||||
To determine the IP address of your programmer, log in to your AP/Router web interface.
|
||||
If you're not sure the IP address of your AP, it is likely `192.168.1.1.`
|
||||
You can determine the correct IP address with `ip r` on a GNU+Linux system.
|
||||
You can determine the correct IP address with `ip r` on a Linux system.
|
||||
You should see your programmer somewhere on the homepage, depending on your router firmware.
|
||||
This author recommends using [https://openwrt.org/](https://openwrt.org/) for your router firmware.
|
||||
|
||||
|
|
@ -83,7 +83,7 @@ sudo ldto merge spicc spicc-spidev
|
|||
Using Flashprog
|
||||
==============
|
||||
|
||||
Some GNU+Linux distros will provide flashprog in their default repositories.
|
||||
Some Linux distros will provide flashprog in their default repositories.
|
||||
|
||||
```
|
||||
sudo apt update
|
||||
|
|
|
|||
|
|
@ -322,4 +322,4 @@ You should see something like this:
|
|||
|
||||
 
|
||||
|
||||
Now [install GNU+Linux](../gnulinux/).
|
||||
Now [install Linux](../linux/).
|
||||
|
|
|
|||
|
|
@ -353,4 +353,4 @@ You should see something like this:
|
|||
|
||||
|
||||
|
||||
Now [install GNU+Linux](../gnulinux/).
|
||||
Now [install Linux](../linux/).
|
||||
|
|
|
|||
|
|
@ -270,7 +270,7 @@ You should see something like this:
|
|||
|
||||
|
||||
|
||||
Now [install GNU+Linux](../gnulinux/).
|
||||
Now [install Linux](../linux/).
|
||||
|
||||
X200S and X200 Tablet users: GPIO33 trick will not work.
|
||||
--------------------------------------------------------
|
||||
|
|
|
|||
|
|
@ -262,7 +262,7 @@ Tablet (для цих систем потрібно повністю видал
|
|||
|
||||
|
||||
|
||||
Тепер [встановлюйте GNU+Linux](../gnulinux/).
|
||||
Тепер [встановлюйте Linux](../linux/).
|
||||
|
||||
Користувачі X200S та X200 Tablet: трюк GPIO33 не спрацює.
|
||||
--------------------------------------------------------
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: Installing GNU+Linux
|
||||
title: Installing Linux
|
||||
x-toc-enable: true
|
||||
...
|
||||
|
||||
|
|
@ -10,16 +10,16 @@ If you're using SeaBIOS, it's quite intuitive and works similarly to other BIOS
|
|||
software; refer to the documentation on <https://seabios.org/SeaBIOS>.
|
||||
|
||||
This guide explains how to prepare a bootable USB for Canoeboot systems that
|
||||
can be used to install several GNU+Linux distributions. For this guide, you
|
||||
can be used to install several Linux distributions. For this guide, you
|
||||
will only need a USB flash drive and the `dd` utility (it's installed into all
|
||||
GNU+Linux distributions, by default).
|
||||
Linux distributions, by default).
|
||||
|
||||
These instructions are intended to be generic, applicable to just about any
|
||||
GNU+Linux distribution.
|
||||
Linux distribution.
|
||||
|
||||
## Prepare the USB Drive in GNU+Linux
|
||||
If you downloaded your ISO while on an existing GNU+Linux system, here is how
|
||||
to create the bootable GNU+Linux USB drive:
|
||||
## Prepare the USB Drive in Linux
|
||||
If you downloaded your ISO while on an existing Linux system, here is how
|
||||
to create the bootable Linux USB drive:
|
||||
|
||||
Connect the USB drive. Check `lsblk`, to confirm its device name
|
||||
(e.g., **/dev/sdX**):
|
||||
|
|
@ -32,7 +32,7 @@ it's not mounted:
|
|||
sudo umount /dev/sdb
|
||||
|
||||
Overwrite the drive, writing your distro ISO to it with `dd`. For example, if
|
||||
we are installing *Foobarbaz* GNU+Linux, and it's located in our Downloads
|
||||
we are installing *Foobarbaz* Linux, and it's located in our Downloads
|
||||
folder, this is the command we would run:
|
||||
|
||||
sudo dd if=~/Downloads/foobarbaz.iso of=/dev/sdb bs=8M; sync
|
||||
|
|
@ -44,17 +44,17 @@ That's it! You should now be able to boot the installer from your USB drive
|
|||
[This page](https://wiki.netbsd.org/tutorials/how_to_install_netbsd_from_an_usb_memory_stick/)
|
||||
on the NetBSD website shows how to create a NetBSD bootable USB drive, from
|
||||
within NetBSD itself. You should the `dd` method documented there. This will
|
||||
work with any GNU+Linux ISO image.
|
||||
work with any Linux ISO image.
|
||||
|
||||
## Prepare the USB drive in FreeBSD
|
||||
[This page](https://www.freebsd.org/doc/handbook/bsdinstall-pre.html) on the
|
||||
FreeBSD website shows how to create a bootable USB drive for installing
|
||||
FreeBSD. Use the `dd` method documented. This will work with any GNU+Linux ISO
|
||||
FreeBSD. Use the `dd` method documented. This will work with any Linux ISO
|
||||
image.
|
||||
|
||||
## Prepare the USB drive in LibertyBSD or OpenBSD
|
||||
If you downloaded your ISO on a LibertyBSD or OpenBSD system, here is how to
|
||||
create the bootable GNU+Linux USB drive:
|
||||
create the bootable Linux USB drive:
|
||||
|
||||
Connect the USB drive. Run `lsblk` to determine which drive it is:
|
||||
|
||||
|
|
@ -103,7 +103,7 @@ menu, converted from the usual ISOLINUX menu provided by that distro.
|
|||
|
||||
## Booting ISOLINUX Images (Manual Method)
|
||||
These are generic instructions. They may or may not be correct for your
|
||||
distribution. You must adapt them appropriately, for whatever GNU+Linux
|
||||
distribution. You must adapt them appropriately, for whatever Linux
|
||||
distribution it is that you are trying to install.
|
||||
|
||||
If the `ISOLINUX parser` or `Search for GRUB configuration` options won't work,
|
||||
|
|
@ -154,9 +154,9 @@ USB drive in the way that you specified.
|
|||
## Troubleshooting
|
||||
Most of these issues occur when using Canoeboot with coreboot's `text-mode`
|
||||
with libgfxinit for video initialization. This mode is useful for text mode
|
||||
payloads, like `MemTest86+`, which expect `text-mode`, but for GNU+Linux
|
||||
payloads, like `MemTest86+`, which expect `text-mode`, but for Linux
|
||||
distributions it can be problematic when they are trying to switch to a
|
||||
framebuffer, because no mode switching support is present (GNU+Linux/BSD kernels
|
||||
framebuffer, because no mode switching support is present (Linux/BSD kernels
|
||||
do Kernel Mode Setting, so they are able to initialize a frame buffer in bare
|
||||
metal regardless of whatever coreboot is doing).
|
||||
|
||||
|
|
@ -41,7 +41,7 @@ linked above tells you how to apply your modifications for flashing.**
|
|||
Flash write protection
|
||||
======================
|
||||
|
||||
Although not strictly related to GNU GRUB, flash protection will prevent anyone
|
||||
Although not strictly related to GRUB, flash protection will prevent anyone
|
||||
except you from overwriting the flash without permission. This is important,
|
||||
because you don't want some malicious software running as root from overwriting
|
||||
your flash, thus removing any of the above protections.
|
||||
|
|
@ -1,12 +1,12 @@
|
|||
---
|
||||
title: GNU+Linux guides
|
||||
title: Linux guides
|
||||
x-toc-enable: true
|
||||
...
|
||||
|
||||
NOTE: This guide pertains to x86 hosts, and does not cover supported CrOS/ARM
|
||||
chromebooks. For ARM targets, you should refer to u-boot documentation.
|
||||
|
||||
GNU GRUB
|
||||
GRUB
|
||||
--------
|
||||
|
||||
This page is useful for those who wish to use the GRUB GRUB payload directly.
|
||||
|
|
@ -14,7 +14,7 @@ If you're using SeaBIOS, the boot process will work similarly to traditional
|
|||
BIOS systems; refer to the SeaBIOS documentation
|
||||
on <https://seabios.org/SeaBIOS>
|
||||
|
||||
GNU+Linux is generally assumed, especially for Canoeboot development, but Canoeboot
|
||||
Linux is generally assumed, especially for Canoeboot development, but Canoeboot
|
||||
also works quite nicely with [BSD systems](../bsd/).
|
||||
|
||||
Useful links
|
||||
|
|
@ -104,7 +104,7 @@ has argon2 support, but older releases only supported PBKDF2 which would make
|
|||
LUKS2 dysfunctional unless you swapped it to use PBKDF2 (not argon2) and/or
|
||||
downgraded to LUKS1.
|
||||
|
||||
With modern Canoeboot, you can just use LUKS2 as-is, on most/all GNU+Linux distros.
|
||||
With modern Canoeboot, you can just use LUKS2 as-is, on most/all Linux distros.
|
||||
At the time of the Canoeboot 20231026 release, the GRUB upstream (on gnu.org)
|
||||
did not have these argon2 patches in its source tree, but Canoeboot merges and
|
||||
maintains them out of tree.
|
||||
|
|
@ -123,7 +123,7 @@ NOTE: You should also read the instructions about about `GRUB_TERMINAL`.
|
|||
Rebooting system in case of freeze
|
||||
===================================
|
||||
|
||||
GNU+Linux kernel has a feature to do actions to the system any time, even
|
||||
Linux kernel has a feature to do actions to the system any time, even
|
||||
with it freezes, this is called a
|
||||
[Magic SysRq keys](https://en.wikipedia.org/wiki/Reisub). You can do these
|
||||
actions with Alt + Sysrq + Command. These are the actions:
|
||||
|
|
@ -28,9 +28,9 @@ Canoeboot's build system (called *cbmk*).
|
|||
|
||||
The homepage of Canoeboot says that Canoeboot is a *coreboot distro*, providing
|
||||
the necessary integration of coreboot, payloads and utilities so as to provide
|
||||
releases, much like GNU+Linux distros do for your operating system, but here we are
|
||||
releases, much like Linux distros do for your operating system, but here we are
|
||||
concerned about the *boot firmware* instead. Canoeboot is to coreboot, what
|
||||
Debian is to GNU+Linux. It provides easier, more automated configuration and
|
||||
Debian is to Linux. It provides easier, more automated configuration and
|
||||
installation.
|
||||
|
||||
The build system, cbmk, *is* that coreboot distro, at its very core. You can
|
||||
|
|
@ -82,7 +82,7 @@ This concerns system requirements when *building* Canoeboot.
|
|||
Operating system
|
||||
----------------
|
||||
|
||||
Any sensible GNU+Linux distribution will do. Canoeboot's build system is regularly
|
||||
Any sensible Linux distribution will do. Canoeboot's build system is regularly
|
||||
testing on all the major distros. Please do report bugs if you encounter
|
||||
issues.
|
||||
|
||||
|
|
@ -367,7 +367,7 @@ src/grub/TREE
|
|||
|
||||
Please also visit: <https://www.gnu.org/software/grub/>
|
||||
|
||||
The GNU GRUB bootloader, a reference multiboot implementation with its own
|
||||
The GRUB bootloader, a reference multiboot implementation with its own
|
||||
small kernel/OS and drivers (e.g. file systems, cryptography). This is the
|
||||
default recommended [coreboot payload](https://doc.coreboot.org/payloads.html)
|
||||
on x86-based Canoeboot systems. GRUB will load and execute your Linux kernel,
|
||||
|
|
@ -717,7 +717,7 @@ other than `default`, which is the default if the option is missing.
|
|||
The `grub_scan_disk` option specifies can be `ahci`, `ata` or `both`, and it
|
||||
determines which types of disks are to be scanned, when the `grub.cfg` file in
|
||||
GRUB payloads tries to automatically find other `grub.cfg` files supplied by
|
||||
your GNU+Linux distro. On some machines, setting it to `ata` or `ahci`
|
||||
your Linux distro. On some machines, setting it to `ata` or `ahci`
|
||||
can improve boot speed by reducing delays; for example, trying to scan `ata0`
|
||||
on a ThinkPad X60 with the optical drive may cause GRUB to hang, so on that
|
||||
machine it is advisable to set this option to `ahci` (becuse the default HDD
|
||||
|
|
|
|||
|
|
@ -308,7 +308,7 @@ In addition to not using bashisms, commands that cbmk uses must also
|
|||
be portable; where possible, third party projects should be tweaked.
|
||||
|
||||
This is actually something that is currently lacking or otherwise untested
|
||||
in Canoeboot; it's currently assumed that only Linux (specifically GNU+Linux)
|
||||
in Canoeboot; it's currently assumed that only Linux (specifically Linux)
|
||||
will work, because many of the projects that Canoeboot makes use of will use
|
||||
bashisms, or other GNUisms (e.g. GNU-specific C extensions or GNU Make specific
|
||||
behaviour in Makefiles).
|
||||
|
|
|
|||
|
|
@ -64,7 +64,7 @@ Might want to run with --calibrate first
|
|||
|
||||
If powertop doesn't work, another way (reduces battery life slightly)
|
||||
is to add *processor.max\_cstate=2* to the *linux* line in grub.cfg,
|
||||
using [this guide](../gnulinux/grub_cbfs.md).
|
||||
using [this guide](../linux/grub_cbfs.md).
|
||||
|
||||
X60/T60: Serial port - how to use (for dock owners)
|
||||
|
||||
|
|
@ -101,7 +101,7 @@ The following guide is for Ubuntu, but it should work in Debian-based distros:
|
|||
|
||||
Note: part of the tutorial above requires changing your grub.cfg. Just
|
||||
change the `linux` line to add instructions for enabling getty. See
|
||||
[../gnulinux/grub\_cbfs.md](../gnulinux/grub_cbfs.md).
|
||||
[../linux/grub\_cbfs.md](../linux/grub_cbfs.md).
|
||||
|
||||
Finetune backlight control on intel gpu's
|
||||
=========================================
|
||||
|
|
@ -206,7 +206,7 @@ behaviour.
|
|||
You need to write changes in a Canoeboot ROM image, and flash it, in order
|
||||
to apply them. You can either use a pre-compiled rom image, or create an image
|
||||
from the current one in your computer. See here
|
||||
[../gnulinux/grub_cbfs.html#get-the-rom-image](../gnulinux/grub_cbfs.html#get-the-rom-image)
|
||||
[../linux/grub_cbfs.html#get-the-rom-image](../linux/grub_cbfs.html#get-the-rom-image)
|
||||
for more information on how to do that.
|
||||
|
||||
Once you have a Canoeboot rom image, say 'canoeboot.rom', you can write
|
||||
|
|
@ -227,7 +227,7 @@ You can check that the parameters are set in the image with :
|
|||
sudo ./nvramtool -C canoeboot.rom -a
|
||||
|
||||
Finally, you need to flash the rom with this new image. See here
|
||||
[../gnulinux/grub_cbfs.html#with-re-flashing-the-rom](../gnulinux/grub_cbfs.html#with-re-flashing-the-rom)
|
||||
[../linux/grub_cbfs.html#with-re-flashing-the-rom](../linux/grub_cbfs.html#with-re-flashing-the-rom)
|
||||
for a detailed explanation.
|
||||
|
||||
Get EDID: Find out the name (model) of your LCD panel
|
||||
|
|
@ -269,7 +269,7 @@ using more power) non-stop, which will drain battery life if this is a
|
|||
laptop. If power usage is a concern, then you should not use this.
|
||||
(we're also not sure whether this workaround is appropriate)*
|
||||
|
||||
To disable c-states, do this in GNU+Linux:
|
||||
To disable c-states, do this in Linux:
|
||||
|
||||
```
|
||||
for i in /sys/devices/system/cpu/cpu/cpuidle/state/disable;
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ x-toc-enable: true
|
|||
Background
|
||||
==========
|
||||
|
||||
The following process should theoretically be applicable to other U-Boot devices and GNU/Linux distributions, but the focus here is specifically on ArchLinuxARM.
|
||||
The following process should theoretically be applicable to other U-Boot devices and Linux distributions, but the focus here is specifically on ArchLinuxARM.
|
||||
|
||||
Sources used for this guide include the [following guide to install ArchLinuxARM on a RockPro64,](https://jforberg.se/blog/posts/2023-02-19-rockpro64/rockpro64.html)
|
||||
|
||||
|
|
@ -18,7 +18,7 @@ The purpose of this guide is to instruct users on how to install an ArchLinuxARM
|
|||
Boot Method
|
||||
===========
|
||||
|
||||
There are (at least) three methods that can be used to boot into a GNU+Linux distribution from u-boot:
|
||||
There are (at least) three methods that can be used to boot into a Linux distribution from u-boot:
|
||||
1) EFI - common, modern boot method for amd64 architecture machines. This is not distribution-specific, so if you intend to make a portable drive that is compatible across multiple systems, you may have a use case.
|
||||
|
||||
This is an unlikely use-case, so it's a bit odd to use an EFI partition when not using a UEFI system.
|
||||
|
|
@ -46,14 +46,14 @@ timeout 50
|
|||
|
||||
|
||||
label arch
|
||||
menu label Arch GNU+Linux ARM
|
||||
menu label Arch Linux ARM
|
||||
linux /Image
|
||||
initrd /initramfs-linux.img
|
||||
fdt /dtbs/rockchip/rk3399-gru-bob.dtb
|
||||
append root=PARTUUID=$PARTUUID rw console=tty1 console=ttyS2,115200 earlycon rootwait LANG=en_US.UTF-8
|
||||
|
||||
label archfallback
|
||||
menu label Arch GNU+Linux ARM (FALLBACK)
|
||||
menu label Arch Linux ARM (FALLBACK)
|
||||
linux /Image
|
||||
initrd /initramfs-linux-fallback.img
|
||||
fdt /dtbs/rockchip/rk3399-gru-bob.dtb
|
||||
|
|
@ -83,7 +83,7 @@ In the fdisk tui, create two partitions on a Master Boot Record:
|
|||
- set type to fat32 (ext2 is also supported by extlinux I believe, but I used fat32)
|
||||
- create a second partition of up to 15.8GB
|
||||
|
||||
You will find the appropriate options by typing `m` when using the fdisk tui on GNU+Linux distros.
|
||||
You will find the appropriate options by typing `m` when using the fdisk tui on Linux distros.
|
||||
|
||||
Now make the filesystems:
|
||||
```
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ a payload on x86 machines, both 32- and 64-bit. This is using the excellent work
|
|||
done by Simon Glass and others, on making U-Boot run as a generic x86 coreboot
|
||||
payload. It has several boot methods but the most interesting (in an x86
|
||||
context) is UEFI. U-Boot provides a very sensible UEFI implementation that can
|
||||
reliably boot many GNU+Linux and BSD systems.
|
||||
reliably boot many Linux and BSD systems.
|
||||
|
||||
Availability
|
||||
------------
|
||||
|
|
@ -62,7 +62,7 @@ If you see error `-2` it's likely that you have tried to boot a USB drive
|
|||
automatically; sometimes you have to do it manually (see the section below
|
||||
about using the bootflow command manually, via `bootflow select`).
|
||||
|
||||
Boot GNU/Linux or BSD installer (USB)
|
||||
Boot Linux or BSD installer (USB)
|
||||
---------------------------
|
||||
|
||||
Just stick your formatted USB stick in. U-Boot should detect it. Sometimes some
|
||||
|
|
@ -127,7 +127,7 @@ storing EFI variables, and Canoeboot disables SecureBoot by default. However,
|
|||
you can enable it. Information is available in U-Boot's official documentation.
|
||||
|
||||
If you want real boot security, don't use UEFI. Canoeboot's GRUB payload can
|
||||
be heavily hardened, by following the [GRUB hardening](../gnulinux/grub_hardening.md)
|
||||
be heavily hardened, by following the [GRUB hardening](../linux/grub_hardening.md)
|
||||
guide; this means using the GRUB payload instead of U-Boot.
|
||||
|
||||
UEFI SecureBoot with a Linux UKI could achieve similar results in a security
|
||||
|
|
|
|||
18
site/faq.md
18
site/faq.md
|
|
@ -78,7 +78,7 @@ Loading the option ROM from the PIKE2008 module on either ASUS KCMA-D8
|
|||
or KGPE-D16 causes the system to hang at boot. It's possible to use
|
||||
this in the payload (if you use a linux kernel payload, like linuxboot),
|
||||
or to boot (with SeaGRUB and/or SeaBIOS) from regular SATA and then use
|
||||
it in GNU+Linux. The GNU+Linux kernel is capable of using the PIKE2008
|
||||
it in Linux. The Linux kernel is capable of using the PIKE2008
|
||||
module without loading the option ROM.
|
||||
|
||||
How to save kernel panic logs on thinkpad laptops?
|
||||
|
|
@ -594,7 +594,7 @@ boot just fine, using the bootloader (GRUB) that is in the flash chip.
|
|||
This also means that even if you remove the HDD or SSD, you'll still
|
||||
have a functioning bootloader installed which could be used to boot a
|
||||
live distribution installer from a USB flash drive. See
|
||||
[Install GNU+Linux on Canoeboot](../docs/gnulinux/grub_boot_installer.md)
|
||||
[Install Linux on Canoeboot](../docs/linux/grub_boot_installer.md)
|
||||
|
||||
Nowadays, other payloads are also provided. If you're using the SeaBIOS payload,
|
||||
then the normal MBR bootsector is used on your HDD or SSD, like you would
|
||||
|
|
@ -608,7 +608,7 @@ automatically switch to a GRUB configuration on the HDD or SSD, if it
|
|||
exists. You can also load a different GRUB configuration, from any kind
|
||||
of device that is supported in GRUB (such as a USB flash drive). For
|
||||
more information, see
|
||||
[Modifying the GRUB configuration in Canoeboot](../docs/gnulinux/grub_cbfs.md)
|
||||
[Modifying the GRUB configuration in Canoeboot](../docs/linux/grub_cbfs.md)
|
||||
|
||||
If you're using the SeaBIOS payload, it's even easier. It works just like you
|
||||
would expect. SeaBIOS implements a normal x86 BIOS interface.
|
||||
|
|
@ -669,7 +669,7 @@ is transparent to the user of the drive.
|
|||
HDDs and SSDs are quite complex, and these days contain quite complex
|
||||
hardware which is even capable of running an entire operating system (by
|
||||
this, we mean that the drive itself is capable of running its own
|
||||
embedded OS), even GNU+Linux.
|
||||
embedded OS), even Linux.
|
||||
|
||||
SSDs and HDDs are a special case, since they are persistent storage
|
||||
devices as well as computers.
|
||||
|
|
@ -757,7 +757,7 @@ Other links:
|
|||
It is recommended that you use full disk encryption, on HDDs connected
|
||||
via USB. There are several adapters available online, that allow you to
|
||||
connect SATA HDDs via USB, and Canoeboot is capable of booting from them the
|
||||
normal way. Consult the documentation for your GNU+Linux/BSD operating system, so
|
||||
normal way. Consult the documentation for your Linux/BSD operating system, so
|
||||
that you can know how to install it with *full disk encryption*.
|
||||
|
||||
The current theory (unproven) is that this will at least prevent
|
||||
|
|
@ -832,12 +832,12 @@ as these are generally much safer.
|
|||
Operating Systems
|
||||
=================
|
||||
|
||||
Can I use GNU+Linux?
|
||||
Can I use Linux?
|
||||
--------------------------------------------------
|
||||
|
||||
Absolutely! It is well-tested in Canoeboot, and highly recommended. See
|
||||
[installing GNU+Linux](../docs/gnulinux/grub_boot_installer.md) and
|
||||
[booting GNU+Linux](../docs/gnulinux/grub_cbfs.md).
|
||||
[installing Linux](../docs/linux/grub_boot_installer.md) and
|
||||
[booting Linux](../docs/linux/grub_cbfs.md).
|
||||
|
||||
Any recent distribution should work, as long as it uses KMS (kernel mode
|
||||
setting) for the graphics.
|
||||
|
|
@ -847,7 +847,7 @@ Fedora won't boot? (maybe Redhat/CentOS)
|
|||
|
||||
On Fedora, by default the grub.cfg tries to boot linux in 16-bit mode. You
|
||||
just have to modify Fedora's GRUB configuration.
|
||||
Refer to [the GNU+Linux page](docs/gnulinux/).
|
||||
Refer to [the Linux page](docs/linux/).
|
||||
|
||||
Can I use BSD?
|
||||
----------------------------------
|
||||
|
|
|
|||
|
|
@ -37,7 +37,7 @@ Flashrom скаржиться на доступ DEVMEM
|
|||
|
||||
Приклад виводу flashprog з обома `CONFIG_STRICT_DEVMEM` та `CONFIG_IO_STRICT_DEVMEM` ввімкненими:
|
||||
```
|
||||
flashprog v0.9.9-r1955 on GNU+Linux 4.11.9-1-ARCH (x86_64)
|
||||
flashprog v0.9.9-r1955 on Linux 4.11.9-1-ARCH (x86_64)
|
||||
flashprog is free software, get the source code at https://flashprog.org
|
||||
|
||||
Calibrating delay loop... OK.
|
||||
|
|
@ -82,7 +82,7 @@ Ethernet не працює на моєму X200/T400/X60/T60, коли я йог
|
|||
або KGPE-D16 викликає зависання системи під час завантаження. Можна використовувати
|
||||
це в корисному навантаженні (якщо ви використовуєте корисне навантаження ядра linux, таке як linuxboot),
|
||||
або завантажитись (з SeaGRUB та/або SeaBIOS) зі звичайного SATA, а потім використовувати
|
||||
це в GNU+Linux. Ядро GNU+Linux здатне використовувати PIKE2008
|
||||
це в Linux. Ядро Linux здатне використовувати PIKE2008
|
||||
модуль без завантаження Option ROM.
|
||||
|
||||
Як зберегти журнали паніки ядра на ноутбуках Thinkpad?
|
||||
|
|
@ -638,7 +638,7 @@ HDD або SSD під час встановлення нового дистри
|
|||
Це означає, що навіть якщо ви виймете жорсткий диск або твердотільний накопичувач, у вас всеодно
|
||||
буде встановлено функціонуючий завантажувач, який можна використовувати для завантаження програми
|
||||
встановлення дистрибутива з флеш-пам'яті USB. Див.
|
||||
[Як інсталювати GNU+Linux у системі Canoeboot](../docs/gnulinux/grub_boot_installer.md)
|
||||
[Як інсталювати Linux у системі Canoeboot](../docs/linux/grub_boot_installer.md)
|
||||
|
||||
В даний час також передбачені інші корисні навантаження. Якщо ви використовуєте корисне навантаження SeaBIOS,
|
||||
тоді на вашому HDD або SSD використовується звичайний завантажувальний сектор MBR, як і слід було
|
||||
|
|
@ -652,7 +652,7 @@ HDD або SSD під час встановлення нового дистри
|
|||
існує. Ви також можете завантажити іншу конфігурацію GRUB з будь-якого пристрою, який підтримується
|
||||
GRUB (наприклад, флеш-накопичувач USB). Для
|
||||
більшої інформації див.
|
||||
[Змінення конфігурації GRUB в системах Canoeboot](../docs/gnulinux/grub_cbfs.md)
|
||||
[Змінення конфігурації GRUB в системах Canoeboot](../docs/linux/grub_cbfs.md)
|
||||
|
||||
Якщо ви використовуєте корисне навантаження SeaBIOS, це ще простіше. Це працює так, як ви
|
||||
очікували. SeaBIOS реалізує звичайний інтерфейс x86 BIOS.
|
||||
|
|
@ -712,7 +712,7 @@ AHCI/SATA), який програмне забезпечення ОС може
|
|||
Жорсткі диски та твердотільні накопичувачі є досить складними, і сьогодні містять досить складне
|
||||
обладнання, яке навіть здатне запускати цілу операційну систему (під цим ми маємо
|
||||
на увазі, що сам диск здатний запускати свою власну вбудовану ОС), навіть
|
||||
GNU+Linux або BusyBox/GNU+Linux.
|
||||
Linux або BusyBox/Linux.
|
||||
|
||||
SSD та HDD є особливим випадком, оскільки вони є постійними пристроями зберігання,
|
||||
а також комп'ютерами.
|
||||
|
|
@ -794,7 +794,7 @@ USB 3.0, який ще не можна використовувати в сво
|
|||
Рекомендовано використовувати повне шифрування диска на жорстких дисках,
|
||||
підключених через USB. У мережі є кілька адаптерів, які дозволяють підключати жорсткі диски
|
||||
SATA через USB, і проект Canoeboot здатний завантажуватись з них
|
||||
звичайним чином. Проконсультуйтесь з документацією для вашої операційної системи GNU+Linux/BSD,
|
||||
звичайним чином. Проконсультуйтесь з документацією для вашої операційної системи Linux/BSD,
|
||||
щоб знати те, як встановити їх з *повнодисковим шифруванням*:
|
||||
|
||||
|
||||
|
|
@ -870,12 +870,12 @@ WWAN, підключення до мережі 3g/4g (наприклад, GSM).
|
|||
Операційні системи
|
||||
=================
|
||||
|
||||
Чи я можу використовувати GNU+Linux?
|
||||
Чи я можу використовувати Linux?
|
||||
--------------------------------------------------
|
||||
|
||||
Абсолютно! Він добре перевірений в Canoeboot, та дуже рекомендований. Подивіться
|
||||
[встановлення GNU+Linux](../docs/gnulinux/grub_boot_installer.md) та
|
||||
[запуск GNU+Linux](../docs/gnulinux/grub_cbfs.md).
|
||||
[встановлення Linux](../docs/linux/grub_boot_installer.md) та
|
||||
[запуск Linux](../docs/linux/grub_cbfs.md).
|
||||
|
||||
Будь-який сучасний дистрибутив має працювати, допоки він використовує KMS (kernel mode
|
||||
setting) для графіки.
|
||||
|
|
@ -885,7 +885,7 @@ Fedora не завантажується? (також може бути заст
|
|||
|
||||
У Fedora типово grub.cfg намагається завантажити linux в 16-розрядному режимі.
|
||||
Вам просто потрібно змінити конфігурацію GRUB Fedora.
|
||||
Зверніться до [сторінки GNU+Linux](docs/gnulinux/).
|
||||
Зверніться до [сторінки Linux](docs/linux/).
|
||||
|
||||
Чи я можу використовувати BSD?
|
||||
----------------------------------
|
||||
|
|
|
|||
|
|
@ -2,6 +2,7 @@
|
|||
-------------------------------------------------------------------------------
|
||||
|
||||
* [Diese Seite bearbeiten](/git.de.md)
|
||||
* [Binary Blob Extermination Policy](/news/policy.html)
|
||||
* [Wer entwickelt Canoeboot?](/who.md)
|
||||
* [Libreboot](https://libreboot.org/)
|
||||
* [Lizenz](/license.md)
|
||||
|
|
|
|||
|
|
@ -2,6 +2,7 @@
|
|||
-------------------------------------------------------------------------------
|
||||
|
||||
* [Edit this page](/git.md)
|
||||
* [Binary Blob Extermination Policy](/news/policy.html)
|
||||
* [Who develops Canoeboot?](/who.md)
|
||||
* [Libreboot](https://libreboot.org/)
|
||||
* [License](/license.md)
|
||||
|
|
|
|||
|
|
@ -2,6 +2,7 @@
|
|||
-------------------------------------------------------------------------------
|
||||
|
||||
* [Modifica questa pagina](/git.de.md)
|
||||
* [Binary Blob Extermination Policy](/news/policy.html)
|
||||
* [Chi sviluppa Canoeboot?](/who.de.md)
|
||||
* [Libreboot](https://libreboot.org/)
|
||||
* [Licenza](/license.md)
|
||||
|
|
|
|||
|
|
@ -2,6 +2,7 @@
|
|||
-------------------------------------------------------------------------------
|
||||
|
||||
* [Редагувати цю сторінку](/git.md)
|
||||
* [Binary Blob Extermination Policy](/news/policy.html)
|
||||
* [Хто розробляє Canoeboot?](/who.md)
|
||||
* [Libreboot](https://libreboot.org/)
|
||||
* [Ліцензія](/license.md)
|
||||
|
|
|
|||
|
|
@ -2,6 +2,7 @@
|
|||
-------------------------------------------------------------------------------
|
||||
|
||||
* [编辑本页面](/git.md)
|
||||
* [Binary Blob Extermination Policy](/news/policy.html)
|
||||
* [谁在开发 Canoeboot?](/who.md)
|
||||
* [Libreboot](https://libreboot.org/)
|
||||
* [许可证](/license.md)
|
||||
|
|
|
|||
|
|
@ -8,7 +8,7 @@ so wie Debian eine Linux-Distribution ist. Das *Canoeboot* Projekt bietet
|
|||
eine [freie](https://writefreesoftware.org/learn) *Boot
|
||||
Firmware* welche auf [bestimmten Intel/AMD x86 und ARM Geräten](docs/install/#which-systems-are-supported-by-canoeboot)
|
||||
die Hardware initialisiert (z.b. Speicher-Controller, CPU, Peripherie),
|
||||
und dann einen Bootloader für dein Betriebssystem startet. [GNU+Linux](docs/gnulinux/)
|
||||
und dann einen Bootloader für dein Betriebssystem startet. [Linux](docs/linux/)
|
||||
sowie [BSD](docs/bsd/) werden gut unterstützt. Es ersetzt proprietäre BIOS/UEFI
|
||||
Firmware. Hilfe ist verfügbar
|
||||
via [\#canoeboot](https://web.libera.chat/#canoeboot)
|
||||
|
|
@ -25,7 +25,7 @@ Warum solltest Du *Canoeboot* verwenden?
|
|||
|
||||
Canoeboot gibt dir [Freiheit](https://writefreesoftware.org/learn) welche
|
||||
Du mit den meisten Boot Firmwares nicht hast, und zusätzlich schnellere Boot
|
||||
Geschwindigkeiten sowie [höhere Sicherheit](docs/gnulinux/grub_hardening.md).
|
||||
Geschwindigkeiten sowie [höhere Sicherheit](docs/linux/grub_hardening.md).
|
||||
Es ist extrem leistungsfähig und für viele Einsatzzwecke [konfigurierbar](docs/maintain/).
|
||||
|
||||
Du hast Rechte. Das Recht auf Privatsphäre, Gedankenfreiheit, Meinungsäußerungsfreiheit,
|
||||
|
|
@ -60,7 +60,7 @@ Tatsächlich versucht Canoeboot so nah am regulären Coreboot zu bleiben wie mö
|
|||
für jedes Board, aber mit vielen automatisch durch das Canoeboot Build System zur
|
||||
Verfügung gestellten verschiedenen Konfigurationstypen.
|
||||
|
||||
Ebenso wie *Debian* eine *GNU+Linux Distribution* ist, ist Canoeboot eine
|
||||
Ebenso wie *Debian* eine *Linux Distribution* ist, ist Canoeboot eine
|
||||
*Coreboot Distribution*. Sofern Du ein ROM Image von Grund auf herstellen möchtest,
|
||||
musst Du zunächst Konfigurationen auf Experten Level durchführen,
|
||||
und zwar für Coreboot, GRUB sowie sämtliche Software die Du sonst noch verwenden
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ x-toc-enable: true
|
|||
Canoeboot est un micrologiciel de démarrage [libéré](https://writefreesoftware.org/learn)
|
||||
qui initialise le matériel (càd le contrôleur mémoire, CPU,
|
||||
périphériques) sur [des ordinateurs x86/ARM spécifiques](docs/install/#which-systems-are-supported-by-canoeboot)
|
||||
et lance un chargeur d'amorçage pour votre système d'exploitation. [GNU+Linux](docs/gnulinux/) et [BSD](docs/bsd/) sont bien supportés. C'est un
|
||||
et lance un chargeur d'amorçage pour votre système d'exploitation. [Linux](docs/linux/) et [BSD](docs/bsd/) sont bien supportés. C'est un
|
||||
remplacement pour le micrologiciel UEFI/BIOS propriétaire.
|
||||
Des canaux d'aide sont disponibles
|
||||
dans le canal [\#canoeboot](https://web.libera.chat/#canoeboot) sur le serveur IRC [Libera](https://libera.chat/).
|
||||
|
|
@ -21,7 +21,7 @@ Pourquoi devriez-vous utiliser *Canoeboot*?
|
|||
|
||||
Canoeboot vous donne des [libertés](https://writefreesoftware.org/learn)
|
||||
que nous n'auriez pas autrement avec d'autre micrologiciel de démarrage. Il est
|
||||
extremement [puissant](docs/gnulinux/grub_hardening.md)
|
||||
extremement [puissant](docs/linux/grub_hardening.md)
|
||||
et [configurable](docs/maintain) pour plein de cas d'utilisations.
|
||||
|
||||
Vous avez des droits. Un droit à la vie privée, liberté de pensée, liberté d'espression et le droit de lire. Dans ce contexte là, Canoeboot vous permet d'avoir ces droits.
|
||||
|
|
@ -56,7 +56,7 @@ pas de fournir un Coreboot déblobbé; ceci n'est simplement qu'une
|
|||
des politiques de Canoeboot, une importante certes, mais qui n'est qu'un
|
||||
aspect mineur de Canoeboot.
|
||||
|
||||
De la même façon que *Debian* est une distribution GNU+Linux, Canoeboot
|
||||
De la même façon que *Debian* est une distribution Linux, Canoeboot
|
||||
est une *distribution coreboot*. Si vous voulez compilé une image ROM
|
||||
en partant des bases, vous devez alors effectuer une configuration experte
|
||||
de Coreboot, GRUB et n'importe quel autre logiciel dont vous avez besoin
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@ grazie al firmware basato su coreboot, sostituendo cosi', firmware BIOS/UEFI pro
|
|||
su [alcune schede madri basate su Intel/AMD x86 o ARM](docs/install/#which-systems-are-supported-by-canoeboot),
|
||||
in computer fissi e portatili. Inizializza l'hardware (controller di
|
||||
memoria, CPU, periferiche) e avvia un bootloader per il tuo sistema operativo.
|
||||
[GNU+Linux](docs/gnulinux/) e [BSD](docs/bsd/) sono ben supportati.
|
||||
[Linux](docs/linux/) e [BSD](docs/bsd/) sono ben supportati.
|
||||
L'aiuto e' disponibile sul canale IRC [\#canoeboot](https://web.libera.chat/#canoeboot)
|
||||
su [Libera](https://libera.chat/).
|
||||
|
||||
|
|
@ -23,7 +23,7 @@ Per quale ragione utilizzare *Canoeboot*?
|
|||
|
||||
Canoeboot ti permette [liberta'](https://writefreesoftware.org/learn) che non potresti ottenere
|
||||
con altri firmware di boot, velocita' di avvio maggiori
|
||||
e [migliore sicurezza](docs/gnulinux/grub_hardening.md).
|
||||
e [migliore sicurezza](docs/linux/grub_hardening.md).
|
||||
E' estremamente flessibile e [configurabile](docs/maintain/) per la maggior parte dei casi.
|
||||
|
||||
*Noi* crediamo nella liberta' di [studiare, condividere, modificare and usare
|
||||
|
|
@ -58,7 +58,7 @@ In effetti, Canoeboot tenta di essere il piu' possibile simile alla versione *uf
|
|||
per ogni scheda, ma con diversi tipi di configurazione forniti automaticamente dal sistema di
|
||||
compilazione automatico di Canoeboot.
|
||||
|
||||
Esattamente come *Debian* e' una *distribuzione GNU+Linux*, Canoeboot e' una
|
||||
Esattamente come *Debian* e' una *distribuzione Linux*, Canoeboot e' una
|
||||
*distribuzione coreboot*. Per fare un immagine ROM da zero, hai bisogno di esperienza necessaria
|
||||
nel configurare coreboot, GRUB e qualunque altra cosa ti serve. Con *Canoeboot*,
|
||||
che puoi scaricare da Git o da un archivio di codici sorgenti, puoi far partire `make`,
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ firmware based on coreboot, replacing proprietary BIOS/UEFI firmware
|
|||
on [specific Intel/AMD x86 and ARM based motherboards](docs/install/#which-systems-are-supported-by-canoeboot),
|
||||
including laptop and desktop computers. It initialises the hardware (e.g. memory
|
||||
controller, CPU, peripherals) and starts a bootloader for your operating
|
||||
system. [GNU+Linux](docs/gnulinux/) and [BSD](docs/bsd/) are well-supported. Help is
|
||||
system. [Linux](docs/linux/) and [BSD](docs/bsd/) are well-supported. Help is
|
||||
available via [\#canoeboot](https://web.libera.chat/#canoeboot)
|
||||
on [Libera](https://libera.chat/) IRC.
|
||||
|
||||
|
|
@ -26,7 +26,7 @@ Why should you use *Canoeboot*?
|
|||
|
||||
Canoeboot gives you [freedoms](https://writefreesoftware.org/learn) that
|
||||
you otherwise can't get with most other boot firmware, plus faster boot speeds
|
||||
and [better security](docs/gnulinux/grub_hardening.md). It's extremely powerful
|
||||
and [better security](docs/linux/grub_hardening.md). It's extremely powerful
|
||||
and [configurable](docs/maintain/) for many use cases. Canoeboot is a *special
|
||||
fork* of [Libreboot](https://libreboot.org/), maintained in parallel to it by the same developer (Leah
|
||||
Rowe); Canoeboot [removes all binary blobs](news/policy.md) from coreboot, unlike
|
||||
|
|
@ -48,7 +48,7 @@ In this context, *software freedom* matters. Your freedom matters. Education
|
|||
matters.
|
||||
[Right to repair](https://en.wikipedia.org/wiki/Right_to_repair) matters.
|
||||
Many people use proprietary (non-libre)
|
||||
boot firmware, even if they use a fully free GNU+Linux distribution.
|
||||
boot firmware, even if they use a fully free Linux distribution.
|
||||
Proprietary firmware often [contains](faq.html#intel) [backdoors](faq.html#amd),
|
||||
and can be buggy. The Canoeboot project was founded in October 2023, with the
|
||||
express purpose of making coreboot firmware accessible for non-technical users.
|
||||
|
|
@ -74,7 +74,7 @@ In fact, Canoeboot tries to stay as close to *stock* coreboot as possible,
|
|||
for each board, but with many different types of configuration provided
|
||||
automatically by the Canoeboot build system.
|
||||
|
||||
In the same way that *Debian* is a *GNU+Linux distribution*, Canoeboot is
|
||||
In the same way that *Debian* is a *Linux distribution*, Canoeboot is
|
||||
a *coreboot distribution*. If you want to build a ROM image from scratch, you
|
||||
otherwise have to perform expert-level configuration of coreboot, GRUB and
|
||||
whatever other software you need, to prepare the ROM image. With *Canoeboot*,
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ x-toc-enable: true
|
|||
[вільну](https://writefreesoftware.org/learn) *завантажувальну
|
||||
прошивку*, яка ініціалізує апаратне забезпечення (наприклад, контролер пам'яті, ЦП,
|
||||
периферію) на [конкретних цілях Intel/AMD x86 та ARM](docs/install/#which-systems-are-supported-by-canoeboot), що
|
||||
потім розпочинає завантажувач для вашої операційної системи. [GNU+Linux](docs/gnulinux/)
|
||||
потім розпочинає завантажувач для вашої операційної системи. [Linux](docs/linux/)
|
||||
та [BSD](docs/bsd/) добре підтримуються. Це заміняє пропрієтарну BIOS/UEFI
|
||||
прошивку. Допомога доступна
|
||||
через [\#canoeboot](https://web.libera.chat/#canoeboot)
|
||||
|
|
@ -23,7 +23,7 @@ x-toc-enable: true
|
|||
|
||||
Canoeboot надає вам [свободи](https://writefreesoftware.org/learn), які в
|
||||
іншому випадку ви не можете отримати з більшістю інших завантажувальних
|
||||
прошивок. Він надзвичайно [потужний](docs/gnulinux/grub_hardening.md)
|
||||
прошивок. Він надзвичайно [потужний](docs/linux/grub_hardening.md)
|
||||
та [налаштовується](docs/maintain/) для багатьох випадків використання.
|
||||
|
||||
У вас є права. Право на конфіденційність, свобода мислення, свобода висловлювання
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ x-toc-enable: true
|
|||
...
|
||||
|
||||
Canoeboot 是 [Libreboot](https://libreboot.org/) 的分支。
|
||||
*Canoeboot* 项目基于 coreboot 提供了[自由且开源](https://writefreesoftware.org/zh-cn/learn/)的引导固件，替代了特定基于 Intel/AMD x86 及 ARM 的主板（包括笔记本和桌面计算机）上的专有 BIOS/UEFI 固件。它首先对硬件（如内存控制器、CPU、外设）进行初始化，然后为操作系统启动 bootloader。本项目对 [GNU+Linux](docs/gnulinux/) 和 [BSD](docs/bsd/) 支持良好。寻求帮助，可以前往 [Libera](https://libera.chat/) IRC 上的 [\#canoeboot](https://web.libera.chat/#canoeboot) 频道。
|
||||
*Canoeboot* 项目基于 coreboot 提供了[自由且开源](https://writefreesoftware.org/zh-cn/learn/)的引导固件，替代了特定基于 Intel/AMD x86 及 ARM 的主板（包括笔记本和桌面计算机）上的专有 BIOS/UEFI 固件。它首先对硬件（如内存控制器、CPU、外设）进行初始化，然后为操作系统启动 bootloader。本项目对 [Linux](docs/linux/) 和 [BSD](docs/bsd/) 支持良好。寻求帮助，可以前往 [Libera](https://libera.chat/) IRC 上的 [\#canoeboot](https://web.libera.chat/#canoeboot) 频道。
|
||||
|
||||
<img tabindex=1 class="r" src="https://av.canoeboot.org/t60logo.jpg" /><span class="f"><img src="https://av.canoeboot.org/t60logo.jpg" /></span>
|
||||
|
||||
|
|
@ -13,7 +13,7 @@ Canoeboot 是 [Libreboot](https://libreboot.org/) 的分支。
|
|||
为什么要使用 *Canoeboot*?
|
||||
----------------------------
|
||||
|
||||
Canoeboot 赋予了你[自由](https://writefreesoftware.org/learn)，而这等自由，是你用其他引导固件得不到的。同时，它的启动速度更加快，[安全性也更加高](docs/gnulinux/grub_hardening.md)。在各种情况下使用，它都十分强大，具有高度[可配置性](docs/maintain/)。
|
||||
Canoeboot 赋予了你[自由](https://writefreesoftware.org/learn)，而这等自由，是你用其他引导固件得不到的。同时，它的启动速度更加快，[安全性也更加高](docs/linux/grub_hardening.md)。在各种情况下使用，它都十分强大，具有高度[可配置性](docs/maintain/)。
|
||||
|
||||
*我们*相信，不受限制地[研究、分享、修改及使用软件](https://writefreesoftware.org/)的自由，是每个人都必须享有的基本人权的一部分。这时，*软件自由*至关重要。你的自由至关重要。教育至关重要。[修理权](https://en.wikipedia.org/wiki/Right_to_repair)至关重要。尽管许多人在用自由的操作系统，但他们用的引导固件却是专有（非自由）的。专有固件常常[包含](faq.html#intel)了[后门](faq.html#amd)，并且也可能出问题。2023 年 10 月，我们建立了 Canoeboot 项目，目的是让不懂技术的用户能使用 coreboot 固件。
|
||||
|
||||
|
|
@ -26,7 +26,7 @@ Canoeboot 不是 coreboot 的分支
|
|||
|
||||
事实上，Canoeboot 对每一块主板，都尽可能保持与*标准*的 coreboot 接近，但 Canoeboot 构建系统也自动提供了许多不同类型的配置。
|
||||
|
||||
Canoeboot 是一个 *coreboot 发行版*，就好比 *Debian* 是一个 *GNU+Linux 发行版*。如果你想要从零开始构建 ROM 镜像，那你需要对 coreboot、GRUB 以及其他所需软件进行专业级别的配置，才能准备好 ROM 镜像。有了 *Canoeboot*，你只需要下载 Git 仓库或者源代码归档，然后运行 `make`，接着就能构建整个 ROM 镜像。一套自动构建系统，名为 `cbmk`（Canoeboot Make），将自动构建 ROM 镜像，而无需任何用户输入或干预。配置已经提前完成。
|
||||
Canoeboot 是一个 *coreboot 发行版*，就好比 *Debian* 是一个 *Linux 发行版*。如果你想要从零开始构建 ROM 镜像，那你需要对 coreboot、GRUB 以及其他所需软件进行专业级别的配置，才能准备好 ROM 镜像。有了 *Canoeboot*，你只需要下载 Git 仓库或者源代码归档，然后运行 `make`，接着就能构建整个 ROM 镜像。一套自动构建系统，名为 `cbmk`（Canoeboot Make），将自动构建 ROM 镜像，而无需任何用户输入或干预。配置已经提前完成。
|
||||
|
||||
如果你要构建常规的 coreboot，而不使用 Canoeboot 的自动构建系统，那么需要有很多的干预以及相当的技术知识，才能写出一份能工作的配置。
|
||||
|
||||
|
|
|
|||
|
|
@ -18,12 +18,12 @@ this by providing an automated build system to download, patch and compile
|
|||
the various upstream sources (e.g. coreboot, GRUB, SeaBIOS). Coreboot is used
|
||||
for hardware initialisation, configuring everything from your CPU, memory
|
||||
controller all way to peripherals, readying the hardware so that it can run
|
||||
software, e.g. GNU+Linux operating systems. You can essentially think of *cbmk*,
|
||||
software, e.g. Linux operating systems. You can essentially think of *cbmk*,
|
||||
which is Canoeboot's build system, as a *source-based package manager*. It is
|
||||
what the Canoeboot releases are built with. The *cbmk* build system essentially
|
||||
implements
|
||||
a *[coreboot distro](../docs/maintain/)*, the same way you might think of
|
||||
a GNU+Linux distribution.
|
||||
a Linux distribution.
|
||||
|
||||
Extensive auditing has been performed on cbmk, since the Canoeboot 20240504
|
||||
release. These audits fix bugs, reduce code bloat and generally improve the
|
||||
|
|
|
|||
|
|
@ -14,11 +14,11 @@ this by providing an automated build system to download, patch and compile
|
|||
the various upstream sources (e.g. coreboot, GRUB, SeaBIOS). Coreboot is used
|
||||
for hardware initialisation, configuring everything from your CPU, memory
|
||||
controller all way to peripherals, readying the hardware so that it can run
|
||||
software, e.g. GNU+Linux and BSD systems. You can essentially think of *cbmk*,
|
||||
software, e.g. Linux and BSD systems. You can essentially think of *cbmk*,
|
||||
which is Canoeboot's build system, as a *source-based package manager*. It is
|
||||
what the Canoeboot releases are built with. The *cbmk* build system essentially
|
||||
implements a *[coreboot distro](../docs/maintain/)*,
|
||||
the same way you might think of a GNU+Linux
|
||||
the same way you might think of a Linux
|
||||
distribution; it systematically downloads, resets (to specific revisions) and
|
||||
patches various upstream project sources such as coreboot, U-Boot and GRUB,
|
||||
automatically building entire coreboot images. This build system is what creates
|
||||
|
|
@ -222,7 +222,7 @@ The changes are as follows:
|
|||
Canoeboot 20240612 already removed actual configs using `grubonly`, and we
|
||||
will no longer provide them in Canoeboot, so this feature in cbmk became
|
||||
legacy cruft that can simply be removed. The idea is simple: *safety first*.
|
||||
This has implications for [GRUB hardening](../docs/gnulinux/grub_hardening.md);
|
||||
This has implications for [GRUB hardening](../docs/linux/grub_hardening.md);
|
||||
you can insert the correct bootorder file, to once again disable SeaBIOS, but
|
||||
you must first verify that GRUB is stable. The GRUB hardening guide already
|
||||
documents how to do this.
|
||||
|
|
|
|||
|
|
@ -26,14 +26,14 @@ ROM images, making coreboot easier to use for non-technical people. You can find
|
|||
the [list of supported hardware](../docs/hardware/) in Canoeboot documentation.
|
||||
|
||||
Canoeboot's main benefit is *higher boot speed*,
|
||||
[better](../docs/gnulinux/encryption.md)
|
||||
[security](../docs/gnulinux/grub_hardening.md) and more
|
||||
[better](../docs/linux/encryption.md)
|
||||
[security](../docs/linux/grub_hardening.md) and more
|
||||
customisation options compared to most proprietary firmware. As a
|
||||
[libre](https://writefreesoftware.org/learn) software project, the code can be
|
||||
audited, and coreboot does
|
||||
regularly audit code. The other main benefit is [*freedom* to study, adapt and
|
||||
share the code](https://writefreesoftware.org/), a freedom denied by most boot
|
||||
firmware, but not Canoeboot! Booting Linux/BSD is also [well](../docs/gnulinux/)
|
||||
firmware, but not Canoeboot! Booting Linux/BSD is also [well](../docs/linux/)
|
||||
[supported](../docs/bsd/).
|
||||
|
||||
Canoeboot is maintained in parallel with [Libreboot](https://libreboot.org/), and by the same developer,
|
||||
|
|
|
|||
|
|
@ -28,14 +28,14 @@ ROM images, making coreboot easier to use for non-technical people. You can find
|
|||
the [list of supported hardware](../docs/hardware/) in Canoeboot documentation.
|
||||
|
||||
Canoeboot's main benefit is *higher boot speed*,
|
||||
[better](../docs/gnulinux/encryption.md)
|
||||
[security](../docs/gnulinux/grub_hardening.md) and more
|
||||
[better](../docs/linux/encryption.md)
|
||||
[security](../docs/linux/grub_hardening.md) and more
|
||||
customisation options compared to most proprietary firmware. As a
|
||||
[libre](https://writefreesoftware.org/learn) software project, the code can be
|
||||
audited, and coreboot does
|
||||
regularly audit code. The other main benefit is [*freedom* to study, adapt and
|
||||
share the code](https://writefreesoftware.org/), a freedom denied by most boot
|
||||
firmware, but not Canoeboot! Booting Linux/BSD is also [well](../docs/gnulinux/)
|
||||
firmware, but not Canoeboot! Booting Linux/BSD is also [well](../docs/linux/)
|
||||
[supported](../docs/bsd/).
|
||||
|
||||
Canoeboot is maintained in parallel with Libreboot, and by the same developer,
|
||||
|
|
|
|||
|
|
@ -29,14 +29,14 @@ ROM images, making coreboot easier to use for non-technical people. You can find
|
|||
the [list of supported hardware](../docs/hardware/) in Canoeboot documentation.
|
||||
|
||||
Canoeboot's main benefit is *higher boot speed*,
|
||||
[better](../docs/gnulinux/encryption.md)
|
||||
[security](../docs/gnulinux/grub_hardening.md) and more
|
||||
[better](../docs/linux/encryption.md)
|
||||
[security](../docs/linux/grub_hardening.md) and more
|
||||
customisation options compared to most proprietary firmware. As a
|
||||
[libre](https://writefreesoftware.org/learn) software project, the code can be
|
||||
audited, and coreboot does
|
||||
regularly audit code. The other main benefit is [*freedom* to study, adapt and
|
||||
share the code](https://writefreesoftware.org/), a freedom denied by most boot
|
||||
firmware, but not Canoeboot! Booting Linux/BSD is also [well](../docs/gnulinux/)
|
||||
firmware, but not Canoeboot! Booting Linux/BSD is also [well](../docs/linux/)
|
||||
[supported](../docs/bsd/).
|
||||
|
||||
Canoeboot is maintained in parallel with [Libreboot](https://libreboot.org/), and by the same developer,
|
||||
|
|
|
|||
|
|
@ -30,14 +30,14 @@ ROM images, making coreboot easier to use for non-technical people. You can find
|
|||
the [list of supported hardware](../docs/hardware/) in Canoeboot documentation.
|
||||
|
||||
Canoeboot's main benefit is *higher boot speed*,
|
||||
[better](../docs/gnulinux/encryption.md)
|
||||
[security](../docs/gnulinux/grub_hardening.md) and more
|
||||
[better](../docs/linux/encryption.md)
|
||||
[security](../docs/linux/grub_hardening.md) and more
|
||||
customisation options compared to most proprietary firmware. As a
|
||||
[libre](https://writefreesoftware.org/) software project, the code can be
|
||||
audited, and coreboot does regularly audit code. The other main benefit
|
||||
is [*freedom* to study, adapt and
|
||||
share the code](https://writefreesoftware.org/), a freedom denied by most boot
|
||||
firmware, but not Canoeboot! Booting Linux/BSD is also [well](../docs/gnulinux/)
|
||||
firmware, but not Canoeboot! Booting Linux/BSD is also [well](../docs/linux/)
|
||||
[supported](../docs/bsd/).
|
||||
|
||||
Work done since last release
|
||||
|
|
|
|||
|
|
@ -15,25 +15,25 @@ Introduction
|
|||
|
||||
Canoeboot is a free/libre BIOS/UEFI replacement on x86 and ARM, providing
|
||||
boot firmware that initialises the hardware in your computer, to then load an
|
||||
operating system (e.g. GNU+Linux). It is specifically
|
||||
operating system (e.g. Linux). It is specifically
|
||||
a *[coreboot distribution](../docs/maintain/)*,
|
||||
in the same way that Debian is a GNU+Linux distribution. It provides an automated
|
||||
in the same way that Debian is a Linux distribution. It provides an automated
|
||||
build system to produce coreboot ROM images with a variety of payloads such as
|
||||
GNU GRUB or SeaBIOS, with regular well-tested releases to make coreboot as easy
|
||||
GRUB or SeaBIOS, with regular well-tested releases to make coreboot as easy
|
||||
to use as possible for non-technical users. From a project management perspective,
|
||||
this works in *exactly* the same way as a GNU+Linux distro, providing the same type
|
||||
this works in *exactly* the same way as a Linux distro, providing the same type
|
||||
of infrastructure, but for your boot firmware instead of your operating system.
|
||||
It makes use of [coreboot](https://www.coreboot.org/) for hardware initialisation,
|
||||
and then a payload such as [SeaBIOS](https://www.seabios.org/SeaBIOS)
|
||||
or [GNU GRUB](https://www.gnu.org/software/grub/) to boot your operating
|
||||
or [GRUB](https://www.gnu.org/software/grub/) to boot your operating
|
||||
system; on ARM(chromebooks), we provide *U-Boot* (as a coreboot payload).
|
||||
|
||||
Canoeboot provides many additional benefits such as fast boot speeds, greater
|
||||
security and greater customisation, but the *primary* benefit
|
||||
is [software freedom](https://writefreesoftware.org/learn). With use of GRUB
|
||||
in the flash, you can make use of many advanced features such as the ability
|
||||
to [boot from an encrypted /boot partition](../docs/gnulinux/)
|
||||
and [verify kernel GPG signature at boot time](../docs/gnulinux/grub_hardening.md).
|
||||
to [boot from an encrypted /boot partition](../docs/linux/)
|
||||
and [verify kernel GPG signature at boot time](../docs/linux/grub_hardening.md).
|
||||
Canoeboot's GRUB payload is *heavily* patched; for example, today's release
|
||||
uses GRUB based on version 2.12, but Canoeboot adds argon2 KDF support (for
|
||||
LUKS2) and xHCI support - you can use USB 3.0 devices natively, in GRUB,
|
||||
|
|
@ -51,9 +51,9 @@ is being added all the time!
|
|||
|
||||
These and other examples are just the start. Canoeboot provides a *superior* boot
|
||||
experience compared to proprietary BIOS/UEFI, giving you the same power and level of
|
||||
control that a fully free GNU+Linux system would afford. It's *your* computer
|
||||
control that a fully free Linux system would afford. It's *your* computer
|
||||
to boot however you wish. Canoeboot lets you get more out of the hardware. All
|
||||
your favourite GNU+Linux distros are compatible, even Qubes(on most machines).
|
||||
your favourite Linux distros are compatible, even Qubes(on most machines).
|
||||
|
||||
If you're fed up of the control that proprietary UEFI vendors have over you,
|
||||
then Canoeboot is *for you*. Although many would agree that it is a major step
|
||||
|
|
@ -403,7 +403,7 @@ are highlighted in bold:
|
|||
should increase compatibility with distros that use extlinux.
|
||||
* `grub.cfg`: Handle GRUB *and* syslinux/extlinux configs, on the USB boot menu
|
||||
option. Now it scans for both, thus increasing compatibility with many modern
|
||||
GNU+Linux distro installers. Before this change, Canoeboot's design was made with
|
||||
Linux distro installers. Before this change, Canoeboot's design was made with
|
||||
BIOS systems in mind, because we historically only supported systems that were
|
||||
BIOS-based, whereas GRUB is more common as a bootloader on UEFI-based install
|
||||
media, but in the past we mostly assumed isolinux/syslinux for that.
|
||||
|
|
|
|||
|
|
@ -16,25 +16,25 @@ Introduction
|
|||
Canoeboot is a [free/libre](https://writefreesoftware.org/) BIOS/UEFI replacement
|
||||
on x86 and ARM, providing
|
||||
boot firmware that initialises the hardware in your computer, to then load an
|
||||
operating system (e.g. GNU+Linux). It is specifically
|
||||
operating system (e.g. Linux). It is specifically
|
||||
a *[coreboot distribution](../docs/maintain/)*,
|
||||
in the same way that Debian is a GNU+Linux distribution. It provides an automated
|
||||
in the same way that Debian is a Linux distribution. It provides an automated
|
||||
build system to produce coreboot ROM images with a variety of payloads such as
|
||||
GNU GRUB or SeaBIOS, with regular well-tested releases to make coreboot as easy
|
||||
GRUB or SeaBIOS, with regular well-tested releases to make coreboot as easy
|
||||
to use as possible for non-technical users. From a project management perspective,
|
||||
this works in *exactly* the same way as a GNU+Linux distro, providing the same type
|
||||
this works in *exactly* the same way as a Linux distro, providing the same type
|
||||
of infrastructure, but for your boot firmware instead of your operating system.
|
||||
It makes use of [coreboot](https://www.coreboot.org/) for hardware initialisation,
|
||||
and then a payload such as [SeaBIOS](https://www.seabios.org/SeaBIOS)
|
||||
or [GNU GRUB](https://www.gnu.org/software/grub/) to boot your operating
|
||||
or [GRUB](https://www.gnu.org/software/grub/) to boot your operating
|
||||
system; on ARM(chromebooks), we provide *U-Boot* (as a coreboot payload).
|
||||
|
||||
Canoeboot provides many additional benefits such as fast boot speeds, greater
|
||||
security and greater customisation, but the *primary* benefit
|
||||
is [software freedom](https://writefreesoftware.org/learn). With use of GRUB
|
||||
in the flash, you can make use of many advanced features such as the ability
|
||||
to [boot from an encrypted /boot partition](../docs/gnulinux/)
|
||||
and [verify kernel GPG signature at boot time](../docs/gnulinux/grub_hardening.md).
|
||||
to [boot from an encrypted /boot partition](../docs/linux/)
|
||||
and [verify kernel GPG signature at boot time](../docs/linux/grub_hardening.md).
|
||||
|
||||
If you're fed up of the control that proprietary UEFI vendors have over you,
|
||||
then Canoeboot is *for you*. Although many would agree that it is a major step
|
||||
|
|
|
|||
|
|
@ -12,17 +12,17 @@ Introduction
|
|||
|
||||
Canoeboot is a free/libre BIOS/UEFI replacement on x86 and ARM, providing
|
||||
boot firmware that initialises the hardware in your computer, to then load an
|
||||
operating system (e.g. GNU+Linux). It is specifically
|
||||
operating system (e.g. Linux). It is specifically
|
||||
a *[coreboot distribution](../docs/maintain/)*,
|
||||
in the same way that Debian is a GNU+Linux distribution. It provides an automated
|
||||
in the same way that Debian is a Linux distribution. It provides an automated
|
||||
build system to produce coreboot ROM images with a variety of payloads such as
|
||||
GNU GRUB or SeaBIOS, with regular well-tested releases to make coreboot as easy
|
||||
GRUB or SeaBIOS, with regular well-tested releases to make coreboot as easy
|
||||
to use as possible for non-technical users. From a project management perspective,
|
||||
this works in *exactly* the same way as a GNU+Linux distro, providing the same type
|
||||
this works in *exactly* the same way as a Linux distro, providing the same type
|
||||
of infrastructure, but for your boot firmware instead of your operating system.
|
||||
It makes use of [coreboot](https://www.coreboot.org/) for hardware initialisation,
|
||||
and then a payload such as [SeaBIOS](https://www.seabios.org/SeaBIOS)
|
||||
or [GNU GRUB](https://www.gnu.org/software/grub/) to boot your operating
|
||||
or [GRUB](https://www.gnu.org/software/grub/) to boot your operating
|
||||
system; on ARM(chromebooks), we provide *U-Boot* (as a coreboot payload).
|
||||
|
||||
This is a *bugfix* release, and is considered stable. It fixes a series of bugs
|
||||
|
|
|
|||
|
|
@ -12,17 +12,17 @@ Introduction
|
|||
|
||||
Canoeboot is a free/libre BIOS/UEFI replacement on x86 and ARM, providing
|
||||
boot firmware that initialises the hardware in your computer, to then load an
|
||||
operating system (e.g. GNU+Linux). It is specifically
|
||||
operating system (e.g. Linux). It is specifically
|
||||
a *[coreboot distribution](../docs/maintain/)*,
|
||||
like how Debian is a GNU+Linux distribution. It provides an automated
|
||||
like how Debian is a Linux distribution. It provides an automated
|
||||
build system to produce coreboot ROM images with a variety of payloads such as
|
||||
GNU GRUB or SeaBIOS, with regular well-tested releases to make coreboot as easy
|
||||
GRUB or SeaBIOS, with regular well-tested releases to make coreboot as easy
|
||||
to use as possible for non-technical users. From a project management perspective,
|
||||
this works in *exactly* the same way as a GNU+Linux distro, providing a source-based
|
||||
this works in *exactly* the same way as a Linux distro, providing a source-based
|
||||
package manager (called cbmk) which patches sources and compiles coreboot images.
|
||||
It makes use of [coreboot](https://www.coreboot.org/) for hardware initialisation,
|
||||
and then a payload such as [SeaBIOS](https://www.seabios.org/SeaBIOS)
|
||||
or [GNU GRUB](https://www.gnu.org/software/grub/) to boot your operating
|
||||
or [GRUB](https://www.gnu.org/software/grub/) to boot your operating
|
||||
system; on ARM(chromebooks), we provide *U-Boot* (as a coreboot payload).
|
||||
|
||||
Summarised list of changes
|
||||
|
|
@ -233,7 +233,7 @@ The changes are as follows:
|
|||
Canoeboot 20240612 already removed actual configs using `grubonly`, and we
|
||||
will no longer provide them in Canoeboot, so this feature in cbmk became
|
||||
legacy cruft that can simply be removed. The idea is simple: *safety first*.
|
||||
This has implications for [GRUB hardening](../docs/gnulinux/grub_hardening.md);
|
||||
This has implications for [GRUB hardening](../docs/linux/grub_hardening.md);
|
||||
you can insert the correct bootorder file, to once again disable SeaBIOS, but
|
||||
you must first verify that GRUB is stable. The GRUB hardening guide already
|
||||
documents how to do this.
|
||||
|
|
|
|||
|
|
@ -21,17 +21,17 @@ Introduction
|
|||
|
||||
Canoeboot is a free/libre BIOS/UEFI replacement on x86 and ARM, providing
|
||||
boot firmware that initialises the hardware in your computer, to then load an
|
||||
operating system (e.g. GNU+Linux). It is specifically
|
||||
operating system (e.g. Linux). It is specifically
|
||||
a *[coreboot distribution](../docs/maintain/)*,
|
||||
like how Debian is a GNU+Linux distribution. It provides an automated
|
||||
like how Debian is a Linux distribution. It provides an automated
|
||||
build system to produce coreboot ROM images with a variety of payloads such as
|
||||
GNU GRUB or SeaBIOS, with regular well-tested releases to make coreboot as easy
|
||||
GRUB or SeaBIOS, with regular well-tested releases to make coreboot as easy
|
||||
to use as possible for non-technical users. From a project management perspective,
|
||||
this works in *exactly* the same way as a GNU+Linux distro, providing a source-based
|
||||
this works in *exactly* the same way as a Linux distro, providing a source-based
|
||||
package manager (called cbmk) which patches sources and compiles coreboot images.
|
||||
It makes use of [coreboot](https://www.coreboot.org/) for hardware initialisation,
|
||||
and then a payload such as [SeaBIOS](https://www.seabios.org/SeaBIOS)
|
||||
or [GNU GRUB](https://www.gnu.org/software/grub/) to boot your operating
|
||||
or [GRUB](https://www.gnu.org/software/grub/) to boot your operating
|
||||
system; on ARM(chromebooks), we provide *U-Boot* (as a coreboot payload).
|
||||
|
||||
U-Boot UEFI payload on x86\_64
|
||||
|
|
@ -39,7 +39,7 @@ U-Boot UEFI payload on x86\_64
|
|||
|
||||
For Canoeboot 20241207, today's release, U-Boot is *also* provided as an
|
||||
optional coreboot payload on x86 machines. This provides a sensible UEFI
|
||||
implementation, useful for booting GNU+Linux and BSD systems more easily. More
|
||||
implementation, useful for booting Linux and BSD systems more easily. More
|
||||
information available on the [U-Boot x86 page](../docs/uboot/uboot-x86.md).
|
||||
|
||||
This means that you can have a UEFI boot environment, even on machines where
|
||||
|
|
|
|||
|
|
@ -21,17 +21,17 @@ Introduction
|
|||
|
||||
Canoeboot is a free/libre BIOS/UEFI replacement on x86 and ARM, providing
|
||||
boot firmware that initialises the hardware in your computer, to then load an
|
||||
operating system (e.g. GNU+Linux). It is specifically
|
||||
operating system (e.g. Linux). It is specifically
|
||||
a *[coreboot distribution](../docs/maintain/)*,
|
||||
like how Debian is a GNU+Linux distribution. It provides an automated
|
||||
like how Debian is a Linux distribution. It provides an automated
|
||||
build system to produce coreboot ROM images with a variety of payloads such as
|
||||
GNU GRUB or SeaBIOS, with regular well-tested releases to make coreboot as easy
|
||||
GRUB or SeaBIOS, with regular well-tested releases to make coreboot as easy
|
||||
to use as possible for non-technical users. From a project management perspective,
|
||||
this works in *exactly* the same way as a GNU+Linux distro, providing a source-based
|
||||
this works in *exactly* the same way as a Linux distro, providing a source-based
|
||||
package manager (called cbmk) which patches sources and compiles coreboot images.
|
||||
It makes use of [coreboot](https://www.coreboot.org/) for hardware initialisation,
|
||||
and then a payload such as [SeaBIOS](https://www.seabios.org/SeaBIOS)
|
||||
or [GNU GRUB](https://www.gnu.org/software/grub/) to boot your operating
|
||||
or [GRUB](https://www.gnu.org/software/grub/) to boot your operating
|
||||
system; on ARM(chromebooks), we provide *U-Boot* (as a coreboot payload).
|
||||
Experimental x86 U-Boot support is also available.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue