Hi there! First time posting. I recall getting a rundown of how these projects are working now from Elly previously.
Previously, various projects existed to get Fedora in some shape or form running on this Chromebook of mine, but some of them are defunct now.
May I have some assistance in building a Fedora image for this device?
According to our documentation, C13 Yoga == MORPHIUS, so no need to build custom images if your device is using NVME as storage.
Situation is a bit more complicated with eMMC as Picasso is (AFAIK) the only x86 platform using MMIO (Memory Mapped I/O), where you’d need to either put /boot/efi and /boot on mSD/USB, or indeed - build a depthcharge image.
Ultramarine folks are working on it, so it should get easier fairly soon!
Please post the output from lsblk in ChromeOS, it’ll help with identifying the storage type used by your device
Hi there! Thanks for replying!
This guy uses NVMe instead of emmc so that should be fine. Perhaps one day I’ll upgrade it to a 512gb 2242 instead of the 128gb in there now.
Here’s the results of lsblk from the Linux container- I’m going to enable Developer mode now to get better access to that built-in terminal:
s31bz@penguin:~$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 254:0 0 66M 1 disk /opt/google/cros-containers
vdb 254:16 0 35.4G 0 disk /dev/net/tun
pmem0 259:0 0 710M 0 disk
Booting live usbs of Fedora 39 XFCE or Gnome seems to result in none of the function buttons being recognized, nor the search button. I’ll do so more digging.
That is, to say, that a GUI seems impossible currently on this machine with RW_Legacy, but I don’t have the skills to make my own SuzyQable to install full from on it. Seeing if a friend can make one.
Booting the Ubuntu 23.10.1 live image in safe graphics mode, utilizing RW_Legacy firmware, it runs through the installer fine but then boots to a black screen after.
Wonder if full UEFI is required for this…
Went ahead and took the machine apart, repasting it in the process. Tried the battery method and it didn’t work. No unpopulated jumper that I could see anywhere on the motherboard. I believe this may be one of the devices that requires CCD debugging in order to unlock UEFI for rull rom.
Weird, your device should work with the battery method. Does the battery cable disconnect from the battery or motherboard side? If both, disconnect from both sides.
Nvm got it figured out. The cable was a little loose to begin with.
Went ahead and reinstalled ChromeOS, then enabled Developer Mode, fully unplugged the battery and installed UEFI firmware.
Hello from Fedora- trying out Cinnamon.
Looks like I can update my firmware from here too.