-
Notifications
You must be signed in to change notification settings - Fork 12
rootfs mount issue in polarfire icicle board as it always mounts initramfs with defult configuration #9
Comments
Provided the rootfs has been written to partition 3 & your kernel's CONFIG_CMDLINE contains "root=/dev/mmcblk0p3", |
Hi Conor, Thank you for the suggestions. Note: I am using 2021:11 tip diff --git a/conf/osbi-fit-image.its b/conf/osbi-fit-image.its
govind@govindws:~/work/polarfire/polarfire-soc-buildroot-sdk$ cat conf/icicle-kit-es/defconfig.append /dev/mmcblk0p3 on /media/govind/1f96c5cc-0ebc-42be-8267-4caa1b8e6ba5 type ext4 (rw,nosuid,nodev,relatime,uhelper=udisks2) govind@govindws:~/work/polarfire/polarfire-soc-buildroot-sdk$ ls /media/govind/1f96c5cc-0ebc-42be-8267-4caa1b8e6ba5/ [ 8.475195] VFS: Cannot open root device "mmcblk0p3" or unknown-block(0,0): error -6 |
Hey Govind!
IIUC, that should be |
I have modified the same as seen in kerel bootup logs [ 0.000000] Kernel command line: earlyprintk debug root=/dev/mmcblk0p3 uio_pdrv_genirq.of_id=generic-uio mount error is still seen and all partition are good and tested as mount point is HOST machine. [ 8.490926] VFS: Cannot open root device "mmcblk0p3" or unknown-block(0,0): error -6 |
Hello ,
I am using polarfire icicle board and using 2021:11 release because of some legacy reason.
I am seeing it always mounts initramfs instead of rootfs , which is available in part3, Is there any extra configuration required to mount rootfs instead of initramfs(which is packed in the FIT image @initramfs.cpio.gz").
Boot up log:
U-Boot 2021.10 (Nov 22 2022 - 15:56:12 +0400)
CPU: rv64imafdc
Model: Microchip PolarFire-SoC Icicle Kit
DRAM: 1.7 GiB
MMC: mmc@20008000: 0
Loading Environment from nowhere... OK
In: serial@20100000
Out: serial@20100000
Err: serial@20100000
Net: eth0: ethernet@20112000
Hit any key to stop autoboot: 0
474 bytes read in 16 ms (28.3 KiB/s)
Executing script at 90000000
73880412 bytes read in 3168 ms (22.2 MiB/s)
Loading kernel from FIT Image at 90000000 ...
Using 'conf-riscvpc.dtb' configuration
Trying 'vmlinux.bin' kernel subimage
Description: Linux kernel
Type: Kernel Image
Compression: uncompressed
Data Start: 0x900000d0
Data Size: 21968896 Bytes = 21 MiB
Architecture: RISC-V
OS: Linux
Load Address: 0x80200000
Entry Point: 0x80200000
Hash algo: sha256
Hash value: 6535b70280c1bd85b76e10333cd9178d17c74ef46088f82ad5309cd47b47c bde
Verifying Hash Integrity ... sha256+ OK
Loading ramdisk from FIT Image at 90000000 ...
Using 'conf-riscvpc.dtb' configuration
Trying 'initramfs.cpio.gz' ramdisk subimage
Description: buildroot initramfs
Type: RAMDisk Image
Compression: Unknown Compression
Data Start: 0x914f39d8
Data Size: 51896320 Bytes = 49.5 MiB
Architecture: RISC-V
OS: Linux
Load Address: 0x84000000
Entry Point: unavailable
Hash algo: sha256
Hash value: d4879fb35e85455563f80fef1bceee4feb20f386657730eccee256394ca8e 4da
Verifying Hash Integrity ... sha256+ OK
Loading ramdisk from 0x914f39d8 to 0x84000000
WARNING: 'compression' nodes for ramdisks are deprecated, please fix your .its file!
Loading fdt from FIT Image at 90000000 ...
Using 'conf-riscvpc.dtb' configuration
Trying 'riscvpc.dtb' fdt subimage
Description: Flattened Device Tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x94671abc
Data Size: 13098 Bytes = 12.8 KiB
Architecture: RISC-V
Load Address: 0x82200000
Hash algo: sha256
Hash value: b55d56a3afed47ba8a5d1b58ea738d0891b81967a38676fbfbfe40ae8f1059a5
Verifying Hash Integrity ... sha256+ OK
Loading fdt from 0x94671abc to 0x82200000
Booting using the fdt blob at 0x82200000
Loading Kernel Image
Loading Ramdisk to 8ce82000, end 90000000 ... OK
Loading Device Tree to 000000008ce7b000, end 000000008ce81329 ... OK
Loading Device Tree to 000000008ce71000, end 000000008ce7a329 ... OK
Starting kernel ...
[ 0.000000] Linux version 5.12.19-03920-ged4fb5b0bc51-dirty (govind@govindws) (riscv64-unknown-linux-gnu-gcc (GCC) 10.2.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP Tue Nov 22 15:56:43 +04 2022
The text was updated successfully, but these errors were encountered: