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

Restore original Uboot for Pogoplug V3 (2 replies)

August 11, 2014, 7:27 am
$
0
0
Hello,

I have a Pogoplug V3 (POGO-P24) and installed successfully Arch Linux on it. At the moment I want to use the original software from Cloud Engines, but the Uboot for Arch Linux has disabled it. Can anyone how I can reinstall the original Uboot for my Pogoplug V3?

Thanks in advance,

Dretech
↧
Search

GoFlexNet Bricked after installing Mainline U-Boot (no replies)

August 11, 2014, 7:28 am
$
0
0
I happened to have the perfect GoFlexNet setup, latest uBoot, netconsole enabled, recovery enabled, I was using Archlinuxarm, I went ahead and installed mainline uBoot, which removed all the mtdpartitions except uBoot and data, I lost recovery and netconsole, I somehow flashed Jeff' uBoot from Archlinux and screwed it up

Now the LED does not blink, there is no connectivity, I have serial access, but when logging into it using Serial I'm not able to see anything just some lines going across the screen

Does anybody have UART experience, like booting it from kwboot
↧
↧

Pogoplug Mobile - enable SD card booting from Linux? (3 replies)

August 12, 2014, 12:58 pm
$
0
0
I've been working on my Pogoplug Mobile for a couple months now, (I only get an hour or two at a time to play with it), and I've finally got it up and running.

I want to enable booting from the SD card, but I can't seem to find instructions that connects the dots for exactly my setup.


SETUP HISTORY:
I installed Arch Linux using the regular guide from here: Pogoplug Series 4
Unfortunately the USB flash drive I used was very unstable, and would only successfully boot a fraction of the time. (I tried 6 different flash drives, until I figured out that most Kingston drives do not work well... and all my drives are Kingston).

In the process of debugging the drive I soldered in the serial debug header so I could see the boot spew, which was very helpful. (I only note this to save people asking if I've done that, and to show people this little guy: CP2102 - it's a USB-to-UART adapter based on Silicon Labs' CP2102 chipset. [I'm not promoting this seller; I didn't buy mine from him. I just wanted to show that they are selling for ~$2, shipped.] The driver support for this chipset is fantastic... everything from Win2k to Win8.1, also MacOS X, Linux, Android... even WinCE. And it has worked flawlessly for me. I have an older one with a Prolific chipset, and the stupid thing bluescreened Win7 on me... which is a feat!)

It took me a while to find a USB key that worked with my Mobile, but when I did, I just reinstalled the rootfs on the key and everything started working again.
(Note: 'reinstalling rootfs' was another one that was hard to find instructions for. I did it from a desktop Ubuntu box, using these instructions Reinstallation, but using ext3 instead of ext4, and replacing the .gz with the one from the original install link).

So now everything is working. Time to screw it all up again!


SDCARD BOOTING:
I found this SD card booting tutorial: [Pogoplug Series 4] Booting Debian with Arch Linux ARM uBoot
but it seem to focus on the Pogoplug v4, which makes me afraid it may not work correctly on the Mobile.
And it says I should go update to the new uBoot first: 2014.07 U-Boot for FDT and Non-FDT Kernel
and if I want Debian I should do this one: Linux Kernel 3.16 Kirkwood package and rootfs
... but when I look at those threads I get a nosebleed and have to go lie down for a while.

Then I found this blog post on Qnology.com that targeted the Mobile:
http://blog.qnology.com/2014/07/hacking-pogoplug-v4-series-4-and-mobile.html

but when I try this command:
#remount '/' as read only
mount -o remount,ro /

I get an error "mount: / is busy". I looked it up, and I guess that means there are still processes using files on "/".
The thread suggested trying "fuser -v -m /" to identify the offending processes, but I get a list of several dozen.

I feel like that is probably an indication of something being very different in the expected setup, so I stopped there.

QUESTIONS:
1. Can I follow the Qnology blog post and just skip the 'remount' steps, or will that break something later on?
2. If the answer to #1 is "yes, it will break something", what work-around do I need to perform in order to do this from a working Arch Linux install?

Thanks!
↧

Ability to add extra Linux kernel parameters (2 replies)

August 12, 2014, 1:15 pm
$
0
0
Bodhi, I just saw that zswap was supported in your kernel. I want to enable that. 
zswap.enabled=1
Is there a good way to specify that in uboot?
↧

Pogoplug E02 Bad Block, with questions about installing the U-Boot software (14 replies)

September 9, 2014, 6:14 pm
$
0
0
Hi all,

I have a problem with a bad block coming up when I try to install the U-Boot software on my black pogoplug E02. I’m am following the directions here: http://blog.qnology.com/2013/03/tutorial-pogoplug-e02-with-arch-linux.html I’m attempting to make a (second) Squeezebox player for my network. I’ve followed these instructions before, but when I get to the installing of the U-Boot section, it fails with bad blocks.

I am able to boot into the OS that comes with the plug. I receive an IP address as handed out by my router. I have not set it to be a static IP as of yet. I can log in as root. The LED on the front of the unit is a steady green one. I’ve not looked at passing commands to it and checking for a change in the LED status.

I’ve seen that there are new instructions for this, but I’m unable to completely follow them. I have installed the tools from download.doozan.com .
The following is the output that I have for: dmesg, fw_printenv, and cat /proc/mtd .

Unfortunately I don’t know what version of U-Boot I’m using. I do not have a serial console attached. I have ordered the correct parts in order to have one though. However, they will take a few days to arrive. At least I think I’ve purchased the correct parts for a serial connection. But that’s a different topic altogether.

Thank you for any assistance you may be able to give me.
↧
↧

Do I have the correct uBoot installed? (12 replies)

September 5, 2014, 4:47 pm
$
0
0
Using a GoFlex Home base, I ran this procedure: 
cd /tmp
wget http://projects.doozan.com/uboot/install_uboot_mtd0.sh
chmod +x install_uboot_mtd0.sh
./install_uboot_mtd0.sh
I have a USB stick plugged in to the base with ArchLinux installed. I can boot and login via putty from a Windows machine.
The following command gives this output:
grep -a --null-data U-Boot /dev/mtd0ro 
U-Boot 2011.12 (Apr 18 2012 - 23:08:20)
Seagate GoFlexNetU-Boot
** Invalid partition type "%.32s" (expect "U-Boot")
U-Boot BUG at %s:%d!
I've been trying some things in the meantime, trying to see if I can get uBoot back to original so I can flash OEM firmware back on it.
I tried 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
But now I'm lost and don't know what I got.

Is the above uBoot the one I got from Jeffs tutorial? Also, did I fail to put the kernal on the device...I did Jeff's tutorial wrong, and only did the bootloader. Should I try putting the kernal on the device, unplugging the USB stick and try to get th resuce system loaded so I can boot to device instead of USB stick...or does that not matter?
↧

Pogoplug mobile instalation went hideously wrong (10 replies)

September 26, 2014, 7:59 pm
$
0
0
So I purchased a Pogoplug Mobile last week and wanted to play around with installing arch linux on to it.

I was following the guide here http://blog.qnology.com/2014/07/hacking-pogoplug-v4-series-4-and-mobile.html and was going well until I ran into this part. 

#SET MACADDRESS
/tmp/fw_setenv ethaddr "$(cat /sys/class/net/eth0/address)"

When I typed this in I was getting a error defined message and everything I typed after that I received the same error.

So what do I do? reboot it... and all H&ll breaks loose. :?:

I can't get an IP address on the little black box :( It just blinks green.

So I make a serial cable and putty my way in and the first thing I see is the no mac address set message when it tries to boot.

I go in, setenv ethaddr yadayadayada, I also set an IP address for it and I still can't talk to my little black box via IP/SSH

I went through several post on here trying different things and I'm sure I messed it up even more... I'm stuck

This is what it currently boots up to. 

U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:59:45)
Pogoplug V4

SoC:   Kirkwood 88F6192_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  128 MiB
MMC:   kwsdio: 0
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
Hit any key to stop autoboot:  0

NAND read: device 0 offset 0x100000, size 0x300000
 3145728 bytes read: OK
Unknown command '$(bootargs_root)' - try 'help'
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Pogov4>

If anyone can help that would be great. I would like to just start over and try again but I think i'm in too deep now.
↧

Totaly f***ed up my Goflex Home uBoot (11 replies)

October 4, 2014, 6:18 pm
$
0
0
Hello,

i have semi-bricked my Goflex Home. Updated uBoot and set up some wrong stuff in uBoot-Config. I have working UART, but all i see is: 

U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:41:47)
Seagate GoFlex Home

SoC:   Kirkwood 88F6281_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  256 MiB
In:    nc
Out:   nc
Err:   nc

looks like serial console is completely disabled... after this. i could uart-sideload some old uboot.uart, but dont know what is the next step. any attempts to rewrite the uboot-config from the old sideloaded uboot seem to be ignored by the new uboot.

has anybody some ideas?

greetings,

egon
↧
Search

Which uBoot best to use for E02? (1 reply)

October 10, 2014, 4:37 pm
$
0
0
Hi everyone,

New to the forum. I have a new pink E02 that I'm looking to install Arch (or possibly Debian) on. I already have one running Arch (see my experience with it here).

I was wondering what are the advantages of using Bodhi's (or other) uBoot over the Alarm mainline uBoot? Does any uBoot allow booting to stock Pogo OS anymore? (I know Jeff previously had a method for doing this)

Any other advantages to using alternate uBoot in lieu of Alarm uBoot?

thanks,
Neal
↧
↧

Pogoplug V4 Mobile won't boot after installing Qui's uBoot (1 reply)

October 13, 2014, 9:19 am
$
0
0
I have a Pogoplug V4 Mobile that was running Arch Linux using the uBoot from their site. It was running fine. But I tried to upgrade to Qui’s uBoot at
http://blog.qnology.com/2014/07/hacking-pogoplug-v4-series-4-and-mobile.html
so that I could boot from a SD card.

Now it no longer boots Linux. I’ve tried my existing USB drive and a new one with a fresh image from Archlinux. Both do the same thing. Here is the nc output from the boot:

U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:59:45)
Pogoplug V4 0
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 5 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
3124168 bytes read in 537 ms (5.5 MiB/s)
** File not found /boot/uInitrd **
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-3.1.10-34-ARCH
Created: 2014-07-31 7:56:24 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3124104 Bytes = 3 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK

Starting kernel ...

It stops there. Here is the output from printenv

arcNumber=3960
baudrate=115200
bootcmd=run bootcmd_usb; run bootcmd_mmc; run bootcmd_sata; reset
bootcmd_mmc=run mmc_init; run set_bootargs_mmc; run mmc_boot
bootcmd_sata=run sata_init; run set_bootargs_sata; run sata_boot;
bootcmd_usb=run usb_init; run set_bootargs_usb; run usb_boot;
bootdelay=10
console=ttyS0,115200
device=0:1
ethact=egiga0
ethaddr=00:25:31:05:8a:31
if_netconsole=ping $serverip
ipaddr=192.168.1.10
led_error=orange blinking
led_exit=green off
led_init=green blinking
machid=F78
mainlineLinux=yes
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=ext2load mmc $device 0x800000 /boot/uImage
mmc_load_uinitrd=ext2load mmc $device 0x1100000 /boot/uInitrd
mmc_root=/dev/mmcblk0p1
mtddevname=uImage2
mtddevnum=2
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
ncip=192.168.0.207
partition=nand0,2
preboot=run if_netconsole start_netconsole
preboot_nc=run if_netconsole start_netconsole
rootdelay=10
rootfstype=ext2
sata_boot=mw 0x800000 0 1; run sata_load_uimage; if run sata_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
sata_init=ide reset
sata_load_uimage=ext2load ide $device 0x800000 /boot/uImage
sata_load_uinitrd=ext2load ide $device 0x1100000 /boot/uInitrd
sata_root=/dev/sda1
serverip=192.168.0.207
set_bootargs_mmc=setenv bootargs console=$console root=$mmc_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_sata=setenv bootargs console=$console root=$sata_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$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=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
usb_rootfstype=ext2

I don’t know how to proceed. Any help would be appreciated.
↧

Pogoplug E02 upgrading U-boot. Bad block detected. (6 replies)

October 16, 2014, 1:00 am
$
0
0
Hi,

I was reading the guide on how to update the uBoot for Pogoplug E02. And I've detected bad block.

1. What should I do?
2. Also is it safe to upgrade the uBoot from Archlinux on usb or do I need to unplug all usbs? 


[root@alarm ~]# dmesg | grep -i 'bad'
[    7.269250] Scanning device for bad blocks
[    7.301153] Bad eraseblock 366 at 0x000002dc0000
↧

Pogoplug E02 problems with u-boot (3 replies)

October 17, 2014, 5:18 am
$
0
0
pogoplug e02
I am unable to see anything through putty, my USB to TTL Converter is http://www.ebay.com/itm/New-1PCS-5PIN-PL2303-USB-To-TTL-Auto-Converter-Adapter-Module-unit-For-arduino-/141150349286

I am following this guide:
http://blog.qnology.com/2013/10/pogoplug-e02-v2-serial-connection.html
Tested on 2 compters, winxp/win7 x32.
Putty window just stays blank.


If i connect sata drive inside 2.5" usb 2.0 external case it boots fine into debian installed on hdd, rescue system http://forum.doozan.com/read.php?4,7915 works too.


Here is fw_printenv output:
Quote

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_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_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:XX XX XX XX XX
serverip=192.168.1.2
ipaddr=192.168.1.100
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
set_bootargs_rescue=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts
bootcmd_rescue=run set_bootargs_rescue; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000
bootcmd_pogo=run bootcmd_rescue
rescue_installed=1
arcNumber=3542
machid=dd6
usb_rootfstype=ext3


cat /etc/fw_env.config
Quote

# MTD device name Device offset Env. size Flash sector size Number of sectors
/dev/mtd0 0xc0000 0x20000 0x20000

Both outputs were created while booted into rescue system.



Here is netconsole output:
http://forum.doozan.com/read.php?3,14,page=1
Quote

nc111nt_rodneybeede>nc -l -u -p 6666


U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
Pogoplug E02
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
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-0x000008000000 : "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: attached mtd1 to ubi0
UBI: MTD device name: "mtd=3"
UBI: MTD device size: 91 MiB
UBI: number of good PEBs: 726
UBI: number of bad PEBs: 2
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 0
UBI: available PEBs: 715
UBI: total number of reserved PEBs: 11
UBI: number of PEBs reserved for bad PEB handling: 7
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
** 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..

NAND read: device 0 offset 0x100000, size 0x400000
4194304 bytes read: OK
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-3.3.2-kirkwide
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3627768 Bytes = 3.5 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Using machid 0xdd6 from environment

Starting kernel ...




Now i flashed with method A http://forum.doozan.com/read.php?3,12381,12381#msg-12381 , now pogo e02 wont boot, with/without usb hdd.
Quote

\nc111nt_rodneybeede>nc -l -u -p 6666

U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:29:52)
Pogo E02
gcc (Debian 4.6.3-14) 4.6.3
GNU ld (GNU Binutils for Debian) 2.22
Unknown command 'fw_setenv' - try 'help'

U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:29:52)
Pogo E02
gcc (Debian 4.6.3-14) 4.6.3
GNU ld (GNU Binutils for Debian) 2.22
Hit any key to stop autoboot: 0
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found

no USB devices available

no USB devices available

no USB devices available

no USB devices available
PogoE02>



with 1 usb hdd attached:
Quote

\nc111nt_rodneybeede>nc -l -u -p 6666


U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:29:52)
Pogo E02
gcc (Debian 4.6.3-14) 4.6.3
GNU ld (GNU Binutils for Debian) 2.22
Unknown command 'fw_setenv' - try 'help'

U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:29:52)
Pogo E02
gcc (Debian 4.6.3-14) 4.6.3
GNU ld (GNU Binutils for Debian) 2.22
Hit any key to stop autoboot: 0
(Re)start 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: DOS

Part Start Sector Num Sectors UUID Type
1 2048 20971520 000d7189-01 83 Boot
2 20973568 1932550144 000d7189-02 83
Unknown command 'setexpr' - try 'help'
Attempting to boot from usb 0:1...
Unknown command 'load' - try 'help'
Checking if uenvcmd is set ...
Running default loadzimage ...
Unknown command 'load' - try 'help'
Running default loaduimage ...
Unknown command 'load' - try 'help'

no USB devices available

no USB devices available

no USB devices available
PogoE02>


Quote

PogoE02> printenv
p r i n t e n v
arcNumber=3542
baudrate=115200
bootcmd=usb start; setenv letter 9;for type in usb; do for disk in 0 1 2 3; do i
f ${type} part ${disk};then setexpr letter $letter + 1;run load;fi;done;done;
bootcmd_pogo=run bootcmd_rescue
bootcmd_rescue=run set_bootargs_rescue; nand read.e 0x800000 0x100000 0x400000;
bootm 0x800000
bootdelay=10
bootm=echo Booting from ${disk} ...; run setargs; bootm ${loadaddr};
bootz=echo Booting from ${disk} ...; run setargs; bootz ${loadaddr} - ${fdt_addr
};
console=ttyS0
ethact=egiga0
ethaddr=00:XXXXXXXX
fdt_addr=0x800000
fdt_file=/boot/dtbs/kirkwood-pogo_e02.dtb
if_netconsole=ping $serverip
importbootenv=echo Importing environment (uEnv.txt)...; env import -t $loadaddr
$filesize
ipaddr=192.168.1.100
letter=9
load=echo Attempting to boot from ${type} ${disk}:1...;if run loadbootenv; then
run importbootenv;fi;echo Checking if uenvcmd is set ...;if test -n $uenvcmd; th
en echo Running uenvcmd ...;run uenvcmd;fi;echo Running default loadzimage ...;i
f run loadzimage; then run loadfdt;run bootz;fi;echo Running default loaduimage
...;if run loaduimage; then run bootm;fi;
loadaddr=0x810000
loadbootenv=load ${type} ${disk}:1 ${loadaddr} /boot/uEnv.txt
loadfdt=load ${type} ${disk}:1 ${fdt_addr} ${fdt_file}
loaduimage=load ${type} ${disk}:1 ${loadaddr} ${uimage}
loadzimage=load ${type} ${disk}:1 ${loadaddr} ${zimage}
machid=dd6
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),-(rootfs)
ncip=192.168.1.2
preboot=run if_netconsole start_netconsole
rescue_installed=1
serverip=192.168.1.2
set_bootargs_rescue=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs
ro rootfstype=ubifs $mtdparts
setargs=setenv bootargs console=${console},${baudrate} ${optargs} root=/dev/sd${
letter}1 rw rootwait ${mtdparts}
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; se
tenv stdout nc; setenv stderr nc; version;fw_setenv start_netconsole setenv ncip
$serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stder
r nc; version;
stderr=nc
stdin=nc
stdout=nc
uimage=/boot/uImage
zimage=/boot/zImage

Environment size: 2162/131068 bytes
PogoE02>
↧

my Pogoplug v4 dead after Nand flash (1 reply)

October 19, 2014, 1:47 pm
$
0
0
Hi all,
I bricked my seconde Pogo v4 ( I don't remember how that happen ) and my big problem is when I tried to revert back the stock firmware to mtd0 with serial/UART and tftp I did something wrong and now the pogoplug light wont turn on and I see no boot info on Putty with serial connexion ( just black screen) but at least I see the RJ45 light blinking ( but no ip adress on my router dhcp) and the cpu heat as normal, the last thing I did is :
tftpboot 0x800000 mtd0
nand erase 0x0 0x80000
nand write 0x800000 0x0 0x80000
then I hard rebooted the pogo and it wont come back, I think something happend to the nand flash.
note: I have another pogoplug v4 working on archlinux on a sata hdd .
Do you thing my pogoplug is dead or is there a chance to give it another life ?
↧
↧

PogoPlug V4 won't boot after failed env input (1 reply)

October 20, 2014, 10:13 pm
$
0
0
Hello everyone,

I was trying to do a reinstall of arch on my pogoplug when the power in the part of the house where the pogolpug was connected went down. My pogo didn't start correctly so I soldered a serial cable. I can see what is happening via putty. Could somebody please help me to get the pogoplug working again? I am not a very experienced user.

This is the installation log, in-till power went down: 
login as: root
root@192.168.178.17's password:
~ # killall hbwd
~ # cd /tmp
/tmp # wget http://download.doozan.com/uboot/nanddump
Connecting to download.doozan.com (50.116.34.13:80)
/tmp # wget http://download.doozan.com/uboot/nandwrite
Connecting to download.doozan.com (50.116.34.13:80)
/tmp # wget http://download.doozan.com/uboot/flash_erase
Connecting to download.doozan.com (50.116.34.13:80)
/tmp # wget http://download.doozan.com/uboot/fw_printenv
Connecting to download.doozan.com (50.116.34.13:80)
/tmp # chmod +x flash_erase fw_printenv nanddump nandwrite
/tmp # cp fw_printenv fw_setenv
/tmp # mount -o remount,rw /
/tmp # echo "/dev/mtd0 0xc0000 0x20000 0x20000">/etc/fw_env.config
/tmp # wget http://download.qnology.com/pogoplug/v4/uboot.2014.07-tld-1.pogo_v4.
bodhi.tar
Connecting to download.qnology.com (162.252.240.221:80)
/tmp # wget http://download.qnology.com/pogoplug/v4/uboot.2014.07-tld-1.pogo_v4.
bodhi.md5
Connecting to download.qnology.com (162.252.240.221:80)
/tmp # md5sum uboot.2014.07-tld-1.pogo_v4.bodhi.tar
d4b497dc5239844fd2d45f4ca83132e0  uboot.2014.07-tld-1.pogo_v4.bodhi.tar
/tmp # cat uboot.2014.07-tld-1.pogo_v4.bodhi.md5
d4b497dc5239844fd2d45f4ca83132e0

/tmp #
/tmp # tar -xf uboot.2014.07-tld-1.pogo_v4.bodhi.tar
/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.2014.07-tld-1.pogo_v4.mtd0.kwb
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
/tmp #
/tmp # wget http://download.qnology.com/pogoplug/v4/uboot.2014.07-tld-1.environm
ent.img.bodhi.tar
Connecting to download.qnology.com (162.252.240.221:80)
/tmp # wget http://download.qnology.com/pogoplug/v4/uboot.2014.07-tld-1.environm
ent.img.bodhi.md5
Connecting to download.qnology.com (162.252.240.221:80)
/tmp # d5sum uboot.2014.07-tld-1.environment.img.bodhi.tar
-sh: d5sum: not found
/tmp # cat uboot.2014.07-tld-1.environment.img.bodhi.md5
c5921e3ea0a07a859878339ffb771088

/tmp # tar -xf uboot.2014.07-tld-1.environment.img.bodhi.tar
/tmp # /tmp/flash_erase /dev/mtd0 0xc0000 1
Erase Total 1 Units
Performing Flash Erase of length 131072 at offset 0xc0000 done
/tmp # /tmp/nandwrite -s 786432 /dev/mtd0 uboot.2014.07-tld-1.environment.img
Writing data to block 6 at offset 0xc0000
/tmp #
/tmp # /tmp/fw_setenv ethaddr "$(cat /sys/class/net/eth0/address)"
Cannot parse config file: Invalid argument
/tmp # /tmp/fw_printenv ethaddr
Cannot parse config file: Invalid argument
/tmp # /tmp/fw_setenv ethaddr "$(cat /sys/class/net/eth0/address)"
Cannot parse config file: Invalid argument
/tmp # /tmp/fw_setenv ethaddr "$(cat /sys/class/net/eth0/address)"
Cannot parse config file: Invalid argument
/tmp # /tmp/fw_printenv ethaddr
Cannot parse config file: Invalid argument
/tmp # /tmp/fw_setenv arcNumber 3960
Cannot parse config file: Invalid argument
/tmp # /tmp/fw_setenv machid F78
Cannot parse config file: Invalid argument
/tmp # /tmp/flash_erase /dev/mtd0 0xc0000 1
Erase Total 1 Units
Performing Flash Erase of length 131072 at offset 0xc0000 done
/tmp # /tmp/nandwrite -s 786432 /dev/mtd0 uboot.2014.07-tld-1.environment.img
Writing data to block 6 at offset 0xc0000
/tmp #
/tmp # /tmp/fw_setenv ethaddr "$(cat /sys/class/net/eth0/address)"
Cannot parse config file: Invalid argument
/tmp # /tmp/fw_setenv usb_rootfstype ext3
Cannot parse config file: Invalid argument
/tmp # reboot
-sh: reboot: not found
/tmp # /
-sh: /: Permission denied
/tmp #
/tmp # #SET MACADDRESS
/tmp # /tmp/fw_setenv ethaddr "$(cat /sys/class/net/eth0/address)"
Cannot parse config file: Invalid argument
/tmp # /tmp/fw_setenv ethaddr "$(cat /sys/class/net/eth0/address)"
Cannot parse config file: Invalid argument
/tmp # /tmp/fw_printenv ethaddr
Cannot parse config file: Invalid argument
/tmp # /tmp/fw_setenv arcNumber 3960
Cannot parse config file: Invalid argument
/tmp # /tmp/fw_setenv machid F78.
Cannot parse config file: Invalid argument
/tmp # wget http://download.qnology.com/pogoplug/v4/uboot.2014.07-tld-1.environm
ent.img.bodhi.tar
Connecting to download.qnology.com (162.252.240.221:80)
wget: can't open 'uboot.2014.07-tld-1.environment.img.bodhi.tar': File exists
/tmp # wget http://download.qnology.com/pogoplug/v4/uboot.2014.07-tld-1.environm
ent.img.bodhi.md5
Connecting to download.qnology.com (162.252.240.221:80)
wget: can't open 'uboot.2014.07-tld-1.environment.img.bodhi.md5': File exists
/tmp # md5sum uboot.2014.07-tld-1.environment.img.bodhi.tar
c5921e3ea0a07a859878339ffb771088  uboot.2014.07-tld-1.environment.img.bodhi.tar
/tmp # cat uboot.2014.07-tld-1.environment.img.bodhi.md5
c5921e3ea0a07a859878339ffb771088

/tmp # tar -xf uboot.2014.07-tld-1.environment.img.bodhi.tar
/tmp # /tmp/flash_erase /dev/mtd0 0xc0000 1
Erase Total 1 Units
Performing Flash Erase of length 131072 at offset 0xc0000 done
/tmp # /tmp/nandwrite -s 786432 /dev/mtd0 uboot.2014.07-tld-1.environment.img
Writing data to block 6 at offset 0xc0000
/tmp #
/tmp # /tmp/fw_setenv ethaddr "$(cat /sys/class/net/eth0/address)"
Cannot parse config file: Invalid argument

This is what is happening when de device boots: 
U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:59:45)
Pogoplug V4

SoC:   Kirkwood 88F6192_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  128 MiB
MMC:   kwsdio: 0
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
Warning: failed to set MAC address

Hit any key to stop autoboot:  0
Pogov4> printenv
arcNumber=2097
baudrate=115200
bootargs=root=ubi0:rootfs ubi.mtd=2,512 rootfstype=ubifs console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x25,0x31,0x00,0xd4,0x6f mem=128 poweroutage=yes
bootcmd=run boot_nand
bootcmd_mmc=run mmc_init; run set_bootargs_mmc; run mmc_boot
bootcmd_sata=run sata_init; run set_bootargs_sata; run sata_boot;
bootcmd_usb=run usb_init; run set_bootargs_usb; run usb_boot;
bootdelay=10
console=ttyS0,115200
device=0:1
ethact=egiga0
if_netconsole=ping $serverip
ipaddr=192.168.0.231
led_error=orange blinking
led_exit=green off
led_init=green blinking
machid=0x831
mainlineLinux=yes
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=ext2load mmc $device 0x800000 /boot/uImage
mmc_load_uinitrd=ext2load mmc $device 0x1100000 /boot/uInitrd
mmc_root=/dev/mmcblk0p1
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
preboot_nc=run if_netconsole start_netconsole
rootdelay=10
rootfstype=ext3
sata_boot=mw 0x800000 0 1; run sata_load_uimage; if run sata_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
sata_init=ide reset
sata_load_uimage=ext2load ide $device 0x800000 /boot/uImage
sata_load_uinitrd=ext2load ide $device 0x1100000 /boot/uInitrd
sata_root=/dev/sda1
serverip=192.168.0.220
set_bootargs_mmc=setenv bootargs console=$console root=$mmc_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_sata=setenv bootargs console=$console root=$sata_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
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: 2304/131068 bytes

As you can see it loads Uboot, but doesn't set a mac adress. I really hope somebody can help me with this.
↧

U-Boot VAMP 0.6 Pogoplug V4 (no replies)

October 21, 2014, 5:37 am
$
0
0
I have a collection of Pogoplugs thank's to the great U-Boot on here, brilliant little devices.

I also have serial access on them all.

On one of them I run VAMP 0.6 as a music player, I have tried a squeezelite install on ARCH/Debian but it does not seem to work as well as the Fedora based VAMP image that they have created on Vortexbox.

As the E02 is getting harder to find, I have ordered a V4 device, I would like to stick this in the AV rack and use it as just a music player.

The VAMP install is based on a Doozan U-Boot with modified environments, I would love to get VAMP running on a V4 but I believe the U-Boot is different, will the environments script in this guide work? or will I brick the V4

http://vortexbox.org/forum/vortexbox/general/51318-install-vamp-0-6 

/usr/sbin/fw_setenv 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 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'
/usr/sbin/fw_setenv usb_boot 'mw 0x800000 0 1; ext2load usb $usb_device 0x800000 uImage; if ext2load usb $usb_device 0x1100000 uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi'
/usr/sbin/fw_setenv usb_scan_1 "usb=0:1 dev=sda3"
/usr/sbin/fw_setenv usb_scan_2 "usb=1:1 dev=sdb3"
/usr/sbin/fw_setenv usb_scan_3 "usb=2:1 dev=sdc3"
/usr/sbin/fw_setenv usb_scan_4 "usb=3:1 dev=sdd3"
/usr/sbin/fw_setenv usb_rootfstype ext4


If it's a no go, what's required to get this image running on a V4, it looks a perfect device to run as a Squeezebox player, I am not bothered whether it will SD or USB boot, SD would be nice though.

Any help would be gratefully appreciated, keep up the good work :)
↧
Search

Goflex net bad blocks and no boot. (6 replies)

October 24, 2014, 9:27 am
$
0
0
Hi,

Please help.
After install new uboot (2014.07) and rootfs my Goflex net "bricked".

With Serial Jtag I see I have bad blocks on flash.
I realized it during uboot install, but because my nandwrite not reported errors, I disregard it.

Serial consol shows this:
[ 21.935908] Scanning device for bad blocks
[ 22.103884] Bad eraseblock 1534 at 0x00000bfc0000

My problem is not able to boot Goflex net from USB or SATA.

I attached serial console log.
And copy here too:

Thanks for any help.
Robert 


U-Boot 2014.07-tld-1 (Jul 18 2014 - 00:35:50)
Seagate GoFlex Net

SoC:   Kirkwood 88F6281_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
88E1116 Initialized on egiga0
No link on egiga0
ping failed; host 192.168.178.26 is not alive
Hit any key to stop autoboot:  0 
(Re)start 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
2756040 bytes read in 477 ms (5.5 MiB/s)
6032465 bytes read in 592 ms (9.7 MiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.16.0-kirkwood-tld-2
   Created:      2014-09-01  23:18:31 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2755976 Bytes = 2.6 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-3.16.0-kirkwood-tld-2
   Created:      2014-09-01  23:18:48 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6032401 Bytes = 5.8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 3.16.0-kirkwood-tld-2 (root@tldDebian) (gcc version 4.6.3 (Debian 4.6.3-14) ) #2 PREEMPT Sun Aug 31 18:56:01 PDT 2014
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: Seagate GoFlex Net
[    0.000000] Memory policy: Data cache writeback
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfstype=ext3 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Memory: 115744K/131072K available (5441K kernel code, 397K rwdata, 1840K rodata, 257K init, 299K bss, 15328K reserved)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xffe00000   (2048 kB)
[    0.000000]     vmalloc : 0xc8800000 - 0xff000000   ( 872 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc07248b0   (7283 kB)
[    0.000000]       .init : 0xc0725000 - 0xc0765444   ( 258 kB)
[    0.000000]       .data : 0xc0766000 - 0xc07c975c   ( 398 kB)
[    0.000000]        .bss : 0xc07c975c - 0xc08144dc   ( 300 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] NR_IRQS:114
[    0.000011] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474836475ns
[   20.493464] Console: colour dummy device 80x30
[   20.493492] Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584)
[   20.583246] pid_max: default: 32768 minimum: 301
[   20.583363] Security Framework initialized
[   20.583430] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[   20.583449] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[   20.584320] Initializing cgroup subsys devices
[   20.584383] Initializing cgroup subsys freezer
[   20.584412] Initializing cgroup subsys net_cls
[   20.584459] Initializing cgroup subsys blkio
[   20.584557] CPU: Testing write buffer coherency: ok
[   20.585027] Setting up static identity map for 0x5273f0 - 0x527448
[   20.587399] devtmpfs: initialized
[   20.591378] prandom: seed boundary self test passed
[   20.595443] prandom: 100 self tests passed
[   20.595474] pinctrl core: initialized pinctrl subsystem
[   20.595987] regulator-dummy: no parameters
[   20.596461] NET: Registered protocol family 16
[   20.596916] DMA: preallocated 256 KiB pool for atomic coherent allocations
[   20.598166] cpuidle: using governor ladder
[   20.598194] cpuidle: using governor menu
[   20.598334] Kirkwood: MV88F6281-A1, TCLK=200000000.
[   20.598358] Feroceon L2: Enabling L2
[   20.598397] Feroceon L2: Cache support initialised.
[   20.634770] vgaarb: loaded
[   20.635126] usbcore: registered new interface driver usbfs
[   20.635203] usbcore: registered new interface driver hub
[   20.635328] usbcore: registered new device driver usb
[   20.636324] Switched to clocksource orion_clocksource
[   20.675100] NET: Registered protocol family 2
[   20.676090] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[   20.676115] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[   20.676135] TCP: Hash tables configured (established 1024 bind 1024)
[   20.676206] TCP: reno registered
[   20.676219] UDP hash table entries: 256 (order: 0, 4096 bytes)
[   20.676241] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[   20.676505] NET: Registered protocol family 1
[   20.676843] RPC: Registered named UNIX socket transport module.
[   20.676855] RPC: Registered udp transport module.
[   20.676862] RPC: Registered tcp transport module.
[   20.676870] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   20.677181] Unpacking initramfs...
[   21.179454] Freeing initrd memory: 5884K (c1101000 - c16c0000)
[   21.179593] NetWinder Floating Point Emulator V0.97 (double precision)
[   21.180756] futex hash table entries: 256 (order: -1, 3072 bytes)
[   21.180825] audit: initializing netlink subsys (disabled)
[   21.180880] audit: type=2000 audit(0.680:1): initialized
[   21.181700] zbud: loaded
[   21.181972] VFS: Disk quotas dquot_6.5.2
[   21.182023] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[   21.182586] NFS: Registering the id_resolver key type
[   21.182645] Key type id_resolver registered
[   21.182655] Key type id_legacy registered
[   21.182681] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[   21.182696] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[   21.182867] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[   21.183178] msgmni has been set to 237
[   21.183331] Key type big_key registered
[   21.185686] alg: No test for stdrng (krng)
[   21.185805] bounce: pool size: 64 pages
[   21.185872] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[   21.185891] io scheduler noop registered
[   21.185906] io scheduler deadline registered
[   21.186076] io scheduler cfq registered (default)
[   21.186592] mv_xor mv_xor.0: Marvell shared XOR driver
[   21.226404] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[   21.266391] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[   21.266567] mv_xor mv_xor.1: Marvell shared XOR driver
[   21.306390] mv_xor mv_xor.1: Marvell XOR: ( xor cpy )
[   21.346388] mv_xor mv_xor.1: Marvell XOR: ( xor cpy )
[   21.346820] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[   21.347824] console [ttyS0] disabled
[   21.367924] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33, base_baud = 12500000) is a 16550A
[   21.915194] console [ttyS0] enabled
[   21.920126] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
[   21.926537] nand: Micron MT29F2G08AAD
[   21.930215] nand: 256MiB, SLC, page size: 2048, OOB size: 64
[   21.935908] Scanning device for bad blocks
[   22.103884] Bad eraseblock 1534 at 0x00000bfc0000
[   22.163412] 4 cmdlinepart partitions found on MTD device orion_nand
[   22.169726] Creating 4 MTD partitions on "orion_nand":
[   22.174894] 0x000000000000-0x000000100000 : "u-boot"
[   22.180291] 0x000000100000-0x000000500000 : "uImage"
[   22.185644] 0x000000500000-0x000002500000 : "rootfs"
[   22.191025] 0x000002500000-0x000010000000 : "data"
[   22.197176] libphy: Fixed MDIO Bus: probed
[   22.213951] libphy: orion_mdio_bus: probed
[   22.218240] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[   23.297450] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:10:75:26:65:ae
[   23.306443] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   23.313001] ehci-pci: EHCI PCI platform driver
[   23.317547] ehci-orion: EHCI orion driver
[   23.321653] orion-ehci orion-ehci.0: EHCI Host Controller
[   23.327127] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
[   23.334852] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
[   23.356362] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[   23.362498] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[   23.369344] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   23.376619] usb usb1: Product: EHCI Host Controller
[   23.381520] usb usb1: Manufacturer: Linux 3.16.0-kirkwood-tld-2 ehci_hcd
[   23.388267] usb usb1: SerialNumber: orion-ehci.0
[   23.393650] hub 1-0:1.0: USB hub found
[   23.397499] hub 1-0:1.0: 1 port detected
[   23.402311] mousedev: PS/2 mouse device common for all mice
[   23.716383] usb 1-1: new high-speed USB device number 2 using orion-ehci
[   23.944114] usb 1-1: New USB device found, idVendor=058f, idProduct=6387
[   23.950874] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   23.958070] usb 1-1: Product: Mass Storage
[   23.962184] usb 1-1: Manufacturer: Generic
[   23.966299] usb 1-1: SerialNumber: 065414A6
[   24.416355] rtc-mv rtc-mv: internal RTC not ticking
[   24.421447] i2c /dev entries driver
[   24.426765] hidraw: raw HID events driver (C) Jiri Kosina
[   24.432547] drop_monitor: Initializing network drop monitor service
[   24.439106] TCP: cubic registered
[   24.442447] NET: Registered protocol family 17
[   24.447080] Key type dns_resolver registered
[   24.452105] registered taskstats version 1
[   24.457253] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[   24.465431] Freeing unused kernel memory: 256K (c0725000 - c0765000)
Loading, please wait...
[   24.547301] udevd[55]: starting version 175
[   24.722850] SCSI subsystem initialized
[   24.768293] usb-storage 1-1:1.0: USB Mass Storage device detected
[   24.784262] sata_mv sata_mv.0: cannot get optional clkdev
[   24.816169] scsi0 : usb-storage 1-1:1.0
[   24.820268] sata_mv sata_mv.0: slots 32 ports 2
[   24.836109] usbcore: registered new interface driver usb-storage
[   24.860866] scsi1 : sata_mv
[   24.867852] usbcore: registered new interface driver uas
[   24.882622] scsi2 : sata_mv
[   24.885778] ata1: SATA max UDMA/133 irq 21
[   24.911416] ata2: SATA max UDMA/133 irq 21
[   25.256374] ata1: SATA link down (SStatus 0 SControl F300)
[   25.626888] ata2: SATA link down (SStatus 0 SControl F300)
[   25.828598] scsi 0:0:0:0: Direct-Access     Generic  Flash Disk       8.07 PQ: 0 ANSI: 2
[   25.868684] sd 0:0:0:0: [sda] 7989248 512-byte logical blocks: (4.09 GB/3.80 GiB)
[   25.876773] sd 0:0:0:0: [sda] Write Protect is off
[   25.882017] sd 0:0:0:0: [sda] No Caching mode page found
[   25.887407] sd 0:0:0:0: [sda] Assuming drive cache: write through
[   25.937149]  sda: sda1
[   25.942398] sd 0:0:0:0: [sda] Attached SCSI removable disk
[   25.959586] sd 0:0:0:0: Attached scsi generic sg0 type 0
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
mount: mounting /dev/sda1 on /root failed: Invalid argument
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev failed: No such file or directory
done.
Target filesystem doesn't have requested /sbin/init.
No init found. Try passing init= bootarg.
modprobe: module i8042 not found in modules.dep
[   35.845694] uhci_hcd: USB Universal Host Controller Interface driver
[   35.860027] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[   35.874891] usbcore: registered new interface driver usbhid
[   35.880626] usbhid: USB HID core driver
↧

PogoPlug E02 uboot, cannot stop autoboot (5 replies)

November 2, 2014, 3:32 pm
$
0
0
Hi everyone!

My PogoPlug E02 won't boot after I flashed it to the latest U-Boot referenced in the PogoPlug E02 Arch Linux installation instructions.

I get the following from my PogoPlug's serial output when I boot it: 

U-Boot 2014.04.R3-1 (May 26 2014 - 19:45:55) Arch Linux ARM
Pogo E02

SoC:   Kirkwood 88F6281_A0
DRAM:  256 MiB
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
Hit any key to stop autoboot:  0
PogoE02>
PogoE02>
PogoE02>
PogoE02> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>> U-Boot 2014.3>>>

I cannot get to the PogoE02> prompt when I hit a key just after U-Boot starts up- my PogoPlug just prints the "U-Boot 2014.3>>>>", PuTTY "beeps" and I can't type "printenv" or anything else at the PogoE02> prompt. PuTTY just beeps the ASCII "bell" when I hit a key.

I get the output above with or without the USB stick I installed Arch Linux to inserted into a USB port on my PogoPlug.

Is there anything I can do to keep it from printing "U-Boot 2014.3>>>>" and actually be able to type commands at the PogoE02> prompt?

I get the above output with or without the USB drive I installed Arch Linux to plugged into a USB port on my PogoPlug.;

I remember getting errors when I was installing Arch Linux to the USB stick but U-Boot flashed OK (I don't remember seeing any errors).

Thanks in advance for any help you can provide!
↧
↧

Pogoplug e02 boot from iscsi (1 reply)

November 8, 2014, 1:48 am
$
0
0
Hello,

I was wondering if it's possible to boot Debian Wheezy from a iscsi NAS?
Goal is to remove the USB device from the Pogo (I have a total of 5).

Other possibility is to only load system and swap from USB and data from iscsi NAS, but then I still need a USB device that is attached to the Pogo!

Hope to hear from you guys.

Greetings.
↧

has any one installed debian on a ix2-dl (no replies)

November 23, 2014, 3:11 pm
$
0
0
i need help with running debian on a ix2-dl
Processor : Feroceon 88FR131 rev 1 (v5l)
BogoMIPS : 1589.24
Features : swp half thumb fastmult edsp
CPU implementer : 0x56
CPU architecture: 5TE
CPU variant : 0x2
CPU part : 0x131
CPU revision : 1

Hardware : Feroceon-KW
Revision : 0000
Serial : 0000000000000000
root@ix2-dl:/var/lib#
root@ix2-dl:/var/lib# cat /proc/mtd
dev: size erasesize name
mtd0: 00080000 00020000 "uboot"
mtd1: 00020000 00020000 "env"
mtd2: 00020000 00020000 "env2"
mtd3: 00300000 00020000 "uImage"
mtd4: 00400000 00020000 "initrd"
mtd5: 3f800000 00020000 "boot"
mtd6: 40000000 00020000 "flash"
↧

Bootting off network (1 reply)

November 28, 2014, 2:05 pm
$
0
0
I haven't been following up with this forum for quite sometimes. So, I am probably a bit dusty (outdated) w.r.t. the current u-boot version.

Anyway, I have a Seagate GoFLEX NET (with a 2TB SATA HDD) and some Seagate Dockstar units. Instead of installing debian ARM to every single Seagate Dockstar unit, I want to setup my Seagate GoFLEX NET with a single folder to install the debian ARM distro so that any of my Seagate Dockstar units will be able to boot off of this folder and leave the original partitions intact on my Seagate Dockstar units, except replacing its original u-boot with the Doozan u-boot. Is it possible?
↧
Viewing all 902 articles
Browse latest View live
Search