Re: [Angstrom-devel] Images are all broken
On 04/14/2012 06:58 AM, Gary Thomas wrote: On 2012-04-14 02:04, Koen Kooi wrote: Op 13 apr. 2012, om 21:31 heeft Denys Dmytriyenko het volgende geschreven: I'm not convinced that this is the problem. I just rebuilt systemd-image and Cloud9-image from scratch (BeagleBone) and it came up just fine _without_ /etc/machine-id. I'm not sure what changed between my original report and now, but it's working now and I've not done anything different other than update my Angstrom tree and rebuild. Do you see the following message about the missing /etc/machine-id during boot? (I've removed the colour commentary from my log file.) systemd 44 running in system mode. (+PAM +LIBWRAP -AUDIT -SELINUX +SYSVINIT -LIB CRYPTSETUP; angstrom) Welcome to The Angstrom Distribution! [4.385040] usb 1-2.2: new low speed USB device number 4 using ehci-omap [4.427124] NET: Registered protocol family 10 Inserted module 'ipv6' Set hostname to beagleboard. Cannot open /etc/machine-id: No such file or directory (Hopefully that looks as I intended and is readable ...) Graham Murphy -- Space Science Instrumentation Group (SRI) The Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Rd Laurel MD 20723-6099 Phone: 240-228-3552 Fax: 240-228-7636 Internet: [1]graham.a.mur...@jhuapl.edu Space isn't remote at all. It's only an hour's drive away if your car could go straight upwards. - Fred Hoyle. References 1. mailto:graham.a.mur...@jhuapl.edu ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Images are all broken
Op 13 apr. 2012, om 21:31 heeft Denys Dmytriyenko het volgende geschreven:
On Fri, Apr 13, 2012 at 09:54:23AM -0400, Graham Murphy wrote:
I'll add an extra data point. I find that boot succeeds if the file
/etc/machine-id exists, even if it is an empty file.
So far as I can tell from a brief look, systemd tries
to create the file /etc/machine-id, if it does not exist,
but this appears to be attempted when the root file system
is readonly. (And, yes, if you force the root filesystem to
be read-write when /sbin/init starts, again the boot will be
successful.) Not sure yet why that cascades into the observed
failure yet.
Thanks, that's a good analysis! Wondering why it's not manifesting in a
proper
error message in systemd...
I have a hack to get around this:
koen@dominion:/OE/tentacle/sources/meta-openembedded/meta-oe/recipes-core/systemd$
git diff .
diff --git a/meta-oe/recipes-core/systemd/systemd_git.bb
b/meta-oe/recipes-core/systemd/systemd_git.bb
index b23e5f5..f4ca72a 100644
--- a/meta-oe/recipes-core/systemd/systemd_git.bb
+++ b/meta-oe/recipes-core/systemd/systemd_git.bb
@@ -14,7 +14,7 @@ inherit gitpkgv
PKGV = v${GITPKGVTAG}
PV = git
-PR = r26
+PR = r27
inherit useradd pkgconfig autotools vala perlnative
@@ -64,6 +64,10 @@ do_install() {
# create dir for journal
install -d ${D}${localstatedir}/log/journal
+
+ # create machine-id
+ # 20:12 mezcalero koen: you have three options: a) run
systemd-machine-id-setup at install time, b) have / read-only and an empty file
there (for stateless) and c) boot with / writable
+ touch ${D}${sysconfdir}/machine-id
}
But I wonder if we should fix it differently. We already have this one:
koen@dominion:/OE/tentacle/sources/meta-openembedded/meta-oe/recipes-core/systemd$
cat ./systemd-compat-units/machineid.service
[Unit]
Description=Machine ID first boot configure
DefaultDependencies=no
ConditionPathExists=|!/etc/machine-id
After=remount-rootfs.service
Before=sysinit.target
[Service]
ExecStart=/bin/systemd-machine-id-setup
RemainAfterExit=No
Type=oneshot
StandardOutput=syslog
[Install]
WantedBy=basic.target
WantedBy=sysinit.target
Which apparently is too late.
regards,
Koen
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Images are all broken
On 2012-04-14 02:04, Koen Kooi wrote:
Op 13 apr. 2012, om 21:31 heeft Denys Dmytriyenko het volgende geschreven:
On Fri, Apr 13, 2012 at 09:54:23AM -0400, Graham Murphy wrote:
I'll add an extra data point. I find that boot succeeds if the file
/etc/machine-id exists, even if it is an empty file.
So far as I can tell from a brief look, systemd tries
to create the file /etc/machine-id, if it does not exist,
but this appears to be attempted when the root file system
is readonly. (And, yes, if you force the root filesystem to
be read-write when /sbin/init starts, again the boot will be
successful.) Not sure yet why that cascades into the observed
failure yet.
Thanks, that's a good analysis! Wondering why it's not manifesting in a proper
error message in systemd...
I have a hack to get around this:
koen@dominion:/OE/tentacle/sources/meta-openembedded/meta-oe/recipes-core/systemd$
git diff .
diff --git a/meta-oe/recipes-core/systemd/systemd_git.bb
b/meta-oe/recipes-core/systemd/systemd_git.bb
index b23e5f5..f4ca72a 100644
--- a/meta-oe/recipes-core/systemd/systemd_git.bb
+++ b/meta-oe/recipes-core/systemd/systemd_git.bb
@@ -14,7 +14,7 @@ inherit gitpkgv
PKGV = v${GITPKGVTAG}
PV = git
-PR = r26
+PR = r27
inherit useradd pkgconfig autotools vala perlnative
@@ -64,6 +64,10 @@ do_install() {
# create dir for journal
install -d ${D}${localstatedir}/log/journal
+
+ # create machine-id
+ # 20:12 mezcalero koen: you have three options: a) run
systemd-machine-id-setup at install time, b) have / read-only and an empty file there
(for stateless) and c) boot with / writable
+ touch ${D}${sysconfdir}/machine-id
}
But I wonder if we should fix it differently. We already have this one:
koen@dominion:/OE/tentacle/sources/meta-openembedded/meta-oe/recipes-core/systemd$
cat ./systemd-compat-units/machineid.service
[Unit]
Description=Machine ID first boot configure
DefaultDependencies=no
ConditionPathExists=|!/etc/machine-id
After=remount-rootfs.service
Before=sysinit.target
[Service]
ExecStart=/bin/systemd-machine-id-setup
RemainAfterExit=No
Type=oneshot
StandardOutput=syslog
[Install]
WantedBy=basic.target
WantedBy=sysinit.target
Which apparently is too late.
I'm not convinced that this is the problem. I just rebuilt
systemd-image and Cloud9-image from scratch (BeagleBone) and
it came up just fine _without_ /etc/machine-id. I'm not sure
what changed between my original report and now, but it's working
now and I've not done anything different other than update my
Angstrom tree and rebuild.
My working Angstrom setup is:
OE Build Configuration:
BB_VERSION= 1.15.1
TARGET_ARCH = arm
TARGET_OS = linux-gnueabi
MACHINE = beaglebone
DISTRO= angstrom
DISTRO_VERSION= v2012.04-core
TUNE_FEATURES = armv7a vfp neon cortexa8
TARGET_FPU= vfp-neon
meta-angstrom = master:bfb6c66ee406d2e3db618e41e32d51d63e430657
meta-oe
toolchain-layer
meta-efl
meta-gpe
meta-gnome
meta-xfce
meta-initramfs= master:204f537a181e3532ef8ba9ddadb7baf49a3b2be5
meta-opie = master:efa3892b20a4ef80274e56e5633ebd62c16f9731
meta-java = master:3386ea6c96096f107f43f282f654e5afa456109e
meta-mozilla = master:5737d9fa26a632a27b2aa760c0d01190f0a17d0e
meta-ti = master:246cb75a970e9aab0a3974a55e72c6d90f1df151
meta-efikamx = master:2c09a3a780b23448e8a6ca964256ff7f5ccba65d
meta-nslu2= master:3d9fc951b05b4df476374b6fc3085ebac7f293ee
meta-htc
meta-nokia
meta-openmoko
meta-palm = master:ba34166f4565b52209adea82cef196615cf82246
meta-handheld = master:1f05a15aceb4c3a19fa070463b58125b5658b2a9
meta-intel
meta-sugarbay
meta-crownbay
meta-emenlow
meta-fishriver
meta-fri2
meta-jasperforest
meta-n450 = master:15860ffb2164629c27f4bf49614efad5177441c4
meta = master:17f3cc1be0e8648cb4579793a9eb5a701deac85f
--
Gary Thomas | Consulting for the
MLB Associates |Embedded world
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Images are all broken
On 04/14/2012 06:58 AM, Gary Thomas wrote:
On 2012-04-14 02:04, Koen Kooi wrote:
Op 13 apr. 2012, om 21:31 heeft Denys Dmytriyenko het volgende
geschreven:
On Fri, Apr 13, 2012 at 09:54:23AM -0400, Graham Murphy wrote:
I'll add an extra data point. I find that boot succeeds if the file
/etc/machine-id exists, even if it is an empty file.
So far as I can tell from a brief look, systemd tries
to create the file /etc/machine-id, if it does not exist,
but this appears to be attempted when the root file system
is readonly. (And, yes, if you force the root filesystem to
be read-write when /sbin/init starts, again the boot will be
successful.) Not sure yet why that cascades into the observed
failure yet.
Thanks, that's a good analysis! Wondering why it's not manifesting in
a proper
error message in systemd...
I have a hack to get around this:
koen@dominion:/OE/tentacle/sources/meta-openembedded/meta-oe/recipes-core/systemd$
git diff .
diff --git a/meta-oe/recipes-core/systemd/systemd_git.bb
b/meta-oe/recipes-core/systemd/systemd_git.bb
index b23e5f5..f4ca72a 100644
--- a/meta-oe/recipes-core/systemd/systemd_git.bb
+++ b/meta-oe/recipes-core/systemd/systemd_git.bb
@@ -14,7 +14,7 @@ inherit gitpkgv
PKGV = v${GITPKGVTAG}
PV = git
-PR = r26
+PR = r27
inherit useradd pkgconfig autotools vala perlnative
@@ -64,6 +64,10 @@ do_install() {
# create dir for journal
install -d ${D}${localstatedir}/log/journal
+
+ # create machine-id
+ # 20:12 mezcalero koen: you have three options: a) run
systemd-machine-id-setup at install time, b) have / read-only and an
empty file there (for stateless) and c) boot with / writable
+ touch ${D}${sysconfdir}/machine-id
}
But I wonder if we should fix it differently. We already have this one:
koen@dominion:/OE/tentacle/sources/meta-openembedded/meta-oe/recipes-core/systemd$
cat ./systemd-compat-units/machineid.service
[Unit]
Description=Machine ID first boot configure
DefaultDependencies=no
ConditionPathExists=|!/etc/machine-id
After=remount-rootfs.service
Before=sysinit.target
[Service]
ExecStart=/bin/systemd-machine-id-setup
RemainAfterExit=No
Type=oneshot
StandardOutput=syslog
[Install]
WantedBy=basic.target
WantedBy=sysinit.target
Which apparently is too late.
I'm not convinced that this is the problem. I just rebuilt
systemd-image and Cloud9-image from scratch (BeagleBone) and
it came up just fine _without_ /etc/machine-id. I'm not sure
what changed between my original report and now, but it's working
now and I've not done anything different other than update my
Angstrom tree and rebuild.
My working Angstrom setup is:
OE Build Configuration:
BB_VERSION = 1.15.1
TARGET_ARCH = arm
TARGET_OS = linux-gnueabi
MACHINE = beaglebone
DISTRO = angstrom
DISTRO_VERSION = v2012.04-core
TUNE_FEATURES = armv7a vfp neon cortexa8
TARGET_FPU = vfp-neon
meta-angstrom = master:bfb6c66ee406d2e3db618e41e32d51d63e430657
meta-oe
toolchain-layer
meta-efl
meta-gpe
meta-gnome
meta-xfce
meta-initramfs = master:204f537a181e3532ef8ba9ddadb7baf49a3b2be5
meta-opie = master:efa3892b20a4ef80274e56e5633ebd62c16f9731
meta-java = master:3386ea6c96096f107f43f282f654e5afa456109e
meta-mozilla = master:5737d9fa26a632a27b2aa760c0d01190f0a17d0e
meta-ti = master:246cb75a970e9aab0a3974a55e72c6d90f1df151
meta-efikamx = master:2c09a3a780b23448e8a6ca964256ff7f5ccba65d
meta-nslu2 = master:3d9fc951b05b4df476374b6fc3085ebac7f293ee
meta-htc
meta-nokia
meta-openmoko
meta-palm = master:ba34166f4565b52209adea82cef196615cf82246
meta-handheld = master:1f05a15aceb4c3a19fa070463b58125b5658b2a9
meta-intel
meta-sugarbay
meta-crownbay
meta-emenlow
meta-fishriver
meta-fri2
meta-jasperforest
meta-n450 = master:15860ffb2164629c27f4bf49614efad5177441c4
meta = master:17f3cc1be0e8648cb4579793a9eb5a701deac85f
What is your build machine OS by chance? Thanks
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Images are all broken
Gary Thomas gary@... writes: All of the recent images I've built (for beaglebone at least) fail on boot with these messages: Starting Journal Service... Failed to start Journal Service I'll add an extra data point. I find that boot succeeds if the file /etc/machine-id exists, even if it is an empty file. So far as I can tell from a brief look, systemd tries to create the file /etc/machine-id, if it does not exist, but this appears to be attempted when the root file system is readonly. (And, yes, if you force the root filesystem to be read-write when /sbin/init starts, again the boot will be successful.) Not sure yet why that cascades into the observed failure yet. An annoying complication I found was that the rescue and emergency modes were not working, leaving the system with no access at all. This turned out to be because the systemd-image.tar.bz2 did not include a /root directory. Creating /root resulted in the emergency maintenance prompt being presented. -- Space Science Instrumentation Group (SRI) The Johns Hopkins University Applied Physics Laboratory 11100 Johns Hopkins Rd Laurel MD 20723-6099 Phone: 240-228-3552 Fax: 240-228-7636 Internet: graham.a.mur...@jhuapl.edu Space isn't remote at all. It's only an hour's drive away if your car could go straight upwards. - Fred Hoyle. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Images are all broken
Op 13 apr. 2012, om 15:54 heeft Graham Murphy het volgende geschreven: Gary Thomas gary@... writes: All of the recent images I've built (for beaglebone at least) fail on boot with these messages: Starting Journal Service... Failed to start Journal Service I'll add an extra data point. I find that boot succeeds if the file /etc/machine-id exists, even if it is an empty file. So far as I can tell from a brief look, systemd tries to create the file /etc/machine-id, if it does not exist, but this appears to be attempted when the root file system is readonly. (And, yes, if you force the root filesystem to be read-write when /sbin/init starts, again the boot will be successful.) Not sure yet why that cascades into the observed failure yet. An annoying complication I found was that the rescue and emergency modes were not working, leaving the system with no access at all. This turned out to be because the systemd-image.tar.bz2 did not include a /root directory. Creating /root resulted in the emergency maintenance prompt being presented. Thanks for the report, the emergency and rescue modes have been fixed in r26. regards, Koen ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Images are all broken
On 13-04-12 15:54, Graham Murphy wrote: I'll add an extra data point. I find that boot succeeds if the file /etc/machine-id exists, even if it is an empty file. Thank you. The resolution for a week of struggling trying to get my own build to run on beagleboard-xm. -- Jaap Versteegh ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Images are all broken
On Fri, Apr 13, 2012 at 09:54:23AM -0400, Graham Murphy wrote: I'll add an extra data point. I find that boot succeeds if the file /etc/machine-id exists, even if it is an empty file. So far as I can tell from a brief look, systemd tries to create the file /etc/machine-id, if it does not exist, but this appears to be attempted when the root file system is readonly. (And, yes, if you force the root filesystem to be read-write when /sbin/init starts, again the boot will be successful.) Not sure yet why that cascades into the observed failure yet. Thanks, that's a good analysis! Wondering why it's not manifesting in a proper error message in systemd... -- Denys ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Images are all broken
2012/3/20 Benny B. Simonsen b...@serenergy.com 2012/3/8 Gary Thomas g...@mlbassoc.com On 2012-03-08 12:20, Ulf Samuelsson wrote: You can at time rlogin even if you do not get a prompt. also, NFS mounting will give you access to logs onthe NFS host. I can't log in - no services get started because the postinst functions have not run and the system is not fully configured. See the most recent email about this from eariler today. Hi, It seems like I have the same issue with postinst on beaglebone. Did anyone find out why systemd apparently skip this step? Thanks /Benny My problem were apparently caused by a filesystem error on the SD card. After running e2fsck the same image booted without problems. I have not used systemd before, but I would have expected a console message if the systemd-fsck failed during boot. I have to check it again, but e2fsck could be a hint if anyone else have the problem /Benny ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Images are all broken
2012/3/8 Gary Thomas g...@mlbassoc.com On 2012-03-08 12:20, Ulf Samuelsson wrote: You can at time rlogin even if you do not get a prompt. also, NFS mounting will give you access to logs onthe NFS host. I can't log in - no services get started because the postinst functions have not run and the system is not fully configured. See the most recent email about this from eariler today. Hi, It seems like I have the same issue with postinst on beaglebone. Did anyone find out why systemd apparently skip this step? Thanks /Benny ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Images are all broken
On 07.03.2012 15:04, Koen Kooi wrote: Does your kernel have these options enabled: http://dominion.thruhere.net/koen/cms/recommended-kernel-config-options-for-a-modern-angstrom-system ? It does now... Thank you ! This solved most of the issues but I still get : Dependency failed. Aborted start of Getty on tty1 [ABORT] I will look into it. -- Christophe Aeschlimann Embedded Software Engineer IT Manager ACN Advanced Communications Networks S.A. 2000 - Neuchâtel, Switzerland Tel. +41 32 724 74 31 ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Images are all broken
On 2012-03-08 05:36, Gary Thomas wrote: On 2012-03-08 05:30, Christophe Aeschlimann wrote: On 07.03.2012 15:04, Koen Kooi wrote: Does your kernel have these options enabled: http://dominion.thruhere.net/koen/cms/recommended-kernel-config-options-for-a-modern-angstrom-system ? It does now... Thank you ! This solved most of the issues but I still get : Dependency failed. Aborted start of Getty on tty1 [ABORT] I will look into it. This is happening because the postinst scripts are not being run during the first boot. I'm not sure why they don't run anymore, but they used to be run via the script /etc/rcS.d/S98configure With the change to systemd, this doesn't seem to happen. To be clear, I believe it's the change to use systemd that has broken this function, not running the first-boot scripts. These should be executed by running 'opkg-cl configure' -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Images are all broken
You can at time rlogin even if you do not get a prompt. also, NFS mounting will give you access to logs onthe NFS host. Best Regards Ulf Samuelsson 4 mar 2012 kl. 13:48 skrev Gary Thomas g...@mlbassoc.com: All of the recent images I've built (for beaglebone at least) fail on boot with these messages: Starting Journal Service... Failed to start Journal Service [FAILED] See 'systemctl status systemd-journald.service' for details. Dependency failed. Aborted start of Getty on tty1 [ ABORT] Dependency failed. Aborted start of Serial Getty on ttyO0 [ ABORT] Since this is a very early-on failure, nothing runs and I can't get in to run the status command to figure out what's wrong. Perhaps there is some way to get more verbose output to the console? I could edit some config file, etc, offline an try another boot. This build was for systemd-image, from a 100% scratch setup, as of 2012-03-02 1500 GMT OE Build Configuration: BB_VERSION= 1.15.1 TARGET_ARCH = arm TARGET_OS = linux-gnueabi MACHINE = beaglebone DISTRO= angstrom DISTRO_VERSION= v2012.03-core TUNE_FEATURES = armv7a vfp neon cortexa8 TARGET_FPU= vfp-neon meta-angstrom = master:2129eed920364abcc4f3f72d395333a041634e26 meta-oe meta-efl meta-gpe meta-gnome meta-xfce meta-initramfs= master:fdff8697ea2db6254d26510adb7d11e6352d950f meta-opie = master:efa3892b20a4ef80274e56e5633ebd62c16f9731 meta-java = master:d430de31c167cd264be74a1d82af4b732bb915dd meta-mozilla = master:5737d9fa26a632a27b2aa760c0d01190f0a17d0e meta-ti = master:020b6f893d13e36bccd7a2d8e6a0e6ab5e602450 meta-efikamx = master:2c09a3a780b23448e8a6ca964256ff7f5ccba65d meta-nslu2= master:3d9fc951b05b4df476374b6fc3085ebac7f293ee meta-htc meta-nokia meta-openmoko meta-palm = master:cda19686a2a3573ce50c86733c3469d926124995 meta-handheld = master:fa1e6dcb524eb7ed29a6cd971a150d35c31e96e7 meta-intel meta-sugarbay meta-crownbay meta-emenlow meta-fishriver meta-jasperforest meta-n450 = master:df18b721f86f0737c0f302e49b27ea232c70e683 meta = master:b24d4bcde21b013e48eaffea5f3a70d8b1df1047 -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Images are all broken
On 2012-03-08 12:20, Ulf Samuelsson wrote: You can at time rlogin even if you do not get a prompt. also, NFS mounting will give you access to logs onthe NFS host. I can't log in - no services get started because the postinst functions have not run and the system is not fully configured. See the most recent email about this from eariler today. 4 mar 2012 kl. 13:48 skrev Gary Thomasg...@mlbassoc.com: All of the recent images I've built (for beaglebone at least) fail on boot with these messages: Starting Journal Service... Failed to start Journal Service [FAILED] See 'systemctl status systemd-journald.service' for details. Dependency failed. Aborted start of Getty on tty1 [ ABORT] Dependency failed. Aborted start of Serial Getty on ttyO0 [ ABORT] Since this is a very early-on failure, nothing runs and I can't get in to run the status command to figure out what's wrong. Perhaps there is some way to get more verbose output to the console? I could edit some config file, etc, offline an try another boot. This build was for systemd-image, from a 100% scratch setup, as of 2012-03-02 1500 GMT OE Build Configuration: BB_VERSION= 1.15.1 TARGET_ARCH = arm TARGET_OS = linux-gnueabi MACHINE = beaglebone DISTRO= angstrom DISTRO_VERSION= v2012.03-core TUNE_FEATURES = armv7a vfp neon cortexa8 TARGET_FPU= vfp-neon meta-angstrom = master:2129eed920364abcc4f3f72d395333a041634e26 meta-oe meta-efl meta-gpe meta-gnome meta-xfce meta-initramfs= master:fdff8697ea2db6254d26510adb7d11e6352d950f meta-opie = master:efa3892b20a4ef80274e56e5633ebd62c16f9731 meta-java = master:d430de31c167cd264be74a1d82af4b732bb915dd meta-mozilla = master:5737d9fa26a632a27b2aa760c0d01190f0a17d0e meta-ti = master:020b6f893d13e36bccd7a2d8e6a0e6ab5e602450 meta-efikamx = master:2c09a3a780b23448e8a6ca964256ff7f5ccba65d meta-nslu2= master:3d9fc951b05b4df476374b6fc3085ebac7f293ee meta-htc meta-nokia meta-openmoko meta-palm = master:cda19686a2a3573ce50c86733c3469d926124995 meta-handheld = master:fa1e6dcb524eb7ed29a6cd971a150d35c31e96e7 meta-intel meta-sugarbay meta-crownbay meta-emenlow meta-fishriver meta-jasperforest meta-n450 = master:df18b721f86f0737c0f302e49b27ea232c70e683 meta = master:b24d4bcde21b013e48eaffea5f3a70d8b1df1047 -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Images are all broken
Hi, On 04.03.2012 13:48, Gary Thomas wrote: All of the recent images I've built (for beaglebone at least) fail on boot with these messages: Starting Journal Service... Failed to start Journal Service [FAILED] See 'systemctl status systemd-journald.service' for details. Dependency failed. Aborted start of Getty on tty1 [ ABORT] Dependency failed. Aborted start of Serial Getty on ttyO0 [ ABORT] Since this is a very early-on failure, nothing runs and I can't get in to run the status command to figure out what's wrong. Perhaps there is some way to get more verbose output to the console? I could edit some config file, etc, offline an try another boot. This build was for systemd-image, from a 100% scratch setup, I'm in the same boat except I get access to the serial terminal in the end. I'm new to systemd so I have to read a little bit about it. In the meantime the suggested commands returns : root@ixppci:~# systemctl status systemd-journald.service Failed to get D-Bus connection: No connection to service manager. My image is a modified version of systemd-image that uses a modified version of task-basic which doesn't install the connection manager and avahi. My image had to be smaller than 14MB to fit in a 16MB chip with the Kernel (~2MB). I'll keep you informed if I find anything. Best regards, -- Christophe Aeschlimann Embedded Software Engineer IT Manager ACN Advanced Communications Networks S.A. 2000 - Neuchâtel, Switzerland Tel. +41 32 724 74 31 ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Images are all broken
On 2012-03-07 05:34, Christophe Aeschlimann wrote: Hi, On 04.03.2012 13:48, Gary Thomas wrote: All of the recent images I've built (for beaglebone at least) fail on boot with these messages: Starting Journal Service... Failed to start Journal Service [FAILED] See 'systemctl status systemd-journald.service' for details. Dependency failed. Aborted start of Getty on tty1 [ ABORT] Dependency failed. Aborted start of Serial Getty on ttyO0 [ ABORT] Since this is a very early-on failure, nothing runs and I can't get in to run the status command to figure out what's wrong. Perhaps there is some way to get more verbose output to the console? I could edit some config file, etc, offline an try another boot. This build was for systemd-image, from a 100% scratch setup, I'm in the same boat except I get access to the serial terminal in the end. How long did you have to wait? My BeagleBone has been sitting at this point for about 24 hours - I don't think it will ever come out of it ;-) I'm new to systemd so I have to read a little bit about it. In the meantime the suggested commands returns : root@ixppci:~# systemctl status systemd-journald.service Failed to get D-Bus connection: No connection to service manager. In the end is dbus running? My image is a modified version of systemd-image that uses a modified version of task-basic which doesn't install the connection manager and avahi. My image had to be smaller than 14MB to fit in a 16MB chip with the Kernel (~2MB). I'll keep you informed if I find anything. Best regards, Thanks, at least now I know I'm not the only one with problems :-) -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Images are all broken
On 07.03.2012 14:33, Gary Thomas wrote:
How long did you have to wait? My BeagleBone has been sitting at this
point
for about 24 hours - I don't think it will ever come out of it ;-)
It comes instantly... but I do get the [ABORT] on getty after I've
logged into the system. Boot log here : http://pastebin.com/e5gV316J
In the end is dbus running?
PID USER VSZ STAT COMMAND
1 root 4396 S{systemd} /sbin/init
2 root 0 SW [kthreadd]
3 root 0 SW [ksoftirqd/0]
4 root 0 SW [kworker/0:0]
5 root 0 SW [kworker/u:0]
6 root 0 SW [rcu_kthread]
7 root 0 SW [khelper]
8 root 0 SW [sync_supers]
9 root 0 SW [bdi-default]
10 root 0 SW [kblockd]
11 root 0 SW [ata_sff]
12 root 0 SW [khubd]
13 root 0 SW [rpciod]
14 root 0 SW [kworker/0:1]
15 root 0 SW [kswapd0]
16 root 0 SW [fsnotify_mark]
17 root 0 SW [nfsiod]
18 root 0 SW [mtdblock0]
19 root 0 SW [mtdblock1]
20 root 0 SW [mtdblock2]
21 root 0 SW [mtdblock3]
22 root 0 SW [kworker/u:1]
25 root 0 SW [mtdblock4]
30 root 0 SW [wpan-phy1]
41 root 2416 S/lib/udev/udevd
46 root 0 SW [flush-mtd-unmap]
47 root 0 SWN [jffs2_gcd_mtd1]
52 root 2740 S/lib/systemd/systemd-logind
90 root 2828 S/bin/login --
91 messageb 2472 S/usr/bin/dbus-daemon --system
--address=systemd: --nofork --systemd-activation
94 root 2412 S/lib/udev/udevd
95 root 2412 S/lib/udev/udevd
110 root 4040 S/usr/sbin/sshd
111 root 2296 S-sh
114 root 2296 Rps -w
Looks like it.
Tried to stop/restart it using
root@ixppci:~#/etc/init.d/dbus-1 stop
root@ixppci:~#/etc/init.d/dbus-1 start
But systemctl still says :
Failed to get D-Bus connection: No connection to service manager.
Thanks, at least now I know I'm not the only one with problems :-)
Too bad you haven't found a solution already ;)
Regards,
--
Christophe Aeschlimann
Embedded Software Engineer IT Manager
ACN Advanced Communications Networks S.A.
2000 - Neuchâtel, Switzerland
Tel. +41 32 724 74 31
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Images are all broken
Op 7 mrt. 2012, om 14:59 heeft Christophe Aeschlimann het volgende geschreven: On 07.03.2012 14:33, Gary Thomas wrote: How long did you have to wait? My BeagleBone has been sitting at this point for about 24 hours - I don't think it will ever come out of it ;-) It comes instantly... but I do get the [ABORT] on getty after I've logged into the system. Boot log here : http://pastebin.com/e5gV316J Does your kernel have these options enabled: http://dominion.thruhere.net/koen/cms/recommended-kernel-config-options-for-a-modern-angstrom-system ? [..] Tried to stop/restart it using root@ixppci:~#/etc/init.d/dbus-1 stop root@ixppci:~#/etc/init.d/dbus-1 start That's the sysv script, don't use that! ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Images are all broken
On 2012-03-07 08:22, Gary Thomas wrote: On 2012-03-07 05:34, Christophe Aeschlimann wrote: Hi, On 04.03.2012 13:48, Gary Thomas wrote: All of the recent images I've built (for beaglebone at least) fail on boot with these messages: Starting Journal Service... Failed to start Journal Service [FAILED] See 'systemctl status systemd-journald.service' for details. Dependency failed. Aborted start of Getty on tty1 [ ABORT] Dependency failed. Aborted start of Serial Getty on ttyO0 [ ABORT] Since this is a very early-on failure, nothing runs and I can't get in to run the status command to figure out what's wrong. Perhaps there is some way to get more verbose output to the console? I could edit some config file, etc, offline an try another boot. This build was for systemd-image, from a 100% scratch setup, I'm in the same boat except I get access to the serial terminal in the end. I'm new to systemd so I have to read a little bit about it. In the meantime the suggested commands returns : root@ixppci:~# systemctl status systemd-journald.service Failed to get D-Bus connection: No connection to service manager. My image is a modified version of systemd-image that uses a modified version of task-basic which doesn't install the connection manager and avahi. My image had to be smaller than 14MB to fit in a 16MB chip with the Kernel (~2MB). I'll keep you informed if I find anything. I found out why my system was not coming up - it seems that the avahi daemon (and dbus component) was not enabled. Looking at the systemd setup, I found this: /etc/systemd/system /etc/systemd/system/sockets.target.wants /etc/systemd/system/sockets.target.wants/dropbear.socket /etc/systemd/system/basic.target.wants /etc/systemd/system/basic.target.wants/timestamp.service /etc/systemd/system/multi-user.target.wants /etc/systemd/system/multi-user.target.wants/dropbearkey.service /etc/systemd/system/multi-user.target.wants/connman.service /etc/systemd/system/multi-user.target.wants/remote-fs.target /etc/systemd/system/local-fs.target.wants /etc/systemd/system/sysinit.target.wants /etc/systemd/system/getty.target.wants /etc/systemd/system/getty.target.wants/getty@tty1.service /etc/systemd/system/getty.target.wants/serial-getty@ttyO0.service I booted the system manually into just a shell and ran sh-4.2# systemctl enable avahi-daemon.service ln -s '/lib/systemd/system/avahi-daemon.service' '/etc/systemd/system/dbus-org.freedesktop.Avahi.service' ln -s '/lib/systemd/system/avahi-daemon.service' '/etc/systemd/system/multi-user.target.wants/avahi-daemon.service' ln -s '/lib/systemd/system/avahi-daemon.socket' '/etc/systemd/system/sockets.target.wants/avahi-daemon.socket' Now, it comes up to a prompt. I'll look into the build logs to figure out why the avahi-daemon is not being enabled. I see now in the build log: Configuring avahi-daemon. Configuring avahi-systemd. avahi-systemd.postinst returned 1, marking as unpacked only, configuration required on target. But it doesn't look like this runtime initialization ever happened. -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Images are all broken
On 2012-03-07 08:29, Gary Thomas wrote: On 2012-03-07 08:22, Gary Thomas wrote: On 2012-03-07 05:34, Christophe Aeschlimann wrote: Hi, On 04.03.2012 13:48, Gary Thomas wrote: All of the recent images I've built (for beaglebone at least) fail on boot with these messages: Starting Journal Service... Failed to start Journal Service [FAILED] See 'systemctl status systemd-journald.service' for details. Dependency failed. Aborted start of Getty on tty1 [ ABORT] Dependency failed. Aborted start of Serial Getty on ttyO0 [ ABORT] Since this is a very early-on failure, nothing runs and I can't get in to run the status command to figure out what's wrong. Perhaps there is some way to get more verbose output to the console? I could edit some config file, etc, offline an try another boot. This build was for systemd-image, from a 100% scratch setup, I'm in the same boat except I get access to the serial terminal in the end. I'm new to systemd so I have to read a little bit about it. In the meantime the suggested commands returns : root@ixppci:~# systemctl status systemd-journald.service Failed to get D-Bus connection: No connection to service manager. My image is a modified version of systemd-image that uses a modified version of task-basic which doesn't install the connection manager and avahi. My image had to be smaller than 14MB to fit in a 16MB chip with the Kernel (~2MB). I'll keep you informed if I find anything. I found out why my system was not coming up - it seems that the avahi daemon (and dbus component) was not enabled. Looking at the systemd setup, I found this: /etc/systemd/system /etc/systemd/system/sockets.target.wants /etc/systemd/system/sockets.target.wants/dropbear.socket /etc/systemd/system/basic.target.wants /etc/systemd/system/basic.target.wants/timestamp.service /etc/systemd/system/multi-user.target.wants /etc/systemd/system/multi-user.target.wants/dropbearkey.service /etc/systemd/system/multi-user.target.wants/connman.service /etc/systemd/system/multi-user.target.wants/remote-fs.target /etc/systemd/system/local-fs.target.wants /etc/systemd/system/sysinit.target.wants /etc/systemd/system/getty.target.wants /etc/systemd/system/getty.target.wants/getty@tty1.service /etc/systemd/system/getty.target.wants/serial-getty@ttyO0.service I booted the system manually into just a shell and ran sh-4.2# systemctl enable avahi-daemon.service ln -s '/lib/systemd/system/avahi-daemon.service' '/etc/systemd/system/dbus-org.freedesktop.Avahi.service' ln -s '/lib/systemd/system/avahi-daemon.service' '/etc/systemd/system/multi-user.target.wants/avahi-daemon.service' ln -s '/lib/systemd/system/avahi-daemon.socket' '/etc/systemd/system/sockets.target.wants/avahi-daemon.socket' Now, it comes up to a prompt. I'll look into the build logs to figure out why the avahi-daemon is not being enabled. I see now in the build log: Configuring avahi-daemon. Configuring avahi-systemd. avahi-systemd.postinst returned 1, marking as unpacked only, configuration required on target. But it doesn't look like this runtime initialization ever happened. It seems that the script /etc/rcS.d/S98configure which is responsible for running these postinst scripts is not being run at all. Any ideas why? -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] Images are all broken
All of the recent images I've built (for beaglebone at least) fail on boot with these messages: Starting Journal Service... Failed to start Journal Service [FAILED] See 'systemctl status systemd-journald.service' for details. Dependency failed. Aborted start of Getty on tty1 [ ABORT] Dependency failed. Aborted start of Serial Getty on ttyO0 [ ABORT] Since this is a very early-on failure, nothing runs and I can't get in to run the status command to figure out what's wrong. Perhaps there is some way to get more verbose output to the console? I could edit some config file, etc, offline an try another boot. This build was for systemd-image, from a 100% scratch setup, as of 2012-03-02 1500 GMT OE Build Configuration: BB_VERSION= 1.15.1 TARGET_ARCH = arm TARGET_OS = linux-gnueabi MACHINE = beaglebone DISTRO= angstrom DISTRO_VERSION= v2012.03-core TUNE_FEATURES = armv7a vfp neon cortexa8 TARGET_FPU= vfp-neon meta-angstrom = master:2129eed920364abcc4f3f72d395333a041634e26 meta-oe meta-efl meta-gpe meta-gnome meta-xfce meta-initramfs= master:fdff8697ea2db6254d26510adb7d11e6352d950f meta-opie = master:efa3892b20a4ef80274e56e5633ebd62c16f9731 meta-java = master:d430de31c167cd264be74a1d82af4b732bb915dd meta-mozilla = master:5737d9fa26a632a27b2aa760c0d01190f0a17d0e meta-ti = master:020b6f893d13e36bccd7a2d8e6a0e6ab5e602450 meta-efikamx = master:2c09a3a780b23448e8a6ca964256ff7f5ccba65d meta-nslu2= master:3d9fc951b05b4df476374b6fc3085ebac7f293ee meta-htc meta-nokia meta-openmoko meta-palm = master:cda19686a2a3573ce50c86733c3469d926124995 meta-handheld = master:fa1e6dcb524eb7ed29a6cd971a150d35c31e96e7 meta-intel meta-sugarbay meta-crownbay meta-emenlow meta-fishriver meta-jasperforest meta-n450 = master:df18b721f86f0737c0f302e49b27ea232c70e683 meta = master:b24d4bcde21b013e48eaffea5f3a70d8b1df1047 -- Gary Thomas | Consulting for the MLB Associates |Embedded world ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
