Tutorial of native sata boot for pogoplug pro
Posted by youxiaojie
|
Tutorial of native sata boot for pogoplug pro March 12, 2017 12:06PM |
Registered: 7 years ago Posts: 67 |
I summed up the old post about sata boot for pogoplug pro and fixed some broken links
Just for reference to others, I made a very detailed summary.
Please revise my comment are there right in technical aspect. (?? if I have doubt - I will revise based on your comment)
Synopsys:
My device Pogo Plug P24 - V3 (nonpci) - oxnas 820
I have serial connection,
I Screw up UBoot in NAND - Therefore no boot from USB,
and NOTHING appears on Serial console!!!
Only way to boot is well prepared SATA because oxnas tries to boot Uboot on SATA then Uboot on NAND then USB. (?? is that right??)
Steps
1. Get a SATA HDD. You have to delete all partition from it. Sorry :(
2. Put it to USB HDD frame. Attache to PC. Umount all partition if automount happened.
3. remove partitions, and create new.
fdisk /dev/sdb
o - create a new empty DOS partition table
n - Create part 1 (start with 2048 ; size: +2G )
w - write
q - exit
4. mkext4 fs.
( If you have problems with "mkfs.ext4 /dev/sdb is not a block special device."
Detach USB _and_ reboot your PC. and attache again - will solve the problem...)
5 Labell it:
6.Mount rootfs
7. Prepare Sata uboot file on PC :
a.) Extract the content Shv made ox820-sata-uboot.tar.gz to your PC
cd /yourpath
tar -xjf ox820-sata-uboot.tar.gz
(It is only a boot directory on your PC)
Navigate to /yourpath/boot/dts directory and rename this files:
-it is only needed in case noPCI devices like P24.
b.) and copy modified /yourpath/boot directory to the rootfs partition.
c.)Modify 2 lines in disk create script on your PC:
c1.) disk=/dev/sdb
c2.) workarea="/yourpath"
d.) save changes
8. Now you have to run Sata uboot SCRIPT on your PC.
It will write U-Boot SPL to Sata disk on the beginning (in the first 2048 sector) on the disk.
8a.) Umount - Just to be safe side: Not write to disk which is mounted... - skip if brave.
8b.) Run Sata uboot SCRIPT
Prepare Debian Rootfs files.
9.) Mount rootfs again:
10.) Extract debian files to your PC /yourpath directory. Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2
11. Copy all directory from PC to your rootfs partition BUT /boot . (It means do not overwrite the existing /boot on rootfs!!)
detach from PC and attache to Pogo.
Attache serial TTL connector and see output. Trust Bodhi, Picocom is better than GNU Screen. I learned :)
Power on your POGO.
Debian will not boot because Uboot env not well set for this configuration. try it but for sure it will freeze. :) then power on - and - of again.
Now Stop the counter by press a key:
Hit any key to stop autoboot: 3
Now set the environment to this setup:
Looks like your V3 is trying to boot from ide. If what you posted is your complete printenv, you are missing some stuff.
Here is my ide boot setenv's (partial) for a frame of reference:
And for usb booting it's this (complete):
Do a printenv and try to determine what you are missing based on what I have posted. Note that my boot env's are pretty simple compared to some of the really complicated netconsole / tftp ones I have seen on the forum so you might want to take a look at some of those if you wanna get funky.
Boot success!!
I hope -you Masters (Bodhi, SHV, Morph) - find my guide is useful. :) and it is a little benefit give back to community. Respect.
To be continued
No! But if you put the right stage1 bootloader and the right uboot to your SATA drive it might boot with them. You can't use the files which are provided here for Flash install. Moreover you must put the stage1 bootloader to your drive as it is done by OXNAS-SATA-Boot skript from ALARM forum. The uboot can be put to the filesystem of the first partition (Fat32 or ext4 depends on the stage1 loader).
I tested the following setups:
sda1: just für boot files like u-boot.img, u-boot.env, uImage, uInitrd (ext4 or fat32)
sda2: rootfs (ext3 or ext4)
sda3: linux swap partition
sda4: data (ext4)
or
sda1: rootfs including boot files (ext4)
sda2: linux swap partition
sda3: data (ext4)
For both setups you can use the same stage1 bootloader (u-boot-spl.bin) which reads the boot files from and stores boot environment to the first ext4 partition of the SATA drive. The device must support 512 Byte sector size either natively or by simulation.
u-boot files for SATA booting: http://pogoplug.square7.ch/ox820-sata-uboot.tar.gz (environment must be adapted with the serial console to boot the uImage and uInitrd files) - uImage, uInitrd and dtb file are for Pogoplug Pro - you might replace them with the right files of your kernel
can be download at :
This is courtesy of LeggoMyEggo. I've upload the tarball Leggo sent me to Dropbox.
There are 2 tarballs in it. One from shv, one from WarheadsSE. It's easier to use the shv's: ox820-sata-uboot.tar.gz.
Dropbox download link:
https://www.dropbox.com/s/p9bo06us5fo2i3s/oxnasboottarball.zip
md5
8e016437146f40cdb51ad9dbd63b1bdd
Preparing SATA drive and storing u-boot-spl.bin alias stage1 to it:
You must execute the steps from the ALARM script until stage1 file (u-boot-spl.bin from my package must be used instead the provided stage1 file) is stored to the HDD.
You must adapt the following lines of the boot environment:
to be continued
http://forum.doozan.com/read.php?3,16017,19666#msg-19666
@Robert,
your boot environment looks OK for the old WarheadsSE booting procedure. It looks that you don't have the right rootfs on partition sda2 (ext3/partition name rootfs).
Nevertheless I want to recommend you to use new uboot. Bodhi already pointed you to my post: http://forum.doozan.com/read.php?3,16017,17297#msg-17297.
The device must support 512 Byte sector size either natively or by simulation.
Step1: prepare mbr partition table:
sda1: rootfs including boot files (ext4) with partition name rootfs
sda2: linux swap partition
sda3: data (ext4)
Step2: Extract the content of the archive http://pogoplug.cwsurf.de/ox820-sata-uboot.tar.gz (http://pogoplug.square7.ch/ox820-sata-uboot.tar.gz)to your rootfs partition
Step3: Prepare SATA booting by adapting and executing the following script
#!/bin/sh
# uncomment line below and set to the correct disk
#disk=/dev/sda
if [ -z "${disk}" ] ; then
echo "You must uncomment/set the 'disk' variable"
exit -1
fi
workarea="/boot"
stage1File=$workarea/u-boot-spl.bin
perl <<EOF | dd of="$disk" bs=512
print "\x00" x 0x1a4;
print "\x00\x5f\x01\x00";
print "\x00\xdf\x00\x00";
print "\x00\x80\x00\x00";
print "\x00" x (0x1b0 -0x1a4 -12 );
print "\x22\x80\x00\x00";
print "\x22\x00\x00\x00";
print "\x00\x80\x00\x00";
EOF
if [ -f $stage1File ];then
echo "Writing stage 1"
dd if=$stage1File of="$disk" bs=512 seek=34
fi
Step4: Boot with serial cable connected and adapt the boot-env settings to your needs
Please also read the posts of morph027 starting from: http://forum.doozan.com/read.php?3,16017,18341#msg-18341
-shv
TBC
my really test:
1.gpt partition with one ext3 labeled "rootfs"
2.download
Dropbox download link:
https://www.dropbox.com/s/p9bo06us5fo2i3s/oxnasboottarball.zip
md5
8e016437146f40cdb51ad9dbd63b1bdd
3. make rootfs by untar Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2
mount /dev/sdb1 /mnt
cd /mnt
tar -xjvf /home/allan/Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2
4.untar 0x820-sata-uboot.tar.gz ,there will be a boot direcotory and enter boot directory.
5 cp u-boot.img u-boot.env to /boot directory of rootfs we just made
6 umount /dev/sdb1
7 make script disk_create_mod.sh as following saving and running on ox820-sata-uboot/boot directory.
ox820-sata-uboot #
8
9
reboot.
boot log:
opps! my 256M ram mod is recognized.
but due to improper uboot env ,the linux can not boot.
modify uboot env
you can edit env in uboot envirment or use
mkenvimage -s <environment partition size> -o <output> <input file>
command from "u-boot-tool" package. I prefer latter. just save following code to a plan txt say ide-only.txt
and run
"mkenvimage -s 16380 -o u-boot.env ide-only.txt"
at /boot directory, overwrite old u-boot.env.
reboot.boot into linux, modify /etc/apt/sources.list
change the wheezy to jessie,
apt-get update; apt-get dist-upgrade
everything is ok
but if I change the wheezy to sid
apt-get update will show error.
install packages:mtd-utils and u-boot-tools for future use.
Edited 10 time(s). Last edit at 03/20/2017 01:42PM by youxiaojie.
Just for reference to others, I made a very detailed summary.
Please revise my comment are there right in technical aspect. (?? if I have doubt - I will revise based on your comment)
Synopsys:
My device Pogo Plug P24 - V3 (nonpci) - oxnas 820
I have serial connection,
I Screw up UBoot in NAND - Therefore no boot from USB,
and NOTHING appears on Serial console!!!
Only way to boot is well prepared SATA because oxnas tries to boot Uboot on SATA then Uboot on NAND then USB. (?? is that right??)
Steps
1. Get a SATA HDD. You have to delete all partition from it. Sorry :(
2. Put it to USB HDD frame. Attache to PC. Umount all partition if automount happened.
3. remove partitions, and create new.
fdisk /dev/sdb
o - create a new empty DOS partition table
n - Create part 1 (start with 2048 ; size: +2G )
w - write
q - exit
4. mkext4 fs.
mkfs.ext4 /dev/sdb1
( If you have problems with "mkfs.ext4 /dev/sdb is not a block special device."
Detach USB _and_ reboot your PC. and attache again - will solve the problem...)
5 Labell it:
tune2fs -L "rootfs" /dev/sdb1
6.Mount rootfs
mount /dev/sdb1 /media/rootfs
7. Prepare Sata uboot file on PC :
a.) Extract the content Shv made ox820-sata-uboot.tar.gz to your PC
cd /yourpath
tar -xjf ox820-sata-uboot.tar.gz
(It is only a boot directory on your PC)
Navigate to /yourpath/boot/dts directory and rename this files:
-it is only needed in case noPCI devices like P24.
mv ox820-pogoplug-pro.dtb ox820-pogoplug-pro.dtb.ori cp ox820-pogoplug-classic.dtb ox820-pogoplug-pro.dtb
b.) and copy modified /yourpath/boot directory to the rootfs partition.
c.)Modify 2 lines in disk create script on your PC:
c1.) disk=/dev/sdb
c2.) workarea="/yourpath"
d.) save changes
8. Now you have to run Sata uboot SCRIPT on your PC.
It will write U-Boot SPL to Sata disk on the beginning (in the first 2048 sector) on the disk.
8a.) Umount - Just to be safe side: Not write to disk which is mounted... - skip if brave.
umount rootfs
8b.) Run Sata uboot SCRIPT
./disk_create_shv
Prepare Debian Rootfs files.
9.) Mount rootfs again:
mount /dev/sdb1 /media/rootfs
10.) Extract debian files to your PC /yourpath directory. Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2
tar -xjf Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2
11. Copy all directory from PC to your rootfs partition BUT /boot . (It means do not overwrite the existing /boot on rootfs!!)
detach from PC and attache to Pogo.
Attache serial TTL connector and see output. Trust Bodhi, Picocom is better than GNU Screen. I learned :)
picocom -b 115200 /dev/ttyUSB0
Power on your POGO.
Debian will not boot because Uboot env not well set for this configuration. try it but for sure it will freeze. :) then power on - and - of again.
Now Stop the counter by press a key:
Hit any key to stop autoboot: 3
Now set the environment to this setup:
Looks like your V3 is trying to boot from ide. If what you posted is your complete printenv, you are missing some stuff.
Here is my ide boot setenv's (partial) for a frame of reference:
setenv uinitrd_addr '0x60e00000' setenv uimage_addr '0x60500000' setenv dtb_addr '0x62c00000' setenv ide_set_bootargs 'setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10' setenv dt_bootm 'bootm $uimage_addr $uinitrd_addr $dtb_addr' setenv dt_load_dtb 'ext2load ide 0:1 $dtb_addr /boot/dts/ox820-pogoplug-pro.dtb' setenv dt_load_initrd 'ext2load ide 0:1 $uinitrd_addr /boot/uInitrd' setenv dt_load_uimage 'ext2load ide 0:1 $uimage_addr /boot/uImage' setenv dt_ide_boot 'run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm' setenv dt_ide_bootcmd 'run ide_set_bootargs; run dt_ide_boot' setenv dt_bootcmd_ide 'ide reset; run dt_ide_bootcmd; reset' setenv bootcmd 'run dt_bootcmd_ide'
And for usb booting it's this (complete):
setenv autoload no setenv baudrate 115200 setenv bootargs console=ttyS0,115200n8 setenv bootdelay 10 setenv console console=ttyS0,115200n8 setenv ethact mii0 setenv ethaddr (removed for security) setenv ipaddr 192.168.1.100 setenv mtdids nand0=41000000.nand setenv mtdparts mtdparts=41000000.nand:14m(boot),-(data) setenv serverip 192.168.1.110 setenv stderr serial setenv stdin serial setenv stdout serial setenv usb_device 0:1 setenv if_netconsole ping $serverip setenv preboot_nc run if_netconsole start_netconsole setenv start_netconsole setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version setenv usb_set_bootargs setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10 setenv uinitrd_addr 0x60e00000 setenv uimage_addr 0x60500000 setenv dtb_addr 0x62c00000 setenv dt_load_dtb ext2load usb 0:1 $dtb_addr /boot/dts/ox820-pogoplug-pro.dtb setenv dt_load_initrd ext2load usb 0:1 $uinitrd_addr /boot/uInitrd setenv dt_load_uimage ext2load usb 0:1 $uimage_addr /boot/uImage setenv dt_bootm bootm $uimage_addr $uinitrd_addr $dtb_addr setenv dt_usb_boot run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm setenv dt_usb_bootcmd run usb_set_bootargs; run dt_usb_boot setenv dt_bootcmd_usb usb start; run dt_usb_bootcmd; usb stop; reset setenv bootcmd run dt_bootcmd_usb
Do a printenv and try to determine what you are missing based on what I have posted. Note that my boot env's are pretty simple compared to some of the really complicated netconsole / tftp ones I have seen on the forum so you might want to take a look at some of those if you wanna get funky.
Boot success!!
I hope -you Masters (Bodhi, SHV, Morph) - find my guide is useful. :) and it is a little benefit give back to community. Respect.
To be continued
No! But if you put the right stage1 bootloader and the right uboot to your SATA drive it might boot with them. You can't use the files which are provided here for Flash install. Moreover you must put the stage1 bootloader to your drive as it is done by OXNAS-SATA-Boot skript from ALARM forum. The uboot can be put to the filesystem of the first partition (Fat32 or ext4 depends on the stage1 loader).
I tested the following setups:
sda1: just für boot files like u-boot.img, u-boot.env, uImage, uInitrd (ext4 or fat32)
sda2: rootfs (ext3 or ext4)
sda3: linux swap partition
sda4: data (ext4)
or
sda1: rootfs including boot files (ext4)
sda2: linux swap partition
sda3: data (ext4)
For both setups you can use the same stage1 bootloader (u-boot-spl.bin) which reads the boot files from and stores boot environment to the first ext4 partition of the SATA drive. The device must support 512 Byte sector size either natively or by simulation.
u-boot files for SATA booting: http://pogoplug.square7.ch/ox820-sata-uboot.tar.gz (environment must be adapted with the serial console to boot the uImage and uInitrd files) - uImage, uInitrd and dtb file are for Pogoplug Pro - you might replace them with the right files of your kernel
can be download at :
http://forum.doozan.com/read.php?3,28162,28313#msg-28313
This is courtesy of LeggoMyEggo. I've upload the tarball Leggo sent me to Dropbox.
There are 2 tarballs in it. One from shv, one from WarheadsSE. It's easier to use the shv's: ox820-sata-uboot.tar.gz.
ox820-sata-uboot.tar.gz/*recommend and use modified disk_create.sh which not dd u-boot.img and uImage.img*/ oxnas_sata_boot.tgz /*this file contain older kernel maybe3.12 and uboot 1.1.2. the script need to dd uImage to first partition and rootfs on second partition,not success when booting kernel (uImage on partition 1,bad magic number)Try later*/
Dropbox download link:
https://www.dropbox.com/s/p9bo06us5fo2i3s/oxnasboottarball.zip
md5
8e016437146f40cdb51ad9dbd63b1bdd
Preparing SATA drive and storing u-boot-spl.bin alias stage1 to it:
http://archlinuxarm.org/forum/viewtopic.php?f=55&t=2146&sid=f4dc4863e3a93822a4f9e925b3cbda45
You must execute the steps from the ALARM script until stage1 file (u-boot-spl.bin from my package must be used instead the provided stage1 file) is stored to the HDD.
You must adapt the following lines of the boot environment:
dt_ide_bootcmd=run ide_set_bootargs; run dt_ide_boot ide_set_bootargs=setenv bootargs root=/dev/sda1 rootfstype=ext4 console=ttyS0,115200 mem=128M
to be continued
http://forum.doozan.com/read.php?3,16017,19666#msg-19666
@Robert,
your boot environment looks OK for the old WarheadsSE booting procedure. It looks that you don't have the right rootfs on partition sda2 (ext3/partition name rootfs).
Nevertheless I want to recommend you to use new uboot. Bodhi already pointed you to my post: http://forum.doozan.com/read.php?3,16017,17297#msg-17297.
The device must support 512 Byte sector size either natively or by simulation.
Step1: prepare mbr partition table:
sda1: rootfs including boot files (ext4) with partition name rootfs
sda2: linux swap partition
sda3: data (ext4)
Step2: Extract the content of the archive http://pogoplug.cwsurf.de/ox820-sata-uboot.tar.gz (http://pogoplug.square7.ch/ox820-sata-uboot.tar.gz)to your rootfs partition
Step3: Prepare SATA booting by adapting and executing the following script
#!/bin/sh
# uncomment line below and set to the correct disk
#disk=/dev/sda
if [ -z "${disk}" ] ; then
echo "You must uncomment/set the 'disk' variable"
exit -1
fi
workarea="/boot"
stage1File=$workarea/u-boot-spl.bin
perl <<EOF | dd of="$disk" bs=512
print "\x00" x 0x1a4;
print "\x00\x5f\x01\x00";
print "\x00\xdf\x00\x00";
print "\x00\x80\x00\x00";
print "\x00" x (0x1b0 -0x1a4 -12 );
print "\x22\x80\x00\x00";
print "\x22\x00\x00\x00";
print "\x00\x80\x00\x00";
EOF
if [ -f $stage1File ];then
echo "Writing stage 1"
dd if=$stage1File of="$disk" bs=512 seek=34
fi
Step4: Boot with serial cable connected and adapt the boot-env settings to your needs
Please also read the posts of morph027 starting from: http://forum.doozan.com/read.php?3,16017,18341#msg-18341
-shv
TBC
my really test:
1.gpt partition with one ext3 labeled "rootfs"
2.download
Dropbox download link:
https://www.dropbox.com/s/p9bo06us5fo2i3s/oxnasboottarball.zip
md5
8e016437146f40cdb51ad9dbd63b1bdd
ox820-sata-uboot.tar.gz/*recommend and use modified disk_create.sh which not dd u-boot.img and uImage.img*/ oxnas_sata_boot.tgz /*this file contain older kernel maybe3.12 and uboot 1.1.2. the script need to dd uImage to first partition and rootfs on second partition,not success when booting kernel (uImage on partition 1,bad magic number) ,320G hd not recognize correctly Try again later*/
3. make rootfs by untar Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2
mount /dev/sdb1 /mnt
cd /mnt
tar -xjvf /home/allan/Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2
4.untar 0x820-sata-uboot.tar.gz ,there will be a boot direcotory and enter boot directory.
5 cp u-boot.img u-boot.env to /boot directory of rootfs we just made
6 umount /dev/sdb1
7 make script disk_create_mod.sh as following saving and running on ox820-sata-uboot/boot directory.
ox820-sata-uboot #
#!/bin/sh
# uncomment line below and set to the correct disk
disk=/dev/sdb
#pay attention to fit yourself.this is my situation
if [ -z "${disk}" ] ; then
echo "You must uncomment/set the 'disk' variable"
exit -1
fi
workarea=.
stage1File=$workarea/u-boot-spl.bin
perl <<EOF | dd of="$disk" bs=512
print "\x00" x 0x1a4;
print "\x00\x5f\x01\x00";
print "\x00\xdf\x00\x00";
print "\x00\x80\x00\x00";
print "\x00" x (0x1b0 -0x1a4 -12 );
print "\x22\x80\x00\x00";
print "\x22\x00\x00\x00";
print "\x00\x80\x00\x00";
EOF
if [ -f $stage1File ];then
echo "Writing stage 1"
dd if=$stage1File of="$disk" bs=512 seek=34
fi
8
9
reboot.
boot log:
U-Boot SPL 2013.10-g3a0f380-dirty (Jul 26 2014 - 14:31:34)
Boot device: SATA
Attempting to set PLLA to 850 MHz ...
plla_ctrl0 : 0000020a
plla_ctrl1 : 00330000
plla_ctrl2 : 0065008b
plla_ctrl3 : 000000f1
PLLA Set
Bus 0: OK
Device 0:
** File not found /boot/bootargs.bin **
U-Boot 2013.10-g3a0f380-dirty (Jul 26 2014 - 10:18:57) for OXNAS
DRAM: 256 MiB
IDE: Bus 0: OK
Device 0: Model: ST3320418AS Firm: CC34 Ser#: 6VM1309B
Type: Hard Disk
Supports 48-bit addressing
Capacity: 305245.3 MB = 298.0 GB (625142448 x 512)
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net:
Led: GREEN
mii0
Main Loop
Hit any key to stop autoboot: 0
opps! my 256M ram mod is recognized.
but due to improper uboot env ,the linux can not boot.
modify uboot env
you can edit env in uboot envirment or use
mkenvimage -s <environment partition size> -o <output> <input file>
command from "u-boot-tool" package. I prefer latter. just save following code to a plan txt say ide-only.txt
and run
"mkenvimage -s 16380 -o u-boot.env ide-only.txt"
at /boot directory, overwrite old u-boot.env.
mtdids=nand0=41000000.nand mtdparts=mtdparts=41000000.nand:14m(boot),-(data) autoload=no baudrate=115200 bootargs=console=ttyS0,115200n8 bootcmd=run dt_bootcmd_ide bootdelay=3 console=console=ttyS0,115200n8 dtb_addr=0x62c00000 uimage_addr=0x60500000 uinitrd_addr=0x60e00000 dt_bootm=bootm $uimage_addr $uinitrd_addr $dtb_addr dt_ide_load_dtb=ext2load ide 0:1 $dtb_addr /boot/dts/ox820-pogoplug-pro.dtb dt_ide_load_uinitrd=ext2load ide 0:1 $uinitrd_addr /boot/uInitrd dt_ide_load_uimage=ext2load ide 0:1 $uimage_addr /boot/uImage dt_ide_boot=run dt_ide_load_uimage; run dt_ide_load_uinitrd; run dt_ide_load_dtb; run dt_bootm ide_set_bootargs=setenv bootargs root=/dev/sda1 rootfstype=ext3 console=ttyS0,115200 mem=256M dt_ide_bootcmd=run ide_set_bootargs; run dt_ide_boot dt_bootcmd_ide=ide start; run dt_ide_bootcmd; ide stop; reset ethact=mii0 ethaddr=00:25:31:01:C6:76 serverip=192.168.0.1 // ip of pc running nc or Hercules SETUP utility if_netconsole=ping $serverip ipaddr=192.168.0.100 //pogo's ip start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version preboot_nc=run if_netconsole start_netconsole stderr=serial stdin=serial stdout=serial
reboot.boot into linux, modify /etc/apt/sources.list
change the wheezy to jessie,
apt-get update; apt-get dist-upgrade
everything is ok
but if I change the wheezy to sid
apt-get update will show error.
install packages:mtd-utils and u-boot-tools for future use.
Edited 10 time(s). Last edit at 03/20/2017 01:42PM by youxiaojie.
|
Re: Tutorial of pure sata boot pogoplug pro March 12, 2017 12:30PM |
Registered: 11 years ago Posts: 1,303 |
youxiaojie Wrote:
-------------------------------------------------------
> I summed up the old post about sata boot for pogoplug pro and fixed some broken links
>
> Just for reference to others, I made a very detailed summary.
>
> Please revise my comment are there right in technical aspect. (?? if I have doubt - I will revise based on your comment)
>
> Synopsys:
> My device Pogo Plug P24 - V3 (nonpci) - oxnas 820
> I have serial connection,
>
> I Screw up UBoot in NAND - Therefore no boot from USB, and NOTHING appears on Serial console!!!
>
> Only way to boot is well prepared SATA because oxnas tries to boot Uboot on SATA then Uboot on NAND then USB. (?? is that right??)
>
> Steps
>
> 1. Get a SATA HDD. You have to delete all partitio
> n from it. Sorry :(
> 2. Put it to USB HDD frame. Attache to PC. Umount
> all partition if automount happened.
> 3. remove partitions, and create new.
>
Shouldn't tte above steps #2 and #3 part of step 1, i.e. 1a and 1b, respectively?
> fdisk /dev/sdb
> o - create a new empty DOS partition table
> n - Create part 1 (start with 2048 ; size: +2G )
> w - write
> q - exit
>
>
>
> 4. mkext4 fs.
>
>
I have never tried this. However, will the mkfs.ext4 (mkext4 fs) utility be able to format a DOS partition? BTW, mkfs.ext4 -L "Label" /dev/partition will create a label on the formatted partition at once.
>
>
> ( If you have problems with "mkfs.ext4 /dev/sdb is not a block special device."
> Detach USB _and_ reboot your PC. and attache again - will solve the problem...)
>
> 5 Labell it:
>
>
>
>
>
> 6.Mount rootfs
>
>
>
>
>
> 7. Prepare Sata uboot file on PC :
> a.) Extract the content Shv made ox820-sata-uboot.tar.gz to your PC
>
> cd /yourpath
> tar -xjf ox820-sata-uboot.tar.gz
>
Can you please clarify the above /yourpath, i.e. is /yourpath = /media/rootfs?
>
> (It is only a boot directory on your PC)
> Navigate to /yourpath/boot/dts directory and rename this files:
> -it is only needed in case noPCI devices like P24.
>
>
>
>
>
> b.) and copy modified /yourpath/boot directory to the rootfs partition.
>
> c.)Modify 2 lines in disk create script on your PC
> :
>
> c1.) disk=/dev/sdb
> c2.) workarea="/yourpath"
> d.) save changes
>
> 8. Now you have to run Sata uboot SCRIPT on your PC.
> It will write U-Boot SPL to Sata disk on the beginning (in the first 2048 sector) on the disk.
>
> 8a.) Umount - Just to be safe side: Not write to disk which is mounted... - skip if brave.
>
>
>
>
> 8b.) Run Sata uboot SCRIPT
>
>
I am completely lost here. My understanding is you wanna use the host uboot utility to create a uboot SPL (Pardon me, what the heck is SPL?) on the SATA HDD mounted on the host computer?
-------------------------------------------------------
> I summed up the old post about sata boot for pogoplug pro and fixed some broken links
>
> Just for reference to others, I made a very detailed summary.
>
> Please revise my comment are there right in technical aspect. (?? if I have doubt - I will revise based on your comment)
>
> Synopsys:
> My device Pogo Plug P24 - V3 (nonpci) - oxnas 820
> I have serial connection,
>
> I Screw up UBoot in NAND - Therefore no boot from USB, and NOTHING appears on Serial console!!!
>
> Only way to boot is well prepared SATA because oxnas tries to boot Uboot on SATA then Uboot on NAND then USB. (?? is that right??)
>
> Steps
>
> 1. Get a SATA HDD. You have to delete all partitio
> n from it. Sorry :(
> 2. Put it to USB HDD frame. Attache to PC. Umount
> all partition if automount happened.
> 3. remove partitions, and create new.
>
Shouldn't tte above steps #2 and #3 part of step 1, i.e. 1a and 1b, respectively?
> fdisk /dev/sdb
> o - create a new empty DOS partition table
> n - Create part 1 (start with 2048 ; size: +2G )
> w - write
> q - exit
>
>
>
> 4. mkext4 fs.
>
>
> mkfs.ext4 /dev/sdb1 >>
I have never tried this. However, will the mkfs.ext4 (mkext4 fs) utility be able to format a DOS partition? BTW, mkfs.ext4 -L "Label" /dev/partition will create a label on the formatted partition at once.
>
>
> ( If you have problems with "mkfs.ext4 /dev/sdb is not a block special device."
> Detach USB _and_ reboot your PC. and attache again - will solve the problem...)
>
> 5 Labell it:
>
>
> tune2fs -L "rootfs" /dev/sdb1 >>
>
>
>
> 6.Mount rootfs
>
>
> mount /dev/sdb1 /media/rootfs >>
>
>
>
> 7. Prepare Sata uboot file on PC :
> a.) Extract the content Shv made ox820-sata-uboot.tar.gz to your PC
>
> cd /yourpath
> tar -xjf ox820-sata-uboot.tar.gz
>
Can you please clarify the above /yourpath, i.e. is /yourpath = /media/rootfs?
>
> (It is only a boot directory on your PC)
> Navigate to /yourpath/boot/dts directory and rename this files:
> -it is only needed in case noPCI devices like P24.
>
>
> mv ox820-pogoplug-pro.dtb ox820-pogoplug-pro.dtb.ori > cp ox820-pogoplug-classic.dtb ox820-pogoplug-pro.dtb >>
>
>
>
> b.) and copy modified /yourpath/boot directory to the rootfs partition.
>
> c.)Modify 2 lines in disk create script on your PC
> :
>
> c1.) disk=/dev/sdb
> c2.) workarea="/yourpath"
> d.) save changes
>
> 8. Now you have to run Sata uboot SCRIPT on your PC.
> It will write U-Boot SPL to Sata disk on the beginning (in the first 2048 sector) on the disk.
>
> 8a.) Umount - Just to be safe side: Not write to disk which is mounted... - skip if brave.
>
>
> umount rootfs >>
>
>
> 8b.) Run Sata uboot SCRIPT
>
>
> ./disk_create_shv >>
I am completely lost here. My understanding is you wanna use the host uboot utility to create a uboot SPL (Pardon me, what the heck is SPL?) on the SATA HDD mounted on the host computer?
|
Re: Tutorial of pure sata boot pogoplug pro March 12, 2017 05:10PM |
Admin Registered: 13 years ago Posts: 18,898 |
@youxiaojie,
Thanks for gathering the info into a tutorial and testing it, great job!
The instruction can be improved for clarity, so I will post suggestions to make it a little easier for users who are not familiar with embedded Linux..
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Thanks for gathering the info into a tutorial and testing it, great job!
The instruction can be improved for clarity, so I will post suggestions to make it a little easier for users who are not familiar with embedded Linux..
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Tutorial of pure sata boot pogoplug pro March 12, 2017 05:24PM |
Admin Registered: 13 years ago Posts: 18,898 |
@habibie,
> I am completely lost here. My understanding is you
> wanna use the host uboot utility to create a uboot
> SPL (Pardon me, what the heck is SPL?) on the SATA
> HDD mounted on the host computer?
Our OX820 u-boot installation has 2 images. SPL image the 1st stage boot loader, u-boot image is the 2nd stage bootloader.
The process of creating the SATA-only boot disk can be done on any Linux host. After that, you'd take the HDD to the Pogo V3 and boot it.This process is different from installing u-boot and SPL on NAND.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 03/12/2017 05:27PM by bodhi.
> I am completely lost here. My understanding is you
> wanna use the host uboot utility to create a uboot
> SPL (Pardon me, what the heck is SPL?) on the SATA
> HDD mounted on the host computer?
Our OX820 u-boot installation has 2 images. SPL image the 1st stage boot loader, u-boot image is the 2nd stage bootloader.
Quote
http://forum.doozan.com/read.php?3,16017
Download U-Boot image at Dropbox:
uboot.2015.10-tld-1.ox820.bodhi.tar
md5
90afc75a29601cdb60adc7afd8bbda26
This archive contains the following 4 files:
uboot.2015.10-tld-1.ox820.mtd0.img
uboot.spl.2013.10.ox820.850mhz.mtd0.img
uboot.2013.10-tld-5.ox820.environment
uboot.2013.10-tld-5.ox820.environment.img
The process of creating the SATA-only boot disk can be done on any Linux host. After that, you'd take the HDD to the Pogo V3 and boot it.This process is different from installing u-boot and SPL on NAND.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 03/12/2017 05:27PM by bodhi.
|
Re: Tutorial of pure sata boot pogoplug pro March 13, 2017 12:28AM |
Admin Registered: 13 years ago Posts: 18,898 |
@ youxiaojie,
1. When you are quoting other people, use the "insert quoted text" button.
2. Use "formatted code" button for all commands and logs.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
1. When you are quoting other people, use the "insert quoted text" button.
2. Use "formatted code" button for all commands and logs.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Tutorial of native sata boot for pogoplug pro March 13, 2017 11:47AM |
Registered: 11 years ago Posts: 214 |
@ youxiaojie,
I want to recommend to start form a basic process and add additional description.
============================================================================
The device must support 512 Byte sector size either natively or by simulation.
Step1: Attach the target drive to any linux device, e.g. PC or a working Pogoplug
Step2: Prepare mbr partition table:
Step3: Format sda1 partition with ext4 filesystem and "rootfs" as name.
Step4: Mount sda1 partition
Step5: Extract the content of the archive http://zyxel.diskstation.eu/Pogoplug/ox820-sata-uboot.tar.gz to the rootfs partition. This should create a boot directory with uboot.img, uboot.env and other files. The outdated kernel and dts files can be deleted so that only uboot.img and uboot.env stay in the /boot directory.
Step6: Prepare SATA booting by adapting and executing the following script (disk is the drive you want to modify, workarea is the directory which contains the uboot-spl.bin, e.g. /boot of the rootfs partition)
Step7: Extract bodhi's latest rootfs package to the rootfs partition and check if uImage, uInitrd and the right dts file are available in the /boot directory.
Step8: Attach the drive to the target Pogoplug device
Step9: Boot with serial cable connected, stop the boot countdown and adapt the boot-env settings to your needs, e.g. exchange the name of the dts file if you are using non Pro device
Step10: Check if Pogoplug boots the rootfs completely
Step11: (optional) Update the kernel to bodhi's latest one
Please also read the posts of morph027 starting from: http://forum.doozan.com/read.php?3,16017,18341#msg-18341
Source code download: http://pogoplug.square7.de/Pogoplug/u-boot-oxnas-sata.tar.bz2
Description how to compile: https://github.com/kref/u-boot-oxnas/wiki/uboot-for-sata but use ox820_ext4_config instead of ox820_fat_config
============================================================================
The idea behind is that some magic dust (WarheadsSE) and uboot-spl.bin is written to the beginning of the SATA disk. If this is done the processor will boot from SATA harddrive and not from flash - absolutely nothing is read from flash. If uboot-spl.bin is executed it will read uboot.img and uboot.env from the /boot directory of the first partition. If uboot is executed it will boot the system based on the content of uboot.env.
-shv
Edited 28 time(s). Last edit at 05/24/2020 05:13AM by shv.
I want to recommend to start form a basic process and add additional description.
============================================================================
The device must support 512 Byte sector size either natively or by simulation.
Step1: Attach the target drive to any linux device, e.g. PC or a working Pogoplug
Step2: Prepare mbr partition table:
sda1: rootfs including boot files (ext4) with partition name rootfs sda2: linux swap partition sda3: data (ext4)
Step3: Format sda1 partition with ext4 filesystem and "rootfs" as name.
Step4: Mount sda1 partition
Step5: Extract the content of the archive http://zyxel.diskstation.eu/Pogoplug/ox820-sata-uboot.tar.gz to the rootfs partition. This should create a boot directory with uboot.img, uboot.env and other files. The outdated kernel and dts files can be deleted so that only uboot.img and uboot.env stay in the /boot directory.
Step6: Prepare SATA booting by adapting and executing the following script (disk is the drive you want to modify, workarea is the directory which contains the uboot-spl.bin, e.g. /boot of the rootfs partition)
#!/bin/sh
# uncomment line below and set to the correct disk
#disk=/dev/sda
if [ -z "${disk}" ] ; then
echo "You must uncomment/set the 'disk' variable"
exit -1
fi
workarea="/boot"
stage1File=$workarea/u-boot-spl.bin
perl <<EOF | dd of="$disk" bs=512
print "\x00" x 0x1a4;
print "\x00\x5f\x01\x00";
print "\x00\xdf\x00\x00";
print "\x00\x80\x00\x00";
print "\x00" x (0x1b0 -0x1a4 -12 );
print "\x22\x80\x00\x00";
print "\x22\x00\x00\x00";
print "\x00\x80\x00\x00";
EOF
if [ -f $stage1File ];then
echo "Writing stage 1"
dd if=$stage1File of="$disk" bs=512 seek=34
fi
Step7: Extract bodhi's latest rootfs package to the rootfs partition and check if uImage, uInitrd and the right dts file are available in the /boot directory.
Step8: Attach the drive to the target Pogoplug device
Step9: Boot with serial cable connected, stop the boot countdown and adapt the boot-env settings to your needs, e.g. exchange the name of the dts file if you are using non Pro device
Step10: Check if Pogoplug boots the rootfs completely
Step11: (optional) Update the kernel to bodhi's latest one
Please also read the posts of morph027 starting from: http://forum.doozan.com/read.php?3,16017,18341#msg-18341
Source code download: http://pogoplug.square7.de/Pogoplug/u-boot-oxnas-sata.tar.bz2
Description how to compile: https://github.com/kref/u-boot-oxnas/wiki/uboot-for-sata but use ox820_ext4_config instead of ox820_fat_config
============================================================================
The idea behind is that some magic dust (WarheadsSE) and uboot-spl.bin is written to the beginning of the SATA disk. If this is done the processor will boot from SATA harddrive and not from flash - absolutely nothing is read from flash. If uboot-spl.bin is executed it will read uboot.img and uboot.env from the /boot directory of the first partition. If uboot is executed it will boot the system based on the content of uboot.env.
-shv
Edited 28 time(s). Last edit at 05/24/2020 05:13AM by shv.
|
Re: Tutorial of native sata boot for pogoplug pro March 13, 2017 02:57PM |
Registered: 11 years ago Posts: 214 |
This is the script to deactivate automatic booting from SATA HDD:
Edited 2 time(s). Last edit at 03/13/2017 03:02PM by shv.
#!/bin/sh
# uncomment line below and set to the correct disk
#disk=/dev/sda
if [ -z "${disk}" ] ; then
echo "You must uncomment/set the 'disk' variable"
exit -1
fi
perl <<EOF | dd of="$disk" bs=512
print "\x00" x 0x1bc;
EOF
- shvEdited 2 time(s). Last edit at 03/13/2017 03:02PM by shv.
|
Re: Tutorial of native sata boot for pogoplug pro March 13, 2018 10:37PM |
Registered: 6 years ago Posts: 183 |
Bodhi, ok starting from scratch:
Partitioned sdf1 labeled "rootfs" to ext3 : size
3.77 gb (looks tiny compared to the drive size)
Partitioned sdf2 Labeled " linux-swap" to Linux Swap: 292 gb (probably overkill)
Partitioned sdf3 Labeled "data" to Ext4: 402 gb, (this was a spare drive so its all I had available, hence large partitions)
unmounted
opened terminal
entered:sudo su
entered password
entered:mkfs.ext3 /dev/sdf1
it loaded however unable to copy terminal at this time.
so far that is as far as I got tonight, eastern time zone, gonna call it a night :) thanks EW108
Partitioned sdf1 labeled "rootfs" to ext3 : size
3.77 gb (looks tiny compared to the drive size)
Partitioned sdf2 Labeled " linux-swap" to Linux Swap: 292 gb (probably overkill)
Partitioned sdf3 Labeled "data" to Ext4: 402 gb, (this was a spare drive so its all I had available, hence large partitions)
unmounted
opened terminal
entered:sudo su
entered password
entered:mkfs.ext3 /dev/sdf1
it loaded however unable to copy terminal at this time.
so far that is as far as I got tonight, eastern time zone, gonna call it a night :) thanks EW108
|
Re: Tutorial of native sata boot for pogoplug pro March 14, 2018 01:21AM |
Admin Registered: 13 years ago Posts: 18,898 |
Here is what we should see in the log: copy and paste the terminal session that has all commands executed and its output, from step 1 to step 9 in this post:
https://forum.doozan.com/read.php?2,32994,33021#msg-33021
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
https://forum.doozan.com/read.php?2,32994,33021#msg-33021
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Tutorial of native sata boot for pogoplug pro March 14, 2018 01:42PM |
Registered: 6 years ago Posts: 183 |
bodhi, first I tried the TAR you gave me that I download, it put in the files but there was no boot folder:
root@Desktop-MS-7578:/media/russ/rootfs# tar xvxf /home/russ/Downloads/uboot.2015.10-tld-2.ox820.bodhi.tar
Then I tried to download from the url in step 5 however the link gives me a 404 error so I tried to directly extract the url that was in step 5:
root@Desktop-MS-7578:/media/russ/rootfs#
kinda stuck right there for now but this is the ls for the rootfs drive so far:
was able to get the /boot installed the following is the log of what I did next, am I going in the right direction?
Thanks EW108
-----
moderator: use code tags
Edited 4 time(s). Last edit at 03/15/2018 02:41PM by bodhi.
root@Desktop-MS-7578:/media/russ/rootfs# tar xvxf /home/russ/Downloads/uboot.2015.10-tld-2.ox820.bodhi.tar
uboot.2015.10-tld-2.ox820.mtd0.img uboot.spl.2013.10.ox820.850mhz.mtd0.img uboot.2015.10-tld-2.ox820.environment uboot.2015.10-tld-2.ox820.environment.img root@Desktop-MS-7578:/media/russ/rootfs#
Then I tried to download from the url in step 5 however the link gives me a 404 error so I tried to directly extract the url that was in step 5:
root@Desktop-MS-7578:/media/russ/rootfs# tar xvxf http://pogoplug.cwsurf.de/ox820-sata-uboot.tar.gz tar: Cannot connect to http: resolve failed
root@Desktop-MS-7578:/media/russ/rootfs#
kinda stuck right there for now but this is the ls for the rootfs drive so far:
root@Desktop-MS-7578:/media/russ/rootfs# ls lost+found uboot.2015.10-tld-2.ox820.environment uboot.2015.10-tld-2.ox820.environment.img uboot.2015.10-tld-2.ox820.mtd0.img uboot.spl.2013.10.ox820.850mhz.mtd0.img root@Desktop-MS-7578:/media/russ/rootfs#
was able to get the /boot installed the following is the log of what I did next, am I going in the right direction?
root@Desktop-MS-7578:/media/russ/rootfs# ls boot lost+found uboot.2015.10-tld-2.ox820.environment uboot.2015.10-tld-2.ox820.environment.img uboot.2015.10-tld-2.ox820.mtd0.img uboot.spl.2013.10.ox820.850mhz.mtd0.img
root@Desktop-MS-7578:/media/russ/rootfs# cd boot root@Desktop-MS-7578:/media/russ/rootfs/boot# ls dts u-boot.img uImage uInitrd u-boot.env u-boot-spl.bin uImage_2.6.31.14_OX820_1.2_shv.Proroot@Desktop-MS-7578:/media/russ/rootfs/boot#
root@Desktop-MS-7578:/media/russ/rootfs# /bin/sh
# disk=/dev/sdf1
# if [ -z "${disk}" ] ; then
echo "You must uncomment/set the 'disk' variable"
exit -1> >
> fi
# workarea="/boot"
# perl <<EOF | dd of="$disk" bs=512
print "\x00" x 0x1a4;
print "\x00\x5f\x01\x00";
print "\x00\xdf\x00\x00";
print "\x00\x80\x00\x00";
print "\x00" x (0x1b0 -0x1a4 -12 );
print "\x22\x80\x00\x00";
print "\x22\x00\x00\x00";
print "\x00\x80\x00\x00";
EOF> > > > > > > > > if [ -f $stage1File ];then
echo "Writing stage 1"
dd if=$stage1File of="$disk" bs=512 seek=34> > fi
>
Thanks EW108
-----
moderator: use code tags
Edited 4 time(s). Last edit at 03/15/2018 02:41PM by bodhi.
|
Re: Tutorial of native sata boot for pogoplug pro March 15, 2018 08:31AM |
Registered: 9 years ago Posts: 104 |
You can take a look at my sata 'installer" from this post: https://forum.doozan.com/read.php?2,16044,23122#msg-23122
I will have it updated to the latest kernel and rootfs soon.
I will have it updated to the latest kernel and rootfs soon.
|
Re: Tutorial of native sata boot for pogoplug pro March 15, 2018 02:47PM |
Admin Registered: 13 years ago Posts: 18,898 |
echowarrior108,
It looks like you did it correctly. But you did not post enough information so I can't tell for sure. You might have missed some steps.
You could try schee installer to see if it works for you.
If it does, then just install new u-boot to NAND and then format a USB rootfs to use as system drive. Once you can boot with NAND u-boot and USB rootfs, you can set up your SATA drive as normal boot drive (without the magic dust that were written by disk_create).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
It looks like you did it correctly. But you did not post enough information so I can't tell for sure. You might have missed some steps.
You could try schee installer to see if it works for you.
If it does, then just install new u-boot to NAND and then format a USB rootfs to use as system drive. Once you can boot with NAND u-boot and USB rootfs, you can set up your SATA drive as normal boot drive (without the magic dust that were written by disk_create).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Tutorial of native sata boot for pogoplug pro March 16, 2018 12:57PM |
Registered: 6 years ago Posts: 183 |
|
Re: Tutorial of native sata boot for pogoplug pro March 16, 2018 01:23PM |
Registered: 6 years ago Posts: 183 |
|
Re: Tutorial of native sata boot for pogoplug pro March 17, 2018 12:48AM |
Registered: 6 years ago Posts: 183 |
Hi Bodhi,
ok, here is the log for what I did to the SATA drive using Schnee's install :
# ./pogoSATA.sh: line 52: [: =: unary operator expected
this is all I get:
# picocom -b 115200 /dev/ttyUSB0
then it just hangs:
the ethernet lights do flash, I checked the router but its not there either.
got same results on second usb to tty adapter, have 2 just in case:)
thanks echowarrior108
-----
Moderator: please use code tags, it is not easy to read log without it.
np, sorry, still just learning:)
Edited 3 time(s). Last edit at 03/17/2018 12:14PM by echowarrior108.
ok, here is the log for what I did to the SATA drive using Schnee's install :
# ./pogoSATA.sh: line 52: [: =: unary operator expected
WARNING!!!!
ALL DATA ON /dev/sdb WILL BE DESTROYED!
PROCEED? (y/N)
y
Deleting partitions...
Welcome to fdisk (util-linux 2.30.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): Created a new DOS disklabel with disk identifier 0x0ccd13dd.
Command (m for help): The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.
Creating partions....
Welcome to fdisk (util-linux 2.30.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): Partition type
p primary (0 primary, 0 extended, 4 free)
e extended (container for logical partitions)
Select (default p): Partition number (1-4, default 1): First sector (2048-1465149167, default 2048): Last sector, +sectors or +size{K,M,G,T,P} (2048-1465149167, default 1465149167):
Created a new partition 1 of type 'Linux' and of size 16 MiB.
Partition #1 contains a ext3 signature.
Command (m for help): Partition type
p primary (1 primary, 0 extended, 3 free)
e extended (container for logical partitions)
Select (default p): Partition number (2-4, default 2): First sector (34816-1465149167, default 34816): Last sector, +sectors or +size{K,M,G,T,P} (34816-1465149167, default 1465149167):
Created a new partition 2 of type 'Linux' and of size 4 GiB.
Command (m for help): Partition type
p primary (2 primary, 0 extended, 2 free)
e extended (container for logical partitions)
Select (default p): Partition number (3,4, default 3): First sector (8423424-1465149167, default 8423424): Last sector, +sectors or +size{K,M,G,T,P} (8423424-1465149167, default 1465149167):
Created a new partition 3 of type 'Linux' and of size 694.6 GiB.
Command (m for help): The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.
Done!
Formating /dev/sdb1...mkfs.fat 4.1 (2017-01-24)
Done!
Formating /dev/sdb2...mke2fs 1.43.5 (04-Aug-2017)
Creating filesystem with 1048576 4k blocks and 262144 inodes
Filesystem UUID: 361e9fab-7e67-4224-91a1-f2afd64c0d47
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736
Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done
Done!
Formating /dev/sdb3...mke2fs 1.43.5 (04-Aug-2017)
Creating filesystem with 182090718 4k blocks and 45522944 inodes
Filesystem UUID: 6bd15947-48ad-457b-ad52-1f68dd25b01a
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000
Allocating group tables: done
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
Done!
Copying uBoot files...rmdir: failed to remove './boot': Directory not empty
Done!
Create magic...0+1 records in
0+1 records out
444 bytes copied, 0.0177294 s, 25.0 kB/s
Done!
Writing stage 156+1 records in
56+1 records out
29172 bytes (29 kB, 28 KiB) copied, 0.0312296 s, 934 kB/s
Mount rootfs... Done!
Copy root filesystem... Done!
Extract rootfs... Done!
Copying new kernel... Done!
Finalizing...rmdir: failed to remove 'rfs': Directory not empty
umount: /dev/sdb1: not mounted.
umount: /dev/sdb2: not mounted.
umount: /dev/sdb3: not mounted.
Done!
Finished!
Connect the drive to the Pogo and boot! Connect a serial console and an enthernet cable to the Pogo and boot it. Let .1stboot.sh to finish after you loged on!
Username: root, Password:root
ENJOY!
this is all I get:
# picocom -b 115200 /dev/ttyUSB0
picocom v2.2 port is : /dev/ttyUSB0 flowcontrol : none baudrate is : 115200 parity is : none databits are : 8 stopbits are : 1 escape is : C-a local echo is : no noinit is : no noreset is : no nolock is : no send_cmd is : sz -vv receive_cmd is : rz -vv -E imap is : omap is : emap is : crcrlf,delbs, Type [C-a] [C-h] to see available commands Terminal ready ���ZU�
then it just hangs:
the ethernet lights do flash, I checked the router but its not there either.
got same results on second usb to tty adapter, have 2 just in case:)
thanks echowarrior108
-----
Moderator: please use code tags, it is not easy to read log without it.
np, sorry, still just learning:)
Edited 3 time(s). Last edit at 03/17/2018 12:14PM by echowarrior108.
|
Re: Tutorial of native sata boot for pogoplug pro March 17, 2018 05:49AM |
Registered: 9 years ago Posts: 104 |
|
Re: Tutorial of native sata boot for pogoplug pro March 17, 2018 10:05AM |
Registered: 6 years ago Posts: 183 |
Hi Shnee. The serial is connect directly from audio connector that fits in the serial port of the with three wires, mine are green for ground, white for txd and black for rxd and going to the USB to ttl with the same configuration. then using a USB port on my desktop pc.
As far as the sata drive, I am really a novice with this thing so I am not sure if the SATA port powers the drive or not. You may be laughing but its ok:) I simply have never done Linux so I am only guessing that this was right:)
My original plan was to simply run it from the USB port and then it lost connection to my ethernet so I am learning this as I go...
ok after writing this I tried this, I turned off everything I connected the power supply from the desktop pc to the other connector on th SATA drive, still got nothing , so then I turned everything off again and reversed the tdx and rdx on the usb adapter and got something, kinda cool I am actually kinda excited to see something but for some reason I cannot copy and pasted the text but I did take a picture (see Attachment) because I could not screenshot it either. so now I have to figure out where to go from there :)
thanks for the help , I really want to make this thing work:) echowarrior108
Edited 1 time(s). Last edit at 03/17/2018 10:47AM by echowarrior108.
As far as the sata drive, I am really a novice with this thing so I am not sure if the SATA port powers the drive or not. You may be laughing but its ok:) I simply have never done Linux so I am only guessing that this was right:)
My original plan was to simply run it from the USB port and then it lost connection to my ethernet so I am learning this as I go...
ok after writing this I tried this, I turned off everything I connected the power supply from the desktop pc to the other connector on th SATA drive, still got nothing , so then I turned everything off again and reversed the tdx and rdx on the usb adapter and got something, kinda cool I am actually kinda excited to see something but for some reason I cannot copy and pasted the text but I did take a picture (see Attachment) because I could not screenshot it either. so now I have to figure out where to go from there :)
thanks for the help , I really want to make this thing work:) echowarrior108
Edited 1 time(s). Last edit at 03/17/2018 10:47AM by echowarrior108.
|
Re: Tutorial of native sata boot for pogoplug pro March 17, 2018 01:41PM |
Registered: 6 years ago Posts: 183 |
Bodhi and Shnee, I have been able to access repeatedly and my terminal allows me to copy and paste text only after reboot for some reason but here is where I am at so far:
Thanks for getting me in!!!!! will do more later:) Echowarrior108
Edited 5 time(s). Last edit at 03/17/2018 02:17PM by echowarrior108.
root@Desktop-MS-7578:/home/russ# picocom -b 115200 /dev/ttyUSB0
picocom v2.2
port is : /dev/ttyUSB0
flowcontrol : none
baudrate is : 115200
parity is : none
databits are : 8
stopbits are : 1
escape is : C-a
local echo is : no
noinit is : no
noreset is : no
nolock is : no
send_cmd is : sz -vv
receive_cmd is : rz -vv -E
imap is :
omap is :
emap is : crcrlf,delbs,
Type [C-a] [C-h] to see available commands
Terminal ready
U-Boot SPL 2013.10-ga72eb8f-dirty (Feb 19 2014 - 15:21:12)
Boot device: SATA
Attempting to set PLLA to 800 MHz ...
plla_ctrl0 : 0000030a
plla_ctrl1 : 00400000
plla_ctrl2 : 007f0068
plla_ctrl3 : 00000193
PLLA Set
Bus 0: OK
Device 0:
reading bootargs.bin
reading u-boot.img
reading u-boot.img
U-Boot 2013.10-ga72eb8f-dirty (Feb 19 2014 - 15:21:12) for OXNAS
DRAM: 128 MiB
IDE: Bus 0: OK
Device 0: Model: WDC WD7500BPKT-75PK4T0 Firm: 01.01A01 Ser#: WD-WXD1A61R3456
Type: Hard Disk
Supports 48-bit addressing
Capacity: 715404.8 MB = 698.6 GB (1465149168 x 512)
NAND: 128 MiB
reading u-boot.env
In: serial
Out: serial
Err: serial
Net: mii0
## Error: "safeboot" not defined
Hit any key to stop autoboot: 0
** File not found /boot/uImage **
** File not found /boot/dts/ox820-pogoplug-classic.dtb **
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
Wrong Image Format for bootm command
ERROR: can't get kernel image!
OX820 # printenv
SET_dtb=fdt addr ${fdtaddr} ; fdt header
autoload=no
baudrate=115200
bootcmd=run ideboot
bootdelay=3
bootnew=bootm 60000000 - 61000000
bootold=bootm 60000000
console=console=ttyS0,115200n8
ethact=mii0
ethaddr=74:F0:6D:6A:1D:17
ext2_dtb=ext2load ide 0:2 61000000 /boot/dts/ox820-pogoplug-classic.dtb
ext2_ideboot=run ext2_uimage ; run ext2_dtb ; run SET_dtb ; run bootnew
ext2_uimage=ext2load ide 0:2 60000000 /boot/uImage
ext4_dtb=ext4load ide 0:2 61000000 /boot/dts/ox820-pogoplug-classic.dtb
ext4_ideboot=run ext4_uimage ; run ext4_dtb ; run SET_dtb ; run bootnew
ext4_uimage=ext4load ide 0:2 60000000 /boot/uImage
fdtaddr=61000000
filesize=1b79
ideboot=run ext4_ideboot
idebootold=${loadold} ;${bootold}
imgaddr=60000000
ipaddr=10.0.0.71
keypressed=1
mtdids=nand0=41000000.nand
mtdparts=mtdparts=41000000.nand:14m(boot),-(data)
netcon=echo switch to net console;setenv stderr nc;setenv stdin nc;setenv stdout nc;echo switch to net console
preboot=run safeboot
serialcon=echo switch to serial console;setenv stderr serial;setenv stdin serial;setenv stdout serial;echo switch to serial console
stderr=serial
stdin=serial
stdout=serial
updboot=bootp;tftp 60000000 u-boot.img;ide write 60000000 400 400
Environment size: 1267/16380 bytes
OX820 #
Thanks for getting me in!!!!! will do more later:) Echowarrior108
Edited 5 time(s). Last edit at 03/17/2018 02:17PM by echowarrior108.
|
Re: Tutorial of native sata boot for pogoplug pro March 17, 2018 04:27PM |
Admin Registered: 13 years ago Posts: 18,898 |
echowarrior108,
Congrats :)
At this point, it is unbricked :) Now you can boot into Debian. And set up booting with USB rootfs. Keep this HDD as a rescue mechanism, until you can boot with u-boot in NAND and USB rootfs. After that, you can switch back to HDD rootfs if you like to do that.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Congrats :)
At this point, it is unbricked :) Now you can boot into Debian. And set up booting with USB rootfs. Keep this HDD as a rescue mechanism, until you can boot with u-boot in NAND and USB rootfs. After that, you can switch back to HDD rootfs if you like to do that.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Tutorial of native sata boot for pogoplug pro March 17, 2018 04:28PM |
Admin Registered: 13 years ago Posts: 18,898 |
@schnee,
Good works :)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Good works :)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Tutorial of native sata boot for pogoplug pro March 17, 2018 05:16PM |
Registered: 6 years ago Posts: 183 |
You Guys are all Awesome!!!!!!!!! I got a ways to go, but getting this unbricked is supercool!!!!probably will have more questions along the way, but gonna keep plugging (pun intended) away at it! Thanks!!!!!
echowarrior108
Edited 1 time(s). Last edit at 03/17/2018 05:18PM by echowarrior108.
echowarrior108
Edited 1 time(s). Last edit at 03/17/2018 05:18PM by echowarrior108.
|
Re: Tutorial of native sata boot for pogoplug pro March 19, 2018 07:13PM |
Registered: 6 years ago Posts: 183 |
I am seriously a novice at linux, been doing windows for decades but this is new turf to me. I have not located a way step by step to setup the usb drive, I have a 16 gb Sandisk , is there a simple link to get me to the right place?
I have no trouble getting into the pogoplug with the serial but past that I am not sure what to do, kinda feeling stupid asking because I am sure that its been asked on other posts:)
right now I am right where I was when I booted up, I am sure I am doing it wrong!!
also this is what I find in nand ,is this right?
if this was water and I was a horse I would dehydrate to death :) lol
thanks , Echowarrior108
Edited 2 time(s). Last edit at 03/19/2018 07:24PM by echowarrior108.
I have no trouble getting into the pogoplug with the serial but past that I am not sure what to do, kinda feeling stupid asking because I am sure that its been asked on other posts:)
right now I am right where I was when I booted up, I am sure I am doing it wrong!!
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
OX820 # usb help
usb - USB sub-system
Usage:
usb start - start (scan) USB controller
usb reset - reset (rescan) USB controller
usb stop [f] - stop USB [f]=force stop
usb tree - show USB device tree
usb info [dev] - show available USB devices
usb test [dev] [port] [mode] - set USB 2.0 test mode
(specify port 0 to indicate the device's upstream port)
Available modes: J, K, S[E0_NAK], P[acket], F[orce_Enable]
usb storage - show details of USB storage devices
usb dev [dev] - show or set current USB storage device
usb part [dev] - print partition table of one or all USB storage devices
usb read addr blk# cnt - read `cnt' blocks starting at block `blk#'
to memory address `addr'
usb write addr blk# cnt - write `cnt' blocks starting at block `blk#'
from memory address `addr'
OX820 # usb tree
USB device tree:
1 Hub (480 Mb/s, 0mA)
| u-boot EHCI Host Controller
|
+-2 Hub (480 Mb/s, 100mA)
| USB2.0 Hub
|
+-3 Mass Storage (480 Mb/s, 200mA)
SanDisk Cruzer 4C530001170203104075
also this is what I find in nand ,is this right?
OX820 # nand info Device 0: nand0, sector size 128 KiB Page size 2048 b OOB size 64 b Erase size 131072 b OX820 #
if this was water and I was a horse I would dehydrate to death :) lol
thanks , Echowarrior108
Edited 2 time(s). Last edit at 03/19/2018 07:24PM by echowarrior108.
|
Re: Tutorial of native sata boot for pogoplug pro March 20, 2018 03:08AM |
Admin Registered: 13 years ago Posts: 18,898 |
echowarrior108,
> I have no trouble getting into the pogoplug with
> the serial but past that I am not sure what to do,
> kinda feeling stupid asking because I am sure that
> its been asked on other posts:)
No, there is alway the first time for everything :) so far you did great!
Good. That's a good USB drive to use as your rootfs.
To boot into a full Debian rootfs:
1. Create a USB rootfs using Debian-4.4.54-oxnas-tld-1-rootfs-bodhi.tar.bz2, following this instruction (very closely to the letter, i.e. copy/paste), ask question if you can't run a certain commands on the Linux box that you are doing this installation):
https://forum.doozan.com/read.php?2,16044
2. Come back and I'll help you adjusting u-boot envs to boot into that USB rootfs.
3. After that, you can install u-boot 2015.10 using this instruction:
https://forum.doozan.com/read.php?3,16017
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I have no trouble getting into the pogoplug with
> the serial but past that I am not sure what to do,
> kinda feeling stupid asking because I am sure that
> its been asked on other posts:)
No, there is alway the first time for everything :) so far you did great!
Quote
> OX820 # usb tree
> USB device tree:
> 1 Hub (480 Mb/s, 0mA)
> | u-boot EHCI Host Controller
> |
> +-2 Hub (480 Mb/s, 100mA)
> | USB2.0 Hub
> |
> +-3 Mass Storage (480 Mb/s, 200mA)
> SanDisk Cruzer 4C530001170203104075
Good. That's a good USB drive to use as your rootfs.
To boot into a full Debian rootfs:
1. Create a USB rootfs using Debian-4.4.54-oxnas-tld-1-rootfs-bodhi.tar.bz2, following this instruction (very closely to the letter, i.e. copy/paste), ask question if you can't run a certain commands on the Linux box that you are doing this installation):
https://forum.doozan.com/read.php?2,16044
2. Come back and I'll help you adjusting u-boot envs to boot into that USB rootfs.
3. After that, you can install u-boot 2015.10 using this instruction:
https://forum.doozan.com/read.php?3,16017
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Tutorial of native sata boot for pogoplug pro March 20, 2018 10:43AM |
Registered: 6 years ago Posts: 183 |
|
Re: Tutorial of native sata boot for pogoplug pro March 20, 2018 10:04PM |
Registered: 6 years ago Posts: 183 |
Bodhi, Ok I believe I have successfully create the usb rootfs;
didn't appear to be any issues:)
I did alter some envs for the:
setenv ethaddr 00:**:**:**:**:**
setenv ipaddr 192.168.**.*** ,
and setenv serverip 192.168.**.***
I am omitting the real numbers for security:)
here is the printenv thus far:
gonna just hold up here until you get back to me, thanks a ton! Ecowarrior108
didn't appear to be any issues:)
I did alter some envs for the:
setenv ethaddr 00:**:**:**:**:**
setenv ipaddr 192.168.**.*** ,
and setenv serverip 192.168.**.***
I am omitting the real numbers for security:)
here is the printenv thus far:
OX820 # printenv
SET_dtb=fdt addr ${fdtaddr} ; fdt header
autoload=no
baudrate=115200
bootcmd=run ideboot
bootcmd_l=set_bootargs_lede
bootdelay=3
bootnew=bootm 60000000 - 61000000
bootold=bootm 60000000
console=console=ttyS0,115200n8
ethact=mii0
ethaddr=00:**:**:**:**:**
ext2_dtb=ext2load ide 0:2 61000000 /boot/dts/ox820-pogoplug-classic.dtb
ext2_ideboot=run ext2_uimage ; run ext2_dtb ; run SET_dtb ; run bootnew
ext2_uimage=ext2load ide 0:2 60000000 /boot/uImage
ext4_dtb=ext4load ide 0:2 61000000 /boot/dts/ox820-pogoplug-classic.dtb
ext4_ideboot=run ext4_uimage ; run ext4_dtb ; run SET_dtb ; run bootnew
ext4_uimage=ext4load ide 0:2 60000000 /boot/uImage
fdtaddr=61000000
filesize=1b79
ideboot=run ext4_ideboot
idebootold=${loadold} ;${bootold}
imgaddr=60000000
ipaddr=192.168.**.***
keypressed=1
mtdids=nand0=41000000.nand
mtdparts=mtdparts=orion_nand:0x100000@0x0(u-boot),-@0x100000(ubi)
nand_erasesize=20000
nand_oobsize=40
nand_writesize=800
netcon=echo switch to net console;setenv stderr nc;setenv stdin nc;setenv stdout nc;echo switch to net console
preboot=run safeboot
serialcon=echo switch to serial console;setenv stderr serial;setenv stdin serial;setenv stdout serial;echo switch to serial console
serverip=192.168.**.***
set_bootargs_lede=setenv bootargs console=ttyS0,115200 $mtdparts
stderr=serial
stdin=serial
stdout=serial
updboot=bootp;tftp 60000000 u-boot.img;ide write 60000000 400 400
Environment size: 1469/16380 bytes
OX820 #
gonna just hold up here until you get back to me, thanks a ton! Ecowarrior108
|
Re: Tutorial of native sata boot for pogoplug pro March 21, 2018 12:14AM |
Admin Registered: 13 years ago Posts: 18,898 |
echowarrior108,
With the HDD and the USB rootfs attached to the Pogo. Power up, interrupt serial console at count down, and
and then boot
Post the entire serial console log here.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
With the HDD and the USB rootfs attached to the Pogo. Power up, interrupt serial console at count down, and
setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10' setenv uinitrd_addr 0x60e00000 setenv uimage_addr 0x60500000 setenv dtb_addr 0x62c00000 setenv dt_load_dtb 'ext2load usb 0:1 $dtb_addr /boot/dts/ox820-pogoplug-pro.dtb' setenv dt_load_initrd 'ext2load usb 0:1 $uinitrd_addr /boot/uInitrd' setenv dt_load_uimage 'ext2load usb 0:1 $uimage_addr /boot/uImage' setenv dt_bootm 'bootm $uimage_addr $uinitrd_addr $dtb_addr' setenv dt_usb_boot 'run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm' setenv dt_usb_bootcmd 'run usb_set_bootargs; run dt_usb_boot' setenv dt_bootcmd_usb 'usb start; run dt_usb_bootcmd; usb stop; reset' setenv bootcmd 'run dt_bootcmd_usb'
and then boot
boot
Post the entire serial console log here.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Tutorial of native sata boot for pogoplug pro March 21, 2018 01:38PM |
Registered: 6 years ago Posts: 183 |
Hi Bodhi !!!
Here is what happened!
so far so good!!!! got a few things to do so I will wait to see what is next:) but we are in root@Debian !!!
Added note, I saved the setenv you posted after a few tries to make sure it worked, this now works I can now get to root@debian but am still using the sata to startup as it won't boot without the sata connection. I am however running to an issue with copy/paste from terminal. do you have a link to fix that on ubuntu 17.10?
Thanks Echowarrior108
Edited 1 time(s). Last edit at 03/21/2018 03:33PM by echowarrior108.
Here is what happened!
# picocom -b 115200 /dev/ttyUSB0
picocom v2.2
port is : /dev/ttyUSB0
flowcontrol : none
baudrate is : 115200
parity is : none
databits are : 8
stopbits are : 1
escape is : C-a
local echo is : no
noinit is : no
noreset is : no
nolock is : no
send_cmd is : sz -vv
receive_cmd is : rz -vv -E
imap is :
omap is :
emap is : crcrlf,delbs,
Type [C-a] [C-h] to see available commands
Terminal ready
�
U-Boot SPL 2013.10-ga72eb8f-dirty (Feb 19 2014 - 15:21:12)
Boot device: SATA
Attempting to set PLLA to 800 MHz ...
plla_ctrl0 : 0000030a
plla_ctrl1 : 00400000
plla_ctrl2 : 007f0068
plla_ctrl3 : 00000193
PLLA Set
Bus 0: OK
Device 0:
reading bootargs.bin
reading u-boot.img
reading u-boot.img
U-Boot 2013.10-ga72eb8f-dirty (Feb 19 2014 - 15:21:12) for OXNAS
DRAM: 128 MiB
IDE: Bus 0: OK
Device 0: Model: WDC WD7500BPKT-75PK4T0 Firm: 01.01A01 Ser#: WD-WXD1A61R3456
Type: Hard Disk
Supports 48-bit addressing
Capacity: 715404.8 MB = 698.6 GB (1465149168 x 512)
NAND: 128 MiB
reading u-boot.env
In: serial
Out: serial
Err: serial
Net: mii0
## Error: "safeboot" not defined
Hit any key to stop autoboot: 0
OX820 # setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10'
OX820 # setenv uinitrd_addr 0x60e00000
OX820 # setenv uimage_addr 0x60500000
OX820 # setenv dtb_addr 0x62c00000
OX820 # setenv dt_load_dtb 'ext2load usb 0:1 $dtb_addr /boot/dts/ox820-pogoplug-pro.dtb'
OX820 # setenv dt_load_initrd 'ext2load usb 0:1 $uinitrd_addr /boot/uInitrd'
OX820 # setenv dt_load_uimage 'ext2load usb 0:1 $uimage_addr /boot/uImage'
OX820 # setenv dt_bootm 'bootm $uimage_addr $uinitrd_addr $dtb_addr'
OX820 # setenv dt_usb_boot 'run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm'
OX820 # setenv dt_usb_bootcmd 'run usb_set_bootargs; run dt_usb_boot'
OX820 # setenv dt_bootcmd_usb 'usb start; run dt_usb_bootcmd; usb stop; reset'
OX820 # setenv bootcmd 'run dt_bootcmd_usb'
OX820 # boot
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
4621824 bytes read in 526 ms (8.4 MiB/s)
4594376 bytes read in 561 ms (7.8 MiB/s)
7067 bytes read in 259 ms (26.4 KiB/s)
## Booting kernel from Legacy Image at 60500000 ...
Image Name: Linux-4.4.117-oxnas-tld-1
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4621760 Bytes = 4.4 MiB
Load Address: 60008000
Entry Point: 60008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 60e00000 ...
Image Name: initramfs-4.4.117-oxnas-tld-1
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 4594312 Bytes = 4.4 MiB
Load Address: 60000000
Entry Point: 60000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 62c00000
Booting using the fdt blob at 0x62c00000
Loading Kernel Image ... OK
Loading Ramdisk to 679c9000, end 67e2aa88 ... OK
Loading Device Tree to 679c4000, end 679c8b9a ... OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.4.54-oxnas-tld-1 (root@tldDebian) (gcc version 4.9.2 (Debian 4.9.2-10) ) #2 SMP PREEMPT Sat Mar 18 23:09:58 PDT 2017
[ 0.000000] CPU: ARMv6-compatible processor [410fb025] revision 5 (ARMv7), cr=00c5787d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine model: Pogoplug V3 Pro
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] DT missing boot CPU MPIDR[23:0], fall back to default cpu_logical_map
[ 0.000000] PERCPU: Embedded 12 pages/cpu @c7eda000 s17696 r8192 d23264 u49152
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512
[ 0.000000] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10
[ 0.000000] PID hash table entries: 512 (order: -1, 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: 116204K/131072K available (6410K kernel code, 288K rwdata, 1908K rodata, 224K init, 247K bss, 14868K reserved, 0K cma-reserved)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0xc8800000 - 0xff800000 ( 880 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xc8000000 ( 128 MB)
[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
[ 0.000000] .text : 0xc0008000 - 0xc0827e14 (8320 kB)
[ 0.000000] .init : 0xc0828000 - 0xc0860000 ( 224 kB)
[ 0.000000] .data : 0xc0860000 - 0xc08a8378 ( 289 kB)
[ 0.000000] .bss : 0xc08a8378 - 0xc08e6350 ( 248 kB)
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] NR_IRQS:160
[ 0.000000] clocksource: rps_clocksource_timer: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 19112603332 ns
[ 0.000007] sched_clock: 24 bits at 390kHz, resolution 2560ns, wraps every 21474835200ns
[ 0.000174] Console: colour dummy device 80x30
[ 0.000209] Calibrating delay loop... 319.48 BogoMIPS (lpj=1597440)
[ 0.050030] pid_max: default: 32768 minimum: 301
[ 0.050209] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.050227] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.051084] Initializing cgroup subsys net_cls
[ 0.051169] CPU: Testing write buffer coherency: ok
[ 0.051612] Setting up static identity map for 0x60008220 - 0x60008258
[ 0.190149] Brought up 2 CPUs
[ 0.190172] SMP: Total of 2 processors activated (638.97 BogoMIPS).
[ 0.190999] devtmpfs: initialized
[ 0.196700] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.196751] futex hash table entries: 512 (order: 2, 16384 bytes)
[ 0.197073] prandom: seed boundary self test passed
[ 0.201766] prandom: 100 self tests passed
[ 0.201794] pinctrl core: initialized pinctrl subsystem
[ 0.202718] NET: Registered protocol family 16
[ 0.203294] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.230018] cpuidle: using governor ladder
[ 0.260011] cpuidle: using governor menu
[ 0.265364] gpio-oxnas 44000000.gpio: at address c8848000
[ 0.265784] gpio-oxnas 44100000.gpio: at address c884a000
[ 0.266378] pinctrl-oxnas pinctrl: initialized OX820 pinctrl driver
[ 0.390679] oxnas-pcie 47c00000.pcie-controller: PCIe version/deviceID 0x82510b5
[ 0.390799] oxnas-pcie 47c00000.pcie-controller: link up
[ 0.391147] oxnas-pcie 47c00000.pcie-controller: PCI host bridge to bus 0000:00
[ 0.391175] pci_bus 0000:00: root bus resource [mem 0x48000000-0x49ffffff]
[ 0.391193] pci_bus 0000:00: root bus resource [mem 0x4a000000-0x4bdfffff pref]
[ 0.391208] pci_bus 0000:00: root bus resource [io 0x0000-0xfffff]
[ 0.391226] pci_bus 0000:00: root bus resource [bus 00-7f]
[ 0.391810] PCI: bus0: Fast back to back transfers disabled
[ 0.391907] pci 0000:00:00.0: BAR 0: assigned [mem 0x48000000-0x4800ffff]
[ 0.392389] vgaarb: loaded
[ 0.392903] SCSI subsystem initialized
[ 0.393835] usbcore: registered new interface driver usbfs
[ 0.393948] usbcore: registered new interface driver hub
[ 0.394112] usbcore: registered new device driver usb
[ 0.394334] pps_core: LinuxPPS API ver. 1 registered
[ 0.394350] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.394401] PTP clock support registered
[ 0.396641] clocksource: Switched to clocksource rps_clocksource_timer
[ 0.416322] NET: Registered protocol family 2
[ 0.417272] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.417313] TCP bind hash table entries: 1024 (order: 1, 8192 bytes)
[ 0.417351] TCP: Hash tables configured (established 1024 bind 1024)
[ 0.417454] UDP hash table entries: 256 (order: 1, 8192 bytes)
[ 0.417500] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[ 0.417779] NET: Registered protocol family 1
[ 0.418347] RPC: Registered named UNIX socket transport module.
[ 0.418370] RPC: Registered udp transport module.
[ 0.418380] RPC: Registered tcp transport module.
[ 0.418391] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.418813] Unpacking initramfs...
[ 0.925539] Freeing initrd memory: 4488K (c79c9000 - c7e2b000)
[ 0.927150] Initialise system trusted keyring
[ 0.953879] zbud: loaded
[ 0.971507] NFS: Registering the id_resolver key type
[ 0.971584] Key type id_resolver registered
[ 0.971599] Key type id_legacy registered
[ 0.971642] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 0.971665] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 0.972636] fuse init (API version 7.23)
[ 0.974781] Key type big_key registered
[ 1.056302] Key type asymmetric registered
[ 1.056337] Asymmetric key parser 'x509' registered
[ 1.056476] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 1.056504] io scheduler noop registered
[ 1.056527] io scheduler deadline registered
[ 1.056593] io scheduler cfq registered (default)
[ 1.057280] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
[ 1.058874] console [ttyS0] disabled
[ 1.058977] 44200000.uart: ttyS0 at MMIO 0x44200000 (irq = 6, base_baud = 390625) is a 16550A
[ 1.638430] console [ttyS0] enabled
[ 1.654005] loop: module loaded
[ 1.659217] scsi host0: sata_oxnas
[ 1.663119] ata1: SATA max UDMA/133 irq 7
[ 1.667215] sata_oxnas: resetting SATA core
[ 1.668285] nand: Could not find valid ONFI parameter page; aborting
[ 1.668326] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xf1
[ 1.668334] nand: Hynix NAND 128MiB 3,3V 8-bit
[ 1.668341] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 1.668359] Scanning device for bad blocks
[ 1.688686] Bad eraseblock 249 at 0x000001f20000
[ 1.751413] 2 ofpart partitions found on MTD device 41000000.nand
[ 1.757483] Creating 2 MTD partitions on "41000000.nand":
[ 1.762897] 0x000000000000-0x000000e00000 : "boot"
[ 1.769710] 0x000000e00000-0x000008000000 : "data"
[ 1.777131] oxnas-gmac 40400000.ethernet: no reset control found
[ 1.783157] stmmac - user ID: 0x12, Synopsys ID: 0x35
[ 1.788180] Ring mode enabled
[ 1.791234] DMA HW capability register supported
[ 1.795742] Enhanced/Alternate descriptors
[ 1.800071] Enabled extended descriptors
[ 1.804075] RX Checksum Offload Engine supported (type 2)
[ 1.809528] TX Checksum insertion supported
[ 1.813788] Wake-Up On Lan supported
[ 1.817433] Enable RX Mitigation via HW Watchdog Timer
[ 1.838786] libphy: stmmac: probed
[ 1.842252] eth%d: PHY ID 001cc914 at 0 IRQ POLL (stmmac-0:00) active
[ 1.848665] eth%d: PHY ID 001cc914 at 3 IRQ POLL (stmmac-0:03)
[ 1.855367] PPP generic driver version 2.4.2
[ 1.860154] rt2800pci 0000:00:00.0: enabling device (0140 -> 0142)
[ 1.866511] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3090, rev 3213 detected
[ 1.877790] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0005 detected
[ 1.887078] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.893642] ehci-pci: EHCI PCI platform driver
[ 1.898478] oxnas-ehci 40200100.ehci: EHCI Host Controller
[ 1.904038] oxnas-ehci 40200100.ehci: new USB bus registered, assigned bus number 1
[ 1.911877] oxnas-ehci 40200100.ehci: irq 10, io mem 0x40200100
[ 1.930150] oxnas-ehci 40200100.ehci: USB 2.0 started, EHCI 1.00
[ 1.936471] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.943270] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.950484] usb usb1: Product: EHCI Host Controller
[ 1.955340] usb usb1: Manufacturer: Linux 4.4.54-oxnas-tld-1 ehci_hcd
[ 1.961768] usb usb1: SerialNumber: 40200100.ehci
[ 1.967518] hub 1-0:1.0: USB hub found
[ 1.971389] hub 1-0:1.0: 2 ports detected
[ 1.976634] usbcore: registered new interface driver cdc_acm
[ 1.982318] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 1.990433] usbcore: registered new interface driver cdc_wdm
[ 1.996234] usbcore: registered new interface driver usb-storage
[ 2.002462] usbcore: registered new interface driver usbserial
[ 2.008335] usbcore: registered new interface driver usbserial_generic
[ 2.015045] usbserial: USB Serial support registered for generic
[ 2.021542] mousedev: PS/2 mouse device common for all mice
[ 2.027284] i2c /dev entries driver
[ 2.032225] hidraw: raw HID events driver (C) Jiri Kosina
[ 2.037880] usbcore: registered new interface driver usbhid
[ 2.043466] usbhid: USB HID core driver
[ 2.049446] NET: Registered protocol family 10
[ 2.055503] sit: IPv6 over IPv4 tunneling driver
[ 2.061327] NET: Registered protocol family 17
[ 2.065917] Key type dns_resolver registered
[ 2.071797] registered taskstats version 1
[ 2.075919] Loading compiled-in X.509 certificates
[ 2.080852] zswap: loaded using pool lzo/zbud
[ 2.101045] Key type encrypted registered
[ 2.220006] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 2.290140] usb 1-1: new high-speed USB device number 2 using oxnas-ehci
[ 2.442030] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[ 2.448709] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 2.455846] usb 1-1: Product: USB2.0 Hub
[ 2.460884] hub 1-1:1.0: USB hub found
[ 2.465034] hub 1-1:1.0: 4 ports detected
[ 2.564979] ata1.00: ATA-8: WDC WD7500BPKT-75PK4T0, 01.01A01, max UDMA/133
[ 2.571873] ata1.00: 1465149168 sectors, multi 0: LBA48 NCQ (depth 0/32)
[ 2.605644] ata1.00: configured for UDMA/133
[ 2.650416] scsi 0:0:0:0: Direct-Access ATA WDC WD7500BPKT-7 1A01 PQ: 0 ANSI: 5
[ 2.660177] sd 0:0:0:0: [sda] 1465149168 512-byte logical blocks: (750 GB/699 GiB)
[ 2.667911] sd 0:0:0:0: [sda] 4096-byte physical blocks
[ 2.673710] sd 0:0:0:0: [sda] Write Protect is off
[ 2.678714] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2.698280] sda: sda1 sda2 sda3
[ 2.704302] sd 0:0:0:0: [sda] Attached SCSI disk
[ 2.709271] Freeing unused kernel memory: 224K (c0828000 - c0860000)
[ 2.760302] usb 1-1.3: new high-speed USB device number 3 using oxnas-ehci
Loading, please wait...
[ 2.872048] usb 1-1.3: New USB device found, idVendor=0781, idProduct=5530
[ 2.878906] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2.886292] usb 1-1.3: Product: Cruzer
[ 2.890027] usb 1-1.3: Manufacturer: SanDisk
[ 2.894336] usb 1-1.3: SerialNumber: 20053248121181F0AC47
[ 2.901278] usb-storage 1-1.3:1.0: USB Mass Storage device detected
starting version 232
[ 2.917532] random: systemd-udevd: uninitialized urandom read (16 bytes read, 9 bits of entropy available)
[ 2.927354] scsi host1: usb-storage 1-1.3:1.0
[ 2.930639] random: udevadm: uninitialized urandom read (16 bytes read, 9 bits of entropy available)
[ 2.933122] random: udevadm: uninitialized urandom read (16 bytes read, 9 bits of entropy available)
[ 2.933314] random: udevadm: uninitialized urandom read (16 bytes read, 9 bits of entropy available)
[ 2.934558] random: udevadm: uninitialized urandom read (16 bytes read, 9 bits of entropy available)
[ 2.935651] random: udevadm: uninitialized urandom read (16 bytes read, 9 bits of entropy available)
[ 2.936860] random: udevadm: uninitialized urandom read (16 bytes read, 9 bits of entropy available)
[ 2.937955] random: udevadm: uninitialized urandom read (16 bytes read, 9 bits of entropy available)
[ 2.939102] random: udevadm: uninitialized urandom read (16 bytes read, 9 bits of entropy available)
[ 2.940405] random: udevadm: uninitialized urandom read (16 bytes read, 9 bits of entropy available)
[ 3.230338] usbcore: registered new interface driver uas
[ 3.317035] rt2800pci 0000:00:00.0 wlp0s0: renamed from wlan0
Begin: Loading essential drivers ... done.
[ 4.031790] scsi 1:0:0:0: Direct-Access SanDisk Cruzer 1.20 PQ: 0 ANSI: 5
[ 4.047449] sd 1:0:0:0: [sdb] 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB)
[ 4.062848] sd 1:0:0:0: [sdb] Write Protect is off
[ 4.069158] sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 4.090608] sdb: sdb1
[ 4.103628] sd 1:0:0:0: [sdb] Attached SCSI removable disk
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Will now check root file system ... fsck from util-linux 2.29.2
[/sbin/fsck.ext4 (1) -- /dev/sdb1] fsck.ext4 -a -C0 /dev/sdb1
rootfs: recovering journal
rootfs: clean, 14023/488640 files, 177715/1953792 blocks
done.
[ 15.743902] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
INIT: version 2.88 booting
[info] Using makefile-style concurrent boot in runlevel S.
[....] Starting the hotplug events dispatcher: systemd-udevdstarting version 232
. ok
[....] Synthesizing the initial hotplug events...[ 18.470830] random: nonblocking pool is initialized
done.
[ ok ] Waiting for /dev to be fully populated...done.
[ ok ] Activating swap...done.
[ 20.077788] EXT4-fs (sdb1): re-mounted. Opts: errors=remount-ro
[ ok ] Activating lvm and md swap...done.
[....] Checking file systems...fsck from util-linux 2.29.2
done.
[ ok ] Loading kernel modules...done.
[ ok ] Cleaning up temporary files... /tmp.
[ ok ] Mounting local filesystems...done.
[ ok ] Activating swapfile swap...done.
[ ok ] Cleaning up temporary files....
[ ok ] Setting kernel variables...done.
[....] Configuring network interfaces...Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/eth0/00:25:31:01:0c:d5
Sending on LPF/eth0/00:25:31:01:0c:d5
Sending on Socket/fallback
DHCPREQUEST of 192.168.0.16 on eth0 to 255.255.255.255 port 67
[ 28.970316] oxnas-gmac 40400000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
DHCPREQUEST of 192.168.0.16 on eth0 to 255.255.255.255 port 67
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPREQUEST of 192.168.5.97 on eth0 to 255.255.255.255 port 67
DHCPOFFER of 192.168.5.97 from 192.168.5.72
DHCPACK of 192.168.5.97 from 192.168.5.72
bound to 192.168.5.97 -- renewal in 20161 seconds.
done.
[ ok ] Starting RPC port mapper daemon: rpcbind.
[ ok ] Starting NFS common utilities: statd idmapd.
[ ok ] Cleaning up temporary files....
INIT: Entering runlevel: 2
[info] Using makefile-style concurrent boot in runlevel 2.
[....] Starting busybox' syslogd implementation : syslogdStarting /sbin/syslogd...
1254 (syslogd)
. ok
[ ok ] Starting NFS common utilities: statd idmapd.
[ ok ] Starting system message bus: dbus.
[warn] Not starting NFS kernel daemon: no exports. ... (warning).
[ ok ] Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
[ ok ] Starting OpenBSD Secure Shell server: sshd.
[....] Starting busybox' klogd implementation : klogdStarting /sbin/klogd...
1250 (klogd)
. ok
[ ok ] Starting NTP server: ntpd.
Debian GNU/Linux 9 debian ttyS0
debian login: root
Password:
Last login: Tue Aug 1 17:15:07 PDT 2017 from 192.168.0.220 on pts/0
Linux debian 4.4.54-oxnas-tld-1 #2 SMP PREEMPT Sat Mar 18 23:09:58 PDT 2017 armv6l
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
so far so good!!!! got a few things to do so I will wait to see what is next:) but we are in root@Debian !!!
Added note, I saved the setenv you posted after a few tries to make sure it worked, this now works I can now get to root@debian but am still using the sata to startup as it won't boot without the sata connection. I am however running to an issue with copy/paste from terminal. do you have a link to fix that on ubuntu 17.10?
Thanks Echowarrior108
Edited 1 time(s). Last edit at 03/21/2018 03:33PM by echowarrior108.
|
Re: Tutorial of native sata boot for pogoplug pro March 21, 2018 07:47PM |
Admin Registered: 13 years ago Posts: 18,898 |
echowarrior108 Wrote:
-------------------------------------------------------
> Hi Bodhi !!!
>
> Here is what happened!
>
>
>
> so far so good!!!! got a few things to do so I
> will wait to see what is next:) but we are in
> root@Debian !!!
Awesome!
>
> Added note, I saved the setenv you posted after a
> few tries to make sure it worked, this now works I
> can now get to root@debian but am still using the
> sata to startup as it won't boot without the sata
> connection. I am however running to an issue with
> copy/paste from terminal. do you have a link to
> fix that on ubuntu 17.10?
>
> Thanks Echowarrior108
You will need to install uboot to NAND to make it stick. Look back to what I posted above. I will be back to check if you have question.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> Hi Bodhi !!!
>
> Here is what happened!
>
>
# picocom -b 115200 /dev/ttyUSB0 > picocom v2.2 > > port is : /dev/ttyUSB0 > flowcontrol : none > baudrate is : 115200 > parity is : none > databits are : 8 > stopbits are : 1 > escape is : C-a > local echo is : no > noinit is : no > noreset is : no > nolock is : no > send_cmd is : sz -vv > receive_cmd is : rz -vv -E > imap is : > omap is : > emap is : crcrlf,delbs, > > Type [C-a] [C-h] to see available commands > > Terminal ready > � > U-Boot SPL 2013.10-ga72eb8f-dirty (Feb 19 2014 - > 15:21:12) > Boot device: SATA > Attempting to set PLLA to 800 MHz ... > plla_ctrl0 : 0000030a > plla_ctrl1 : 00400000 > plla_ctrl2 : 007f0068 > plla_ctrl3 : 00000193 > > PLLA Set > Bus 0: OK > Device 0: > reading bootargs.bin > reading u-boot.img > reading u-boot.img > > > U-Boot 2013.10-ga72eb8f-dirty (Feb 19 2014 - > 15:21:12) for OXNAS > > DRAM: 128 MiB > IDE: Bus 0: OK > Device 0: Model: WDC WD7500BPKT-75PK4T0 Firm: > 01.01A01 Ser#: WD-WXD1A61R3456 > Type: Hard Disk > Supports 48-bit addressing > Capacity: 715404.8 MB = 698.6 GB > (1465149168 x 512) > NAND: 128 MiB > reading u-boot.env > In: serial > Out: serial > Err: serial > Net: mii0 > ## Error: "safeboot" not defined > Hit any key to stop autoboot: 0 > OX820 # setenv usb_set_bootargs 'setenv bootargs > console=ttyS0,115200 root=LABEL=rootfs > rootdelay=10' > OX820 # setenv uinitrd_addr 0x60e00000 > OX820 # setenv uimage_addr 0x60500000 > OX820 # setenv dtb_addr 0x62c00000 > OX820 # setenv dt_load_dtb 'ext2load usb 0:1 > $dtb_addr /boot/dts/ox820-pogoplug-pro.dtb' > OX820 # setenv dt_load_initrd 'ext2load usb 0:1 > $uinitrd_addr /boot/uInitrd' > OX820 # setenv dt_load_uimage 'ext2load usb 0:1 > $uimage_addr /boot/uImage' > OX820 # setenv dt_bootm 'bootm $uimage_addr > $uinitrd_addr $dtb_addr' > OX820 # setenv dt_usb_boot 'run dt_load_uimage; > run dt_load_initrd; run dt_load_dtb; run > dt_bootm' > OX820 # setenv dt_usb_bootcmd 'run > usb_set_bootargs; run dt_usb_boot' > OX820 # setenv dt_bootcmd_usb 'usb start; run > dt_usb_bootcmd; usb stop; reset' > OX820 # setenv bootcmd 'run dt_bootcmd_usb' > OX820 # boot > (Re)start USB... > USB0: USB EHCI 1.00 > scanning bus 0 for devices... 3 USB Device(s) > found > scanning usb for storage devices... 1 > Storage Device(s) found > 4621824 bytes read in 526 ms (8.4 MiB/s) > 4594376 bytes read in 561 ms (7.8 MiB/s) > 7067 bytes read in 259 ms (26.4 KiB/s) > ## Booting kernel from Legacy Image at 60500000 > ... > Image Name: Linux-4.4.117-oxnas-tld-1 > Image Type: ARM Linux Kernel Image > (uncompressed) > Data Size: 4621760 Bytes = 4.4 MiB > Load Address: 60008000 > Entry Point: 60008000 > Verifying Checksum ... OK > ## Loading init Ramdisk from Legacy Image at > 60e00000 ... > Image Name: initramfs-4.4.117-oxnas-tld-1 > Image Type: ARM Linux RAMDisk Image (gzip > compressed) > Data Size: 4594312 Bytes = 4.4 MiB > Load Address: 60000000 > Entry Point: 60000000 > Verifying Checksum ... OK > ## Flattened Device Tree blob at 62c00000 > Booting using the fdt blob at 0x62c00000 > Loading Kernel Image ... OK > Loading Ramdisk to 679c9000, end 67e2aa88 ... > OK > Loading Device Tree to 679c4000, end 679c8b9a > ... OK > > Starting kernel ... > > Uncompressing Linux... done, booting the kernel. > [ 0.000000] Booting Linux on physical CPU 0x0 > [ 0.000000] Linux version 4.4.54-oxnas-tld-1 > (root@tldDebian) (gcc version 4.9.2 (Debian > 4.9.2-10) ) #2 SMP PREEMPT Sat Mar 18 23:09:58 PDT > 2017 > [ 0.000000] CPU: ARMv6-compatible processor > [410fb025] revision 5 (ARMv7), cr=00c5787d > [ 0.000000] CPU: PIPT / VIPT nonaliasing data > cache, VIPT aliasing instruction cache > [ 0.000000] Machine model: Pogoplug V3 Pro > [ 0.000000] Memory policy: Data cache > writealloc > [ 0.000000] DT missing boot CPU MPIDR[23:0], > fall back to default cpu_logical_map > [ 0.000000] PERCPU: Embedded 12 pages/cpu > @c7eda000 s17696 r8192 d23264 u49152 > [ 0.000000] Built 1 zonelists in Zone order, > mobility grouping on. Total pages: 32512 > [ 0.000000] Kernel command line: > console=ttyS0,115200 root=LABEL=rootfs > rootdelay=10 > [ 0.000000] PID hash table entries: 512 (order: > -1, 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: 116204K/131072K available > (6410K kernel code, 288K rwdata, 1908K rodata, > 224K init, 247K bss, 14868K reserved, 0K > cma-reserved) > [ 0.000000] Virtual kernel memory layout: > [ 0.000000] vector : 0xffff0000 - > 0xffff1000 ( 4 kB) > [ 0.000000] fixmap : 0xffc00000 - > 0xfff00000 (3072 kB) > [ 0.000000] vmalloc : 0xc8800000 - > 0xff800000 ( 880 MB) > [ 0.000000] lowmem : 0xc0000000 - > 0xc8000000 ( 128 MB) > [ 0.000000] modules : 0xbf000000 - > 0xc0000000 ( 16 MB) > [ 0.000000] .text : 0xc0008000 - > 0xc0827e14 (8320 kB) > [ 0.000000] .init : 0xc0828000 - > 0xc0860000 ( 224 kB) > [ 0.000000] .data : 0xc0860000 - > 0xc08a8378 ( 289 kB) > [ 0.000000] .bss : 0xc08a8378 - > 0xc08e6350 ( 248 kB) > [ 0.000000] SLUB: HWalign=32, Order=0-3, > MinObjects=0, CPUs=2, Nodes=1 > [ 0.000000] Preemptible hierarchical RCU > implementation. > [ 0.000000] NR_IRQS:160 > [ 0.000000] clocksource: rps_clocksource_timer: > mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: > 19112603332 ns > [ 0.000007] sched_clock: 24 bits at 390kHz, > resolution 2560ns, wraps every 21474835200ns > [ 0.000174] Console: colour dummy device 80x30 > [ 0.000209] Calibrating delay loop... 319.48 > BogoMIPS (lpj=1597440) > [ 0.050030] pid_max: default: 32768 minimum: > 301 > [ 0.050209] Mount-cache hash table entries: > 1024 (order: 0, 4096 bytes) > [ 0.050227] Mountpoint-cache hash table > entries: 1024 (order: 0, 4096 bytes) > [ 0.051084] Initializing cgroup subsys net_cls > [ 0.051169] CPU: Testing write buffer > coherency: ok > [ 0.051612] Setting up static identity map for > 0x60008220 - 0x60008258 > [ 0.190149] Brought up 2 CPUs > [ 0.190172] SMP: Total of 2 processors > activated (638.97 BogoMIPS). > [ 0.190999] devtmpfs: initialized > [ 0.196700] clocksource: jiffies: mask: > 0xffffffff max_cycles: 0xffffffff, max_idle_ns: > 19112604462750000 ns > [ 0.196751] futex hash table entries: 512 > (order: 2, 16384 bytes) > [ 0.197073] prandom: seed boundary self test > passed > [ 0.201766] prandom: 100 self tests passed > [ 0.201794] pinctrl core: initialized pinctrl > subsystem > [ 0.202718] NET: Registered protocol family 16 > [ 0.203294] DMA: preallocated 256 KiB pool for > atomic coherent allocations > [ 0.230018] cpuidle: using governor ladder > [ 0.260011] cpuidle: using governor menu > [ 0.265364] gpio-oxnas 44000000.gpio: at > address c8848000 > [ 0.265784] gpio-oxnas 44100000.gpio: at > address c884a000 > [ 0.266378] pinctrl-oxnas pinctrl: initialized > OX820 pinctrl driver > [ 0.390679] oxnas-pcie > 47c00000.pcie-controller: PCIe version/deviceID > 0x82510b5 > [ 0.390799] oxnas-pcie > 47c00000.pcie-controller: link up > [ 0.391147] oxnas-pcie > 47c00000.pcie-controller: PCI host bridge to bus > 0000:00 > [ 0.391175] pci_bus 0000:00: root bus resource > [mem 0x48000000-0x49ffffff] > [ 0.391193] pci_bus 0000:00: root bus resource > [mem 0x4a000000-0x4bdfffff pref] > [ 0.391208] pci_bus 0000:00: root bus resource > [io 0x0000-0xfffff] > [ 0.391226] pci_bus 0000:00: root bus resource > [bus 00-7f] > [ 0.391810] PCI: bus0: Fast back to back > transfers disabled > [ 0.391907] pci 0000:00:00.0: BAR 0: assigned > [mem 0x48000000-0x4800ffff] > [ 0.392389] vgaarb: loaded > [ 0.392903] SCSI subsystem initialized > [ 0.393835] usbcore: registered new interface > driver usbfs > [ 0.393948] usbcore: registered new interface > driver hub > [ 0.394112] usbcore: registered new device > driver usb > [ 0.394334] pps_core: LinuxPPS API ver. 1 > registered > [ 0.394350] pps_core: Software ver. 5.3.6 - > Copyright 2005-2007 Rodolfo Giometti > <giometti@linux.it> > [ 0.394401] PTP clock support registered > [ 0.396641] clocksource: Switched to > clocksource rps_clocksource_timer > [ 0.416322] NET: Registered protocol family 2 > [ 0.417272] TCP established hash table entries: > 1024 (order: 0, 4096 bytes) > [ 0.417313] TCP bind hash table entries: 1024 > (order: 1, 8192 bytes) > [ 0.417351] TCP: Hash tables configured > (established 1024 bind 1024) > [ 0.417454] UDP hash table entries: 256 (order: > 1, 8192 bytes) > [ 0.417500] UDP-Lite hash table entries: 256 > (order: 1, 8192 bytes) > [ 0.417779] NET: Registered protocol family 1 > [ 0.418347] RPC: Registered named UNIX socket > transport module. > [ 0.418370] RPC: Registered udp transport > module. > [ 0.418380] RPC: Registered tcp transport > module. > [ 0.418391] RPC: Registered tcp NFSv4.1 > backchannel transport module. > [ 0.418813] Unpacking initramfs... > [ 0.925539] Freeing initrd memory: 4488K > (c79c9000 - c7e2b000) > [ 0.927150] Initialise system trusted keyring > [ 0.953879] zbud: loaded > [ 0.971507] NFS: Registering the id_resolver > key type > [ 0.971584] Key type id_resolver registered > [ 0.971599] Key type id_legacy registered > [ 0.971642] nfs4filelayout_init: NFSv4 File > Layout Driver Registering... > [ 0.971665] Installing knfsd (copyright (C) > 1996 okir@monad.swb.de). > [ 0.972636] fuse init (API version 7.23) > [ 0.974781] Key type big_key registered > [ 1.056302] Key type asymmetric registered > [ 1.056337] Asymmetric key parser 'x509' > registered > [ 1.056476] Block layer SCSI generic (bsg) > driver version 0.4 loaded (major 252) > [ 1.056504] io scheduler noop registered > [ 1.056527] io scheduler deadline registered > [ 1.056593] io scheduler cfq registered > (default) > [ 1.057280] Serial: 8250/16550 driver, 1 ports, > IRQ sharing disabled > [ 1.058874] console [ttyS0] disabled > [ 1.058977] 44200000.uart: ttyS0 at MMIO > 0x44200000 (irq = 6, base_baud = 390625) is a > 16550A > [ 1.638430] console [ttyS0] enabled > [ 1.654005] loop: module loaded > [ 1.659217] scsi host0: sata_oxnas > [ 1.663119] ata1: SATA max UDMA/133 irq 7 > [ 1.667215] sata_oxnas: resetting SATA core > [ 1.668285] nand: Could not find valid ONFI > parameter page; aborting > [ 1.668326] nand: device found, Manufacturer > ID: 0xad, Chip ID: 0xf1 > [ 1.668334] nand: Hynix NAND 128MiB 3,3V 8-bit > [ 1.668341] nand: 128 MiB, SLC, erase size: 128 > KiB, page size: 2048, OOB size: 64 > [ 1.668359] Scanning device for bad blocks > [ 1.688686] Bad eraseblock 249 at > 0x000001f20000 > [ 1.751413] 2 ofpart partitions found on MTD > device 41000000.nand > [ 1.757483] Creating 2 MTD partitions on > "41000000.nand": > [ 1.762897] 0x000000000000-0x000000e00000 : > "boot" > [ 1.769710] 0x000000e00000-0x000008000000 : > "data" > [ 1.777131] oxnas-gmac 40400000.ethernet: no > reset control found > [ 1.783157] stmmac - user ID: 0x12, Synopsys > ID: 0x35 > [ 1.788180] Ring mode enabled > [ 1.791234] DMA HW capability register > supported > [ 1.795742] Enhanced/Alternate descriptors > [ 1.800071] Enabled extended descriptors > [ 1.804075] RX Checksum Offload Engine > supported (type 2) > [ 1.809528] TX Checksum insertion supported > [ 1.813788] Wake-Up On Lan supported > [ 1.817433] Enable RX Mitigation via HW > Watchdog Timer > [ 1.838786] libphy: stmmac: probed > [ 1.842252] eth%d: PHY ID 001cc914 at 0 IRQ > POLL (stmmac-0:00) active > [ 1.848665] eth%d: PHY ID 001cc914 at 3 IRQ > POLL (stmmac-0:03) > [ 1.855367] PPP generic driver version 2.4.2 > [ 1.860154] rt2800pci 0000:00:00.0: enabling > device (0140 -> 0142) > [ 1.866511] ieee80211 phy0: rt2x00_set_rt: Info > - RT chipset 3090, rev 3213 detected > [ 1.877790] ieee80211 phy0: rt2x00_set_rf: Info > - RF chipset 0005 detected > [ 1.887078] ehci_hcd: USB 2.0 'Enhanced' Host > Controller (EHCI) Driver > [ 1.893642] ehci-pci: EHCI PCI platform driver > [ 1.898478] oxnas-ehci 40200100.ehci: EHCI Host > Controller > [ 1.904038] oxnas-ehci 40200100.ehci: new USB > bus registered, assigned bus number 1 > [ 1.911877] oxnas-ehci 40200100.ehci: irq 10, > io mem 0x40200100 > [ 1.930150] oxnas-ehci 40200100.ehci: USB 2.0 > started, EHCI 1.00 > [ 1.936471] usb usb1: New USB device found, > idVendor=1d6b, idProduct=0002 > [ 1.943270] usb usb1: New USB device strings: > Mfr=3, Product=2, SerialNumber=1 > [ 1.950484] usb usb1: Product: EHCI Host > Controller > [ 1.955340] usb usb1: Manufacturer: Linux > 4.4.54-oxnas-tld-1 ehci_hcd > [ 1.961768] usb usb1: SerialNumber: > 40200100.ehci > [ 1.967518] hub 1-0:1.0: USB hub found > [ 1.971389] hub 1-0:1.0: 2 ports detected > [ 1.976634] usbcore: registered new interface > driver cdc_acm > [ 1.982318] cdc_acm: USB Abstract Control Model > driver for USB modems and ISDN adapters > [ 1.990433] usbcore: registered new interface > driver cdc_wdm > [ 1.996234] usbcore: registered new interface > driver usb-storage > [ 2.002462] usbcore: registered new interface > driver usbserial > [ 2.008335] usbcore: registered new interface > driver usbserial_generic > [ 2.015045] usbserial: USB Serial support > registered for generic > [ 2.021542] mousedev: PS/2 mouse device common > for all mice > [ 2.027284] i2c /dev entries driver > [ 2.032225] hidraw: raw HID events driver (C) > Jiri Kosina > [ 2.037880] usbcore: registered new interface > driver usbhid > [ 2.043466] usbhid: USB HID core driver > [ 2.049446] NET: Registered protocol family 10 > [ 2.055503] sit: IPv6 over IPv4 tunneling > driver > [ 2.061327] NET: Registered protocol family 17 > [ 2.065917] Key type dns_resolver registered > [ 2.071797] registered taskstats version 1 > [ 2.075919] Loading compiled-in X.509 > certificates > [ 2.080852] zswap: loaded using pool lzo/zbud > [ 2.101045] Key type encrypted registered > [ 2.220006] ata1: SATA link up 1.5 Gbps > (SStatus 113 SControl 310) > [ 2.290140] usb 1-1: new high-speed USB device > number 2 using oxnas-ehci > [ 2.442030] usb 1-1: New USB device found, > idVendor=05e3, idProduct=0608 > [ 2.448709] usb 1-1: New USB device strings: > Mfr=0, Product=1, SerialNumber=0 > [ 2.455846] usb 1-1: Product: USB2.0 Hub > [ 2.460884] hub 1-1:1.0: USB hub found > [ 2.465034] hub 1-1:1.0: 4 ports detected > [ 2.564979] ata1.00: ATA-8: WDC > WD7500BPKT-75PK4T0, 01.01A01, max UDMA/133 > [ 2.571873] ata1.00: 1465149168 sectors, multi > 0: LBA48 NCQ (depth 0/32) > [ 2.605644] ata1.00: configured for UDMA/133 > [ 2.650416] scsi 0:0:0:0: Direct-Access ATA > WDC WD7500BPKT-7 1A01 PQ: 0 ANSI: 5 > [ 2.660177] sd 0:0:0:0: [sda] 1465149168 > 512-byte logical blocks: (750 GB/699 GiB) > [ 2.667911] sd 0:0:0:0: [sda] 4096-byte > physical blocks > [ 2.673710] sd 0:0:0:0: [sda] Write Protect is > off > [ 2.678714] sd 0:0:0:0: [sda] Write cache: > enabled, read cache: enabled, doesn't support DPO > or FUA > [ 2.698280] sda: sda1 sda2 sda3 > [ 2.704302] sd 0:0:0:0: [sda] Attached SCSI > disk > [ 2.709271] Freeing unused kernel memory: 224K > (c0828000 - c0860000) > [ 2.760302] usb 1-1.3: new high-speed USB > device number 3 using oxnas-ehci > Loading, please wait... > [ 2.872048] usb 1-1.3: New USB device found, > idVendor=0781, idProduct=5530 > [ 2.878906] usb 1-1.3: New USB device strings: > Mfr=1, Product=2, SerialNumber=3 > [ 2.886292] usb 1-1.3: Product: Cruzer > [ 2.890027] usb 1-1.3: Manufacturer: SanDisk > [ 2.894336] usb 1-1.3: SerialNumber: > 20053248121181F0AC47 > [ 2.901278] usb-storage 1-1.3:1.0: USB Mass > Storage device detected > starting version 232 > [ 2.917532] random: systemd-udevd: > uninitialized urandom read (16 bytes read, 9 bits > of entropy available) > [ 2.927354] scsi host1: usb-storage 1-1.3:1.0 > [ 2.930639] random: udevadm: uninitialized > urandom read (16 bytes read, 9 bits of entropy > available) > [ 2.933122] random: udevadm: uninitialized > urandom read (16 bytes read, 9 bits of entropy > available) > [ 2.933314] random: udevadm: uninitialized > urandom read (16 bytes read, 9 bits of entropy > available) > [ 2.934558] random: udevadm: uninitialized > urandom read (16 bytes read, 9 bits of entropy > available) > [ 2.935651] random: udevadm: uninitialized > urandom read (16 bytes read, 9 bits of entropy > available) > [ 2.936860] random: udevadm: uninitialized > urandom read (16 bytes read, 9 bits of entropy > available) > [ 2.937955] random: udevadm: uninitialized > urandom read (16 bytes read, 9 bits of entropy > available) > [ 2.939102] random: udevadm: uninitialized > urandom read (16 bytes read, 9 bits of entropy > available) > [ 2.940405] random: udevadm: uninitialized > urandom read (16 bytes read, 9 bits of entropy > available) > [ 3.230338] usbcore: registered new interface > driver uas > [ 3.317035] rt2800pci 0000:00:00.0 wlp0s0: > renamed from wlan0 > Begin: Loading essential drivers ... done. > [ 4.031790] scsi 1:0:0:0: Direct-Access > SanDisk Cruzer 1.20 PQ: 0 ANSI: 5 > [ 4.047449] sd 1:0:0:0: [sdb] 15633408 512-byte > logical blocks: (8.00 GB/7.45 GiB) > [ 4.062848] sd 1:0:0:0: [sdb] Write Protect is > off > [ 4.069158] sd 1:0:0:0: [sdb] Write cache: > disabled, read cache: enabled, doesn't support DPO > or FUA > [ 4.090608] sdb: sdb1 > [ 4.103628] sd 1:0:0:0: [sdb] Attached SCSI > removable disk > Begin: Running /scripts/init-premount ... done. > Begin: Mounting root file system ... Begin: > Running /scripts/local-top ... done. > Begin: Running /scripts/local-premount ... done. > Begin: Will now check root file system ... fsck > from util-linux 2.29.2 > [/sbin/fsck.ext4 (1) -- /dev/sdb1] fsck.ext4 -a > -C0 /dev/sdb1 > rootfs: recovering journal > rootfs: clean, 14023/488640 files, 177715/1953792 > blocks > done. > [ 15.743902] EXT4-fs (sdb1): mounted filesystem > with ordered data mode. Opts: (null) > done. > Begin: Running /scripts/local-bottom ... done. > Begin: Running /scripts/init-bottom ... done. > INIT: version 2.88 booting > [info] Using makefile-style concurrent boot in > runlevel S. > [....] Starting the hotplug events dispatcher: > systemd-udevdstarting version 232 > . ok > [....] Synthesizing the initial hotplug events...[ > 18.470830] random: nonblocking pool is > initialized > done. > [ ok ] Waiting for /dev to be fully > populated...done. > [ ok ] Activating swap...done. > [ 20.077788] EXT4-fs (sdb1): re-mounted. Opts: > errors=remount-ro > [ ok ] Activating lvm and md swap...done. > [....] Checking file systems...fsck from > util-linux 2.29.2 > done. > [ ok ] Loading kernel modules...done. > [ ok ] Cleaning up temporary files... /tmp. > [ ok ] Mounting local filesystems...done. > [ ok ] Activating swapfile swap...done. > [ ok ] Cleaning up temporary files.... > [ ok ] Setting kernel variables...done. > [....] Configuring network interfaces...Internet > Systems Consortium DHCP Client 4.3.5 > Copyright 2004-2016 Internet Systems Consortium. > All rights reserved. > For info, please visit > https://www.isc.org/software/dhcp/ > > Listening on LPF/eth0/00:25:31:01:0c:d5 > Sending on LPF/eth0/00:25:31:01:0c:d5 > Sending on Socket/fallback > DHCPREQUEST of 192.168.0.16 on eth0 to > 255.255.255.255 port 67 > [ 28.970316] oxnas-gmac 40400000.ethernet eth0: > Link is Up - 1Gbps/Full - flow control off > DHCPREQUEST of 192.168.0.16 on eth0 to > 255.255.255.255 port 67 > DHCPDISCOVER on eth0 to 255.255.255.255 port 67 > interval 6 > DHCPREQUEST of 192.168.5.97 on eth0 to > 255.255.255.255 port 67 > DHCPOFFER of 192.168.5.97 from 192.168.5.72 > DHCPACK of 192.168.5.97 from 192.168.5.72 > bound to 192.168.5.97 -- renewal in 20161 > seconds. > done. > [ ok ] Starting RPC port mapper daemon: rpcbind. > [ ok ] Starting NFS common utilities: statd > idmapd. > [ ok ] Cleaning up temporary files.... > INIT: Entering runlevel: 2 > [info] Using makefile-style concurrent boot in > runlevel 2. > [....] Starting busybox' syslogd implementation : > syslogdStarting /sbin/syslogd... > 1254 (syslogd) > . ok > [ ok ] Starting NFS common utilities: statd > idmapd. > [ ok ] Starting system message bus: dbus. > [warn] Not starting NFS kernel daemon: no exports. > ... (warning). > [ ok ] Starting Avahi mDNS/DNS-SD Daemon: > avahi-daemon. > [ ok ] Starting OpenBSD Secure Shell server: > sshd. > [....] Starting busybox' klogd implementation : > klogdStarting /sbin/klogd... > 1250 (klogd) > . ok > [ ok ] Starting NTP server: ntpd. > > Debian GNU/Linux 9 debian ttyS0 > > debian login: root > Password: > Last login: Tue Aug 1 17:15:07 PDT 2017 from > 192.168.0.220 on pts/0 > Linux debian 4.4.54-oxnas-tld-1 #2 SMP PREEMPT Sat > Mar 18 23:09:58 PDT 2017 armv6l > > The programs included with the Debian GNU/Linux > system are free software; > the exact distribution terms for each program are > described in the > individual files in /usr/share/doc/*/copyright. > > Debian GNU/Linux comes with ABSOLUTELY NO > WARRANTY, to the extent > permitted by applicable law. > >>
>
> so far so good!!!! got a few things to do so I
> will wait to see what is next:) but we are in
> root@Debian !!!
Awesome!
>
> Added note, I saved the setenv you posted after a
> few tries to make sure it worked, this now works I
> can now get to root@debian but am still using the
> sata to startup as it won't boot without the sata
> connection. I am however running to an issue with
> copy/paste from terminal. do you have a link to
> fix that on ubuntu 17.10?
>
> Thanks Echowarrior108
You will need to install uboot to NAND to make it stick. Look back to what I posted above. I will be back to check if you have question.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Tutorial of native sata boot for pogoplug pro March 21, 2018 09:41PM |
Registered: 6 years ago Posts: 183 |
Thanks Bodhi, should we continue this on https://forum.doozan.com/read.php?3,16017 ? I think we are done on the SATA boot part:)
and many thanks to the rest of you who helped with getting me safely back into my pogoplug!! The walkthrough really helped and I do plan to work on my sata more once I have the pogoplug up and running completely:)
Thanks Echowarrior108
note:learning just enough to be dangerous to my equipment:)
and many thanks to the rest of you who helped with getting me safely back into my pogoplug!! The walkthrough really helped and I do plan to work on my sata more once I have the pogoplug up and running completely:)
Thanks Echowarrior108
note:learning just enough to be dangerous to my equipment:)
|
Re: Tutorial of native sata boot for pogoplug pro March 23, 2018 04:25PM |
Admin Registered: 13 years ago Posts: 18,898 |
Echowarrior108,
Some discrepancy here. During boot, u-boot loaded the images named with kernel 4.4.117-oxnas-tld-1. But the actual kernel you booting the rootfs with is 4.4.54-oxnas-tld-1.
Since you are booting OK, it was probably just an editorial mistake. But to make sure you did the right installation, tell us why was the difference? did you try to upgrade the kernel to 4.4.117-oxnas-tld-1 on the rootfs?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Some discrepancy here. During boot, u-boot loaded the images named with kernel 4.4.117-oxnas-tld-1. But the actual kernel you booting the rootfs with is 4.4.54-oxnas-tld-1.
Quote
## Booting kernel from Legacy Image at 60500000 ...
Image Name: Linux-4.4.117-oxnas-tld-1
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4621760 Bytes = 4.4 MiB
Load Address: 60008000
Entry Point: 60008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 60e00000 ...
Image Name: initramfs-4.4.117-oxnas-tld-1
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 4594312 Bytes = 4.4 MiB
Load Address: 60000000
Entry Point: 60000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 62c00000
Booting using the fdt blob at 0x62c00000
Loading Kernel Image ... OK
Loading Ramdisk to 679c9000, end 67e2aa88 ... OK
Loading Device Tree to 679c4000, end 679c8b9a ... OK
Quote
Uncompressing Linux... done, booting the kernel.
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.4.54-oxnas-tld-1 (root@tldDebian) (gcc version 4.9.2 (Debian 4.9.2-10) ) #2 SMP PREEMPT Sat Mar 18 23:09:58 PDT 2017
[ 0.000000] CPU: ARMv6-compatible processor [410fb025] revision 5 (ARMv7), cr=00c5787d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine model: Pogoplug V3 Pro
Since you are booting OK, it was probably just an editorial mistake. But to make sure you did the right installation, tell us why was the difference? did you try to upgrade the kernel to 4.4.117-oxnas-tld-1 on the rootfs?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
