Quantcast
Viewing all 902 articles
Browse latest View live
↧

recovering a pogoplug from a failed (quasi-bricked) linux installation attempt (7 replies)

November 11, 2016, 10:28 pm
$
0
0
Some time ago (maybe two or three years) I have (quasi) bricked a Pogoplug E02 Model attempting to install Debian on it. I leave it as I was since I haven't the skill to "repair" it. Now a friend of mine who is very competent has disassembled it and he has told me that the device is not dead and reacts to a jtag connection with some linux output.
Is this the right place to ask for help? Otherwise, where?
I can post the photos of the devices and the output of the trasmitted commands.
Thank you in advance.
↧
Search

Pogo V4 installation problem (1 reply)

November 9, 2016, 11:39 pm
$
0
0
Hi and thank you for the great work you've done. I've used it as a road map, but I realized a few problems near the end.
I have a pogo-v4-a3-01 I've read your work and also Qui's (7/2014 blog.qnology.com) and Jack i.t. (2014 pogoplug4.blogspot.com)
got your: linux-tools-installation-bodhi.tar.gz uboot.2016.05-tld-1.pogo_v4.bodhi.tar uboot.2016.05-tld-1.environment.bodhi.tar
-save initial mtd0 and inital env to current_env.txt
-as in #5, #6, #7 extracted erased and then wrote
-went to part "B" and did b. c. d. e.
but stopped before f.
my pogoplug v4 has no /boot directory, and I cannot locate any *.dtb file (1) do I need or need to make a /boot/dts/kirkwood-dockstar.dtb file?
(2) is my original stock kernel a non-FDT or FDT kernel boot? (3) is your newest debian kernel FDT (4) the arch kernel from 2014, or the latest, FDT?
(4) where is the ? file, or files, locations, that 'fw_printenv' lists the environment
(5) in section "C" uEnv.txt -do I need /boot/uEnv.txt ?
(6) my /etc/fw_env.config still only is just "/dev/mtd0 0xc0000 0x20000 0x20000" is this still needed? should it be something more or different by now?
(7) I'm still hoping to have an option to boot the original bootloader and run the cloudengine software. Would I simply follow QUI's directions? thanks in advance
↧
↧

Goflex Home bricked after installing Uboot (11 replies)

November 14, 2016, 5:32 pm
$
0
0
Thank you for your attention and please forgive my poor English.

I installed ArchLinux ARM on my goflex home, well, it ran well but it's slower and slower recently, so I wanted to go back to the stock firmware. I followed the instructions from doozan.com as the following wishing I could boot the stock firmware with this operation (maybe it worked previously? I don't remember that well):

cd /tmp
wget http://projects.doozan.com/uboot/install_uboot_mtd0.sh
chmod +x install_uboot_mtd0.sh
./install_uboot_mtd0.sh

However, on the last step, it stopped and warned me that the code of the Uboot doesn't meet with that of Goflex Home, so I used another way as this:

wget http://goflex.scottn.us/uboot-mtd0-orig-goflexhome.kwb
flash_erase /dev/mtd0 0 4
nandwrite /dev/mtd0 uboot-mtd0-orig-goflexhome.kwb

After that, it reported the nand was successfully flashed. Then I re-ran the ./install_uboot_mtd0.sh from doozan.com and it went through without any problem and reported information of success. So I typed reboot to reboot my Goflex Home, but it never booted again, nor registered any IP on my router. I tried to listen on 10.10.10.5 6666, as well as 10.10.10.2 and 10.10.10.4 with a Macbook, but got nothing at all.

I also created a USB disk with the latest rootfs (Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2), after plugged in the USB disk, the front light went off, but there was still no registration of the device on my router. I also put the uboot.2016.05-tld-1.environment as uEnv.txt into the boot folder, but got no luck either. After powered on, the front green light blinked quickly, followed by the amber light, and the USB disk is blinking, too, indicating some access is happening. After a while (one minute or so), all front light went off, the USB access stopped.

So, is there any chance for restoring my device back? It the JTAG or a serial cable the only way to save it? Thank you very much!

BTW, I have a LAN (RJ45) to COM cable, will that work as a serial cable?
↧

Zyxel NSA320 Debian HDD LEDs (3 replies)

November 20, 2016, 2:53 am
$
0
0
Hi,

after some struggling with the uboot upgrade, that works fine and debian is booting:-)

It's not absolutely importand, but nice to have: The HDD Leds... 

root@nsa320-debian:~# echo ide-disk2 >  /sys/class/leds/nsa320\:red\:hdd2/trigger 
root@nsa320-debian:~# echo ide-disk1 >  /sys/class/leds/nsa320\:red\:hdd1/trigger 
root@nsa320-debian:~# hdparm -tT /dev/sdb

Does not work... If I map heartbeat or default on or anything on the LED, the LED works, so the driver itself is up and running, but the trigger "ide-diskX" seems not to work...

has anyone an idea why?

Thanks s lot!

Cheers,

4920441
↧

GoFlexHome Maybe Bricked (5 replies)

November 21, 2016, 9:02 pm
$
0
0
So first thank you for these forums seems like a lot of good info and was enough to think I could follow along and migrate from Arch to Debian.

My setup had been to boot Arch off of the HD mounted on the GoFlexHome. But Debian seemed like a better choice so I dug out an old Arch bootable USB drive and went to work modifying the GoFlex rootfs on the hard drive.

First I followed http://forum.doozan.com/read.php?3,12381 it seemed rather straight forward other than having to install a few additional tools but everything went smoothly.

Next I followed the Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 install instructions.

After reboot everything seems to go normal from a link light and front light POV but the system does not grab an IP from the DHCP server on the router and so I have no way back into the GoFlex. But I have a green link light on the Ethernet port, and the front lights cycle from flashing green, to orange, to solid green.

Thinking maybe I'd messed up the rootfs install I made a bootable USB following the instructions here http://forum.doozan.com/read.php3,30890 Unfortunately it has the same light activity as with the hard drive.

I feel like I must be missing something obvious but I'm not sure what. I don't have a serial cable for this unit so I can't play that way.

Thanks for the help.

-MacKenzie
↧
↧

how to switch netconsole back to serial? (3 replies)

November 20, 2016, 3:57 pm
$
0
0
Hello, i have two nsa320's, that i both want to update to latest u-Boot.
The process went fine on one NSA, but on the other one i have some issues:
Right now there are no harddrives installed, but i could take the HD containing the rootfs from the other working NSA.
Unfortunately, all stdin, stout, stderr are set to nc,(which works fine). But i need to have it set to serial to be able to kwboot the latest u-boot. kwboot-updating worked fine on my other NSA(see my signature)
Below is my environment:
U-Boot 2015.10-tld-1 (Nov 06 2015 - 16:12:51 -0800)
ZyXEL NSA320 2-Bay Power Media Server
gcc (Debian 4.9.2-10) 4.9.2
GNU ld (GNU Binutils for Debian) 2.25
Hit any key to stop autoboot:  9
NSA320> print
print
arcNumber=3956
baudrate=115200
boot_sata1=mw 0x800000 0 1; setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10 $mtdparts; ide reset; ext2load ide 0:1 0x800000 /boot/uImage; ext2load ide 0:1 0x01100000 /boot/uInitrd; bootm 0x00800000 0x01100000
boot_sata2=mw 0x800000 0 1; setenv bootargs console=ttyS0,115200 root=/dev/sdb1 rootdelay=10 $mtdparts; ide reset; ext2load ide 1:1 0x800000 /boot/uImage; ext2load ide 1:1 0x01100000 /boot/uInitrd; bootm 0x00800000 0x01100000
bootcmd=run boot_sata1; run boot_sata2; run bootcmd_usb; usb stop; run bootcmd_rescue; reset
bootcmd_usb=run usb_init; run usb_load_uimage; run set_bootargs_usb; run usb_boot;
bootdelay=10
console=ttyS0,115200
ethact=egiga0
ethaddr=b0:b2:dc:ee:d4:f2
if_netconsole=ping $serverip
ipaddr=10.9.1.208
load_dtb=ext2load usb 0:1 0x1c00000 /boot/dts/kirkwood-nsa320.dtb
load_initrd=ext2load usb 0:1 0x1100000 /boot/uInitrd
load_uimage=ext2load usb 0:1 0x800000 /boot/uImage
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),512K(uboot_env),512K(key_store),512K(info),10M(etc),10M(kernel_1),48896K(rootfs1),10M(kernel_2),-(rootfs2)
nc_ready=1
ncip=10.9.1.200
netmask=255.255.255.0
partition=nand0,2
preboot=run preboot_nc
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi
serverip=10.9.1.200
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=nc
stdin=nc
stdout=nc
usb_boot=run load_dtb; run load_uimage; if run load_initrd; then bootm 0x800000 0x1100000 0x1c00000; else bootm 0x800000 - 0x1c00000; fi
usb_device=0:1
usb_init=usb start
usb_load_uimage=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage
usb_root=LABEL=USBROOT
usb_rootdelay=10
usb_rootfstype=ext2

Environment size: 2095/131068 bytes
NSA320>
From what i understand i pings my netcat server(10.9.1.200) up to five times, if it responds,it runs start_netconsole.
First i tried to switch the netconsole to serial like this:
 setenv start_netconsole'setenv ncip $serverip; setenv bootdelay 5;setenv stdin serial;setenv stdout serial;setenv stderr serial; version;'
but to no avail,when i executed this command, it just printed it(without error), but the environment stays unchanged.
Then i did:
NSA320> setenv serverip 10.9.1.201
setenv serverip 10.9.1.201
saveenv
Saving Environment to NAND...
Erasing NAND...
Erasing at 0xc0000 -- 100% complete.
Writing to NAND... OK
NSA320> reset
reset
Now it seems i've locked myself out, since nc doesnt come up(10.9.1.201 isnt pingable right now), and also the serial console doesnt react. The NSA is in a reboot loop.
Of course i could help myself by setting up my machine to the 10.9.1.201 address, but thats not the point.
What did i do wrong?
Whats the difference between serverip and ncip ?
Which other / better ways are there to set the stdin/-out/-err to serial?
should i maybe opt to install the new uboot from a working linux system?
↧

Pogoplug mobile (2 replies)

November 22, 2016, 2:34 pm
$
0
0
i bought two pogoplug mobiles a few years ago and apparently i activated ssh on one of them but i don't remember the pw. am i right to assume this bc ssh port 22 is open and i can send curl commands to port 443 but the ceadmin pw doesn't work?

will attaching a serial cable do anything for this issue or should i just scrap this one and move onto the other (port 22 closed on that one btw.)?

nmap logs attached.

thanks
↧

Enable SSH Access not found in the Settings page (Pogoplug V4-A1-01) (2 replies)

November 23, 2016, 4:57 am
$
0
0
Hi,

Just received my Pogo today and have successfully activated it. But in the settings page, I do not see the "Enable SSH Access" option.
Anyone knows why? Is there any other way to enable it? I tried to SSH and Telnet to it but I just get a "Connection Refused" error.

TIA
↧
Search

NSA325V2 u-boot installation - Problem with permission denied (3 replies)

November 29, 2016, 12:48 pm
$
0
0
Hello!

I'm trying to install the newest U-Boot 2016.05.

Part "A. Flashing Instruction:" doesn't work for me ("flash_erase /dev/mtd0 0 4" results in an error message). A little bit of googling got me to a page on this forum stating, that my NSA325v2 is using stock boot environment parameter and I've to update them by using the update procedure described in section "B. Flashing default u-boot envs image"

Nevertheless, this doesn't work either, "/usr/sbin/flash_erase /dev/mtd0 0xc0000 1" gives me 
root@debian:/media/test/envs# /usr/sbin/flash_erase /dev/mtd0 0xc0000 1
flash_erase: error!: /dev/mtd0
             error 13 (Permission denied)

Any suggestions?

Maybe the following information can help you in finding the problem? 

root@debian:/media/test/envs# uname -a
Linux debian 3.14.0-kirkwood-tld-1 #1 PREEMPT Tue Apr 1 22:54:58 PDT 2014 armv5tel GNU/Linux
root@debian:/media/test/envs# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00100000 00020000 "uboot"
mtd1: 00080000 00020000 "uboot_env"
mtd2: 00080000 00020000 "key_store"
mtd3: 00080000 00020000 "info"
mtd4: 00a00000 00020000 "etc"
mtd5: 00a00000 00020000 "kernel_1"
mtd6: 02fc0000 00020000 "rootfs1"
mtd7: 00a00000 00020000 "kernel_2"
mtd8: 02fc0000 00020000 "rootfs2"
root@debian:/media/test/envs# cat /proc/cmdline
console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) root=LABEL=rootfs loglevel=8
root@debian:/media/test/envs# dmesg | grep nand
[    0.000000] Kernel command line: console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) root=LABEL=rootfs loglevel=8
[   20.299750] nand: device found, Manufacturer ID: 0x92, Chip ID: 0xf1
[   20.306133] nand: Eon NAND 128MiB 3,3V 8-bit
[   20.310436] nand: 128MiB, SLC, page size: 2048, OOB size: 64
[   20.390829] Creating 9 MTD partitions on "orion_nand":
↧
↧

Getting error trying to install uboot on pogoplug V4 - already flash erased..help (14 replies)

November 30, 2016, 12:57 am
$
0
0
Hello!

I initially had a pogoplug that I had used the Qnology guide to install uboot about a year and a half ago, it worked great. Unfortunately, the pogo had an accident so I bought a new one (Pogoplug Mobile V4-A1-01). After trying to get SSH access and realizing I couldn't anymore, I bought a USB->TTL converter and wired it up and PuTTYed into it. Unfortunately, quickly into the process I realized Qnology's download links are no longer valid so I went ahead and started using the guide that is pinned at top of this page. Unfortunately it is not working and I think it may be related to it being a fresh flash? I'm not sure exactly what is going on but I keep getting an error. Namely: 

/tmp # tar -xf uboot.2016.05-tld-1.pogo_v4.bod
tar: invalid tar magic

Just some background, I'm completely Linux-tarded and terminal-tarded and kept noodling around with it, unzipped in windows then somehow managed to WGET the untarred file over to the TMP folder (at least, I thought I did). 

/tmp # /tmp/flash_erase /dev/mtd0 0 4
Erase Total 4 Units
Performing Flash Erase of length 131072 at offset 0x60000 done
/tmp # /tmp/nandwrite /dev/mtd0 /tmp/uboot.2016.05-tld-1.pogo_v4.mtd0.kwb
Input file is not page-aligned. Use the padding option.
Data was only partially written due to error
: Success

Now getting the above error. I'm not sure exactly what I did wrong. I do think what happened was I was unsuccessful in getting the proper file over to the Pogo but I have no clue how to do it with terminal. I can't figure out how to WGET from my windows based computer, dropbox, or any of the other solutions I've tried (e.g. my router based NAS, any of the web based mirrors I've found.)

That's where I'm at and now I'm afraid to close the COM session or reboot my Pogo since I flash erased the POGO at this point. Hopefully my power doesn't go out or something. If anyone can help me or point me in the direction I need to go, it would be greatly appreciated. I tried reading over the directions in the pinned folder as carefully as possible but again, I'm linux-tarded and I don't think I did it right (I even had to google how to delete stuff in the linux terminal).
↧

After update to u-boot 2016.05-tld-1 on NSA325v1 is not booting (1 reply)

November 29, 2016, 1:03 pm
$
0
0
Hi there,

I've been reading here for a long time and I dared yesterday to change the u-boot from 1.1.4 on one of my two NSA325v1. So I used a serial connection to my Mac and updated the u-boot as described in this article: http://forum.doozan.com/read.php?3,12381 With nandwrite the expected output was right: 
Writing data to block 0 at offset 0x0 
Writing data to block 1 at offset 0x20000 
Writing data to block 2 at offset 0x40000 
Writing data to block 3 at offset 0x60000
But now I'm in trouble at step B, after a reboot the system shows the following: 
U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:48:40 -0700)
ZyXEL NSA325 2-Bay Power Media Server

SoC:   Kirkwood 88F6282_A1
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
MV88E1318 PHY initialized on egiga0
Hit any key to stop autoboot:  0
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found

Partition Map for USB device 0  --   Partition Type: EFI

Part    Start LBA       End LBA         Name
        Attributes
        Type GUID
        Partition GUID
  1     0x00000022      0x0079b15e      "Microsoft basic data"
        attrs:  0x0000000000000000
        type:   ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
        guid:   c1d82d0b-dafe-47ba-a20a-7c116fb4c695
loading envs from usb 0 ...
reading /boot/uEnv.txt
** Unable to read file /boot/uEnv.txt **
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
Wrong Image Format for bootm command
Error occured, error code = 112
ERROR: can't get kernel image!
stopping USB..

Reset IDE: Bus 0: OK Bus 1: OK
  Device 0: Model: WDC WD10EADS-11M2B2  Firm: 80.00A80 Ser#:  WD-WCAV5D830190
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512)
  Device 1: Model: Hitachi HDS721010CLA332  Firm: JP4OA3EA Ser#: JP2911HD188TZC
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512)
** File not found /boot/uImage **
** File not found /boot/uInitrd **
Wrong Image Format for bootm command
Error occured, error code = 112
ERROR: can't get kernel image!
resetting ...
So - what where my configs (with the old u-boot from marvel):
cat /etc/fw_env.config 
 
# Configuration file for fw_(printenv/saveenv) utility.
# Up to two entries are valid, in this case the redundand
# environment sector is assumed present.
# Notice, that the "Number of sectors" is ignored on NOR.

# MTD device name       Device offset   Env. size       Flash sector size       Number of sectors
# NAND example
/dev/mtd1		0x0000		0x20000		0x20000			4
cat /proc/mtd 
 
dev:    size   erasesize  name
mtd0: 00100000 00020000 "uboot"
mtd1: 00080000 00020000 "uboot_env"
mtd2: 00080000 00020000 "key_store"
mtd3: 00080000 00020000 "info"
mtd4: 00a00000 00020000 "etc"
mtd5: 00a00000 00020000 "kernel_1"
mtd6: 02fc0000 00020000 "rootfs1"
mtd7: 00a00000 00020000 "kernel_2"
mtd8: 02fc0000 00020000 "rootfs2"
I'm not shure how I'm flashing now the default u-boot envs into the image. Which are these envs? Which files must located where? Or I'm totally wrong? So it would be great if someone could help me and lead me to the right way ;-)

Kind regards, machnetz
↧

Pogoplug - uBoot Debian vs Stock (8 replies)

December 6, 2016, 9:55 pm
$
0
0
Hi, When I got my pogoplug I installed uBoot on my pogoplug to run debian because I thought I had to; now I reallize this might have been a mistake. Pogoplug seems to run a weird proprietary version of linux, is this right? Can I run regular commands like move, copy, link, etc? It is also essential that I can set up some form of Wake-on-LAN/WAN, so I need to be able to install the required modules and be able to enter hibernate/sleep/standby. Can this be done in stock pogoplug, or is Debian required to do this kind of thing?
↧

variable for booting from sdcard on pogoplug mobile/v4 (2 replies)

December 6, 2016, 10:14 pm
$
0
0
I was having trouble getting one of my plugs to boot from the mmc card - just getting an error. after carefully reviewing the env.config I noticed that the bootcmd_mmc variable is missing in the file, so it just overpasses it with an error.


I have the bootcmd variable set as follows; 
bootcmd=run bootcmd_usb; run bootcmd_mmc; run bootcmd_sata; run net_bootcmd; run bootcmd_pogo; reset

so...bootcmd_mmc= ?

The only example I could find here in the forums was here http://forum.doozan.com/read.php?2,28798,28798#msg-28798 

mmc_boot=mw 0x800000 0 1; run mmc_load_uimage; if run mmc_load_uinitrd; then boo tm 0x800000 0x1100000; else bootm 0x800000; fi 
mmc_init=mmc rescan 
mmc_load_uimage=ext2load mmc $device 0x800000 /boot/uImage 
mmc_load_uinitrd=ext2load mmc $device 0x1100000 /boot/uInitrd 
mmc_root=/dev/mmcblk0p1

If my sdcard has debian installed on ext3 and it is labelled rootfs and is device 1 , would the above code I copied be= 

mmc_boot=mw 0x800000 0 1; run mmc_load_uimage; if run mmc_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi 
mmc_init=mmc rescan 
mmc_load_uimage=ext3load mmc $device 0x800000 /boot/uImage 
mmc_load_uinitrd=ext3load mmc $device 0x1100000 /boot/uInitrd 
mmc_root=/dev/rootfs

I know I can always trial and error it but I'm trying to understand (and finally starting to get it a little) exactly how the script/code itself within the env.config file works as well.

Thanks!
↧
↧

2016.05 U-Boot Kirkwood - Can't set ethaddr (5 replies)

December 7, 2016, 9:48 pm
$
0
0
Hi,
I can't change my ethernet address using

root@debian:/share# fw_setenv ethaddr "XX:XX:XX:XX:XX:XX"
Can't overwrite "ethaddr"

I tried even after reboot
↧

How to use usbboot? soft-bricked v4 pogoplug (2 replies)

December 15, 2016, 4:41 am
$
0
0
Hello all.

I tried to install the lastest version of uboot and switch over to sd card booting on my pogoplug, but I messed up somewhere and it doesnt boot on its own. There are no lights by default, but I can make it boot using kwboot.

My trouble now is once I am controlling it via serial, how do I tell it to try to boot from the rootfs usb stick that I just made?

Ideally I would like to get archlinuxarm on it, and I am happy to restore it to stock before continuing. Currently I have a rootfs usb stick that I made while following this post:
http://forum.doozan.com/read.php?2,12096

I tried usbboot, but I just get "no device specified". Also, usbboot /dev/sda1 and usbboot USB0 did not work either (these were done after I issued the command usb start)

Attached are my printenv along with my usb start output in case it helps.

Thank you. 


Pogov4> printenv
baudrate=115200
bootcmd=run boot_nand
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootcmd_usb=run usb_init; run set_bootargs_usb; run usb_boot;
bootdelay=10
console=ttyS0,115200
device=0:1
ethact=egiga0
ethaddr=b6:d0:5e:0f:a1:17
led_error=orange blinking
led_exit=green off
led_init=green blinking
machid=f78
mainlineLinux=no
mtddevname=uImage2
mtddevnum=2
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
partition=nand0,2
rootdelay=10
rootfstype=ext2
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
stderr=serial
stdin=serial
stdout=serial
uenv_import=echo importing envs ...; env import -t 0x810000
uenv_load=usb start; mmc rescan; ide reset; setenv uenv_loaded 0; for devtype in usb mmc ide; do for disknum in 0; do run uenv_read_disk; done; done
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 0x810000 /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
usb_boot=mw 0x800000 0 1; run usb_load_uimage; if run usb_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_init=usb start
usb_load_uimage=ext2load usb $device 0x800000 /boot/uImage
usb_load_uinitrd=ext2load usb $device 0x1100000 /boot/uInitrd
usb_root=/dev/sda1

Environment size: 1564/131068 bytes



Pogov4> usb start
starting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found

------
mod edit: use code tags
↧
Search

http://validdumps.net/shop dumps,dumps with pin,shop dumps online (no replies)

January 3, 2017, 7:50 am
$
0
0
http://validdumps.net/ Dumps shop,dumps with pin track1&2,sell dumps online. valid.....!!!!!
Selling dumps - dumps shop - dumps with pin - sell dumps


- Gmail : maryabbate128@gmail.com

- Skype : maryabbate128

- My shop: http://validdumps.net/

Shop dumps, dumps with pin + track 1&2 : http://validdumps.net/
http://validdumps.net/ Selling dumps, sell dumps, dumps shop, fresh dumps, dumps sale
http://validdumps.net/ update dumps good daily . price cheap rate work 95%
http://validdumps.net/ if order payment westernu union and money gram Min 100$
http://validdumps.net/ have Good Base and vaild rate 95% bulk dumps with Pin and code 101,110,201,210,220 and more Country
http://validdumps.net/ dumps shop, good dumps,shop dumps,dumps valid,dumps with pin,


Prices:
FOR USA DUMPS:
CLASSIC/STANDARD:$50
GOLD/PLAT:$50
SIGN/CORP/BIZ/WORLD/PURCH:$50
DISCO:$40



EU
classic/standart -70$
discover/amex -70$
gold/business/platinum -70$
corporate/signature/world -70$
Infinite -70$



Prices:
FOR CA DUMPS:
CLASSIC/STANDARD:$50
GOLD/PLAT:$50
SIGN/CORP/BIZ/WORLD/PURCH:50$
AMEX/DISCO:$50 >>>>:BULK BUYER CONTACT ON ICQ WE HAVE GOOD OFFER FOR BULK BUYER AND RESELLER



We sell USA AND CANADA tr2, tr1+tr2, tr2+name DUMPS
ATTENTION GUYS !CANADA REPLACEMNT TIME IS BEFORE 12HOURS !USA REPLACEMNT TIME BEFORE 24HOURS!


Peculiarities of our service:


===========================
>High-percent valid.
>Weekly update.
>We're not resellers of somebody else's dumps - that's why all articles sold to you will stay only with you.
Payment and Guarantees:
==========================


>MoneyGram WU MINUMUM 100$
>WMZ,BITCOINS no minumum
>Instant Delivery with WMZ,BTC
Substitution and replacements:
===============================


>We NEVER make REFUND, ONLY REPLACE!
>No replacements for Region Lock DUMPS.
>We only replace hold/stolen/decline dumps.
Our rules
======================


-We do not check the dumps
-We do not guarantee limits and amounts on Dumps
-No Test / No Free / No Sample Dumps
-REGION BLOCK NEVER WILL BE REPLACED, so choose your bin carefully
======================


ATM SKIMMERS PRICE LIST


Wincor Nixdorf : 1200 $


Wincor : 1000 $


Slimm : 1000 $


NCR : 1000 $


NCR With Wireles 1200 $


Diebold Opteva : 1000 $


Diebold : 1000 $


Universal : 1500 $


Small : 1000 $


Chip POS ingenico&amigo : 600 $


======================


Sell cvv random ..cvv with dob ..us ssn .. fullz info . . good balance - 100% live


i don't sell 1 .. all cvv have been check live b4 send


us 40$ for 10 ccs


uk 40$ for 5 ccs


ca 40$ for 5 ccs


Eu 60$ for 5 ccs


and more country . contact to know

Skype : maryabbate128

Shop dumps online : http://validdumps.net

http://www.youtube.com/watch?v=-ZHatZlPwWg
↧

Help with Pogoplug v4 – blinks green for ten seconds and reboots in a loop (11 replies)

September 9, 2016, 5:39 pm
$
0
0
Bodhi and everyone else here: you've done some amazing work. I wanted to honor that and not end up needing help but...

I started to flash my Pogoplug v4-A3-01 years ago with some tutorial but abandoned the project. I started it again recently and found that I could boot into Arch with root:root. I tried picking up Qui Hong's tutorial but his links are down, so I tried a combination of that and Bodhi's 2016.05 tutorial. When I rebooted (the "cross your fingers" part), it no longer boots into the USB drive I was using or the SD card, which I formatted in the tutorial (with both or either inserted). I removed the power cord to power cycle and the status light immediately blinks/flashes green for about ten seconds then goes dark for a second or two and begins the cycle again. (I assume that it's restarting during that pause.) Just as it goes dark, the ethernet jack briefly lights both orange and green. I formatted another SD card with the Debian-4.4 in case it was a file system issue and had the same result (also that wouldn't explain why the unmodified USB drive used for the original flash no longer registers). When I formatted this SD card, it was formerly FAT 32 and while its partition is ext3, the `pttype="dos"` instead of "gpt" when I run blkid—not sure if that's an issue. The device doesn't go solid green so I can't SSH and netconnect is not installed. Would you know whether this is a bad flash or what I might need to do to restart and try over?

Appreciate your help. I'd be willing to rewrite the Qui tutorial with your updated materials so that future installs can go more smoothly. I still have another Pogoplug Mobile I'd like to try, but hopefully I can get this v4 up if it isn't bricked.
↧
↧

How to flash new uboot from boot console (5 replies)

January 15, 2017, 5:20 am
$
0
0
@bodhi,
I saw somewhere a post that flashing uboot and/or uboot env is also possible in the boot console (stop bootup at the beginning) using files from a connected usb stick. I have Goflex Net device where rootfs in flash is partly bricked. The original uboot is still on this device. Can you please tell me how to flash new uboot and uboot env with the boot console. This device does not support serial booting. Is there any other posibility?

Regards.
shv
↧

BUG report: Net console for 2015.10 U-Boot for Pogoplug V3 (OXNAS OX820) not working (13 replies)

January 17, 2017, 8:53 pm
$
0
0
Followed this thread http://forum.doozan.com/read.php?3,16017 to update my pogoplug pro's uboot.

The Uboot I used for my pogoplug Pro: uboot.2015.10-tld-1.ox820.bodhi.tar

Followed the flashing Instruction from 1 to 16 (just changed IP in step 12) on two Pogoplug-Pro, both can boot into debian rootfs usb fine.both had no net console output. It seems there's something broken in uboot. The preboot did not execute?

If I put "run preboot" or something like that to the bootcmd line

bootcmd=run preboot; run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; reset


I can get some output from net console, but no use. I can't stop the booting procedure in this way.

Net console is not supposed to work this way...

However, I have serial cable and serial worked fine for the uboot.


serverip / router etc has no problem. I can get the nc output infomation from my kirkwood boxes in the same machine, also, if I changed uboot / enviroment for pogoplug pro to an old version (uboot.2013.10-tld-4.ox820.bodhi.tar --this file is pretty difficult to find now.) with this instruction http://blog.qnology.com/2015/04/hacking-pogoplug-v3oxnas-proclassic.html, the net console worked.

Thank you guys for your time.
↧

PogoPlug P21/v3 Unable to Boot after U-Boot Update (2 replies)

January 17, 2017, 9:14 pm
$
0
0
Hey folks,

New to the forums here, so forgive my ignorance with what I'm doing with my PogoPlug.

Long story short, I've got a box that has the 2013.10-tld-4 U-Boot installed (seems I upgraded it properly at the time), but I believe due to a number of factors that went wrong with everything thereafter (U-Boot envs, amongst others), I can't get the thing to boot.

Initially, I'd extracted a Debian rootfs tar to a flash drive and I'd left this thing on for days with it rebooting itself. The box would start with a solid green light, then flashing green, then solid, then flashing amber and reboot. I've been able to get the box to at least load the kernel on the drive (on it's own now), but it's not going any further.

I'm using a cheapo BTE13-009 (CH340G clone) USB to TTL converter and it's receiving output from the PP just fine, but I'm unable to transmit (using PuTTy, all settings right that I can tell) so it won't accept any keyboard entry. Drivers are the latest I can find for the board, and the board itself has a blue LED that shows when it's transmitting to the PP, but no response from it (for example, when autoboot runs, I can't interrupt).

I've checked all my connections, and I've rebooted the box multiple times, and the output is the same every time as per what's below. Any guidance available would be most appreciated.

Also, I have Windows 7, Windows 10, and Linux Mint to work with for OSes (and possibly more linux flavors via VM).

Quote
U-Boot SPL 2013.10-tld-4 (Sep 07 2014 - 14:10:12)
Boot device: NAND
Attempting to set PLLA to 850 MHz ...
plla_ctrl0 : 0000020a
plla_ctrl1 : 00330000
plla_ctrl2 : 0065008b
plla_ctrl3 : 000000f1

PLLA Set


U-Boot 2013.10-tld-4 (Sep 08 2014 - 19:43:38) for OXNAS

DRAM: 128 MiB
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net:
Led: GREEN
mii0
Main Loop
Hit any key to stop autoboot: 0
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 4 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
4102704 bytes read in 354 ms (11.1 MiB/s)
1953812 bytes read in 253 ms (7.4 MiB/s)
7029 bytes read in 205 ms (33.2 KiB/s)
## Booting kernel from Legacy Image at 60500000 ...
Image Name: Linux-3.17.0-oxnas-tld-1
Created: 2014-11-01 7:16:44 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4102640 Bytes = 3.9 MiB
Load Address: 60008000
Entry Point: 60008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 60e00000 ...
Image Name: initramfs-3.17.0-oxnas-tld-1
Created: 2014-11-01 7:18:53 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 1953748 Bytes = 1.9 MiB
Load Address: 60000000
Entry Point: 60000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 62c00000
Booting using the fdt blob at 0x62c00000
Loading Kernel Image ... OK
Loading Ramdisk to 67c4b000, end 67e27fd4 ... OK
Loading Device Tree to 67c46000, end 67c4ab74 ... OK

Led: GREEN

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
↧
Viewing all 902 articles
Browse latest View live
Search