boonxiong2
1c99c77b3f
There were three independent reasons a fresh build produced an image that
OVMF would not boot. All three are fixed here; verified by booting the
resulting ISO/deshab-dev.img under QEMU/OVMF through to FirstInit.
1. ESP rejected by OVMF (CODE/linux/pack_system_image.sh)
The vfat formatter was invoked with an explicit -s 8, forcing 4KiB clusters.
On the 256MiB ESP that yields exactly 65535 clusters - the FAT32 0xFFF5
boundary - and OVMF's FatPkg refuses to mount the volume. Symptom: BdsDxe
logs "failed to load ... Not Found", the ESP shows up as BLKn with no FS in
the UEFI Shell, and the firmware falls through to the internal shell.
The sidecar FAT32 image (make_sata_sidecar.sh) mounts fine because it calls
the formatter without -s. Drop -s here too and let the tool pick geometry.
Do NOT add -f 1: OVMF mounts nfat=1 and nfat=2 alike, it was not the cause.
2. Limine dropped into a panic (CODE/linux/pack_system_image.sh)
limine.conf declares the Linux-compat guest modules. build.sh uncomments
them once Linux has been built, but nothing ever comments them back, so the
file says "load boot():/boot/linux-initrd.img" while only linux-bzImage
exists on disk - Limine panics on the missing module and never reaches the
kernel. Filter the guest module_path lines against SYSTEM/boot/ at pack
time and write the result to the ESP. Both the root /limine.conf and
/limine/limine.conf are written, since Limine 10 prefers the latter. The
tracked source file is left untouched.
3. Nine drivers were never compiled (build.ps1)
Commit 055c521 untracked the .drv binaries on the grounds that they are
regenerable, but build.ps1 only ever invoked Build-DkmDriver for 8 of the
17 drivers listed in manifest.json. timer/acpi/pci/ahci/bootfs/vfs/fat32/
devfs/ps2kbd had sources under CODE/DKM/ and no build step, so the image
shipped without them and Limine failed on the first one. Add the missing
compile steps, grouped by load stage. All 17 now match manifest.json.
Also in this commit (environment/tooling hygiene):
- check_env.sh: stop hardcoding /mnt/d/Code/Deshab (the original author's
machine); derive the repo root from the script's own location. It was
reporting a bogus "wsl_mount" failure on every other checkout and sending
people to install packages that were already present. Also check and
advertise the image-packing tools (dosfstools/e2fsprogs/fdisk/rsync), which
were missing from the dependency list even though pack_system_image.sh
hard-requires them.
- build_initrd.sh: same hardcoded-path fix.
- README.md: relative path instead of the stale absolute one.
Verified: ./build.bat -Variant dev under WSL2/Ubuntu, then QEMU/OVMF boots
through BdsDxe -> Limine -> UTSM -> DKM (17/17) -> DSK -> FirstInit, with the
PS/2 mouse initialising cleanly.
Deshab-OS
实验内核 · QEMU 可启动演示 · 非生产系统
Deshab-OS 是一个从零编写的独立 64 位操作系统，基于 x86_64 long mode，采用单地址空间 Ring0（SAS-R0）内核架构，配套封缄内存（UTSM）、专用恢复根（DRR）与可加载驱动模块系统（DKM）。
当前已完成可启动的实验内核闭环：Limine 引导 → UTSM 首阶段内核 → 14 个 DKM 驱动加载 → DSK 主内核 → 桌面/登录/向导。
项目特质
Deshab 的灵魂是自相矛盾：一边封圣一边爆粗，一边敞开门一边焊死锁——疯的是姿态，稳的是时序。
- 疯但好使。 提交历史像涂鸦墙，但
run_qemu.bat一下，莲花确实开了。每个里程碑必须有 QEMU 证据，疯要有画面证据。 - 毛坯神殿，不是赛博保险柜。 SAS-R0 单地址空间 Ring0——没有隔断的机房，每面墙上写着"此处无墙"。自由是默认值：用户代码即内核代码，想改就改；卡了按时光键（DRR 回滚）。
- 仪式感是功能。 给空气上锁（UTSM 封缄）不是因为有人窥探，是因为喜欢咔哒声——所以它必须是可开关的旋钮（
@sealed可选标记），而不是强加的道袍。崩溃也要崩出莲花（DEAICUP 莲花崩溃屏）。 - 诚实比体面重要。 不假装安全，只声明边界；不假装完成，只标⬜。状态唯一来源是 STATUS.md，每个 ✅ 都带证据路径，⬜ 是坦白不是路线装饰。
- 错也错得有章法。 0bug 不靠形式化验证，靠 B0-B4 启动契约、分级自检（F4）、看门狗与 A/B checkpoint 回滚兜底。
完整宣言与三条箴言见 docs/PHILOSOPHY.md。
核心架构
SAS-R0-PCQ 单地址空间 Ring0 + Per-CPU O(1) 位图调度器（当前 BSP-only）
UTSM UUID 调谐封缄内存（明文须经 UTRW 读写器）
UTRW 带标记读写器（Fast/Slow Path ✅，RFC 8439 KAT 对拍）
DRR 专用恢复根（看门狗 / checkpoint / A-B 回滚 / 独立 Emergency Pool）
DKM 驱动模块系统（ELF64 .drv ABI，4 stage 分阶段加载）
项目状态
唯一状态源见 docs/STATUS.md，本表只是引用摘要。
| 子系统 | 状态 |
|---|---|
| 早期启动 / IRQ / DMA / DKM 14 驱动 | ✅ |
| UTSM 封缄（Fast/Slow Path + RFC 8439 KAT + @sealed 旋钮） | ✅ |
| AHCI / e1000 / FAT32 写盘 | ✅ |
| NVMe / virtio-net / FAT32 完整路径 | 🔶 |
| PCQ 调度器 / DRR 恢复根 | ✅（BSP-only / 演示级） |
| 五期填补计划进度 | 一期二期全勾，见 docs/TASKBOARD.md |
已知边界（Non-Goals）
- 无进程隔离：SAS-R0 单地址空间 Ring0，驱动 bug = 内核全盘崩。这不是安全 OS，是敞开工坊。
- UTSM 仅 selftest 覆盖：封缄是"设计意图 + 演示级实现"，不是机密计算。
- 驱动为演示级：QEMU 能演示 ≠ 真机可依赖；NVMe/virtio-net 尚未走完数据路径。
文档
| 文档 | 内容 |
|---|---|
| STATUS.md | 单一状态源（全子系统三色表 + 证据） |
| ROADMAP_INSANE.md | 五期填补计划（F/U/D/R/E 唯一任务编号） |
| TASKBOARD.md | 可勾选任务表 |
| PHILOSOPHY.md | 疯圣典：矛盾美学与「疯但好使」物理学 |
| ARCHITECTURE.md | 架构设计 + 非目标章 |
| BOOT_SEQUENCE.md | B0-B4 五阶段启动序列（演示版） |
| ROADMAP.md | Phase 0-9 历史存档 + 用户态主线 |
| CONTRIBUTING.md | 开发环境、代码规范、Git 工作流 |
| CLAUDE.md | 项目当前状态与下一阶段路线 |
| LESSONS_LEARNED.md | 开发经验与教训 |
构建
Windows 走
build.bat；Linux/macOS 用根目录 Makefile（make dev|release|realtest，打包需 mkfs.vfat/mkfs.ext4）。
# Windows：LLVM Clang + ld.lld + Python/Pillow + QEMU + WSL(mkfs)
.\build.bat # 构建 utsm.elf + deshab.elf + 14 个 .drv + ISO/deshab.img
.\build.bat -Variant dev # 开发者模式（自动跑 shell 测试，调试全开）
.\build.bat -Variant release # 发布版（进桌面+登录）
.\ISO\run_qemu.bat # QEMU UEFI 启动验证（串口输出到 stdio）
# Linux / macOS（F3 跨平台构建）
make dev # 等价 build.bat -Variant dev
make both # dev + release
"Deshab 不假装安全，只声明边界；不假装完成，只标⬜。" 🪷