*Participation Requested*
MicroOS Desktop Use to Help with ALP Feedback
-
Boot failure after security updates
Problem:
Security updates after upgrade, killed system.
Specifically, system won't boot using 5.3.18-150300.59.43 unless I use the "safe-mode" selection. Works OK 5.3.18-59.40-default kernel.
Symptom:
Screen goes dark after ramdisk loads, both monitor loose signal and no activity on harddrive after a few seconds.
Troubleshooting / Remediation Steps
1) Using [AMD/ATI] RS780L [Radeon 3000] card, so suspected Bug 1195142
Tried:
# mkdir /lib/modules/5.3.18-*.43-default/updates
# cp /lib/modules/5.3.18-*.40-default/kernel/drivers/gpu/drm/radeon/radeon.ko* /lib/modules/5.3.18-*.43-default/updates/
# depmod 5.3.18-150300.59.43-default
# mkinitrd
This didn't seem to change anything.
2) Removed quiet boot options and add debug, I see lots of boot-up activity and screen then goes black after about a minute. No red flags or errors that I could see, it just goes dark at 66 seconds. There is some radeon messages ~57 seconds, but no errors that I could see. Used cell phone to record scrolling and captured last frame before darkness.
Image
Request
I hate to run with an unpacked system, but I'm not sure how to get around this.
I welcome any suggestions on how to isolate or remediate the problem. Thanks in advance.
-
Re: Boot failure after security updates
Don't you still have the 59.40 kernel installed to boot from?
I only tried those bug instructions for one installation, though not exactly. Instead of to updates I copied over the original. After that one I've been installing the kernel from here instead of messing with the bad one. On my main installation I'm still running on 59.37.
Reg. Linux User 211409 *** multibooting since 1992
Primary: 15.3, TW, 15.1 & 13.1 on Haswell @earthlink.net
Secondary: eComStation (OS/2) &15.2 on i965P/Radeon
Tertiary: Debian, Fedora, Mageia, more on Rocket Lake & older Intel, AMD, NVidia....
-
Re: Boot failure after security updates
 Originally Posted by mrmazda
Don't you still have the 59.40 kernel installed to boot from?
Yes, I can boot to the old kernel, which is what I'm doing now. I just wanted to know the root cause so I can see when it's resolved and keep up with patches.
-
Re: Boot failure after security updates
I'm having the same problem. Now booting from 5.3.18-59-37. Are you saying that 5.3.18-150300.59.43 is from a bad repository? How to recover?
-
Re: Boot failure after security updates
This is the only weirdo I found in Yast: http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_$releasever/
I just now replaced it with: http://ftp.gwdg.de/pub/linux/misc/pa...SUSE_Leap_15.3
Am I supposed to be using https://download.opensuse.org/reposi.../pool/x86_64/? All the others use the same base: https://download.opensuse.org/
-
Re: Boot failure after security updates
 Originally Posted by HealingMindNOS
It's an option. It contains patches that are not in the 59.43 kernel, including one that solves the black screen problem with radeon GPUs.
Reg. Linux User 211409 *** multibooting since 1992
Primary: 15.3, TW, 15.1 & 13.1 on Haswell @earthlink.net
Secondary: eComStation (OS/2) &15.2 on i965P/Radeon
Tertiary: Debian, Fedora, Mageia, more on Rocket Lake & older Intel, AMD, NVidia....
-
Re: Boot failure after security updates
There's "me too" here. Following for resolution.
-
Re: Boot failure after security updates
Although the work-around didn't fix my problem, the Kernel update to 5.3.18-150300.59.46 did. Problem resolved.
-
Re: Boot failure after security updates
The current kernal that actually works likes like something from "Farscape." Here's my Kinfo:
Operating System: openSUSE Leap 15.3
KDE Plasma Version: 5.18.6
KDE Frameworks Version: 5.76.0
Qt Version: 5.12.7
Kernel Version: 5.3.18-150300.257.g6971cec-default
OS Type: 64-bit
Processors: 6 × AMD FX(tm)-6100 Six-Core Processor
Memory: 11.4 GiB of RAM
I included the OSS debug repositories on my last update.
-
AW: Boot failure after security updates
The actual problem should be resolved with the new kernel from Leap 15.3 by updating.
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|