Home Forums Software discussion Linux Kernel Environment variables for various boot scenarios

This topic contains 2 replies, has 2 voices, and was last updated by  akrog 2 months ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #596

    CaptainData
    Participant

    Can you please provide the boot parameter settings for the various boot scenarios?

    I built a kernel and have everything working and auto-booting, but I get errors from get_images. I have one ext4 filesystem. get_images uses fatload which produces two error messages when booting:

    get_images=mmc dev 0; fatload mmc 0 $kernel_addr $image_name; fatload mmc 0 $fdt_addr $fdt_name; run get_ramfs

    Marvell>> run get_images
    switch to partitions #0, OK
    mmc0 is current device
    ** Unrecognized filesystem type **
    ** Unrecognized filesystem type **
    Marvell>>

    What is the get_images string for booting the example “Ubuntu – Initial network configuration?”

    Also, what is the bootcmd for the example above?

    I had to change:
    bootcmd=run get_images; run set_bootargs;booti $kernel_addr $ramfs_addr $ftdt_addr
    to
    bootcmd=run get_images; run set_bootargs;run bootmmc

    How many of these these things have been sold? Why is the documentation so lacking?

    #635

    CaptainData
    Participant

    Should I just change:
    get_images=mmc dev 0; fatload mmc 0 $kernel_addr $image_name; fatload mmc 0 $fdt_addr $fdt_name; run get_ramfs
    to
    get_images=mmc dev 0; run get_ramfs
    ?

    #793

    akrog
    Keymaster

    Hi CaptainData,

    Try replacing fatload with ext4load if you have an EXT4 formatted partition. I cannot tell much from that one variable, so please post output of printenv command.

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.

Signup to our newsletter

Technical specification tables can not be displayed on mobile. Please view on desktop