It seems to boot normally to the point where it should display on screen, but screen remains blank. Waited a few minutes. (tried twice) The previously installed kernel-desktop-4.14.50-2.mga6 continues to work normally.
please reproduce the issue with the new kernel, then boot the old kernel and run, as root: journalctl -b-1 > newkernel.txt and journalctl -b > oldkernel.txt and attach both files to this bug report
Assignee: bugsquad => kernelCC: (none) => marja11Keywords: (none) => NEEDINFO
Created attachment 10294 [details] journalctl log ; new kernel with problem, truncated to file limit size
Created attachment 10295 [details] journalctl log ; old kernel which works. Note there are 3 error messages/warnings which display, but everything seems to work properly. They may be due to using a usb key for important data. It has 2 partions, both in fstab, mounted under my user account. (It allows easy transfer to another computer if problems.)
Let me know if you want the entire newkernel file. It doesn't seem useful, since the video error messages seem to repeat a lot.
Keywords: NEEDINFO => (none)
Is radeon-firmware installed ?
CC: (none) => tmb
It wasn't, but installing radeon-firmware didn't help. Same symptoms. The disk churns continuously without any display once selecting the kernel to start, long after the first display usually appears (in maybe 15 seconds). The previous kernel still works nicely. (with the same 3 error/warning msgs) Before there were only 3 radeon packages installed (all required by other pkgs) : lib64drm_radeon1-2.4.91-1.1.mga6.x86_64 libdrm_radeon1-2.4.91-1.1.mga6.i586 radeontool-1.6.3-7.mga6.x86_64
You need to re-create the initrd after installing the radeon-firmware... if you boot to 4.14.50-2, then as root in a terminal: dracut -f /boot/initrd-4.14.56-desktop-1.mga6.img 4.14.56-desktop-1.mga6 and then you can try to boot into 4.14.56 again
With recreated initrd, works like a charm. (with the same 3 error/warning messages I had with previous kernels.) Thanks Thomas ! Why didn't wasn'r radeon-firmware needed before ?
I should have closed this as invalid
Resolution: (none) => INVALIDStatus: NEW => RESOLVED