Re: Pogoplug V4 - uBoot with Debian
October 08, 2020 05:59PM
Nirmal,

Yes, stock FW on NAND was corrupted.

You need to boot with Debian USB rootfs.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Pogoplug V4 - uBoot with Debian
October 10, 2020 04:09AM
ok Bodhi,


I was able to Boot now using old 4.4.0 Debian and This is the message when i ran the dmesg

[ 1.639248] Scanning device for bad blocks
[ 1.781270] Bad eraseblock 1290 at 0x00000a140000

Should i upgrade to Latest Uboot ?



Edited 1 time(s). Last edit at 10/10/2020 05:32AM by Nirmal_Kumar.
Re: Pogoplug V4 - uBoot with Debian
October 10, 2020 04:18PM
Nirmal,

>
> [ 1.639248] Scanning device for bad blocks
> [ 1.781270] Bad eraseblock 1290 at
> 0x00000a140000
>
> Should i upgrade to Latest Uboot ?

Bad eraseblock 1290 is way out in flash, so it is safe to update u-boot.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Pogoplug V4 - uBoot with Debian
October 18, 2020 02:57AM
Thank you Bodhi.

I went head and upgraded uBoot. Shall i retain the old Debian or should i need to upgrade Debian also?

Its stuck in Starting Kernel..

U-Boot 2017.07-tld-1 (Oct 24 2017 - 22:32:36 -0700)
Seagate FreeAgent DockStar
gcc (Debian 6.3.0-18) 6.3.0 20170516
GNU ld (GNU Binutils for Debian) 2.28
Hit any key to stop autoboot:  9


Scan device usb
device usb 0:1
1 bytes read in 631 ms (0 Bytes/s)
Found bootable drive on usb 0
loading uImage ...
3166793 bytes read in 898 ms (3.4 MiB/s)
loading uInitrd ...
7179935 bytes read in 990 ms (6.9 MiB/s)
loading DTB /boot/dts/kirkwood-dockstar.dtb ...
10398 bytes read in 769 ms (12.7 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.4.0-kirkwood-tld-1
   Created:      2020-10-10   9:43:42 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3166729 Bytes = 3 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-4.4.0-kirkwood-tld-1
   Created:      2016-02-19   7:33:04 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7179871 Bytes = 6.8 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01c00000
   Booting using the fdt blob at 0x1c00000


Starting kernel ...




 


DockStar> printenv
printenv
arcNumber=2998
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi; sleep 3
bootdelay=10
bootdev=usb
device=0:1
devices=usb ide mmc
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-dockstar.dtb
ethact=egiga0
ethaddr=52:3b:20:9c:11:51
if_netconsole=ping $serverip
ipaddr=192.168.1.8
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_dtb_addr=0x1c00000
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_initrd_addr=0x1100000
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
load_uimage_addr=0x800000
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
nc_ready=1
ncip=192.168.1.18
partition=nand0,2
preboot=run preboot_nc
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start";  setenv scan_ide "ide reset";  setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
serverip=192.168.1.18
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=nc
stdin=nc
stdout=nc
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=echo Initializing devices...; setenv init_usb "usb start";  setenv init_ide "ide reset";  setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices; do for disknum in $disks; do if test $uenv_loaded -eq 0; then setenv device_type $devtype; setenv disk_number $disknum; run uenv_read; fi; done; done;
uenv_read=echo Loading envs from $device_type $disk_number...; if load $device_type  $disk_number:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; echo ... envs loaded; fi
usb_ready_retry=15
Re: Pogoplug V4 - uBoot with Debian
October 18, 2020 03:14AM
I also replaced the uImage.orig to uImage
Re: Pogoplug V4 - uBoot with Debian
October 18, 2020 03:36PM
Nirmal,

When you boot with netconsole, the output stops at

Starting kernel ...

So chance is that it already booted into Debian. Now look for a new IP address in your network, or try to ping the host name of the box

ping debian.local

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Pogoplug V4 - uBoot with Debian
October 19, 2020 12:07AM
Yes. Unable to reach the box and i don't see the IP address in the IP Scanner after the Starting Kernel message.

Anyway, I will try the serial console and troubleshoot what going on..



Edited 1 time(s). Last edit at 10/19/2020 10:41AM by Nirmal_Kumar.
Re: Pogoplug V4 - uBoot with Debian
October 19, 2020 09:32PM
Thanks bodhi. The latest 5.2.9 with fresh usb worked well on Dockstar.


Now on the PogoPlug V4 i am getting "EHCI timed out on" which is running uBoot 2017 Sep. I saw searched the forum and i saw you have released patch on Oct 2017 for uboot. But how to boot the debian on this device?

Thanks again for your support.



Edited 2 time(s). Last edit at 10/20/2020 11:56AM by Nirmal_Kumar.
Re: Pogoplug V4 - uBoot with Debian
October 27, 2020 02:01AM
Hello Bodhi,

Can you show some lights on the pogo issue mentioned in the above thread?

Regards
Nirmal
Re: Pogoplug V4 - uBoot with Debian
October 27, 2020 05:13AM
Re: Pogoplug V4 - uBoot with Debian
October 27, 2020 05:55AM
Hi Bodhi,

I mean this one. https://forum.doozan.com/read.php?3,33656,110124#msg-110124

PogoPlug V4 i am getting "EHCI timed out on" which is running uBoot 2017 Sep. I saw searched the forum and i saw you have released patch on Oct 2017 for uboot. But how to boot the debian on this device?

-- Nirmal
Re: Pogoplug V4 - uBoot with Debian
October 27, 2020 04:25PM
Nirmal,

>But how to boot the debian on this
> device?

It is the same as other boxes. There is no difference.

When you see the "EHCI timed out..." error, it is because the patch did not work on this USB drive. You can just ignore it if the booting works OK. If it interfered with the booting process, then the only remedy is to use a different USB drive.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Re: Pogoplug V4 - uBoot with Debian
November 01, 2020 12:51AM
Thank you Bodhi.

I changed the USB and it working well now. Thanks again. Hope the uboot with 2017 - Sep build is enough for me. (Instead of Oct update)

Now all my devices are running 2017 version of UBoot.

Regards
Nirmal
Re: Pogoplug V4 - uBoot with Debian
November 13, 2020 10:56PM
Hello Bodhi,

I see a strange issue with the PogoPlug V4 (Running Debian 5.7)

I can see the device on the Network and in the IP Scanner ( 192.168.1.11). But i couldn't SSH to the device. When i checked the device open ports in the IP scanner, i can see only 2 Ports. (rpcbind 111 and nfs 2049)

Any insights on this strange thing and i have not see this before.?

Regards
Nirmal
Re: Pogoplug V4 - uBoot with Debian
November 14, 2020 04:56PM
> I see a strange issue with the PogoPlug V4
> (Running Debian 5.7)

Did you mean kernel 5.7?

In any case, you could be more specific about your system:

uname -a
cat /proc/debian/version  # or
cat /etc/os-release

Probably the only way to see why port 22 is not open is to reboot, or connect serial console.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
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: