2023, 11:37 a.m. Adrian Vovk,
wrote:
> Without the debug logs this is just a blind guess, but could it possibly
> be this issue: https://github.com/systemd/systemd/issues/27436?
>
> Best,
> Adrian
>
> On Sat, Apr 29, 2023, 19:20 Caeri Tech wrote:
>
>> So my next ques
So my next question is under what circumstances does systemd issue this
message?
On Tue., Apr. 25, 2023, 9:18 a.m. Caeri Tech, wrote:
> Interesting. If I downgrade systemd and systemd-libs from 253 to 252 it
> works as before.
>
> Is there perhaps a dependency that I'm now re
Interesting. If I downgrade systemd and systemd-libs from 253 to 252 it
works as before.
Is there perhaps a dependency that I'm now required to include in the
initramfs config?
On Tue., Apr. 25, 2023, 4:54 a.m. Lennart Poettering, <
lenn...@poettering.net> wrote:
> On Di, 25.04.2
ing
wrote:
> On Fr, 21.04.23 18:36, Caeri Tech (caerit...@gmail.com) wrote:
>
> > I've been running Linux from RAM for a couple years without issue.
> > However, since the upgrade from 252 to 253 the load to RAM fails and the
> > computer hangs with the message b
I've been running Linux from RAM for a couple years without issue.
However, since the upgrade from 252 to 253 the load to RAM fails and the
computer hangs with the message below:
[!!] Failed to start up manager.
[ 439.264894] systemd[1]: Freezing execution.
What does this message mean and w
