On Wed, 25.06.14 10:54, Jay D Bhatt (jay.bh...@igate.com) wrote:
>
> Hi,
>
> Finally I was able to get the my systemd running for multi-user mode,
> so I got login , password and then I could login and get prompt. I
> removed few services which were hindering the progress and included
> serial-g
On Tue, 2014-06-24 at 03:10 +, Jay D Bhatt wrote:
> Hi Steev,
>
> You are almost correct. I use IMX6 board with 3.0.35 kernel ,but board is
> sabreauto. Can you guide how you made systemd work or settings needed on
> these board?
>
> Thanks,
> Jay
You just need to make sure that all (poss
Hi,
Finally I was able to get the my systemd running for multi-user mode, so I got
login , password and then I could login and get prompt. I removed few services
which were hindering the progress and included serial-getty.service in my
multi-user mode, that did the trick.
Since this is only th
>
> > I think I came across this issue the other day (also booting on an arm
> > board, stuck at kernel 3.1), I think that it may be the change to the
> > xattr support in 214 means systemd can no longer be booted if you
> > don't have cgroups xattr support. 213 seems fine, but I haven't tried
> >
On Mon, 23.06.14 21:53, Tom Hirst (tom.hi...@ipe-systems.co.uk) wrote:
> I think I came across this issue the other day (also booting on an arm
> board, stuck at kernel 3.1), I think that it may be the change to the
> xattr support in 214 means systemd can no longer be booted if you
> don't have c
Hi,
'Twas brillig, and Jay D Bhatt at 24/06/14 07:50 did gyre and gimble:
> I am using ttymxc3 as I have LVDS with the board, so, I think tty1
> should not conflict as I will be using console=ttymxc3?
I'm not sure that console= affects actual login getty's. Unless there is
some new generator that
Hi Colin,
I am using ttymxc3 as I have LVDS with the board, so, I think tty1 should not
conflict as I will be using console=ttymxc3?
Also, I think there is some problem with systemd-logind.service it doesn't ask
for login or password nor does it display the shell prompt, because after
startin
Hi Steev,
You are almost correct. I use IMX6 board with 3.0.35 kernel ,but board is
sabreauto. Can you guide how you made systemd work or settings needed on these
board?
Thanks,
Jay
~~Disclaimer~~
On Mon, 2014-06-23 at 12:47 +, Jay D Bhatt wrote:
> Hi Lennart,
>
> Yes, I am working on ARM system, after solving the errors on kernel side, I
> got uImage but it does not work.
>
> But as you suggested, in README it says the kernel above 3.0 should work
> fine. So, I should be on safe sid
'Twas brillig, and Jay D Bhatt at 23/06/14 11:28 did gyre and gimble:
> My systemd stops indefinitely at this point:
>
> [ OK ] Reached target Login Prompts.
>
Just as a quick "is it plugged in?" type check, have you configured
anything that would perhaps conflict with getty@tty1?
I mean, unl
Hi Lennart,
Yes, I am working on ARM system, after solving the errors on kernel side, I got
uImage but it does not work.
But as you suggested, in README it says the kernel above 3.0 should work fine.
So, I should be on safe side then.
Thanks,
Jay
~~
On Mon, 23.06.14 12:30, Jay D Bhatt (jay.bh...@igate.com) wrote:
>
> Hi Zbyszek,
>
> Now, I am able to mount temporary directory, I changed the /etc/fstab
> file and was able to mount it. But still the systemd stops as
> previously at the same point.
systemd will always mount /run and thelike o
HI Kay,
I have configured all kernel options supported in 3.0.35 kernel. I think smack
is not supported, but that should do.
Thanks,
Jay
~~Disclaimer~~~
Information containe
Hi Zbyszek,
Now, I am able to mount temporary directory, I changed the /etc/fstab file and
was able to mount it. But still the systemd stops as previously at the same
point.
I think kernel should not be problem, because as per readme, it should be
greater than 3.0.
I wanted to check if the l
On Mon, Jun 23, 2014 at 12:28 PM, Jay D Bhatt wrote:
>
> My systemd stops indefinitely at this point:
>
> [ OK ] Reached target Login Prompts.
>
> As Lennart suggested, I looked at my kernel version which is 3.0.35, which
> is >= 3.0, so should not give problem for systemd initialization.
>
> Th
On Mon, Jun 23, 2014 at 10:28:27AM +, Jay D Bhatt wrote:
> Hi,
>
> My systemd stops indefinitely at this point:
>
> [ OK ] Reached target Login Prompts.
>
> As Lennart suggested, I looked at my kernel version which is 3.0.35, which is
> >= 3.0, so should not give problem for systemd initi
'Twas brillig, and Kay Sievers at 17/12/11 16:07 did gyre and gimble:
> On Sat, Dec 17, 2011 at 10:41, Sipos Ferenc wrote:
>> I have a laptop with a dual boot and lvm setup, systemd works fine there. On
>> my desktop machine, it stops booting after starting lock (mounting all
>> partition), I can
On Sat, Dec 17, 2011 at 10:41, Sipos Ferenc wrote:
> I have a laptop with a dual boot and lvm setup, systemd works fine there. On
> my desktop machine, it stops booting after starting lock (mounting all
> partition), I can reboot with ctrl-alt-del (it complains about ck-log-
> start.service). The
18 matches
Mail list logo
