Thank you for the response. A few questions, comments below (inline). ----- 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... >
I tried setting the architecture to arm64, but the build process cannot find linux-image-arm64. I checked manually and it doesn't exist in any of the repos currently configured in the C2's sources.list. > > > 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. > I added that in when I initially tried to set the KERNEL_ARCH parameter in the conf file to "c2". That correctly causes the build process to download and install kernel package linux-image-c2 from the deb.odroid.in/c2 repo. But that fails with some dependency errors. There appears to be some issue with the package kernel linux-image-c2, I can't even get it to install on the regular Ubuntu Mate desktop on the C2. Google indicates there some dependency issues with that package. I guess what really needs to happen is that the correct kernel package needs to be downloaded from the Odroid repos, but that's not happening (see next comment below). > > > 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? > I think not, or rather I think I'm pretty sure it doesn't support the C2. I am not very familiar yet with how LTSP works, so not sure how to get build-client script to download the correct kernel package. The latest build on the C2 runs kernel version 3.14.x. Whereas, as you can see above, the ltsp-build-client script is downloading and installing kernel version 4.4.x. Problem is, I don't know how to get the ltsp-build-client script to download the correct kernel version which I believe needs to come from the Odroid repos. > > > 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. > Would you be kind enough to tell me how to do that? Rather, what is the root device it's looking for? > > > 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. > Ok, clearly I have a lot of reading to do. I have no idea where the chroot's /etc/ is located. I thought the chroot was the location where the client image is built. If it is, how would I get there if the build never succeeded? > > 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! > I hear you, thanks. > > 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
