| 8 Apr 2025 |
Alex | In reply to @rosscomputerguy:matrix.org Yeah, NVME boot doesn't work when I've tried NVMe boot is possible, a few of us have it working (I needed to customise the u-boot rules, can't remember what I changed). | 19:45:37 |
Alex | In reply to @michal:tar.black Yeah, wouldn't expect it to be crazy, can it boot from an EMMC module fine-ish? I do recall seeing space for one when putting the case on it Yes, it can. | 19:45:49 |
Tristan Ross | In reply to @alex:tunstall.xyz NVMe boot is possible, a few of us have it working (I needed to customise the u-boot rules, can't remember what I changed). The problem I have is the initrd cannot find the NVME despite having the drivers | 19:46:14 |
Tristan Ross | https://github.com/NixOS/nixos-hardware/issues/1347#issue-2812099176 | 19:49:03 |
Tristan Ross | * https://github.com/NixOS/nixos-hardware/issues/1347 | 19:49:10 |
Alex | In reply to @michal:tar.black How is NixOS with the VisionFive2 currently? Just had it arrive earlier today and was thinking of NixOS-ing it :) It works. I haven't been able to get uptimes beyond 2 weeks, but that might just be overheating (thermal throttling is broken in the kernels I use).
Don't expect great performance. And don't expect to be able to get perfectly working HDMI (maybe just a kernel issue?). | 19:49:16 |
Michal | Yes, afaik HDMI is one of the only things left to merge into the mainline kernel from what I've read | 19:49:46 |
Alex | I've tried the module from an older version of the patches and it didn't properly work. Even the vendor image would sometimes change the screen colours suddenly. | 19:51:26 |
| 9 Apr 2025 |
dramforever | Tristan Ross: have you tried the "generic-extlinux-compatible" boot for nvme? it seems to be a devicetree problem | 02:50:06 |
dramforever | the one you installed to nvme is somehow loading the device tree | 02:54:53 |
dramforever | * whatever you installed to nvme is somehow loading the device tree | 02:56:18 |
Tristan Ross | In reply to @dramforever:matrix.org Tristan Ross: have you tried the "generic-extlinux-compatible" boot for nvme? it seems to be a devicetree problem Only UEFI | 03:05:54 |
dramforever | Tristan Ross: Try hardware.deviceTree.name = "starfive/jh7110-starfive-visionfive-2-v1.3b.dtb"; (or v1.2a, depending on what your board is) | 03:07:43 |
dramforever | u-boot -> efi -> systemd-boot doesn't seem to support picking the right dtb file based on system name | 03:08:13 |
dramforever | where did your devicetree even come from... | 03:17:03 |
Tristan Ross | Idk | 03:17:23 |
Tristan Ross | NixOS hardware is used | 03:17:31 |
dramforever | can you paste the output of fdt print / from uboot somewhere | 03:18:56 |
Tristan Ross | In reply to @dramforever:matrix.org can you paste the output of fdt print / from uboot somewhere Maybe in like 3 months lol | 03:22:01 |
Tristan Ross | If you respond to the issue, I'll get to it when I have time | 03:22:16 |
dramforever | lol | 03:22:19 |
dramforever | i'll put it in the issue | 03:22:26 |
dramforever |  Download Screenshot_20250409_113158.png | 03:32:26 |
dramforever | well, that would explain it https://github.com/u-boot/u-boot/commit/84d3911a01783ce386883a97fcc4157039793144 | 03:32:30 |
dramforever | we have 2025.01 in nixpkgs, that's only 2025.04, so the current one is actually missing the linux,pci-domain property that the kernel expects | 03:38:10 |
dramforever | wouldn't it be really funny if the ethernet dma problem is caused by the same thing | 03:45:33 |
implr | Has anyone tried to build home-assistant-chip-wheels for rv64? Cross compiling (at ~current -unstable) fails with
Running phase: configurePhase
@nix { "action": "setPhase", "phase": "configurePhase" }
gn flags: chip_project_config_include_dirs=\[\"//..\"\] chip_crypto=\"openssl\" enable_rtti=true chip_config_memory_debug_checks=false chip_config_memory_debug_dmalloc=false chip_mdns=\"minimal\" chip_minmdns_default_policy=\"libnl\" chip_python_version=\"3.13\" chip_python_platform_tag=\"any\" chip_python_package_prefix=\"home-assistant-chip\" custom_toolchain=\"custom\" target_cc=\"riscv64-linux-cc\" target_cxx=\"riscv64-linux-c++\" target_ar=\"riscv64-linux-ar\"
ERROR at //build/config/linux/pkg_config.gni:125:17: Script returned non-zero exit code.
pkgresult = exec_script(pkg_config_script, args, "value")
^----------
Current dir: /build/source/connectedhomeip/out/Release/
Command: python3 /build/source/connectedhomeip/build/config/linux/pkg-config.py openssl
Returned 1.
stderr:
Could not run pkg-config.
See //src/crypto/BUILD.gn:82:3: whence it was called.
pkg_config("openssl_config") {
^-----------------------------
See //BUILD.gn:138:7: which caused the file to be included.
"${chip_root}/src/crypto",
^------------------------
| 23:15:59 |
implr | Haven't tried native yet | 23:16:05 |
Alex | You could try cross-compiling to aarch64.
If that fails with a similar error, then it's likely because of cross and not because of host arch. | 23:17:21 |
implr | huh, why didn't I think of that, of course | 23:26:46 |