Can't boot Slackware after visiting The Dark (M$) Side...
by business_kid from LinuxQuestions.org on (#6MJ74)
Every 2-3 months recently I've been lighting up M$ windows to grab the updates, then vanishing again. This time, I can't boot Slackware. I'm on current of 2024-04-20, except for elogind-252.23-x86_64-3 & polkit-124. When booting, Slackware set up the internet & vpn. Then it hangs on the line Code:/lib64/elogind/elogind --daemon and a restart is needed :scratch:. That repeats ad nauseam.
I went saying bad things about windows, and reached for a liveslak usb made in March/April. It wasn't in my box or near the updates. But that hung at exactly the same spot, booting elogind. :confused:
I'm on ext4 all round here, so the only shared partition is the EFI partition. Windows did pick up some bugs in the updates, but I didn't hang around to sort them.
I get online successfully in Slackware64 and set up a vpn, so if elogind needs the internet it should be there. Internet is on the blink in windows (now you see it, now you don't).
So you're getting my slightly mystified post courtesy of Devuan on /dev/sda. Windows 11 was being upgraded to 22H2, and uses nvme0n1p3, with recoveries on p4 &p8. Slackware has nvme0n1p5-p7, /boot, / & /home resp.
The things I can vouch for are the main OS & the liveslak. Windows is what it is. But the linux/edlogind issues are caused by.......... what?
I went saying bad things about windows, and reached for a liveslak usb made in March/April. It wasn't in my box or near the updates. But that hung at exactly the same spot, booting elogind. :confused:
I'm on ext4 all round here, so the only shared partition is the EFI partition. Windows did pick up some bugs in the updates, but I didn't hang around to sort them.
I get online successfully in Slackware64 and set up a vpn, so if elogind needs the internet it should be there. Internet is on the blink in windows (now you see it, now you don't).
So you're getting my slightly mystified post courtesy of Devuan on /dev/sda. Windows 11 was being upgraded to 22H2, and uses nvme0n1p3, with recoveries on p4 &p8. Slackware has nvme0n1p5-p7, /boot, / & /home resp.
The things I can vouch for are the main OS & the liveslak. Windows is what it is. But the linux/edlogind issues are caused by.......... what?