I tried setting the KERNEL_ARCH to 3.14.79-109 (the current kernel running on the C2). The ltsp-build-client gets to the point where it starts installing the kernel and throws the following error:
Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: kernel-common Suggested packages: kernel-package fdutils linux-doc-3.14.79-109 | linux-source-3.14.79-109 linux-image-3.14.79-109-dbg linux-manual-3.14.79-109 The following NEW packages will be installed: kernel-common linux-image-3.14.79-109 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 24.6 kB/16.6 MB of archives. After this operation, 58.7 MB of additional disk space will be used. WARNING: The following packages cannot be authenticated! linux-image-3.14.79-109 Authentication warning overridden. Get:1 http://ports.ubuntu.com/ubuntu-ports xenial/universe arm64 kernel-common all 13.018 [24.6 kB] Fetched 24.6 kB in 0s (32.4 kB/s) Preconfiguring packages ... Selecting previously unselected package linux-image-3.14.79-109. (Reading database ... 33803 files and directories currently installed.) Preparing to unpack .../linux-image-3.14.79-109_20170316_arm64.deb ... Done. Unpacking linux-image-3.14.79-109 (20170316) ... Selecting previously unselected package kernel-common. Preparing to unpack .../kernel-common_13.018_all.deb ... Unpacking kernel-common (13.018) ... Processing triggers for man-db (2.7.5-1) ... Setting up linux-image-3.14.79-109 (20170316) ... Hmm. There is a symbolic link /lib/modules/3.14.79-109/build However, I can not read it: No such file or directory Therefore, I am deleting /lib/modules/3.14.79-109/build Hmm. The package shipped with a symbolic link /lib/modules/3.14.79-109/source However, I can not read the target: No such file or directory Therefore, I am deleting /lib/modules/3.14.79-109/source Running depmod. Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/Image 3.14.79-109 /boot/vmlinuz-3.14.79-109 run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.14.79-109 /boot/vmlinuz-3.14.79-109 run-parts: executing /etc/kernel/postinst.d/copy_dtb 3.14.79-109 /boot/vmlinuz-3.14.79-109 run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.14.79-109 /boot/vmlinuz-3.14.79-109 update-initramfs: Generating /boot/initrd.img-3.14.79-109 run-parts: executing /etc/kernel/postinst.d/ltsp-update-kernels 3.14.79-109 /boot/vmlinuz-3.14.79-109 run-parts: executing /etc/kernel/postinst.d/uInitrd 3.14.79-109 /boot/vmlinuz-3.14.79-109 /etc/kernel/postinst.d/uInitrd: 25: /etc/kernel/postinst.d/uInitrd: mkimage: not found run-parts: /etc/kernel/postinst.d/uInitrd exited with return code 127 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-3.14.79-109.postinst line 391. dpkg: error processing package linux-image-3.14.79-109 (--configure): subprocess installed post-installation script returned error exit status 2 Setting up kernel-common (13.018) ... Errors were encountered while processing: linux-image-3.14.79-109 E: Sub-process /usr/bin/dpkg returned an error code (1) error: LTSP client installation ended abnormally ----- Original Message ----- > From: "Vagrant Cascadian" <vagr...@debian.org> > To: ltsp-discuss@lists.sourceforge.net > Sent: Sunday, March 19, 2017 10:51:21 AM > Subject: Re: [Ltsp-discuss] Ubuntu LTSP for ODROID-C2 fails > > 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 > > ------------------------------------------------------------------------------ > 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 > ------------------------------------------------------------------------------ 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
