tilpner_ has joined #nixos-aarch64
tilpner has quit [Ping timeout: 246 seconds]
tilpner_ is now known as tilpner
h0m1 has quit [Ping timeout: 260 seconds]
h0m1 has joined #nixos-aarch64
knerten2 has joined #nixos-aarch64
knerten1 has quit [Ping timeout: 246 seconds]
njd has quit [Ping timeout: 272 seconds]
njd has joined #nixos-aarch64
orivej has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-aarch64
cole-h has quit [Quit: Goodbye]
zupo has joined #nixos-aarch64
zupo has quit [Client Quit]
zupo has joined #nixos-aarch64
zupo has quit [Ping timeout: 240 seconds]
rajivr has joined #nixos-aarch64
FRidh has joined #nixos-aarch64
<fps> patagonicus: samueldr: it worked in the end. i had to recreate the FIRMWARE partition with the new size since libparted doesn't handle fat16 correctly it seems. but i just backed up the files up up and copied everythin back over after recreating the partition and file system..
<patagonicus> At least the RPis just read the filesystem and look for file names and don't have any magic offsets. :)
zupo has joined #nixos-aarch64
<samueldr> great!
<fps> yeppo :)
<fps> 128M is just a little bit too little space for rebuilding the system when there's a new kernel involved
<fps> most of the time removing everything in /boot/old before the rebuild/switch helped though..
<fps> i'm trying with 256M for now
<patagonicus> samueldr++ boot.initrd.preLVMCommands = lib.mkBefore "waitDevice /sys/class/net/eth0"; works. :)
<{^_^}> samueldr's karma got increased to 247
njd has quit [Ping timeout: 258 seconds]
njd has joined #nixos-aarch64
FRidh has quit [Quit: Konversation terminated!]
wavirc22 has quit [Ping timeout: 256 seconds]
bennofs__ has joined #nixos-aarch64
bennofs_ has quit [Ping timeout: 256 seconds]
ryantrinkle has quit [Ping timeout: 246 seconds]
ryantrinkle has joined #nixos-aarch64
FRidh has joined #nixos-aarch64
ryantrinkle has quit [Ping timeout: 258 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
ryantrinkle has joined #nixos-aarch64
AmandaC has quit [*.net *.split]
grw1 has quit [*.net *.split]
makefu has quit [*.net *.split]
sigtrm has quit [*.net *.split]
lovesegfault has quit [*.net *.split]
AmandaC has joined #nixos-aarch64
grw1 has joined #nixos-aarch64
lovesegfault has joined #nixos-aarch64
makefu has joined #nixos-aarch64
sigtrm has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
FRidh has quit [Ping timeout: 240 seconds]
FRidh has joined #nixos-aarch64
cole-h has joined #nixos-aarch64
Thra11 has quit [Quit: WeeChat 2.8]
zupo has joined #nixos-aarch64
rajivr has quit [Quit: Connection closed for inactivity]
alp has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
alp has quit [Ping timeout: 272 seconds]
alp has joined #nixos-aarch64
FRidh has quit [Quit: Konversation terminated!]
Thra11 has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
alp has quit [Ping timeout: 272 seconds]
mla has quit [Ping timeout: 256 seconds]
alp has joined #nixos-aarch64
noneucat has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<colemickens> samueldr: not sure if you have time for possibly dumb questions, but I'm poking at blueline again. the mainline kernel is close to building, but it builds Image instead of Image.gz that seems to be expected. https://github.com/colemickens/mobile-nixos/tree/mobile-nixos-blueline/devices/google-blueline I'm not sure what controls this behvaior, is it part of the defconfig?
<samueldr> the behaviour between building Image vs. Image.gz?
<colemickens> yes
<samueldr> >> installTargets = [ "zinstall" "Image.gz-dtb" "install" ];
<samueldr> AFAIK this should have been enough (zInstall)
<colemickens> hm, the kernel-android I copied from the PR you had sent also explicitly had "Image.gz" ahead of "zinstall" in that list.
<samueldr> right, some of it may be bad cargo culting, but for some I know it's required because of bad makefiles
<samueldr> though when it's required IIRC zinstall fails not knowing how to build Image.gz
<colemickens> yeah, I was wondering, I figured it might popped up differently too. I'll keep prodding it.
<samueldr> try it with
<samueldr> I'll clone and launch the build and see if I can intuit something
<colemickens> oh hey, it did get further
<colemickens> (readme pushed)
<samueldr> *** Missing file: arch/arm64/boot/Image.gz
<samueldr> *** You need to run "make" before "make install".
<samueldr> (from before your last push I presume)
<samueldr> so to me it looks like it's another "bad makefile"
<samueldr> or that there is something off with what I do and zinstall
<colemickens> this time its: make[2]: *** No rule to make target 'arch/arm64/boot/Image.gz-dtb'. Stop.
<samueldr> the latter may be more likely because this is mainline based
<colemickens> I assumed it might be related to my kernel and if it does dtb, how it does it, idk, I just started looking more
<samueldr> yeah, Image.gz-dtb may not be a thing with mainline
<colemickens> (I can do some digging here I just started looking at this next one)
<samueldr> >> android-mainline: doesn’t build
<samueldr> kernel-android? :)
t184256 has left #nixos-aarch64 ["Error from remote client"]
<colemickens> lol
<colemickens> wow, I really messed that up
<colemickens> the top one is andriod, the bottom is mainline
<samueldr> Serial access
<samueldr> Nothing works.
<samueldr> what have you tried? :)
<samueldr> I mean, what kind of hardware setup fo you have?
<colemickens> oh no, refresh refresh refresh :P
<samueldr> ah!
<colemickens> Pixel 3, I haven't tested anything, that was old copy pasta
<samueldr> get yourself the items to make a serial cable
<samueldr> get a couple
<samueldr> >> Instant discount: C$ 4.17 off per C$ 277.76
<samueldr> WHAT A DEAL
<colemickens> whoa, cool
<samueldr> so yeah, this only works on pixel phone devices since the 2
<samueldr> you will read online that the "suzy-q" cables for chromeos devices works
<samueldr> NO it does not
<samueldr> well, yes it does, but you only get the titan chip
<samueldr> that breakout board is likely helpful for other shenanigans on type-c
<samueldr> that's why I recommend getting a couple :)
<samueldr> btw, hi, it me, samueldr, who modified kernel-android/default.nix and built kernel-mainline/default.nix
<samueldr> five minutes down the drain
<colemickens> wat
<samueldr> I edited the wrong derivation
<DigitalKiwi> only 5 minutes for a kernel?
<samueldr> sorry?
<colemickens> oh oh I see
<samueldr> it's not a _defconfig kernel, so it's much quicker
<DigitalKiwi> i would expect that to waste a lot more than 5 minutes
<samueldr> it's a somewhat specialised build
<samueldr> colemickens: haven't checked, where do the config.aarch64 come from?