Meta: Use the correct boot device addressing mode for NVMe devices
Commit: 2c84466ad8
("Kernel/Storage: Introduce new boot device
addressing modes") changed the way we pass the boot device parameter.
That commit missed updating boot parameter in the run.sh script for NVMe
boot devices.
This commit is contained in:
parent
f8b67e1596
commit
a1f2f08764
Notes:
sideshowbarker
2024-07-18 03:23:00 +09:00
Author: https://github.com/Panky-codes Commit: https://github.com/SerenityOS/serenity/commit/a1f2f08764 Pull-request: https://github.com/SerenityOS/serenity/pull/17805
1 changed files with 1 additions and 1 deletions
|
@ -223,7 +223,7 @@ else
|
|||
SERENITY_BOOT_DRIVE="-drive file=${SERENITY_DISK_IMAGE},format=raw,index=0,media=disk,if=none,id=disk"
|
||||
SERENITY_BOOT_DRIVE="$SERENITY_BOOT_DRIVE -device i82801b11-bridge,id=bridge4 -device sdhci-pci,bus=bridge4"
|
||||
SERENITY_BOOT_DRIVE="$SERENITY_BOOT_DRIVE -device nvme,serial=deadbeef,drive=disk,bus=bridge4,logical_block_size=4096,physical_block_size=4096"
|
||||
SERENITY_KERNEL_CMDLINE="$SERENITY_KERNEL_CMDLINE root=/dev/nvme0n1"
|
||||
SERENITY_KERNEL_CMDLINE="$SERENITY_KERNEL_CMDLINE root=nvme0:1:0"
|
||||
else
|
||||
SERENITY_BOOT_DRIVE="-drive file=${SERENITY_DISK_IMAGE},format=raw,index=0,media=disk,id=disk"
|
||||
fi
|
||||
|
|
Loading…
Add table
Reference in a new issue