<srk>
samueldr: hardware.deviceTree now builds these with -@ but it doesn't work with rpi kernels / overlays
<samueldr>
yeah
<samueldr>
I don't know if that's relevant to betaboon's situation here
dstzd has joined #nixos-aarch64
dstzd has joined #nixos-aarch64
dstzd has quit [Changing host]
<srk>
I need to bring back the old way to handle that - something like hardware.deviceTree.raspberrypi that gonna work with device-tree_rpi like before (no checking for compatible just apply overlay to all dtbs)
Acou_Bass has joined #nixos-aarch64
<srk>
FDT_ERR_NOTFOUND could mean that 'fdtget file.dtb / compatible' failed or it cannot apply the overlay due to missing properties
<srk>
very unhelpful error code
<srk>
was looking at libfdt if it could be improved.. difficult as it's used in numerous places
justanotheruser has quit [Ping timeout: 265 seconds]
<betaboon>
I'm somewhat at loss here i've got another problem that i realy don't understand: if run `nix-shell -p qutebrowser` it states that it will build qutebrowser and fetch the rest from cache. If i add it to `environment.systemPackages` it claims that it will build a whole load of packages. i don't even know where to start looking :/
<samueldr>
system (root's) and user's NIX_PATH or channels not pointing to the same revision?
<samueldr>
though I would figure you've already looked at that
<betaboon>
samueldr: weirdly enough i am running it as root xD
<samueldr>
is your configuration.nix somehow using cross-compilation?
<samueldr>
or would it apply a Nixpkgs overlay with far-reaching consequences?
<betaboon>
samueldr: it started out as a configuration for cross-compilation. i built an image (cross-compiled) wrote it to sd-card, booted it up, copied the same configuration to the raspberry, removed the crossSystem/localSystem-settings and did a `nixos-rebuild switch` which worked fine
<samueldr>
right, so it shouldn't be
<betaboon>
samueldr: i only got an overlay in that uses a different kernel and raspberrypifw
<samueldr>
right, so it shouldn't matter either
<betaboon>
nope. I'm confused
<samueldr>
I don't really have more of a clue, sorry :)
<samueldr>
and I'm sure even those were things you looked at already
<samueldr>
so really the main thing I would have in mind is that you're not building against the same nixpkgs
<betaboon>
I'll run a `nix-channel --update` and see what happens
<betaboon>
samueldr: where would another nixpkgs be found if not in nix-channel ? oO
<samueldr>
you could be using nixpkgs.pkgs to "pin" to a version of nixpkgs, but your running software wouldn't intrinsically use it as part of their NIX_PATH
<samueldr>
which would end up relying on the defaults that makes nix-channel work
<betaboon>
hm. I'm not willingly/knowingly pinning nixpkgs anywhere.
<betaboon>
could using one of the following imports cause the problem `<nixpkgs/nixos/modules/installer/cd-dvd/sd-image.nix>`, `<nixpkgs/.../channel.nix>`, `<nixpkgs/nixos/modules/profiles/base.nix>` ? oO
<samueldr>
not that kind of problem
<samueldr>
oh uh, maybe that kind of problem
<samueldr>
I'm not usre
<betaboon>
ahhh i think i got it. i had a `environment.noXlibs = true;` burried somewhere ...
<samueldr>
now that's one way things could break :)
<betaboon>
so back to building and trying to get the vc4 support working so that i can run sway on the pi XD
<betaboon>
should i add "vc4" to `boot.kernelModules` ?
<samueldr>
not sure about the foundation's kernel
<samueldr>
look at lsmod on a running system
<samueldr>
the reason it is for the mainline image is for early console
<betaboon>
samueldr: when i booted the system vc4 wasnt loaded, but i could load it via modprobe
<samueldr>
might not be needed for the early text console on the foundation's kernel
<betaboon>
btw is there any way to determine if the dtoverlay way actually loaded ?
<betaboon>
samueldr: in there vc4 only shows under `__symbols__`
<samueldr>
that's the whole FDT as running
<samueldr>
now, what it means in your situation I don't know
<samueldr>
though know that u-boot may be reloading a fresh FDT
<betaboon>
I'm currently not using uboot
<samueldr>
okay
<betaboon>
(thanks for all the info btw)
<samueldr>
so it might not
<samueldr>
:)
<samueldr>
yeah, I don't know how to solve the problem you're having, but I do have bits of knowledge that could help
<samueldr>
hopefully enough to fit the gaps
lopsided98 has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo_ has joined #nixos-aarch64
leonardp has joined #nixos-aarch64
cornu has joined #nixos-aarch64
Smith[m]1 has joined #nixos-aarch64
kyren has joined #nixos-aarch64
codyopel has joined #nixos-aarch64
Dandellion has joined #nixos-aarch64
tnias[m] has joined #nixos-aarch64
bbigras has joined #nixos-aarch64
blitzclone[m] has joined #nixos-aarch64
Ox4A6F has joined #nixos-aarch64
alexarice[m] has joined #nixos-aarch64
colemickens has joined #nixos-aarch64
tilcreator has joined #nixos-aarch64
Danct12[m] has joined #nixos-aarch64
Ke has joined #nixos-aarch64
betrion[m] has joined #nixos-aarch64
hpfr has joined #nixos-aarch64
JJJollyjim has joined #nixos-aarch64
bennofs[m] has joined #nixos-aarch64
bqy has joined #nixos-aarch64
puzzlewolf has joined #nixos-aarch64
Ericson2314 has joined #nixos-aarch64
hsngrmpf[m] has joined #nixos-aarch64
pinage404[m] has joined #nixos-aarch64
thefloweringash has joined #nixos-aarch64
smrtak[m] has joined #nixos-aarch64
flo[m] has joined #nixos-aarch64
Jake[m]1 has joined #nixos-aarch64
fgaz has joined #nixos-aarch64
ArtemVorotnikov[ has joined #nixos-aarch64
yangm has joined #nixos-aarch64
danielrf[m] has joined #nixos-aarch64
<betaboon>
samueldr: i just noticed the whole gpu-support section in the raspberry_pi_4 wiki-page must somewhat be out of date. it still mentions slim ;D
zupo_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
<samueldr>
plausible
alp has quit [Ping timeout: 244 seconds]
<betaboon>
the no-gpu part works with slim just replaced with lightdm here
<betaboon>
srk: seems like just adding `dtoverlay=vc4-fmks-v4d` isnt enough. i dont get any /dev/dri/* showing up
<samueldr>
5.4 or 4.9?
<betaboon>
booting up raspbian to see if i can find the missing link
<samueldr>
things could have changed
<betaboon>
5.4
<samueldr>
I know the instructions in the wiki were tested against 4.9
<betaboon>
i need 5.4 for touchscreen-drivers
<samueldr>
yeah, was just saying so you'd know it's a factor
<betaboon>
yep :) thanks :D
zupo has quit [Ping timeout: 240 seconds]
zupo has joined #nixos-aarch64
<betaboon>
hm on raspbian i can see a `vc4-drm gpu` in dmesg. here i cant
<samueldr>
5.4 too?
<betaboon>
5.4.51-v7l+ on raspbian
<samueldr>
just checking :)
<betaboon>
5.4.51 aarch64 on my nixos-system :D
<samueldr>
though I wonder if it ends up using the same defconfig for armv7l vs. aarch64
<samueldr>
and if there are differences here
<betaboon>
i can see "bcm2835_vc_sm_cma_probe: Videocore shared memory driver" on the nixos-installs dmesg
<betaboon>
maybe it's the mesa version? but wouldnt that come after the vc4-drm ?
<samueldr>
I really don't know :)
<samueldr>
I would assume mesa wouldn't affect drivers in the kernel
<samueldr>
was the nixos installer 5.4 too?
<betaboon>
i built the sd-card-image with 5.4
<betaboon>
if that's what you mean
<samueldr>
yeah
<samueldr>
good
* colemickens
thought there wasn't 5.4 for rpi4?
<samueldr>
the foundation recently rebased their vendor fork (booooo, user-hostile) on top of 5.4
<samueldr>
since 4.9 is soon EOL'd I think
<samueldr>
or was it 4.19?
<samueldr>
anyway, whichever they were based on
<betaboon>
so playtime is over for today. ttyl
noonien has quit [Quit: Connection closed for inactivity]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]