Its been a while since I built a UDOO image (need another kernel module), when I ran compile.sh, it pulled new source and told me to clone a new build directory.

In the process of cloning, however with UDOO being EOS, is it still possible to build the legacy kernel/image with current sources?

1 minute ago, chiefwigms said:

is it still possible to build the legacy kernel/image with current sources?

It should be possible to build both kernels/images and they most likely still works fine. We just stop to maintain them. There are two kernels, stock 3.14 and 4.4 which is probably better to go for.

Thanks! For whatever reason, my VM keeps dropping the connection and I can't finish the clone.  Hopefully I'll get a build going tonight

I have two other imx6 based devices (Utilite Pro & Cubox-i 4), both running a nearly unmodified mainline kernel.   

We have DEV branch attached to mainline 4.14.y with a few patches on top, but I am not aware what works and what not. 

 

12 hours ago, chiefwigms said:

VM keeps dropping the connection and I can't finish the clone.

That must be some network/GitHub related issue.

Finally got around to messing with it... I compiled fine, but from the build and install log:

dpkg-genchanges: warning: unknown substitution variable ${kernel:debarch}
dpkg-genchanges: warning: package linux-libc-dev-next-udoo in control file but not in files list

dpkg: dependency problems prevent configuration of armbian-config:
 armbian-config depends on sunxi-tools; however:
  Package sunxi-tools is not installed.

dpkg: error processing package armbian-config (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 armbian-config
dpkg-deb: building package 'armbian-firmware' in 'armbian-firmware_5.46_all.deb'.
dpkg-deb: building package 'armbian-firmware-full' in 'armbian-firmware-full_5.46_all.deb'.
(Reading database ... 99053 files and directories currently installed.)
Preparing to unpack .../armbian-firmware_5.46_all.deb ...
Unpacking armbian-firmware (5.46) over (5.45) ...
Setting up armbian-firmware (5.46) ...
Selecting previously unselected package armbian-tools-xenial.
(Reading database ... 99053 files and directories currently installed.)
Preparing to unpack .../armbian-tools-xenial_5.46_armhf.deb ...
Unpacking armbian-tools-xenial (5.46) ...
Setting up armbian-tools-xenial (5.46) ...
Processing triggers for systemd (229-4ubuntu21.2) ...
Processing triggers for ureadahead (0.100.0-19) ...

After I flash the image, on subsequent boots, i get:

[FAILED] Failed to start Load Kernel Modules.
See 'systemctl status systemd-modules-load.service' for details.

root@udoo:~# systemctl status systemd-modules-load.service
? systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; vendor preset: enabled)
  Drop-In: /lib/systemd/system/systemd-modules-load.service.d
           +-10-timeout.conf
   Active: failed (Result: exit-code) since Sun 2018-06-10 01:15:40 UTC; 4min 9s ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
 Main PID: 297 (code=exited, status=1/FAILURE)

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

Here's the output of armbianmonitor -u

http://ix.io/1cS2

 

I guess its EOS though  

 

The last working image I have was w/ kernel 4.4.76.. anyway to specify that in the checkout/build just to build a kernel module ?

 

If i run /lib/systemd/systemd-modules-load, i get:
Failed to find module 'lp'
Failed to find module 'ppdev'
Failed to find module 'parport_pc'
 

In cat /etc/modules-load.d/cups-filters.conf
# Parallel printer driver modules loading for cups
# LOAD_LP_MODULE was 'yes' in /etc/default/cups
lp
ppdev
parport_pc

 

Commenting out those three seemed to fix it.  Don't believe I need CUPS

15 hours ago, chiefwigms said:

Commenting out those three seemed to fix it.

Or enabling those: https://github.com/armbian/build/commit/ea4723a445f8167ad7250bb97aed79a43665ee77

5 hours ago, Igor said:

Or enabling those: https://github.com/armbian/build/commit/ea4723a445f8167ad7250bb97aed79a43665ee77

Yeah - didn't wanna have to rebuild   Thanks for the commit though - i'm sure i'll be back in 5 months trying to rebuild a module

1 hour ago, chiefwigms said:

Yeah - didn't wanna have to rebuild   Thanks for the commit though - i'm sure i'll be back in 5 months trying to rebuild a module

For future images: https://github.com/armbian/build/blob/master/lib/distributions.sh#L54-L59