Exotic Nix Targets - Public Room Timeline

	Exotic Nix Targets	339 Members
		104 Servers

Load older messages

Sender	Message	Time
8 Jul 2023
misuzu	Yeah, that's probably it	19:59:14
9 Jul 2023
	@jkachmar:matrix.org joined the room.	03:19:50
Pratham Patel	In reply to @alex:tunstall.xyz I was on upstream 6.4.0 (from commit `4964ce0a869e`) when I wrote that. I assume from your repository that this behaviour is from a build of `e5a381c51d624ffd8784db908a58ae227d0608a4`? by upstream, do you mean StarFive's repo or Linus' tree? I belive Linus' tree is missing support for the eMMC node for the VF2 dtsi (haven't checked for `-next`).	11:14:28
Alex	In reply to @thefossguy:matrix.org by upstream, do you mean StarFive's repo or Linus' tree? I belive Linus' tree is missing support for the eMMC node for the VF2 dtsi (haven't checked for `-next`). Vendor's, sorry I was unclear (I'd call Linus' mainline).	11:15:32
Alex	FWIW I tried mainline too but it didn't boot and I don't have the hardware to debug failed boots.	11:16:26
Pratham Patel	Ah okay... I tried their 6.4-rc3 with my old arch image a few months ago... It would boot but the GPU drivers are tied to the vendor 5.15.0 kernel for now :(	11:17:08
Pratham Patel	In reply to @alex:tunstall.xyz FWIW I tried mainline too but it didn't boot and I don't have the hardware to debug failed boots. Yeah, the mainline kernel doesn't know where the SD card is. I checked it via UART and it panicked at a recovery shell with a missing rootfs. Dug deeper to find out that the upstream DTB doesn't yet have an "entry" for the eMMC node.	11:18:21
Pratham Patel	Vendor kernel has this node: https://github.com/starfive-tech/linux/blob/b4920a1a3dd328124c61b07e8a6ab48c67881037/arch/riscv/boot/dts/starfive/jh7110-visionfive-v2.dtsi#L23	11:21:02
Pratham Patel	Meanwhile upstream doesn't yet have it: https://github.com/torvalds/linux/blob/e2c510d6d630fe6593a0cf87531913b4b08ebeb1/arch/riscv/boot/dts/starfive/jh7110-starfive-visionfive-2.dtsi#L18	11:21:33
Alex	For microSD, mmc1 is the correct node btw. I don't think mmc0 is used in the VF2, but it seems like it's for eMMC. `[nixos@nixos:/etc/nixos]$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mmcblk1 179:0 0 232.2G 0 disk ├─mmcblk1p1 179:1 0 256M 0 part /boot └─mmcblk1p2 179:2 0 231.9G 0 part /nix/store /`	11:22:27
Pratham Patel	Yes, but both are missing from upstream ;)	11:23:22
Alex	Oh dear, no ethernet in mainline either	11:23:29
Pratham Patel	:')	11:23:47
10 Jul 2023
trofi	artemis: RE your past problems with `libtool` cross-compiling on Gentoo. I think I found the issue: if you run `nix` itself in a containerized environment `nix` silently falls back into the mode without a sandbox enabled (due to a `sandbox-fallback = true`) and happily runs unsandboxed builds in `/tmp`. ALl the bianries in `/usr/bin` and whatnot are available to the builds and this impurity contaminates the environemtn with `/usr/lib` library search paths breaks the builds. The easy way to check it is to set `sandbox-fallback = false` in `/etc/nix/nix.conf`, restart `nix-daemon` and try to build something. If it fails that means you have been using unsandboxed builds.	08:32:39
trofi	I disabled sandbox fallback in the overlay with https://github.com/trofi/nix-guix-gentoo/commit/88050fcf0f3a11a7a6763494eda580b707be1267 and added a `README` entry to diagnose it: https://github.com/trofi/nix-guix-gentoo/commit/8109131192dc340e314d9e41159b176bfb5b82c8	08:33:40
trofi	What environment did you use to run `nix`? Real machine, a VM or some container?	08:34:20
artemis	In reply to @trofi:matrix.org What environment did you use to run `nix`? Real machine, a VM or some container? real machine, no VMs, no containers	08:56:22
artemis	also my /etc/nix/nix.conf already has `sandbox-fallback = false`	08:58:48
artemis	* also my /etc/nix/nix.conf already has `sandbox-fallback = false` without issue	08:59:01
artemis	* also my /etc/nix/nix.conf already has `sandbox-fallback = false` without issue. i dont know when i added that but it's been there	08:59:53
	@achnazoor:matrix.org joined the room.	09:05:21
	avnik joined the room.	09:39:14
trofi	Must be something else then (or a poisoned local cache when was built without a sandbox, before nix.conf tweaks)	09:46:47
artemis	how coud i clean local cache to ttest that theory	10:41:41
trofi	Good question. I would "uninstall" everything by cleaning all gc roots in /nix/var/nix/gcroots and run nix-xollect-garbage -d.	10:56:09
trofi	* Good question. I would "uninstall" everything by cleaning all gc roots in /nix/var/nix/gcroots and run nix-collect-garbage -d.	10:56:33
trofi	Alternatively you can `nix-build --check` all paths in the problematic closure. But it will require checking for false positives manually.	11:00:46
artemis	i will do the first option	11:25:01
11 Jul 2023
Alex	In reply to @alex:tunstall.xyz I'm currently compiling with a few patches applied to try to fix the compilation problems without disabling DRM, since I'd really like to get working HDMI on my VF2. I'll share the configuration if I'm able to get it working. Given the similarities between the two SBCs (and their respective Linux fork), it might work for the Star64 too. I've gotten Linux 5.15 to compile but it doesn't boot, doesn't log to journalctl, and doesn't output to HDMI, so I've folded and ordered the necessary hardware to debug over serial.	10:41:37
Alex	* I've gotten Linux 5.15 (VF2 dev branch) to compile but it doesn't boot, doesn't log to journalctl, and doesn't output to HDMI, so I've folded and ordered the necessary hardware to debug over serial.	10:42:00

Show newer messages

Back to Room ListRoom Version: 6