Welcome! Log In Create A New Profile

Advanced

Rescue System Pogo V3 - Using Stock Pogo V3 OS

Posted by bodhi 
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS
March 05, 2016 06:03PM
hachigo,

The envs look fine. You can create the 3.17 Debian rootfs without changing anything (just tar it). Follow the instruction (extract it to a single partition type Ext3, as root user, and label it rootfs). That's it, no further change (don't embed the DTB).

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS
March 05, 2016 06:39PM
Hi bodhi,

Hmm. What you suggested is what I did the the very first time, but it never booted. I just tried again what you suggested and still nothing.

Just to be sure I'm not screwing anything up here's what I did.

On my ubuntu machine, I erased and reformatted my sata harddrive with fdisk. Created one 4GB primary partition. Then formatted to ext3 with the label "rootfs" using this command
mke2fs -L rootfs -j /dev/sdb1

I then un-tar the 3.17 Debian rootfs into that partition, issued a sync command. Powered off my PC, removed the sata drive and plugged it into the pogoplug pro and powered on the pogoplug pro.

What does " ## Error: "dt_bootcmd_usb" not defined" mean? I'm not sure what I'm doing wrong. Also I didn't mean to steal the thread. Should I post in another post?

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

PLLA Set


U-Boot 2015.10-tld-1 (Nov 21 2015 - 01:17:59 -0800)
OXNAS OX820

DRAM:  128 MiB
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   dwmac.40400000
Hit any key to stop autoboot:  0 
## Error: "dt_bootcmd_usb" not defined

Loading from nand0, offset 0x200000
   Image Name:   Linux-2.6.31.6_SMP_820
   Created:      2010-11-30  20:05:12 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2260628 Bytes = 2.2 MiB
   Load Address: 60008000
   Entry Point:  60008000
## Booting kernel from Legacy Image at 60500000 ...
   Image Name:   Linux-2.6.31.6_SMP_820
   Created:      2010-11-30  20:05:12 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2260628 Bytes = 2.2 MiB
   Load Address: 60008000
   Entry Point:  60008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK

Starting kernel ...

Uncompressing Linux................................................................................................................................... done, booting the kernel.
[    0.000000] Linux version 2.6.31.6_SMP_820 (bdietrich@brad-ux) (gcc version 4.4.1 (Sourcery G++ Lite 2009q3-67) ) #71 SMP Tue Nov 30 12:05:09 PST 2010
[    0.000000] CPU: ARMv6-compatible processor [410fb025] revision 5 (ARMv7), cr=00c5387f
[    0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[    0.000000] Machine: Oxsemi NAS
[    0.000000] 1 memory region
[    0.000000] Ignoring unrecognised tag 0x00000000
[    0.000000] Memory policy: ECC disabled, Data cache writealloc
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: root=ubi0:rootfs ubi.mtd=2,512 rootfstype=ubifs console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 mem=128M
[    0.000000] PID hash table entries: 512 (order: 9, 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: 128MB = 128MB total
[    0.000000] Memory: 125468KB available (3724K code, 275K data, 124K init, 0K highmem)
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS:96
[    0.000000] OX820_RPS_init_irq: interrupts 64 to 96
[    0.010000] Console: colour dummy device 80x30
[    0.010000] console [ttyS0] enabled
[    0.020000] Calibrating delay loop... 339.14 BogoMIPS (lpj=1695744)
[    0.240000] Security Framework initialized
[    0.240000] Mount-cache hash table entries: 512
[    0.250000] CPU: Testing write buffer coherency: ok
[    0.250000] Calibrating local timer... 425.50MHz.
[    0.320000] CPU1: Booted secondary processor
[    0.420000] Calibrating delay loop... 339.14 BogoMIPS (lpj=1695744)
[    0.630000] Brought up 2 CPUs
[    0.640000] SMP: Total of 2 processors activated (678.29 BogoMIPS).
[    0.650000] NET: Registered protocol family 16
[    0.650000] Number of DMA channels = 4, version = 4
[    0.660000] Reserving a DMA channel for DirectRAID
[    0.660000] Allocating 389 SRAM generic DMA descriptors
[    1.170000] PCIeA version/deviceID 082510b5
[    1.170000] PCIeB version/deviceID 082510b5
[    4.200000] ox820_pci_preinit() PCIEB link up timeout (00001814)
[    4.200000] ox820_pcie_setup_resources() Enabling PCIe Pre-Emphasis
[    4.210000] ox820_pciea_setup_resources() resource c781b2c0
[    4.210000] ox820_pciea_setup_resources()    io:      0x4be00000 - 0x4befffff
[    4.220000] ox820_pciea_setup_resources()    non-pre: 0x48000000 - 0x49ffffff
[    4.230000] ox820_pciea_setup_resources()    pre:     0x4a000000 - 0x4bdfffff
[    4.230000] PCI: bus0: Fast back to back transfers disabled
[    4.240000] PCI: bus1: Fast back to back transfers enabled
[    4.250000] bio: create slab <bio-0> at 0
[    4.260000] SCSI subsystem initialized
[    4.290000] NET: Registered protocol family 2
[    4.290000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[    4.300000] Switched to NOHz mode on CPU #0
[    4.300000] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
[    4.300000] Switched to NOHz mode on CPU #1
[    4.310000] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
[    4.320000] TCP: Hash tables configured (established 4096 bind 4096)
[    4.320000] TCP reno registered
[    4.330000] NET: Registered protocol family 1
[    4.330000] Create fragment cache
[    4.340000] fuse init (API version 7.12)
[    4.340000] msgmni has been set to 245
[    4.350000] alg: No test for stdrng (krng)
[    4.350000] io scheduler noop registered
[    4.360000] io scheduler anticipatory registered
[    4.360000] io scheduler deadline registered
[    4.370000] io scheduler cfq registered (default)
[    4.390000] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    4.390000] serial8250: ttyS0 at MMIO 0x44200000 (irq = 55) is a 16550A
[    4.410000] brd: module loaded
[    4.420000] loop: module loaded
[    4.420000] ox820sata: OX820 sata core.
[    4.420000] scsi0 : oxnassata
[    4.430000] scsi1 : oxnassata
[    4.430000] ata1: SATA max UDMA/133 irq 50
[    4.440000] ata2: SATA max UDMA/133 irq 50
[    4.440000] ox820sata: reseting SATA core
[    4.960000] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    4.960000] ata1.00: ATA-8: FUJITSU MHY2160BH, 0085000B, max UDMA/100
[    4.970000] ata1.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 0/32)
[    4.980000] ata1.00: configured for UDMA/100
[    4.980000] ox820sata: reseting SATA core
[    5.690000] ata2: SATA link down (SStatus 0 SControl 300)
[    5.690000] scsi 0:0:0:0: Direct-Access     ATA      FUJITSU MHY2160B 0085 PQ: 0 ANSI: 5
[    5.700000] sd 0:0:0:0: [sda] 312581808 512-byte logical blocks: (160 GB/149 GiB)
[    5.710000] sd 0:0:0:0: [sda] Write Protect is off
[    5.710000] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    5.720000] tun: Universal TUN/TAP device driver, 1.6
[    5.720000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[    5.720000] NAND: Page read time 40ms
[    5.720000] NAND device: Manufacturer ID: 0xad, Chip ID: 0xf1 (Hynix NAND 128MiB 3,3V 8-bit)
[    5.720000] Scanning device for bad blocks
[    5.780000] Creating 2 MTD partitions on "NAND 128MiB 3,3V 8-bit":
[    5.790000] 0x000000000000-0x000000e00000 : "boot"
[    5.790000]  sda:
[    5.800000] 0x000000e00000-0x000008000000 : "rootfs"
[    5.800000] UBI: attaching mtd2 to ubi0
[    5.810000] UBI: physical eraseblock size:   131072 bytes (128 KiB)
[    5.810000] UBI: logical eraseblock size:    129024 bytes
[    5.820000] UBI: smallest flash I/O unit:    2048
[    5.820000] UBI: sub-page size:              512
[    5.830000] UBI: VID header offset:          512 (aligned 512)
[    5.830000] UBI: data offset:                2048
[    6.010000]  sda1
[    6.190000] UBI: attached mtd2 to ubi0
[    6.190000] UBI: MTD device name:            "rootfs"
[    6.200000] UBI: MTD device size:            114 MiB
[    6.200000] UBI: number of good PEBs:        912
[    6.210000] UBI: number of bad PEBs:         0
[    6.210000] UBI: max. allowed volumes:       128
[    6.210000] UBI: wear-leveling threshold:    4096
[    6.220000] UBI: number of internal volumes: 1
[    6.220000] UBI: number of user volumes:     1
[    6.230000] UBI: available PEBs:             0
[    6.230000] UBI: total number of reserved PEBs: 912
[    6.240000] UBI: number of PEBs reserved for bad PEB handling: 9
[    6.240000] UBI: max/mean erase counter: 2/0
[    6.250000] UBI: image sequence number: 0
[    6.250000] UBI: background thread "ubi_bgt0d" started, PID 285
[    6.260000] mice: PS/2 mouse device common for all mice
[    6.260000] TCP cubic registered
[    6.270000] NET: Registered protocol family 10
[    6.270000] NET: Registered protocol family 17
[    6.280000] RPC: Registered udp transport module.
[    6.280000] sd 0:0:0:0: [sda] Attached SCSI disk
[    6.290000] RPC: Registered tcp transport module.
[    6.390000] UBIFS: recovery needed
[    6.520000] UBIFS: recovery completed
[    6.530000] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[    6.530000] UBIFS: file system size:   114573312 bytes (111888 KiB, 109 MiB, 888 LEBs)
[    6.540000] UBIFS: journal size:       9033728 bytes (8822 KiB, 8 MiB, 71 LEBs)
[    6.550000] UBIFS: media format:       w4/r0 (latest is w4/r0)
[    6.550000] UBIFS: default compressor: zlib
[    6.560000] UBIFS: reserved for root:  0 bytes (0 KiB)
[    6.560000] VFS: Mounted root (ubifs filesystem) on device 0:10.
[    6.570000] Freeing init memory: 124K
Too many bit errors @ 0xa0000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa0800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa1000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa1800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa2000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa2800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa3000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa3800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa4000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa4800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa5000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa5800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa6000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa6800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa7000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa7800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa8000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa8800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa9000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xa9800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xaa000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xaa800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xab000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xab800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xac000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xac800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xad000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xad800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xae000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xae800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xaf000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xaf800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb0000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb0800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb1000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb1800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb2000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb2800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb3000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb3800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb4000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb4800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb5000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb5800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb6000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb6800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb7000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb7800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb8000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb8800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb9000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xb9800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xba000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xba800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xbb000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xbb800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xbc000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xbc800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xbd000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xbd800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xbe000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xbe800 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xbf000 -- Can't correct!
PAGE DATA:
OOB:
Too many bit errors @ 0xbf800 -- Can't correct!
PAGE DATA:
OOB:
   -- Invalid CRC32 on parameters: 0x6e206369 != 0x27033e1f
/etc/init.d/rcS: /tmp/ethaddr: line 1: 00000380:: not found
/etc/init.d/rcS: /tmp/ethaddr: line 3: syntax error: EOF in backquote substitution



-Hachigo



Edited 1 time(s). Last edit at 03/05/2016 06:45PM by hachigo.
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS
March 05, 2016 06:56PM
hachigo,

> What does " ## Error: "dt_bootcmd_usb" not
> defined" mean? I'm not sure what I'm doing wrong.
> Also I didn't mean to steal the thread. Should I
> post in another post?

Ah! I see, I've missed that :). This is what was wrong.

In serial console:

setenv bootcmd 'run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_stock; reset'

and then
boot

After booting into Debian, to make it permanent:
fw_setenv bootcmd 'run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_stock; reset'

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS
March 05, 2016 07:06PM
hi bodhi,

Success!!! thank you so much! This almost makes up for the exam I bombed this past Friday...

How did you learn how to do all this stuff? lol. I gotta a lot of learning to do.

If you don't mind, I have another question that got me into this mess of trying to boot from sata in the first place.

I was wondering if there was a Rescue System like Rescue v.2.8.2 for the pro. My pogo pro doesn't boot into the stock pogo OS anymore. Is there a replacement that has more features than the stock I could just flash over? Thanks again.

-hachigo
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS
March 05, 2016 07:24PM
hachigo,

> I was wondering if there was a Rescue System like
> Rescue v.2.8.2 for the pro. My pogo pro doesn't
> boot into the stock pogo OS anymore
. Is there a
> replacement that has more features than the stock
> I could just flash over? Thanks again.

It did. That was the purpose of this thread. You see a lot of errors during boot, but it did not prevent the stock kernel running.

[    0.000000] Linux version 2.6.31.6_SMP_820 (bdietrich@brad-ux) (gcc version 4.4.1 (Sourcery G++ Lite 2009q3-67) ) #71 SMP Tue Nov 30 12:05:09 PST 2010
[    0.000000] CPU: ARMv6-compatible processor [410fb025] revision 5 (ARMv7), cr=00c5387f
[    0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[    0.000000] Machine: Oxsemi NAS

Shutdown, pull the USB drive out, power up, watch the stock kernel booting, and you should see the stock OS command line prompt like you did before.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS
March 05, 2016 07:35PM
bodhi,

Oh ok. Before I was able to ssh into it and also use the netconsole, but now I can't. I guess now I can only get into the stock OS with serial cable?

I was also wondering if installing debian to the nand is still viable option. I came across this https://github.com/ingmar-k/Pogoplug_V3_Emdebian_Debian while browsing other threads on this site and google.

I'd like to be able to ssh into my bare pogoplug pro with no USB or harddrives attached.

thanks,
hachigo
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS
March 05, 2016 07:47PM
hachigo,

> Oh ok. Before I was able to ssh into it and also
> use the netconsole, but now I can't. I guess now I
> can only get into the stock OS with serial cable?
>

Not true. It only means that your setup has some errors. Check the error about ethaddr above at the end of your log. If the installation in the 1st post was OK, then you can ssh into Pogo OS. Again, that's the goal, you must be able to ssh into it.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS
March 05, 2016 08:13PM
bodhi,

Ok I will go through my uBoot envs again. I just realized I didn't copy my working env settings before I formatted my USB drive. I hope Chessplayer's env settings will work for me too. Thanks again for your help.

-hachigo
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS
April 03, 2016 02:03PM
I have installed the rescue system on my Pogoplug v3 and it works as advertised. But in rescue mode, the ethernet mac address is set to 00:30:E0:00:00:00 which is different from the mac address on the foot. Not a big problem, but it's the same on another v3 and if they were both in rescue mode, there would be a mac conflict.

Is there a way to set the rescue ethernet mac address to the address on the foot of the device? I have it set correctly in printenv. Thanks.
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS
April 03, 2016 04:12PM
I figured it out.. It's set using the mac_adr variable under bootcmd_stock.
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS
April 03, 2016 04:25PM
dexter Wrote:
-------------------------------------------------------
> I figured it out.. It's set using the mac_adr
> variable under bootcmd_stock.

Thanks dexter, did you change the bootcmd_stock to set that?

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS
April 03, 2016 11:12PM
>> I figured it out.. It's set using the mac_adr
>> variable under bootcmd_stock.

>Thanks dexter, did you change the bootcmd_stock to set that?

>-bodhi

Yes, I did change bootcmd_stock to reflect the correct mac address, but it had no effect after a reboot. The HWaddr for eth0 reported by ifconfig is still 00:30:E0:00:00:00 which is almost but not exactly the same as the mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 in the original bootcmd_stock earlier in this thread.

The "wrong" mac_adr does match the bootargs line in blparam.txt saved from before the Uboot upgrade:
bootargs=root=ubi0:rootfs ubi.mtd=2,512 rootfstype=ubifs console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 mem=128M poweroutage=yes

I have tried altering this part of /etc/init.d/rcS

if [ "x$ethaddr" != "x" ]; then
ifconfig eth0 hw ether $ethaddr
else
if [ "x$ceethhwaddr" != "x" ]; then
ifconfig eth0 hw ether $ceethhwaddr

but no joy. Could this be modified to fix?
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS
April 07, 2016 02:18PM
dexter Wrote:
-------------------------------------------------------
> >> I figured it out.. It's set using the mac_adr
> >> variable under bootcmd_stock.
>
> >Thanks dexter, did you change the bootcmd_stock
> to set that?
>
> >-bodhi
>
> Yes, I did change bootcmd_stock to reflect the
> correct mac address, but it had no effect after a
> reboot. The HWaddr for eth0 reported by ifconfig
> is still 00:30:E0:00:00:00 which is almost but not
> exactly the same as the
> mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 in the
> original bootcmd_stock earlier in this thread.
>
> The "wrong" mac_adr does match the bootargs line
> in blparam.txt saved from before the Uboot
> upgrade:
> bootargs=root=ubi0:rootfs ubi.mtd=2,512
> rootfstype=ubifs console=ttyS0,115200 elevator=cfq
> mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 mem=128M
> poweroutage=yes
>
> I have tried altering this part of
> /etc/init.d/rcS
>
> if [ "x$ethaddr" != "x" ]; then
> ifconfig eth0 hw ether $ethaddr
> else
> if [ "x$ceethhwaddr" != "x" ]; then
> ifconfig eth0 hw ether $ceethhwaddr
>
> but no joy. Could this be modified to fix?

I'm not sure I remember how with stock OS.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS
May 13, 2016 05:21AM
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS
February 04, 2017 10:03PM
I've followed these instructions to create a rescue system on both of my PogoPlug Pros -- works great!

I'm going to start fiddling with a couple PogoPlug Mobiles next week and I see that the rescue systems for Kirkwood involve replacing the stock OS. Is there a reason for that? I'm sure it's fun to do, and I get that. But is there any reason I couldn't use a similar approach to the Oxnas/PogoV3?

I figure it will work as long as the Kirkwood u-boot supports the same commands for scanning external storage and defaulting back to booting NVRAM. I'll do some more reading on the different rescue systems offered in the forum, maybe they're so cool I won't be able to resist using them ;)
Re: Rescue System Pogo V3 - Using Stock Pogo V3 OS
February 07, 2017 05:42AM
GeekSmith,

> I'm going to start fiddling with a couple PogoPlug
> Mobiles next week and I see that the rescue system
> s for Kirkwood involve replacing the stock OS. Is
> there a reason for that? I'm sure it's fun to do,
> and I get that. But is there any reason I couldn't
> use a similar approach to the Oxnas/PogoV3?

Yes, you could. The reason I did not bother creating envs setup for Kirkwood because Jeff's Rescue System V2 works for the small Kirkwood plugs already (Pogo V4, Mobile, E02, Dockstar, GoFlex Home/Net). And davygravy's V2.8 also supposed to work the same way.

And later, bobafetthotmail also created a OpenWrt rescue system (beta version).

In fact, I've also built a new rescue system with a modern kernel as an exercise, but did not release it.

-bodhi
===========================
Wiki
latest Kirkwood kernel builds and rootfs
latest u-boot-kirkwood builds
latest Oxnas kernel builds and rootfs
latest u-boot-oxnas builds
latest MVEBU Armada kernel builds and rootfs
U-Boot & Kernel Booting process
bodhi's u-boot GitHub
bodhi's corner
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: