How to install Pogoplug software on V2 Plug

[moonman]

xce.ko for kernel version 3.1.10-12-ARCH
Versions for Pogoplug V2 and Pogoplug Mobile/V4 are attached

Just to document a couple of changes: mtd-abi.h still isn't included: Ticket: https://github.com/archlinuxarm/PKGBUILDs/issues/206
Needed to edit Makefile to change "KERNELDIR ?= /lib/modules/$(shell uname -r)/build" to "KERNELDIR ?= /usr/lib/modules/$(shell uname -r)/build"

[rummy]

Right, I've kicked the tyres on this until my feet hurt!
I have 3 problems, almost certainly all related...

o I can not get my v2 pogo to show up in the "media" section on pogoplug's site.
o It also doesn't show up outside my LAN. Though inside the LAN it shows up fine.
o I can't "get Link" for anything on the ALARM pogo. (An unhandled RPC exception occurred on method enableShare: 804 [No such file])

I have a second "virgin" plug, and that is working exactly as advertised, so it's unlikely to be firewall stuff.

I'm not asking anyone to fix this, you've already done more than I could have hoped for.
But can someone confirm that it really is just me before I try a fresh install.

[moonman]

I dont have the problems you just described. Try to re-register your plug.

[rty]

Bad news.... After running Cloudengines fine for two weeks, my V2 rebooted again. I ran a modinfo on
/usr/local/cloudengines/bin/xce.ko and found that it reverted back to 2.0.5.10. I then copied 2.1.0 version of xce.ko (from Moonman) to overwrite 2.0.5.10, rebooted the V2, and Cloudengines worked fine again. Just to make sure that the xce.ko is 2.1.0, I did confirm it with modinfo

After about an hour, v2 rebooted again. I then went straight to run modinfo on /usr/local/cloudengines/bin.xce.ko and guess what.... it reverted back to 2.0.5.10! Help.... please....

[moonman]

It seems that it updates itself and overwrites xce module. We need to figure out a way to block updates.

[rty]

Yup... it keeps reverting to the old xce.ko after a while and V2 would reboot by itself in an hour or so. This is kinda weird because it was running fine before for more than two weeks. It is a total mystery to me where it picks up the old xce.ko from.

"chmod -w /usr/local/cloudengines/bin/xce.ko" doesn't help.

[WarheadsSE]

It self-updates the software

This is why I neutered rebooting from the driver, but there are other parts. Best option is to keep a copy in your actual modules folder, and alter the rc.d script to use that.

$this->bbcode_second_pass_quote('WarheadsSE', 'I')t self-updates the software .

[moonman]

neutered version will only help with reboots, it won't prevent the updates. I'm thinking if we find out what the host name is where it checks for the updates, then we can put it in hosts file assign some unreachable address (this is what crackers do )

[moonman]

$this->bbcode_second_pass_quote('rty', '')$this->bbcode_second_pass_quote('WarheadsSE', 'I')t self-updates the software .