Jelle van der Waa
Jelle van der Waa
So the issue for me is that dmidecode ie. `machine_info.dmi_info()` returns fields for my RPI and we don't reach the catch(). As Fedora Server/IoT use uboot with a EFI payload...
[hostnamed dbus API](https://www.freedesktop.org/software/systemd/man/org.freedesktop.hostname1.html) now has chassis/hardware vendor but lacks product_serial/chassis_serial so if we can get that added it would be beneficial.
Just cross compiled u-boot from git ( f6973cce6af066d28980c9f82c99cb4e10af8a6f ) today on Arch Linux with: ``` make ARCH=arm CROSS_COMPILE=aarch64-linux-gnu- rpi_3_defconfig make ARCH=arm CROSS_COMPILE=aarch64-linux-gnu- ``` And then replaced `rpi3-u-boot.bin` on the FAT...
On Fedora IOT the u-boot version is 2022.05 which still shows unknown everywhere, so I'll check if this was recently fixed.
Rebased the branch, and now we get something: 
Mostly FYI: * When `pf-theme-dark` is set, patternfly enables the dark theme. * In chrom(ium) toggling dark mode can be done in devtools: click the three dotted (kebab) menu, `more...
Last rebase has imporved the situation some obvious issues: - metrics page has issues   - top bar looks weird:  - Graphs are not readable (network manager page)...
> Oh, you didn't push your rebase... so, as it rebased cleanly, I just did. wink Hmm strange, I force pushed again with a rebase plus fixes for some pages...
Pushed one fix for the graphs in storaged/networkmanager page.
The flashing is now gone, as we set the html background when creating the new iframe, but it feels that there is still some minor issue with flashing? Unrelated: networkmanager...