Siduction Forum

Siduction Forum => Upgrade Warnings => Topic started by: titan on 2020/12/29, 09:11:14

Title: Kernel: 5.10.3-towo.2 (fixed)
Post by: titan on 2020/12/29, 09:11:14

After du this morning PC fail to continue beyond grub screen. Reverting to previous kernel everything works fine.

Code: [Select]

CPU: Quad Core AMD Ryzen 5 2400G with Radeon Vega Graphics (-MT MCP-) speed/min/max: 1418/1600/3600 MHz 
Kernel: 5.10.3-towo.1-siduction-amd64 x86_64 Up: 10m Mem: 2651.6/6943.6 MiB (38.2%) Storage: 1.34 TiB (29.5% used) Procs: 261 
Shell: Bash inxi: 3.2.01
 




Title: Re: Kernel: 5.10.3-towo.1
Post by: towo on 2020/12/29, 09:19:17

And that should help me how?

Your post is the same as:

Code: [Select]

CPU: 8-Core AMD Ryzen 7 2700X (-MT MCP-) speed/min/max: 2188/2200/3700 MHz Kernel: 5.11.0-rc1 x86_64 Up: 1h 06m
Mem: 2433.0/32098.9 MiB (7.6%) Storage: 6.14 TiB (13.9% used) Procs: 404 Shell: Bash inxi: 3.2.01Works fine, and now?

Title: Re: Kernel: 5.10.3-towo.1
Post by: titan on 2020/12/29, 09:40:00

Not sure what you mean, there was a new kernel today (and grub) when I restart after du with new kernel it gets to grub with latest kernel and then screen goes black with no cursor. this is with  Kernel: 5.10.3-towo.1 you have kernel 5.11.0. When I reboot with last kernel all works fine. Or did you mean I have not supplied enough information to be useful, what do you need.

Title: Re: Kernel: 5.10.3-towo.1
Post by: towo on 2020/12/29, 09:50:57

Yes, to less informations.
At minimum you should provide the journal from the failed boot. As you can see, Kernel works fine here:

Code: [Select]

CPU: 8-Core AMD Ryzen 7 2700X (-MT MCP-) speed/min/max: 2058/2200/3700 MHz Kernel: 5.10.3-towo.2-siduction-amd64 x86_64 Up: 1m
Mem: 1851.6/32096.8 MiB (5.8%) Storage: 6.14 TiB (13.9% used) Procs: 427 Shell: Bash inxi: 3.2.01
Its at least kernel 5.10.4-rc1.

Title: Re: Kernel: 5.10.3-towo.1
Post by: titan on 2020/12/29, 10:33:54

Is this the log you want.

Title: Re: Kernel: 5.10.3-towo.1
Post by: towo on 2020/12/29, 10:50:25

There is no problem in your logfile.
2nd question, you say kernel 5.10.3-towo.1 fails to boot, but you post a inxi output with that kernel.
How is that possible?

Title: Re: Kernel: 5.10.3-towo.1
Post by: titan on 2020/12/29, 11:01:08

I  said today's kernel update failed to boot  5.10.3-towo.2 . I was posting from my PC with the previous kernel  5.10.3-towo.1

Title: Re: Kernel: 5.10.3-towo.1
Post by: towo on 2020/12/29, 11:03:37

Read your Threadtitle and change it!

Title: Re: Kernel: 5.10.3-towo.2
Post by: titan on 2020/12/29, 11:08:46

Apologies  :-[

Title: Re: Kernel: 5.10.3-towo.2
Post by: towo on 2020/12/29, 11:10:35

And that logfile is useless, since it is from kernel 5.10.3-towo.1.

Title: Re: Kernel: 5.10.3-towo.2
Post by: Pip on 2020/12/29, 12:07:51

I did an upgrade to 5.10.3-towo.2 this morning with no problems, so it doesn't seem inherently in the kernel (which towo would have spotted before releasing anyway).
titan, have you tried booting with an init=/bin/bash option? If that works, maybe boot into single user mode, the command line mode. If you get that far, it would then seem a GUI issue - screen driver, perhaps?
With a black screen, what happens if you press Ctrl-Alt-F1?

Title: Re: Kernel: 5.10.3-towo.2
Post by: towo on 2020/12/29, 12:15:47

It seems, that kernel has a problem with vega graphics.
I can reproduce the issue on my notebook. I will investigate, if i find the problem.
It is then an upstream issue, hopefully it will get fixed, before the release of kernel 5.10.4.

Title: Re: Kernel: 5.10.3-towo.2
Post by: titan on 2020/12/29, 14:05:59

From journalctl  when loading SDDM there are a lot of errors of the type

Code: [Select]

TypeError: Cannot read property


Title: Re: Kernel: 5.10.3-towo.2
Post by: titan on 2020/12/30, 10:33:11

With du this morning and new kernel 5.10.3.towo.3 all is good again thanks