You are not logged in.
Pages: 1
Hello,
I have recently updated my system and when booting into Arch it gets the login for TTY1 and then continues to print systemd processes therefore making me unable to log in. If I switch to TTY2 I am able to log in but as soon as I do, it continus to print more systemd messages, from here I can startx and run my system but if I try to suspend using
systemctl suspend
or
poweroff
the machine it fails due to waiting on systemd-udevd. If I look at my processes I have about 22 instances of systemd-udevd, which I never had before the upgrade.
journalctl -b
Output: https://pastebin.com/A8haxrat
dmesg
Output: https://pastebin.com/dDCMuqYn
I have attempted to downgrade the kernel which solves the suspend and poweroff issues but still hangs on TTY1 with "Loading/Saving Seed". I have no idea what has broken my system. If it helps my machine is corebooted and none of my other machines are having this issue.
Thank you
EDIT:
After attempting to suspend the machine, it can no longer take keystrokes.
Last edited by NarcoticNoble (2019-10-29 08:57:47)
Offline
I'm having exactly the same issue, also on a corebooted x230 (with Skulls) - Hope there is a solution soon.
Offline
Do your systems have enough entropy after boot?
Offline
cat /proc/sys/kernel/random/entropy_avail
returns 3694 so I don't believe this is the issue.
Offline
This may be a issue with corebooted thinkpads
My corebooted x220 also becomes unusable after installing 'linux-5.3.7.arch1-2'
I downgraded to linux-5.3.7.arch1-1 and all ok again.
fingers crossed the next kernel upgrade fixes this.
Offline
This may be a issue with corebooted thinkpads
My corebooted x220 also becomes unusable after installing 'linux-5.3.7.arch1-2'
I downgraded to linux-5.3.7.arch1-1 and all ok again.
fingers crossed the next kernel upgrade fixes this.
Do you have any idea when that patch may be released?
Offline
The only relevant change of that update was specifically enable kernel options to ease use for coreboot users, https://git.archlinux.org/svntogit/pack … cfdd43464a
If that config actively breaks your system now, you should post that in that bug report and request it to be reopened so that the change can be reevaluated.
Offline
Not a clue, but Arch rolls quickly, so hopefully not too long.
This is only the second time in 5 years an update has rendered this install unusable, and the first since I corebooted by x220 the last time it happened it was fixed before I could highlight an issue.
EDIT: see the response above given while I typed mine for detail
Last edited by Hootiegibbon (2019-10-29 10:17:32)
Offline
Downgrading to linux-5.3.7.arch1-1 fixes the issue for me now. Not sure what went wrong when I downgraded last time. I will post in the bug report shortly.
Offline
Offline
Thank you so much, this solution worked for me!
To be clear, I did the following:
Added line: blacklist gsmi
to /etc/modprobe.d/blacklist.conf
Upgraded linux, linux-firmware and linux-headers and all works now
Offline
Cheers!
blacklisting gsmi works on my corebooted (w/ seabios payload) x220
Offline
Pages: 1