Follow

PSA: If you're running Arch, DO NOT UPDATE FOR THE TIME BEING!!!

- Anyone running Dell XPS 15 laptops will have a bricked system

- Systemd hibernate is broken on laptops

You have been warned

@Skoll3 no, Manjaro has its own repos and is usually 2 weeks or so behind Arch stable

@cdmnky Thanks for the heads-up. I'm on a Dell XPS 13 but still heeding this warning. This made me think I should really subscribe to somesuch channels to get such warnings in future.

(just made my update script un-executable in case I attempt to run it for now! (force of habit))

@acrylicjam I only randomly saw a thread while browsing Reddit. There's nothing on any of the official news feeds or the forums right now

reddit.com/r/archlinux/comment

@cdmnky maybe I should go back to fuckin ubuntu at this point

@ivesen probably. The hibernation issue is definitely systemd

the XPS issue returns the error
/sbin/init: not executable

@ivesen @cdmnky reddit posts are an hour old, not enough time for a full investigation. We'll find out when its fixed.


But of course people will jump to conclusions prematurely
@cdmnky @ivesen oh of course warning people is the right thing to do
@cdmnky @ivesen that systemd breaks hibernation is almost certainly correct


that it breaks boot seems to be a lot less certain, we'll see

@kurisu @ivesen @cdmnky Yep, looks like it was.... I was going to write a similar reply as you. I was thinking corruption on user install. Can happen for kernels too. In this case it might be on a mirror but seems to be fixed already.

If corruption the machine definitely is not bricked. A quick fix with arch-chroot is usually the only thing that is needed.

@cdmnky @kurisu @ivesen That doesn't sound right... if everyone got their /etc/mkinitcpio.conf replaced with a pacnew (or something) it would show. Not sure what kernel that is. The kernel use by default 'CONFIG_FS_ENCRYPTION=m'...

'zcat /proc/config.gz | grep -i fs_enc'

It is more likely a user made change or specific non-common package the user use. It is probably easy to check.

@cdmnky Thanks. I suppose I should subscribe to the announcement mailing list.

@cdmnky Jokes on you, I run a non-systemd distro. So hibernation didn't work in the first place

@shibayashi @cdmnky
It seems that the problem occurs with Displaymanagers in combination with Systemd.
I have also arch but now display manager. updated everything and hybernation works out of the box most of the times. the other times it also didn't work in the past.

@Hetti @cdmnky
GDM was broken for me anyway for weeks now. Each time the lockscreen came up, I could see the clock and the wallpaper but it wasn’t possible to swipe away the screen to get to the password input field.

Arch is great and works. It’s mostly Gnome that causes problems for me.

I really should look into more minimal systems. Sway or another window manager.

@cdmnky
I wouldn't call it bricked if the problem is "/sbin/init is not executable".

The system is corrupted/unbootable, yes.

But for me, the word "bricked" means "beyond repair", or, at least, "the hardware is unable to boot ANY external software".

In this case, as far as I understand, the hardware/firmware is perfectly fine, it will still boot from a livecd/liveusb, with which you can fix your Arch installation.

@RandomDamage @cdmnky yeah but then you end up in initramfs without the rootfs mounted.

But if I had to, I'd do that, then read the initscript in initramfs to figure out the correct parameter to make it stop just before switch_root, then reboot with that parameter, chroot, and fix stuff.

@Wolf480pl @cdmnky if you have root={rootfs} you end up in the right place if it can do it at all. It's been my go-to for hard fail system recovery for decades now.

@RandomDamage @cdmnky

AFAIK this only works if you have no initramfs, and from my experience, most people either:
- are not very knowledgable about mounting root, and use the distro's default initramfs
- are knowledgable enough that they play with fancy stuff like cryptsetup or lvm, which require you to use initramfs

I haven't seen an initramfs-less system for a long time.

@Wolf480pl @cdmnky I suppose you are right.

Thinking about it, with zfs root it's where I would want to be anyway. It's not like it isn't obvious once you start poking at it.

Sign in to participate in the conversation
niu.moe

We are a cute and loving international community O(≧▽≦)O !