Tartarus changed the topic of #u-boot to: SOURCE MOVED TO https://source.denx.de/u-boot/u-boot.git / U-Boot v2025.04 is OUT / Merge Window is OPEN, next branch is CLOSED / Release v2025.07 is scheduled for 07 July 2025 / Channel archives at https://libera.irclog.whitequark.org/u-boot
Danct12 has quit [Quit: ZNC 1.9.1 - https://znc.in]
Danct12 has joined #u-boot
Daanct12 has joined #u-boot
Danct12 has quit [Killed (NickServ (GHOST command used by Daanct12))]
Daanct12 is now known as Danct12
Danct12 has quit [Quit: ZNC 1.9.1 - https://znc.in]
Danct12 has joined #u-boot
clamor has joined #u-boot
alexxy[home] has joined #u-boot
alexxy has quit [Ping timeout: 276 seconds]
clamor has quit [Ping timeout: 252 seconds]
clamor has joined #u-boot
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #u-boot
apritzel_ has joined #u-boot
<Tartarus> sjg1: alexandra is out of disk space again
<sjg1> Tartarus: Hmmm I don't have a KVM on that one and can't login. Can you clear the cache?
goliath has quit [Quit: SIGSEGV]
<Tartarus> sjg1: It's likely a bunch of dead docker stuff that needs to be cleared out
<sjg1> Tartarus: OK, I got in, it is deleting things
clamor has quit [Read error: Connection reset by peer]
<Tartarus> Thanks
<Tartarus> You might want to put "docker system prune --all --force --volumes" in crontab or whatever to run weekly
mmu_man has quit [Ping timeout: 252 seconds]
vagrantc has joined #u-boot
haritz has quit [Ping timeout: 260 seconds]
Jones42 has quit [Ping timeout: 252 seconds]
<sjg1> Tartarus: I have that weekly. I changed it to daily
<sjg1> Tartarus: /run/qemu seems to be using 47G and I'm not sure what it is
<Tartarus> i wonder, yeah
haritz has joined #u-boot
haritz has joined #u-boot
goliath has joined #u-boot
haritzondo has joined #u-boot
haritz has quit [Read error: Connection reset by peer]
<Stalevar> I have a device with mmcblk0 and mmcblk0boot0 and boot1, I wonder if those partitions are part of the mmcblk block device or it's just one chip has three virtual blockdevs?
<Stalevar> Also I found that both mmcblk0boot0 and mmcblk0 contain u-boot but it seem to be different
mmu_man has joined #u-boot
<Tartarus> the "bootN" partitions are part of the physical boot partition the eMMC has
<Tartarus> Check the help on "mmc dev"
<Tartarus> I *think* 0 is the user space (ie mmcblk0) 1 is the first boot partitionn and 2 is the 2n
<Tartarus> d
<Stalevar> Tartarus, the problem is that I can't access U-Boot console but I know that the device is supposed to boot from USB somehow, only question is how to make USB flash bootable on it
enok has joined #u-boot
enok has quit [Ping timeout: 245 seconds]
sng has quit [Ping timeout: 260 seconds]
sng has joined #u-boot
vagrantc has quit [Quit: leaving]
mmu_man has quit [Ping timeout: 252 seconds]
mmu_man has joined #u-boot
persmule has quit [Ping timeout: 264 seconds]
umbramalison has quit [Ping timeout: 276 seconds]
persmule has joined #u-boot
umbramalison has joined #u-boot
persmule has quit [Remote host closed the connection]
persmule has joined #u-boot