From a1f2f08764fb6974d868ccaa2ce1342bfec080d8 Mon Sep 17 00:00:00 2001 From: Pankaj Raghav Date: Sat, 11 Mar 2023 10:48:27 +0100 Subject: [PATCH] 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. --- Meta/run.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Meta/run.sh b/Meta/run.sh index 78795b0ff0..da3d69cd3f 100755 --- a/Meta/run.sh +++ b/Meta/run.sh @@ -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