On Fri, May 8, 2015 at 3:45 PM, Figue wrote:
> On 09/05/15 00:03, Steven Noonan wrote:
>>
>> On Fri, May 1, 2015 at 6:10 PM, Javier Vasquez
>> wrote:
On Fri, May 1, 2015 at 4:11 AM, Mark Lee wrote:
...
This is unrelated, but does Arch Linux respect rootwait?
>>>
>>> Linu
On 09/05/15 00:03, Steven Noonan wrote:
On Fri, May 1, 2015 at 6:10 PM, Javier Vasquez wrote:
On Fri, May 1, 2015 at 4:11 AM, Mark Lee wrote:
...
This is unrelated, but does Arch Linux respect rootwait?
Linux does, :-) I don't need on this laptop, but I have Arch also on
a USB disk, and for
On Fri, May 1, 2015 at 6:10 PM, Javier Vasquez wrote:
>> On Fri, May 1, 2015 at 4:11 AM, Mark Lee wrote:
>> ...
>>
>> This is unrelated, but does Arch Linux respect rootwait?
>
> Linux does, :-) I don't need on this laptop, but I have Arch also on
> a USB disk, and for that one, at times linux d
> On Fri, May 1, 2015 at 4:11 AM, Mark Lee wrote:
> ...
>
> This is unrelated, but does Arch Linux respect rootwait?
Linux does, :-) I don't need on this laptop, but I have Arch also on
a USB disk, and for that one, at times linux doesn't find root, so I
found it just needed to wait for it to be
I ran into the same problem this morning unfortunately :(
The relevant journalctl output (it is quite similar to Javier's)
= journalctl ===
May 01 12:50:13 archM systemd[1]: Listening on D-Bus System Message Bus
Socket.
May 01 12:50:13 archM systemd[1]: Starting D-
On Thursday, April 30, 2015 11:29:18 AM Javier Vasquez wrote:
> echo 'Loading Linux linux ...'
> linux /vmlinuz-linux root=UUID= rw rootwait
> rootfstype=ext4 resume=UUID=
This is unrelated, but does Arch Linux respect rootwait?
> echo 'Loading initial ramdisk ...'
> init
> On Wed, Apr 29, 2015 at 9:25 PM, Mark Lee wrote:
> ...
>
> What's your kernel cmdline?
> What's your initcpio hooks?
>
> Regards,
> Mark
My "grub" stuff to call linux (the kernel):
echo 'Loading Linux linux ...'
linux /vmlinuz-linux root=UUID= rw rootwait
rootfstype=ext4 resume=UU
Javier Vasquez on Wed, 2015/04/29 15:40:
> I haven't identified under which circumstances, when booting the
> system hangs, and the only thing that can be related to that is the
> message:
>
> Failed to start Login Service
>
> Of course the recommendation to see the output of:
>
> systemctl sta
Here's mine which is a little different than yours
[Login]
#NAutoVTs=6
#ReserveVT=6
#KillUserProcesses=no
#KillOnlyUsers=
#KillExcludeUsers=root
#Controllers=
#ResetControllers=cpu
#InhibitDelayMaxSec=5
HandlePowerKey=ignore
HandleSuspendKey=ignore
HandleHibernateKey=ignore
HandleLidSwitch=ignore
On Wednesday, April 29, 2015 09:21:10 PM Javier Vasquez wrote:
> On Wed, Apr 29, 2015 at 8:30 PM, Marshall Neill
wrote:
> > logind.conf is in /etc/systemd
>
> Yeap:
>
> % grep '^[^#]' /etc/systemd/logind.conf
> [Login]
> HandlePowerKey=reboot
> HandleLidSwitch=ignore
>
> The rest are commentar
On Wed, Apr 29, 2015 at 8:30 PM, Marshall Neill wrote:
> logind.conf is in /etc/systemd
Yeap:
% grep '^[^#]' /etc/systemd/logind.conf
[Login]
HandlePowerKey=reboot
HandleLidSwitch=ignore
The rest are commentaries...
--
Javier
logind.conf is in /etc/systemd
On 04/29/2015 08:58 PM, Mark Lee wrote:
On Wednesday, April 29, 2015 07:17:53 PM Javier Vasquez wrote:
On Wed, Apr 29, 2015 at 3:51 PM, Mark Lee wrote:
...
Systemd usually logs startup in journalctl. Can you post your journalctl
output (from a time when you're
> On Wed, Apr 29, 2015 at 7:58 PM, Mark Lee wrote:
> ...
>
> Can you post the output of your /etc/logind.conf?
>
> Regards,
> Mark
Weird, I don't remember removing that file, but it's not there. I
remember I had in it the with the power button I wanted reboot, that
the Lid close did nothing, and
On Wednesday, April 29, 2015 07:17:53 PM Javier Vasquez wrote:
> > On Wed, Apr 29, 2015 at 3:51 PM, Mark Lee wrote:
> > ...
> > Systemd usually logs startup in journalctl. Can you post your journalctl
> > output (from a time when you're sure you had the issue)?
>
> Not sure how useful it is. Not
> On Wed, Apr 29, 2015 at 4:24 PM, Rodrigo Rivas
> wrote:
> ...
>
> You can enable the debug shell with:
>
> # systemctl enable debug-shell.service
>
> And then when the boot fails, switch to the debugging shell with
> CTRL+ALT+F9 and get the status of the system:
>
> # systemctl status systemd-l
> On Wed, Apr 29, 2015 at 3:51 PM, Mark Lee wrote:
> ...
> Systemd usually logs startup in journalctl. Can you post your journalctl
> output (from a time when you're sure you had the issue)?
Not sure how useful it is. Not sure if attaching the whole output,
but here it goes what related to login
On Wed, Apr 29, 2015 at 11:40 PM, Javier Vasquez
wrote:
> I haven't identified under which circumstances, when booting the
> system hangs, and the only thing that can be related to that is the
> message:
>
> Failed to start Login Service
>
> Of course the recommendation to see the output of:
>
> s
On Wednesday, April 29, 2015 03:40:33 PM Javier Vasquez wrote:
> I haven't identified under which circumstances, when booting the
> system hangs, and the only thing that can be related to that is the
> message:
>
> Failed to start Login Service
>
> Of course the recommendation to see the output o
On 04/29/2015 05:40 PM, Javier Vasquez wrote:
I haven't identified under which circumstances, when booting the
system hangs, and the only thing that can be related to that is the
message:
Failed to start Login Service
...
Yes I have seen this but only on one of my computers (laptop, wireless
I haven't identified under which circumstances, when booting the
system hangs, and the only thing that can be related to that is the
message:
Failed to start Login Service
Of course the recommendation to see the output of:
systemctl status systemd-logind.service
Is useless when that happens. T
20 matches
Mail list logo
