Is fixed by:
https://github.com/openwrt/openwrt/pull/4882
On 12/25/21 22:02, Nick wrote:
Thanks for your answer, but it did not help. :/
I will look at the change-log again and see if something changed.
On 12/25/21 19:46, David Bauer wrote:
Hi Nick,
On 12/25/21 16:49, Nick wrote:
The
I think I fixed it accidentally by this PR:
https://github.com/openwrt/openwrt/pull/4879
The flash memory is not enough anymore using 5.10. I would be happy if
it could be merged, soon. Otherwise ubnt-xm targets are broken in master.
Bests
Nick
On 12/25/21 22:02, Nick wrote:
Thanks for your
Thanks for your answer, but it did not help. :/
I will look at the change-log again and see if something changed.
On 12/25/21 19:46, David Bauer wrote:
Hi Nick,
On 12/25/21 16:49, Nick wrote:
The flash-chip mx25l6405d that is contained in the Ubiquity
Nanostation M5 (XM) is not able to write
Hi Nick,
On 12/25/21 16:49, Nick wrote:
The flash-chip mx25l6405d that is contained in the Ubiquity Nanostation
M5 (XM) is not able to write to the flash with kernel 5.10. Probably,
caused by invalid block protection clearing. For example the logread
contains a lot of those messages:
The flash-chip mx25l6405d that is contained in the Ubiquity Nanostation
M5 (XM) is not able to write to the flash with kernel 5.10. Probably,
caused by invalid block protection clearing. For example the logread
contains a lot of those messages:
jffs2: Newly-erased block contained word
