Aggregated 5.10 Issues

alec685

A question? I have not updated the roundup 18 yet, So i do not have kernel 5.10, Should I update or I need to wait

littlebitjumpy

I continue to have the gray screen of no-boot, on an HP AMD A10 notebook, now with a fresh install of Solus 4.1 Budgie. Standing O to Josh for the heavy lifting on this issue. Spamming the spacebar to get the kernel menu is working for me to get me into the system, but after the newest updates I no longer see 5.6 (which was working for me). Current choices:

 solus-current.5.4.12-144.conf
 solus-current.5.10.2-164.conf
 solus-current.5.10.4-165.conf

Only 5.4 lets me boot in to Solus. Everything seems to be functioning just fine on 5.4, although I'm still tweaking Budgie.

I'll keep checking back here for more news, but any hope of a fix that will let me boot normally into 5.10?

More details:
I know my way around a command line, but am not an advanced user. I happily came to Solus a few years ago after going from Mint to Kubuntu. I have an HP Notebook, AMD A10-9600P/Radeon R5 with Insyde BIOS F.24 (a very limited BIOS). I converted the machine from Win10Home to Solus; HP offers a BIOS update for this machine only for Windows, via .exe, which I'm assuming I should not try to run on Solus!

I was on Solus 4.1 Plasma when I ran the Dec. 14 updates and lost the ability to boot into the OS. I get a gray screen with no cursor. A ragged horizontal line of pixels flashes toward the bottom of the screen with POST (I think that's what's happening), and then gray screen 4eva. I came here and saw the discussion around sddm being a possible culprit, so I backed up my data using the live image, and did a clean install of Solus Budgie from the latest image, hoping the flagship DE would solve the problem. No joy.

Chrym

littlebitjumpy

I'm also on HP EliteBook AMD Machine and there is a way for updating the BIOS: you need a Windows Machine (VM works also - if VBOX would work 😃 ), download the .exe, double klick the .exe in Windows and create a USB Stick. Reboot your HP and spam F2 (if I remember right), then you can update your BIOS with the USB Stick.

I guess, the old AMD APUs are very low prioritized in bugfixing in general

timbba

I have Dell Precision 5540 with Nvidia Quadro T2000 but I'm using only Intel GPU at the moment.

For me 5.10.4-165 doesn't work when I use the laptop with Thunderbolt Dock WD19TB (there is Dell Ultrawide monitor attached to dock using DP). But if I boot 5.10.4-165 without the TB dock, it boots just fine --> once attaching the dock, it freezes immediately with blank screen.

So due to that, I noticed this:
https://mailman.alsa-project.org/pipermail/alsa-devel/2021-January/178794.html

And I found it out from this thread (#52 message):
https://www.linuxquestions.org/questions/slackware-14/kernel-5-10-4-i915-and-dual-screen-freeze-on-intel-gpu-4175687776/

Is this patch worth trying? Is it possible to try out by manually adding it into some test kernel build?

PS. I'm using now 5.10.1-162, which works ok.

timbba

By continuing to follow the thread above (linuxquestions.org), the following fixed the dual screen freeze problems for me:
# /etc/modprobe.d/snd_hda.conf options snd_hda_codec_hdmi enable_silent_stream=N

But sound is not working via HDMI/DP now. I can live without it, because I never even needed it 🙂

JoshStrobl

timbba Just an FYI, that change will not be necessary as of our 5.10.5, which includes a backport to fix a deadlock regarding the Intel silent stream code. This is in unstable at the moment, just doing kernel module rebuilds, and stable users can expect it tomorrow.

timbba

Weird, I cannot edit my older post... so therefore I will just inform that sound works ok with HDMI/DP too. I guess it was some hickup earlier when using enable_silent_stream=N option. It seems to work now with that option too 🙂

DDariusA

If there's a beta .iso for 4.2 (or 4.1 with 5.10 kernel) I'm open for testing too.

JoshStrobl

No, we don't put out beta or testing ISOs.

JoshStrobl

@Lucien_Lachance Could you test something for me? Could you install gdm and modify gdm's service file (via sudo nano /usr/lib64/systemd/system/gdm.service) to have After=systemd-udev-trigger.service? There's a comment where it says # replaces plymouth-quit since it quits plymouth on its own with empty Conflicts and Afters, you can add the systemd-udev-trigger.service there.

Just using this gdm issue as a reference. I know we're not using Wayland, but the premise of the devices not being available by the time GDM starts may still be the issue you're facing, since you can swap to and from a TTY to fix it.

Lucien_Lachance

JoshStrobl
ill try to get that done tonight..but not right now, no time

Lucien_Lachance

JoshStrobl no change

just to make sure i did it correctly:

[Unit]
Description=GNOME Display Manager

# replaces the getty
Conflicts=getty@tty1.service
After=getty@tty1.service

# replaces plymouth-quit since it quits plymouth on its own
Conflicts=
After=systemd-udev-trigger.service

# Needs all the dependencies of the services it's replacing
# pulled from getty@.service and 
# (except for plymouth-quit-wait.service since it waits until
# plymouth is quit, which we do)
After=rc-local.service plymouth-start.service systemd-user-sessions.service

# GDM takes responsibility for stopping plymouth, so if it fails
# for any reason, make sure plymouth still stops
OnFailure=plymouth-quit.service

JoshStrobl

Lucien_Lachance No rush 🙂

henetic

Today's update to 5.10.5-167.current fixed all issues with crashing when using the external display for me.

JoshStrobl

Lucien_Lachance Yep that looks right, was worth a shot. Could I get a pastebin with the journalctl for that boot please?

Lucien_Lachance

JoshStrobl allright, for a later boot though, but with the changes still intact
https://hastebin.com/ijanofiros.yaml

ReillyBrogan

@JoshStrobl Here's mine as well with the latest linux-current kernel and the systemd unit file change.
https://hastebin.com/zizivitime.yaml

Lucien_Lachance

@JoshStrobl
josh, unless the gmd issue was solved with yesterdays update (i was so busy messing with a new nvme and also trying out kde i lost a bit track of when this could have happened) i think i may have discovered something

as i said, i got a new nvme, so now i have 2. one contains solus budgie/gnome/gdm encrypted, the 2nd one contains my data, also encrypted. after some research on how to automatically decrypt and mount the data nvme i ended up with a howto i can show u if u need it.
in any case the result of this auto decryption is that bootup takes longer, between the regular decryption screen and loginscreen it halts for maybe 2 seconds, i guess to decrypt the data nvme, and i get some text on the screen with the asterikses from the manual decryption earlier, anyway, this pause makes gdm appear as it should do. tried it 3 or 4 times now, gdm appears every time

thought maybe this could help in the hunt for a fix

edit: i can still help debug, got solus installed on an ssd as well, without the autodecryption. this one still needs tty for gdm, just tested

Chrym

Kernel 5.10.5 is working also for me and my AMD APU Laptop.

tflovik

Today i installed Solus Budgie on a Lenovo Ideapad S340 with the AMD 3500U processor.
Upgraded after install and as far as i can see so far everything is working as it should. I had Linux mint on this laptop before and had to use the 5.8 kernel on that but still it stopped occasionally with the boot process.
I hope to use this distro for a long time 🙂

« Previous Page Next Page »