ChanServ changed the topic of #linux-cros-arm to:
krei-se- has quit []
krei-se has joined #linux-cros-arm
tobhe has joined #linux-cros-arm
tobhe_ has quit [Ping timeout: 480 seconds]
hexdump01 has joined #linux-cros-arm
hexdump0815 has quit [Ping timeout: 480 seconds]
weirdtreething has quit [Remote host closed the connection]
weirdtreething has joined #linux-cros-arm
krei-se- has joined #linux-cros-arm
krei-se has quit [Ping timeout: 480 seconds]
hexdump01 has quit []
hexdump0815 has joined #linux-cros-arm
<hexdump0815> Jasper[m]: is that supposed to allow one to set the gbb flags from an installed linux system instead from chromeos?
<hexdump0815> Jasper[m]: maybe that crossystem path changed? it should be in the recovery image as that has the full system and crossystem is definitely still around
<hexdump0815> Jasper[m]: maybe try with an older recovery image - i think https://cros.download/recovery has an archive of old recovery images
<Jasper[m]> <hexdump0815> "Jasper: is that supposed to..." <- Guess so? The issue is mostly that there's some dependency issues with the packaged version that refrain you from doing these things
<Jasper[m]> So instead you chroot into the recovery image
<Jasper[m]> <hexdump0815> "Jasper: maybe try with an..." <- Will try, thank you
pankpati has quit []
pankpati has joined #linux-cros-arm