Pi52 Rack modules are glitchy
52Pi modules not working with Pi 5? (SD extender keeps throwing I/O errors)
So I've got a Pi 5 in a 52Pi rack setup, and the SD extender module has been a nightmare. Card works perfectly in the native microSD slot, boots clean, zero errors. But the moment I put it through the 52Pi extender (front module with ribbon to back module), I get immediate I/O error floods during boot,
The weird part: the HDMI passthrough on the front module works fine with no problems. It's just the SD reader that's broken.
What I've tried:
Swapped the back/extender module (fresh one)
Swapped the ribbon cable (brand new)
Tried two different front modules
Reseated everything, tightened ribbons, the works
Every config fails the same way. The card reads perfectly when I bypass the whole extender and use the Pi's native slot directly.
Is this a known issue? Like, is the 52Pi extender just not compatible with Pi 5, or am I missing something obvious? Seems weird that swapping multiple components doesn't help if it's just a bad part.
Anyone else run into this?
https://preview.redd.it/j6oqfakem0ch1.jpg?width=1140&format=pjpg&auto=webp&s=02d1d034e5ad9e5400f44e0f049f3336f70e54f7
https://redd.it/1uqu5tw
@r_raspberry_pi
52Pi modules not working with Pi 5? (SD extender keeps throwing I/O errors)
So I've got a Pi 5 in a 52Pi rack setup, and the SD extender module has been a nightmare. Card works perfectly in the native microSD slot, boots clean, zero errors. But the moment I put it through the 52Pi extender (front module with ribbon to back module), I get immediate I/O error floods during boot,
mmcblk0 throwing read/write failures everywhere, filesystem goes read-only, system hangs.The weird part: the HDMI passthrough on the front module works fine with no problems. It's just the SD reader that's broken.
What I've tried:
Swapped the back/extender module (fresh one)
Swapped the ribbon cable (brand new)
Tried two different front modules
Reseated everything, tightened ribbons, the works
Every config fails the same way. The card reads perfectly when I bypass the whole extender and use the Pi's native slot directly.
Is this a known issue? Like, is the 52Pi extender just not compatible with Pi 5, or am I missing something obvious? Seems weird that swapping multiple components doesn't help if it's just a bad part.
Anyone else run into this?
https://preview.redd.it/j6oqfakem0ch1.jpg?width=1140&format=pjpg&auto=webp&s=02d1d034e5ad9e5400f44e0f049f3336f70e54f7
https://redd.it/1uqu5tw
@r_raspberry_pi
Pi won't connect to the wifi after ssd migration
Hi all, I'm hoping someone can help me. I have officially run out of ideas. I recently got a geekworm m2 hat for my rpi5 and an integral SSD. I've moved my librelec install to the SSD and ever since then ive had issues with the WiFi connection on it. Seems I can connect to it, but every time I reboot the pi, I have to manually reconnect to the WiFi. The connection state is always down as failed, but it seems to connect ok. I then am unable to connect via ssh, I keep getting a timeout then connection stopped by the pi.
Sorry for the big old chunk of text, I've asked AI and it suggests that maybe the SSD is drawing too much power but im using the official power adapter. I've also tried making the WiFi kick in later after boot and clearing the connman cache. Anyonr got any ideas for things to check?
https://redd.it/1uqz605
@r_raspberry_pi
Hi all, I'm hoping someone can help me. I have officially run out of ideas. I recently got a geekworm m2 hat for my rpi5 and an integral SSD. I've moved my librelec install to the SSD and ever since then ive had issues with the WiFi connection on it. Seems I can connect to it, but every time I reboot the pi, I have to manually reconnect to the WiFi. The connection state is always down as failed, but it seems to connect ok. I then am unable to connect via ssh, I keep getting a timeout then connection stopped by the pi.
Sorry for the big old chunk of text, I've asked AI and it suggests that maybe the SSD is drawing too much power but im using the official power adapter. I've also tried making the WiFi kick in later after boot and clearing the connman cache. Anyonr got any ideas for things to check?
https://redd.it/1uqz605
@r_raspberry_pi
Reddit
From the raspberry_pi community on Reddit
Explore this post and more from the raspberry_pi community
Four months ago I showed my retro-futuristic Pi camera here. Today it's fully released - firmware, print files, assembly manual. Build your own SATURNIX
https://redd.it/1urysi6
@r_raspberry_pi
https://redd.it/1urysi6
@r_raspberry_pi
Reddit
From the raspberry_pi community on Reddit: Four months ago I showed my retro-futuristic Pi camera here. Today it's fully released…
Explore this post and more from the raspberry_pi community
DroneAware community network update: 160 sensors and 1.6 million Remote ID detections
https://redd.it/1ut0n1b
@r_raspberry_pi
https://redd.it/1ut0n1b
@r_raspberry_pi
Reddit
From the raspberry_pi community on Reddit: DroneAware community network update: 160 sensors and 1.6 million Remote ID detections
Explore this post and more from the raspberry_pi community
Issues with connecting to Raspberry Pi Connect
Hi all. I am completely new to RPI, I only just got my first one (Raspberry Pi 4B 1GB) mostly to experiment and try to learn.
I am now trying to use Raspberry Pi Connect as I don't have a monitor cable for it. The RPI is connected to my network, I am able to control it from my PC, and it pings outside the network (I've tried google.com and raspberrypi.com with success). It also displays as online on connect.raspberrypi.com.
However, when actually trying to connect to it, whether by screen share or remote shell, nothing happens. It stalls at "Waiting for response from raspberrypi".
$ rpi-connect doctor returns the following:
Screen sharing is supported by this version of rpi-connect
✓ Wayland compositor available
✓ Screen sharing services enabled and active
✓ Communication with Raspberry Pi Connect WebSocket server
✗ Communication with Raspberry Pi Connect API - Please check your connection to the internet.
Further diagnostics will be available once communication with Raspberry Pi Connect API is successful.
✗ Some checks failed
I am honestly not entirely sure where to go from here. I haven't been able to find a solution to this anywhere else - does anyone have any idea what I can do to fix this?
https://redd.it/1usk4nn
@r_raspberry_pi
Hi all. I am completely new to RPI, I only just got my first one (Raspberry Pi 4B 1GB) mostly to experiment and try to learn.
I am now trying to use Raspberry Pi Connect as I don't have a monitor cable for it. The RPI is connected to my network, I am able to control it from my PC, and it pings outside the network (I've tried google.com and raspberrypi.com with success). It also displays as online on connect.raspberrypi.com.
However, when actually trying to connect to it, whether by screen share or remote shell, nothing happens. It stalls at "Waiting for response from raspberrypi".
$ rpi-connect doctor returns the following:
Screen sharing is supported by this version of rpi-connect
✓ Wayland compositor available
✓ Screen sharing services enabled and active
✓ Communication with Raspberry Pi Connect WebSocket server
✗ Communication with Raspberry Pi Connect API - Please check your connection to the internet.
Further diagnostics will be available once communication with Raspberry Pi Connect API is successful.
✗ Some checks failed
I am honestly not entirely sure where to go from here. I haven't been able to find a solution to this anywhere else - does anyone have any idea what I can do to fix this?
https://redd.it/1usk4nn
@r_raspberry_pi
Reddit
From the raspberry_pi community on Reddit
Explore this post and more from the raspberry_pi community