Attempt to restore Pink Pogoplug e02 to factory corrupt uboot. Where to go from here?
Posted by Oakley470
|
Oakley470
Attempt to restore Pink Pogoplug e02 to factory corrupt uboot. Where to go from here? July 15, 2013 03:44PM |
So i got Linux and everything up running successfully until i got to setting up the DLNA streaming server and things went downhill from there. Needless to say i thought after the mess i had made i should just start from scratch and went about trying to figure out how to flash the pogo back to stock. I ran this command from the original pogoplug software environment(booted without the linux usb)
Can someone please direct me from here how i can reflash the original pogoplug boot/software? I just want to get it back to factory settings so i can restart the project! I am not very strong with Linux coding so i have been having trouble figuring out where to go next with my google searching. Thank you very much in advance!!!
/usr/local/cloudengines/bin/./blparam 'bootcmd=run bootcmd_original"After that the pogo would no longer boot with or without the flash drive and i cannot ssh into it. So i now have a serial connection established and get the following output on boot.
U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
Pogoplug E02
SoC: Kirkwood 88F6281_A0
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: 128 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-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: 728
UBI: number of bad PEBs: 0
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: 717
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..
### JFFS2 loading 'uboot-original-mtd0.kwb' to 0x800000
Scanning JFFS2 FS: ........ done.
### JFFS2 load complete: 524288 bytes loaded to 0x800000
## Starting application at 0x00800200 ...
U-Boot 1.1.4 (Sep 28 2009 - 11:55:23) Cloud Engines v2.0 (3.4.16)
U-Boot code: 00600000 -> 0067FFF0 BSS: -> 00690D60
Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz
DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000 size 256MB
DRAM Total size 256MB 16bit width
Flash: 0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:128 MB
CPU : Marvell Feroceon (Rev 1)
CLOUD ENGINES BOARD: PPV2
Streaming disabled
Write allocate disabled
USB 0: host mode
PEX 0: interface detected no Link.
Net: egiga0 [PRIME], egiga1
Hit any key to stop autoboot: 0
## Error: "bootcmd_original
/usr/local/cloudengines/bin/./blparam" not defined
CE>>
Can someone please direct me from here how i can reflash the original pogoplug boot/software? I just want to get it back to factory settings so i can restart the project! I am not very strong with Linux coding so i have been having trouble figuring out where to go next with my google searching. Thank you very much in advance!!!
|
Re: Attempt to restore Pink Pogoplug e02 to factory corrupt uboot. Where to go from here? July 16, 2013 02:36AM |
Admin Registered: 13 years ago Posts: 18,585 |
First, you should get it booted back to either Arch or Debian. From there you can restore it easily. Take either:
- Arch rootfs at Arch site
or
- my rootfs:
http://forum.doozan.com/read.php?2,12096
(Updated 19 June 2013)
or
- Davy's rootfs:
http://forum.doozan.com/read.php?2,7806
Put it on an empty USB thumb, and try booting with it.
- Arch rootfs at Arch site
or
- my rootfs:
http://forum.doozan.com/read.php?2,12096
(Updated 19 June 2013)
or
- Davy's rootfs:
http://forum.doozan.com/read.php?2,7806
Put it on an empty USB thumb, and try booting with it.
|
Oakley470
Re: Attempt to restore Pink Pogoplug e02 to factory corrupt uboot. Where to go from here? July 16, 2013 04:06PM |
Sorry for being too newb about this but I want to make sure I get it right and don't brick the pogo. I'm using a Windows machine and do not have access to a linux one btw. So if I download your file, I can find a program online that will allow me to format the drive to ext3, label it as rootfs, put your file on the root of the drive, and then put it back into the pogoo and reboot. (Previously I formatted the drive using ssh comands I no longer can access.) But From there it should boot into the system and I will regain ssh access to the root prompt?
|
Oakley470
Re: Attempt to restore Pink Pogoplug e02 to factory corrupt uboot. Where to go from here? July 16, 2013 09:18PM |
|
Re: Attempt to restore Pink Pogoplug e02 to factory corrupt uboot. Where to go from here? July 16, 2013 11:51PM |
Admin Registered: 13 years ago Posts: 18,585 |
Oakley470 Wrote:
-------------------------------------------------------
> Your method did not work, i get the exact same
> process as originally stated above when booting
> with the ext3 drive in. I downloaded your rootfs,
> extracted and placed all 3 files in the root of
> the empty drive and nothing was different in the
> boot process.
Oakley470,
In each alternative, the rootfs needs to be extracted. For the first 2, use tar command to extract. The 3rd alternative, Davy's rootfs is an image so you have to use the method described in his post.
Did you extract all the files in the archive to the Ext3 USB?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> Your method did not work, i get the exact same
> process as originally stated above when booting
> with the ext3 drive in. I downloaded your rootfs,
> extracted and placed all 3 files in the root of
> the empty drive and nothing was different in the
> boot process.
Oakley470,
In each alternative, the rootfs needs to be extracted. For the first 2, use tar command to extract. The 3rd alternative, Davy's rootfs is an image so you have to use the method described in his post.
Did you extract all the files in the archive to the Ext3 USB?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Oakley470
Re: Attempt to restore Pink Pogoplug e02 to factory corrupt uboot. Where to go from here? July 17, 2013 06:08AM |
|
Oakley470
Re: Attempt to restore Pink Pogoplug e02 to factory corrupt uboot. Where to go from here? July 17, 2013 10:47AM |
I apologize for being dumb...i didn't look at what i was downloading from your link. Downloaded the correct file and got it to boot to here
can you direct where i need to go from here?
UBI: attached mtd1 to ubi0 UBI: MTD device name: "mtd=3" UBI: MTD device size: 91 MiB UBI: number of good PEBs: 728 UBI: number of bad PEBs: 0 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: 717 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'! Loading file "/boot/uImage" from usb device 0:1 (usbda1) 1 bytes read Found bootable drive on usb 0:1 Loading file "/boot/uImage" from usb device 0:1 (usbda1) 1806344 bytes read Loading file "/boot/uInitrd" from usb device 0:1 (usbda1) 6082114 bytes read ## Booting kernel from Legacy Image at 00800000 ... Image Name: Linux-3.8.11-kirkwood-tld-3 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1806280 Bytes = 1.7 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 01100000 ... Image Name: initramfs-3.8.11-kirkwood-tld-3 Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 6082050 Bytes = 5.8 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Using machid 0xdd6 from environment 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] Linux version 3.8.11-kirkwood-tld-3 (root@tldDebian) (gcc version 4.6.3 (Debian 4.6.3-1) ) #2 PREEMPT Fri Jun 14 07:51:05 PDT 2013 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977 [ 0.000000] CPU: VIVT data cache, VIVT instruction cache [ 0.000000] Machine: Pogoplug E02 [ 0.000000] Memory policy: ECC disabled, Data cache writeback [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024 [ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfstype=ext2 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) [ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes) [ 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.000000] __ex_table already sorted, skipping sort [ 0.000000] Memory: 256MB = 256MB total [ 0.000000] Memory: 248604k/248604k available, 13540k reserved, 0K highmem [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) [ 0.000000] vmalloc : 0xd0800000 - 0xff000000 ( 744 MB) [ 0.000000] lowmem : 0xc0000000 - 0xd0000000 ( 256 MB) [ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB) [ 0.000000] .text : 0xc0008000 - 0xc0465134 (4469 kB) [ 0.000000] .init : 0xc0466000 - 0xc04895bc ( 142 kB) [ 0.000000] .data : 0xc048a000 - 0xc04cc508 ( 266 kB) [ 0.000000] .bss : 0xc04cc508 - 0xc052fb08 ( 398 kB) [ 0.000000] NR_IRQS:114 [ 0.000000] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474ms [ 0.000000] Console: colour dummy device 80x30 [ 14.345528] Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584) [ 14.435347] pid_max: default: 32768 minimum: 301 [ 14.435449] Security Framework initialized [ 14.435517] Mount-cache hash table entries: 512 [ 14.436062] Initializing cgroup subsys cpuacct [ 14.436081] Initializing cgroup subsys devices [ 14.436093] Initializing cgroup subsys freezer [ 14.436103] Initializing cgroup subsys net_cls [ 14.436113] Initializing cgroup subsys blkio [ 14.436196] CPU: Testing write buffer coherency: ok [ 14.436568] Setting up static identity map for 0x32e0a0 - 0x32e0dc [ 14.438182] devtmpfs: initialized [ 14.439744] pinctrl core: initialized pinctrl subsystem [ 14.440070] regulator-dummy: no parameters [ 14.440372] NET: Registered protocol family 16 [ 14.441480] DMA: preallocated 1024 KiB pool for atomic coherent allocations [ 14.442149] Kirkwood: MV88F6281-A0, TCLK=200000000. [ 14.442169] Feroceon L2: Enabling L2 [ 14.442207] Feroceon L2: Cache support initialised. [ 14.444437] bio: create slab <bio-0> at 0 [ 14.444748] vgaarb: loaded [ 14.445285] Switching to clocksource orion_clocksource [ 14.458737] NET: Registered protocol family 2 [ 14.459257] TCP established hash table entries: 2048 (order: 2, 16384 bytes) [ 14.459313] TCP bind hash table entries: 2048 (order: 1, 8192 bytes) [ 14.459344] TCP: Hash tables configured (established 2048 bind 2048) [ 14.459408] TCP: reno registered [ 14.459421] UDP hash table entries: 256 (order: 0, 4096 bytes) [ 14.459443] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) [ 14.459622] NET: Registered protocol family 1 [ 14.459851] Unpacking initramfs... [ 14.974200] Freeing initrd memory: 5936K [ 14.974267] NetWinder Floating Point Emulator V0.97 (double precision) [ 14.974751] audit: initializing netlink socketÿ (disabled) [ 14.974799] type=2000 audit(0.620:1): initialized [ 14.975702] VFS: Disk quotas dquot_6.5.2 [ 14.975754] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 14.975895] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc. [ 14.976116] msgmni has been set to 497 [ 14.977923] alg: No test for stdrng (krng) [ 14.978012] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252) [ 14.978024] io scheduler noop registered [ 14.978032] io scheduler deadline registered [ 14.978052] io scheduler cfq registered (default) [ 14.978160] mv_xor mv_xor.0: Marvell XOR driver [ 15.015395] mv_xor mv_xor.0: Marvell XOR: ( xor cpy ) [ 15.055390] mv_xor mv_xor.0: Marvell XOR: ( xor fill cpy ) [ 15.055480] mv_xor mv_xor.1: Marvell XOR driver [ 15.095391] mv_xor mv_xor.1: Marvell XOR: ( xor cpy ) [ 15.135388] mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy ) [ 15.135626] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled [ 15.156173] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A [ 15.591057] console [ttyS0] enabled [ 15.595403] NAND device: Manufacturer ID: 0xad, Chip ID: 0xf1 (Hynix NAND 128MiB 3,3V 8-bit), 128MiB, page size: 2048, OOB size: 64 [ 15.607299] Scanning device for bad blocks [ 15.718548] 4 cmdlinepart partitions found on MTD device orion_nand [ 15.724842] Creating 4 MTD partitions on "orion_nand": [ 15.730023] 0x000000000000-0x000000100000 : "u-boot" [ 15.735235] 0x000000100000-0x000000500000 : "uImage" [ 15.740441] 0x000000500000-0x000002500000 : "rootfs" [ 15.745692] 0x000002500000-0x000008000000 : "data" [ 15.751064] mousedev: PS/2 mouse device common for all mice [ 16.765440] rtc-mv rtc-mv: internal RTC not ticking [ 16.770428] i2c /dev entries driver [ 16.774087] cpuidle: using governor ladder [ 16.778297] cpuidle: using governor menu [ 16.782273] leds-gpio leds-gpio: pins are not configured from the driver [ 16.789242] drop_monitor: Initializing network drop monitor service [ 16.795835] TCP: cubic registered [ 16.799166] NET: Registered protocol family 17 [ 16.803678] Key type dns_resolver registered [ 16.808342] registered taskstats version 1 [ 16.813258] drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 16.820267] Freeing init memory: 140K Loading, please wait... [ 16.875994] udevd[47]: starting version 175 [ 16.944148] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4 [ 17.015525] usbcore: registered new interface driver usbfs [ 17.021105] usbcore: registered new interface driver hub [ 17.038644] libphy: mv643xx_eth smi: probed [ 17.071628] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:25:31:00:a2:3a [ 17.093346] usbcore: registered new device driver usb [ 17.119236] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 17.150835] orion-ehci orion-ehci.0: Marvell Orion EHCI [ 17.175562] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1 [ 17.183384] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000 [ 17.235366] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00 [ 17.241411] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 17.248253] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 17.255524] usb usb1: Product: Marvell Orion EHCI [ 17.260245] usb usb1: Manufacturer: Linux 3.8.11-kirkwood-tld-3 ehci_hcd [ 17.266990] usb usb1: SerialNumber: orion-ehci.0 [ 17.272489] hub 1-0:1.0: USB hub found [ 17.276307] hub 1-0:1.0: 1 port detected [ 17.595375] usb 1-1: new high-speed USB device number 2 using orion-ehci [ 17.746896] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608 [ 17.753643] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 17.760837] usb 1-1: Product: USB2.0 Hub [ 17.767801] hub 1-1:1.0: USB hub found [ 17.779041] hub 1-1:1.0: 4 ports detected [ 18.065649] usb 1-1.1: new high-speed USB device number 3 using orion-ehci [ 18.178396] usb 1-1.1: New USB device found, idVendor=05dc, idProduct=a740 [ 18.185317] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 18.192685] usb 1-1.1: Product: USB Flash Drive [ 18.197249] usb 1-1.1: Manufacturer: UFD [ 18.201185] usb 1-1.1: SerialNumber: AA04016900000361 [ 18.226261] SCSI subsystem initialized [ 18.234296] Initializing USB Mass Storage driver... [ 18.239593] scsi0 : usb-storage 1-1.1:1.0 [ 18.245104] usbcore: registered new interface driver usb-storage [ 18.251174] USB Mass Storage support registered. [ 19.236745] scsi 0:0:0:0: Direct-Access UFD USB Flash Drive 1100 PQ: 0 ANSI: 0 CCS [ 19.261337] sd 0:0:0:0: [sda] 15663104 512-byte logical blocks: (8.01 GB/7.46 GiB) [ 19.270303] sd 0:0:0:0: [sda] Write Protect is off [ 19.275800] sd 0:0:0:0: [sda] No Caching mode page present [ 19.281315] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 19.291669] sd 0:0:0:0: [sda] No Caching mode page present [ 19.297221] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 19.304181] sda: sda1 [ 19.309420] sd 0:0:0:0: [sda] No Caching mode page present [ 19.314953] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 19.321113] sd 0:0:0:0: [sda] Attached SCSI removable disk [ 19.336794] 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. [ 27.345218] EXT2-fs (sda1): warning: mounting ext3 filesystem as ext2 Begin: Running /scripts/local-bottom ... done. done. Begin: Running /scripts/init-bottom ... done. Target filesystem doesn't have requested /sbin/init. No init found. Try passing init= bootarg. [ 27.405263] uhci_hcd: USB Universal Host Controller Interface driver [ 27.419102] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 27.436160] usbcore: registered new interface driver usbhid [ 27.441758] usbhid: USB HID core driver (initramfs)
can you direct where i need to go from here?
|
Re: Attempt to restore Pink Pogoplug e02 to factory corrupt uboot. Where to go from here? July 18, 2013 12:18AM |
Admin Registered: 13 years ago Posts: 18,585 |
@Oakley470,
NP. Your uBoot env for rootfstype is currently set to ext2.
Take the rootfs USB stick to a Linux box and convert it to ext2 using tune2fs. Boot with it. If not successful, go back to serial console and please get the output of
> printenv
and post it here.
It's a really good sign that it got to the point where it is right now. Might need to tweak some uBoot envs to get it boot into Debian.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
NP. Your uBoot env for rootfstype is currently set to ext2.
Take the rootfs USB stick to a Linux box and convert it to ext2 using tune2fs. Boot with it. If not successful, go back to serial console and please get the output of
> printenv
and post it here.
It's a really good sign that it got to the point where it is right now. Might need to tweak some uBoot envs to get it boot into Debian.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Oakley470
Re: Attempt to restore Pink Pogoplug e02 to factory corrupt uboot. Where to go from here? July 18, 2013 03:50PM |
Switched to ext2 and i get the same boot error i got in the beginning with no usb drive in. here is my boot process with the drive and the printenv results. I ran printenv booted with the drive in, not sure if that makes a difference or if i had to reboot and then run it with no drive.
U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
Pogoplug E02
SoC: Kirkwood 88F6281_A0
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: 128 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... 3 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
** Bad partition 1 **
** Partition 1 not valid on device 0 **
** Unable to use usb 0:1 for fatload **
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: 728
UBI: number of bad PEBs: 0
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: 717
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'!
** Bad partition 1 **
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
** Bad partition 1 **
** Bad partition 1 **
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.
### JFFS2 load complete: 524288 bytes loaded to 0x800000
## Starting application at 0x00800200 ...
U-Boot 1.1.4 (Sep 28 2009 - 11:55:23) Cloud Engines v2.0 (3.4.16)
U-Boot code: 00600000 -> 0067FFF0 BSS: -> 00690D60
Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz
DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000 size 256MB
DRAM Total size 256MB 16bit width
Flash: 0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:128 MB
CPU : Marvell Feroceon (Rev 1)
CLOUD ENGINES BOARD: PPV2
Streaming disabled
Write allocate disabled
USB 0: host mode
PEX 0: interface detected no Link.
Net: egiga0 [PRIME], egiga1
Hit any key to stop autoboot: 0
## Error: "bootcmd_original
/usr/local/cloudengines/bin/./blparam" not defined
CE>> printenv
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
bootargs=console=ttyS0,115200 root=/dev/mtdblock2 ro
serverip=169.254.254.252
ipaddr=169.254.254.253
ethaddr=00:25:31:00:A2:3A
cesvcid=AWVSL58GTCD4T3R3FQGZ8K7G5E
ceboardver=PPV2
bootcmd=run bootcmd_original
/usr/local/cloudengines/bin/./blparam bootcmd=run
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
Environment size: 758/131068 bytes
CE>>
|
Re: Attempt to restore Pink Pogoplug e02 to factory corrupt uboot. Where to go from here? July 19, 2013 12:52AM |
Admin Registered: 13 years ago Posts: 18,585 |
Oakley470,
Pardon me if I state the obvious below! I just want to cover all the details.
The environment I am looking for can be printed out when you stop the serial console at count down (> Hit any key to stop autoboot: 0)
How did you remove the journal from the rootfs USB to make it Ext2? The command should be (assuming the USB drive was assigned sdb1):
tune2fs -O ^has_journal /dev/sdb1
After removing journal, execute:
sync
to make sure everything is written. If you want to double check, umount/mount the USB drive again on that Linux box, see if it was mounted as Ext2.
Then umount the drive, and take it to the Pogo E02 and boot with it.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 07/19/2013 12:53AM by bodhi.
Pardon me if I state the obvious below! I just want to cover all the details.
> U-Boot 2011.12 (Feb 20 2012 - 21:21:59) > Pogoplug E02 > > SoC: Kirkwood 88F6281_A0 > DRAM: 256 MiB > WARNING: Caches not enabled > NAND: 128 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... 3 USB Device(s) found > scanning bus for storage devices... 1 > Storage Device(s) found > ** Bad partition 1 ** > ** Partition 1 not valid on device 0 **The above indicated that the USB drive was not formatted properly. So it could not be used for booting.
> > Environment size: 758/131068 bytes > CE>> >The above indicated that the stock uBoot was used for booting (the new uBoot was not able to boot from USB). So the environments you've printed were not what we are looking for.
The environment I am looking for can be printed out when you stop the serial console at count down (> Hit any key to stop autoboot: 0)
How did you remove the journal from the rootfs USB to make it Ext2? The command should be (assuming the USB drive was assigned sdb1):
tune2fs -O ^has_journal /dev/sdb1
After removing journal, execute:
sync
to make sure everything is written. If you want to double check, umount/mount the USB drive again on that Linux box, see if it was mounted as Ext2.
Then umount the drive, and take it to the Pogo E02 and boot with it.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 07/19/2013 12:53AM by bodhi.
|
oakley470
Re: Attempt to restore Pink Pogoplug e02 to factory corrupt uboot. Where to go from here? July 24, 2013 08:53PM |
You definitely are not pointing out the obvious! I don't understand much of this. After unable to make the drive work, I stopped messing around with windows programs that could supposedly change the format to ext2 and made a live Linux cd. I was finally now able to get the pogo booted back to debian successfully. Can you give me a link/instructions on how to now flash the pogoplug back to factory settings so I can start over with the whole thing? There is a lot online saying many different things, which is how I got into this situation in the first place, so I just want to make sure I get it right this time. Thank you for everything now I feel much better now that im making progress!
|
Re: Attempt to restore Pink Pogoplug e02 to factory corrupt uboot. Where to go from here? July 25, 2013 12:09AM |
Admin Registered: 13 years ago Posts: 18,585 |
Since we all ran Jeff's script to replace uBoot to install Debian or Arch, only mtd0 was erased, and the original uBoot image was written to the rootfs (mtd2).
Here is what shv did to restore uBoot on a GoFlex Net:
http://forum.doozan.com/read.php?3,12506,12506#msg-12506
The instruction should be the same. However, you need to be aware that on Pogoplug E02, if you make a mistake then it's JTAG time! UART booting does not work on the E02. So if you're not sure about something, please post. Also, I have not tried this, since I never want to go back to the original software.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Here is what shv did to restore uBoot on a GoFlex Net:
http://forum.doozan.com/read.php?3,12506,12506#msg-12506
The instruction should be the same. However, you need to be aware that on Pogoplug E02, if you make a mistake then it's JTAG time! UART booting does not work on the E02. So if you're not sure about something, please post. Also, I have not tried this, since I never want to go back to the original software.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Oakley470
Re: Attempt to restore Pink Pogoplug e02 to factory corrupt uboot. Where to go from here? July 25, 2013 11:00AM |
Something went wrong...I followed the first few steps and everything was ok, however when i got to the first reboot the device never booted back up. I reestablished my serial connection and now here is the output, right back to where i was at the start of all this however i cannot boot from the usb for debian anymore.
here is the output from printenv when i stop the autoboot if it helps.
U-Boot 1.1.4 (Sep 28 2009 - 11:55:23) Cloud Engines v2.0 (3.4.16) U-Boot code: 00600000 -> 0067FFF0 BSS: -> 00690D60 Soc: 88F6281 A0 (DDR2) CPU running @ 1200Mhz L2 running @ 400Mhz SysClock = 400Mhz , TClock = 200Mhz DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6 DRAM CS[0] base 0x00000000 size 256MB DRAM Total size 256MB 16bit width Flash: 0 kB Addresses 8M - 0M are saved for the U-Boot usage. Mem malloc Initialization (8M - 7M): Done NAND:128 MB CPU : Marvell Feroceon (Rev 1) CLOUD ENGINES BOARD: PPV2 Streaming disabled Write allocate disabled USB 0: host mode PEX 0: interface detected no Link. Net: egiga0 [PRIME], egiga1 Hit any key to stop autoboot: 0 ## Error: "bootcmd_original /usr/local/cloudengines/bin/./blparam" not defined CE>>
here is the output from printenv when i stop the autoboot if it helps.
U-Boot 1.1.4 (Sep 28 2009 - 11:55:23) Cloud Engines v2.0 (3.4.16) U-Boot code: 00600000 -> 0067FFF0 BSS: -> 00690D60 Soc: 88F6281 A0 (DDR2) CPU running @ 1200Mhz L2 running @ 400Mhz SysClock = 400Mhz , TClock = 200Mhz DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6 DRAM CS[0] base 0x00000000 size 256MB DRAM Total size 256MB 16bit width Flash: 0 kB Addresses 8M - 0M are saved for the U-Boot usage. Mem malloc Initialization (8M - 7M): Done NAND:128 MB CPU : Marvell Feroceon (Rev 1) CLOUD ENGINES BOARD: PPV2 Streaming disabled Write allocate disabled USB 0: host mode PEX 0: interface detected no Link. Net: egiga0 [PRIME], egiga1 Hit any key to stop autoboot: 0 CE>> printenv 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 bootargs=console=ttyS0,115200 root=/dev/mtdblock2 ro serverip=169.254.254.252 ipaddr=169.254.254.253 ethaddr=00:25:31:00:A2:3A cesvcid=AWVSL58GTCD4T3R3FQGZ8K7G5E ceboardver=PPV2 bootcmd=run bootcmd_original /usr/local/cloudengines/bin/./blparam bootcmd=run 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 Environment size: 758/131068 bytes CE>>
|
Re: Attempt to restore Pink Pogoplug e02 to factory corrupt uboot. Where to go from here? July 26, 2013 12:35AM |
Admin Registered: 13 years ago Posts: 18,585 |
Oakley470,
Did you keeop the log of your attempt to restore?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Did you keeop the log of your attempt to restore?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
oa
Re: Attempt to restore Pink Pogoplug e02 to factory corrupt uboot. Where to go from here? July 26, 2013 06:43AM |
|
Re: Attempt to restore Pink Pogoplug e02 to factory corrupt uboot. Where to go from here? July 27, 2013 01:46AM |
Admin Registered: 13 years ago Posts: 18,585 |
oa Wrote:
-------------------------------------------------------
> No,I dumbly did not. There were no failures or
> anything that seemed important like that so I
> didn't even think about it.
OK. It's not a brick yet! but we need to be careful. I'll will see if I can try a few commands to get you boot back to Debian.
But in the mean time, could you get back to serial console and do:
> help
and post the output here. It would be good to see which commands this CE uBoot version supports.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> No,I dumbly did not. There were no failures or
> anything that seemed important like that so I
> didn't even think about it.
OK. It's not a brick yet! but we need to be careful. I'll will see if I can try a few commands to get you boot back to Debian.
But in the mean time, could you get back to serial console and do:
> help
and post the output here. It would be good to see which commands this CE uBoot version supports.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Oakley470
Re: Attempt to restore Pink Pogoplug e02 to factory corrupt uboot. Where to go from here? July 27, 2013 11:00AM |
Here it is, glad to hear im not screwed!!
U-Boot 1.1.4 (Sep 28 2009 - 11:55:23) Cloud Engines v2.0 (3.4.16) U-Boot code: 00600000 -> 0067FFF0 BSS: -> 00690D60 Soc: 88F6281 A0 (DDR2) CPU running @ 1200Mhz L2 running @ 400Mhz SysClock = 400Mhz , TClock = 200Mhz DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6 DRAM CS[0] base 0x00000000 size 256MB DRAM Total size 256MB 16bit width Flash: 0 kB Addresses 8M - 0M are saved for the U-Boot usage. Mem malloc Initialization (8M - 7M): Done NAND:128 MB CPU : Marvell Feroceon (Rev 1) CLOUD ENGINES BOARD: PPV2 Streaming disabled Write allocate disabled USB 0: host mode PEX 0: interface detected no Link. Net: egiga0 [PRIME], egiga1 Hit any key to stop autoboot: 0 CE>> help ? - alias for 'help' base - print or set address offset boot - boot default, i.e., run 'bootcmd' bootd - boot default, i.e., run 'bootcmd' bootext2 dev:boot_part1,boot_part2 addr boot_image linux_dev_name bootm - boot application image from memory bootp - boot image via network using BootP/TFTP protocol bubt - Burn an image on the Boot Nand Flash. chpart - change active partition cmp - memory compare cmpm - Compare Memory cp - memory copy cpumap - Display CPU memory mapping settings. crc32 - checksum calculation date - get/set/reset date & time dclk - Display the MV device CLKs. dhcp - invoke DHCP client to obtain IP/boot params diskboot- boot from IDE device echo - echo args to console eeprom - EEPROM sub-system erase - erase FLASH memory ext2load- load binary file from a Ext2 filesystem ext2ls - list files in a directory (default /) fi - Find value in the memory. flinfo - print FLASH memory information fsinfo - print information about filesystems fsload - load binary file from a filesystem image g - start application at cached address 'addr'(default addr 0x40000) go - start application at address 'addr' help - print online help icrc32 - checksum calculation ide - IDE sub-system iloop - infinite loop on address range imd - i2c memory display imm[.b, .s, .w, .l] - i2c memory modify (auto-incrementing) imw - memory write (fill) inm - memory modify (constant address) iprobe - probe to discover valid I2C chip addresses ir - reading and changing MV internal register values. loop - infinite loop on address range ls - list files in a directory (default /) map - Diasplay address decode windows md - memory display me - PCI master enable mm - memory modify (auto-incrementing) mp - map PCI BAR mtdparts- define flash/nand partitions mtest - simple RAM test mv_diag - perform board diagnostics mw - memory write (fill) nand - NAND sub-system nboot - boot from NAND device nbubt - Burn a boot loader image on the Boot Nand Flash. nm - memory modify (constant address) pci - list and access PCI Configuration Space phyRead - Read PCI-E Phy register pciePhyWrite - Write PCI-E Phy register phyRead - Read Phy register phyWrite - Write Phy register ping - send ICMP ECHO_REQUEST to network host printenv- print environment variables protect - enable or disable FLASH write protection rarpboot- boot image via network using RARP/TFTP protocol reset - Perform RESET of the CPU resetenv - Return all environment variable to default. run - run commands in an environment variable saveenv - save environment variables to persistent storage se - PCI Slave enable setenv - set environment variables sflash - read, write or erase the external SPI Flash. sg - scanning the PHYs status sp - Scan PCI bus. tftpboot- boot image via network using TFTP protocol version - print monitor version CE>>
|
Re: Attempt to restore Pink Pogoplug e02 to factory corrupt uboot. Where to go from here? July 27, 2013 05:22PM |
Admin Registered: 13 years ago Posts: 18,585 |
Here is Davygravy's thread about how to flash uBoot using serial console and tftp. You can see the steps that he did to pull the image using tftp.
http://forum.doozan.com/read.php?3,6965
At this point, IMO I think this is your safest approach to get it boot back to new uBoot, and then Debian. But if it something goes wrong during this, then JTAG is the only way (if uBoot is all messed up).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
http://forum.doozan.com/read.php?3,6965
At this point, IMO I think this is your safest approach to get it boot back to new uBoot, and then Debian. But if it something goes wrong during this, then JTAG is the only way (if uBoot is all messed up).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
oakley470
Re: Attempt to restore Pink Pogoplug e02 to factory corrupt uboot. Where to go from here? July 28, 2013 08:57PM |
Alright i've started working on this, however i cannot seem to set the server ip address for the server to work. Using the commands
setenv ipaddr ... setenv server ... tftp 0x800000 <filename>I am able to set the pogoplug ip address but the server address always defaults to 169.254.254.252 when the pogo begins to read, which is not an available ip address for my tftp server. I have the pogo plugged directly into the pc right now via ethernet so i can still serial into it, i was able to make the tftp server work before using these commands, not sure why it's not letting me change the server ip now, any idea?
|
Re: Attempt to restore Pink Pogoplug e02 to factory corrupt uboot. Where to go from here? July 28, 2013 09:10PM |
Admin Registered: 13 years ago Posts: 18,585 |
@oakley470,
The server ip should be name:
setenv serverip ...
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> setenv ipaddr ... > setenv server ... > tftp 0x800000 <filename> >
The server ip should be name:
setenv serverip ...
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Oakley470
Re: Attempt to restore Pink Pogoplug e02 to factory corrupt uboot. Where to go from here? July 29, 2013 03:28PM |
Interesting, even after fixing that command issue it still will not set the correct server ip
Hit any key to stop autoboot: 0 CE>> setenv ipaddr 169.254.209.185 CE>> setenv severip 169.254.209.184 CE>> tftpboot 0x800000 uboot.mtd0.kwb-2011.12-pogo_e02-L2Coff Using egiga0 device TFTP from server 169.254.254.252; our IP address is 169.254.209.185 Filename 'uboot.mtd0.kwb-2011.12-pogo_e02-L2Coff'. Load address: 0x800000 Loading: T T T T T T T T T T Retry count exceeded; starting again *** ERROR: `eth1addr' not setAny ideas? i considered running "saveenv" to write the serverip but wasn't sure if that would be a good idea.
|
Re: Attempt to restore Pink Pogoplug e02 to factory corrupt uboot. Where to go from here? July 29, 2013 11:28PM |
Admin Registered: 13 years ago Posts: 18,585 |
I think you have mispelled the variable, should be serverip.
And yes you are right, don't do saveenv until after you can tftp and boot.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 07/29/2013 11:30PM by bodhi.
And yes you are right, don't do saveenv until after you can tftp and boot.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 07/29/2013 11:30PM by bodhi.
|
oakley470
Re: Attempt to restore Pink Pogoplug e02 to factory corrupt uboot. Where to go from here? July 31, 2013 04:00PM |
I guess it'd help if i could spell. Thank you i am booted back into debian now. So i think i have given up on restoring the pogo since the last attempt failed. With my current state of boot am i pretty much just back at the begining of installing linux? So i currently have linux set up as if i followed the regular install process and can begin updating and installing packages?
|
Re: Attempt to restore Pink Pogoplug e02 to factory corrupt uboot. Where to go from here? July 31, 2013 11:43PM |
Admin Registered: 13 years ago Posts: 18,585 |
oakley470 Wrote:
-------------------------------------------------------
> I guess it'd help if i could spell.
:))
Thank you i am
> booted back into debian now. So i think i have
> given up on restoring the pogo since the last
> attempt failed. With my current state of boot am i
> pretty much just back at the begining of
> installing linux?
You can keep using this rootfs.
So i currently have linux set up
> as if i followed the regular install process and
> can begin updating and installing packages?
You can start running apt-get update and then apt-get install <whatever package> .
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> I guess it'd help if i could spell.
:))
Thank you i am
> booted back into debian now. So i think i have
> given up on restoring the pogo since the last
> attempt failed. With my current state of boot am i
> pretty much just back at the begining of
> installing linux?
You can keep using this rootfs.
So i currently have linux set up
> as if i followed the regular install process and
> can begin updating and installing packages?
You can start running apt-get update and then apt-get install <whatever package> .
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Oakley470
Re: Attempt to restore Pink Pogoplug e02 to factory corrupt uboot. Where to go from here? August 01, 2013 11:13PM |
Awesome thank you! I think my final question now is this, i want to use this site http://blog.qnology.com/2013/03/tutorial-pogoplug-e02-with-arch-linux.html as an install guide for everything, however many of the commands will not run. They say command not found, i ran the command you gave me to install pacman and even then it still says command not found. Trying to start from the begining of that guide doesn't work because the drive is in use. That is the guide i used previously and had no trouble with anything until i got to re-enabling the pogoplug services, thanks in advance.
|
Re: Attempt to restore Pink Pogoplug e02 to factory corrupt uboot. Where to go from here? August 02, 2013 12:46AM |
Admin Registered: 13 years ago Posts: 18,585 |
Oakley,
Arch package management commands are different. Pacman is package manager on Arch, apt or dpkg is Debian package manager. For installation purpose, that guide can not be used as is on Debian.
So if you want to follow that guide, you will have to rework it to use Debian dialect. For example,
pacman -Syu samba
in Debian it is:
apt-get install samba
so on so forth.
However, pure Linus commands are the same, such as:
mkswap /media/usb/swapfile.img
I'm not sure if I've answered your question? is that what you're looking for, or do you want to install Arch?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Arch package management commands are different. Pacman is package manager on Arch, apt or dpkg is Debian package manager. For installation purpose, that guide can not be used as is on Debian.
So if you want to follow that guide, you will have to rework it to use Debian dialect. For example,
pacman -Syu samba
in Debian it is:
apt-get install samba
so on so forth.
However, pure Linus commands are the same, such as:
mkswap /media/usb/swapfile.img
I'm not sure if I've answered your question? is that what you're looking for, or do you want to install Arch?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
oakley470
Re: Attempt to restore Pink Pogoplug e02 to factory corrupt uboot. Where to go from here? August 02, 2013 07:49AM |
Ohhh, ok I had thought any linux package just used the same commands. Thanks you did answer my question, I'll see how it goes to modify the commands. In the event I just decide to install arch and follow that guide I would have to put in a second flash drive and modify the mount point from sda to sdb and everything should work correct? Or would there be a way to write arch onto the drive that currently is using debian?
|
Re: Attempt to restore Pink Pogoplug e02 to factory corrupt uboot. Where to go from here? August 02, 2013 04:01PM |
Admin Registered: 13 years ago Posts: 18,585 |
oakley470 Wrote:
-------------------------------------------------------
> Ohhh, ok I had thought any linux package just used
> the same commands. Thanks you did answer my
> question, I'll see how it goes to modify
> the commands. In the event I just decide to
> install arch and follow that guide I would have to
> put in a second flash drive and modify the mount
> point from sda to sdb and everything should work
> correct? Or would there be a way to write arch
> onto the drive that currently is using debian?
If you want to install Arch, then follow the guide on Arch site to put Arch rootfs on another USB stick. No, they can not be mixed. If you want to use Debian then keep using the current rootfs stick, and find comparable instruction for Debian.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> Ohhh, ok I had thought any linux package just used
> the same commands. Thanks you did answer my
> question, I'll see how it goes to modify
> the commands. In the event I just decide to
> install arch and follow that guide I would have to
> put in a second flash drive and modify the mount
> point from sda to sdb and everything should work
> correct? Or would there be a way to write arch
> onto the drive that currently is using debian?
If you want to install Arch, then follow the guide on Arch site to put Arch rootfs on another USB stick. No, they can not be mixed. If you want to use Debian then keep using the current rootfs stick, and find comparable instruction for Debian.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Oakley470
Re: Attempt to restore Pink Pogoplug e02 to factory corrupt uboot. Where to go from here? August 03, 2013 07:34PM |
|
Oakley470
Re: Attempt to restore Pink Pogoplug e02 to factory corrupt uboot. Where to go from here? August 05, 2013 04:17PM |
Guess i spoke too soon. So things went fine installing arch to a second flash drive, then during the update process of arch it stopped being able to boot. So reflashing a flash drive to your rootfs, i attempted to boot, no go. So i used Davygravys tftp method to reflash uboot and again reflashing the drive to your rootfs. I get this error
1 bytes read Found bootable drive on usb 0:1 Loading file "/boot/uImage" from usb device 0:1 (usbda1) 2010224 bytes read Loading file "/boot/uInitrd" from usb device 0:1 (usbda1) 6514910 bytes read ## Booting kernel from Legacy Image at 00800000 ... Image Name: Linux-3.9.11-kirkwood-tld-1 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 2010160 Bytes = 1.9 MiB Load Address: 00008000 Entry Point: 00008000 Verifying Checksum ... OK ## Loading init Ramdisk from Legacy Image at 01100000 ... Image Name: initramfs-3.9.11-kirkwood-tld-1 Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 6514846 Bytes = 6.2 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Using machid 0xdd6 from environment 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] Linux version 3.9.11-kirkwood-tld-1 (root@tldDebian) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 PREEMPT Tue Jul 23 01:14:09 PDT 2013 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977 [ 0.000000] CPU: VIVT data cache, VIVT instruction cache [ 0.000000] Machine: Pogoplug E02 [ 0.000000] Memory policy: ECC disabled, Data cache writeback [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024 [ 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: 1024 (order: 0, 4096 bytes) [ 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.000000] __ex_table already sorted, skipping sort [ 0.000000] Memory: 256MB = 256MB total [ 0.000000] Memory: 247568k/247568k available, 14576k reserved, 0K highmem [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) [ 0.000000] vmalloc : 0xd0800000 - 0xff000000 ( 744 MB) [ 0.000000] lowmem : 0xc0000000 - 0xd0000000 ( 256 MB) [ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB) [ 0.000000] .text : 0xc0008000 - 0xc04ef160 (5021 kB) [ 0.000000] .init : 0xc04f0000 - 0xc051764c ( 158 kB) [ 0.000000] .data : 0xc0518000 - 0xc0561bc8 ( 295 kB) [ 0.000000] .bss : 0xc0561bc8 - 0xc05c8f84 ( 413 kB) [ 0.000000] Preemptible hierarchical RCU implementation. [ 0.000000] NR_IRQS:114 [ 0.000000] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474ms [ 0.000000] Console: colour dummy device 80x30 [ 8.340929] Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584) [ 8.430750] pid_max: default: 32768 minimum: 301 [ 8.430854] Security Framework initialized [ 8.430918] Mount-cache hash table entries: 512 [ 8.431522] Initializing cgroup subsys cpuacct [ 8.431542] Initializing cgroup subsys devices [ 8.431553] Initializing cgroup subsys freezer [ 8.431562] Initializing cgroup subsys net_cls [ 8.431570] Initializing cgroup subsys blkio [ 8.431656] CPU: Testing write buffer coherency: ok [ 8.432047] Setting up static identity map for 0xc0398858 - 0xc0398894 [ 8.433950] devtmpfs: initialized [ 8.435738] pinctrl core: initialized pinctrl subsystem [ 8.436079] regulator-dummy: no parameters [ 8.436389] NET: Registered protocol family 16 [ 8.437529] DMA: preallocated 1024 KiB pool for atomic coherent allocations [ 8.438208] Kirkwood: MV88F6281-A0, TCLK=200000000. [ 8.438226] Feroceon L2: Enabling L2 [ 8.438264] Feroceon L2: Cache support initialised. [ 8.441540] bio: create slab <bio-0> at 0 [ 8.441864] vgaarb: loaded [ 8.442435] Switching to clocksource orion_clocksource [ 8.456310] NET: Registered protocol family 2 [ 8.456956] TCP established hash table entries: 2048 (order: 2, 16384 bytes) [ 8.457014] TCP bind hash table entries: 2048 (order: 1, 8192 bytes) [ 8.457045] TCP: Hash tables configured (established 2048 bind 2048) [ 8.457108] TCP: reno registered [ 8.457121] UDP hash table entries: 256 (order: 0, 4096 bytes) [ 8.457143] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) [ 8.457325] NET: Registered protocol family 1 [ 8.457609] RPC: Registered named UNIX socket transport module. [ 8.457620] RPC: Registered udp transport module. [ 8.457626] RPC: Registered tcp transport module. [ 8.457633] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 8.457851] Unpacking initramfs... [ 9.002296] Freeing initrd memory: 6360K [ 9.002389] NetWinder Floating Point Emulator V0.97 (double precision) [ 9.002969] audit: initializing netlink socket (disabled) [ 9.003014] type=2000 audit(0.660:1): initialized [ 9.003839] VFS: Disk quotas dquot_6.5.2 [ 9.003889] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) [ 9.004230] Installing knfsd (copyright (C) 1996 okir@monad.swb.de). [ 9.004390] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc. [ 9.004597] msgmni has been set to 495 [ 9.006430] alg: No test for stdrng (krng) [ 9.006522] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252) [ 9.006532] io scheduler noop registered [ 9.006540] io scheduler deadline registered [ 9.006559] io scheduler cfq registered (default) [ 9.006670] mv_xor mv_xor.0: Marvell shared XOR driver [ 9.042521] mv_xor mv_xor.0: Marvell XOR: ( xor cpy ) [ 9.082515] mv_xor mv_xor.0: Marvell XOR: ( xor fill cpy ) [ 9.082612] mv_xor mv_xor.1: Marvell shared XOR driver [ 9.122510] mv_xor mv_xor.1: Marvell XOR: ( xor cpy ) [ 9.162510] mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy ) [ 9.162753] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled [ 9.183302] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A [ 9.653343] console [ttyS0] enabled [ 9.657699] NAND device: Manufacturer ID: 0xad, Chip ID: 0xf1 (Hynix NAND 128MiB 3,3V 8-bit), 128MiB, page size: 2048, OOB size: 64 [ 9.669605] Scanning device for bad blocks [ 9.780874] 4 cmdlinepart partitions found on MTD device orion_nand [ 9.787185] Creating 4 MTD partitions on "orion_nand": [ 9.792346] 0x000000000000-0x000000100000 : "u-boot" [ 9.797566] 0x000000100000-0x000000500000 : "uImage" [ 9.802766] 0x000000500000-0x000002500000 : "rootfs" [ 9.807994] 0x000002500000-0x000008000000 : "data" [ 9.813392] mousedev: PS/2 mouse device common for all mice [ 10.822561] rtc-mv rtc-mv: internal RTC not ticking [ 10.827555] i2c /dev entries driver [ 10.831152] cpuidle: using governor ladder [ 10.835285] cpuidle: using governor menu [ 10.839386] leds-gpio leds-gpio: pins are not configured from the driver [ 10.846356] drop_monitor: Initializing network drop monitor service [ 10.852953] TCP: cubic registered [ 10.856287] NET: Registered protocol family 17 [ 10.860846] Key type dns_resolver registered [ 10.865546] registered taskstats version 1 [ 10.870468] drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 10.877541] Freeing init memory: 156K Loading, please wait... [ 10.953181] udevd[51]: starting version 175 [ 11.045600] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4 [ 11.093443] usbcore: registered new interface driver usbfs [ 11.099015] usbcore: registered new interface driver hub [ 11.113865] libphy: mv643xx_eth smi: probed [ 11.148165] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:25:31:00:a2:3a [ 11.172845] usbcore: registered new device driver usb [ 11.197054] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 11.232535] orion-ehci orion-ehci.0: Marvell Orion EHCI [ 11.237811] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1 [ 11.285322] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000 [ 11.302512] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00 [ 11.308548] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 11.315395] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 11.322667] usb usb1: Product: Marvell Orion EHCI [ 11.327395] usb usb1: Manufacturer: Linux 3.9.11-kirkwood-tld-1 ehci_hcd [ 11.334141] usb usb1: SerialNumber: orion-ehci.0 [ 11.339689] hub 1-0:1.0: USB hub found [ 11.343527] hub 1-0:1.0: 1 port detected [ 11.662497] usb 1-1: new high-speed USB device number 2 using orion-ehci [ 11.813953] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608 [ 11.820698] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 11.827896] usb 1-1: Product: USB2.0 Hub [ 11.834978] hub 1-1:1.0: USB hub found [ 11.846278] hub 1-1:1.0: 4 ports detected [ 12.132830] usb 1-1.1: new high-speed USB device number 3 using orion-ehci [ 12.245449] usb 1-1.1: New USB device found, idVendor=0951, idProduct=1653 [ 12.252372] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 12.259740] usb 1-1.1: Product: DT 100 G2 [ 12.263781] usb 1-1.1: Manufacturer: Kingston [ 12.268161] usb 1-1.1: SerialNumber: 001CC0EC32F6FBA0A5ED23E3 [ 12.294114] SCSI subsystem initialized [ 12.302176] Initializing USB Mass Storage driver... [ 12.307555] scsi0 : usb-storage 1-1.1:1.0 [ 12.313135] usbcore: registered new interface driver usb-storage [ 12.319170] USB Mass Storage support registered. [ 13.375681] scsi 0:0:0:0: Direct-Access Kingston DT 100 G2 1.00 PQ: 0 ANSI: 2 [ 13.399140] sd 0:0:0:0: [sda] 31324160 512-byte logical blocks: (16.0 GB/14.9 GiB) [ 13.407865] sd 0:0:0:0: [sda] Write Protect is off [ 13.413229] sd 0:0:0:0: [sda] No Caching mode page present [ 13.418752] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 13.428476] sd 0:0:0:0: [sda] No Caching mode page present [ 13.434048] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 13.441106] sda: sda1 [ 13.446102] sd 0:0:0:0: [sda] No Caching mode page present [ 13.451635] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 13.457826] sd 0:0:0:0: [sda] Attached SCSI removable disk [ 13.473594] 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 [ 21.505392] uhci_hcd: USB Universal Host Controller Interface driver [ 21.518661] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 21.534674] hidraw: raw HID events driver (C) Jiri Kosina [ 21.542431] usbcore: registered new interface driver usbhid [ 21.548174] usbhid: USB HID core driver BusyBox v1.20.2 (Debian 1:1.20.0-7) built-in shell (ash) Enter 'help' for a list of built-in commands. /bin/sh: can't access tty; job control turned off (initramfs)I officially don't know what to do from here? I don't know enough linux commands to understand what is happening. Thank you for your help, at this point my pogoplug has really become a way for me to learn debian code haha!
