97 lines
4.8 KiB
Nix
97 lines
4.8 KiB
Nix
{ pkgs, ... }:
|
|
let
|
|
dmesg = "${pkgs.util-linux}/bin/dmesg";
|
|
grep = "${pkgs.gnugrep}/bin/grep";
|
|
modprobe = "${pkgs.kmod}/bin/modprobe";
|
|
ensureHWReady = ''
|
|
# common boot failure:
|
|
# blank screen (no backlight even), with the following log:
|
|
# ```syslog
|
|
# sun8i-dw-hdmi 1ee0000.hdmi: Couldn't get the HDMI PHY
|
|
# ...
|
|
# sun4i-drm display-engine: Couldn't bind all pipelines components
|
|
# ...
|
|
# sun8i-dw-hdmi: probe of 1ee0000.hdmi failed with error -17
|
|
# ```
|
|
#
|
|
# in particular, that `probe ... failed` occurs *only* on failed boots
|
|
# (the other messages might sometimes occur even on successful runs?)
|
|
#
|
|
# reloading the sun8i hdmi driver usually gets the screen on, showing boot text.
|
|
# then restarting display-manager.service gets us to the login.
|
|
#
|
|
# NB: the above log is default level. though less specific, there's a `err` level message that also signals this:
|
|
# sun4i-drm display-engine: failed to bind 1ee0000.hdmi (ops sun8i_dw_hdmi_ops [sun8i_drm_hdmi]): -17
|
|
# NB: this is the most common, but not the only, failure mode for `display-manager`.
|
|
# another error seems characterized by these dmesg logs, in which reprobing sun8i_drm_hdmi does not fix:
|
|
# ```syslog
|
|
# sun6i-mipi-dsi 1ca0000.dsi: Couldn't get the MIPI D-PHY
|
|
# sun4i-drm display-engine: Couldn't bind all pipelines components
|
|
# sun6i-mipi-dsi 1ca0000.dsi: Couldn't register our component
|
|
# ```
|
|
|
|
if (${dmesg} --kernel --level err --color=never --notime | ${grep} -q 'sun4i-drm display-engine: failed to bind 1ee0000.hdmi')
|
|
then
|
|
echo "reprobing sun8i_drm_hdmi"
|
|
# if a command here fails it errors the whole service, so prefer to log instead
|
|
${modprobe} -r sun8i_drm_hdmi || echo "failed to unload sun8i_drm_hdmi"
|
|
${modprobe} sun8i_drm_hdmi || echo "failed to load sub8i_drm_hdmi"
|
|
fi
|
|
'';
|
|
in
|
|
{
|
|
# kernel compatibility (2024/05/21: ea8eaaa91ad0b5a1716e69aad65d61e7cb2e7353)
|
|
# - linux-megous: boots to ssh, desktop
|
|
# - linux-postmarketos: boots to ssh, no graphics
|
|
# boot.kernelPackages = pkgs.linuxPackagesFor pkgs.linux-postmarketos;
|
|
boot.kernelPackages = pkgs.linuxPackagesFor pkgs.linux-megous;
|
|
# boot.kernelPackages = pkgs.linuxPackagesFor pkgs.linux-manjaro;
|
|
# boot.kernelPackages = pkgs.linuxPackagesFor pkgs.linux_latest;
|
|
|
|
# nixpkgs.hostPlatform.linux-kernel becomes stdenv.hostPlatform.linux-kernel
|
|
nixpkgs.hostPlatform.linux-kernel = {
|
|
# defaults:
|
|
name = "aarch64-multiplatform";
|
|
# baseConfig: defaults to "defconfig";
|
|
# baseConfig = "pinephone_defconfig"; #< N.B.: ignored by `pkgs.linux-megous`
|
|
DTB = true; #< DTB: compile device tree blobs
|
|
# autoModules (default: true): for config options not manually specified, answer `m` to anything which supports it.
|
|
# - this effectively builds EVERY MODULE SUPPORTED.
|
|
autoModules = true; #< N.B.: ignored by `pkgs.linux-megous`
|
|
# preferBuiltin (default: false; true for rpi): for config options which default to `Y` upstream, build them as `Y` (overriding `autoModules`)
|
|
# preferBuiltin = false;
|
|
|
|
# build a compressed kernel image: without this i run out of /boot space in < 10 generations
|
|
# target = "Image"; # <-- default
|
|
target = "Image.gz"; # <-- compress the kernel image
|
|
# target = "zImage"; # <-- confuses other parts of nixos :-(
|
|
};
|
|
|
|
# disable proximity sensor.
|
|
# the filtering/calibration is bad that it causes the screen to go fully dark at times.
|
|
# boot.blacklistedKernelModules = [ "stk3310" ];
|
|
|
|
boot.kernelParams = [
|
|
# without this some GUI apps fail: `DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory`
|
|
# this is because they can't allocate enough video ram.
|
|
# see related nixpkgs issue: <https://github.com/NixOS/nixpkgs/issues/260222>
|
|
# TODO(2023/12/03): remove once mesa 23.3.1 lands: <https://github.com/NixOS/nixpkgs/pull/265740>
|
|
#
|
|
# the default CMA seems to be 32M.
|
|
# i was running fine with 256MB from 2022/07-ish through 2022/12-ish, but then the phone quit reliably coming back from sleep (phosh): maybe a memory leak?
|
|
# bumped to 512M on 2023/01
|
|
# bumped to 1536M on 2024/05
|
|
# `cat /proc/meminfo` to see CmaTotal/CmaFree if interested in tuning this.
|
|
# kernel param mentioned here: <https://cateee.net/lkddb/web-lkddb/CMA_SIZE_PERCENTAGE.html>
|
|
# i think cma mem isn't exclusive -- it can be used as ordinary `malloc`, still. i heard someone suggest the OS default should just be 50% memory to CMA.
|
|
"cma=1536M"
|
|
# 2023/10/20: potential fix for the lima (GPU) timeout bugs:
|
|
# - <https://gitlab.com/postmarketOS/pmaports/-/issues/805#note_890467824>
|
|
"lima.sched_timeout_ms=2000"
|
|
];
|
|
|
|
# services.xserver.displayManager.job.preStart = ensureHWReady;
|
|
# systemd.services.greetd.preStart = ensureHWReady;
|
|
systemd.services.unl0kr.preStart = ensureHWReady;
|
|
}
|