<unclechu>
samueldr: resize worked on unstable or stable 20.09?
<samueldr>
I haven't *verified* it works on unstable, but the change is already present
<samueldr>
and the change has been pushed to 20.09, so no need to document it as it's soon going to be updated to towk
<samueldr>
to work*
<samueldr>
the "starting kernel..." issues documented on the nixos wiki are... as I tried to explain... of various causes
<samueldr>
that alone as a symptom is not enough to know what the issue is
<samueldr>
it's like you told me that on your laptop "there's nothing on the screen" when you start it
<samueldr>
could be a wide range of issues
<samueldr>
(I'm pretty sure I wrote the sections on the wiki page about it)
<unclechu>
it just recommends to replug the HDMI after boot
<samueldr>
it helped for one (1) user
<unclechu>
samueldr: okay, i build my first config and successfully rebooted and sshed into the rpi
<unclechu>
thanks for your help
<unclechu>
it seems now i can go forward
<samueldr>
you're welcome
<samueldr>
hopefully you can figure out something for the hdmi output not really working well
<samueldr>
it's a bit odd and problematic how no one who could check seems to have a 3B+ on hand to do so
andi- has quit [Remote host closed the connection]
andi- has joined #nixos-aarch64
<unclechu>
i didn’t do `passwd` for my user, now i can’t do `sudo`
<unclechu>
is there any way to do this from my laptop?
<samueldr>
from u-boot you should be able to select a previous generation (before starting kernel...)
<unclechu>
chroot wouldn’t work i suppose since binaries are not compatible
<samueldr>
you could also undeclaratively edit the /boot/extlinux.conf file in the rootfs to change the default generation it boots from
<samueldr>
that will be reset on the next rebuild
<unclechu>
samueldr: hm... but how i would change a password for the user that does not exist in that generation?
<samueldr>
hmmm... you might sudo passwd to change the root user's password
<samueldr>
oh, but then ssh as root is not a thing
<samueldr>
you could also drop a .ssh/authorized_keys in the new user's home dir?
<unclechu>
yeah, unless i allow ssh as root in the config
<samueldr>
(mind the correct file and directory modes)
<unclechu>
i did that, i mean i added my authorized keys
<unclechu>
i can ssh as my user
<samueldr>
ah
<samueldr>
then you can passwd root
<unclechu>
but when i ssh-ed i can’t do `sudo smth`
<samueldr>
(on an older generation
<samueldr>
and then ssh, su, then passwd your new user
<unclechu>
yeah, i’ll probably just temporarily allow ssh as root
zarel has quit [Ping timeout: 256 seconds]
veleiro has joined #nixos-aarch64
Asmadeus has joined #nixos-aarch64
<noneucat>
mmmmm
<noneucat>
looks like the modem/suspend situation for pp is still a little hackish now
<noneucat>
some stuff has been upstreamed, but there are still one or two hacky patches i would need to apply to get some stuff working
<samueldr>
go on
<noneucat>
the main issue i'm struggling with is with the pp missing either calls or sms that were received during a suspend
<samueldr>
yeah, but that doesn't tell me anything about the two hacky patches
<samueldr>
are there reasons for us not to include them?
<noneucat>
there are some behaviors that were patched out in pmos to facilitate that, like preventing MM from hanging up on probes and patching a parser to fix some vendor weirdness
<noneucat>
they're not the 'right' solutions i guess
zarel has joined #nixos-aarch64
<noneucat>
i guess they could be put in the pinephone overlay
<samueldr>
or maybe outright mobile nixos overlay
<samueldr>
but yeah, pinephone overlay seems okay enough
<noneucat>
currently building mm with the changes to test them out
<samueldr>
in a way, mobile nixos is not against pragmatic changes like those
<samueldr>
after all, look at the vendor kernels
<noneucat>
hahaha
<Ke>
my honeycomb is now in finland
<noneucat>
i just looked it up
<noneucat>
looks fancy!
<noneucat>
damn, my local build is failing :/ guess i need to grab a cloud box to build this on
ib07 has quit [Ping timeout: 256 seconds]
cole-h has quit [Quit: Goodbye]
orivej has joined #nixos-aarch64
Darkmatter66 has joined #nixos-aarch64
wavirc22_ has quit [Ping timeout: 256 seconds]
Darkmatter66 has quit [Ping timeout: 264 seconds]
orivej has quit [Ping timeout: 264 seconds]
<Ke>
ups ninja attempted delivery and I was not at home
<Ke>
which is news to me
<Ke>
at least there are ups access points nearby
veleiro has quit [Ping timeout: 256 seconds]
Darkmatter66 has joined #nixos-aarch64
tilpner has quit [Remote host closed the connection]
tilpner has joined #nixos-aarch64
<sphalerite>
Ke: oh yeah probably same for me, except I know I'm not there and I knew I wouldn't be there a week ago and I couldn't do a thing about it.
<sphalerite>
\o/
monk has left #nixos-aarch64 ["Error from remote client"]
monk has joined #nixos-aarch64
<DigitalKiwi>
i thought everyone was at home
Darkmatter66 has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-aarch64
ehmry has quit [Read error: Connection reset by peer]
justanotheruser has quit [Ping timeout: 272 seconds]
ehmry has joined #nixos-aarch64
justanotheruser has joined #nixos-aarch64
alpernebbi has joined #nixos-aarch64
elvishjerricco has quit [Ping timeout: 260 seconds]
globin_ has quit [Quit: o/]
globin has joined #nixos-aarch64
globin has joined #nixos-aarch64
globin has quit [Changing host]
elvishjerricco has joined #nixos-aarch64
quinn has quit [Ping timeout: 264 seconds]
quinn has joined #nixos-aarch64
<yorick>
is there any raspberryi4 armv7l image?
<patagonicus>
yorick: The RPi3 can boot the multiplatform armv7l image, but I don't think the RPi4 can because it needs non-mainline kernel (although I'm not sure if it boots with mainline). You could either try cross-compiling or natively compiling if you have a working armv7l system and generate the multiplatform image, but with the RPi4 kernel.
<yorick>
patagonicus: thanks, I'll try that
<patagonicus>
yorick: I'd start with https://github.com/samueldr/cross-system for cross-compiling, otherwise it's probably not going to be fun. You'll want to use ./build.sh --argstr system armv7-linux and add whatever RPi4 specific stuff you need to configuration.nix - or copy armv7-linux to raspberrypi4-armv7l.nix, add stuff there and then use ./build.sh …
<patagonicus>
raspberrypi4-armv7l
<yorick>
patagonicus: I do have a bunch of the armv7l-multiplatform builds already, so they might just need the different kernel
<patagonicus>
Without looking into it, my guess is also that it's just the kernel. And potentially the bootloader, although I'd guess that that shouldn't change between 32-bit and 64-bit ARM.
jb55 has quit [Remote host closed the connection]
<flokli>
there is pkgs.ubootRaspberryPi4_32bit and pkgs.ubootRaspberryPi4_64bit
quinn has quit [Ping timeout: 272 seconds]
<yorick>
hmm, already having fun cross-compiling adventures
orivej has quit [Ping timeout: 265 seconds]
<flokli>
Hmmh. I wonder if we could have a bit more of that stuff built by hydra
<yorick>
seems like staging-next doesn't cross compile to armv7, anyways