Dustin C. Hatch 0caf50f656 xinit: Start Xorg on tty1
Because `tty1` is active when `xinit@user.service` starts on `tty7`,
Xorg cannot bind the modesetting driver to the DRM device:

> (II) systemd-logind: got fd for /dev/dri/card2 226:2 fd 13 paused 1
> (EE) Error systemd-logind returned paused fd for drm node

To fix this, we need to start Xorg on the active console.

Another potential fix would be to run `chvt 7` before running `startx`,
but running the GUI on tty1 seems to be what the major display managers,
e.g. GDM, are doing now.
2022-12-13 11:44:16 -06:00
2022-12-01 20:40:27 -06:00
2022-12-13 11:44:16 -06:00
2022-12-01 20:03:33 -06:00
2022-04-04 20:59:32 -05:00
2022-04-04 20:59:34 -05:00
2022-04-06 17:35:56 -05:00
2022-04-04 20:59:32 -05:00
2022-12-13 10:01:07 -06:00
2022-04-04 20:59:32 -05:00
2022-04-04 20:59:32 -05:00
2022-04-04 20:59:32 -05:00

Basement Hud Network-Booted OS

Customized Fedora-based operating system distributed as an immutable root filesystem image.

Building

Must run on a Fedora host or privileged container.

Build the root filesystem image:

make rootfs

This will create an _build/rootfs directory containing the root filesystem hierarchy. The _build/rootfs/boot directory contains the necessary files to boot the system:

  • efi: This directory contains the Raspberry Pi firmware files
  • initramfs.img: Early userspace image
  • vmlinuz: Kernel image
  • basementhud.squashfs: Root filesystem image

The Raspberry Pi firmware, initramfs image, and kernel image files must be served by a TFTP, while the rootfs image is served by NBD.

Build the initramfs image:

make initramfs
Description
No description provided
Readme 382 KiB
Languages
Shell 89%
Dockerfile 5.7%
Makefile 5.3%