@geerlingguy will they work on the #TuringPi2 I wonder. However, would it make any sense at all even if it works, as they gave up and went for RK1 already with larger RAM.
This might be too little and too late.
@geerlingguy will they work on the #TuringPi2 I wonder. However, would it make any sense at all even if it works, as they gave up and went for RK1 already with larger RAM.
This might be too little and too late.
Turing Pi 2 - Retrofitting an EMC2301 Fancontroller
The Turing Pi 2 (v.2.4) has actually some secrets that just start to get uncovered. Looking closely at the board, you will find the red marked area with what seems to be an unpopulated 4-pin fan header (J16) and an unpopulated IC spot (U109).
These spots were, as found out by Sam Edwards (CFSworks) actually a place to install Molex 47053-1000 4-p
https://www.nico-maas.de/?p=2702
#Computer #Hardware #ProductSpecific #Projects #TuringPi2
Install a bootloader onto Turing RK1 eMMC memory
The Turing RK1 is a new Compute Module, made for the Turing Pi 2 board and with compability to the Nvidia Jetson cards in mind. While the board has some impressive specs ( https://docs.turingpi.com/docs/turing-rk1-specs-and-io-ports ) it had one small issue: The used Rockchip RK3588 needed a bootloader on its eMMC to be able t
https://www.nico-maas.de/?p=2669
#Computer #Hardware #ProductSpecific #Projects #RK1 #Turing #TuringRK1 #TuringPi2
The Turing Pi 2.5 is an updated version of the mini ITX cluster board for Raspberry Pi CM4 and NVIDIA Jetson modules. Changes include improved internal USB connections, HDMI improvements, an RTC battery fix, and more. https://buff.ly/460xpRY #TuringPi #ClusterBoard #RaspberryPiCM4 #TuringPi2.5 #NVIDIAJetson
good morning internets!
It's a beautiful day with fun things to work on, assuming the motivation to arise from the couch occurs before lulling into daydreams; 8hrs of sleep has me feeling uncommonly rested.
Today revisits this week's multi-day #Linux performance #benchmarking on an AMD EPYC (64C/128T, 1.5TB RAM, 192TB gen4 NVMe U.2). Then, some fun w/ Poudriere on ARM64 (#SolidRun #honeycomblx2 #FreeBSD), and maybe provisioning more #nvidia Orin-NX on a grief inducing #TuringPi2 board.
Been running K3s on four RK1 compute modules plugged into a TuringPi2 board for almost two weeks now. Everything except media stuff has been moved over, including this Mastodon instance.
It's been working a lot better than when I had previously tried RaspberyPis. Being able to use NVME storage (I'm using Longhorn) is a huge improvement to the RPi’s USB.
Parts for my Turing Pi v2 finally showed up. I've had the board for over 12 months but never had Pi's to stick in it. I now have 2 32GB Pi4's for it, and I think I will get a NVIDIA Jetson to go in the other board and essentially turn it into 1 node for general containers/API's and stuff, and the Jetson for running ollama with local models and doing some light model training/customization experimentation.
Before I get to that, I need my 20core Xeon Proxmox box up and running, my Ubiquiti gateway updated so I can run dual failover connections (NBN and Starlink) and my wifi hot spots for the house cabled and mounted in the right places.
time to get in the roof I think.
Oh and I got the latest protocol spec PDF from Polyaire for my AirTouch2+ and need to get my #AI powered aircon client functioning.
If I ever hit lotto, I might be able to get to some of this.. heh.
I've had the TuringPi2 (v2.4) for over a year, but never got around to setting it up until recently. The build is a WIP, waiting on two additional Jetson Orin NX 16GB modules and am testing different arrangements for the node storage, networking, and oob/remote access functions.
There are also several CM4 8GB modules, one presently installed, but the final deployment will be 3x Orin NX + 1x Xavier NX (16GB on all).
I own a Turing Pi2 and have three RK1 compute modules on order. I am going to set up a K8s lab using all 3 nodes. Should I save money and buy 512GB M.2 boot drives ($45 each) or go with 1TB at about $75 each? I guess it's only an extra $130 after tax... but I keep throwing money at this project...
https://docs.turingpi.com/docs/turing-pi2-intro
#homelab #TuringPi2 #k8s
Repairing a TuringPi 2
Intro
In April 2023 I finally got my TuringPi 2 - happy to finally got it into my hands I plugged it in, headed over to the TuringPi 2 Github ( https://github.com/turing-machines/BMC-Firmware ) got myself the latest BMC firmware and started to flash it. Thats when things got wrong: The power supply coils started to screech - and seconds later I was gree
https://www.nico-maas.de/?p=2637
#Computer #Hardware #ProductSpecific #Projects #Repair #ThermalCamera #TuringPi2
@lil5
First a quick rant: DO NOT BUY SWITCHBOT. They are unsafe and have no warranty and they can suck whatever piece of my anatomy they find most distasteful. We couldn't afford to replace them, but we had to anyway because Fire is Bad.
Ahem. Anyway. Yes! The grow is driven by #HomeAssistant (along with the rest of the #snarkhouse.) I can post the grow hardware BoM (my lights, plugs, etc) if you're interested, but the basic stack is #HomeAssistant as a #Truenas VM with everything else on ARM64 under #k3s. The control plane is CM4 on #TuringPi2, and Zigbee/Zwave pods talk to ser2sock + node-feature-detector to find their USB radios. (They are plugged into the client port of the Turing, so I can move them programmatically.)
On the far side of the radios, a cheap #esp32 Rover handles #bigear listening as well as the MiFloras and #BLE hygrometers. Inside the grow tent, an #esp32cam on a 3d printed mount watches over the grow. Power relays are a mix of old #Securifi peanuts and new #ThirdReality switches. (DO NOT BUY SWITCHBOT.)
Edit to add: I use power use to confirm that the lights and such are working, and templated 'traffic light' sensors (ok/error) confirm that the schedule, the switch and the power drain all align. If it goes red, the house starts shouting at us about it.
#zigbee #zwave #homeassistant #snarkhome #smarthome #homegrow #growyourown #smartgrow #switchbot #thirdreality #kubernetes #k8s #raspberrypi
I received 2 more CM4s that I thought were a canceled order (Dec/Jan time frame). I have them up on ebay, please boost for visibility. I had no intention of getting them after I ordered this other batch of CM4s. https://www.ebay.com/itm/176036779528 I am listing them at below retail starting bid.
#k8s #RaspberryPi #TuringPi2 #kubernetes #HomeLab #CM4
Finally received my Raspberry Pi CM4 at retail pricing.
4 @ 8GB Lite CM4s in a Turing Pi 2 board. After my 256GB endurance SD cards come in, time to create a K8s cluster.
I've had both bad and good experiences with #crowdfunded projects, but the #TuringPi2 is definitely a good one. They're continually working towards a better product, and I'm really looking forward to V2 of the firmware!
Here is today's reminder that #Discord is NOT a forum!
@turingpi@mastodon.social I'm looking at you. (Nice to see you here though!)
Discord is directly hostile to #opensource users.
It is not #accessible
It is not archived.
It does not allow anonymous viewing.
It is not searchable, and neither is it indexed by external search engines.
Data is walled in and unexportable.
Bonus round: Chat is also NOT a forum!
Chat is a chronological firehose, good for temporally transient information, largely ungrouped. Forums are a topical tree, good for longer-lasting information grouped by subject.
If you would write it down in real life (including email) then use a forum.
If you would only say it out loud (in the hallway or on a call) then chat is perfectly fine.
And if you say it out loud while someone else writes it down, tell your assistant to use a forum.
https://turingpi.com/tpi-case-current-status/
#turingpi #turingpi2 #rk1 #raspberrypi #snarkhome #oss
Here is today's reminder that #Discord is NOT a forum!
@turingpi I'm looking at you. (Nice to see you here though!)
Discord is directly hostile to #opensource users.
It is not #accessible
It is not archived.
It does not allow anonymous viewing.
It is not searchable, and neither is it indexed by external search engines.
Data is walled in and unexportable.
Bonus round: Chat is also NOT a forum!
Chat is a chronological firehose, good for temporally transient information, largely ungrouped. Forums are a topical tree, good for longer-lasting information grouped by subject.
If you would write it down in real life (including email) then use a forum.
If you would only say it out loud (in the hallway or on a call) then chat is perfectly fine.
And if you say it out loud while someone else writes it down, tell your assistant to use a forum.
Yesterday the #weedlings got Fitbits (ok, #miflora, but they don't know the difference) and I spent a bunch of time arguing with a plant API instead of just inputting my decent-enough values from last time.
Part of the arguing involved removing the old devices. A smart person would have saved the thresholds, but I'm not that person. Doh!
Pics tomorrowish when I get back to it and build the dash.
Today was supposed to be offline, so I spent it integrating #calico and #k3s and #linkerd and such in the new #homelab. I .. am bad at not being burnt out.
Some good news. Changes involved a cluster CIDR change, so I had to reset from zero. Thank FSM for flux2. I expected pain and it basically Just Worked.
@ramikrispin Can you get Compute Modules now for the #TuringPi2 ? I sort of gave up watching after the kickstarter campaign.
(hmm. Nope...)