Pogoplug Series 4 - Want to boot from Sata HDD

Hi Bodhi, I'm booting the system off an USB stick and I'd like to change it to a SATA 2.5inch hdd instead. Do I need to change any settings anywhere? Now my current fw_printenv looks like following:

root@debian:~# fw_printenv 
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=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
bootdev=usb
device=0:1
devices=usb ide mmc
disks=0 1 2 3
ethact=egiga0
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb_addr=0x1c00000
load_initrd_addr=0x1100000
load_uimage_addr=0x800000
mainlineLinux=yes
mtdids=nand0=orion_nand
partition=nand0,2
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
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
stderr=serial
stdin=serial
stdout=serial
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_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 0; do run uenv_read_disk; done; done;
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
usb_ready_retry=15
arcNumber=3960
machid=f78
mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
ethaddr=00:25:31:05:2e:99
dtb_file=/boot/dts/kirkwood-pogoplug_v4.dtb
ipaddr=192.168.0.112
load_dtb=ext2load usb 0:1 0x1c00000 /boot/dts/kirkwood-pogoplug_v4.dtb
load_initrd=ext2load usb 0:1 0x1100000 /boot/uInitrd
load_uimage=ext2load usb 0:1 0x800000 /boot/uImage
usb_boot=run load_dtb; run load_uimage; if run load_initrd; then bootm 0x800000 0x1100000 0x1c00000; else bootm 0x800000 - 0x1c00000; fi
root@debian:~#

What I already tried:

1. I connected a new 80GB HDD to the pogoplug v4,
2. Made the entire partition as ext4,
3. Labeled the hdd as 'rootfs' and after that,
4. Extracted Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar files inside it.
5. Shutdown the system. Removed the flash drive,
6. Power the pogoplug back on with only sata hdd connected.

But the red light keeps on flashing. What's wrong?

Thanks,

Tushar



Edited 1 time(s). Last edit at 09/14/2019 08:24AM by Tushar.

Tushar,

With the current envs in the new u-boot, there is no need for extra setup.

1. Did you do 4 as root user?

2. When you format the HDD with Ext4, with the intention to use as the booting drive. You need to force the formatting to complete immediately. The option is

lazy_itable_init=0

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------
> Tushar,
>
> With the current envs in the new u-boot, there is
> no need for extra setup.
>
> 1. Did you do 4 as root user?
>
> 2. When you format the HDD with Ext4, with the
> intention to use as the booting drive. You
> need to force the formatting to complete
> immediately. The option is
>
> lazy_itable_init=0

Bodhi, Thanks for replying. Yes I did everything as 'root' while I was log right into my pogoplug. Note that I didn't have another linux machine so I inserted the SATA HDD on top of pogoplug v4's SATA port and performed the operation. Also as you have suggested, on 2nd try I did 'lazy_itable_init=0' - still no luck if I try to boot the system up without the USB key inserted.

Here's what happening: After rootfs extraction (as root) on the HDD, if I shutdown the system and take out USB stick (while HDD keep mounted on the SATA port), the system doesn't boot at all. the red light keeps on flashing.

BUT, if I keep the USB key inserted and restart the system, pogoplug v4 comes online and let me ssh back in and I see the system running off the SATA HDD . I find it strange that I have to keep the USB key connected all the time? I also noticed (at the time when Pogoplug runs off SATA HDD, that the USB key was not mounted automatically - so why do I need the USB key mounted all the time?

(as a root, I did the following)

parted /dev/sda mklabel gpt
parted -a opt /dev/sda mkpart primary ext4 0% 100%
mkfs.ext4 -L rootfs /dev/sda1 -E lazy_itable_init=0
cd /media/sda1 
tar -xjvf Debian-4.12.1-kirkwood-tld-1-rootfs-bodhi.tar.bz2

1. is there any way I can run Pogoplug v4 without USB key and only with the SATA HDD?

2. Another interesting fact I found that the file /etc/fstab has ext3 entry.

Thanks again.



Edited 2 time(s). Last edit at 09/15/2019 07:14AM by Tushar.

Tushar,

There should be no problem with booting from the HDD rootfs as the only disk drive in the system.

Quote

Here's what happening: After rootfs extraction (as root) on the HDD, if I shutdown the system and take out USB stick (while HDD keep mounted on the SATA port), the system doesn't boot at all. the red light keeps on flashing.

The red light flashing means uboot did not find the kernel file uImage. So it did not go very far.

You don't have serial console so the only way to troubleshoot is either:

1. set up netconsole so that we can see u-boot booting activities.

Quote
https://forum.doozan.com/read.php?3,12381

10. Set up netconsole. It's important to set up neconsole if you don't already have serial console connected. If you have serial console, don't set up netconsole at this moment, because it will interfere with serial console.

or

2. Look closely at the HDD formatting and file system. You could try to reformat it in MBR using fdisk. And use Ext3. That way you know that it works before switching to Ext4. The HDD is small so there is no need to use GPT.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

bodhi Wrote:
-------------------------------------------------------
> Tushar,
>
> 1. set up netconsole so that we can see u-boot
> booting activities.
>
> or
>
> 2. Look closely at the HDD formatting and file
> system. You could try to reformat it in MBR using
> fdisk. And use Ext3. That way you know that it
> works before switching to Ext4. The HDD is small
> so there is no need to use GPT.

Hi Bodhi, I followed your suggestions and reformatted HDD using MBR with fdisk + used Ext3. Still no luck. Below is netconsole output:

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:34:01 -0700)
Pogoplug V4
gcc (Debian 6.3.0-18) 6.3.0 20170516
GNU ld (GNU Binutils for Debian) 2.28
Hit any key to stop autoboot:  0 
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Reset IDE: Bus 0: OK Bus 1: not available  
  Device 0: Model: FUJITSU MHW2080BJ G2 Firm: 0085001A Ser#: K30TT812D539
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 76319.0 MB = 74.5 GB (156301488 x 512)
Card did not respond to voltage select!
mmc_init: -95, time 11
## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0
loading envs from usb 0 ...
** Bad device usb 0 **

Partition Map for IDE device 0  --   Partition Type: DOS

Part	Start Sector	Num Sectors	UUID		Type
  1	2048      	8388608   	4825ce1a-01	83
Card did not respond to voltage select!
mmc_init: -95, time 11
running scan_disk ...
Scan device usb
device usb 0:1
** Bad device usb 0 **
device usb 1:1
** Bad device usb 1 **
device usb 2:1
** Bad device usb 2 **
device usb 3:1
** Bad device usb 3 **
Scan device ide

Reset IDE: Bus 0: OK Bus 1: not available  
  Device 0: Model: FUJITSU MHW2080BJ G2 Firm: 0085001A Ser#: K30TT812D539
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 76319.0 MB = 74.5 GB (156301488 x 512)
device ide 0:1
1 bytes read in 56 ms (0 Bytes/s)
Found bootable drive on ide 0
** Bad device usb 0 **
** Bad device usb 0 **
** Bad device usb 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Pogov4>

Edited 1 time(s). Last edit at 09/16/2019 10:52AM by Tushar.

Tushar,

I see.

Interrupt netconsole at countdown and

setenv devices 'ide usb mmc'
setenv bootdev ide
boot

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Quote
bodhi
Interrupt netconsole at countdown and

setenv devices 'ide usb mmc'
setenv bootdev ide
boot

Hi Bodhi,

I wasn't able to issue the command 'setenv' as it returned error. So I did 'fw_setenv' instead. Please note I also followed Jeff's netconsole setup from wiki so it was 'view-only'. I applied the following commends while I was inside pogoplug logged as root (it was booted up with help using USB Flash drive inserted):

fw_setenv devices 'ide usb mmc'
fw_setenv bootdev ide

Then I shutdown the Pogoplug, took off the USB, and turn it on again while HDD was only mounted. But it didn't boot-up. Here's the latest netconsole output (using ide as bootdev and devices 'ide usb mmc':

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:34:01 -0700)
Pogoplug V4
gcc (Debian 6.3.0-18) 6.3.0 20170516
GNU ld (GNU Binutils for Debian) 2.28
Hit any key to stop autoboot:  0 

Reset IDE: Bus 0: OK Bus 1: not available  
  Device 0: Model: FUJITSU MHW2080BJ G2 Firm: 0085001A Ser#: K30TT812D539
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 76319.0 MB = 74.5 GB (156301488 x 512)
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Card did not respond to voltage select!
mmc_init: -95, time 11

Partition Map for IDE device 0  --   Partition Type: DOS

Part	Start Sector	Num Sectors	UUID		Type
  1	2048      	8388608   	4825ce1a-01	83
## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0
loading envs from usb 0 ...
** Bad device usb 0 **
Card did not respond to voltage select!
mmc_init: -95, time 11
running scan_disk ...
Scan device ide

Reset IDE: Bus 0: OK Bus 1: not available  
  Device 0: Model: FUJITSU MHW2080BJ G2 Firm: 0085001A Ser#: K30TT812D539
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 76319.0 MB = 74.5 GB (156301488 x 512)
device ide 0:1
1 bytes read in 56 ms (0 Bytes/s)
Found bootable drive on ide 0
** Bad device usb 0 **
** Bad device usb 0 **
** Bad device usb 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Pogov4>

I later checked the printenv status: Pogov4>printenv and the report is below;

Pogov4> printenv
printenv
arcNumber=3960
bootargs=console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
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
bootdelay=10
bootdev=ide
device=0:1
devices=ide usb mmc
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-pogoplug_v4.dtb
ethact=egiga0
ethaddr=00:25:31:05:2e:99
fileaddr=800000
filesize=1
if_netconsole=ping $serverip
init_ide=ide reset
init_mmc=mmc rescan
init_usb=usb start
ipaddr=192.168.0.151
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=ext2load usb 0:1 0x1c00000 /boot/dts/kirkwood-pogoplug_v4.dtb
load_dtb_addr=0x1c00000
load_initrd=ext2load usb 0:1 0x1100000 /boot/uInitrd
load_initrd_addr=0x1100000
load_uimage=ext2load usb 0:1 0x800000 /boot/uImage
load_uimage_addr=0x800000
machid=f78
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
ncip=192.168.0.100
partition=nand0,2
preboot=run if_netconsole start_netconsole
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
scan_ide=ide reset
scan_mmc=mmc rescan
scan_usb=usb start
serverip=192.168.0.100
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=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 0; do run uenv_read_disk; done; done;
uenv_loaded=0
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
usb_boot=run load_dtb; run load_uimage; if run load_initrd; then bootm 0x800000 0x1100000 0x1c00000; else bootm 0x800000 - 0x1c00000; fi
usb_ready_retry=15

Environment size: 3243/131068 bytes

what's going on?

Tushar ,

Let's try these.

Power up, interrupt netconsole at countdown

Hit any key to stop autoboot:  0

When you see the prompt like you did in printenv up there

Pogov4> printenv

Enter:

printenv
setenv devices ide
setenv bootdev ide
boot

And post the log here.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi Bodhi, ok, as you said I did the same. NC output below:

Pogov4> setenv devices ide
Pogov4> setenv bootdev ide
Pogov4> boot

Reset IDE: Bus 0: OK Bus 1: not available  
  Device 0: Model: FUJITSU MHW2080BJ G2 Firm: 0085001A Ser#: K30TT812D539
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 76319.0 MB = 74.5 GB (156301488 x 512)

Partition Map for IDE device 0  --   Partition Type: DOS

Part	Start Sector	Num Sectors	UUID		Type
  1	2048      	156299440 	66f6249b-01	83 Boot
running scan_disk ...
Scan device ide

Reset IDE: Bus 0: OK Bus 1: not available  
  Device 0: Model: FUJITSU MHW2080BJ G2 Firm: 0085001A Ser#: K30TT812D539
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 76319.0 MB = 74.5 GB (156301488 x 512)
device ide 0:1
1 bytes read in 58 ms (0 Bytes/s)
Found bootable drive on ide 0
** Bad device usb 0 **
** Bad device usb 0 **
** Bad device usb 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Pogov4>

After this failed, I did this: (While the USB Flash still mounted on the Pogo V4)

Pogov4> setenv devices 'ide usb mmc'
Pogov4> setenv bootdev ide
Pogov4> boot

the result was this:

Reset IDE: Bus 0: OK Bus 1: not available  
  Device 0: Model: FUJITSU MHW2080BJ G2 Firm: 0085001A Ser#: K30TT812D539
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 76319.0 MB = 74.5 GB (156301488 x 512)
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 
Use USB retry period from the environment: 15 second(s)
1 Storage Device(s) found
Card did not respond to voltage select!
mmc_init: -95, time 11

Partition Map for IDE device 0  --   Partition Type: DOS

Part	Start Sector	Num Sectors	UUID		Type
  1	2048      	156299440 	66f6249b-01	83 Boot

Partition Map for USB device 0  --   Partition Type: DOS

Part	Start Sector	Num Sectors	UUID		Type
  1	2048      	15431680  	0c04d391-01	83

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0
loading envs from usb 0 ...
** File not found /boot/uEnv.txt **
Card did not respond to voltage select!
mmc_init: -95, time 11
running scan_disk ...
Scan device ide

Reset IDE: Bus 0: OK Bus 1: not available  
  Device 0: Model: FUJITSU MHW2080BJ G2 Firm: 0085001A Ser#: K30TT812D539
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 76319.0 MB = 74.5 GB (156301488 x 512)
device ide 0:1
1 bytes read in 58 ms (0 Bytes/s)
Found bootable drive on ide 0
3821592 bytes read in 960 ms (3.8 MiB/s)
7245696 bytes read in 996 ms (6.9 MiB/s)
10284 bytes read in 1799 ms (4.9 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-4.12.1-kirkwood-tld-1
   Created:      2017-07-20   8:11:24 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3821528 Bytes = 3.6 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-4.12.1-kirkwood-tld-1
   Created:      2017-07-24   0:18:23 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7245632 Bytes = 6.9 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 ...

Now that the Pogo v4 started fine with both the USB flash drive and HDD mounted, I shut it down from within the SSH. Took the USB pendrive out and left HDD mounted. But the device didn't boot. NC output shows below:

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:34:01 -0700)
Pogoplug V4
gcc (Debian 6.3.0-18) 6.3.0 20170516
GNU ld (GNU Binutils for Debian) 2.28
Hit any key to stop autoboot:  0 
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Reset IDE: Bus 0: OK Bus 1: not available  
  Device 0: Model: FUJITSU MHW2080BJ G2 Firm: 0085001A Ser#: K30TT812D539
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 76319.0 MB = 74.5 GB (156301488 x 512)
Card did not respond to voltage select!
mmc_init: -95, time 11
## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0
loading envs from usb 0 ...
** Bad device usb 0 **

Partition Map for IDE device 0  --   Partition Type: DOS

Part	Start Sector	Num Sectors	UUID		Type
  1	2048      	156299440 	66f6249b-01	83 Boot
Card did not respond to voltage select!
mmc_init: -95, time 11
running scan_disk ...
Scan device usb
device usb 0:1
** Bad device usb 0 **
device usb 1:1
** Bad device usb 1 **
device usb 2:1
** Bad device usb 2 **
device usb 3:1
** Bad device usb 3 **
Scan device ide

Reset IDE: Bus 0: OK Bus 1: not available  
  Device 0: Model: FUJITSU MHW2080BJ G2 Firm: 0085001A Ser#: K30TT812D539
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 76319.0 MB = 74.5 GB (156301488 x 512)
device ide 0:1
1 bytes read in 58 ms (0 Bytes/s)
Found bootable drive on ide 0
** Bad device usb 0 **
** Bad device usb 0 **
** Bad device usb 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Pogov4>

Edited 3 time(s). Last edit at 09/18/2019 02:29AM by Tushar.

Tushar,

Now that output log above triggered my doubt so I examined your envs more closely. It was messed up. You probably have been playing and changing some envs. They are no longer a consistent set like I have set up in the default envs.

These 3 lines are wrong:

load_dtb=ext2load usb 0:1 0x1c00000 /boot/dts/kirkwood-pogoplug_v4.dtb
load_initrd=ext2load usb 0:1 0x1100000 /boot/uInitrd
load_uimage=ext2load usb 0:1 0x800000 /boot/uImage

They should be:

load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage

At this point if you cannot get it to boot with the above 3 envs, I would suggest you boot with USB, and reflash the default envs image (repeat section 8 in the installation instruciton):

Quote

8. Flashing default u-boot envs image (if you are upgrading from 2016.05-tld-1 u-boot, you can skip this step 8).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 09/18/2019 03:36AM by bodhi.

Hi Bodhi,

Thanks a lot. That was the issue. Now it's working just as expected. Now 3 other questions,

1. In the wiki under Linux Tools, I see HDD spin down sections:

Debian hdparm (HDD spin down)
Hard Drive Idle Tool (an alternative to the standard Debian hdparm)

-is this a good practice to apply those? In my case, I'm planing to use my Pogo v4 as local Wordpress web server. pls advice.

2. Now that everything is up as I wanted and I have a serial cable around, If I want to disable the netconsole, what to do?

fw_setenv 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'
fw_setenv preboot 'run preboot_nc'
fw_setenv ipaddr    '192.168.0.xxx'
fw_setenv serverip '192.168.0.yyy'

3. If I want to add the optional Section C's. uEnv.txt to /boot directory, do I have to enter everything that appears in fw_printenv output on my current settings?

Thanks a lot.

- Tushar.

Tushar,

> 1. In the wiki under Linux Tools, I see HDD spin
> down sections:
>
> Debian hdparm (HDD spin down)
> Hard Drive Idle Tool (an alternative to the
> standard Debian hdparm)
>
> -is this a good practice to apply those? In my
> case, I'm planing to use my Pogo v4 as local
> Wordpress web server. pls advice.

You can only spin down the HDD only if you boot with USB rootfs. If the HDD house the rootfs, then it will not spin down for long (always something going on), and it actually bad to spin it down too frequently.

>
> 2. Now that everything is up as I wanted and I
> have a serial cable around, If I want to disable
> the netconsole, what to do?
>

Clear the preboot env

fw_setenv preboot

Alternatively, you could also change the preboot_nc to do nothing:

fw_setenv preboot_nc_old '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'
fw_setenv preboot_nc 'echo Netconsole is not running'

> 3. If I want to add the optional Section C's.
> uEnv.txt to /boot directory, do I have to enter
> everything that appears in fw_printenv output on
> my current settings?

You only need additional variables in uEnv.txt. The envs in uEnv.txt are updated on the fly during u-boot booting and not saved. So you can try out things without changing envs permanently.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)