Home Forums Getting Started Can someone make a better guide for Ubuntu?

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
  • #478

    I spent most of my weekend trying to go beyond the Marvell prompt and 3 SD cards and 1 USB stick didn’t work.

    Can some one write up a better guide or give me the bullets and I can make it for everyone else.

    On a side note, when will be BSD supported? I am targeting to install pfsense and give them out to family members.



    The guide that’s up now wants you to format a SD card with a single ext4 partition, but the default u-boot environment is set up for (and works automatically!) if you have a SD card with:
    – The first partition being a FAT32 partition, on which you put Image and the dtb.
    – The second partition being an ext4 with your root filesystem.


    Then (assuming that your SD card reader enumerates the card as /dev/sde as it did on my machine)
    – Use cfdisk and create a smallish (100M is more than enough) FAT32 partition, then allocate the rest to be Linux.
    sudo mkfs.vfat /dev/sde1
    sudo mkfs.ext4 /dev/sde2
    sudo mkdir -p /mnt/sde1 /mnt/sde2 /mnt/iso
    sudo mount /dev/sde1 /mnt/sde1
    sudo mount /dev/sde2 /mnt/sde2
    sudo mount -o loop ubuntu-16.04.2-server-arm64.iso /mnt/iso
    sudo unsquashfs -f -d /mnt/sde2 /mnt/iso/install/filesystem.squashfs
    You should apply the fixups that the wiki recommends:
    edit /mnt/sde2/etc/passwd and remove the x in in root:x:0:0:root:/root:/bin/bash so root can log in.
    edit /mnt/sde2/etc/securetty and add ttyMV0
    unzip kernel.zip
    sudo mv kernel/armada-3720-community.dtb /mnt/sde1
    sudo mv kernel/Image /mnt/sde1
    sudo umount /dev/sde1
    sudo umount /dev/sde2

    At this point, you should be able to insert the SD card into your EspressoBin and it should Just Work with the default environment.
    If you’ve mucked around with it, you’ll need to reset it. At the u-boot prompt (‘Marvell>>‘)
    setenv bootcmd 'run get_images; run set_bootargs; booti $kernel_addr $ramfs_addr $fdt_addr'

    You should also be aware of this kernel panic issue that you’ll hit with the Ubuntu image: http://espressobin.net/forums/topic/crash-after-booting-for-about-a-minute/



    Thanks for all the information, very informative. Quick question about your last statement, if you mucked around with it. Is that the process to reset it back to default or to set it for the new card created above?




    That’s to reset it back to what mine shipped with. The salient bits are:
    setenv bootcmd 'run get_images; run set_bootargs; booti $kernel_addr $ramfs_addr $fdt_addr'
    setenv get_images 'mmc dev 0; fatload mmc 0 $kernel_addr $image_name; fatload mmc 0 $fdt_addr $fdt_name; run get_ramfs'
    setenv get_ramfs 'if test "${ramfs_name}" != "-"; then setenv ramfs_addr 0x3000000; tftp $ramfs_addr $ramfs_name; else setenv ramfs_addr -;fi'
    setenv fdt_name 'armada-3720-community.dtb'
    setenv image_name 'Image'
    setenv root 'root=/dev/mmcblk0p2 rw'

    You’d think that the way to get to defaults would be env default -a, but that actually went and changed a bunch of other things on me that I wasn’t expecting: It reset my ethaddr, changed the fdt_name to fdt.dtb, and my get_images to tftp $kernel_addr $image_name; tftp $fdt_addr $fdt_name; run get_ramfs… so the defaults that are cooked into u-boot aren’t actually what I had in my out-of-the-box configuration.

    (My u-boot version is U-Boot 2015.01-armada-17.02.0-g48dc978 (May 18 2017 - 17:28:01))


    Yo da man! You made it easy, all I had to do is find the equivalent for the OSX.

    Any idea how I can install additional packages for Ubuntu Server 16? Apt-get just moans that a lot of dependencies are missing…



    thanks for the information


    great information, thanks

Viewing 7 posts - 1 through 7 (of 7 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