EMMC and SD Reader not initializing in Kevin

[vi-technocat]

This may be user error, but I'm experiencing some odd issues testing out the latest master branch (2a87d98) building for samsung-kevin using the docker image in the pull requests (I'm on fedora and quite familiar with docker, so it makes sense to me) and the build works, flashes to my flash drive, boots and seems normal except the emmc and sd reader aren't initializing, or even trying to.

I checked dmesg from a cold boot to the flash drive I'm using to test and there's nothing in here about the emmc or the sd reader period. In the past sometimes the emmc wouldn't initialize on boot but generally after a reboot that issue goes away and there's always dmesg logs about it, but here there's nothing.

The boot menu for ChromeOS still starts, so I assume the emmc is working, unless there's a secondary one for boot, but not being seen in linux by doing fdisk -l or lsusb / lspci

I was able to modify install-to-emmc to install to a sdcard plugged in using a usb-c to sdcard adapter and it worked fully with gnome and everything (no sign of the emmc again), but when I took the working sdcard from the usb adapter and put it into the sdcard slot on the device it starts to boot, and seems to hang at the Cd boot screen, with the following lines:
[1.39xxx] debugfs: File 'Capture' in directory 'dapm' already present!
[1.4xxx] rockchip-dp ff970000.edp: no DP ply configured
[65.xxx] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work] *ERROR* Timed out trying to load firmware

Thinking about it, I guess this is because it gets initialized with /dev/mmcblkXXX when in the sdcard slot versus /dev/sdX when in the reader, confusing the boot process, but it does mean the sdcard slot works, just not when booted from usb?

I let it sit for a few minutes to see if it would boot and then force shut it down. After putting the sdcard in the usb reader again it booted right up and I tried a few other sd cards I have in the reader but none of them worked. As a last ditch effort I put a different sdcard in the reader and rebooted to see if maybe having something in the reader and bootihng from usb from a cold boot would make it work, it didn't.

I do have a customized build of Cadium (I was messing around with waydroid and a few other things about a month ago) installed on the internal emmc and when I try to boot that it complains about "Unable to initialize emmc" and a handful of other log messages that I don't have enough time to read and then reboots after 5 seconds with apparently no way to stop it, which is what I was originally trying to fix by remaking the build. I assume the build I have flashed on the emmc is causing issues but I'm not sure how to get access to it to reflash it. Plus with the sd card reader now having issues I can't easily run an OS without the emmc so I'm not sure how to go about trying to fix this, if it's possible.

Any thoughts on these oddities?

Also, thank you all for your work on this project, it's honestly really impressive!