Page MenuHomeSolus

can't boot in kernel 5.0.5
Closed, ResolvedPublic

Description

Hello,

I can't boot in kernel 5.0.5. When it's done booting, my main monitor blink black/grey and my other monitor stuck in tty.
If I disabled my sides monitors. I only have the blinking black/grey on the main monitor.
When i boot on 4.20.16 i have no problem.

The first time I thought that I messed up my install, so I reinstall Solus from sractch. But the problem still there.

I'm on a Dell 9570, without nvidia driver and nouveau blacklisted.

Thanks for your great product and help !

Event Timeline

henres created this task.Apr 11 2019, 8:26 AM
henres updated the task description. (Show Details)Apr 11 2019, 8:30 AM

What DE and is it an xps?

I'm on Gnome and yes, it's an xps.

Have you checked via systemd-analyze if backlight starts to late? XPS have often this issue on solus

The tty is unusable when boot to 5.0.5.

In 4.20, here the output:

$ systemd-analyze
Startup finished in 12.134s (firmware) + 9.855s (loader) + 1.811s (kernel) + 793ms (initrd) + 465ms (userspace) = 25.059s
graphical.target reached after 427ms in userspace

Looks to me like it got as far as GDM. I'd start looking at your Xorg log.

chax added a subscriber: chax.Apr 11 2019, 7:23 PM

Can you try to edit kernel options from bootloader? Select kernel and press 'e' (instead of enter) and then delete following from kernel options: 'quiet loglevel=3 splash systemd.show_status=false' and then boot by pressing enter. See what systemd prints out during boot.

henres added a comment.EditedApr 12 2019, 11:18 AM

Hello,

I have try this : delete following from kernel options: 'quiet loglevel=3 splash systemd.show_status=false'
I don't have time to read before it start to goes blinking. Before trying i have remove Xorg.log. When boot ended no Xorg.log was generated.

I join the journalctl -b log when on kernel 5.0.5 and the critical-chain.

Apr 12 13:10:11 henres-solus-9570 gnome-shell[787]: Failed to read EDID blob from eDP-1: No such file or directory
Apr 12 13:10:12 henres-solus-9570 gnome-shell[787]: Failed to apply DRM plane transform 0: Permission denied
Apr 12 13:10:12 henres-solus-9570 gnome-shell[787]: Failed to apply DRM plane transform 0: Permission denied
Apr 12 13:10:12 henres-solus-9570 gnome-shell[787]: Failed to apply DRM plane transform 0: Permission denied
Apr 12 13:10:13 henres-solus-9570 gnome-shell[787]: Failed to read EDID from 'eDP-1': No such file or directory
Apr 12 13:10:13 henres-solus-9570 gnome-shell[787]: Failed to read EDID from 'eDP-1': No such file or directory
Apr 12 13:10:13 henres-solus-9570 gnome-shell[787]: Failed to read EDID from 'eDP-1': No such file or directory
Apr 12 13:10:13 henres-solus-9570 gsd-color[1024]: could not find device: property match 'XRANDR_name'='DP-7' does not exist
Apr 12 13:10:13 henres-solus-9570 gnome-shell[787]: Failed to set CRTC mode 1920x1080: Permission denied
Apr 12 13:10:13 henres-solus-9570 gnome-shell[787]: Failed to set CRTC mode 1920x1080: Permission denied
Apr 12 13:10:13 henres-solus-9570 gnome-shell[787]: Failed to set CRTC mode 1920x1080: Permission denied

This says to me that something is up with display detection. When and why did you start blacklisting nouveau?

henres added a comment.EditedApr 12 2019, 12:15 PM

I'm on Dell xps 9570 connected to a dock dell thunderbolt 3 tb16, who have a dp connector. But i don't use the dp port. Only vga and hdmi.
To boot this laptop we need to blacklist nouveau. I currently use the intel iGPU.

The blinking screen appear when the computer connected or not to the dock. It's not related.
But i can't access to the tty on kernel 5 if i don't have an external screen.

I just find a similar problem here: https://bugzilla.redhat.com/show_bug.cgi?id=1695275

It seem to be related to kernel 5 and not solus.
It looks like to be fix in 5.0.7. I will try when the new patch come to solus.

Alright, if 5.0.7 fixes it I'll make sure it hits Unstable this weekend.

Alright, if 5.0.7 fixes it I'll make sure it hits Unstable this weekend.

That's the best customer support I have ever seen. And I worked with lots of different suppliers ! 👍

Thanks a lot guys !

Girtablulu edited projects, added Software; removed Lacks Project.

Hello guys,

I have installed kernel 5.0.7 and it doesn't fix the problem. :(
I still think it's a kernel problem. So for now I'll wait for next kernel.

Thanks

Ok, just reread the issue in redhat buzilla, it's the 5.0.7-200 kernel that fix it. The last kernel installed by solus is the 5.0.7-114.
I'll wait for another version.

200 is their release number, not part of the kernel version. Looks like they had to manually apply https://patchwork.freedesktop.org/patch/296408/ to fix it. I'll look when I have time this week.

DataDrake triaged this task as High priority.Apr 30 2019, 1:46 PM
DataDrake closed this task as Resolved.May 5 2019, 6:46 PM

This should be fixed with this week's upcoming sync.

Hello,

I still can't boot in 5.0.12 but it works with 5.0.16.

So ok for me !