After recent system update EOS lags unusably

General system Newbie
1

I updated my desktop system’s packages recently, and after rebooting, it lags enough that I’m lucky to get 1fps. Nothing can be clicked, because some part of the software is still tracking cursor position, but actual position is not synced to visual position. No keyboard shortcuts function, because input to visual response lag exceeds 3 seconds.

I’m using two monitors (Primary: ASUS VP28U 3840x2160. Secondary: eMachines E12T5W 1440x900), and after the update, the primary monitor is automatically disconnected instantly.

System specs:
GPU: Radeon RX 580 Series (8 GB)
Ram: 32 GB (at 2133 MT/s)
CPU: AMD Ryzen 5 3600X 6-core (at 3.80 GHz)

2

What a nightmare for your first post.

Something got fubar’d on that we agree.

Endeavour has a PITA-looking rollback page (https://discovery.endeavouros.com/pacman/easy-downgrade-by-date/2021/06/) and if that was successful you still wouldn’t know which package sunk you.

Ironically there is a great thread about log posting (was it @UncleSpellbinder ‘s thread?) and under what circumstance in the troubleshooting process you should post which logs for which situation…it was so brilliant I didnt bookmark or remember how to find it :slight_smile:

stay patient for the Calvary. I’m responding only to bump this as it’s 2 hours old.

edit/redundancy

3

As said in the post above, to help the wizards of this forum with a possible answer, please post the link provided by those two commands :

inxi -Fxxc0z | eos-sendlog
and
cat /var/log/pacman.log | eos-sendlog

Edit : Maybe related to this problem ?

4

Here ya go…

5

Recommend you use a live ISO to collect the hardware information, will make it a lot faster…

6

@Bloghol
Post the full hardware output as has been asked above. You can post the url.

inxi -Faz | eos-sendlog

7

I don’t think that issue is the same as mine, though I can’t say for certain.

I’ll get to using those commands as soon as I can get things to work well enough that a live ISO functions.

Hopefully shouldn’t take more than a day or two, and I can’t imagine many (if any) issues preventing it from being a simple and smooth process, but I have limited time to work on this for the time being.

8

Here is the link it spat out for -Fxxc0z

And I couldn’t get the cat command to run:

cat:/var/log/pacman.log: No such file or diredctory
eos-sendlog-helper: error: No input!

Edit: -Faz command link

Edit2: all done via a live ISO via USB2.0 flash drive

9

You’ll have to chroot into your installed system to get the pacman logs.

10

I’ll do that soon; hopefully within the next day or two I’ll have time to do that.

11

Okay, so… after hunting things down by manually mounting all the relevant partitions, the file “/var/log/pacman.log” literally doesn’t exist. It never existed.

I think you wanted this text log, though? I got it by send-logging the “journalctl” command.
Let me know if I need to hunt down some other obscure nonsense, though. :face_exhaling:

Edit: spelling “/var/log/pacman/log” → “/var/log/pacman.log”

12

It is /var/log/pacman.log Is that a typo? Also you are on kernel 6.17.8-arch1-1 There is a newer kernel. When you arch-chroot you can also update the system so it is updated. Also there are newer UEFI Bios updates for this motherboard. B550M Steel Legend

13

Yeah, that’s my typo, lol.

/var/log/pacman.log does not exist, as a file on my machine.

For updates; I had used the command “sudo pacman -Syu” to attempt an update just a few days ago, which is what’s causing my current problems.

And for my mobo, I just haven’t had any issues with my UEFI setup. I’ll update if I ever have the time and inclination, but for now, it’s not causing any problems, as far as I know, so I don’t care.

If it is an issue, I’ll update the Bios, but…