Welcome! Log In Create A New Profile

Advanced

Sata boot failed after 3.17 upgrade.

Posted by robert1968@gmail.com 
Forum List Message List New Topic
robert1968@gmail.com
Sata boot failed after 3.17 upgrade.
November 03, 2014 01:09PM
Hi,

I've just upgraded to 3.17 on my Goflex Net and failed to boot.
Ext3 Sata boot, was working fine on 3.16 kernel.

I made described upgrade steps: 1), 2) 3), and 4a) steps and reboot.

my environment is : 

root@pogo:/boot# fw_printenv 
ethact=egiga0
bootdelay=3
baudrate=115200
mainlineLinux=yes
console=ttyS0,115200
led_init=green blinking
led_exit=green off
led_error=orange blinking
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
mtdids=nand0=orion_nand
partition=nand0,2
stdin=serial
stdout=serial
stderr=serial
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_list=1 2 3 4
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_init=run usb_scan
usb_device=0:1
usb_root=/dev/sda1
usb_rootdelay=10
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
ethaddr=00:10:75:26:6D:EC
rescue_installed=1
serverip=192.168.178.20
ipaddr=192.168.178.22
if_netconsole=ping $serverip
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
usb_bootcmd=run usb_init; setenv usb_root LABEL=rootfs; run usb_set_bootargs; run usb_boot
sata_boot=ide reset; mw 0x800000 0 1; ext2load ide 0:1 0x800000 /boot/uImage; if ext2load ide 0:1 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
sata_bootcmd=run usb_set_bootargs; run sata_boot
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run sata_bootcmd; run rescue_bootcmd; run pogo_bootcmd; reset
arcNumber=3089
usb_rootfstype=ext3
preboot_nc=run if_netconsole start_netconsole
load_dtb=ext2load usb 0:1 0x1c00000 /boot/dts/kirkwood-goflexnet.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@pogo:/boot#


Unfortunately not able to access via netconsole jet....

Best regards,
Robert
Reply Quote
bodhi
Re: Sata boot failed after 3.17 upgrade.
November 03, 2014 11:15PM
@Robert,

Step 4 in the installation:

Quote

4. Create uImage and uInitrd and setup for booting.

I'm using the GoFlex Net booting with USB drive as an example here. Please replace its name (kirkwood-goflexnet.dtb) with the box you are installing on (for example, kirkwood-pogo_e02.dtb). Look inside /boot/dts/ for the correct DTB file name for your box.

…………

4a. Boot with DTB file (standard way to boot FDT kernel). Recommended.

Generate the uImage and uInitrd, and set U-Boot envs for booting:
cd /boot
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-3.17.0-kirkwood-tld-1 -d /boot/vmlinuz-3.17.0-kirkwood-tld-1 /boot/uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-3.17.0-kirkwood-tld-1 -d /boot/initrd.img-3.17.0-kirkwood-tld-1 /boot/uInitrd

fw_setenv load_dtb 'ext2load usb 0:1 0x1c00000 /boot/dts/kirkwood-goflexnet.dtb'
fw_setenv load_initrd 'ext2load usb 0:1 0x1100000 /boot/uInitrd'
fw_setenv load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage'
fw_setenv usb_boot 'run load_dtb; run load_uimage; if run load_initrd; then bootm 0x800000 0x1100000 0x1c00000; else bootm 0x800000 - 0x1c00000; fi'

So in order to boot SATA only, no USB booting: 

fw_setenv load_dtb 'ext2load ide 0:1 0x1c00000 /boot/dts/kirkwood-goflexnet.dtb' 
fw_setenv load_initrd 'ext2load ide 0:1 0x1100000 /boot/uInitrd' 
fw_setenv load_uimage 'ext2load ide 0:1 0x800000 /boot/uImage' 
fw_setenv sata_boot 'run load_dtb; run load_uimage; if run load_initrd; then bootm 0x800000 0x1100000 0x1c00000; else bootm 0x800000 - 0x1c00000; fi'

Now, if you wish to have both USB and SATA booting in the same bootcmd, then you could rename the above as: 

fw_setenv load_dtb_sata 'ext2load ide 0:1 0x1c00000 /boot/dts/kirkwood-goflexnet.dtb' 
fw_setenv load_initrd_sata 'ext2load ide 0:1 0x1100000 /boot/uInitrd' 
fw_setenv load_uimage_sata 'ext2load ide 0:1 0x800000 /boot/uImage' 
fw_setenv sata_boot 'run load_dtb_sata; run load_uimage_sata; if run load_initrd_sata; then bootm 0x800000 0x1100000 0x1c00000; else bootm 0x800000 - 0x1c00000; fi'

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



Edited 1 time(s). Last edit at 11/03/2014 11:16PM by bodhi.
Reply Quote
robert1968@gmail.com
Re: Sata boot failed after 3.17 upgrade.
November 04, 2014 06:37AM
Hi Bodhi,

Thank you very much.

My state getting worst and worst. :)

No boot form USB no boot from Sata.

I did a new ext3 USB drive and steps but not booted I only have rescue!

Unfortunately rescue doesnot able to run mkimage (and even not recognise sata in dmesg.)

(Although I already made mkimage yesterday when i had bootable 3.16 kernel. On sata ! )

I assume because my bootargs_usb is not proper??? 

rescue:~# fw_printenv | grep set_bootargs_usb
set_bootargs_usb=setenv=bootargs console= root= rootdelay= rootfstype=ext2


No netconsole works even I set fw_setenv serverip to my pc (server) IP.

My environment is this: 
rescue:~# fw_printenv | grep set_bootargs_usb
set_bootargs_usb=setenv=bootargs console= root= rootdelay= rootfstype=ext2
rescue:~# fw_printenv
ethact=egiga0
bootdelay=3
baudrate=115200
mainlineLinux=yes
console=ttyS0,115200
led_init=green blinking
led_exit=green off
led_error=orange blinking
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
mtdids=nand0=orion_nand
partition=nand0,2
stdin=serial
stdout=serial
stderr=serial
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_list=1 2 3 4
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_init=run usb_scan
usb_device=0:1
usb_root=/dev/sda1
usb_rootdelay=10
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
ethaddr=00:10:75:26:6D:EC
rescue_installed=1
serverip=192.168.178.20
ipaddr=192.168.178.22
if_netconsole=ping $serverip
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
usb_bootcmd=run usb_init; setenv usb_root LABEL=rootfs; run usb_set_bootargs; run usb_boot
sata_bootcmd=run usb_set_bootargs; run sata_boot
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run sata_bootcmd; run rescue_bootcmd; run pogo_bootcmd; reset
arcNumber=3089
usb_rootfstype=ext3
preboot_nc=run if_netconsole start_netconsole
usb_boot=run load_dtb; run load_uimage; if run load_initrd; then bootm 0x800000 0x1100000 0x1c00000; else bootm 0x800000 - 0x1c00000; fi
load_dtb_sata=ext2load ide 0:1 0x1c00000 /boot/dts/kirkwood-goflexnet.dtb
load_initrd_sata=ext2load ide 0:1 0x1100000 /boot/uInitrd
load_uimage_sata=ext2load ide 0:1 0x800000 /boot/uImage
set_bootargs_usb=setenv=bootargs console= root= rootdelay= rootfstype=ext2
load_dtb=ext2load ide 0:1 0x1c00000 /boot/dts/kirkwood-goflexnet.dtb
load_initrd=ext2load ide 0:1 0x1100000 /boot/uInitrd
load_uimage=ext2load ide 0:1 0x800000 /boot/uImage
sata_boot=run load_dtb; run load_uimage; if run load_initrd; then bootm 0x800000 0x1100000 0x1c00000; else bootm 0x800000 - 0x1c00000; fi
rescue:~#


Should i serial console to inspect why not boot??

Regards,R
Reply Quote
bodhi
Re: Sata boot failed after 3.17 upgrade.
November 04, 2014 12:49PM
@Robert,

Activate netconsole 
fw_setenv preboot 'run preboot_nc'

Set bootargs 
fw_setenv set_bootargs_usb  'setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params'

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
robert1968@gmail.com
Re: Sata boot failed after 3.17 upgrade.
November 04, 2014 01:28PM
Thank You Bodhi,

Netcat works!! Hurray. :)

Sata not booted yet. see nc log. 

b@big2 ~ $ nc -u 192.168.178.22 6666

U-Boot 2013.10 (Nov 02 2013 - 01:11:12)-tld
Seagate GoFlex Net
gcc (Debian 4.6.3-14) 4.6.3
GNU ld (GNU Binutils for Debian) 2.22
Hit any key to stop autoboot:  0 
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
** Bad device usb 0 **
** Bad device usb 0 **
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:            219 MiB
UBI: number of good PEBs:        1751
UBI: number of bad PEBs:         1
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:             1730
UBI: total number of reserved PEBs: 21
UBI: number of PEBs reserved for bad PEB handling: 17
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "rootfs", error -22
UBIFS error (pid 0): ubifs_mount: Error reading superblock on volume 'rootfs' errno=-22!

ubifsmount - mount UBIFS volume

Usage:
ubifsmount <volume-name>
    - mount 'volume-name' volume
## Error: "dt_usb_bootcmd" not defined
stopping USB..
** Bad device size - ide 0 **
** Bad device size - ide 0 **
** Bad device size - ide 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!

NAND read: device 0 offset 0x100000, size 0x400000
3.1 4194304 bytes read: OK
 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... ## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-2.6.32.18-dockstar
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3236180 Bytes = OK


Starting kernel ...

Should I try usb pendrive?
But on pendrive I dont have mkimage ... because I cant generate it from rescue...

Regards,Robert
Reply Quote
bodhi
Re: Sata boot failed after 3.17 upgrade.
November 04, 2014 11:49PM
@robert,

Your u-boot envs seem to be messed up! I can't see where this dt_usb_bootcmd env came from. Are your current u-boot envs different from the listing above? Be careful changing them, you could get locked out netconsole too if the related envs are not set correctly.

You could either try to fix it, or switch to USB booting and then fix it in Debian. mkimage is available in the rootfs. If you use my uploaded latest rootfs, then at this directory in the USB rootfs: 
/media/sda1/usr/bin/mkimage

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



Edited 2 time(s). Last edit at 11/05/2014 01:49AM by bodhi.
Reply Quote
robert1968@gmail.com
Re: Sata boot failed after 3.17 upgrade.
November 05, 2014 04:48AM
Thanks Bodhi,

Really appreciate to help me... :)

>I can't see where this dt_usb_bootcmd env came from. Are your current u-boot envs different from the listing above?
I tried to modify usb_bootcmd=run dt_usb_bootcmd because you wrote here:
C. How to boot Debian FDT kernel

I assume i totally messed up my env. :)

How to get a simple env?
Is it good if I follow your description here : B. Flashing default u-boot envs image
???

I would have SATA, USB, Netconsole, rescue boot... Just to be on a safe side... :)

>or switch to USB booting
USB not booting!! thats my problem too.
So can not resolve the situation....

My present environment is this: 

rescue:~# fw_printenv 
ethact=egiga0
bootdelay=3
baudrate=115200
mainlineLinux=yes
console=ttyS0,115200
led_init=green blinking
led_exit=green off
led_error=orange blinking
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
mtdids=nand0=orion_nand
partition=nand0,2
stdin=serial
stdout=serial
stderr=serial
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_list=1 2 3 4
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_init=run usb_scan
usb_device=0:1
usb_root=/dev/sda1
usb_rootdelay=10
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
ethaddr=00:10:75:26:6D:EC
rescue_installed=1
serverip=192.168.178.20
ipaddr=192.168.178.22
if_netconsole=ping $serverip
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
sata_bootcmd=run usb_set_bootargs; run sata_boot
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run sata_bootcmd; run rescue_bootcmd; run pogo_bootcmd; reset
arcNumber=3089
usb_rootfstype=ext3
preboot_nc=run if_netconsole start_netconsole
usb_boot=run load_dtb; run load_uimage; if run load_initrd; then bootm 0x800000 0x1100000 0x1c00000; else bootm 0x800000 - 0x1c00000; fi
load_dtb_sata=ext2load ide 0:1 0x1c00000 /boot/dts/kirkwood-goflexnet.dtb
load_initrd_sata=ext2load ide 0:1 0x1100000 /boot/uInitrd
load_uimage_sata=ext2load ide 0:1 0x800000 /boot/uImage
load_dtb=ext2load ide 0:1 0x1c00000 /boot/dts/kirkwood-goflexnet.dtb
load_initrd=ext2load ide 0:1 0x1100000 /boot/uInitrd
load_uimage=ext2load ide 0:1 0x800000 /boot/uImage
sata_boot=run load_dtb; run load_uimage; if run load_initrd; then bootm 0x800000 0x1100000 0x1c00000; else bootm 0x800000 - 0x1c00000; fi
usb_bootcmd=run dt_usb_bootcmd
preboot=run preboot_nc
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params

Regards,
Robert
Reply Quote
robert1968@gmail.com
Re: Sata boot failed after 3.17 upgrade.
November 05, 2014 04:54AM
Just a small addition to Previous post....

If I try USB boot on the same environment: 

b@big2 ~ $ nc -u 192.168.178.22 6666

U-Boot 2013.10 (Nov 02 2013 - 01:11:12)-tld
Seagate GoFlex Net
gcc (Debian 4.6.3-14) 4.6.3
GNU ld (GNU Binutils for Debian) 2.22
Hit any key to stop autoboot:  0 
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 1 Storage Device(s) found
** File not found /rescueme **
** Unrecognized filesystem type **
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:            219 MiB
UBI: number of good PEBs:        1751
UBI: number of bad PEBs:         1
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:             1730
UBI: total number of reserved PEBs: 21
UBI: number of PEBs reserved for bad PEB handling: 17
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "rootfs", error -22
UBIFS error (pid 0): ubifs_mount: Error reading superblock on volume 'rootfs' errno=-22!

ubifsmount - mount UBIFS volume

Usage:
ubifsmount <volume-name>
    - mount 'volume-name' volume
## Error: "dt_usb_bootcmd" not defined
stopping USB..
** Bad device size - ide 0 **
** Bad device size - ide 0 **
** Bad device size - ide 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!

NAND read: device 0 offset 0x100000, size 0x400000
 4194304 bytes read: OK
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-2.6.32.18-dockstar
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3236180 Bytes = 3.1 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK


Starting kernel ...


Regards,
Robert
Reply Quote
bodhi
Re: Sata boot failed after 3.17 upgrade.
November 06, 2014 02:14AM
@robert,


Yes. Do this to get back to a default set of ens as described in the u-boot thread: 
B. Flashing default u-boot envs image

And then immediately (without reboot), follow the instruction in the kernel thread (Updated 26 Oct 2014) to setup FDT kernel booting envs: 
4a. Boot with DTB file (standard way to boot FDT kernel). Recommended.

And you did the wrong thing: you did not follow exactly the instruction in the kernel thread when you upgraded to the FDT kernel 3.17. In the U-boot thread, section "C. How to boot Debian FDT kernel" is for information when people boot an FDT kernel of their own.

Basically, when you install a new kernel, you must follow the instruction in that post as exactly described. If u-boot envs needed to be set a certain way in installing kernel, then whatever envs you set in installing u-boot before might or might apply any more.

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



Edited 1 time(s). Last edit at 11/06/2014 02:34AM by bodhi.
Reply Quote
robert1968@gmail.com
Re: Sata boot failed after 3.17 upgrade.
November 06, 2014 11:47PM
Hi Bodhi.

Million thanks. (I was hopeless almost)
I will try this today.


>you did not follow exactly the instruction in the kernel thread

I did follow! :)
All them, sequentially! (It was not clear for me)

Step 3, has sense, (i mean to me) because this new kernel is ftd.

So I hope , this is the reason why it is failed.

Thanks for help!

Robert
Reply Quote
bodhi
Re: Sata boot failed after 3.17 upgrade.
November 07, 2014 01:20AM
robert,

> I did follow! :)
> All them, sequentially! (It was not clear for me)
>
> Step 3, has sense, (i mean to me) because this
> new kernel is ftd.
>

It is true. Since you installed u-boot first, I can see why you thought it was necessary to do this first :) in any case, the u-boot envs in the kernel thread are the ones to use.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Reply Quote
robert1968@gmail.com
Re: Sata boot failed after 3.17 upgrade. - RESOLVED
November 07, 2014 05:26AM
Hi Bodhi,.

Tons of Thanks!!! IT IS WORKING NOW!

SATA boots with these settings 

w_setenv load_dtb_sata 'ext2load ide 0:1 0x1c00000 /boot/dts/kirkwood-goflexnet.dtb' 
fw_setenv load_initrd_sata 'ext2load ide 0:1 0x1100000 /boot/uInitrd' 
fw_setenv load_uimage_sata 'ext2load ide 0:1 0x800000 /boot/uImage' 
fw_setenv sata_boot 'run load_dtb_sata; run load_uimage_sata; if run load_initrd_sata; then bootm 0x800000 0x1100000 0x1c00000; else bootm 0x800000 - 0x1c00000; fi'



All my working settings here: 
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
baudrate=115200
bootcmd=run bootcmd_usb; run bootcmd_mmc; run bootcmd_sata; reset
bootcmd_mmc=run mmc_init; run set_bootargs_mmc; run mmc_boot
bootcmd_sata=run sata_init; run set_bootargs_sata; run sata_boot;
bootcmd_usb=run usb_init; run set_bootargs_usb; run usb_boot;
bootdelay=10
console=ttyS0,115200
device=0:1
ethact=egiga0
if_netconsole=ping $serverip
led_error=orange blinking
led_exit=green off
led_init=green blinking
mainlineLinux=yes
mmc_boot=mw 0x800000 0 1; run mmc_load_uimage; if run mmc_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
mmc_init=mmc rescan
mmc_load_uimage=ext2load mmc $device 0x800000 /boot/uImage
mmc_load_uinitrd=ext2load mmc $device 0x1100000 /boot/uInitrd
mmc_root=/dev/mmcblk0p1
mtdids=nand0=orion_nand
partition=nand0,2
preboot_nc=run if_netconsole start_netconsole
rootdelay=10
rootfstype=ext3
sata_init=ide reset
sata_load_uimage=ext2load ide $device 0x800000 /boot/uImage
sata_load_uinitrd=ext2load ide $device 0x1100000 /boot/uInitrd
sata_root=/dev/sda1
set_bootargs_mmc=setenv bootargs console=$console root=$mmc_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_sata=setenv bootargs console=$console root=$sata_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
usb_init=usb start
usb_load_uimage=ext2load usb $device 0x800000 /boot/uImage
usb_load_uinitrd=ext2load usb $device 0x1100000 /boot/uInitrd
usb_root=/dev/sda1
arcNumber=3089
ethaddr=00:10:75:26:6D:EC
preboot=run preboot_nc
ipaddr=192.168.178.22
serverip=192.168.178.20
load_dtb=ext2load usb 0:1 0x1c00000 /boot/dts/kirkwood-goflexnet.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
load_dtb_sata=ext2load ide 0:1 0x1c00000 /boot/dts/kirkwood-goflexnet.dtb
load_initrd_sata=ext2load ide 0:1 0x1100000 /boot/uInitrd
load_uimage_sata=ext2load ide 0:1 0x800000 /boot/uImage
sata_boot=run load_dtb_sata; run load_uimage_sata; if run load_initrd_sata; then bootm 0x800000 0x1100000 0x1c00000; else bootm 0x800000 - 0x1c00000; fi


Thank you very much for help !!!!


Summary:
  • I had 3.16 on SATA. booted OK. but want to upgrade to 3.17.
  • Upgraded to 3.17 generate uimage and uinitrd as described. All right.
    but follow a (for my case) wrong instruction (4.b) and I set wrong env. (for this I've judged 4 days of hell for proper punishment :) )

Bodhi! Thanks for help me out from hell !!! :)

Suggestion / question:
Is it better to have a new extension about sata boot in your kernel setup instruction ? as sent to me in second post within this thread ?
Because sata is more reliable... and many people wants to boot sata instead of usb.

Regards,Robert



Edited 1 time(s). Last edit at 11/07/2014 05:29AM by robert1968@gmail.com.
Reply Quote
Newer Topic Older Topic
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: