00:15
ris has quit [Ping timeout: 244 seconds]
01:31
jtojnar has quit [Read error: Connection reset by peer]
01:33
jtojnar has joined #nixos-aarch64
01:33
jtojnar has quit [Read error: Connection reset by peer]
03:04
orivej has quit [Ping timeout: 246 seconds]
05:16
zupo has joined #nixos-aarch64
05:23
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
06:00
orivej has joined #nixos-aarch64
06:41
t184256 has left #nixos-aarch64 [#nixos-aarch64]
06:44
t184256 has joined #nixos-aarch64
08:56
orivej has quit [Ping timeout: 246 seconds]
09:40
zupo has joined #nixos-aarch64
09:57
orivej has joined #nixos-aarch64
12:13
marek has quit [Ping timeout: 272 seconds]
12:50
marek has joined #nixos-aarch64
13:34
<
tilpner >
DigitalKiwi: Compare /init-interface-version of your newly built system and the currently running one
13:35
<
DigitalKiwi >
i get it every time i do it and have rebooted a few times
13:36
<
DigitalKiwi >
what's /init-interface-version
13:36
<
tilpner >
A file in your built system
13:36
<
tilpner >
If it changes, the activation will print that line
13:36
<
tilpner >
cat /run/current-system/init-interface-version
13:38
<
DigitalKiwi >
systemd 2
13:39
<
tilpner >
And in the system you built?
13:40
orivej has quit [Ping timeout: 248 seconds]
13:40
<
tilpner >
Something like cat $(nix-build --no-out-link '<nixpkgs/nixos>' -A system)/init-interface-version
13:42
<
DigitalKiwi >
systemd 3
13:42
<
tilpner >
There you go
13:43
<
DigitalKiwi >
but how do i make it go away when i reboot it'll do it again
13:43
<
DigitalKiwi >
it never did it before like a few days ago
13:43
<
tilpner >
Are you also deploying to it remotely?
13:44
<
DigitalKiwi >
no it's just a raspberry pi at my house
13:44
<
DigitalKiwi >
nothing special about it
13:44
<
tilpner >
You can deploy to those remotely
13:44
<
tilpner >
(And that would cause problem if you're not careful)
13:44
<
DigitalKiwi >
i don't do nixops or anything the only thing i use is nixos-rebuild
13:44
<
tilpner >
nixos-rebuild can deploy remotely
13:45
<
tilpner >
But unless you're passing --target-host, you're not using that functionality
13:45
<
DigitalKiwi >
i ssh to it and do nixos-rebuild
13:45
<
tilpner >
What does cat /run/booted-system/init-interface-version say?
13:45
<
DigitalKiwi >
nothing has changed in what i do it's a recent update
13:46
<
DigitalKiwi >
systemd 2
13:46
<
tilpner >
Then you're not booting the system you just built
13:46
<
tilpner >
Do you sometimes login as root, and sometimes use sudo?
13:47
<
tilpner >
That might cause a difference in NIX_PATH and result in you switching back and forth between channels, maybe
13:48
<
DigitalKiwi >
pretty much always sudo and not root recently afaik
13:50
<
DigitalKiwi >
maybe i messed up the channels somehow
14:30
marek has joined #nixos-aarch64
14:30
marek has quit [Changing host]
15:10
orivej has joined #nixos-aarch64
15:22
orivej has quit [Ping timeout: 245 seconds]
15:26
orivej has joined #nixos-aarch64
15:27
ryantrinkle has quit [Quit: Leaving.]
15:28
ryantrinkle has joined #nixos-aarch64
16:14
<
DigitalKiwi >
tilpner: thanks for the help i got it working for now got it on nixos 19.03
16:15
<
tilpner >
DigitalKiwi: What was the culprit? Channels?
16:16
<
DigitalKiwi >
yeah something to do with them i think
16:48
orivej has quit [Ping timeout: 248 seconds]
17:45
wildtrees has joined #nixos-aarch64
17:46
wildtrees has quit [Max SendQ exceeded]
17:46
wildtrees has joined #nixos-aarch64
17:48
wildtrees has quit [Max SendQ exceeded]
17:49
wildtrees has joined #nixos-aarch64
17:50
wildtrees has quit [Max SendQ exceeded]
17:51
ToxicFrog has quit [Ping timeout: 246 seconds]
17:51
wildtrees has joined #nixos-aarch64
17:52
wildtrees has quit [Max SendQ exceeded]
17:53
ToxicFrog has joined #nixos-aarch64
18:26
ris has joined #nixos-aarch64
18:27
jslight90 has joined #nixos-aarch64
18:43
wildtrees has joined #nixos-aarch64
19:29
<
jslight90 >
I am having a problem with NixOS 19.03 booting the console tty on a Raspberry 3B+. The display hangs at "Starting kernel...".
19:29
<
jslight90 >
Meanwhile, I can still access the system through SSH.
20:24
orivej has joined #nixos-aarch64
20:56
<
ToxicFrog >
jslight90: I think I had the same problem, hang on a moment
20:56
* ToxicFrog
rummages through her logs
20:57
<
ToxicFrog >
jslight90: boot.initrd.kernelModules = [ "vc4" ]; fixed it for me
21:01
<
samueldr >
once it gets to stage-2, the vc4 module will load, if this is not added
21:01
<
samueldr >
I'm not sure why I had to also add "bcm2835_dma" "i2c_bcm2835" though
21:01
<
samueldr >
maybe it's not required anymore
21:02
<
samueldr >
and of note, the sd image now includes the required kernel modules in stage-1 on unstable (thus 19.09)
21:08
<
jslight90 >
Thanks, I'll give those a try.
21:21
orivej has quit [Ping timeout: 246 seconds]
23:29
<
jslight90 >
I tried adding those initrd kernel modules but I'm still having the same problem. The SD will boot fine until I run "nixos-rebuild switch".
23:37
<
samueldr >
can you share the configuration.nix?
23:53
<
samueldr >
hmm, I don't see anything wrong in there
23:53
<
samueldr >
maybe the difference is in the kernel being used?
23:53
<
samueldr >
unless the sd image you used already was using the latest kernel
23:56
wildtrees has quit [Quit: Leaving]