this post was submitted on 22 Aug 2024
171 points (98.3% liked)
Linux
48323 readers
749 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Well, since Cosmic isn't going to be ready for a couple years yet, let's try to fix your multimonitor issue. Are you running on Wayland and what's your GPU?
Wayland, Lenovo idepad 1 2018 (Ryzen 3) second monitor is Arzopa A1 GAMUT SLIM
I'm guessing that's the onboard AMD graphics then?
If you do an
lspci -k | grep -EA3 'VGA|3D|Display'
what does it return? Are you able to find anything in dmsg (journalctl -xb-1
for previous boot log) that would give an error message to investigate?here is what I got
04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mendocino (rev c2) Subsystem: Lenovo Device 380e Kernel driver in use: amdgpu Kernel modules: amdgpu
I don't think I understand what I'm reading but here is all the error I could find: https://rentry.org/gni28ogyMight have to get the full log, and it should be from immediately after one of those unexpected reboots. The flag
b-1
indicates journalctl to export the logs from the previous boot (-1) instead of the current log. So if you dosudo journalctl -xb-1 > log.txt
after one of these reboots and paste that file to look at, we might get something useful.I'm fairly confident that's a problem that can be fixed with having an AMD graphics driver running. If it were nVidia, I'd be less confident.