Arch Linux

IMSOASIAN

Member

From: binary land

Registered: 2021-03-29

Posts: 11

Website

[SOLVED!] Arch Linux booting loops at '</TASK>'

Hello there!

This all started when I was getting a lot of visual glitches.

I restarted my system, however in doing so, Arch Linux no longer loads.

I checked my GRUB parameters, in case anything was going wrong:

I noticed that the debug level was set to 3, accompanied by the command 'quiet'.

I decided to set this to 7 (after reading about Linux debug levels online) and removed the 'quiet' option.

A ton of text flew by, but then I realized it would get stuck on something called '</TASK>' for a few minutes, and then some more text would scroll by and it would repeat.

Honestly, I'm out of options at this point. I've tried installing video drivers and updating via 'arch-chroot', but that doesn't seem to work either.

Does anybody know why this is happening?

And, preferably, does anyone know how to solve this?

Thanks,

-[K] IMSOASIAN

Last edited by IMSOASIAN (2022-01-25 19:59:16)

---

retardation has become mainstream

seth

Member

Registered: 2012-09-03

Posts: 51,348

Re: [SOLVED!] Arch Linux booting loops at '</TASK>'

udevd blocks - reset the debug level to "3", keep the "quiet" away and try to boot "nomodeset" and see whether that gets you a more digestable output.

Also try to install and boot the lts kernel (from the chroot - don't forget to mount the /boot partition!)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

IMSOASIAN

Member

From: binary land

Registered: 2021-03-29

Posts: 11

Website

Re: [SOLVED!] Arch Linux booting loops at '</TASK>'

udevd blocks - reset the debug level to "3", keep the "quiet" away and try to boot "nomodeset" and see whether that gets you a more digestible output.

Also, try to install and boot the lts kernel (from the chroot - don't forget to mount the /boot partition!)

Thanks for replying,

I changed the boot options as you said, and it actually boots into KDE! However, it only shows up on one monitor with the other screens not even being activated (i.e., in 'detecting input' mode).

I tried booting with the LTS kernel, but it didn't work (with or without initramfs).

So, how do I regain multi-monitor functionality?

It has something to do with the graphics driver, right?

-[K] IMSOASIAN

---

retardation has become mainstream

seth

Member

Registered: 2012-09-03

Posts: 51,348

Re: [SOLVED!] Arch Linux booting loops at '</TASK>'

If you added "nomodeset" you'll only get a display server on the VESA driver. That's not a solution.
However, you can now look at the journal for this or previous boots to get a better sight on the errors. ("sudo journalctl -b -1" for the previous one)

And yes: it's likely a problem w/ the DRM driver then.
What's the output of "lspci -k"?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

IMSOASIAN

Member

From: binary land

Registered: 2021-03-29

Posts: 11

Website

Re: [SOLVED!] Arch Linux booting loops at '</TASK>'

If you added "nomodeset" you'll only get a display server on the VESA driver. That's not a solution.
However, you can now look at the journal for this or previous boots to get a better sight on the errors. ("sudo journalctl -b -1" for the previous one)

And yes: it's likely a problem w/ the DRM driver then.
What's the output of "lspci -k"?

I did both, and I discovered a post on this forum that led me to my solution.

I got a line of error that stated the following:

systemd-modules-load: Failed to find module 'nvidia-uvm'

I searched up this error and found the aforementioned post that listed a solution to this problem, and I removed the package 'nvidia-utils'.

Since I wasn't using Nvidia's proprietary drivers, this worked.

Thanks for helping me find this solution!

Until next time,

-[K] IMSOASIAN

Last edited by IMSOASIAN (2022-01-26 05:23:02)

---

retardation has become mainstream