<html><head></head><body><div dir="auto">That, or use a low current source such as the fan header to control a 5v switch feeding the pi from a different source. Same net result, and no excess loads on your mobo. (Might be able to work this into the case using a spare power supply connector to feed it . . .)<br><br>Still have not figured out why though, but that's not relevant to what you are trying to accomplish.</div><br><br><div class="gmail_quote"><div dir="auto">On September 28, 2024 5:57:41 AM EDT, Jim Klimov via Nut-upsuser <nut-upsuser@alioth-lists.debian.net> wrote:</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div dir="ltr"><div>I guess I should scratch the idea about fan sockets as the power source: they are rated typically at 0.2A each, so fan headers should be expected 1A max (3A in some vendors/models), well under the 5A that the RPi5 wants.</div><div><br></div><div>Jim</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Sep 28, 2024 at 11:52 AM Jim Klimov <<a href="mailto:jimklimov%2Bnut@gmail.com">jimklimov+nut@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Follow-up:</div><div><br></div><div>* Powering the Raspberry Pi5 from an USB-C port wired on the motherboard was much more promising, it survived over 8 hours building NUT in a loop (in a tmpfs). And in the morning I found it turned off (red light on the Pi).</div><div><br></div><div>* Per <a href="https://stackoverflow.com/questions/4702216/controlling-a-usb-power-supply-on-off-with-linux" target="_blank">https://stackoverflow.com/questions/4702216/controlling-a-usb-power-supply-on-off-with-linux</a> it seems not possible to programmatically truly power-cycle USB port/hub, as 5V pins are "always on"; and per <a href="https://stackoverflow.com/a/16316401/4715872" target="_blank">https://stackoverflow.com/a/16316401/4715872</a> - at least not on MoBo ports (some hubs may have invested into being fully up to spec and control power fully). The referenced <a href="https://github.com/mvp/uhubctl" target="_blank">uhubctl</a> on my PC said "No compatible devices detected!" so I guess that's it.</div><div><br></div><div>* Whatever I could find with (suggestions welcome) `<span style="font-family:monospace">grep -r . `find /sys/devices/pci0000\:00 -name '*usb*port*'` /sys/bus/usb/devices/</span>` did not expose any differences beside timestamps with the RPi5 plugged and off, unplugged, and plugged back in again (with auto-boot). I hoped for some power draw statistics to at least learn which port it lives on, to try managing that somehow.</div><div><br></div><div>* Overall, housing the Pi inside a cooled and somewhat dust-protected PC case seems a neat idea, but for powering the Pi, it seems I would need to use a real wall-power adapter (as noted many times on the net, ideally Raspberry's own one as others tend to vary in actual voltage provided under load).</div><div><br></div><div>* But before that, I'm thinking if I could tap into the ATX power supply though (using "HDD" or "FDD" plugs) or fan sockets (could be individually manageable? gotta exempt one from OS/HW temperature-based mgmt then).</div><div><br></div><div>Did anyone trod these side paths yet, any learnings? :D</div><div><br></div><div>Jim</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Sep 27, 2024 at 4:43 PM Jim Klimov <<a href="mailto:jimklimov%2Bnut@gmail.com" target="_blank">jimklimov+nut@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">FWIW, a few lessons learned:<div dir="auto"><br></div><div dir="auto">* Different USB-A sized ports (even if marked USB-3.2) did not prove a stable source, with Pi5 occasionally turning off or rebooting. Sort of behaved well for days, but as soon as I added load like package installs or NUT builds, it did not survive 5 minutes...</div><div dir="auto"><br></div><div dir="auto">* Might be the MoBo turning off or cycling the port due to "overload"?..</div><div dir="auto"><br></div><div dir="auto">* Tried the `usb_resetter` script (referenced in NUT contribs) and host `dmesg` did show re-detection of keyboard etc., but a turned-off Pi did not boot up. Did not check much further, but did harbor hopes that a funny NUT driver could "shutdown/reboot" the USB port acting as an UPS for Pi...</div><div dir="auto"><br></div><div dir="auto">* The Pi power socket is dumb-USB so the host does not "see" any IDs about it.</div><div dir="auto"><br></div><div dir="auto">* Currently trying with a USB-C port on the MoBo, and a USB-C to USB-C cable rated for 60W -- and so far it survived a few loops of NUT fightwarn builds. Complains of undervoltage fairly frequently (every 30-60s), but now did not crash yet.</div><div dir="auto"><br></div><div dir="auto">Jim</div><div dir="auto"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Sep 16, 2024, 13:57 Greg Troxel via Nut-upsuser <<a href="mailto:nut-upsuser@alioth-lists.debian.net" target="_blank">nut-upsuser@alioth-lists.debian.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Kelly Byrd <<a href="mailto:kbyrd@memcpy.com" rel="noreferrer" target="_blank">kbyrd@memcpy.com</a>> writes:<br>
<br>
> With USB-C ports and cables, there are a ton of profiles, I don't know what<br>
> the new Pi's support, but likely something like 3A @ 5V, 9V, or 12V over<br>
> USB-C<br>
<br>
Up to the RPI4, I was pretty sure there wasn't PD, just 5V and it drew<br>
what it drew, and you hoped that the supply was big enough.<br>
<br>
It seems the RPI5 will use PD if given a capable supply. Looks like 5V<br>
5A, and it won't negotitate higher voltages. There's an official<br>
supply that does PD<br>
<br>
<a href="https://www.newark.com/raspberry-pi/sc1153/power-supply-usb-c-5-1v-5a-white/dp/82AK3955" rel="noreferrer noreferrer" target="_blank">https://www.newark.com/raspberry-pi/sc1153/power-supply-usb-c-5-1v-5a-white/dp/82AK3955</a><br>
<br>
and the output spec is<br>
<br>
5A at 5.1V, 3A at 9V, 2.25A at 12V, 1.8A at 15V<br>
<br>
looks like a TUV seal<br>
<br>
<br>
<br>
I find Jim's way of using this interesting, but my approach is totally<br>
different. First, when I'm using a Pi, it's because I want a low power<br>
computer that I can leave on all the time, or can place in a different<br>
physical location I don't particularly want to do things on a Pi instead<br>
of a desktop. And then I want it to be reliable.<br>
<br>
That leads me to plug a power supply into a UPS, or to use POE (from a<br>
POE switch which is plugged into a UPS). For RPI3, I found a POE<br>
ejector that splits the POE ethernet cable into ethernet only and a<br>
micro USB.<br>
<br>
<br>
_______________________________________________<br>
Nut-upsuser mailing list<br>
<a href="mailto:Nut-upsuser@alioth-lists.debian.net" rel="noreferrer" target="_blank">Nut-upsuser@alioth-lists.debian.net</a><br>
<a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser" rel="noreferrer noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a><br>
</blockquote></div>
</blockquote></div>
</blockquote></div>
</blockquote></div><div dir="auto"><div class='k9mail-signature'>-- <br>Sent from my Android device with K-9 Mail. Please excuse my brevity.</div></div></body></html>