I don’t find any bpi-r4 PRO 8GB firmwares, too.
you have to select snapshot in firmare-selector…r4pro is not part of stable (25.12)
I select snapshot, then I can fund the r4 pro 8g then I get the message: no model found
Devices are named
- Bananapi BPi-R4 Pro 4E
- Bananapi BPi-R4 Pro 8X
but most time i see this error:
Failed to fetch https://downloads.openwrt.org/snapshots//.overview.json
and i need to reload page with skipping the cache
Use the Firmware Builder on Linux instead of the website. That’s what I do, and it works.
I downloaded the suggested ‘custom’ build from SNAPSHOTS and Balena etched it onto an SD card. power up R4-pro 8x with dip switches down, appears on network at 192.168.1.1 with ports 22,53 and 80 open, and http port 80 serves me a login page, but no password I’ve tried (including blank) lets me in. Same via SSH. What’s the default password? or how can I reset it to blank as it should be for vanilla OpenWRT install? TIA.
EDIT: I reflashed the SD card and tried again, this time I get into the LUCI web UI with blank password. However, any attempted config changes (like to set password or enable ssh) are not taking effect. Are these things picky about what SD card they work with?..
EDIT again: etched a 3rd SD card (not even a hi perf one) and things are working better. something screwy with SD cards, confirmed here: Confusing Boot Switch Behavior & SD Card Issues - #6 by furkan
I had issues with sandisk cards (original,not fake) on R4Pro when running in real highspeed (52MHz) so i upstreamed the sd-overlay with 48MHZ where it looks stable so far (except some warnings on linux bootup which seem to be compensated - had no more in later runtime). Make sure you write not to fast and wait till cache is written completely to card.
yup. as mentioned, a cheaper card actually worked better for me. have no idea how to “upstream the sd-overlay with 48MHZ” but will google it if sd card issues persist.
for anyone else who runs into it, the OpenWRT snapshot build seems to enable the SFP wan port, so I had no link on the RJ45 wan port (furthest right, by the dc in port) until I ran the following at the u-boot prompt:
setenv bootconf_extra mt7988a-bananapi-bpi-r4-pro-8x-wan-phy
saveenv
reset
Also, it seems quite slow to bring up the web ui (luci?), so slow in fact that i have to “apply unchecked” when changing interface IP’s, as the UI isn’t available before the reconnect timeout reverts the change. Need to increase that timeout to avoid confusion/frustration…
The board support was with only sfp because phy driver needed for RJ45 of combo was not working and downstream driver was rejected. So first versions were with only SFP.
To not break existing setups after we (thx to pietro) got upstream phy driver working we made sfp default with the possibility to change via the overlay config.
We are waiting for the mux part where basic patches are currently upstreamed (phy port series from maxime) to drop overlays at some time as it allows automatic switch (via moddef0 gpio of sfp).
greek to me, but sounds good. really appreciate all the work. Bought this hoping to get a Rooter (GoldenOrb) build for it, (or OpenMPTCPRouter) and that may actually happen at some point now…
Finally and with help of claude I could install and run the snapshot yesterday. The move to emmc did work, too. Uboot is current.
I use the router as repeater which works well.
Should I upgrade the switch firmware to 1.0.85?
I did read there were some problems, but someone found solutions and did patch some files.
Are the patches already in the snapshot?
Without actual firmware you will experience issues with the lan-combo port. Files are not shipped with openwrt,but linked here in forum and my wiki
Meanwhile I did do the Firmware-Update and even a snapshot update. Both did work very well. Thank you. I am waiting for a mesh implementation in luci (I didn’t see anything yet) then I buy a second R4 Pro.
Can anyone help with a weird issue that is only just now popping up? It seems my device is bricking itself every roughly 24 hours. I am on the latest snapshot and I have confirmed I’m on the latest mxl firmware. Every day I wake up to find the radios are detected as “Generic Device” and do nothing. A reboot then takes down the wired connection also and I have no internet at all. Reflashing the latest snapshot fixes this, but then the same problem presents itself the next day. Anyone else have this? Only just started a few days ago for me.
Can you access the device via ethernet (wired)? Please look into logs (dmesg) before reboot. Sounds like a wifi only issue…reboot of course cut off wired connection but it should be restored when system is up again…maybe your flashing was incomplete? Which bootdevice are you using (sdmmc,spinand,emmc)?
Booting from sd card. When the radios went down I was able to ssh into it over ethernet, but after rebooting to see if that would fix the issue, I am no longer even able to ssh in wired.
Since it wont come up again after the reboot maybe the image on the sd card is somehow being corrupted because the sd card is dying? I’m really not sure though because whatever is occurring is only happening during early morning hours and it seems weird to me that a damaged sd card would only malfunction during a specific time frame, and that reflashing that same card would then WORK after. Very confused atm, gonna run out and get a different sd card because the only other one I have is fast and large and I’ve heard theres issues with those.
Can you do an lspci when the radios are not available?
If they don’t show up there, look at mediatek: filogic: keep MT7988 PCIe PEXTP clocks enabled by Folkerist · Pull Request #25751 · openwrt/openwrt · GitHub
I did that earlier and they did not show up, neither did my nvme drive as well. I’ll take a look at that right now, thank you!
How do I go about testing these patches? Do I need to download something and then use the firmware builder?