you really don't want to use it ...
1 Like
I believe you also need to enable battery charging (assuming your battery is rechargeable) by editing /boot/config.txt and adding:
dtparam=rtc=bbat_vchg=3000000
Can check with:
cat /sys/devices/platform/soc/soc:rpi_rtc/rtc/rtc0/charging_voltage
My battery is a rechargable (Panasonic ML-2020 lithium manganese dioxide rechargeable battery) but at least for Raspberry Pi OS you need to change a config setting to enable charging.
1 Like
Wifi works at RPI5 as access point. Use this snapshot for temp.
that's not what he said, and it's not the official build.
also, friends don't let friends run Broadcom wifi.
Anyone know how to override the fan control? Thanks
Hello y'all,
Anyone had luck with using the PCIE with wifi? Have two cards, one wasn't even seen with lspci and the other one was.
root@OpenWrt:~# lspci
0000:00:00.0 PCI bridge: Broadcom Inc. and subsidiaries BCM2712 PCIe Bridge (rev 21)
0000:01:00.0 Network controller: Intel Corporation Wireless 3165 (rev 79)
0001:00:00.0 PCI bridge: Broadcom Inc. and subsidiaries BCM2712 PCIe Bridge (rev 21)
0001:01:00.0 Ethernet controller: Raspberry Pi Ltd RP1 PCIe 2.0 South Bridge
installed " kmod-iwlwifi " && " iwlwifi-firmware-iwl-7265d " and still not showing in the interfaces. Is there another package(s) I need to add or something else I need to do?
Or has anyone had any wifi working through the PCIE? Thanks
for openwrt use (router only) it makes more sense now to use The Raspberry Pi 5 SBC is now available with 2GB RAM for just $50 - CNX Software (cnx-software.com)
Anyone else having issues getting usb to boot for pi 5?
I found the issue. Seems like if you restore a backup file. It will change the cmdline.txt back to using PARTUUID instead of /dev/sda2
Just jumping in here. Picked up the 2GB model myself as one last attempt at my mobile 5G router project before I shelve it for a bit.
One thing I did notice when toying with the built in Wifi in AP mode is on the latest snapshot revision I couldn't get it to show on my Windows machine or in a Wifi scanner app on my Pixel 6A. Reviewing the Git history, it looks like the upstream patch mentioned here that was previously removed was added back in on later commits. Manually removing it from my local copy and things appear to work again. I'm able to see the SSID and connect successfully. So not sure if this re-add of that patch was intentional or just missed? To be fair I didn't do a super thorough check with/without the patch.
Internal wifi works poorly, latest snapshot
internal wifi will always suck, say hi to Broadcom FOSS.
Tested pi5 with the latest snapshot (on 09/29/24) wireguard performance was VERY bad ~500-750kbps, trying to adjust MTU didn't help (fills like the problem is there). At the same time I tested pi4 with the exact same configuration (also using snapshot) with result of ~600mbps
Humor me for a moment on the Wifi situation as I was doing a little bit of research on it last night. Given Raspbian and other distros don't seem to really have issues to speak of, there has to be some disconnect. Is it down to the firmware or drivers themselves? I totally get the FOSS argument and how that kinda limits what can be done with OpenWRT officially. For a private build with no care if closed source/non-FOSS code is used, is there a path that can be taken to make it more reliable? I've seen plenty of mentions of varying firmware versions for the Wifi chipset but still doing the research on that front.
The project I'm working on with the Pi 5, if it works out positively, I'd really like to have the internal wifi available as a simple short range single client AP and not just treat it as a boat anchor and have to hang another dongle off the side.