Aggregated 5.10 Issues

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

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 )

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.

JoshStrobl

@Lucien_Lachance @polomi If you two want to test 5.11, below is the installation command for it.

Note for you folks and anyone else reading this: This is the first release candidate of the 5.11 kernel and may have considerable bugs or other issues. Building on that, this is an internal build for mostly the Solus team to perform kernel validation, and as such we do not provide any support or other drivers for it, e.g. NVIDIA, broadcom, virtualbox, etc. Don't like it? Don't use it.

sudo eopkg install https://getsol.us/sources/linux-next-5.11.0-18-1-x86_64.eopkg

Spam spacebar on boot, select the 5.11 option. If it doesn't work, reboot into your preferred kernel and do: sudo eopkg remove linux-next to nuke it.

Lucien_Lachance

JoshStrobl made no difference, still got the gdm bug (which doesent bother me much anyway, just wanna help out so u can go 4.2)

so nuking it as suggested
thanks providing it

JoshStrobl

Lucien_Lachance Thanks for testing, unfortunate we didn't have better results.

ReillyBrogan

@JoshStrobl Yep, can confirm that the 5.11 RC kernel doesn't help the AMD DP issue. I also built a kernel with 5.10.4 (disabling all the /amd patches beforehand) and that was also not effective at fixing the issue.

JoshStrobl

5.10.4 has, as expected, no meaningful difference for Solus users. As it turns out, out all the patches I've backported for AMD, only one of them has actually been merged in. 🤦‍♂️ So yea, if it didn't work before it won't work now.

Currently cooking on the build server, then the usual routine of kernel module / driver rebuilds. But commit itself is here.

polomi

Had a long day, so I'll only be testing tomorrow. Should I bother with 5.11? Looks like it doesn't work, but I'll still give it a shot just in case. Or whatever Josh is cooking. 😁

JoshStrobl

polomi Nah, didn't fix it for @Lucien_Lachance so probably not going to for you either. No changes in any of the 5700xt related issues on amd's drm issue tracker either :\

ReillyBrogan

@polomi Considering I have the same issue and I've already tested the 5.11 kernel and my own built 5.10.4 kernel I suspect there is little point in you trying either unless you want to.

@JoshStrobl Could you add

 -j`nproc`

to the end of line 49 in the linux-current package file? I have to keep adding it after every git reset and without it builds are significantly slower (it tells the kernel compilation to use as many threads as the system has reported CPUs). I can make a PR for this if that's better.

JoshStrobl

No, I'm not going to do that and that's the completely wrong way to approach the problem. Copy /usr/share/defaults/eopkg/eopkg.conf into /etc/eopkg/eopkg.conf (you'll need to make the directory) and change the job count to your liking.

JoshStrobl

henetic There are multiple issues ranging from i915 changes, to amdgpu dc changes, to DisplayPort-related changes, to DPMS changes. I've elaborated on this throughout the thread.

There is no indication that many of those issues are going to be fixed. Others have already tested the 5.11-rc1 I built with the drm-tip merges in and there's been no changes for them. Many of the issues reported have been reported in other operating systems, some issues upstream being reported for 7 months or so now with no resolution.

« Previous Page Next Page »