08:53 <mps> Tim[m]123: I checked with 5.18.1 and 5.18.6, it is detected as SDR104

08:54 <mps> msg is like 'new ultra high speed ... SDR104', I'm not now on gru-kevin so can't copy exact msg

08:55 <Tim[m]123> I was using the Debian kernel, which has CONFIG_ROCKCHIP_IODOMAIN as module so voltage switching failed at boot

08:59 <Tim[m]123> With CONFIG_ROCKCHIP_IODOMAIN=y it was detected as UHS SDR104

08:59 <mps> Tim[m]123: I'm using alpine linux kernel, which I maintain btw

08:59 <mps> and I also have set 'CONFIG_ROCKCHIP_IODOMAIN=y'

09:00 <mps> sorry, not as module because I boot sometimes from external mmc and from internal emmc

15:35 <alpernebbi> Tim[m]123: you need the io-domain module in the initramfs, it works fine with Debian unstable, since it's automatically included

15:37 <alpernebbi> on Debian bullseye you can add it to /etc/initramfs-tools/modules and run sudo update-initramfs -u

15:39 <alpernebbi> the patch handling it didn't get into bullseye yet

15:40 <Tim[m]123> alpernebbi: Thanks I figured it out. I am aswell currently upgrading to testing, but stuck due to grub-install failing with grub-install: error: unknown filesystem.

15:42 <alpernebbi> maybe something wrong with /boot or /etc/fstab?

15:44 <alpernebbi> or the EFI system partition

15:46 <Tim[m]123> It was working with grub 2.04 from bullseye, maybe something wrong with 2.06, not sure. I think the problem is it tries to detect the filesystem of /dev/mmcblk0 but EFI is on mmcblk0p2, root on mmcblk0p3

15:56 <Tim[m]123> For the moment I downgraded again to grub 2.04-20

16:58 <mps> to ask also here: is there option to inhibit battery charging in chromebooks

17:18 <amstan> mps: ectool help, look for something like charging current

17:18 <amstan> set it to 0

17:19 <amstan> http://kmkeen.com/c100p-tweaks/#:~:text=controlling%20the%20battery%20charge

17:28 <mps> amstan: thanks. will look

17:28 <mps> I've got idea from asahi kernel

17:29 <mps> already made small hackish daemon to control charging on M1 notebool macbook

17:36 <amstan> you generally want to let the firmware do this kind of stuff, as these decisions need to happen while the laptop is off too

17:36 <amstan> but i guess the firmware on that device won't really have it

17:37 <mps> I think so

17:38 <mps> maybe they have something somewhere in flash ram but I have no idea where and what

17:48 <amstan> what do you mean?

17:48 <amstan> ec firmware is on a separate chip's flash

17:49 <mps> I mean maybe there some NVRAM registers where this can be set

21:25 <macc24> urja: i updated your patch for hdmi stuff btw https://github.com/Maccraft123/Cadmium/commit/6662e0b773e57b23938f872c3b802ebde6646eaf

22:03 <urja> ah, thank you <3 (i'll take a look at that later... but yeah, my mainline c201 kernel build is currently broken because my quick conflict resolution on them wasnt good enough to build and well lazy)