| 30 Jun 2022 |
matthewcroughan - nix.how | even though I'm doing
-r ${jh7100_recovery_binary} \
-b ${jh7100_secondBoot} \
-d ${jh7100_ddrinit}
Which really does flash the original binaries from their releases, it just nukes whatever uboot proper you happen to have on the board
| 08:17:57 |
fufexan | hi guys, just booted nixos on the visionfive | 08:18:01 |
matthewcroughan - nix.how | :D | 08:18:05 |
fufexan | trying to connect it to wifi | 08:18:07 |
matthewcroughan - nix.how | yeah the wifi seems not to work at the moment based on https://github.com/NixOS/nixpkgs/pull/168826 | 08:18:32 |
fufexan | [0;nixos@nixos: ~nixos@nixos:~]$ rfkill
[0;nixos@nixos: ~nixos@nixos:~]$ systemctl status wpa_supplicant.service
● wpa_supplicant.service - WPA Supplicant instance
Loaded: loaded (8;;file://nixos/etc/systemd/system/wpa_supplicant.service/etc/systemd/system/wpa_supplicant.service8;;; linked; vendor8;;>
Active: active (running) since Thu 2021-12-23 20:11:44 UTC; 2min 49s ago
Main PID: 907 (wpa_supplicant-)
IP: 0B in, 0B out
IO: 252.0K read, 0B written
Tasks: 4 (limit: 7844)
Memory: 2.3M
CPU: 158ms
CGroup: /system.slice/wpa_supplicant.service
├─907 /nix/store/h8xcpjsipl1hvzz6bnkwmdlgajzclj77-bash-5.1-p16-ris>
├─911 grep -q ^ACTION=add
├─912 /nix/store/h8xcpjsipl1hvzz6bnkwmdlgajzclj77-bash-5.1-p16-ris>
└─913 udevadm monitor -s net/wlan -pu
Dec 23 20:11:44 nixos systemd[1]: Started WPA Supplicant instance.
Dec 23 20:11:44 nixos wpa_supplicant-start[907]: Waiting for wireless interfaces
| 08:18:32 |
fufexan | ah, alright | 08:18:41 |
matthewcroughan - nix.how | just do ifconfig -a, you'll see that the interface doesn't even exist | 08:18:49 |
fufexan | yeah, rfkill reports no devices | 08:19:02 |
fufexan |  Download IMG20220630111934.jpg | 08:19:59 |
fufexan | have you guys had similar issues? 😆 | 08:20:06 |
fufexan | seems like tty looks like this, but the GUI actually looks fine | 08:20:18 |
matthewcroughan - nix.how | https://github.com/NixOS/nixpkgs/pull/168826#issuecomment-1152990386 | 08:20:22 |
dramforever | there's a forum post about this i think | 08:20:23 |
dramforever | something about unsupported resolutions | 08:20:30 |
matthewcroughan - nix.how | Looks like luizribeiro got the wifi working via this comment | 08:20:48 |
dramforever | weird display issue: https://forum.rvspace.org/t/my-bootup-screen-is-all-blurred/515 | 08:21:07 |
matthewcroughan - nix.how | which I can add to my visionfive-cross-x86 images attribute in my visionfive-nix flake, and you should then see the wifi just work when you build that image | 08:21:08 |
matthewcroughan - nix.how | I will also add a nixinate output that lets you nix run .#apps.nixinate.visionfive-nix and deploy to the board | 08:21:52 |
fufexan | would be appreciated | 08:21:57 |
matthewcroughan - nix.how | then you won't have to keep re-flashing it | 08:22:07 |
matthewcroughan - nix.how | could also just use nixos-rebuild switch --target-host, but nixinate is at least declarative and lets me encode that in the flake, but that really is all it takes to deploy to a machine | 08:22:32 |
fufexan | I can also use your repo in my dotfiles to configure the board and then deploy it? | 08:22:46 |
fufexan | * can I also use your repo in my dotfiles to configure the board and then deploy it? | 08:22:54 |
matthewcroughan - nix.how | Not sure what you mean by that | 08:23:04 |
fufexan | uh, use whatever nixpkgs + overlays you have for the board | 08:23:27 |
matthewcroughan - nix.how | It's better just to use the flake as is, it's not very re-usable if you want to import it into your own flake | 08:23:28 |
matthewcroughan - nix.how | I could make functions like mkVisionFive ./configuration.nix which would be very re-usable | 08:23:59 |
fufexan | that would be nice | 08:24:24 |
dramforever | there could be a visionfive.nix module that adds things like config.system.build.flashBootloader | 08:24:44 |