16:44 <jmabsd> Hi all - just for confirmation, the Debian image from Radxa, how does it do DHCP client function?    I remember the RockPi did DHCP client but now it suddenly stopped working, not sure in what config files to look

16:45 <jmabsd> The Debian does not have "dhclient" installed. Yet it did DHCP client somehow.

16:46 <CounterPillow> Sounds like a question you should those who made the image, namely radxa

16:46 <CounterPillow> *ask

16:46 <phh> systemd-networkd maybe?

16:48 <jmabsd> phh: Is there some configuration file that regulates it. Does systemd-networkd have a built-in dhcp client?

16:51 <jmabsd> This DHCP client function worked for a long time and now suddenly on boot it just doesn't do DHCP client anymore lol. Puzzling. So I tried adding /etc/network/interfaces.d/ file and then ifupdown complains 'dhclient' is not installed.

19:28 <helene> hi! i've been trying to get fedora running on a rk3588-based board (a friendlyelec nas board), but i'm getting a few issues trying to get mmc/sdmmc working (on both linux-next and collabora's tree)

19:31 <helene> tl;dr: no SDMMC/MMC devices are detected, but the u-boot i compiled (collabora's u-boot tree) detects both the eMMC and the SD card perfectly fine (they boot from it); and grub2 works, but it might be using the EFI APIs? booting the kernel without EFI makes no difference in what I observe

19:35 <helene> the underlying issue *seems* to be related to SPI and the PMIC/pinmux: it seems that the mmc drivers are probing the associated regulators, which show up as not-ready because the PMIC isn't, and the PMIC is over SPI, and the SPI has a deferred probe with "reason unknown" (https://brpaste.xyz/wwwm9g) and that's about all the information i'm seeing from kernel logs

19:36 <helene> i'm fairly new to this stuff, so I am probably missing something very obvious; but if anyone knows what that's about, I'd appreciate any help :) the DT i'm using is basically rk3588-nanopc-t6 (in mainline sources)