I have a Lenovo 330 laptop with Ryzen 5 processor. Ever since the first snapshot incorporating Linux 4.2.x it will not fully boot. If I edit the linuxefi line at boot time and append nomodeset, then it will boot okay. Unfortunately it will not awaken from suspend, so that’s a big suckeroo.
Any thoughts - anyone?
nomodeset creates a crippled X condition useful for little more than troubleshooting and reconfiguration. Is there still a 4.19 kernel in your Grub menu that you can boot to? If not, do you still have a snapshot you can roll back to that predates the first 4.20.x? What output do you get after first installing inxi, then within an X session running:
inxi -GxxS
rpm -qa | grep xf86-vid
cat /proc/cmdline
Do you have any optional repos installed?
zypper lr -d
Hi
There was another ryzen user having similar issues, adding the boot option iommu=soft helped, perhaps worth a try?
for mrmazda…
I have an old Clonezilla image of the 20190108 snapshot, with Linux 4.19.12. With the desktop being my primary machine, was hoping that eventually the laptop would get straightened out (like when the driver for the Lenovo 330 trackpad was not available and had to use a mouse).
for malcolmlewis…
Added amd_iommu=soft to grub default boot params - same result. 
What exactly does this mean? When it has booted as much as it will, what’s on the screen? Does Ctrl-Alt-F3 at that point do anything? Does it help any if instead of typing nomodeset you type plymouth.enable=0 before continuing? What if you replace splash=silent with splash=0?
About Clonezilla I can’t help. I don’t use it.
To be precise: The Lenovo 330 runs through the boot process, displaying the animated Tumbleweed logo. Then it flashes to a blank screen with an underline terminal cursor (nonblinking) in the upper left corner. It never progresses beyond this point (unless I use nomodeset). Normally the mouse cursor would appear in short order followed soon thereafter by the login screen.
Ctrl-Alt-F3 at this point does nothing.
plymouth.enable=0 dumps the boot process, but omitted the last few lines
splash=0 displayed additional terminal output lines, with the last screen being…
OK ] Started Apply settings from /etc/sysconfig/keyboard.
OK ] Started Name Service Cache Daemon.
OK ] Started Generate issue file for login session.
OK ] Started Avahi mDNS/DNS-SD Stack.
OK ] Started Bluetooth service.
OK ] Started System Logging Service.
OK ] Started NTP client/server.
Starting Authorization manager…
OK ] Reached target Bluetooth
OK ] Reached target User and Group Name Lookups.
OK ] Reachedtarget Host and Network Name Lookups.
Starting Login Service…
Starting Hostname Service…
OK ] Started Hostname Service.
OK ] Started Login Service.
OK ] Started Authorization Manager.
OK ] Started Modem Manager.
OK ] Started Update cron periods from /etc/sysconfig/btrfsmaintenance.
OK ] Started firewalld - dynamic firewall daemon.
OK ] Reached target Network (Pre).
Starting Network Manager…
Started bpfilter
OK ] Started Network Manager
Starting Fix for Network Manager…
OK ] Reached target Network.
Starting Login and scanning of iSCSI devices…
OK ] Started CUPS Scheduler.
OK ] Started Backupof /etc/sysconfig.
OK ] Reached target Timers.
Starting Postfix Mail Transport Agent…
Starting Network Manager Script Dispatcher Service…
Stopping Network Manager…
OK ] Started Network Manager Script Dispatcher Service.
OK ] Started Login and scanning of iSCSI devices.
OK ] Reached target Remote File Systems.
Starting Permit User Sessions…
OK ] Started Permit User Sessions.
Starting Hold until boot process finishes up…
Starting X Display Manager…
Starting WPA Supplicant daemon…
OK ] Stopped Network Manager.
OK ] Started WPA Supplicant daemon.
Starting Locale Service…
Starting wicked DHCPv6 supplicant service…
Starting wicked DHCPv4 supplicant service…
Starting wicked AutoIPv4 supplicant service…
OK ] Started Locale Service.
And that is where the machine hangs, at some point after starting Locale Service.
That is the most complete a description that I can provide - hope it helps.
As for Clonezilla, no help required. I am comfortable creating/restoring images.
Try appending 3 instead of nomodeset on a boot attempt directly subsequent to a normal boot attempt. If you can reach a login prompt you can examine the journal for the previous boot attempt:
journalctl -b -1
If you can’t reach a login prompt using a 3, try again instead using S or 1.
Please try the kernel parameter malcolmlewis posted,
Actually I did - although not precisely as he requested - as referenced in my 01:19 post above…
for malcolmlewis…
Added amd_iommu=soft to grub default boot params - same result.
Sensing some insistence from your post, I edited the linuxefi line at bootup, appending iommu=soft to the end (rather than the amd_iommu=soft from my earlier Grub2 edit).
That does the trick. Sorry for not following Malcolm’s suggestion - just assumed that the amd_ qualifier probably was necessary.
There is no such post in my browser window. However, post #4 has a 20:19 timestamp. We don’t all live in the same time zone, so it’s best to refer to other posts by number instead of time.
Sensing some insistence from your post, I edited the linuxefi line at bootup, appending iommu=soft to the end (rather than the amd_iommu=soft from my earlier Grub2 edit).
That does the trick. Sorry for not following Malcolm’s suggestion - just assumed that the amd_ qualifier probably was necessary.
The way you worded your response, it’s not entirely clear to me which worked, amd_iommu=soft or iommu=soft (I think the latter).
Glad malcolmlewis pointed to the right solution, and your ordeal is over with. 