Hi All,
I'm really confuesd about my Pogoplug Pro behaviour, so I'm currently not sure on which point of "brickness" I'm currently at. I hope you can help me getting the Pogoplug run again.
After receivin my Pogoplug I decided to have it run an alternative firmware then the original. So Idecided to run ArchLinux on it.
Before I startet I made a flash dump of my Pogoplug with a script I found on the net - its name was something like dumpflash or so. The output of the script were the following files:
$this->bbcode_second_pass_code('', 'Pogoplug Flash Dump
│ .ceid
│ mtd0
│ mtd0.oob
│ mtd1
│ mtd1.oob
│ mtd2
│ mtd2.oob
│
└───.cedata
ceacct
cedb
cefoldersync')
After running the ArchLinux for a while I decided to give the original fimrware one more try. So I started to reestore the dumped Flash Images back to the mtdx partitions. The trouble began ...
My Pogoplug stopped working. I had the situation the front LED flashes and then turnes off. I read about surviveing the Pogoplug with a SATA disk and started to tryout. Nothing changed in the behaveiour. Next step was to build a serial cable.
After I got my own running cable I started reveiving the Pogoplugwith howtos like this: viewtopic.php?f=29&t=1203
Looks my problems get more worse ...
My current situation is the Pogoplug doesn't give any output if the SATA disk isn't connected.
If the SATA disk is connected I got the following output:
$this->bbcode_second_pass_code('', 'Stage-1 Bootloader Mon Nov 14 22:36:34 EST 2011
Attempting to set PLLA to 850MHz ...
plla_ctrl0 : 0x0000020A
plla_ctrl1 : 0x00330000
plla_ctrl2 : 0x0065008B
plla_ctrl3 : 0x000000F1
PLLA Set
Setup memory, testing
Reading disk 0, Image 0
Sector : 0x0000009A
Hdr len: 0x0001FB34
Hdr CRC: 0x2229BDCD
OK
Initialising disks
SATA PHY not ready for device 1
Detecting SATA busses:
Bus 0: Found first device OK
Device 0: Model: FUJITSU MHY2040BH Firm: 0000000B Ser#: K400T8828TU6
Type: Hard Disk
Capacity: 38154.3 MB = 37.2 GB (78140160 x 512)
Device 1: not available
Environment successfully read from disk 0 primary image
U-Boot 1.1.2 (Dec 31 2011 - 15:24:45)
U-Boot code: 60E00000 -> 60E1FB34 BSS: -> 60E5435C
RAM Configuration:
Bank #0: 60000000 128 MB
SRAM Configuration:
64KB at 0x50000000
NAND:128 MiB
In: serial
Out: serial
Err: serial
Setting Linux mem= boot arg value
IDE read: device 0 block # 288, count 1 ... 1 blocks read: OK
Hit any key to stop autoboot: 0
## Error: "boot_nand" not defined
$
')
Could anybody give me some hints how to get the original or ArchLinux running again on the system?
I'd love to hear some advice from the experts.
Thank you in advance.
Regards,
killer