He has different symptoms from what I see, he has red and green light, mine is red and blue, only boots to recovery mode if you press reset
No overheating on that bucket regulator, doesn’t even get hot, so I don’t see that as an issue
The y21c seems to be running in spec, produces similar numbers to yours
Tried that already, tried to switch storage media same issue
If you haven’t done so, try removing the BE14 card from the R4 mainboard. And test R4 standalone from there.
(be careful with your body’s electrostatic that might cause potential damage)
Tried that too lol, unfortunately it doesn’t do anything differently
lol. Sadly then likely some components damaged.
When you say “if I do the … trick it goes into initramfs recovery,” how do you confirm you’re in recovery mode?
I can access openwrt recovery luci
Pressing the reset button takes me to recovery too as I learnt
I can access openwrt recovery luci
Oh, I think your R4 hardware is mostly fine then. Little difference between recovery mode and “normal” from the perspective of loading the kernel.
Did you manage get connected to DEBUG port in recovery mode? Perhaps we can put this aside first.
Were you experimenting a custom kernel or loading a kerne that’s not vanilla OpenWrt?
Nope it was plain vanilla openwrt, no custom kernel and unfortunately uart still doesn’t work
If I recall correctly, the ip address of your R4 in recovery mode is 192.168.1.1. You can ssh into it if DEBUG port doesn’t work.
Then delete everything inside /sys/fs/pstore/* Then reboot, you’ll get into “normal” mode.
Given that said, a freshly burned sd card image should simply the whole process. But since you said it didn’t work for you, it’ll a little puzzling and the above procedure may still fail to get you in the normal mode.
Yeah I tried to delete everything in pstore but weirdly nothing is in there to delete
If there is nothing in /sys/fs/pstore, R4 will reboot into normal mode. If it can’t then very likely kernel panics while handling some hardware in booting normal mode. Though I expect something will be written to pstore, so that it triggers recovery mode.
Very weird in your case. Perhaps it has to do with the DEBUG port. Kernal can’t initialise it in early boot and revert back to recovery mode.
I would check on your R4 if any short circuits on the DEBUG port…
Yeah nothing,
imma just sell this kit off, if anyone’s interested feel free to pm me, I’ve bought an ubiquiti Dream Router 7, it’s not as powerful or customisable but at least it’ll be reliable and won’t die on me randomly
1 Like
Its serial port cable was directly connected to the CPU. Perhaps it is related to the static electricity mentioned by Kvic, which directly caused the serial port function of the CPU to be damaged.
Tried using the uart 1 etc and all I get is garbled junk with that
Other uart has to be configured to use as debug port and even when setting speed in cmdline it was still 9600 in my basic tests
Afaik @rmandrad did some further tests with uart1/2 here but also needs change in pinctrl and dts
Ah I see, well that’s out of the question then because I can’t boot off sd card, can only press reset and enter recovery mode