!xmLtiCaAJxfhURjrXl:matrix.org

NixOS RISC-V

208 Members
NixOS on RISC-V https://wiki.nixos.org/wiki/RISC-V https://pad.lassul.us/NixOS-riscv64-linux 62 Servers

Load older messages


SenderMessageTime
9 Apr 2025
@rosscomputerguy:matrix.orgTristan 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:matrix.orgdramforever 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:matrix.orgdramforeveru-boot -> efi -> systemd-boot doesn't seem to support picking the right dtb file based on system name03:08:13
@dramforever:matrix.orgdramforeverwhere did your devicetree even come from...03:17:03
@rosscomputerguy:matrix.orgTristan Ross Idk 03:17:23
@rosscomputerguy:matrix.orgTristan RossNixOS hardware is used03:17:31
@dramforever:matrix.orgdramforever can you paste the output of fdt print / from uboot somewhere 03:18:56
@rosscomputerguy:matrix.orgTristan 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
@rosscomputerguy:matrix.orgTristan Ross If you respond to the issue, I'll get to it when I have time 03:22:16
@dramforever:matrix.orgdramforeverlol03:22:19
@dramforever:matrix.orgdramforeveri'll put it in the issue03:22:26
@dramforever:matrix.orgdramforeverScreenshot_20250409_113158.png
Download Screenshot_20250409_113158.png
03:32:26
@dramforever:matrix.orgdramforeverwell, that would explain it https://github.com/u-boot/u-boot/commit/84d3911a01783ce386883a97fcc415703979314403:32:30
@dramforever:matrix.orgdramforeverwe 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 expects03:38:10
@dramforever:matrix.orgdramforeverwouldn't it be really funny if the ethernet dma problem is caused by the same thing03:45:33
@implr:hackerspace.plimplr

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:hackerspace.plimplrHaven't tried native yet23:16:05
@alex:tunstall.xyzAlex 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:hackerspace.plimplrhuh, why didn't I think of that, of course23:26:46
@implr:hackerspace.plimplrwill try, thanks23:26:57
10 Apr 2025
@implr:hackerspace.plimplrit is cross. oh well.10:20:07
11 Apr 2025
@dramforever:matrix.orgdramforever this is one of the most confusing dependency list i've seen, has both pkg-config and pkgconfig 02:30:09
@dramforever:matrix.orgdramforeveri mean the home-assistant-chip-wheels cross thing from yesterday02:30:25
@dramforever:matrix.orgdramforeverand the scary part is it seems to be actually correct, the former is the "normal" pkg-config and the latter is a python package02:30:51
@hexa:lossy.networkhexaRedacted or Malformed Event04:02:13
@hexa:lossy.networkhexalooked at it, and I have no clue why it fails like that04:02:30
@hexa:lossy.networkhexabut upstream certainly didn't envision riscv6404:02:36
@hexa:lossy.networkhexathis was a shitty native build to begin with04:02:48
@dramforever:matrix.orgdramforever

found how to fix the pkg-config problem

--- a/pkgs/development/python-modules/home-assistant-chip-wheels/default.nix
+++ b/pkgs/development/python-modules/home-assistant-chip-wheels/default.nix
@@ -259,6 +259,7 @@ stdenv.mkDerivation rec {
     ''target_cc="${stdenv.cc.targetPrefix}cc"''
     ''target_cxx="${stdenv.cc.targetPrefix}c++"''
     ''target_ar="${stdenv.cc.targetPrefix}ar"''
+    ''pkg_config="${stdenv.cc.targetPrefix}pkg-config"''
   ];
 
   preBuild = ''
07:01:51
@dramforever:matrix.orgdramforeverstill fails later on some python pip problem, no idea 07:02:18

Show newer messages


Back to Room ListRoom Version: 10