Aggregated 5.10 Issues

treehouse55

Not sure if related, but got no sound on my Acer Swift 3: https://discuss.getsol.us/d/6001-suddenly-no-sound-after-update. Running latest KDE, kernel 5.10.1-162.current.
cat /proc/asound/cards
Tells me I have no soundcards.

Temporary fix: Spamming space at boot, choosing previous kernel. In this case 5.6.19-159.current.

ReillyBrogan

FYI I just tested 5.10.2 and it does not help with the DisplayPort/Navi1 issues (not that I expected it to given nothing in the changelog looked related). I say Navi1 because my 5500XT is also affected and that indicates that the issue is likely architecture-wide. Just saving you some time from testing that yourself @JoshStrobl .

tedi

Hello, is there any way of reverting to linux-current-5.6.19-159-1-x86_64.eopkg if I don't have it anymore in list kernels? Can I download it from somewhere? Thanks!

H6LS1S

tedi Good news, gdm ran without magic on kernel 5.6.19-159. If you have a black screen with a blinking cursor after updating Solus 4.1 + Gnome, the way to fix is:

Install older kernel sudo eopkg it https://mirrors.rit.edu/solus/packages/shannon/l/linux-current/linux-current-5.6.19-159-1-x86_64.eopkg
Set kernel sudo clr-boot-manager set-kernel com.solus-project.current.5.6.19-159

Perhaps these steps do not need to be done, but it certainly will not be superfluous.

Rebuild eopkg database sudo eopkg rdb

Reconfiguration system sudo usysconf run -f

Spam the <Space> during reboot
Select the installed kernel using the arrows
Press <d> to set it as the default kernel

Solution works on:

Dell Latitude E5570 ( i5-6440HQ + HD Graphics 530 | Solus 4.1 + GDM 3.38.2.1 )

Silgrond

I am having performance-related issues on my Asus E403 laptop. I am mostly just browsing the internet and playing a java game (Oldschool RuneScape, namely the RuneLite client), in which I have noticed that my fps has dropped to its half as if I was switching to battery-mode with TLP. For now, I have switched back to the previous kernel, but I would like to provide logs. What commands do I have to submit here?

henkesteen

Silgrond
I had some performance issues as well. Posted about it here:
https://discuss.getsol.us/d/5977-what-just-happened-last-update-slowed-down-my-computer-a-lot

The solution worked, but it seems like it "gets slow" again, after wake-up from suspend.......

Edit: I actually ended up just removing TLP all together...... ATM I'm using AC all the time anyway. Will probably install it when stuff works again.

polomi

I noticed that today's update includes a new kernel version. Given that only one older version is kept around, I'm afraid that upgrading will wipe the 5.6 kernel from my machine, which is the only one that currently works. Is there a way to mark this specific version to be kept around longer? Otherwise, I might need to hold off from updating for now.

I didn't hear anything here about it, so I assume that the new kernel does not fix the issues, which would render my point moot.

MysteryGrayLeaf

5.10.2-164 is borked for me. However, the amdgpu-test-2/linux-current-5.10.1-163-1 one works.

Lucien_Lachance

no diffence here, still have to tty for gdm (yes i went back to gnome, still 5700 xt)
otherwise all seems to be fine except i have no idea what haskell is

UncleSlacky

Still no improvement with the latest updates - but at least the 5.6 kernel is still listed as a boot option. Weirdly, sometimes (maybe 30-40% of the time) when booting from AC the display is fine, whereas it's always flickery/jumpy when booting on battery.

H6LS1S

i5 6440HQ ( HD Graphics 530 ) Managed to run gdm on kernel 5.10.2-164 via tty ( sudo systemctl start gdm ) with installed tls ( 4.14.201-162 ) kernel 🤨, without tls kernel - gdm didn't respond at all. Tried a couple of days earlier on the kernel 5.10.1-162, nothing came of it

X11 gives an error that the screen was not found

H6LS1S

I just rebooted and all attempts to fix this are in vain, gdm is only runed manually:
1) Alt + F2
2) sudo systemctl stop gdm
3) sudo systemctl restart gdm

dostana

H6LS1S I do have the same issue manually has to load to previous kernel. Tried to look for boot file to make changes bit difficult for me.

gozo

H6LS1S bug still present - having the same issue, even after latest updates system won't boot. However, your workaround works - at each reboot have to manually stop and restart gdm. Thanks to Solus team for working on the issue!

dostana

dostana fixed the default kernel pointer to the working kernel.
I had 3 kernels in the list 5.10.1-162, 5.10.1-163, 5.10.2-164, only one kernel is working 5.10.1-163 and default point was at 5.10.2-164. Used

clr-boot-manager list-kernels
clr-boot-manager set-kernel com.solus-project.current.5.10.1-163

tedi

H6LS1S Thank you!

henetic

H6LS1S Thanks a lot, this fixed it for me. Had issues with my external display going blank after disabling my primary display (notebook display which I have turned off in my daily setup). Due to my setup, this happened right after login.
Switching to linux-lts also did the trick, but it made my system slow as hell, laggy and have 100% CPU usage, which opened another rabbit hole which I did not want to go into.
Do you happen to have an idea what the issue is with the kernel 5.10.4-165 that suddenly causes this display issues and if this is going to be fixed in next kernel versions? My Solus already wants me to update to the faulty 5.10.4-165 through Software Center.

UncleSlacky

Here's the hastebin link to my journal: https://hastebin.com/irojenemik.yaml
Hardware is an Asus Vivobook X407MA (Intel Pentium Silver N5000 CPU) with Intel UHD Graphics 605, driver: i915
Apparently it's a generation 9.5 (Gemini Lake) GPU. I've been working my way through the suggestions on the Arch Wiki to help with flickering and artifacts in general, the best result so far was with "Option "NoAccel" "True"" in xorg.conf, which stopped the sidescrolling and most of the flickering, except when running fullscreen windows, which "maximized" to the left half of the screen only. I'm still working my way through the various combinations of kernel parameters and xorg options (the kernel parameters on their own don't seem to make any difference).

Edit: I'm going to try updating the BIOS too - looks like I'm a few versions behind the latest one.

UncleSlacky

Updating the BIOS seems to have done the trick! So, if anyone else has an Asus Vivobook X407MA and/or a Gemini Lake GPU, make sure your BIOS is up to date...

Chrym

Since the 5.10.2-164 is not solving my issues, I need a working system. Is there any possibility to uninstall the 5.10 kernel without messing up the system and any dependencies? VirtualBox does actually not work because of installed 5.10 kernel and booted 5.6 kernel. I hope, with uninstalling the 5.10 kernel VirtualBox is running again.

BTW:
sudo clr-boot-manager set-kernel com.solus-project.current.5.6.19-159

is on my system not reboot persistent. Also i have changed the default kernel in GRUB with "d", which is also not reboot persistent.

Lucien_Lachance

im no good at reading tech documents but might the amd issue be fixed in 5.10.4 ?
https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.4

JoshStrobl

Lucien_Lachance Most of the commits there I've already backported, so if it hasn't fixed your issue already then chances are .4 isn't going to either: https://dev.getsol.us/source/linux-current/browse/master/files/amd/

But we'll see either today or tomorrow, will get the kernel updated then. I'll also be updating our internal linux-next to 5.11-rc1 and putting an eopkg on the web server so if anyone wants to tinker with that (assuming I don't run into any problems rebasing our apparmor patches for snap) they can install it. It'll only be for those that don't have any other kernel modules / drivers (e.g. broadcom-sta, nvidia, virtualbox, etc.). At least we'll know then if any of the drm changes that landed in 5.11-rc1 resolve it.

« Previous Page Next Page »