Virtual memory file corrupted?

[desht]

Hi all,

Not sure at what point this happened, or if I did anything to cause it, but for some reason I'm no longer able to enable virtual memory file on my N800. /etc/osso_software_version is: RX-34+RX-44_2008SE_2.2007.50-2_PR_MR0

If I try to enable it, I get this message: "Virtual memory file corrupted and disabled. Use the Memory applet in the Control panel to enable it."

But if I do that, I just get the same message over & over. Resizing the file does not help either.

The swap file is /media/mmc2/.swap, right? (which is my internal memory card). I tried manually creating a swap file:


# cd /media/mmc2
# dd if=/dev/zero of=.swap bs=1024 count=65536
# mkswap .swap
# swapon .swap
# free
total used free shared buffers
Mem: 126828 123272 3556 0 20
Swap: 65528 0 65528
Total: 192356 123272 69084


So that seemed to work fine. But on the next reboot, I get the same "Virtual memory corrupted" error again.

Any ideas? Maybe my SD card is bad?

[GeneralAntilles]

Reformat your SD card.

[desht]

Just reformatted the card (4GB card, by the way) using sfdisk & mkdosfs. No luck, though, still getting the corrupted virtual memory error. The filesystem appears to be fine (df reports a size slightly smaller than the partition size as reported in /proc/partitions).

What's strange is that if I try to create a swap file of less than 64MB from the Memory applet, it succeeds & I can see the swap enabled when I type 'free'. Until I reboot, that is - I then get the corrupted message and swap is disabled.

If I try to create a swap file 64MB or greater, it fails immediately with the corrupted message.

If I create /media/mmc2/.swap manually (dd,mkswap,swapon), it succeeds regardless of size until the next reboot.

Something's seriously flaky here.

[desht]

It gets weirder. I can umount /media/mmc2 OK, but as soon as I run sfdisk on /dev/mmcblk0, something automatically re-mounts /media/mmc2 and attempts to re-enable virtual memory (resulting in the "virtual memory corrupted" error), even though I've told the system not to use it.

wtf?

[davep]

I have that same problem. I'm thinking of reflashing.