00:35 <Armbian-Discord> <Z​anoryt> Spent a lot of time on this and I'm frustrated because I can't figure this out.

00:36 <Armbian-Discord> <Z​anoryt> I wish I had some more clarity on the error. It seems inconsistent too, because one out of maybe 20 builds goes through without issue.

00:50 <Macer> well then

00:50 <Macer> https://pastebin.com/bXe1KqY9

00:50 <ArmbianHelper> ^ [ 503.458391] PM: suspend exit[ 503.464216] mmc_host mmc1: Bus speed (slot 0 - Pastebin.com

00:50 <Macer> seems like coming out of s2idle the emmc is completely borked

00:54 <Armbian-Discord> <T​enkawa> What SoC?

00:54 <Macer> this is the pinebook pro

00:55 <Macer> rk3399

00:55 <Armbian-Discord> <T​enkawa> ah. I have the soc but not the full unit

00:55 <Macer> yeah it has some serious emmc issues it seems heh

00:58 <Macer> since i had this handy dandy serial cable now i figured i'd take a look at kernel msgs while i put it in suspend to see where it is getting borked.

00:59 <Armbian-Discord> <T​enkawa> hehe.. yeah if I ever buy me one I'm definitely getting that rca serial cable

00:59 <Macer> now later i can take a look at installing armbian on another emmc module i have to see where that breaks. i have a 128GB one i got from pine

00:59 <Macer> i also got the nvme board for it

01:00 <Macer> but i need the nvme for that thing to be useful

01:00 <Macer> you can't mount it without the nvme already. which kind of sucks. i was hoping i could jus tthrow it in there and open it tomorrow when the nvme arrives and pop that in but it screws in from the bottom

01:00 <Armbian-Discord> <T​enkawa> yeah almost every soc I have has a nvme or m.2 on it

01:01 <Macer> this one uses a board you buy for $7 with a ribbon cable that screws into the housing in a seriously awkward way but i'm sure it will get the job done

01:02 <Macer> i'm tempted to install something on an SD just to see if i can get it to boot and put it to sleep. the lack of a sleep mode is driving me crazy :)

01:02 <Macer> but emmc has random noboot issues as well. it will just... not work sometimes

01:02 <Armbian-Discord> <T​enkawa> nod. I was directed to it this afternoon if I was interested in the PBP

01:03 <Macer> well.. other than the sleep mode and awkward emmc issues. it's actually really awesome when you're using it. i mean granted it isn't the fastest laptop but you can use it day to day with a decent amount of battery life

01:04 <Armbian-Discord> <T​enkawa> Exactly.. and I want an arm based "tinkering" type laptop unit I can carry on my bike

01:04 <Macer> i've been doing that lately but having to turn it off and then hope it boots when you turn it back on is a bit of a drawback. usually after a 2nd try it will start up but it is still a big problem.

01:04 <Macer> with newer uboot sometimes you have to power it off and on like 5-10 times for it to finally work again lol

01:05 <Armbian-Discord> <T​enkawa> Interesting... my home RK3399 works flawlessly

01:05 <Macer> 2021.07 seems to usually take just the 2nd time for me. i know at some point dsimic helped me rebompile a dtb file for sd issues as well

01:06 <Macer> yah. this seems like a really strange problem. not really sure if it's uboot related, tf-a related or kernel related

01:06 <Armbian-Discord> <T​enkawa> nod... well cheers all for now.. gotta run.. be back tomorrow

01:06 <Macer> yup

01:13 <Armbian-Discord> <Z​anoryt> Any thoughts on this?

10:04 <Armbian-Discord> <I​gorPec> Did you look into output/debug folder for clues?

11:33 <lanefu> The Register: AWS puts latest homebrew Graviton3 Arm processor in production.

11:33 <lanefu> https://go.theregister.com/feed/www.theregister.com/2022/05/24/aws_puts_graviton3_arm_cpus/

11:33 <ArmbianHelper> ^ AWS puts Graviton3 Arm CPUs into production • The Register

12:05 <Armbian-Discord> <Z​anoryt> Yes I looked. No clues.

14:34 <Armbian-Discord> <M​anoftheSea> @IgorPec are we going to be able to include #3789 in Jade? This adds to the boot script to fall back to the variables available with the old-new (circa 2019?) u-boot environment.

14:35 <Armbian-Discord> <I​gorPec> sure we can

14:35 <Armbian-Discord> <I​gorPec> should just merge it?

14:36 <Armbian-Discord> <M​anoftheSea> I think so

14:40 <Armbian-Discord> <I​gorPec> done. how far are other things?

15:02 <Armbian-Discord> <M​anoftheSea> what other things?

15:03 <Armbian-Discord> <I​gorPec> If there are any in WIP state but matured enough

15:03 <Armbian-Discord> <M​anoftheSea> No, nothing else.

20:54 <Armbian-Discord> <Z​anoryt> I keep getting failed downloads (on random builds). Is there a way to specify a US mirror for this stuff? 05/26 20:38:20 [ERROR] CUID#7 - Download aborted. URI=https://armbian.lv.auroradev.org/dl/_rootfs/focal-minimal-arm64.fd4339569120f5a3cd604ea543653c83.tar.lz4 Exception: [AbstractCommand.cc:351] errorCode=3

20:54 <ArmbianHelper> ^ Error retrieving title. Check the log for more details.

20:54 <Armbian-Discord> URI=https://armbian.lv.auroradev.org/dl/_rootfs/focal-minimal-arm64.fd4339569120f5a3cd604ea543653c83.tar.lz4 -> [HttpSkipResponseCommand.cc:218] errorCode=3 Resource not found

20:54 <ArmbianHelper> ^ Error retrieving title. Check the log for more details.

23:50 <Armbian-Discord> <Z​anoryt> [ .... ] Installing from repository [ linux-image-current-rockchip64 ] [ .... ] Installing from repository [ linux-dtb-current-rockchip64 ] [ .... ] Installing from repository [ armbian-bsp-cli-rockpi-4b ] [ error ] ERROR in function install_deb_chroot [ main.sh:588 -> main.sh:549 -> debootstrap.sh:69 -> distributions.sh:342 -> image-helpers.sh:225 -> general.sh:0 ] [ error ] Installation of

23:50 <Armbian-Discord> armbian-bsp-cli-rockpi-4b failed [ rockpi-4b jammy no rockchip64 ] [ o.k. ] Process terminated [ error ] unmount_on_exit() called! [ main.sh:1 -> image-helpers.sh:0 ] [ o.k. ] Unmounting [ /root/armbian/.tmp/rootfs-97806bfd-93ed-4ba9-a9a6-e9066edad590/ ] [ error ] ERROR in function unmount_on_exit [ main.sh:1 -> image-helpers.sh:94 -> general.sh:0 ] [ error ] debootstrap-ng was interrupted

23:50 <Armbian-Discord> <Z​anoryt> this is starting to get exhausting

23:50 <Armbian-Discord> <Z​anoryt> endless build failures because of this

23:53 <nekomancer[m]> somehow I build helios64 image without /dev/fan* devices. but 5.17.5 in repo have them. how I did it?

23:53 <nekomancer[m]> magic

23:55 <Armbian-Discord> <Z​anoryt> From armbian-build/output/debug/debootstrap.log: Filesystem Size Used Avail Use% Mounted on overlay 63G 28G 32G 48% / tmpfs 64M 0 64M 0% /dev tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup shm 64M 0 64M 0% /dev/shm /dev/sda5 63G 28G 32G 48% /root/armbian tmpfs 7.9G 132K 7.9G 1% /tmp/dev/shm tmpfs 7.9G 0 7.9G 0% /proc/asound tmpfs 7.9G 0 7.9G 0% /proc/acpi tmpfs 7.9G 0 7.9G 0% /proc/scsi tmpfs 7.9G 0 7.9G 0%

23:55 <Armbian-Discord> /sys/firmware tmpfs 16G 1.3G 15G 8% /root/armbian/.tmp/rootfs-97806bfd-93ed-4ba9-a9a6-e9066edad590 Nothing looks bad there. Not clear by debootstrap is failing