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)
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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 :
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...
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
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
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.
21 matches
Mail list logo
