I got one (hence the delay with answering) and it does not help. No diods light up. I have not tried connecting serial cable, does it start emitting anything before the diods do? It does seem dead as a brick :-(. But can a strong USB PD charger do this? I have used it quite a lop with a small laptop and there has never been an issue.
Probably worth asking @M10 and @ardiehl as they have done things with the USB C power like powered by 12v without issue.
I can't see how your GAN fast charger could brick it.
1 Like
As for now i have bpi r4 powered by poe+ to 12V adapter... one of mine bpi r4 died after power cycle powered by lenovo 65W usb-c brick from my thinkpads. two other bpi r4 powered by normal dc jsck works like a charm since one year almost... i don't plan to buy openwrt one because i have no use for it.
Do you know if these implement PD specification or not? I aslo have one and it lists 5V at 3A, but nothing about PD and says "for Lenovo only", which I think is just trying to avoid liability. However, BPI R4 are supposed to accept 2V/5.2A or 19V/3.2A, which is a lot more than OpenWRT one.
So I tried with serial cable connected and this is what I get (only when also powered on with USB PD or POE):
�������H���������?��������1�����-�������-�������
���������������@������ x����������@��?�� ��#����?�� D�����!������������
����!�������������!@��P����P�@��'������@���@������ @��������������
Can I claim warranty on this or should I just throw it away? I am not sure what entity is manufacturing the device and also if this is a user mistake or not. I would normally think that a standard off-the-shelf USB-C charger should not manage to brick the device.
I can not say, but maybe @blogic might have some relevant information?
1 Like
the device requires 15V USB-PD. also it looks like the serial is outputing data but at the wrong baud rate. what rate did you set ?
1 Like
I was about to mention this. It looks like a lot of people are trying to use power supplies with the wrong spec.
It’s been noted clearly in the wiki as well as in this thread among others: OpenWrt One - Setup, Install, and Discussion - #172 by RuralRoots
I’d say the issue is more a misunderstanding of the process on power up of a PD power supply prior to boot.
Is the OpenWrt One capable of power redundancy with both POE and USB-power? Can I have both plugged in?
Yes you can plug both in, no this will not result in a fail-over configuration... I think the PoE port takes precedence and if that supplies too little current the One will behave flaky even if the USB power supply is connected.
1 Like
Ok! Yep. Everything is working. I swapped over to my POE switch, then unplugged USB power to one that is acting as a repeater, and no interruption. Fantastic. Thanks.
So i just started using my device.
Sadly the link negotation for the 1gbit interface seems to be faulty and defaults to 100mbit instead of 1gbit. (Connecting to it directly with a cat 7 cable works, but it doesn't like the cable in my wall). With previous routers this worked without any issue.
As i don't need 2.5gbit networking i just tried to swap eth0 and eth1 in /etc/config/network. In the hopes that the 2.5gbit interface works better. Now i got the correct link speed, but i couldn't get dhcp to work on eth1. Which left me with no ip on my wan interface.
Is there anything else i can try to get a 1gbit link?
Could it be the connector on your wall cable? I'd check that out, make sure all the pins are working right before anything else.
the old router worked fine.
I can also get a 1gbit link if i use the 2.5gbit port on my openwrt one. But i didn't manage to configure eth1 to work as wan port correctly.
As both of those work i doubt that the cable is an issue. (Although it definitely is part of the issue, as it worked fine with a short cable directly connected to my laptop)
Logs also look wierd, it seems like its trying to renogatiate eth1 currently but also restarts the connection once it dropped down to 100mbit?
Fri May 16 23:16:41 2025 kern.info kernel: [ 111.544857] br-lan: port 1(eth1) entered blocking state
Fri May 16 23:16:41 2025 daemon.notice netifd: Network device 'eth1' link is up
Fri May 16 23:16:41 2025 daemon.notice netifd: bridge 'br-lan' link is up
Fri May 16 23:16:41 2025 daemon.notice netifd: Interface 'lan' has link connectivity
Fri May 16 23:16:41 2025 kern.info kernel: [ 111.558296] br-lan: port 1(eth1) entered forwarding state
Fri May 16 23:16:42 2025 kern.info kernel: [ 112.592307] mtk_soc_eth 15100000.ethernet eth1: Link is Down
Fri May 16 23:16:42 2025 kern.info kernel: [ 112.598851] br-lan: port 1(eth1) entered disabled state
Fri May 16 23:16:42 2025 daemon.notice netifd: Network device 'eth1' link is down
Fri May 16 23:16:43 2025 daemon.notice netifd: bridge 'br-lan' link is down
Fri May 16 23:16:43 2025 daemon.notice netifd: Interface 'lan' has link connectivity loss
Fri May 16 23:16:43 2025 daemon.warn odhcpd[1926]: No default route present, overriding ra_lifetime to 0!
Fri May 16 23:16:44 2025 kern.info kernel: [ 114.657887] mtk_soc_eth 15100000.ethernet eth1: Link is Up - 1Gbps/Full - flow control off
Fri May 16 23:16:44 2025 kern.info kernel: [ 114.657934] br-lan: port 1(eth1) entered blocking state
Fri May 16 23:16:45 2025 daemon.notice netifd: Network device 'eth1' link is up
Fri May 16 23:16:45 2025 kern.info kernel: [ 114.671378] br-lan: port 1(eth1) entered forwarding state
Fri May 16 23:16:45 2025 daemon.notice netifd: bridge 'br-lan' link is up
Fri May 16 23:16:45 2025 daemon.notice netifd: Interface 'lan' has link connectivity
Fri May 16 23:16:46 2025 kern.info kernel: [ 115.695161] mtk_soc_eth 15100000.ethernet eth1: Link is Down
Fri May 16 23:16:46 2025 kern.info kernel: [ 115.701700] br-lan: port 1(eth1) entered disabled state
Fri May 16 23:16:46 2025 daemon.notice netifd: Network device 'eth1' link is down
Fri May 16 23:16:47 2025 daemon.warn odhcpd[1926]: No default route present, overriding ra_lifetime to 0!
Fri May 16 23:16:47 2025 daemon.notice netifd: bridge 'br-lan' link is down
Fri May 16 23:16:47 2025 daemon.notice netifd: Interface 'lan' has link connectivity loss
Fri May 16 23:16:47 2025 daemon.notice netifd: Network device 'eth1' link is up
Fri May 16 23:16:47 2025 kern.info kernel: [ 116.732982] mtk_soc_eth 15100000.ethernet eth1: Link is Up - 100Mbps/Full - flow control off
Fri May 16 23:16:47 2025 kern.info kernel: [ 116.741710] br-lan: port 1(eth1) entered blocking state
Fri May 16 23:16:47 2025 kern.info kernel: [ 116.746955] br-lan: port 1(eth1) entered forwarding state
If you don’t have a cable tester, sometimes a pencil eraser burnishing the pins on your Ethernet patch cable male ends and a cotton swab with 99% Isopropyl on the connectors in the wall jacks/female connectors can to wonders.
I have a BananaPi openwrt one that I had not used for a while. I recently powered it on again and noticed that the activity and status leds on the 2.5 Ghz RJ45 socket were constantly blinking even with no cable attached. Is this normal or is the unit faulty. I cannot remember whether this was the case the first time I used it. I re-flashed the unit and the blinking was still present.
Any ideas anyone?
It’s normal once the device has booted.
1 Like
Thanks,
A small piece of insulation tape will fix it 
.
But it still seems a little bit weird.
Roger