Morphius: errors on boot on several different distros, with several different kernel versions

not a bad idea tbh

Oooh, this might’ve been my problem too, at Crashes on v4.22 (2023.12.24) - Yoga C13 running Linux.

I got the same UART problem. Mine also has no fingerprint sensor

Interesting.

@MrChromebox any ideas how we could add FPMCU probing in fwconfig? You know more about AMD platforms, so you might have an idea

you’d have to add a field to FW_CONFIG, then program the eeprom, then add the probe statement. I’m not sure there’s a good way for me to detect in firmware currently

1 Like

@elly How would one normally do that for use with an installer live disc?

@thinkpadworship, in what /etc filesystem did you create the new modprobe configuration file? I don’t find any etc directory on any of the three filesystems on my Pop!_OS installation USB drive, which I created from pop-os_22.04_amd64_intel_38.iso.

I, too, have a Thinkpad C13 (morphius) without fingerprint reader, and reach a black screen with only the pointer visible, but moving as if the entire display is upside down. I installed the latest RW_LEGACY firmware from MrChromebox yesterday, which appears to be Google_Morphius.13434.356.0.

Boot with following options appended to cmdline:
iommu=pt modprobe.blacklist=cros-ec-uart

1 Like

Just for clarification if somebody else stumbles upon this

blacklisting cros-ec-uart is the solution but not blacklisting it in cmdline in /etc/default/grub (and then using grub2-mkconfig -o /boot/grub/grub.cfg to apply the changes)

The Blacklisting has to be done in the etc/modprobe.d/ directory. As described by @thinkpadworship

then I used sudo dracut -f (or similar tools depending on the OS) to regenerate the initramfs and then reboot.

Still occurring? Have run run updates on the firmware recently? Still happening after that or have you blacklisted the cros ec as mentioned above?

Mine also has this problem and doesn’t have a fingerprint sensor. My keyboard layout is US. By any chance is yours also US? perhaps this is a thing with the US variants.

It may not be helpful feedback, but I have a Morphius with the US layout and never had this issue.

The keyboard layout was US but the person I bought it from told me it was a model from the Netherlands. Given that blacklisting the kernel module for the fingerprint sensor fixes it I’d guess it’s mainly a fingerprint sensor issue and nothing to do with the region.

How did it end up going, or are we good to close?