Red Bear OS
f2fbf7ad83
40_drivers.target referenced only pcid-spawner-initfs, so the initfs driver-manager service (staged, gated, with its storage TOML and the binary already copied into initfs/bin) never entered the boot graph. The target now lists driver-manager-initfs first and keeps pcid-spawner-initfs as the gated fallback — the initfs cutover is complete. Also correct the initfs-storage.toml header comment (the content is driver-manager format).
44 lines
763 B
TOML
44 lines
763 B
TOML
## Storage drivers for InitFS (driver-manager format) ##
|
|
|
|
[[driver]]
|
|
name = "ahcid"
|
|
description = "AHCI SATA driver"
|
|
priority = 100
|
|
command = ["/scheme/initfs/lib/drivers/ahcid"]
|
|
|
|
[[driver.match]]
|
|
class = 1
|
|
subclass = 6
|
|
|
|
[[driver]]
|
|
name = "ided"
|
|
description = "PATA IDE driver"
|
|
priority = 100
|
|
command = ["/scheme/initfs/lib/drivers/ided"]
|
|
|
|
[[driver.match]]
|
|
class = 1
|
|
subclass = 1
|
|
|
|
[[driver]]
|
|
name = "nvmed"
|
|
description = "NVMe storage driver"
|
|
priority = 100
|
|
command = ["/scheme/initfs/lib/drivers/nvmed"]
|
|
|
|
[[driver.match]]
|
|
class = 1
|
|
subclass = 8
|
|
|
|
[[driver]]
|
|
name = "virtio-blkd"
|
|
description = "VirtIO block device driver"
|
|
priority = 100
|
|
command = ["/scheme/initfs/lib/drivers/virtio-blkd"]
|
|
|
|
[[driver.match]]
|
|
vendor = 0x1AF4
|
|
device = 0x1001
|
|
class = 1
|
|
subclass = 0
|