lbdonovan / image-builder Goto Github PK

/dev/mmcblk0p1 is 1.6G. Let's aim for 3825204736 bytes (3.82GB) (the size of the eMMC on the black)

one at 192.168.7.2(usb0), the other one at 192.168.6.2(usb1). Both working, as far as I can tell, but the latter should be removed

clang fails on math_runfast.c with:

clang: error: unknown argument: '-no-pie'
clang: error: unsupported argument '-mimplicit-it=arm' to option 'Wa,'

gcc fails on Midi.cpp with:

In file Midi.h: alsa/asoundlib.h: No such file or directory column: 28, line: 13

this gives you the current commit hash and writes it to a file

git rev-parse HEAD > gitcommithash

this keeps happening.

No less on the system??? really???

apt-file
less
dnsutils
psmisc
libasound2-dev
alsa-utils
midisport-firmware

libasound2-dev

I tried to install it

root@beaglebone:~/Bela# apt-get install libasound2-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 libasound2-dev : Depends: libasound2 (= 1.1.3-5) but it is not going to be installed
 libc6-dev : Depends: linux-libc-dev (>= 4.9.2-2) but 1cross is to be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).

Instead of doing apt --fix-broken install I did:

root@beaglebone:~/Bela# apt-get install linux-libc-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
  linux-libc-dev

which installed linux-libc-dev armhf 4.9.18-1
at which point I was able to install libasound2-dev

There's no root password but ssh doesn't let you login as root, you have to login as user 'bela' password 'a' then sudo su. Probably an issue with the ssh config

This only started happening after I got rid of Apache and Bone101, it's probably an issue with systemd

USR0 led keeps blinking for over a minute.
Tried
halt
shutdown -h now

Once it dies, the PWR LED stays on.

The images ships with clang-3.8 (from apt-get I suppose).

We should get 4.0 from here. Perhaps that is also available on some dedicated ppa

You would occasionally get this warning (e.g.: when apt-get'ing something that uses perl to configure the package).

perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
	LANGUAGE = (unset),
	LC_ALL = (unset),
	LANG = "en_GB.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory

This solution worked:

$ export LANGUAGE=en_US.UTF-8
$ export LANG=en_US.UTF-8
$ export LC_ALL=en_US.UTF-8
$ locale-gen en_US.UTF-8
$ dpkg-reconfigure locales

note: the current (incomplete, see log above) configuration is en_GB.UTF-8 (so GB instead of US). I reckon the above fixe with en_GB would work similarly well.

apt list --upgradable lists the packages that could be upgrated with apt-get upgrade.
This lists some packages we probably installed manually (e.g.: the kernel). What is the best way to prevent users from mistakenly upgrade some critical packages when doing apt-get upgrade?

apt list --upgradable
Listing... Done
bb-cape-overlays/unknown 4.4.20170418-0rcnee2~stretch+20170421 armhf [upgradable from: 4.4.20170405-0rcnee1~bpo90+20170407]
bb-customizations/unknown 1.20170421-0rcnee1~stretch+20170421 all [upgradable from: 1.20170413-0rcnee4~bpo90+20170413]
bsdmainutils/testing 9.0.12+nmu1 armhf [upgradable from: 9.0.12]
cpp-6/testing 6.3.0-14 armhf [upgradable from: 6.3.0-12]
g++-6/testing 6.3.0-14 armhf [upgradable from: 6.3.0-12]
gcc-6/testing 6.3.0-14 armhf [upgradable from: 6.3.0-12]
gcc-6-base/testing 6.3.0-14 armhf [upgradable from: 6.3.0-12]
libasan3/testing 6.3.0-14 armhf [upgradable from: 6.3.0-12]
libatomic1/testing 6.3.0-14 armhf [upgradable from: 6.3.0-12]
libcc1-0/testing 6.3.0-14 armhf [upgradable from: 6.3.0-12]
libgcc-6-dev/testing 6.3.0-14 armhf [upgradable from: 6.3.0-12]
libgcc1/testing 1:6.3.0-14 armhf [upgradable from: 1:6.3.0-12]
libgomp1/testing 6.3.0-14 armhf [upgradable from: 6.3.0-12]
libicu57/testing 57.1-6 armhf [upgradable from: 57.1-5]
libldap-2.4-2/testing 2.4.44+dfsg-4+b1 armhf [upgradable from: 2.4.44+dfsg-3]
libldap-common/testing 2.4.44+dfsg-4 all [upgradable from: 2.4.44+dfsg-3]
libobjc-6-dev/testing 6.3.0-14 armhf [upgradable from: 6.3.0-12]
libobjc4/testing 6.3.0-14 armhf [upgradable from: 6.3.0-12]
libstdc++-6-dev/testing 6.3.0-14 armhf [upgradable from: 6.3.0-12]
libstdc++6/testing 6.3.0-14 armhf [upgradable from: 6.3.0-12]
libubsan0/testing 6.3.0-14 armhf [upgradable from: 6.3.0-12]
linux-firmware-image-4.4.61-ti-xenomai-r98/unknown 1stretch armhf [upgradable from: 1cross]
linux-headers-4.4.61-ti-xenomai-r98/unknown 1stretch armhf [upgradable from: 1cross]
linux-image-4.4.61-ti-xenomai-r98/unknown 1stretch armhf [upgradable from: 1cross]

After a little fiddling boot time is not too bad, output of systemd-analyze:

Startup finished in 4.925s (kernel) + 19.229s (userspace) = 24.154s

systemd-analyze blame:

14.532s dev-mmcblk0p1.device
12.489s generic-board-startup.service
10.759s networking.service
3.530s systemd-udev-trigger.service
2.735s udhcpd.service
2.692s capemgr.service
1.827s rsyslog.service
1.754s ofono.service
1.721s connman.service
1.187s dundee.service
1.129s systemd-journald.service
1.025s dnsmasq.service
942ms wpa_supplicant.service
774ms avahi-daemon.service
712ms systemd-timesyncd.service
707ms systemd-fsck-root.service
644ms ssh.service
613ms systemd-udevd.service
566ms dev-mqueue.mount
494ms systemd-journal-flush.service
483ms systemd-update-utmp.service
474ms kmod-static-nodes.service
427ms sys-kernel-config.mount
405ms systemd-modules-load.service
365ms systemd-update-utmp-runlevel.service
364ms systemd-user-sessions.service
353ms systemd-sysctl.service
344ms hostapd.service
333ms systemd-random-seed.service
322ms sys-kernel-debug.mount
308ms systemd-tmpfiles-setup.service
282ms systemd-tmpfiles-setup-dev.service
220ms sys-fs-fuse-connections.mount
195ms systemd-remount-fs.service

though it probably does not come with apt-get and we'd have to install it manually. Or add and maintain a ppa for Bela stuff

I was getting EINVAL all over the place (see #3 (comment) )

I configured with this on the BBB:

 $ /root/xenomai/configure --with-core=cobalt --enable-smp --enable-pshared CFLAGS="-fno-pie -no-pie" LDFLAGS="-no-pie -fno-pie"

then compiled and installed and it worked straight away.

Please enable
CONFIG_XENO_DRIVERS_RTIPC

Otherwise you cannot create pipes! (RTIPC is real-time-inter-process-communication).
Perhaps other things need to be enabled as well, check the 3.8.13 kernel config for hints on XENO flags to enable:
BelaPlatform/Bela#171 (comment)