home.social

#cm5 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #cm5, aggregated by home.social.

fetched live
  1. Stock Alert (DK): RPi CM5 - 4GB RAM, 64GB MMC, With Wifi is In Stock at Jkollerup.dk rpilocator.com?instock #CM5
    #rpilocatorDK

  2. Stock Alert (DK): RPi CM5 - 4GB RAM, 64GB MMC, With Wifi is In Stock at Jkollerup.dk rpilocator.com?instock #CM5
    #rpilocatorDK

  3. Stock Alert (DK): RPi CM5 - 4GB RAM, 64GB MMC, With Wifi is In Stock at Jkollerup.dk rpilocator.com?instock #CM5
    #rpilocatorDK

  4. Stock Alert (DK): RPi CM5 - 4GB RAM, 64GB MMC, With Wifi is In Stock at Jkollerup.dk rpilocator.com?instock #CM5
    #rpilocatorDK

  5. Stock Alert (DK): RPi CM5 - 4GB RAM, 64GB MMC, With Wifi is In Stock at Jkollerup.dk rpilocator.com?instock #CM5
    #rpilocatorDK

  6. Pi Server V3: Compute Module 5 Custom Build

    I’m back at it with the planned Pi server upgrade. I've finally been able to get hold of a Compute Module 5 with 8 GB of RAM and picked up a secondhand NVME SSD due to the crazy RAM and storage price hikes of the last six months or so. My current Pi 3 web servers had been pretty reliable, but a bit on the slow side, so this upgrade is much needed. Especially considering my second Pi 3 running Home Assistant had been a bit wobbly with regular crashes. I hadn't figured out why, as the web […]

    alexmasters.com/pi-server-v3/

  7. Pi Server V3: Compute Module 5 Custom Build

    I’m back at it with the planned Pi server upgrade. I've finally been able to get hold of a Compute Module 5 with 8 GB of RAM and picked up a secondhand NVME SSD due to the crazy RAM and storage price hikes of the last six months or so. My current Pi 3 web servers had been pretty reliable, but a bit on the slow side, so this upgrade is much needed. Especially considering my second Pi 3 running Home Assistant had been a bit wobbly with regular crashes. I hadn't figured out why, as the web […]

    alexmasters.com/pi-server-v3/

  8. Pi Server V3: Compute Module 5 Custom Build

    I’m back at it with the planned Pi server upgrade. I've finally been able to get hold of a Compute Module 5 with 8 GB of RAM and picked up a secondhand NVME SSD due to the crazy RAM and storage price hikes of the last six months or so. My current Pi 3 web servers had been pretty reliable, but a bit on the slow side, so this upgrade is much needed. Especially considering my second Pi 3 running Home Assistant had been a bit wobbly with regular crashes. I hadn't figured out why, as the web […]

    alexmasters.com/pi-server-v3/

  9. Pi Server V3: Compute Module 5 Custom Build

    I’m back at it with the planned Pi server upgrade. I've finally been able to get hold of a Compute Module 5 with 8 GB of RAM and picked up a secondhand NVME SSD due to the crazy RAM and storage price hikes of the last six months or so. My current Pi 3 web servers had been pretty reliable, but a bit on the slow side, so this upgrade is much needed. Especially considering my second Pi 3 running Home Assistant had been a bit wobbly with regular crashes. I hadn't figured out why, as the web […]

    alexmasters.com/pi-server-v3/

  10. One gripe with the Argon One Up is WiFi performance seems to be weak. Reading the documentation, it appears the CM5 defaults to using a PCB-trace antenna which lives behind a massive heatsink inside the base of the laptop.

    Not a recipe for success on microwave bands.

    jeffgeerling.com/blog/2022/ena describes how to switch it to the "external" antenna, which is presumably better placed.

    Doing this, it seems to receive a lot better.

    #ArgonOneUp #CM4 #CM5

  11. One gripe with the Argon One Up is WiFi performance seems to be weak. Reading the documentation, it appears the CM5 defaults to using a PCB-trace antenna which lives behind a massive heatsink inside the base of the laptop.

    Not a recipe for success on microwave bands.

    jeffgeerling.com/blog/2022/ena describes how to switch it to the "external" antenna, which is presumably better placed.

    Doing this, it seems to receive a lot better.

    #ArgonOneUp #CM4 #CM5

  12. One gripe with the Argon One Up is WiFi performance seems to be weak. Reading the documentation, it appears the CM5 defaults to using a PCB-trace antenna which lives behind a massive heatsink inside the base of the laptop.

    Not a recipe for success on microwave bands.

    jeffgeerling.com/blog/2022/ena describes how to switch it to the "external" antenna, which is presumably better placed.

    Doing this, it seems to receive a lot better.

    #ArgonOneUp #CM4 #CM5

  13. One gripe with the Argon One Up is WiFi performance seems to be weak. Reading the documentation, it appears the CM5 defaults to using a PCB-trace antenna which lives behind a massive heatsink inside the base of the laptop.

    Not a recipe for success on microwave bands.

    jeffgeerling.com/blog/2022/ena describes how to switch it to the "external" antenna, which is presumably better placed.

    Doing this, it seems to receive a lot better.

    #ArgonOneUp #CM4 #CM5

  14. One gripe with the Argon One Up is WiFi performance seems to be weak. Reading the documentation, it appears the CM5 defaults to using a PCB-trace antenna which lives behind a massive heatsink inside the base of the laptop.

    Not a recipe for success on microwave bands.

    jeffgeerling.com/blog/2022/ena describes how to switch it to the "external" antenna, which is presumably better placed.

    Doing this, it seems to receive a lot better.

    #ArgonOneUp #CM4 #CM5

  15. Been updating the OS on my old faithful (Panasonic CF-53), as well as setting up Gentoo on the Argon One Up CM5.

    Package builds are demonstrably faster on the CM5 than the CF-53. As in big builds like `webkit-gtk` are building a lot faster on the CM5 than they are on the CF-53.

    The CF-53 is a Core i5-3320M; hyperthreaded dual-core x86-64 running 2.6GHz, there's 8GB RAM.
    The CM5 is a Broadcom BCM2712; quad-core ARM Cortex A76 running at 2.4GHz, and the module I have sports 16GB RAM.

    The CM5 is leaving the old machine in the dust in all areas except video acceleration… haven't quite got that working in X11 yet (I'll move to Wayland when it's ready… it isn't now for my use case).

    I guess I'll know more once I get more of my standard desktop applications up and running.

    #CM5 #RaspberryPi #Gentoo

  16. Been updating the OS on my old faithful (Panasonic CF-53), as well as setting up Gentoo on the Argon One Up CM5.

    Package builds are demonstrably faster on the CM5 than the CF-53. As in big builds like `webkit-gtk` are building a lot faster on the CM5 than they are on the CF-53.

    The CF-53 is a Core i5-3320M; hyperthreaded dual-core x86-64 running 2.6GHz, there's 8GB RAM.
    The CM5 is a Broadcom BCM2712; quad-core ARM Cortex A76 running at 2.4GHz, and the module I have sports 16GB RAM.

    The CM5 is leaving the old machine in the dust in all areas except video acceleration… haven't quite got that working in X11 yet (I'll move to Wayland when it's ready… it isn't now for my use case).

    I guess I'll know more once I get more of my standard desktop applications up and running.

    #CM5 #RaspberryPi #Gentoo

  17. Been updating the OS on my old faithful (Panasonic CF-53), as well as setting up Gentoo on the Argon One Up CM5.

    Package builds are demonstrably faster on the CM5 than the CF-53. As in big builds like `webkit-gtk` are building a lot faster on the CM5 than they are on the CF-53.

    The CF-53 is a Core i5-3320M; hyperthreaded dual-core x86-64 running 2.6GHz, there's 8GB RAM.
    The CM5 is a Broadcom BCM2712; quad-core ARM Cortex A76 running at 2.4GHz, and the module I have sports 16GB RAM.

    The CM5 is leaving the old machine in the dust in all areas except video acceleration… haven't quite got that working in X11 yet (I'll move to Wayland when it's ready… it isn't now for my use case).

    I guess I'll know more once I get more of my standard desktop applications up and running.

    #CM5 #RaspberryPi #Gentoo

  18. Been updating the OS on my old faithful (Panasonic CF-53), as well as setting up Gentoo on the Argon One Up CM5.

    Package builds are demonstrably faster on the CM5 than the CF-53. As in big builds like `webkit-gtk` are building a lot faster on the CM5 than they are on the CF-53.

    The CF-53 is a Core i5-3320M; hyperthreaded dual-core x86-64 running 2.6GHz, there's 8GB RAM.
    The CM5 is a Broadcom BCM2712; quad-core ARM Cortex A76 running at 2.4GHz, and the module I have sports 16GB RAM.

    The CM5 is leaving the old machine in the dust in all areas except video acceleration… haven't quite got that working in X11 yet (I'll move to Wayland when it's ready… it isn't now for my use case).

    I guess I'll know more once I get more of my standard desktop applications up and running.

    #CM5 #RaspberryPi #Gentoo

  19. Been updating the OS on my old faithful (Panasonic CF-53), as well as setting up Gentoo on the Argon One Up CM5.

    Package builds are demonstrably faster on the CM5 than the CF-53. As in big builds like `webkit-gtk` are building a lot faster on the CM5 than they are on the CF-53.

    The CF-53 is a Core i5-3320M; hyperthreaded dual-core x86-64 running 2.6GHz, there's 8GB RAM.
    The CM5 is a Broadcom BCM2712; quad-core ARM Cortex A76 running at 2.4GHz, and the module I have sports 16GB RAM.

    The CM5 is leaving the old machine in the dust in all areas except video acceleration… haven't quite got that working in X11 yet (I'll move to Wayland when it's ready… it isn't now for my use case).

    I guess I'll know more once I get more of my standard desktop applications up and running.

    #CM5 #RaspberryPi #Gentoo

  20. I've built a custom kernel and updated my `cmdline.txt` to point `root=` at the Gentoo partition. Damn this thing flies on Gentoo.

    I had Debian momentarily on NVMe as I re-arranged things on the eMMC, and didn't notice much of a speed-up, notably opening a terminal window took ~30 seconds or more, whether running from eMMC or NVMe.

    On Gentoo, it's practically instant (booting from NVMe).

    I have some graphics acceleration issues to sort out in X11, but things are a lot more responsive.

    Maybe it's all that `systemd` junk. It certainly isn't my CFLAGS because they're as plain as they come: `-O2 -pipe`.

    #CM5 #Gentoo

  21. I've built a custom kernel and updated my `cmdline.txt` to point `root=` at the Gentoo partition. Damn this thing flies on Gentoo.

    I had Debian momentarily on NVMe as I re-arranged things on the eMMC, and didn't notice much of a speed-up, notably opening a terminal window took ~30 seconds or more, whether running from eMMC or NVMe.

    On Gentoo, it's practically instant (booting from NVMe).

    I have some graphics acceleration issues to sort out in X11, but things are a lot more responsive.

    Maybe it's all that `systemd` junk. It certainly isn't my CFLAGS because they're as plain as they come: `-O2 -pipe`.

    #CM5 #Gentoo

  22. I've built a custom kernel and updated my `cmdline.txt` to point `root=` at the Gentoo partition. Damn this thing flies on Gentoo.

    I had Debian momentarily on NVMe as I re-arranged things on the eMMC, and didn't notice much of a speed-up, notably opening a terminal window took ~30 seconds or more, whether running from eMMC or NVMe.

    On Gentoo, it's practically instant (booting from NVMe).

    I have some graphics acceleration issues to sort out in X11, but things are a lot more responsive.

    Maybe it's all that `systemd` junk. It certainly isn't my CFLAGS because they're as plain as they come: `-O2 -pipe`.

    #CM5 #Gentoo

  23. I've built a custom kernel and updated my `cmdline.txt` to point `root=` at the Gentoo partition. Damn this thing flies on Gentoo.

    I had Debian momentarily on NVMe as I re-arranged things on the eMMC, and didn't notice much of a speed-up, notably opening a terminal window took ~30 seconds or more, whether running from eMMC or NVMe.

    On Gentoo, it's practically instant (booting from NVMe).

    I have some graphics acceleration issues to sort out in X11, but things are a lot more responsive.

    Maybe it's all that `systemd` junk. It certainly isn't my CFLAGS because they're as plain as they come: `-O2 -pipe`.

    #CM5 #Gentoo

  24. I've built a custom kernel and updated my `cmdline.txt` to point `root=` at the Gentoo partition. Damn this thing flies on Gentoo.

    I had Debian momentarily on NVMe as I re-arranged things on the eMMC, and didn't notice much of a speed-up, notably opening a terminal window took ~30 seconds or more, whether running from eMMC or NVMe.

    On Gentoo, it's practically instant (booting from NVMe).

    I have some graphics acceleration issues to sort out in X11, but things are a lot more responsive.

    Maybe it's all that `systemd` junk. It certainly isn't my CFLAGS because they're as plain as they come: `-O2 -pipe`.

    #CM5 #Gentoo

  25. If #Essex #libraries keep downsizing in #CM5 area, it would be a situation of "Book lack in #Ongar " 😀

  26. If #Essex #libraries keep downsizing in #CM5 area, it would be a situation of "Book lack in #Ongar " 😀

  27. If #Essex #libraries keep downsizing in #CM5 area, it would be a situation of "Book lack in #Ongar " 😀

  28. If #Essex #libraries keep downsizing in #CM5 area, it would be a situation of "Book lack in #Ongar " 😀

  29. If #Essex #libraries keep downsizing in #CM5 area, it would be a situation of "Book lack in #Ongar " 😀

  30. One thing I'm noticing about this machine… `cmake` has a serious case of dependency amnesia.

    Currently I'm building the KDE Plasma applications… `kde-apps/kde-apps-meta`.

    I'll run `emerge`; it'll start building, then one package, `cmake` will claim "I can't find Qt${MODULE}" (it might be QtGui, QtQuick…etc.). I have `--keep-going` but despite this, `emerge` stops there even though there are _other_ packages it could merge in the meantime.

    I hit up-arrow, enter.

    `emerge` thinks for a moment, then successfully builds the package `cmake` said it couldn't find a dependency for. It'll go for a 8-20 packages… then the cycle repeats.

    Aside from that, the machine obviously isn't going to replace the Starbook in terms of performance… but on a per-watt basis, the machine's performance is impressive and the machine is quite usable.

    Gentoo is in a chroot for now, looking forward to getting a kernel building on the machine and seeing if I can coax Grub to run in `arm64-efi` mode.

    #Gentoo #CM5 #arm64

  31. One thing I'm noticing about this machine… `cmake` has a serious case of dependency amnesia.

    Currently I'm building the KDE Plasma applications… `kde-apps/kde-apps-meta`.

    I'll run `emerge`; it'll start building, then one package, `cmake` will claim "I can't find Qt${MODULE}" (it might be QtGui, QtQuick…etc.). I have `--keep-going` but despite this, `emerge` stops there even though there are _other_ packages it could merge in the meantime.

    I hit up-arrow, enter.

    `emerge` thinks for a moment, then successfully builds the package `cmake` said it couldn't find a dependency for. It'll go for a 8-20 packages… then the cycle repeats.

    Aside from that, the machine obviously isn't going to replace the Starbook in terms of performance… but on a per-watt basis, the machine's performance is impressive and the machine is quite usable.

    Gentoo is in a chroot for now, looking forward to getting a kernel building on the machine and seeing if I can coax Grub to run in `arm64-efi` mode.

    #Gentoo #CM5 #arm64

  32. One thing I'm noticing about this machine… `cmake` has a serious case of dependency amnesia.

    Currently I'm building the KDE Plasma applications… `kde-apps/kde-apps-meta`.

    I'll run `emerge`; it'll start building, then one package, `cmake` will claim "I can't find Qt${MODULE}" (it might be QtGui, QtQuick…etc.). I have `--keep-going` but despite this, `emerge` stops there even though there are _other_ packages it could merge in the meantime.

    I hit up-arrow, enter.

    `emerge` thinks for a moment, then successfully builds the package `cmake` said it couldn't find a dependency for. It'll go for a 8-20 packages… then the cycle repeats.

    Aside from that, the machine obviously isn't going to replace the Starbook in terms of performance… but on a per-watt basis, the machine's performance is impressive and the machine is quite usable.

    Gentoo is in a chroot for now, looking forward to getting a kernel building on the machine and seeing if I can coax Grub to run in `arm64-efi` mode.

    #Gentoo #CM5 #arm64

  33. One thing I'm noticing about this machine… `cmake` has a serious case of dependency amnesia.

    Currently I'm building the KDE Plasma applications… `kde-apps/kde-apps-meta`.

    I'll run `emerge`; it'll start building, then one package, `cmake` will claim "I can't find Qt${MODULE}" (it might be QtGui, QtQuick…etc.). I have `--keep-going` but despite this, `emerge` stops there even though there are _other_ packages it could merge in the meantime.

    I hit up-arrow, enter.

    `emerge` thinks for a moment, then successfully builds the package `cmake` said it couldn't find a dependency for. It'll go for a 8-20 packages… then the cycle repeats.

    Aside from that, the machine obviously isn't going to replace the Starbook in terms of performance… but on a per-watt basis, the machine's performance is impressive and the machine is quite usable.

    Gentoo is in a chroot for now, looking forward to getting a kernel building on the machine and seeing if I can coax Grub to run in `arm64-efi` mode.

    #Gentoo #CM5 #arm64

  34. One thing I'm noticing about this machine… `cmake` has a serious case of dependency amnesia.

    Currently I'm building the KDE Plasma applications… `kde-apps/kde-apps-meta`.

    I'll run `emerge`; it'll start building, then one package, `cmake` will claim "I can't find Qt${MODULE}" (it might be QtGui, QtQuick…etc.). I have `--keep-going` but despite this, `emerge` stops there even though there are _other_ packages it could merge in the meantime.

    I hit up-arrow, enter.

    `emerge` thinks for a moment, then successfully builds the package `cmake` said it couldn't find a dependency for. It'll go for a 8-20 packages… then the cycle repeats.

    Aside from that, the machine obviously isn't going to replace the Starbook in terms of performance… but on a per-watt basis, the machine's performance is impressive and the machine is quite usable.

    Gentoo is in a chroot for now, looking forward to getting a kernel building on the machine and seeing if I can coax Grub to run in `arm64-efi` mode.

    #Gentoo #CM5 #arm64

  35. Stock Alert (US): RPi CM5 - 8GB RAM, No MMC, With Wifi is In Stock at Pishop 25 units in stock. rpilocator.com?instock #CM5
    #rpilocatorUS

  36. Stock Alert (US): RPi CM5 - 8GB RAM, No MMC, With Wifi is In Stock at Pishop 25 units in stock. rpilocator.com?instock #CM5
    #rpilocatorUS

  37. Stock Alert (US): RPi CM5 - 8GB RAM, No MMC, With Wifi is In Stock at Pishop 25 units in stock. rpilocator.com?instock #CM5
    #rpilocatorUS

  38. Stock Alert (US): RPi CM5 - 8GB RAM, No MMC, With Wifi is In Stock at Pishop 25 units in stock. rpilocator.com?instock #CM5
    #rpilocatorUS

  39. Stock Alert (US): RPi CM5 - 8GB RAM, No MMC, With Wifi is In Stock at Pishop 25 units in stock. rpilocator.com?instock #CM5
    #rpilocatorUS

  40. Stock Alert (DK): RPi CM5 - 8GB RAM, No MMC, With Wifi is In Stock at Jkollerup.dk rpilocator.com?instock #CM5
    #rpilocatorDK

  41. Stock Alert (DK): RPi CM5 - 8GB RAM, No MMC, With Wifi is In Stock at Jkollerup.dk rpilocator.com?instock #CM5
    #rpilocatorDK

  42. Stock Alert (DK): RPi CM5 - 8GB RAM, No MMC, With Wifi is In Stock at Jkollerup.dk rpilocator.com?instock #CM5
    #rpilocatorDK

  43. Stock Alert (DK): RPi CM5 - 8GB RAM, No MMC, With Wifi is In Stock at Jkollerup.dk rpilocator.com?instock #CM5
    #rpilocatorDK

  44. Stock Alert (DK): RPi CM5 - 8GB RAM, No MMC, With Wifi is In Stock at Jkollerup.dk rpilocator.com?instock #CM5
    #rpilocatorDK

  45. The other day, a 1TB SSD turned up (Western Digital Green SN3000). I tried booting from NVMe but didn't notice much of a speed boost… however for storage of my personal data, NVMe is by far the safest place to keep it: if something destroys the compute module, my data is entombed on the eMMC unless I manage to successfully de-solder it and tack wires to the balls to interface to it.

    It's also a better place for swap space. The NVMe should have better endurance and performance than the eMMC. I'll keep Debian on the eMMC (where the 64GB size is less of a constraint), `/home` and swap on NVMe.

    I've set up a 180GB partition formatted BTRFS, and have Gentoo building inside that.

    So far this machine this machine is taking Gentoo in its stride. I intend to get a bootloader going so I can comfortably dual-boot (maybe U-boot, GRUB or rEFInd?) but my journey into the ARM world is going fine so far.

    #Gentoo #RaspberryPi #CM5

  46. The other day, a 1TB SSD turned up (Western Digital Green SN3000). I tried booting from NVMe but didn't notice much of a speed boost… however for storage of my personal data, NVMe is by far the safest place to keep it: if something destroys the compute module, my data is entombed on the eMMC unless I manage to successfully de-solder it and tack wires to the balls to interface to it.

    It's also a better place for swap space. The NVMe should have better endurance and performance than the eMMC. I'll keep Debian on the eMMC (where the 64GB size is less of a constraint), `/home` and swap on NVMe.

    I've set up a 180GB partition formatted BTRFS, and have Gentoo building inside that.

    So far this machine this machine is taking Gentoo in its stride. I intend to get a bootloader going so I can comfortably dual-boot (maybe U-boot, GRUB or rEFInd?) but my journey into the ARM world is going fine so far.

    #Gentoo #RaspberryPi #CM5

  47. The other day, a 1TB SSD turned up (Western Digital Green SN3000). I tried booting from NVMe but didn't notice much of a speed boost… however for storage of my personal data, NVMe is by far the safest place to keep it: if something destroys the compute module, my data is entombed on the eMMC unless I manage to successfully de-solder it and tack wires to the balls to interface to it.

    It's also a better place for swap space. The NVMe should have better endurance and performance than the eMMC. I'll keep Debian on the eMMC (where the 64GB size is less of a constraint), `/home` and swap on NVMe.

    I've set up a 180GB partition formatted BTRFS, and have Gentoo building inside that.

    So far this machine this machine is taking Gentoo in its stride. I intend to get a bootloader going so I can comfortably dual-boot (maybe U-boot, GRUB or rEFInd?) but my journey into the ARM world is going fine so far.

    #Gentoo #RaspberryPi #CM5

  48. The other day, a 1TB SSD turned up (Western Digital Green SN3000). I tried booting from NVMe but didn't notice much of a speed boost… however for storage of my personal data, NVMe is by far the safest place to keep it: if something destroys the compute module, my data is entombed on the eMMC unless I manage to successfully de-solder it and tack wires to the balls to interface to it.

    It's also a better place for swap space. The NVMe should have better endurance and performance than the eMMC. I'll keep Debian on the eMMC (where the 64GB size is less of a constraint), `/home` and swap on NVMe.

    I've set up a 180GB partition formatted BTRFS, and have Gentoo building inside that.

    So far this machine this machine is taking Gentoo in its stride. I intend to get a bootloader going so I can comfortably dual-boot (maybe U-boot, GRUB or rEFInd?) but my journey into the ARM world is going fine so far.

    #Gentoo #RaspberryPi #CM5

  49. The other day, a 1TB SSD turned up (Western Digital Green SN3000). I tried booting from NVMe but didn't notice much of a speed boost… however for storage of my personal data, NVMe is by far the safest place to keep it: if something destroys the compute module, my data is entombed on the eMMC unless I manage to successfully de-solder it and tack wires to the balls to interface to it.

    It's also a better place for swap space. The NVMe should have better endurance and performance than the eMMC. I'll keep Debian on the eMMC (where the 64GB size is less of a constraint), `/home` and swap on NVMe.

    I've set up a 180GB partition formatted BTRFS, and have Gentoo building inside that.

    So far this machine this machine is taking Gentoo in its stride. I intend to get a bootloader going so I can comfortably dual-boot (maybe U-boot, GRUB or rEFInd?) but my journey into the ARM world is going fine so far.

    #Gentoo #RaspberryPi #CM5

  50. Stock Alert (US): RPi CM5 - 4GB RAM, 16GB MMC, No Wifi is In Stock at Pishop 212 units in stock. rpilocator.com?instock #CM5
    #rpilocatorUS

  51. Stock Alert (US): RPi CM5 - 4GB RAM, 16GB MMC, No Wifi is In Stock at Pishop 212 units in stock. rpilocator.com?instock #CM5
    #rpilocatorUS

  52. Stock Alert (US): RPi CM5 - 4GB RAM, 16GB MMC, No Wifi is In Stock at Pishop 212 units in stock. rpilocator.com?instock #CM5
    #rpilocatorUS

  53. Stock Alert (US): RPi CM5 - 4GB RAM, 16GB MMC, No Wifi is In Stock at Pishop 212 units in stock. rpilocator.com?instock #CM5
    #rpilocatorUS

  54. Stock Alert (US): RPi CM5 - 4GB RAM, 16GB MMC, No Wifi is In Stock at Pishop 212 units in stock. rpilocator.com?instock #CM5
    #rpilocatorUS

  55. Damn, I knew these things were small, but I didn't imagine *THIS* small! #RaspberryPi #CM5

  56. Damn, I knew these things were small, but I didn't imagine *THIS* small! #RaspberryPi #CM5

  57. Damn, I knew these things were small, but I didn't imagine *THIS* small! #RaspberryPi #CM5

  58. Damn, I knew these things were small, but I didn't imagine *THIS* small! #RaspberryPi #CM5

  59. Damn, I knew these things were small, but I didn't imagine *THIS* small! #RaspberryPi #CM5