In addition I have tried hijacking the init script like this, but end up in an endless reboot before the HDMI or serial port come up. so I cannot see what the error is

root@cmp135:/sbin# ls /sbin/init
/sbin/init
root@cmp135:/sbin#

root@cmp135:/sbin# ls /sbin/myinit
/sbin/myinit
root@cmp135:/sbin#

root@cmp135:/sbin# chmod +x /sbin/myinit
root@cmp135:/sbin#

add this to /sbin/myinit
#!/bin/sh
set -e
echo "Setting up OverlayFS for root filesystem..."
mkdir -p /overlay/upper
mkdir -p /overlay/work
mkdir -p /newroot
mkdir -p /lower
mount -o ro /dev/mmcblk0p5 /lower
mount -t tmpfs tmpfs /overlay
mkdir -p /overlay/upper
mkdir -p /overlay/work
mount -t overlay overlay -o lowerdir=/lower,upperdir=/overlay/upper,workdir=/overlay/work /newroot
mount --move /proc /newroot/proc
mount --move /sys /newroot/sys
mount --move /dev /newroot/dev
/sbin/init

root@cmp135:/sbin# cat /boot/extlinux/extlinux.conf
label stm32mp135f-coremp135-buildroot
kernel /boot/zImage
devicetree /boot/stm32mp135f-coremp135.dtb
append root=/dev/mmcblk0p5 rw panic=5 quiet=false rootwait init=/sbin/myinit
root@cmp135:/sbin#

@ajb2k3 said in Forum blocking some Apple Private Relay IP addresses...:

@achayne I have never been IP banned but I have been affected by an IP ban.
The problem is that IPV4 is serverly limited with only 4,294,967,296 available but there are 8.2 billion people on earth. assuming that every one has a TV+computer+smartphone that means that about 24 billion IPV4 address are needed which just isn't available. when a modem or mobile device resets, its external IPV4 address resets which mean s that at some point, an innocent user will end up with one of the black listed IPV4 address.
I have had this a few time and had to reset the device and router to get a new IP address.

Sadly IPV4 is still sticking around, but luckily IPV6 has been making headway.
One plus to using Apple Private Relay, is you just open a new tab and have a new IP most of the time, although the pools are fairly small for each "Maintain general location" region. and the "Use country and time zone" pools also have larger groups of users crammed into the pools since there are less of those node locations globally. (I'm in NYC, so both the local & timezone pools were the same, and 11 of the 15 IPs were blocked by M5Stack).

@felmue said in Forum blocking some Apple Private Relay IP addresses...:

Hello @achayne

thank you for your explanation.

Yes, we are blocking locally.

That said, I lifted the block for now and we'll how it goes.

Thanks
Felix

Thanks for unblocking the addresses, hopefully the people in my timezone behave on this site and your monitoring algorithm isn't too harsh :)

I would be interested in the opposite way. How can I use the M5 library with the original micropython. "import M5" doesn't work.

thank you

@louisandthecat It probably is correct due to the losses from the internal power regulator.

@brrainz @erickadengler you could just try removing the connector and solder wire between each unit or now that you have a prototype made with units, look up the circuit diagrams on the site and build a custom pcb containing the devices.

Another route is to learn how to make a custom cable/connector.
BTW the connectors on the devices are male and not female and so adapters must be female not male

@kuriko Cool, this would be totally awesome!!

M5Unified is the more current library compared to M5Core2. The M5Core2 library has been deprecated, and users are encouraged to transition to M5Unified for ongoing support and updates. This transition is part of M5Stack's strategy to unify their libraries under M5Unified, which offers enhanced features and compatibility across various M5Stack devices.

experiencing this as well. uiflow2 also appears to be down.

edit: issues resolved now, just a few minutes after posting

@teastain Thanks!

@jwd3ca Why do you use a VPN to come here, what is to hide?
Why this VPN in particular? With some shady characters.
"former Mt. Gox (The famous BitCoin fraud/theft) CEO Mark Karpelès runs it.
https://en.wikipedia.org/wiki/Mark_Karpelès#
Read up.
I was gonna let it slide but you persisted.

@flypeek Awesome! Thank you. This led me to a solution.

@thinpoint

Tried a different cable?
Installed the drivers?