samuelbernardo has quit [Ping timeout: 265 seconds]
dustymab1 has joined #fedora-coreos
dustymabe has quit [Ping timeout: 240 seconds]
jpn has quit [Ping timeout: 260 seconds]
Betal has quit [Quit: WeeChat 3.8]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 252 seconds]
lack has quit [Read error: Connection reset by peer]
lack has joined #fedora-coreos
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 240 seconds]
krouma has joined #fedora-coreos
krouma has quit [Ping timeout: 258 seconds]
jzelinskie has quit [Server closed connection]
jzelinskie has joined #fedora-coreos
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 265 seconds]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 240 seconds]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 252 seconds]
michele_ has joined #fedora-coreos
jpn has joined #fedora-coreos
sentenza_ has quit [Remote host closed the connection]
millerthegorilla has joined #fedora-coreos
<millerthegorilla>
Hi, anyone use raspberry pi coreos? I have just returned to a machine that I have been provisioning, and it is loading the edk2f firmware, and then displaying a 'synchronous exception at 0x000000003384D000'. This is occurring with different config.ign, and also with different sd cards.
lack has quit [Read error: Connection reset by peer]
lack has joined #fedora-coreos
<millerthegorilla>
Ok, it seems the latest edk2f firmware - v1.35 - causes this error. I reinstalled using v1.34 and it works fine.
<millerthegorilla>
Had me worried for a while...
jpn has quit [Ping timeout: 265 seconds]
jpn has joined #fedora-coreos
Betal has joined #fedora-coreos
lack has quit [Read error: Connection reset by peer]
<millerthegorilla>
I have just tried using a 256gb microsd card, with an 8gb root and a >200GB var. Luks fails, complaining in logs, that there isn't enough room for keyslots. I am guessing that it stores them on the 1MB Linux reserved partition, which is fine for my 16gb sd card, but not big enough for the 256gb card.
<millerthegorilla>
Not entirely why though.
<millerthegorilla>
*sure
<dustymabe>
hmm. weird. I don't have much expertise in that area of our stack, though
<dustymabe>
I imagine you could reproduce that on a VM and not a RPi4?
<millerthegorilla>
I guess it might be possible. I haven't used coreos on anything other than a pi, personally.
<dustymabe>
ahh :) - it's pretty easy to run in a VM
<dustymabe>
either way - if you could open an issue that with the details, that would be great
<dustymabe>
reproducing it in a VM would be useful because it would be easy for other people to try to reproduce - requiring someone to have a pi (and one that's not being used) to try to reproduce is a bit of a tall order
<millerthegorilla>
Ok, I am guessing that the coreos image has that partition at 1MB. I checked the coreos installer manual page, but there was no way of increasing the allotted size. Is there any way of editing the partition size on an image, that I can then install with coreos-installer?
<millerthegorilla>
And by VM, do you mean libvirt?
<millerthegorilla>
so, I might be able to use the partitions section of config.ign to increase the size
<dustymabe>
I honestly don't know if it's supported to resize that BIOS BOOT partition
<dustymabe>
also I really don't think anything is using that partition on aarch64 at all
<millerthegorilla>
mm, just took a look at my ignition config, and there may be an error with the way I specified the partitions. I am just reprovisioning now.
<dustymabe>
+1
<millerthegorilla>
No, it didn't work. I will try the VM now.
james_ has joined #fedora-coreos
millerthegorilla has quit [Ping timeout: 260 seconds]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 252 seconds]
james_ has quit [Quit: Leaving]
millerthegorilla has joined #fedora-coreos
sentenza has joined #fedora-coreos
millerthegorilla has quit [Quit: Leaving]
ravanell_ has quit [Remote host closed the connection]