Re: Bug#832713: Systemd version 231-1 (current in Sid) doesn't work on arm

2016-07-31 Thread Rick Thomas

On Jul 31, 2016, at 2:02 AM, Christian Marillat  wrote:

> On 31 juil. 2016 10:50, Rick Thomas  wrote:
> 
>> Can you send the output of ‘uname -a ; systemd —version’ on that box?
> 
> Linux rpi3.XXX 4.4.0-1-rpi2 #1 SMP Debian 4.4.6-1+rpi14 (2016-05-05) armv7l 
> GNU/Linux
> 
> ,
> | $ systemd -—version 
> | systemd: invalid option -- 'â'
> `——

darn spelling corrector!  changed my double-dash into an m-dash. humph!

But fortunately you figured out what I *meant*.  Thanks!

> 
> Anyway I've downgraded systemd to 230-7 :
> 
> ,
> | $ systemd --version
> | systemd 230
> | +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
> +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN
> `
> 
> Christian

So I guess there must be something different between the kernel your raspberry 
pi is using and the one my sheevaplug is using.  I know that the “marvel” 
series of kernels have several optional features turned off to save space.  
Maybe there’s something there.

> rbthomas@sheeva:~$ uname -a
> Linux sheeva 4.6.0-1-marvell #1 Debian 4.6.4-1 (2016-07-18) armv5tel GNU/Linux

On the other hand, my Cubox-iP4 has the problem and it’s running

> rbthomas@cube:~$ uname -a
> Linux cube 4.6.0-1-armmp #1 SMP Debian 4.6.4-1 (2016-07-18) armv7l GNU/Linux

The Cubox, I think, doesn’t have those space limitations.

Thanks for your help!
Rick



Re: Bug#832713: Systemd version 231-1 (current in Sid) doesn't work on arm

2016-07-31 Thread Christian Marillat
On 31 juil. 2016 10:50, Rick Thomas  wrote:

> Can you send the output of ‘uname -a ; systemd —version’ on that box?

Linux rpi3.XXX 4.4.0-1-rpi2 #1 SMP Debian 4.4.6-1+rpi14 (2016-05-05) armv7l 
GNU/Linux

,
| $ systemd -—version 
| systemd: invalid option -- 'â'
`

Anyway I've downgraded systemd to 230-7 :

,
| $ systemd --version
| systemd 230
| +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN
`

Christian



Re: Bug#832713: Systemd version 231-1 (current in Sid) doesn't work on arm

2016-07-31 Thread Rick Thomas

Can you send the output of ‘uname -a ; systemd —version’ on that box?

Thanks!

On Jul 31, 2016, at 12:22 AM, Christian Marillat  wrote:

> On 31 juil. 2016 08:50, Rick Thomas  wrote:
> 
>> Thanks, Christian!
>> 
>> What is your armel box?  I *do* see it on my SheevaPlug (armel), so
>> there may be a clue.  Is your armel kernel customized in some way?
> 
> Raspberry Pi 2 kernel 4.1.12
> 
> Christian



Re: Bug#832713: Systemd version 231-1 (current in Sid) doesn't work on arm

2016-07-31 Thread Christian Marillat
On 31 juil. 2016 08:50, Rick Thomas  wrote:

> Thanks, Christian!
>
> What is your armel box?  I *do* see it on my SheevaPlug (armel), so
> there may be a clue.  Is your armel kernel customized in some way?

Raspberry Pi 2 kernel 4.1.12

Christian



Re: Bug#832713: Systemd version 231-1 (current in Sid) doesn't work on arm

2016-07-31 Thread Rick Thomas
Thanks, Christian!

What is your armel box?  I *do* see it on my SheevaPlug (armel), so there may 
be a clue.  Is your armel kernel customized in some way?

Enjoy!
Rick

> On Jul 30, 2016, at 11:33 PM, Christian Marillat  wrote:
> 
> On 30 juil. 2016 23:02, Rick Thomas  wrote:
> 
>> Has anyone else noticed this bug?
>> 
>> Bug#832713: systemd: after "systemd (231-1) unstable" update
>> systemd-jurnald.service fails to start
>> 
>> I’ve tried it on armel (SheevaPlug) and armmp (Cubox-i4Pro).  It fails on 
>> both.
>> I’ve also tried it on amd64 and powerpc hardware.  The bug is not present 
>> there.
> 
> I see this bug on a Raspberry Pi3 armhf 4.4.6 but not on a
> Pandaboard ES armhf 4.2.8
> 
> Also I don't see this bug on armel, i386, powerpc, arm64 arches.
> 
> Christian



Re: Bug#832713: Systemd version 231-1 (current in Sid) doesn't work on arm

2016-07-31 Thread Christian Marillat
On 30 juil. 2016 23:02, Rick Thomas  wrote:

> Has anyone else noticed this bug?
>
> Bug#832713: systemd: after "systemd (231-1) unstable" update
> systemd-jurnald.service fails to start
>
> I’ve tried it on armel (SheevaPlug) and armmp (Cubox-i4Pro).  It fails on 
> both.
> I’ve also tried it on amd64 and powerpc hardware.  The bug is not present 
> there.

I see this bug on a Raspberry Pi3 armhf 4.4.6 but not on a
Pandaboard ES armhf 4.2.8

Also I don't see this bug on armel, i386, powerpc, arm64 arches.

Christian