[Ltsp-discuss] Ubuntu LTSP for RaspBerry2 fails

[Prince Jeremy]

I am dealing with the


warning: root device does not exist
unable to abort; system will probably be broken!

error as well. Any updates on this?


thanks.

[Prince Jeremy]

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

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"

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

and then throws the warning:

Warning: root device   does not exist.

(The space between "device" and "does" above is intentional).

Then,

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.
dpkg: error processing package flash-kernel (--configure):
  subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
  flash-kernel
E: Sub-process /usr/bin/dpkg returned an error code (1)
error: LTSP client installation ended abnormally

I would appreciate it if someone can point in the right direction.

thanks -Billy

[Vagrant Cascadian]

Post by Prince Jeremy
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
$ 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...

Post by Prince Jeremy
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.

Post by Prince Jeremy
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?

Post by Prince Jeremy
Warning: root device   does not exist.

As long as you specify a root device on the commandline, this shouldn't
be a problem.

Post by Prince Jeremy
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

[Russell Ekerete]

Hi

Had a similar issue building LTSP for RPI3 using Lubuntu, Xubuntu and
Ubuntu Mate 16.04 and the flash-kernel. I could go into the technical
details but in the end I had to move up to 16.10 before I overcame the
problem. Put simply it seems its an issue with the 16.04 versions of
flash-kernel.

Try building with 16.10 (and yes I know its not LTS) and see.

Regards,

Russell

Post by Prince Jeremy
$ ltsp-build-client --arch=armhf --config /etc/ltsp/ltsp-build-client-c2.conf
MOUNT_PACKAGES_DIR="/var/cache/apt/archives"
EXTRA_MIRROR="http://deb.odroid.in/c2 xenial main"
update-initramfs: Generating /boot/initrd.img-4.4.0-66-generic
Warning: root device does not exist.
(The space between "device" and "does" above is intentional).
Then,
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.
subprocess installed post-installation script returned error exit status 1
flash-kernel
E: Sub-process /usr/bin/dpkg returned an error code (1)
error: LTSP client installation ended abnormally
I would appreciate it if someone can point in the right direction.
thanks -Billy
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_____________________________________________________________________
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net

[Prince Jeremy]

Thank you for the response. A few questions, comments below (inline).

----- Original Message -----

Sent: Sunday, March 19, 2017 10:51:21 AM
Subject: Re: [Ltsp-discuss] Ubuntu LTSP for ODROID-C2 fails

Post by Prince Jeremy
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
$ 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.

Post by Prince Jeremy
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).

Post by Prince Jeremy
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
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.

Post by Prince Jeremy
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?

Post by Prince Jeremy
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
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
_____________________________________________________________________
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net

[Prince Jeremy]

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 -----

Sent: Sunday, March 19, 2017 10:51:21 AM
Subject: Re: [Ltsp-discuss] Ubuntu LTSP for ODROID-C2 fails

Post by Prince Jeremy
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
$ 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...

Post by Prince Jeremy
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.

Post by Prince Jeremy
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
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?

Post by Prince Jeremy
Warning: root device   does not exist.

As long as you specify a root device on the commandline, this
shouldn't
be a problem.

Post by Prince Jeremy
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
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
_____________________________________________________________________
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net

[Prince Jeremy]

Russell,

Thanks for that info. At least now I know it wasn't anything with the steps I was following. Unfortunately, Hardkernel hasn't released an Ubuntu 16.10 build for the Odroid-C2. So I guess I'm stuck waiting for them. In the meantime, I will try to get an arm64 build from the official Ubuntu repos and see if that works.

Cheers -Billy

----- Original Message -----

Sent: Wednesday, March 29, 2017 1:22:35 AM
Subject: Re: [Ltsp-discuss] Ubuntu LTSP for ODROID-C2 fails
Hi
Had a similar issue building LTSP for RPI3 using Lubuntu, Xubuntu and
Ubuntu Mate 16.04 and the flash-kernel. I could go into the
technical details but in the end I had to move up to 16.10 before I
overcame the problem. Put simply it seems its an issue with the
16.04 versions of flash-kernel.
Try building with 16.10 (and yes I know its not LTS) and see.
Regards,
Russell
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
$ ltsp-build-client --arch=armhf --config
/etc/ltsp/ltsp-build-client-c2.conf
MOUNT_PACKAGES_DIR="/var/cache/apt/archives"
EXTRA_MIRROR= "http://deb.odroid.in/c2 xenial main" The build process
gets to the point where it attempts to install the package
update-initramfs: Generating /boot/initrd.img-4.4.0-66-generic
Warning: root device   does not exist.
(The space between "device" and "does" above is intentional).
Then,
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.
  subprocess installed post-installation script returned error exit
  status 1
  flash-kernel
E: Sub-process /usr/bin/dpkg returned an error code (1)
error: LTSP client installation ended abnormally
I would appreciate it if someone can point in the right direction.
thanks -Billy
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_____________________________________________________________________
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
_____________________________________________________________________
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net