Picostation M2 not saving

Report problems and success stories with Gargoyle on various hardware platforms.

Moderator: Moderators

Post Reply
tin
Posts: 5
Joined: Fri Jul 29, 2011 4:26 am

Picostation M2 not saving

Post by tin »

I've got a customer's PS M2 here. It had AirOS5.6.3 on it before we tried flashing Gargoyle 1.8.1. This ended badly, which I now believe is due to u-boot having been updated by UBNT in 5.6.2.

To cut things short, I now have sucessfully flashed Gargoyle 1.9.0 to it, and it boots... But it loses the settings on reboot.
Is this likely related to this:

Code: Select all

[   32.140000] jffs2_build_filesystem(): unlocking the mtd device... done.
[   32.140000] jffs2_build_filesystem(): erasing all blocks after the end marker...
[   32.490000] jffs2: Newly-erased block contained word 0x0 at offset 0x00380000
[   32.500000] jffs2: Newly-erased block contained word 0xdeadc0de at offset 0x00370000
[   32.510000] jffs2: Newly-erased block contained word 0xdeadc0de at offset 0x00360000
[   32.520000] jffs2: Newly-erased block contained word 0x314d043e at offset 0x00350000
[   32.520000] jffs2: Newly-erased block contained word 0x1a4bf99a at offset 0x00340000
[   32.550000] jffs2: Newly-erased block contained word 0x8a98408d at offset 0x00330000

[   35.440000] jffs2: Newly-erased block contained word 0xdeadc0de at offset 0x00000000
[   35.450000] done.
[   35.450000] jffs2: notice: (2208) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
[   35.560000] jffs2: Node CRC ffffffff != calculated CRC f09e7845 for node at 003d0da8
[   35.580000] jffs2: Node CRC ffffffff != calculated CRC f09e7845 for node at 003d1018
[   35.670000] jffs2: Node CRC ffffffff != calculated CRC f09e7845 for node at 003d2178
??

Any suggestions on how to fix this? I've tried flashing AirOS5.5.x back to it, but it just doesn't like going back to these. I do get a message about not updating u-boot when I try those over serial - do I need to tell uboot to replace itself somehow?

Lantis
Moderator
Posts: 7063
Joined: Mon Jan 05, 2015 5:33 am
Location: Australia

Re: Picostation M2 not saving

Post by Lantis »

its probably the 4mb of flash size that is doing it mate.
https://lantisproject.com/downloads/gargoylebuilds for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.

tin
Posts: 5
Joined: Fri Jul 29, 2011 4:26 am

Re: Picostation M2 not saving

Post by tin »

M2 has 8MB

Code: Select all

U-Boot 1.1.4.2-s956 (Jun 10 2015 - 10:54:50)

DRAM:  32 MB
Flash:  8 MB
PCIe WLAN Module found (#1).
Net:   eth0, eth1
Board: Ubiquiti Networks XM board (rev 1.0 e302)
Hit any key to stop autoboot:  0

Lantis
Moderator
Posts: 7063
Joined: Mon Jan 05, 2015 5:33 am
Location: Australia

Re: Picostation M2 not saving

Post by Lantis »

Apologies. Wrong wiki.

It's a pretty low level tech question you're asking. It's probably better aimed towards the openwrt forum.
https://lantisproject.com/downloads/gargoylebuilds for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.

Post Reply