I got a new laptop (Thinkpad Ryzen 5) and I am trying to install tumbleweed.
The install went fine, but when the system rebooted from the SSD, the boot hangs.
There is another thread about a bad firmware update that results in people not being able to boot, so I thought that might be my problem. I downloaded the older firmware and I think I installed it correctly, but I am still unable to boot the new install.
Does anyone have any ideas why a fresh install from the tumbleweed net-install iso would be unable to boot from the SSD?
You need to give details on what “cannot boot” and “boot hangs” mean. What appears on the screen when you try? When it appears to be hung, what happens if you key Ctrl-Alt-F2?
On one of mine, the only things to follow ‘Started Locale Service.’ are two Samba Daemon lines, the the welcome message, eth0 line, and login prompt, so you got rather well along in the boot process.
Have you tried non-default booting?
1-choose failsafe selection from Grub menu, or
2-append or remove nomodeset to/from the linux line using the e key on the default Grub selection, or
3-starting in single mode, appending S to the end of the line as in #2 above, or
4-turning off plymouth, as in #2, but appending string plymouth.enable=0 instead
If you can get logged in in any manner then you can look for failure clues with journalctl.
Hey, thanks alot for your reply. My grub menu does’t have a failsafe option, but
the nomodeset parameter did the trick and now my system is functional.
You’re running on the ATI X driver. Good chance that modesetting is better, and amdgpu is better still. With Raven ridge I can recall only about two things that might work to make the switch:
1-uninstall xf86-video-ati
2-specify that either the modesetting or the amdgpu driver be used via /etc/X11/xorg.conf.d/50-device.conf, in this fashion:
You might need a cmdline option that I don’t remember how to figure out. Also there might be one or more optional components amdgpu requires that are not installed.
Hi
For that GPU, there should be no need as amdgpu is the default for that card…
modinfo amdgpu | grep 15DD
alias: pci:v00001002d000015DDsv*sd*bc*sc*i*
zypper se -i amdgpu
S | Name | Summary | Type
--+----------------------+------------------------------------------------------------------+--------
i | libdrm_amdgpu1 | Userspace interface for Kernel DRM services for AMD Radeon chips | package
i | libdrm_amdgpu1-32bit | Userspace interface for Kernel DRM services for AMD Radeon chips | package
i | xf86-video-amdgpu | AMDGPU video driver for the Xorg X server | package
The two cards in my HP laptop are only supported by amdgpu…
Right, but according to OP’s inxi output, it’s not even among the options, even though both xf86-video-amdgpu and libdrm_amdgpu1 are installed. What’s left to try? radeon.vce=0? Bug report? Older kernel-firmware? Surely libdrm_amdgpu1-32bit couldn’t be it, could it?
On Mon 21 Jan 2019 03:36:03 AM CST, mrmazda wrote:
malcolmlewis;2892062 Wrote:
> For that GPU, there should be no need as amdgpu is the default for
> that card…Right, but according to OP’s inxi output, it’s not even
> among the
options, even though both xf86-video-amdgpu and libdrm_amdgpu1 are
installed. What’s left to try? radeon.vce=0? Bug report? Older
kernel-firmware? Surely libdrm_amdgpu1-32bit couldn’t be it, could it?
Hi
I only have it because steam is installed… xf86-video-ati is
installed here, seems to have no effect?
Missing firmware perhaps, need to see the output from;
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
SLES 15 | GNOME Shell 3.26.2 | 4.12.14-25.25-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
I’m not sure what you are asking. The nomodeset parameter is not set in my grub config. I have been editing the command line during boot to add
the nomodeset parameter. If I do not do that, then my system locks up during boot. That is what this whole thread is about.
Can you remove nomodeset , ivrs_ioapic[32]=00:14.0 quiet net.ifnames=0 and add plymouth.enable=0 console=tty by editing grub at boot and see how that goes, or how far it gets…
Note that everything following the name of the kernel on the linux lines in Grub are options. Nearly always all can be removed and an otherwise untroublesome normal boot will still complete. Dracut includes the root= parameter in every initrd (unless explicitly directed not to), so its inclusion on cmdline serves only to override in case of conflict. AFAICT, this applies exactly the same with resume=. I routinely use net.ifnames=0, so highly doubt it would impact this thread, other than preventing network start when complete boot success would otherwise be achieved. In most cases, Grub editing typos cause simple omission of an intended parameter. I write all this simply in hopes of making OP’s Grub editing processes less intimidating.
