Quantcast
Channel: Linux Device Hacking - uBoot
Viewing all 902 articles
Browse latest View live

Still having trouble with a new uboot install (9 replies)

$
0
0
Following a prior difficulty and reflashing back to factory, I have managed to mess up my GoFlex Home again. This is the sequence of events:

  1. Mess up the gfh while installing uboot.
  2. booted from usb with a debian image
  3. tried to redo the uboot install, but failed
  4. reflashed to factory (2.7.1)
  5. successfully replaced sshd so that I could ssh in without the long username.
  6. installed uboot via the install_uboot_mtd0.sh script without error other than: cannot overwrite ethaddr
  7. set up netconsole via fw_setenv
  8. set arcnumber via fw_setenv
  9. restart failed to connect to network and no netconsole or ssh access
    flashing green then flashing orange
  10. failed to boot from usb
    flashing green led then no leds at all
  11. failed to reflash back to factory
  12. flashing green led, then usb led flashed twice, followed by orange flashing led,never got the white flash
    tried 2.7.1 and 2.5.3

Any ideas? I do not yet have a serial cable. I ordered one about a week ago, but it is not here yet.

Below is the output from fw_printenv (I saved it before rebooting):
Is there something wrong with the uboot environment? or is there some way that I can connect to it?
I have not installed recovery

baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
netmask=255.255.0.0
run_diag=yes
stdin=serial
stdout=serial
stderr=serial
console=console=ttyS0,115200
mainlineLinux=no
CASset=min
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
MALLOC_len=1
ethprime=egiga0
netbsd_en=no
vxworks_en=no
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
bootdelay=3
disaMvPnp=no
ethaddr=00:50:43:b4:1a:2e
ethmtu=1500
usb0Mode=host
nandEcc=1bit
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
enaAutoRecovery=yes
pcieTune=no
ethact=egiga0
filesize=33AA2E
bootargs=console=ttyS0,115200 root=/dev/ram0 rw ramdisk=0x01100000,8M install_type=nand
bootargs_root=ubi.mtd=2,2048 root=ubi0:rootfs rootfstype=ubifs init=/linuxrc
console2=console=ttyS0,115200
bootcmd=nand read.e 0x800000 0x100000 0x600000; setenv bootargs $(console2) $(bootargs_root); bootm 0x800000
arcNumber=3089
serverip=192.168.0.89
ipaddr=192.168.0.94
if_netconsole=ping $serverip
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
preboot=run if_netconsole start_netconsole

Does any version of uboot support EFI and GPT? (19 replies)

$
0
0
I ask because I have a 3TB GoFlex home. I would like to install linux directly on the drive and boot from it. I am looking for the best solution to this.

I am aware that there is a solution that uses a hybrid MBR/GPT. That isn't ideal, but will be sufficient if I can't do it more directly.

I believe that the best solution would be to use a uboot and kernel that support EFI and GPT.

Ultimately I want to know what I need to do to be able to boot from and use the entire 3TB.

Any help?

Thanks

interchange SD cards between 2 pogopiugs (2 replies)

$
0
0
Hi Jeff.

First, thanks for all of this, from all of us.

I have installed uboot on a second pogoplug (the first was ping and the second black, but identical memory and debian linux) The pink one has an IP of 192.168.0.4 and the black is at 192.168.0.3.

The pink one boots off of an 8GB SD and the black off a 16GB SD. Both run debian just fine (thanks again). I'd like to clone the system from the pink to the black, but am haviong problems. My initial attempts were to verify that the SD cards were intercahngablle between machines.

Since I assumed that the only difference between the two was on the SD card, I put the pink SD card into the black plug. But it won't boot. It never registers with the router even on repeated attempts.

Since I can't use the SD card from one pogo to boot the other, is there a way to set up one pogoplug and then easily clone it to other plugs? I know I'd have to change the IP address and maybe the device name, but that should be simple. What am I missing here.

unsupported machine ID 0x00000bb6 (=2998) (2 replies)

$
0
0
Hi,

I tried to create a wheezy USB stick on my 'old' squeeze dockstar. Now I can only boot into pogo - w/o really knowing why.

1) started the wheezy installation which updated the uboot
2) failed to create wheezy with Kernel to old message
3) found that neither internal debian squeeze nor usb squeeze boots any longer - both fail with unsupported machine id error
4) interrupted boot, printenv shows "arcNumber=2097"
5) tried to install improved rescue system from pogo - which refuses to update the boot partition, reasonable

6) tried to install rescue system on second dockstar - as the upgrade of uboot happend, too, its not stuck, too .-)

7) tried to install squeeze again thinking that it might install an older uboot - which it didn't :-)

So now I'm stuck w/o good ideas how to recover the boxes and continue. I can only boot into pogo at this point in time - serial cable is available.

Help is really appreciated.
Fritz!


unrecognized/unsupported machine ID (r1 = 0x00000bb6).

Available machine support:

ID (hex)        NAME
00000690        Marvell DB-88F6281-BP Development Board
00000691        Marvell RD-88F6192-NAS Development Board
00000692        Marvell RD-88F6281 Reference Board
0000078c        Marvell 88F6281 GTW GE Board
00000a76        Marvell eSATA SheevaPlug Reference Board
00000831        Marvell SheevaPlug Reference Board
00000a63        Marvell GuruPlug Reference Board
0000085b        QNAP TS-119/TS-219
000009c6        QNAP TS-41x
00000b44        Marvell OpenRD Ultimate Board
00000939        Marvell OpenRD Client Board
00000915        Marvell OpenRD Base Board
00000b1e        HP t5325 Thin Client

Please check your kernel config and/or bootloader.


fw_printenv                                                                                                                                                                   
ethact=egiga0
bootdelay=3
baudrate=115200
mainlineLinux=yes
console=ttyS0,115200
led_init=green blinking
led_exit=green off
led_error=orange blinking
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
mtdids=nand0=orion_nand
partition=nand0,2
stdin=serial
stdout=serial
stderr=serial
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_list=1 2 3 4
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_init=run usb_scan
usb_device=0:1
usb_root=/dev/sda1
usb_rootfstype=ext2
usb_rootdelay=10
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
ethaddr=00:10:75:1A:5A:76
arcNumber=2097

Goflex Satellite (no replies)

$
0
0
Has anyone worked with the goflex satellite? Runs on an OMAP with u-boot running Arago project as a base.

Processor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 298.32
Features : swp half thumb fastmult vfp edsp neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x3
CPU part : 0xc08
CPU revision : 2

Hardware : OMAP3 EVM
Revision : 0020
Serial : 0000000000000000

Trashed uboot environment vars (2 replies)

$
0
0
Hi guys,

I've just managed to delete all of my uboot environment variables with a careless reboot. I still have uboot installed, but I cannot natively boot from ANYTHING. I just get dumped to a command line. Anyone know how I can reset my variables long enough to boot something and reset them permanently?

Thanks,

Verification Failed during uboot installation (1 reply)

$
0
0
Hi,

I bought an Pogoplug a week ago. While using the manual from http://projects.doozan.com/uboot/ I got the Error: (after typing "./installing_uboot_mtd0.sh"):

# checking for /usr/sbin/nandwrite...
# checking for /usr/sbin/nanddump...
# checking for /usr/sbin/flash_erase...
# checking for /usr/sbin/fw_printenv...
# checking for /etc/fw_env.config...

# Validating existing uBoot...
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
Connecting to jeff.doozan.com (50.116.34.13:80)
valid-uboot.md5      100% |*******************************|  1133  --:--:-- ETA
## Unknown uBoot detected on mtd0: 6c14964b11a51894f55f63081b79e53b
##
## The installer could not detect the version of your current uBoot
## This may happen if you have installed a different uBoot on
## /dev/mtd0 or if you have bad blocks on /dev/mtd0
##
## If you have bad blocks on mtd0, you should not try to install uBoot.
##
## Installation cancelled.

then I read a little bit in this forum and tested this command: "./installing_uboot_mtd0.sh --no-uboot-check". No he begins to install the bootloader, but he ends with this Error Message:

# Installing uBoot
## Installing pinkpogo davygravy-2012-02-20
Connecting to download.doozan.com (50.116.34.13:80)
uboot.mtd0.kwb.md5   100% |*******************************|    32  --:--:-- ETA
Connecting to download.doozan.com (50.116.34.13:80)
uboot.mtd0.kwb       100% |*******************************|   512k 00:00:00 ETA
Erase Total 4 Units
Performing Flash Erase of length 131072 at offset 0x0
MTD Erase failure: Input/output error
Writing data to block 0 at offset 0x0
Bad block at 0, 1 block(s) from 0 will be skipped
Writing data to block 1 at offset 0x20000
Writing data to block 2 at offset 0x40000
Writing data to block 3 at offset 0x60000
Writing data to block 4 at offset 0x80000
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
## Verifying new uBoot...
Connecting to download.doozan.com (50.116.34.13:80)
uboot.mtd0.kwb.md5   100% |*******************************|    32  --:--:-- ETA
##
##
## VERIFICATION FAILED!
##
## uBoot was not properly installed to mtd0.
##
##
## YOUR DEVICE MAY BE IN AN UNUSABLE STATE.
## DO NOT REBOOT OR POWER OFF YOUR DEVICE
##
##
## Make a backup of /tmp/uboot-mtd0-dump someplace safe and
## then re-run this installer.

And here I am. My Linux knowledge is unfortunately very low. I do not know how to go on. Is there anyone who has ever had this problem and can help me?

Serial cable difficulties with Pogoplug V3 oxnas (no replies)

$
0
0
What is the cause and cure for gibberish over the serial connection?
Pogoplug V3 Basic oxnas no Uboot or kernel changes from the original.

TJ

Problems with POGO-E02 (Black) (25 replies)

$
0
0
Hi there,

I have an POGO-E02 (Black) and wanted to install ArchLinux on it. Hardware-Infos to the device:

Pogoplug:/tmp$ cat /proc/cpuinfo
Processor       : ARM926EJ-S rev 1 (v5l)
BogoMIPS        : 1192.75
Features        : swp half thumb fastmult edsp
CPU implementer : 0x56
CPU architecture: 5TE
CPU variant     : 0x2
CPU part        : 0x131
CPU revision    : 1
Cache type      : write-back
Cache clean     : cp15 c7 ops
Cache lockdown  : format C
Cache format    : Harvard
I size          : 16384
I assoc         : 4
I line length   : 32
I sets          : 128
D size          : 16384
D assoc         : 4
D line length   : 32
D sets          : 128

Hardware        : Feroceon-KW
Revision        : 0000
Serial          : 0000000000000000


Pogoplug:/tmp$ cat /proc/meminfo
MemTotal:       256008 kB
MemFree:        240992 kB
Buffers:            32 kB
Cached:           4304 kB
SwapCached:          0 kB
Active:           2960 kB
Inactive:         2280 kB
SwapTotal:           0 kB
SwapFree:            0 kB
Dirty:               0 kB
Writeback:           0 kB
AnonPages:         932 kB
Mapped:           1576 kB
Slab:             8576 kB
SReclaimable:      316 kB
SUnreclaim:       8260 kB
PageTables:         96 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:    128004 kB
Committed_AS:     3560 kB
VmallocTotal:   385024 kB
VmallocUsed:       324 kB
VmallocChunk:   384696 kB

"uName" gives the following result (when now booting without usb-device) :
Pogoplug:~$ uname -a
Linux Pogoplug 2.6.22.18 #81 Tue Oct 19 16:05:00 PDT 2010 armv5tejl unknown

I used the instructions on the ArchLinux pages (http://archlinuxarm.org/platforms/armv5/pogoplug-v2-pinkgray) what included the installation of "uBoot". Although there was no error-message in the complete installation-process (uBoot & ArchLinux) the POGO-E02 (Black) does not come up. So I wondered if uBoot was installed properly and tried to install again :

Pogoplug:/tmp$ wget http://jeff.doozan.com/debian/uboot/install_uboot_mtd0.sh
Connecting to jeff.doozan.com (50.116.34.13:80)
install_uboot_mtd0.s 100% |*******************************| 18406  --:--:-- ETA
Pogoplug:/tmp$ chmod +x install_uboot_mtd0.sh
Pogoplug:/tmp$ ./install_uboot_mtd0.sh


!!!!!!  DANGER DANGER DANGER DANGER DANGER DANGER  !!!!!!

If you lose power to your device while running this script,
it could be left in an unusable state.

This script will replace the bootloader on /dev/mtd0.

This installer will only work on the following devices:
 Seagate Dockstar
 Seagate GoFlex Net
 Seagate GoFlex Home
 Pogoplug v1
 Pogoplug Pink (v2)
Do not run this installer on any other device.

By typing ok, you agree to assume all liabilities and risks
associated with running this installer.

If you agree, type 'ok' and press ENTER to continue: ok
# checking for /usr/sbin/nandwrite...
# checking for /usr/sbin/nanddump...
# checking for /usr/sbin/flash_erase...
# checking for /usr/sbin/fw_printenv...
# checking for /etc/fw_env.config...

# Validating existing uBoot...
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
Connecting to jeff.doozan.com (50.116.34.13:80)
valid-uboot.md5      100% |*******************************|  1133  --:--:-- ETA
## Valid uBoot detected: [pinkpogo davygravy-2012-02-20-current]
## The newest uBoot is already installed on mtd0.


You are already running the latest uBoot.
Your current uBoot environment should be reasonable.  However, if you're having
any probems booting, you can reset the environment variables to know good values.
Would you like to reset the uBoot environment? [N/y] y

# Installing uBoot environment
Connecting to download.doozan.com (50.116.34.13:80)
uboot.environment.md 100% |*******************************|    32  --:--:-- ETA
Connecting to download.doozan.com (50.116.34.13:80)
uboot.environment    100% |*******************************|   128k 00:00:00 ETA
Erase Total 1 Units
Performing Flash Erase of length 131072 at offset 0xc0000 done
Writing data to block 6 at offset 0xc0000

# Verifying uBoot environment
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x000c0000 and ending at 0x000e0000...
Connecting to download.doozan.com (50.116.34.13:80)
uboot.environment.md 100% |*******************************|    32  --:--:-- ETA

# uBoot installation has completed successfully.

When I start the Pogo-E02 (with plugged in USB-device with installed ArchLinux) the LED stays off, the LED is working for some seconds, then the LED turns orange and nothing else happens (the device is not shown in the router, so it can't received a new, deiffrent IP).

My questions :
- Did I pick the wrong uBoot ?
- Do you see an errors/mistakes in uBoot ?

Thanx 4 help.


Edit: The command "/usr/sbin/fw_printenv" says:
Pogoplug:/$ /usr/sbin/fw_printenv
ethact=egiga0
bootdelay=3
baudrate=115200
mainlineLinux=yes
console=ttyS0,115200
led_init=green blinking
led_exit=green off
led_error=orange blinking
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
mtdids=nand0=orion_nand
partition=nand0,2
stdin=serial
stdout=serial
stderr=serial
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_list=1 2 3 4
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_init=run usb_scan
usb_device=0:1
usb_root=/dev/sda1
usb_rootfstype=ext2
usb_rootdelay=10
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
ethaddr=00:00:00:00:00:00 -----> CHANGED ONLY FOR THIS FORUM-POST !
arcNumber=2097

GRUB on U-Boot! (no replies)

$
0
0
Seems Linaro has been busy!

They have implemented "GRUB on U-Boot" support:

https://wiki.linaro.org/LEG/Engineering/Kernel/GRUB

This could be very handy for embedded devices, and could help to eliminate the work involved in creating fancy boot scripts like Jeff made for Kirkwood and I made for the A10.

Look forward to seeing posts on how well it works. . .

Who has had success with 3TB GFH? [Solved] (2 replies)

$
0
0
I have solved my problems below. The short answer is that I was not using an appropriate kernel. I updated and now all is well. My setup is described below:

my uboot:
http://download.doozan.com/uboot/files/uboot/uboot.mtd0.goflexhome.davygravy-2012-04-19.kwb

my kernel:
Linux-3.3.2-kirkwide from the rescue image

my partitions:
Recovery/transformation command (? for help): p
Disk /dev/sda: 5860533168 sectors, 2.7 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): E6D0FDC0-0A69-47A9-B3DF-672B315FAB76
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 5860533134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048        33556479   16.0 GiB    8300  Linux filesystem
   2        33556480      5860533134   2.7 TiB     8300  Linux filesystem

Recovery/transformation command (? for help): o

Disk size is 5860533168 sectors (2.7 TiB)
MBR disk identifier: 0x00000000
MBR partitions:

Number  Boot  Start Sector   End Sector   Status      Code
   1      *           2048     33556479   primary     0x83
   4                     1         2047   primary     0xEE

my filesystems:
ext3 for /dev/sda1 (boot/root)
ext4 for /dev/sda2 (media storage)

Original post below:
___________________________________________________________________________________

I am having some trouble with my 3TB GFH.

I would like to know who has had full success with the 3TB GFH. By full success I mean:

  • Successfuly boot linux from the drive
  • Have access to the entirety of the drive (bonus if this is nearly all in 1 partition)
  • No significant compromises (net/usb booting, awkward partition setup with symlinks, etc)

I am particularly interested in a few aspects of the setup.
  1. The partitioning scheme
  2. Software versions (kernel and uboot, and setup if non-standard)
  3. The filesystem choice (ext2/3/4 or other)

I have been trying to do my setup with a hybrid MBR using the latest "official" (April 2012) release of uboot from Jeff and Davy. I have yet to get it to boot. I have found that information on a good hybrid MBR setup is very scattered, with people saying that they were successful, but not giving the details. (At least not clearly enough for my feeble mind)

I notice that a lot of people separate their boot and root partitions, is there a need for this for using the Hybrid MBR or is this just their personal partitioning choice? and what about the following question?
"Place EFI GPT (0xEE) partition first in MBR (good for GRUB)? (Y/N)"

I ultimately want to have 2 partitions: one for the system, and one for data to be served up on the network.

I have tried the following setups (all partitions formatted ext4): (hybrid MBRs were setup according to my understanding of rodsbooks - Creating a Hybrid MBR)

1
GPT: boot and root in one partition,data storage in another
Hybrid MBR: Boot/Root Partition

2
GPT: boot and root in one partition,data storage in another
Hybrid MBR: both partitions

3
GPT: boot and root in one partition,data storage in another
Hybrid MBR: no hybrid

4
GPT: boot and root in one partition, no other partitions
Hybrid MBR: boot/root partition

5
Normal MBR: boot and root in one partition, no other partitions

I have not had any success with any of these.

I believe that the uboot environment that I have setup is pretty standard. I try to boot USB, then SATA, then rescue and have no problem booting the other two.

Is ext4 the problem?

Teamspeak 3 Server (no replies)

$
0
0
Hello guys,

is it possible, to run a Teamspeak 3 Server on Pogoplug Pro with Debian on?

Please let me know.

Thanks for your help.

uBoot on Pogoplug Pro: “Unknown uBoot detected on mtd0” (4 replies)

$
0
0
Hi,

I’m new to ARM/Linux Device hacking. After a bit of digging around on various websites I found that it would be wonderful to have Debian GNU/Linux on my Pogoplug Pro (that’s what it says on the bottom sticker). The case is black, and hardware info is attached below.

I went through Run Linux on your Dockstar/Pogoplug but a while after executing “./kirkwood.debian-wheezy.sh” it failed with
Quote
kirkwood.debian-wheezy.sh
## Unknown uBoot detected on mtd0: 188602682dada4308e3d9945c3f6b6ed
##
## The installer could not detect the version of your current uBoot
## This may happen if you have installed a different uBoot on
## /dev/mtd0 or if you have bad blocks on /dev/mtd0

I browsed around in the forums but didn’t find something matching. Is there any solution to this or is this device unsupported for GNU/Linux in general?

Quote
kirkwood.debian-wheezy.sh
# ./kirkwood.debian-wheezy.sh
touch: /sbin/25122012170726: Read-only file system


!!!!!! DANGER DANGER DANGER DANGER DANGER DANGER !!!!!!

This script will replace the bootloader on /dev/mtd0.

If you lose power while the bootloader is being flashed,
your device could be left in an unusable state.


This script will configure your Dockstar to boot Debian
from a USB device. Before running this script, you should have
used fdisk to create the following partitions:

/dev/sda1 (Linux ext2, at least 400MB)
/dev/sda2 (Linux swap, recommended 256MB)


This script will DESTROY ALL EXISTING DATA on /dev/sda1
Please double check that the device on /dev/sda1 is the correct device.

By typing ok, you agree to assume all liabilities and risks
associated with running this installer.

If everything looks good, type 'ok' to continue: ok
Connecting to projects.doozan.com (50.116.34.13:80)
Installing Bootloader
# checking for /usr/sbin/nandwrite...
# checking for /usr/sbin/nanddump...

# Installing /usr/sbin/nanddump...
Connecting to download.doozan.com (50.116.34.13:80)
Connecting to download.doozan.com (50.116.34.13:80)
# Successfully installed /usr/sbin/nanddump.
# checking for /usr/sbin/flash_erase...
# checking for /usr/sbin/fw_printenv...

# Installing /usr/sbin/fw_printenv...
Connecting to download.doozan.com (50.116.34.13:80)
Connecting to download.doozan.com (50.116.34.13:80)
# Successfully installed /usr/sbin/fw_printenv.
# checking for /etc/fw_env.config...

# Installing /etc/fw_env.config...
Connecting to download.doozan.com (50.116.34.13:80)
Connecting to download.doozan.com (50.116.34.13:80)
# Successfully installed /etc/fw_env.config.

# Validating existing uBoot...
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
Connecting to jeff.doozan.com (50.116.34.13:80)
Connecting to projects.doozan.com (50.116.34.13:80)
## Unknown uBoot detected on mtd0: 188602682dada4308e3d9945c3f6b6ed
##
## The installer could not detect the version of your current uBoot
## This may happen if you have installed a different uBoot on
## /dev/mtd0 or if you have bad blocks on /dev/mtd0
##
## If you have bad blocks on mtd0, you should not try to install uBoot.
##
## Installation cancelled.
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
122880 inodes, 491519 blocks
24575 blocks (5%) reserved for the super user
First data block=0
Maximum filesystem blocks=4194304
15 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
./kirkwood.debian-wheezy.sh: line 318: /sbin/mkswap: not found
Connecting to cdn.debian.net (195.71.68.86:80)
./kirkwood.debian-wheezy.sh: line 354: ar: not found
tar: can't open 'data.tar.gz': No such file or directory
mv: can't rename './usr/sbin/debootstrap': No such file or directory
mv: can't rename './usr/share/debootstrap': No such file or directory
# checking for /usr/share/debootstrap/pkgdetails...

# Installing /usr/share/debootstrap/pkgdetails...
Connecting to download.doozan.com (50.116.34.13:80)
wget: can't open '/usr/share/debootstrap/pkgdetails.md5': No such file or directory
Connecting to download.doozan.com (50.116.34.13:80)
wget: can't open '/usr/share/debootstrap/pkgdetails.md5': No such file or directory
## Could not install /usr/share/debootstrap/pkgdetails from http://download.doozan.com/debian/pkgdetails, exiting.

Quote
Pogoplug Pro OS

# cat /proc/version
Linux version 2.6.31.6_SMP_820 (bdietrich@brad-ux) (gcc version 4.4.1 (Sourcery G++ Lite 2009q3-67) ) #96 SMP Tue Feb 8 10:06:27 PST 2011

# uname -a
Linux PogoplugPro 2.6.31.6_SMP_820 #96 SMP Tue Feb 8 10:06:27 PST 2011 armv6l GNU/Linux

# date
Tue Dec 25 17:01:04 UTC 2012

# cat /proc/cpuinfo
Processor : ARMv6-compatible processor rev 5 (v6l)
processor : 0
BogoMIPS : 279.34

processor : 1
BogoMIPS : 279.34

Features : swp half thumb fastmult edsp java
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xb02
CPU revision : 5

Hardware : Oxsemi NAS
Revision : 0000
Serial : 0000000000000000

# cat /proc/meminfo
MemTotal: 125764 kB
MemFree: 84348 kB
Buffers: 0 kB
Cached: 5564 kB
SwapCached: 0 kB
Active: 3604 kB
Inactive: 3712 kB
Active(anon): 1768 kB
Inactive(anon): 0 kB
Active(file): 1836 kB
Inactive(file): 3712 kB
Unevictable: 0 kB
Mlocked: 0 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 1780 kB
Mapped: 2744 kB
Slab: 3524 kB
SReclaimable: 292 kB
SUnreclaim: 3232 kB
PageTables: 124 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 88032 kB
Committed_AS: 5184 kB
VmallocTotal: 598016 kB
VmallocUsed: 1692 kB
VmallocChunk: 594420 kB

My USB flash drive:
Quote

Disk /dev/sda: 2013 MB, 2013265920 bytes
255 heads, 63 sectors/track, 244 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 1 208 1670728+ 83 Linux
/dev/sda2 209 244 289170 82 Linux swap

u-boot for Zyxwl nsa320 (7 replies)

$
0
0
I am struggling with my nsa320 using the stock u-boot. In addition to it not supporting thumb drives, the network is very flaky, but only in u-boot. Sometimes it works and sometimes it doesn't. When it doesn't work, I find that booting the stock firmware or Archlinux and then restarting fixes it. I don't know if this is normal for the nsa320, but it only fails to come up in u-boot and always works in Linux, so I suspect a software issue in the stock u-boot (maybe the lack of some work-around).

In any case, I want to replace u-boot with a version that supports usb and, hopefully, doesn't have the network problem.

I got the uboot-nsa320 source code from github psch2 and built it for the nsa320. This code did not include the kwboot program (but it did make the kwimage). So, I got the u-boot source code from denx and buily kwboot. That denx package did not have nsa320 support (or I somehow missed it). I'm surprised that it hasn't made it to the latest denx mainstream. Maybe I'm not looking in the right place.

Anyway, I used kwboot to load the u-boot.kwb file into the nsa320. It looked like it downloaded (had the [... stuff), but nothing happened. I used the "-t" switch to get a terminal when it was done and saw nothing happening there. (Kwboot with -t and no image let me watch the standard u-boot when I reset, so all that seems to works.)

Is there something else I need to do when building u-boot other than "make nsa320_config" and "make u-boot.kwb"?

Where is the best place to get the u-boot source (i.e., the latest functioning u-boot for nsa320)?

I am using the arm-linux-gnueabi- toolchain with gcc 4.6. Is that appropriate?

Thanks in advance,

Lance

Swap boot disks with between two dock (1 reply)

$
0
0
Hello

Forgive me if it's not the right place to post, I'am a newbie with this subject, I just presume it's the appropriate forum..

I own two docks, on each I attached an USB disk, and I installed Debian squeeze following http://projects.doozan.com/debian/, it works fine, thank you Jeff :-)

If I try to swap disks and put disk 2 on dock 1 (and vice versa), none of them boots.

Do I miss something ? is this normal ? does it mean that the pair can't be separate and only the parts installed conjointly work ?

Thanks for your reply

Andre

Dockstar - now way to boot (1 reply)

$
0
0
Hi all,

I have a dockstar on which I installed a couple of years ago Debian Squeeze.
Yesterday I tried to do a dist-upgrade.
Something went wrong.

No way to reboot via usb key.

I can boot using v3 rescue USB key.

Without USB key this is what I see via serial cable.

U-Boot 2011.12 (Feb 12 2012 - 21:33:07)
Seagate FreeAgent DockStar

SoC: Kirkwood 88F6281_A0
DRAM: 128 MiB
WARNING: Caches not enabled
NAND: 256 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot: 0
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 0 Storage Device(s) found
** Block device usb 0 not supported

** Invalid boot device **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000010000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI error: ubi_read_volume_table: the layout volume was not found
UBI error: ubi_init: cannot attach mtd1
UBI error: ubi_init: UBI error: cannot initialize UBI, error -22
UBI init error 22
** Block device usb 0 not supported
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
** Block device usb 0 not supported
** Block device usb 0 not supported
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS: done.
find_inode failed for name=uboot-original-mtd0.kwb
load: Failed to find inode
### JFFS2 LOAD ERROR<0> for uboot-original-mtd0.kwb!
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS:

thanks to all
Satjuice

I was wrong: installed uboot on B04 (1 reply)

$
0
0
Hi,

I used the command --force, but my pogo is pro and not pink v2, so i have now a bricked pogoplug .
I bought the cable C-42, so I have a serial connection. Befor installing,
i made backups with
# nanddump -nof mtd0.backup /dev/mtd0
# nanddump -nf mtd0.backup.oob
Using the boot sata: i used these commands:
flash_erase /dev/mtd0 0 4
nandwrite /dev/mtd0 mtd0.backup
reboot
The Pogoplug does not start. With serial connection i see this in terminal
# screen /dev/ttyUSB0 115200 8N1
Reading NAND, Image 0
Uncorrectable error(s) encountered in page with starting address 0x00040000.

Uncorrectable error(s) encountered in page with starting address 0x00040000.

Hdr len: 0xA1A2A3A4
Hdr CRC: 0xB1B2B3B4
read failed
Reading NAND, Image 1
Uncorrectable error(s) encountered in page with starting address 0x00100000.

Uncorrectable error(s) encountered in page with starting address 0x00100000.

Hdr len: 0xA1A2A3A4
Hdr CRC: 0xB1B2B3B4
read failed
Reading NAND, Image 0
Uncorrectable error(s) encountered in page with starting address 0x00040000.
Is it possible to reset the nand correctly. ? :S

Thanks

uBoot install canceled with Pogo E02(Black) (10 replies)

$
0
0
Hello

I have a Pogoplug E02Black)

I want to install Debian uboot on my Pogoplug E02(Black). but I can't install on my device

Can you help me to solve my problem?

My pogo's nand flash has a 1 bad blocks at 60000. Maybe, Is this a my problem?

I don't know about it

I hope to resolve my problems and install on my Pogoplug E02(Black)

I'll take iinfomations about my pogoplug E02(Black) below

My Pogo's cpu info is

Processor       : ARM926EJ-S rev 1 (v5l)
BogoMIPS        : 1192.75
Features        : swp half thumb fastmult edsp
CPU implementer : 0x56
CPU architecture: 5TE
CPU variant     : 0x2
CPU part        : 0x131
CPU revision    : 1
Cache type      : write-back
Cache clean     : cp15 c7 ops
Cache lockdown  : format C
Cache format    : Harvard
I size          : 16384
I assoc         : 4
I line length   : 32
I sets          : 128
D size          : 16384
D assoc         : 4
D line length   : 32
D sets          : 128
Hardware        : Feroceon-KW
Revision        : 0000
Serial          : 0000000000000000

uname -a is

Linux Pogoplug 2.6.22.18 #81 Tue Oct 19 16:05:00 PDT 2010 armv5tejl unknown

version is

Linux version 2.6.22.18 (bdietrich@buildman) (gcc version 4.2.1) #81 Tue Oct 19 16:05:00 PDT 2010

meminfo is

MemTotal:       256008 kB
MemFree:        154968 kB
Buffers:            12 kB
Cached:          84940 kB
SwapCached:          0 kB
Active:          18712 kB
Inactive:        67140 kB
SwapTotal:           0 kB
SwapFree:            0 kB
Dirty:               0 kB
Writeback:           0 kB
AnonPages:         928 kB
Mapped:           1588 kB
Slab:            13472 kB
SReclaimable:     1368 kB
SUnreclaim:      12104 kB
PageTables:         96 kB
NFS_Unstable:        0 kB
Bounce:              0 kB
CommitLimit:    128004 kB
Committed_AS:    83048 kB
VmallocTotal:   385024 kB
VmallocUsed:       324 kB
VmallocChunk:   384696 kB

blparam is

baudrate=115200
loads_echo=0
rootpath=/mnt/ARM_FS/
netmask=255.255.0.0
run_diag=yes
console=console=ttyS0,115200
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_root=root=/dev/mtdblock2 ro
ethmtu=1500
usb0Mode=host
nandEcc=1bit
ethact=egiga0
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
bootargs=console=ttyS0,115200 root=/dev/mtdblock2 ro
serverip=169.254.254.252
ipaddr=169.254.254.253
ethaddr=00:25:31:02:D6:74
cesvcid=LE9FW64CV8GHU3Z46W8Q2S3Z7N
ceboardver=PPV2
bootcmd=nand read.e 0x800000 0x100000 0x200000; setenv bootargs $(console) $(bootargs_root); bootm 0x800000

fw_printenv is

ethact=egiga0
bootdelay=3
baudrate=115200
arcNumber=2097
mainlineLinux=yes
console=ttyS0,115200
led_init=green blinking
led_exit=green off
led_error=orange blinking
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
mtdids=nand0=orion_nand
partition=nand0,2
stdin=serial
stdout=serial
stderr=serial
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_list=1 2 3 4
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_init=run usb_scan
usb_device=0:1
usb_root=/dev/sda1
usb_rootfstype=ext2
usb_rootdelay=10
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset

dmesg is
[    0.000000] Linux version 2.6.22.18 (bdietrich@buildman) (gcc version 4.2.1) #81 Tue Oct 19 16:05:00 PDT 2010
[    0.000000] CPU: ARM926EJ-S [56251311] revision 1 (ARMv5TE), cr=00053177
[    0.000000] Machine: Feroceon-KW
[    0.000000] Using UBoot passing parameters structure
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] On node 0 totalpages: 65536
[    0.000000]   DMA zone: 512 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 65024 pages, LIFO batch:15
[    0.000000]   Normal zone: 0 pages used for memmap
[    0.000000] CPU0: D VIVT write-back cache
[    0.000000] CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
[    0.000000] CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
[    0.000000] Built 1 zonelists.  Total pages: 65024
[    0.000000] Kernel command line: console=ttyS0,115200 root=/dev/mtdblock2 ro
[    0.000000] PID hash table entries: 1024 (order: 10, 4096 bytes)
[    0.000000] Console: colour dummy device 80x30
[    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.010000] Memory: 256MB 0MB 0MB 0MB = 256MB total
[    0.010000] Memory: 255872KB available (3592K code, 253K data, 124K init)
[    0.010000] Calibrating delay loop... 1192.75 BogoMIPS (lpj=5963776)
[    0.250000] Mount-cache hash table entries: 512
[    0.250000] CPU: Testing write buffer coherency: ok
[    0.250000] NET: Registered protocol family 16
[    0.250000]
[    0.250000] CPU Interface
[    0.250000] -------------
[    0.250000] SDRAM_CS0 ....base 00000000, size 256MB
[    0.250000] SDRAM_CS1 ....disable
[    0.250000] SDRAM_CS2 ....disable
[    0.250000] SDRAM_CS3 ....disable
[    0.250000] PEX0_MEM ....base e8000000, size 128MB
[    0.250000] PEX0_IO ....base f2000000, size   1MB
[    0.250000] INTER_REGS ....base f1000000, size   1MB
[    0.250000] NFLASH_CS ....base fa000000, size   2MB
[    0.250000] SPI_CS ....base f4000000, size  16MB
[    0.250000] BOOT_ROM_CS ....no such
[    0.250000] DEV_BOOTCS ....no such
[    0.250000] CRYPT_ENG ....base f0000000, size   2MB
[    0.250000]
[    0.250000]   Marvell Development Board (LSP Version KW_LSP_4.2.7_patch21_with_rx_desc_tuned)-- SHEEVA PLUG  Soc: 88F6281 A0 LE
[    0.250000]
[    0.250000]  Detected Tclk 200000000 and SysClk 400000000
[    0.250000] MV Buttons Device Load
[    0.250000] Marvell USB EHCI Host controller #0: c0652600
[    0.750000] PEX0 interface detected no Link.
[    0.750000] PCI: bus0: Fast back to back transfers enabled
[    0.750000] SCSI subsystem initialized
[    0.750000] usbcore: registered new interface driver usbfs
[    0.750000] usbcore: registered new interface driver hub
[    0.750000] usbcore: registered new device driver usb
[    0.750000] NET: Registered protocol family 2
[    0.760000] Time: kw_clocksource clocksource has been installed.
[    0.850000] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.850000] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[    0.850000] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
[    0.850000] TCP: Hash tables configured (established 8192 bind 8192)
[    0.850000] TCP reno registered
[    0.880000] RTC has been updated!!!
[    0.880000] RTC registered
[    0.880000] Use the XOR engines (acceleration) for enhancing the following functions:
[    0.880000]   o RAID 5 Xor calculation
[    0.880000]   o kernel memcpy
[    0.880000]   o kenrel memzero
[    0.880000] Number of XOR engines to use: 4
[    0.880000] cesadev_init(c00117b0)
[    0.880000] mvCesaInit: sessions=640, queue=64, pSram=f0000000
[    0.880000] MV Buttons Driver Load
[    0.880000] squashfs: version 3.3 (2007/10/31) Phillip Lougher
[    0.880000] squashfs: LZMA suppport for slax.org by jro
[    0.880000] JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.880000] io scheduler noop registered
[    0.880000] io scheduler anticipatory registered (default)
[    0.900000] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
[    0.900000] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
[    0.910000] RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
[    0.920000] Loading Marvell Ethernet Driver:
[    0.920000]   o Cached descriptors in DRAM
[    0.920000]   o DRAM SW cache-coherency
[    0.930000]   o Single RX Queue support - ETH_DEF_RXQ=0
[    0.930000]   o Single TX Queue support - ETH_DEF_TXQ=0
[    0.940000]   o TCP segmentation offload enabled
[    0.940000]   o Receive checksum offload enabled
[    0.950000]   o Transmit checksum offload enabled
[    0.950000]   o Network Fast Processing (Routing) supported
[    0.960000]   o Driver ERROR statistics enabled
[    0.960000]   o Driver INFO statistics enabled
[    0.970000]   o Proc tool API enabled
[    0.970000]   o Rx descripors: q0=128
[    0.970000]   o Tx descripors: q0=532
[    0.980000]   o Loading network interface(s):
[    0.990000]     o eth0, ifindex = 1, GbE port = 0
[    0.990000]     o eth1, ifindex = 2, GbE port = 1
[    1.000000]
[    1.000000] mvFpRuleDb (cfdf6000): 2048 entries, 8192 bytes
[    1.000000] Intel(R) PRO/1000 Network Driver - version 7.3.20-k2-NAPI
[    1.010000] Copyright (c) 1999-2006 Intel Corporation.
[    1.020000] e100: Intel(R) PRO/100 Network Driver, 3.5.17-k4-NAPI
[    1.020000] e100: Copyright(c) 1999-2006 Intel Corporation
[    1.030000]
[    1.030000] Warning Sata is Powered Off
[    1.030000] NFTL driver: nftlcore.c $Revision: 1.98 $, nftlmount.c $Revision: 1.41 $
[    1.040000] NAND device: Manufacturer ID: 0xad, Chip ID: 0xf1 (Hynix NAND 128MiB 3,3V 8-bit)
[    1.050000] Scanning device for bad blocks
[    1.050000] Bad eraseblock 3 at 0x00060000
[    1.110000] Using static partition definition
[    1.110000] Creating 4 MTD partitions on "nand_mtd":
[    1.120000] 0x00000000-0x00100000 : "u-boot"
[    1.120000] 0x00100000-0x00500000 : "uImage"
[    1.130000] 0x00500000-0x02500000 : "root"
[    1.130000] 0x02500000-0x08000000 : "data"
[    1.140000] ehci_marvell ehci_marvell.70059: Marvell Orion EHCI
[    1.140000] ehci_marvell ehci_marvell.70059: new USB bus registered, assigned bus number 1
[    1.180000] ehci_marvell ehci_marvell.70059: irq 19, io base 0xf1050100
[    1.200000] ehci_marvell ehci_marvell.70059: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
[    1.200000] usb usb1: configuration #1 chosen from 1 choice
[    1.210000] hub 1-0:1.0: USB hub found
[    1.210000] hub 1-0:1.0: 1 port detected
[    1.330000] ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.330000] USB Universal Host Controller Interface driver v3.0
[    1.610000] usb 1-1: new high speed USB device using ehci_marvell and address 2
[    1.760000] usb 1-1: configuration #1 chosen from 1 choice
[    1.760000] hub 1-1:1.0: USB hub found
[    1.770000] hub 1-1:1.0: 4 ports detected
[    1.880000] usbcore: registered new interface driver usblp
[    1.880000] drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
[    1.890000] Initializing USB Mass Storage driver...
[    1.890000] usbcore: registered new interface driver usb-storage
[    1.900000] USB Mass Storage support registered.
[    1.910000] mice: PS/2 mouse device common for all mice
[    1.910000] i2c /dev entries driver
[    1.910000] Linux telephony interface: v1.00
[    1.920000] md: linear personality registered for level -1
[    1.920000] md: raid0 personality registered for level 0
[    1.930000] md: raid1 personality registered for level 1
[    2.100000] raid6: int32x1     97 MB/s
[    2.270000] raid6: int32x2    114 MB/s
[    2.440000] raid6: int32x4    122 MB/s
[    2.610000] raid6: int32x8    110 MB/s
[    2.610000] raid6: using algorithm int32x4 (122 MB/s)
[    2.610000] md: raid6 personality registered for level 6
[    2.620000] md: raid5 personality registered for level 5
[    2.620000] md: raid4 personality registered for level 4
[    2.630000] raid5: measuring checksumming speed
[    2.680000]    arm4regs  :  1084.000 MB/sec
[    2.730000]    8regs     :   754.800 MB/sec
[    2.780000]    32regs    :   899.600 MB/sec
[    2.780000] raid5: using function: arm4regs (1084.000 MB/sec)
[    2.790000] device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
[    2.790000] dm_crypt using the OCF package.
[    2.800000] sdhci: Secure Digital Host Controller Interface driver
[    2.800000] sdhci: Copyright(c) Pierre Ossman
[    2.810000] usbcore: registered new interface driver usbhid
[    2.810000] drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
[    2.820000] TCP cubic registered
[    2.820000] NET: Registered protocol family 1
[    2.830000] NET: Registered protocol family 17
[    2.830000] md: Autodetecting RAID arrays.
[    2.840000] md: autorun ...
[    2.840000] md: ... autorun DONE.
[    4.600000] Empty flash at 0x009ac208 ends at 0x009ac800
[    8.800000] VFS: Mounted root (jffs2 filesystem) readonly.
[    8.800000] Freeing init memory: 124K
[   10.940000] eth0: link down
[   10.950000] eth0: started
[   12.530000] eth0: link up, full duplex, speed 100 Mbps

Install is

Pogoplug:/$ cd /tmp
Pogoplug:/tmp$ wget http://jeff.doozan.com/debian/uboot/install_uboot_mtd0.sh
Connecting to jeff.doozan.com (50.116.34.13:80)
install_uboot_mtd0.s 100% |*******************************| 18406  00:00:00 ETA
Pogoplug:/tmp$ chmod +x install_uboot_mtd0.sh
Pogoplug:/tmp$ ./install_uboot_mtd0.sh


!!!!!!  DANGER DANGER DANGER DANGER DANGER DANGER  !!!!!!

If you lose power to your device while running this script,
it could be left in an unusable state.

This script will replace the bootloader on /dev/mtd0.

This installer will only work on the following devices:
 Seagate Dockstar
 Seagate GoFlex Net
 Seagate GoFlex Home
 Pogoplug v1
 Pogoplug Pink (v2)
Do not run this installer on any other device.

By typing ok, you agree to assume all liabilities and risks
associated with running this installer.

If you agree, type 'ok' and press ENTER to continue: ok
# checking for /usr/sbin/nandwrite...
# checking for /usr/sbin/nanddump...
# checking for /usr/sbin/flash_erase...
# checking for /usr/sbin/fw_printenv...
# checking for /etc/fw_env.config...

# Validating existing uBoot...
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
Connecting to jeff.doozan.com (50.116.34.13:80)
valid-uboot.md5      100% |*******************************|  1133  --:--:-- ETA
## Unknown uBoot detected on mtd0: ec3fadd50ae24760b035b0afe9ac6018
##
## The installer could not detect the version of your current uBoot
## This may happen if you have installed a different uBoot on
## /dev/mtd0 or if you have bad blocks on /dev/mtd0
##
## If you have bad blocks on mtd0, you should not try to install uBoot.
##
## Installation cancelled.

Install(no prompt no uboot check parameter) is
Pogoplug:/tmp$ ./install_uboot_mtd0.sh --noprompt --no-uboot-check parameter
# checking for /usr/sbin/nandwrite...
# checking for /usr/sbin/nanddump...
# checking for /usr/sbin/flash_erase...
# checking for /usr/sbin/fw_printenv...
# checking for /etc/fw_env.config...

# Validating existing uBoot...
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
Connecting to jeff.doozan.com (50.116.34.13:80)
valid-uboot.md5      100% |*******************************|  1133  --:--:-- ETA
## Unknown uBoot detected on mtd0: ec3fadd50ae24760b035b0afe9ac6018
##
## --no-uboot-check flag detected, continuing installation

############################################
Your device could not be auto-detected.

You must be using a device listed below to run this installer.

What device are you using? Type the number of your device and press ENTER.
1 - Seagate Dockstar
2 - Seagate GoFlex Net
3 - Seagate GoFlex Home
4 - Pogoplug v1
5 - Pogoplug v2 - Pink
6 - Other
5
Selected Pogoplug v2 - Pink

# Installing uBoot
## Installing pinkpogo davygravy-2012-02-20
Connecting to download.doozan.com (50.116.34.13:80)
uboot.mtd0.kwb.md5   100% |*******************************|    32  --:--:-- ETA
Connecting to download.doozan.com (50.116.34.13:80)
uboot.mtd0.kwb       100% |*******************************|   512k 00:00:00 ETA
Erase Total 4 Units
Performing Flash Erase of length 131072 at offset 0x60000
MTD Erase failure: Input/output error
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
Bad block at 60000, 1 block(s) from 60000 will be skipped
Writing data to block 4 at offset 0x80000
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
## Verifying new uBoot...
Connecting to download.doozan.com (50.116.34.13:80)
uboot.mtd0.kwb.md5   100% |*******************************|    32  --:--:-- ETA
##
##
## VERIFICATION FAILED!
##
## uBoot was not properly installed to mtd0.
##
##
## YOUR DEVICE MAY BE IN AN UNUSABLE STATE.
## DO NOT REBOOT OR POWER OFF YOUR DEVICE
##
##
## Make a backup of /tmp/uboot-mtd0-dump someplace safe and
## then re-run this installer.

Goflex Net fail -need help to unbrick (4 replies)

$
0
0
Hello,

i have an almost new Goflex Net device, that i wanted to run debian. After trying different solutions (installing debian and rescue), i have problem with my device.

I cannot install a new uboot, and the only way i can access it is through the serial port with uart boot. I tried some of the suggestions in the forum, but i am stuck with it.
It seems the first nand block is bad. I want to ask the experts, what to do to get it running, if somebody could help me with unbricking. I hope there is some light chance to use it :)

I can boot it by uart to the dns-320 image on the usb, but i cannot install uboot. The script ends with verification failed. I tried writing with nandwrite (found in this forum that somebody managed to repair it with the same symptoms) with no success.

I cannot get further. Here is my log:

##
## VERIFICATION FAILED!
##
## uBoot was not properly installed to mtd0.
##
##
## YOUR DEVICE MAY BE IN AN UNUSABLE STATE.
## DO NOT REBOOT OR POWER OFF YOUR DEVICE
##
##
## Make a backup of /tmp/uboot-mtd0-dump someplace safe and
## then re-run this installer.

root@debian-kirkwood-wide:/tmp# /usr/sbin/flash_erase /dev/mtd0 0 5
Erase Total 5 Un[ 748.998066] nand_erase_nand: attempt to erase a bad block at page 0x00000000
its
Performing Flash Erase of length 131072 at offset 0x0
MTD Erase failure: Input/output error
root@debian-kirkwood-wide:/tmp# /usr/sbin/nandwrite /dev/mtd0 uboot.mtd0.kwb
Writing data to block 0 at offset 0x0
Bad block at 0, 1 block(s) from 0 will be skipped
Writing data to block 1 at offset 0x20000
Writing data to block 2 at offset 0x40000
Writing data to block 3 at offset 0x60000
Writing data to block 4 at offset 0x80000
td0t@debian-kirkwood-wide:/tmp# nanddump -bnof /tmp/uBoot.dump -l 0x80000 /dev/m
Block size 131072, page size 2048, OOB size 64
Dumping data starting at 0x00000000 and ending at 0x00080000...
root@debian-kirkwood-wide:/tmp# diff -s uboot.mtd0.kwb uBoot.dump
Binary files uboot.mtd0.kwb and uBoot.dump differ
root@debian-kirkwood-wide:/tmp#

Any help is much appreciated.

Pogoplug E02 completely dead - no ssh, www and serial (2 replies)

$
0
0
Hi there I have got a Pogoplug which is completetly dead - cant get access to it?
I think the only solution would be to recover via jtag?
Since pogoplugged.com is dead there is not much information about how to realize this with an ftdi chip or with the bus pirate?
Thanks for your replys!
Viewing all 902 articles
Browse latest View live