On 2017-03-19, Prince Jeremy wrote: > I have setup an Ubuntu server with LTSP server packages installed. Now > I am trying to build a client for an Odroid-C2 board (ARM). I execute > the following command from the Odroid-C2 running Ubuntu Mate 16.04.2 > LTS: > > $ ltsp-build-client --arch=armhf --config /etc/ltsp/ltsp-build-client-c2.conf
Odroid-C2 is actually an arm64 platform, which should be backwards-compatible with armhf, but may require a different kernel from the arm64 repositories... > where /etc/ltsp/ltsp-build-client-c2.conf contains the following: > > MOUNT_PACKAGES_DIR="/var/cache/apt/archives" > EXTRA_MIRROR="http://deb.odroid.in/c2 xenial main" What packages are you pulling from this repository? You might also have better luck trying the ltsp-pnp method, to build the client images out of the server install. > The build process gets to the point where it attempts to install the package > linux-image-generic_4.4.0-66.70_armhf.deb. It gets to the line: > > update-initramfs: Generating /boot/initrd.img-4.4.0-66-generic Does this kernel have support for Odroid-C2? Fairly complete Odroid-C2 support wasn't added in linux upstream around 4.9 or 4.10, as I recall. Is that the version in Ubuntu, or pulled from the odroid repository? > and then throws the warning: > > Warning: root device does not exist. As long as you specify a root device on the commandline, this shouldn't be a problem. > Unable to abort; system will probably be broken! > > The process then continues to flash-kernel and gets to the point > > Processing triggers for flash-kernel (3.0-rc.4ubuntu62.2) ... > Unsupported platform. This is because flash-kernel doesn't have information about what to do with this device. You'll need to add a stanza to your chroot's /etc/flash-kernel/db something like this: Machine: Hardkernel Odroid XU4 Kernel-Flavors: armmp armmp-lpae DTB-Id: exynos5422-odroidxu4.dtb Boot-Script-Path: /boot/boot.scr U-Boot-Script-Name: bootscr.uboot-generic Required-Packages: u-boot-tools This example is obviously for the odroid-XU4; you'll have to adjust the machine, kernel-flavors and DTB entry for your board appropriately. Alternately, you could probably remove flash-kernel entirely, and just ensure the appropriate .dtb file is available in the chroot's /boot/dtbs/$version/, and configure pxelinux.cfg/default-arm appropriately. I think I added some support for network booting arm boards to ltsp-update-kernels/update-kernels, but it's been a while and it could probably use some updates... You've got a fairly rough road ahead; good luck! live well, vagrant
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
