Go to file
2020-08-26 22:49:19 +02:00
src Better firmware compatibility. (#19) 2020-08-26 22:45:32 +02:00
test Tagging stivale (#16) 2020-08-11 17:43:39 +02:00
toolchain Force IPV4 in toolchain script (#18) 2020-08-26 02:25:18 +02:00
.gitignore EXT2 and VFS support (#5) 2020-04-15 08:48:35 +02:00
bochsrc Initial linux protocol support 2020-04-19 10:14:49 +02:00
CONFIG.md Add support for chainloading another bootsector 2020-05-13 18:13:17 +02:00
LICENSE.md Update copyright notice 2020-05-31 05:18:04 +02:00
Makefile Add memory clobbers where missing and remove useless stivale signature 2020-07-24 15:38:55 +02:00
qloader2-install Make qloader2-install less verbose 2020-04-21 15:12:00 +02:00
qloader2-install.c Fix fat32 bug 2020-07-02 02:31:27 +02:00
qloader2.bin Update binary image 2020-08-26 22:49:19 +02:00
README.md Mark the partition as bootable (#17) 2020-08-26 01:21:06 +02:00
screenshot.png Add reference screenshot 2020-08-05 00:08:40 +02:00
STIVALE2.md Update STIVALE2.md 2020-08-11 18:10:38 +02:00
STIVALE.md Restore old stivale specification and move stivale2 spec to own file 2020-08-11 17:53:37 +02:00

qloader2

x86/x86_64 BIOS Bootloader

Reference screenshot

Supported boot protocols

  • Linux
  • stivale (qloader2's native boot protocol, see STIVALE.md for details)
  • TempleOS

Supported filesystems

  • ext2
  • echfs
  • FAT32

Supported partitioning schemes

  • MBR
  • GPT

How to use

This repository contains a prebuilt version of qloader2 so building it won't be necessary.

In order to install qloader2 on a MBR device (which can just be a raw image file), run the provided qloader2-install script as such:

./qloader2-install ./qloader2.bin <path to device/image>

If using a GPT formatted device, it will be necessary to create an extra partition (of at least 32K in size) to store stage 2 code. Then it will be necessary to tell the install script where this partition is located by specifying the start sector.

fdisk <device>    # Create bootloader partition using your favourite method
./qloader2-install ./qloader2.bin <path to device/image> <start sector of boot partition>

Then make sure the device/image contains at least 1 partition formatted in a supported filesystem containing a /qloader2.cfg or /boot/qloader2.cfg file and the kernel/modules one wants to load.

An example qloader2.cfg file can be found in test/qloader2.cfg.

More info on the format of qloader2.cfg can be found in CONFIG.md.

For example, to create an empty image file of 64MiB in size, 1 echfs partition on the image spanning the whole device, format it, copy the relevant files over, and install qloader2, one can do:

dd if=/dev/zero bs=1M count=0 seek=64 of=test.img
parted -s test.img mklabel msdos
parted -s test.img mkpart primary 1 100%
parted -s test.img set 1 boot on # Workaround for buggy BIOSes

echfs-utils -m -p0 test.img quick-format 32768
echfs-utils -m -p0 test.img import path/to/qloader2.cfg qloader2.cfg
echfs-utils -m -p0 test.img import path/to/kernel.elf kernel.elf
echfs-utils -m -p0 test.img import <path to file> <path in image>
...
./qloader2-install $THIS_REPO/qloader2.bin test.img

One can get echfs-utils by installing https://github.com/qword-os/echfs.

Building from source

In order to hack qloader2, one must build the GCC toolchain from source first.

To do so, run the make_toolchain.sh script from within the toolchain directory; keep in mind that the script takes MAKEFLAGS as an argument.

cd toolchain
./make_toolchain.sh -j4

After that is done, simply run make in the root of the repo to generate src/qloader2.bin.

Discord server

We have a Discord server if you need support, info, or you just want to hang out: https://discord.gg/QEeZMz4