OpenWRT for PogoPlug Pro rootfs tar
Posted by habibie
|
OpenWRT for PogoPlug Pro rootfs tar April 10, 2015 10:52AM |
Registered: 11 years ago Posts: 1,303 |
I just built OpenWRT for PogoPlug Pro (openwrt-oxnas-bin.tar.xz -- 73.7 MB in size). It contains just basic rootfs + Linux kernels in /boot directory. Just download and untar to extract. I have not tried it yet. I am still playing around with my PogoPlug Pro P02 and will be about to flash uboot from Bodhi. Please let me know how this goes.
EDIT: I just re-read this post and realized I forgot to mention the firmware includes a MAC Telnet package. This is the same MAC Telnet package found on a debian distro and is supposed to allow any user to login into the device using SSH through its MAC Address, instead of the usual IP Address. It comes very handy when the IP Address is not known. By default, this utility is loaded through the boot process. If you don't want it to run, you can either manully remove the /etc/rc.d/S60mactelnet file or run /etc/init.d/mactelnet disable which will automatically delete the file. In order to use this, one needs to add the username:password (plain text) to the /etc/mactelnetd.users file. Then, use SSH with just the MAC Address of the device to login. When connected, mactelnet will prompt for the username and password.
Edited 1 time(s). Last edit at 04/12/2015 06:29AM by habibie.
[debian@debian:/opt/openwrt-git-trunk 937%] ~ ls -la bin/oxnas/ total 197004 drwxr-xr-x 3 debian user 4096 Apr 10 11:19 . drwxr-xr-x 4 debian user 4096 Apr 9 20:51 .. -rw-r--r-- 1 debian user 877 Apr 10 11:19 md5sums -rw-r--r-- 1 debian user 6993 Apr 10 02:38 openwrt-oxnas-pogoplug-pro.dtb -rw-r--r-- 1 debian user 50331648 Apr 10 11:19 openwrt-oxnas-pogoplug-pro-ext4.img -rw-r--r-- 1 debian user 1632948 Apr 10 11:18 openwrt-oxnas-pogoplug-pro-fit-uImage.itb -rw-r--r-- 1 debian user 31588356 Apr 10 11:19 openwrt-oxnas-pogoplug-pro-jffs2-128k.img -rw-r--r-- 1 debian user 31588356 Apr 10 11:19 openwrt-oxnas-pogoplug-pro-jffs2-64k.img -rw-r--r-- 1 debian user 14289407 Apr 10 11:19 openwrt-oxnas-pogoplug-pro-rootfs.tar.gz -rw-r--r-- 1 debian user 13271040 Apr 10 11:19 openwrt-oxnas-pogoplug-pro-squashfs-sysupgrade.tar -rw-r--r-- 1 debian user 13893632 Apr 10 11:19 openwrt-oxnas-pogoplug-pro-squashfs-ubinized.bin -rw-r--r-- 1 debian user 20613120 Apr 10 11:19 openwrt-oxnas-pogoplug-pro-ubifs-sysupgrade.tar -rw-r--r-- 1 debian user 21233664 Apr 10 11:19 openwrt-oxnas-pogoplug-pro-ubifs-ubinized.bin -rw-r--r-- 1 debian user 1624672 Apr 10 11:18 openwrt-oxnas-uImage -rwxr-xr-x 1 debian user 1624608 Apr 10 11:18 openwrt-oxnas-zImage [debian@debian:/opt/openwrt-git-trunk 938%] ~
EDIT: I just re-read this post and realized I forgot to mention the firmware includes a MAC Telnet package. This is the same MAC Telnet package found on a debian distro and is supposed to allow any user to login into the device using SSH through its MAC Address, instead of the usual IP Address. It comes very handy when the IP Address is not known. By default, this utility is loaded through the boot process. If you don't want it to run, you can either manully remove the /etc/rc.d/S60mactelnet file or run /etc/init.d/mactelnet disable which will automatically delete the file. In order to use this, one needs to add the username:password (plain text) to the /etc/mactelnetd.users file. Then, use SSH with just the MAC Address of the device to login. When connected, mactelnet will prompt for the username and password.
Edited 1 time(s). Last edit at 04/12/2015 06:29AM by habibie.
|
Re: OpenWRT for PogoPlug Pro rootfs tar April 10, 2015 04:57PM |
Registered: 9 years ago Posts: 1,037 |
|
Re: OpenWRT for PogoPlug Pro rootfs tar April 10, 2015 05:26PM |
Registered: 11 years ago Posts: 165 |
Gravelrash Wrote:
-------------------------------------------------------
> Grayman4hire. Was I believe looking for something
> like this.
> May be an idea to pm him?
Thanks for looking out. :)
No I have no interest in it. The issue with this is that you'll need provide all the kernel packages making it not very easy to maintain long term.
I figured out how to extract the rootfs from the snapshot build and just posted my tutorial - http://blog.qnology.com/2015/04/openwrt-on-pogoplug-v3oxnas-proclassic.html
-------------------------------------------------------
> Grayman4hire. Was I believe looking for something
> like this.
> May be an idea to pm him?
Thanks for looking out. :)
No I have no interest in it. The issue with this is that you'll need provide all the kernel packages making it not very easy to maintain long term.
I figured out how to extract the rootfs from the snapshot build and just posted my tutorial - http://blog.qnology.com/2015/04/openwrt-on-pogoplug-v3oxnas-proclassic.html
|
Re: OpenWRT for PogoPlug Pro rootfs tar April 10, 2015 09:27PM |
Admin Registered: 13 years ago Posts: 18,543 |
habibie,
I think this thread should be moved to U-Boot forum. It's not really Debian related.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
I think this thread should be moved to U-Boot forum. It's not really Debian related.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: OpenWRT for PogoPlug Pro rootfs tar April 10, 2015 10:32PM |
Registered: 11 years ago Posts: 1,303 |
|
Re: OpenWRT for PogoPlug Pro rootfs tar April 10, 2015 10:33PM |
Registered: 11 years ago Posts: 1,303 |
grayman4hire Wrote:
-------------------------------------------------------
> Gravelrash Wrote:
> --------------------------------------------------
> -----
> > Grayman4hire. Was I believe looking for
> something
> > like this.
> > May be an idea to pm him?
>
> Thanks for looking out. :)
>
> No I have no interest in it. The issue with this
> is that you'll need provide all the kernel
> packages making it not very easy to maintain long
> term.
>
> I figured out how to extract the rootfs from the
> snapshot build and just posted my tutorial -
> http://blog.qnology.com/2015/04/openwrt-on-pogoplu
> g-v3oxnas-proclassic.html
>
Nice tutorial. Thank you.
-------------------------------------------------------
> Gravelrash Wrote:
> --------------------------------------------------
> -----
> > Grayman4hire. Was I believe looking for
> something
> > like this.
> > May be an idea to pm him?
>
> Thanks for looking out. :)
>
> No I have no interest in it. The issue with this
> is that you'll need provide all the kernel
> packages making it not very easy to maintain long
> term.
>
> I figured out how to extract the rootfs from the
> snapshot build and just posted my tutorial -
> http://blog.qnology.com/2015/04/openwrt-on-pogoplu
> g-v3oxnas-proclassic.html
>
Nice tutorial. Thank you.
|
Re: OpenWRT for PogoPlug Pro rootfs tar April 10, 2015 11:19PM |
Admin Registered: 13 years ago Posts: 18,543 |
habibie Wrote:
-------------------------------------------------------
> @Bodhi - Please feel free to move it to u-boot
> forum.
I can't! Only Jeff can do that.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> @Bodhi - Please feel free to move it to u-boot
> forum.
I can't! Only Jeff can do that.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: OpenWRT for PogoPlug Pro rootfs tar April 11, 2015 06:26AM |
Registered: 11 years ago Posts: 1,303 |
|
Re: OpenWRT for PogoPlug Pro rootfs tar April 11, 2015 07:43AM |
Registered: 11 years ago Posts: 1,303 |
|
Re: OpenWRT for PogoPlug Pro rootfs tar April 12, 2015 06:31AM |
Registered: 11 years ago Posts: 1,303 |
|
Re: OpenWRT for PogoPlug Pro rootfs tar April 14, 2015 09:05PM |
Registered: 9 years ago Posts: 1,516 |
|
Re: OpenWRT for PogoPlug Pro rootfs tar May 05, 2015 09:59PM |
Registered: 11 years ago Posts: 1,303 |
|
Re: OpenWRT for PogoPlug Pro rootfs tar May 05, 2015 10:25PM |
Admin Registered: 13 years ago Posts: 18,543 |
I don't think the Pogoplugs support jumbo frame. Whether it it is supports would be in the hardware (NIC).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 05/05/2015 10:26PM by bodhi.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 05/05/2015 10:26PM by bodhi.
|
Re: OpenWRT for PogoPlug Pro rootfs tar May 06, 2015 12:04AM |
Registered: 11 years ago Posts: 1,303 |
After a long delay, today I finally got sometimes to upgrade my PogoPlug Pro 02 to Bodi's u-boot. It boots OK with debian ARM. However, when I tried to boot a self-built OpenWRT, it keeps looping/resetting as shown below. I don't have /boot/uInitrd. Can this be the issue?
U-Boot 2013.10-tld-4 (Sep 08 2014 - 19:43:38) for OXNAS
gcc (Debian 4.6.3-14) 4.6.3
GNU ld (GNU Binutils for Debian) 2.22
Hit any key to stop autoboot: 0
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
1690968 bytes read in 405 ms (4 MiB/s)
** File not found /boot/uInitrd **
6993 bytes read in 184 ms (37.1 KiB/s)
## Booting kernel from Legacy Image at 60500000 ...
Image Name: ARM OpenWrt Linux-3.18.11
Created: 2015-05-06 4:48:07 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1690904 Bytes = 1.6 MiB
Load Address: 60008000
Entry Point: 60008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 60e00000 ...
Image Name: initramfs-3.17.0-oxnas-tld-1
Created: 2014-11-01 7:18:53 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 1953748 Bytes = 1.9 MiB
Load Address: 60000000
Entry Point: 60000000
Verifying Checksum ... Bad Data CRC
Led: ORANGE (Failed)
Ramdisk image is corrupt or invalid
stopping USB..
resetting ...
|
Re: OpenWRT for PogoPlug Pro rootfs tar May 06, 2015 12:21AM |
Admin Registered: 13 years ago Posts: 18,543 |
habibie,
> I don't have
> /boot/uInitrd. Can this be the issue?
Yes. You need to change your bootcmd not to try to load uInitrd, only load uImage.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I don't have
> /boot/uInitrd. Can this be the issue?
Yes. You need to change your bootcmd not to try to load uInitrd, only load uImage.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: OpenWRT for PogoPlug Pro rootfs tar May 06, 2015 07:58AM |
Registered: 11 years ago Posts: 1,303 |
bodhi Wrote:
-------------------------------------------------------
> habibie,
>
> > I don't have
> > /boot/uInitrd. Can this be the issue?
>
> Yes. You need to change your bootcmd not to try to
> load uInitrd, only load uImage.
>
Hello Bodhi,
I hope by removing run dt_load_initrd; from dt_usb_bootcmd is a proper way to do. Otherwise, please kindly provide instruction on how to do this. Now, uboot no longer tries to load /boot/uInitrd file as shown below. However, it still reports with an error message of Ramdisk image is corrupt or invalid.
OTOH, I noticed OpenWRT does generate an initramfs file as shown below.
BTW, I also noticed each 1 second set in the bootdelay variable is equivalent to 2 seconds. So, the setenv bootdelay 10 on start_netconsole provides about 20 seconds for the Hit any key to stop autoboot: to elapse.
-------------------------------------------------------
> habibie,
>
> > I don't have
> > /boot/uInitrd. Can this be the issue?
>
> Yes. You need to change your bootcmd not to try to
> load uInitrd, only load uImage.
>
Hello Bodhi,
I hope by removing run dt_load_initrd; from dt_usb_bootcmd is a proper way to do. Otherwise, please kindly provide instruction on how to do this. Now, uboot no longer tries to load /boot/uInitrd file as shown below. However, it still reports with an error message of Ramdisk image is corrupt or invalid.
U-Boot 2013.10-tld-4 (Sep 08 2014 - 19:43:38) for OXNAS
gcc (Debian 4.6.3-14) 4.6.3
GNU ld (GNU Binutils for Debian) 2.22
Hit any key to stop autoboot: 0
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
1690968 bytes read in 406 ms (4 MiB/s)
6993 bytes read in 184 ms (37.1 KiB/s)
## Booting kernel from Legacy Image at 60500000 ...
Image Name: ARM OpenWrt Linux-3.18.11
Created: 2015-05-06 4:48:07 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1690904 Bytes = 1.6 MiB
Load Address: 60008000
Entry Point: 60008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 60e00000 ...
Image Name: ARM OpenWrt Linux-3.18.11
Created: 2015-05-06 4:51:56 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 15200008 Bytes = 14.5 MiB
Load Address: 60008000
Entry Point: 60008000
Verifying Checksum ... OK
No Linux ARM Ramdisk Image
Led: ORANGE (Failed)
Ramdisk image is corrupt or invalid
stopping USB..
resetting ...
OTOH, I noticed OpenWRT does generate an initramfs file as shown below.
[debian@debian:/opt/openwrt-git-trunk 383%] ~ ls -lart bin/oxnas/ total 142636 drwxr-xr-x 6 debian user 4096 May 5 18:53 .. drwxr-xr-x 9 debian user 4096 May 5 21:58 packages -rw-r--r-- 1 debian user 6993 May 6 00:45 openwrt-oxnas-pogoplug-pro.dtb drwxr-xr-x 3 debian user 4096 May 6 00:48 . -rwxr-xr-x 1 debian user 1690528 May 6 00:50 openwrt-oxnas-zImage -rwxr-xr-x 1 debian user 15200008 May 6 00:51 openwrt-oxnas-zImage-initramfs -rw-r--r-- 1 debian user 1698868 May 6 00:51 openwrt-oxnas-pogoplug-pro-fit-uImage.itb -rw-r--r-- 1 debian user 15208348 May 6 00:51 openwrt-oxnas-pogoplug-pro-fit-uImage-initramfs.itb -rw-r--r-- 1 debian user 1690592 May 6 00:51 openwrt-oxnas-uImage -rw-r--r-- 1 debian user 15200072 May 6 00:51 openwrt-oxnas-uImage-initramfs -rw-r--r-- 1 debian user 25204902 May 6 00:52 openwrt-oxnas-pogoplug-pro-rootfs.tar.gz -rw-r--r-- 1 debian user 34611200 May 6 00:52 openwrt-oxnas-pogoplug-pro-ubifs-sysupgrade.tar -rw-r--r-- 1 debian user 35520512 May 6 00:52 openwrt-oxnas-pogoplug-pro-ubifs-ubinized.bin -rw-r--r-- 1 debian user 749 May 6 00:52 md5sums -rw-r--r-- 1 debian user 1189 May 6 00:52 sha256sums [debian@debian:/opt/openwrt-git-trunk 384%] ~I don't know if the above openwrt-oxnas-uImage-initramfs file is the same as uInitrd file. I noticed uboot has no problem to load it, but reports no Ramdisk Image as shown below, but it still reports with an error message of Ramdisk image is corrupt or invalid. Have you any idea?
U-Boot 2013.10-tld-4 (Sep 08 2014 - 19:43:38) for OXNAS
gcc (Debian 4.6.3-14) 4.6.3
GNU ld (GNU Binutils for Debian) 2.22
Hit any key to stop autoboot: 0
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
1690968 bytes read in 406 ms (4 MiB/s)
15200072 bytes read in 2229 ms (6.5 MiB/s)
6993 bytes read in 184 ms (37.1 KiB/s)
## Booting kernel from Legacy Image at 60500000 ...
Image Name: ARM OpenWrt Linux-3.18.11
Created: 2015-05-06 4:48:07 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1690904 Bytes = 1.6 MiB
Load Address: 60008000
Entry Point: 60008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 60e00000 ...
Image Name: ARM OpenWrt Linux-3.18.11
Created: 2015-05-06 4:51:56 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 15200008 Bytes = 14.5 MiB
Load Address: 60008000
Entry Point: 60008000
Verifying Checksum ... OK
No Linux ARM Ramdisk Image
Led: ORANGE (Failed)
Ramdisk image is corrupt or invalid
stopping USB..
resetting ...
BTW, I also noticed each 1 second set in the bootdelay variable is equivalent to 2 seconds. So, the setenv bootdelay 10 on start_netconsole provides about 20 seconds for the Hit any key to stop autoboot: to elapse.
|
Re: OpenWRT for PogoPlug Pro rootfs tar May 06, 2015 03:43PM |
Admin Registered: 13 years ago Posts: 18,543 |
habibie,
You also need to remove the uInitrd address in the bootm command too. Please list you u-boot envs here and I'll point you to the command, if you're not sure.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
You also need to remove the uInitrd address in the bootm command too. Please list you u-boot envs here and I'll point you to the command, if you're not sure.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: OpenWRT for PogoPlug Pro rootfs tar May 06, 2015 03:48PM |
Registered: 11 years ago Posts: 1,303 |
Hello Bodhi,
Here is my uboot env:
Edited 1 time(s). Last edit at 05/09/2015 01:52PM by habibie.
Here is my uboot env:
OX820> printenv autoload=no baudrate=115200 bootargs=console=ttyS0,115200n8 bootcmd=run dt_bootcmd_usb bootdelay=10 console=console=ttyS0,115200n8 dt_bootcmd_usb=usb start; run dt_usb_bootcmd; usb stop; reset dt_bootm=bootm $uimage_addr $uinitrd_addr $dtb_addr dt_load_dtb=ext2load usb 0:1 $dtb_addr $fdt_file dt_load_initrd=ext2load usb 0:1 $uinitrd_addr /boot/openwrt-oxnas-uImage-initramfs dt_load_uimage=ext2load usb 0:1 $uimage_addr /boot/openwrt-oxnas-uImage dt_usb_boot=run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm dt_usb_bootcmd=run usb_set_bootargs; run dt_usb_boot dtb_addr=0x62c00000 ethact=mii0 ethaddr=00:11:22:33:44:55 fdt_file=/boot/openwrt-oxnas-pogoplug-pro.dtb if_netconsole=ping $serverip ipaddr=10.0.0.253 mtdids=nand0=41000000.nand mtdparts=mtdparts=41000000.nand:14m(boot),-(data) preboot=run preboot_nc preboot_nc=run if_netconsole start_netconsole serverip=10.0.0.100 start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version stderr=serial stdin=serial stdout=serial uimage_addr=0x60500000 uinitrd_addr=0x60e00000 usb_device=0:1 usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10 Environment size: 1273/131068 bytes OX820>
Edited 1 time(s). Last edit at 05/09/2015 01:52PM by habibie.
|
Re: OpenWRT for PogoPlug Pro rootfs tar May 06, 2015 04:02PM |
Admin Registered: 13 years ago Posts: 18,543 |
habibie,
To not loading and using uInitrd, these 2 envs
Note the - (minus) in dt_bootm, it tells u-boot that there is no uInitrd, but there is a DTB file at $dtb_addr.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
To not loading and using uInitrd, these 2 envs
dt_usb_boot=run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm dt_bootm=bootm $uimage_addr $uinitrd_addr $dtb_addrshould be changed to
dt_usb_boot=run dt_load_uimage; run dt_load_dtb; run dt_bootm dt_bootm=bootm $uimage_addr - $dtb_addr
Note the - (minus) in dt_bootm, it tells u-boot that there is no uInitrd, but there is a DTB file at $dtb_addr.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: OpenWRT for PogoPlug Pro rootfs tar May 06, 2015 04:55PM |
Registered: 11 years ago Posts: 1,303 |
Hello Bodhi,
Thank you and that does the trick. Now, my PogoPlug Pro 02 runs OpenWRT. However, it looks like UBIFS generates the following error messages. Have you any idea why?
Thank you and that does the trick. Now, my PogoPlug Pro 02 runs OpenWRT. However, it looks like UBIFS generates the following error messages. Have you any idea why?
[ 1.262241] Waiting 10 sec before mounting root device... [ 11.271293] UBIFS: background thread "ubifs_bgt0_0" started, PID 277 [ 11.305274] UBIFS: recovery needed [ 11.395141] UBIFS: recovery completed [ 11.398896] UBIFS: mounted UBI device 0, volume 0, name "rootfs" [ 11.405560] UBIFS: LEB size: 129024 bytes (126 KiB), min./max. I/O unit sizes: 2048 bys [ 11.414658] UBIFS: FS size: 114573312 bytes (109 MiB, 888 LEBs), journal size 9033728 ) [ 11.424442] UBIFS: reserved for root: 0 bytes (0 KiB) [ 11.429473] UBIFS: media format: w4/r0 (latest is w4/r0), UUID FEE2A8B2-0DDE-49B4-BF18l [ 11.440604] VFS: Mounted root (ubifs filesystem) on device 0:11. [ 11.446835] Freeing unused kernel memory: 164K (c0419000 - c0442000) Too many bit errors @ 0xa0000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa0800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa1000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa1800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa2000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa2800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa3000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa3800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa4000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa4800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa5000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa5800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa6000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa6800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa7000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa7800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa8000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa8800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa9000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa9800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xaa000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xaa800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xab000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xab800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xac000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xac800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xad000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xad800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xae000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xae800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xaf000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xaf800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb0000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb0800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb1000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb1800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb2000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb2800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb3000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb3800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb4000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb4800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb5000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb5800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb6000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb6800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb7000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb7800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb8000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb8800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb9000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb9800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xba000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xba800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xbb000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xbb800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xbc000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xbc800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xbd000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xbd800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xbe000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xbe800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xbf000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xbf800 -- Can't correct! PAGE DATA: OOB: -- Invalid CRC32 on parameters: 0xb2 != 0xaccdd05f /etc/init.d/rcS: /tmp/ethaddr: line 1: 000002f0:: not found /etc/init.d/rcS: /tmp/ethaddr: line 2: 00000730:: not found /etc/init.d/rcS: /tmp/ethaddr: line 3: 000006f0:: not found /etc/init.d/rcS: /tmp/ethaddr: line 4: 00000140:: not found Too many bit errors @ 0xa0000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa0800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa1000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa1800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa2000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa2800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa3000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa3800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa4000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa4800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa5000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa5800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa6000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa6800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa7000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa7800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa8000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa8800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa9000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xa9800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xaa000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xaa800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xab000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xab800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xac000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xac800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xad000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xad800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xae000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xae800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xaf000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xaf800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb0000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb0800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb1000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb1800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb2000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb2800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb3000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb3800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb4000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb4800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb5000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb5800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb6000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb6800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb7000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb7800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb8000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb8800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb9000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xb9800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xba000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xba800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xbb000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xbb800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xbc000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xbc800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xbd000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xbd800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xbe000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xbe800 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xbf000 -- Can't correct! PAGE DATA: OOB: Too many bit errors @ 0xbf800 -- Can't correct! PAGE DATA: OOB: -- Invalid CRC32 on parameters: 0xb2 != 0xaccdd05f /dev/mem opened. Memory mapped at address 0xb6f95000. Value at address 0x44A00000 (0xb6f95000): 0x0 Written 0x14; readback 0x100000 /dev/mem opened. Memory mapped at address 0xb6f31000. Value at address 0x44A00004 (0xb6f31004): 0x0 Written 0x4CE10; readback 0x0 /dev/mem opened. Memory mapped at address 0xb6fe8000. Value at address 0x44A00004 (0xb6fe8004): 0x0 Written 0x2CE10; readback 0x0 /dev/mem opened. Memory mapped at address 0xb6f5a000. Value at address 0x44A00000 (0xb6f5a000): 0x0 Written 0x2004; readback 0x110000 /dev/mem opened. Memory mapped at address 0xb6fd9000. Value at address 0x44A00004 (0xb6fd9004): 0x0 Written 0x482C7; readback 0x0 /dev/mem opened. Memory mapped at address 0xb6fa8000. Value at address 0x44A00004 (0xb6fa8004): 0x0 Written 0x282C7; readback 0x0 modprobe: chdir(3.18.11): No such file or directory modprobe: chdir(3.18.11): No such file or directory [ 12.526970] rt3390sta: version magic '2.6.31.6_SMP_820 SMP mod_unload ARMv6 ' should b' insmod: can't insert '/lib/modules/2.6.31.6_SMP_820/kernel/drivers/net/wireless/rt3390stat udhcpc (v1.16.1) started HWADDR 00 0x25 0x31 0x01 0xc4 0xea PIP0 196 PIP1 234 cat: can't open '/etc/resolv.conf': No such file or directory route: SIOCDELRT: No such process grep: /etc/resolv.conf: No such file or directory Sending discover... [ 14.543608] stmmaceth 40400000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx Sending discover... Sending select for 10.0.0.207... Lease of 10.0.0.207 obtained, lease time 604800 HWADDR 00 0x25 0x31 0x01 0xc4 0xea PIP0 196 PIP1 234 route: SIOCDELRT: No such process modprobe: chdir(3.18.11): No such file or directory modprobe: chdir(3.18.11): No such file or directory modprobe: chdir(3.18.11): No such file or directory modprobe: chdir(3.18.11): No such file or directory modprobe: chdir(3.18.11): No such file or directory mount: mounting none on /proc/bus/usb failed: No such file or directory [ 16.604480] random: dropbear urandom read with 11 bits of entropy available ifconfig: SIOCGIFFLAGS: No such device modprobe: chdir(3.18.11): No such file or directory [ 16.800376] ufsd: version magic '2.6.31.6_SMP_820 SMP mod_unload ARMv6 ' should be '3.' insmod: can't insert '/usr/local/cloudengines/bin/ufsd.ko': invalid module format Loading xce.ko: [ 16.822315] xce: version magic '2.6.31.6_SMP_820 SMP mod_' insmod: can't insert '/usr/local/cloudengines/bin/xce.ko': invalid module format Success /etc/init.d/hbmgr.sh: line 108: can't create /dev/xce: No such device Starting hbplug: Success / # df Filesystem 1K-blocks Used Available Use% Mounted on ubi0:rootfs 104524 11048 93476 11% / none 62620 4 62616 0% /tmp / #
|
Re: OpenWRT for PogoPlug Pro rootfs tar May 06, 2015 05:41PM |
Registered: 11 years ago Posts: 165 |
If you're running OpenWRT, why do you have references to cloudengine?
That doesn't look right. Are you booting the OpenWRT kernel but using the original Pogoplug root file system?
-grayman4hire
======================================
Pogoplug V2 and V3 Serial Connection
Tutorial - Pogoplug v4 (Series 4 and Mobile) with Linux (Debian or Arch)
OpenWRT on Pogoplug Mobile
Tutorial - Pogoplug E02/V4 with Arch Linux ARM
Hacking the Pogoplug v3/Oxnas (Pro/Classic) with Debian
OpenWRT on Pogoplug v3/Oxnas (Pro/Classic)
insmod: can't insert '/usr/local/cloudengines/bin/ufsd.ko': invalid module format Loading xce.ko: [ 16.822315] xce: version magic '2.6.31.6_SMP_820 SMP mod_' insmod: can't insert '/usr/local/cloudengines/bin/xce.ko': invalid module format Success /etc/init.d/hbmgr.sh: line 108: can't create /dev/xce: No such device
That doesn't look right. Are you booting the OpenWRT kernel but using the original Pogoplug root file system?
-grayman4hire
======================================
Pogoplug V2 and V3 Serial Connection
Tutorial - Pogoplug v4 (Series 4 and Mobile) with Linux (Debian or Arch)
OpenWRT on Pogoplug Mobile
Tutorial - Pogoplug E02/V4 with Arch Linux ARM
Hacking the Pogoplug v3/Oxnas (Pro/Classic) with Debian
OpenWRT on Pogoplug v3/Oxnas (Pro/Classic)
|
Re: OpenWRT for PogoPlug Pro rootfs tar May 06, 2015 05:57PM |
Registered: 11 years ago Posts: 1,303 |
@grayman4hire
Actually, those error messages are from OpenWRT snapshot installed on an SD card that I prepared following your tutorial guide (OpenWRT on Pogoplug v3/Oxnas (Pro/Classic)). perhaps, OpenWRT build scripts do reference to CloudEngine's stuffs.
Right now, my build won't boot and just gets stuck on Uncompressing Linux... done, booting the kernel. I believe it has something to do with gcc-4.9.x. I will rebuild again using gcc-4.8.x to see if this works OK.
Actually, those error messages are from OpenWRT snapshot installed on an SD card that I prepared following your tutorial guide (OpenWRT on Pogoplug v3/Oxnas (Pro/Classic)). perhaps, OpenWRT build scripts do reference to CloudEngine's stuffs.
Right now, my build won't boot and just gets stuck on Uncompressing Linux... done, booting the kernel. I believe it has something to do with gcc-4.9.x. I will rebuild again using gcc-4.8.x to see if this works OK.
|
Re: OpenWRT for PogoPlug Pro rootfs tar May 06, 2015 06:10PM |
Admin Registered: 13 years ago Posts: 18,543 |
habibie,
No idea.
But how come you are still trying to load the old modules?
And looks like the stock Pogo OS is running instead of OepnWRT:
What is the ouput of
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
No idea.
But how come you are still trying to load the old modules?
insmod: can't insert '/usr/local/cloudengines/bin/ufsd.ko': invalid module format Loading xce.ko: [ 16.822315] xce: version magic '2.6.31.6_SMP_820 SMP mod_' insmod: can't insert '/usr/local/cloudengines/bin/xce.ko': invalid module format
And looks like the stock Pogo OS is running instead of OepnWRT:
/etc/init.d/hbmgr.sh: line 108: can't create /dev/xce: No such device Starting hbplug: Success
What is the ouput of
uname -a
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: OpenWRT for PogoPlug Pro rootfs tar May 06, 2015 06:25PM |
Registered: 11 years ago Posts: 1,303 |
Bodhi,
If you look at the output from uname -a, the Linux kernel shows the date is 5/5/15. So, it can't be the stock Linux kernel, right?
Just to make sure, here is my uboot env. I couldn't find any reference points to the stock Linux kernel. BTW, how do I remove the dt_load_initrd environment?
Edited 2 time(s). Last edit at 05/09/2015 01:52PM by habibie.
If you look at the output from uname -a, the Linux kernel shows the date is 5/5/15. So, it can't be the stock Linux kernel, right?
/ # uname -a Linux PogoplugPro 3.18.11 #1 SMP Tue May 5 18:17:24 UTC 2015 armv6l GNU/Linux / #
Just to make sure, here is my uboot env. I couldn't find any reference points to the stock Linux kernel. BTW, how do I remove the dt_load_initrd environment?
autoload=no
baudrate=115200
bootargs=console=ttyS0,115200n8
bootcmd=run dt_bootcmd_usb
bootdelay=10
console=console=ttyS0,115200n8
dt_bootcmd_usb=usb start; run dt_usb_bootcmd; usb stop; reset
dt_bootm=bootm $uimage_addr - $dtb_addr
dt_load_dtb=ext2load usb 0:1 $dtb_addr $fdt_file
dt_load_initrd=ext2load usb 0:1 $uinitrd_addr /boot/openwrt-oxnas-uImage-initramfs
dt_load_uimage=ext2load usb 0:1 $uimage_addr /boot/openwrt-oxnas-uImage
dt_usb_boot=run dt_load_uimage; run dt_load_dtb; run dt_bootm
dt_usb_bootcmd=run usb_set_bootargs; run dt_usb_boot
dtb_addr=0x62c00000
ethact=mii0
ethaddr=00:11:22:33:44:55
fdt_file=/boot/openwrt-oxnas-pogoplug-pro.dtb
if_netconsole=ping $serverip
ipaddr=10.0.0.253
mtdids=nand0=41000000.nand
mtdparts=mtdparts=41000000.nand:14m(boot),-(data)
preboot=run preboot_nc
preboot_nc=run if_netconsole start_netconsole
serverip=10.0.0.100
start_netconsole=setenv ncip $serverip; setenv bootdelay 5; setenv stdin nc; setenv stdout nc; setenv stderr nc; version
stderr=serial
stdin=serial
stdout=serial
uimage_addr=0x60500000
uinitrd_addr=0x60e00000
usb_device=0:1
usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10
Environment size: 1240/131068 bytes
OX820>
Edited 2 time(s). Last edit at 05/09/2015 01:52PM by habibie.
|
Re: OpenWRT for PogoPlug Pro rootfs tar May 06, 2015 06:42PM |
Registered: 11 years ago Posts: 1,303 |
I did a telnet into my PogoPlug Pro 02 running on OpenWRT. I did a dmesg and df. From the dmesg dump, it looks like OpenWRT booting sequence. However, from the output of df, it looks like PogoPlug filesystem.
Connected to 10.0.0.207. Escape character is '^]'. PogoplugPro login: root Password: ~ # dmesg <6>[ 0.000000] Booting Linux on physical CPU 0x0 <5>[ 0.000000] Linux version 3.18.11 (openwrt@gb-18) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r45605) ) #1 SMP Tue May 5 18:17:24 UTC 2015 <6>[ 0.000000] CPU: ARMv6-compatible processor [410fb025] revision 5 (ARMv7), cr=00c5787d <6>[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache <6>[ 0.000000] Machine model: Pogoplug Pro <6>[ 0.000000] Memory policy: Data cache writealloc <7>[ 0.000000] On node 0 totalpages: 32768 <7>[ 0.000000] free_area_init_node: node 0, pgdat c04531e0, node_mem_map c7efa000 <7>[ 0.000000] Normal zone: 256 pages used for memmap <7>[ 0.000000] Normal zone: 0 pages reserved <7>[ 0.000000] Normal zone: 32768 pages, LIFO batch:7 <4>[ 0.000000] DT missing boot CPU MPIDR[23:0], fall back to default cpu_logical_map <6>[ 0.000000] PERCPU: Embedded 9 pages/cpu @c7ee1000 s6880 r8192 d21792 u36864 <7>[ 0.000000] pcpu-alloc: s6880 r8192 d21792 u36864 alloc=9*4096 <7>[ 0.000000] pcpu-alloc: [0] 0 [0] 1 <4>[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512 <5>[ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda1 rootdelay=10 <6>[ 0.000000] PID hash table entries: 512 (order: -1, 2048 bytes) <6>[ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) <6>[ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) <4>[ 0.000000] Memory: 125080K/131072K available (3260K kernel code, 179K rwdata, 900K rodata, 164K init, 217K bss, 5992K reserved) <5>[ 0.000000] Virtual kernel memory layout: <5>[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) <5>[ 0.000000] fixmap : 0xffc00000 - 0xffe00000 (2048 kB) <5>[ 0.000000] vmalloc : 0xc8800000 - 0xff000000 ( 872 MB) <5>[ 0.000000] lowmem : 0xc0000000 - 0xc8000000 ( 128 MB) <5>[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB) <5>[ 0.000000] .text : 0xc0008000 - 0xc041834c (4161 kB) <5>[ 0.000000] .init : 0xc0419000 - 0xc0442000 ( 164 kB) <5>[ 0.000000] .data : 0xc0442000 - 0xc046ed58 ( 180 kB) <5>[ 0.000000] .bss : 0xc046ed58 - 0xc04a541c ( 218 kB) <6>[ 0.000000] Hierarchical RCU implementation. <6>[ 0.000000] NR_IRQS:160 <6>[ 0.000015] sched_clock: 24 bits at 390kHz, resolution 2560ns, wraps every 42949670400ns <6>[ 0.000279] Calibrating delay loop... 339.14 BogoMIPS (lpj=1695744) <6>[ 0.050050] pid_max: default: 32768 minimum: 301 <6>[ 0.050301] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) <6>[ 0.050321] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) <6>[ 0.050987] CPU: Testing write buffer coherency: ok <6>[ 0.051335] Setting up static identity map for 0x60011600 - 0x60011638 <4>[ 0.053365] CPU1: Booted secondary processor <6>[ 0.110177] Brought up 2 CPUs <6>[ 0.110202] SMP: Total of 2 processors activated (678.29 BogoMIPS). <6>[ 0.113372] pinctrl core: initialized pinctrl subsystem <6>[ 0.115809] NET: Registered protocol family 16 <6>[ 0.116295] DMA: preallocated 256 KiB pool for atomic coherent allocations <6>[ 0.140049] cpuidle: using governor ladder <6>[ 0.160028] cpuidle: using governor menu <6>[ 0.165534] gpio-oxnas 44000000.gpio: at address c8848000 <6>[ 0.165900] gpio-oxnas 44100000.gpio: at address c884a000 <6>[ 0.166469] pinctrl-oxnas pinctrl: initialized OX820 pinctrl driver <6>[ 0.312222] oxnas-pcie 47c00000.pcie-controller: PCIe version/deviceID 0x82510b5 <6>[ 0.312299] oxnas-pcie 47c00000.pcie-controller: link up <6>[ 0.312588] oxnas-pcie 47c00000.pcie-controller: PCI host bridge to bus 0000:00 <6>[ 0.312627] pci_bus 0000:00: root bus resource [mem 0x48000000-0x49ffffff] <6>[ 0.312647] pci_bus 0000:00: root bus resource [mem 0x4a000000-0x4bdfffff pref] <6>[ 0.312665] pci_bus 0000:00: root bus resource [io 0x0000-0xfffff] <6>[ 0.312688] pci_bus 0000:00: root bus resource [bus 00-7f] <7>[ 0.312747] pci 0000:00:00.0: [1814:3090] type 00 class 0x028000 <7>[ 0.312796] pci 0000:00:00.0: reg 0x10: [mem 0x00000000-0x0000ffff] <6>[ 0.313169] PCI: bus0: Fast back to back transfers disabled <6>[ 0.313280] pci 0000:00:00.0: BAR 0: assigned [mem 0x48000000-0x4800ffff] <5>[ 0.314045] SCSI subsystem initialized <6>[ 0.314762] usbcore: registered new interface driver usbfs <6>[ 0.314895] usbcore: registered new interface driver hub <6>[ 0.315010] usbcore: registered new device driver usb <6>[ 0.315271] pps_core: LinuxPPS API ver. 1 registered <6>[ 0.315289] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> <6>[ 0.315366] PTP clock support registered <6>[ 0.316935] Switched to clocksource rps_clocksource_timer <6>[ 0.319334] NET: Registered protocol family 2 <6>[ 0.320478] TCP established hash table entries: 1024 (order: 0, 4096 bytes) <6>[ 0.320524] TCP bind hash table entries: 1024 (order: 1, 8192 bytes) <6>[ 0.320558] TCP: Hash tables configured (established 1024 bind 1024) <6>[ 0.320665] TCP: reno registered <6>[ 0.320691] UDP hash table entries: 256 (order: 1, 8192 bytes) <6>[ 0.320747] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes) <6>[ 0.321134] NET: Registered protocol family 1 <7>[ 0.321246] PCI: CLS 32 bytes, default 32 <6>[ 0.322803] futex hash table entries: 512 (order: 2, 16384 bytes) <6>[ 0.324275] squashfs: version 4.0 (2009/01/31) Phillip Lougher <6>[ 0.324323] msgmni has been set to 244 <6>[ 0.325061] io scheduler noop registered <6>[ 0.325084] io scheduler deadline registered (default) <6>[ 0.326031] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled <6>[ 0.330442] console [ttyS0] disabled <6>[ 0.330513] 44200000.uart: ttyS0 at MMIO 0x44200000 (irq = 55, base_baud = 390625) is a 16550A <6>[ 0.780856] console [ttyS0] enabled <3>[ 0.786644] nand: Could not find valid ONFI parameter page; aborting <6>[ 0.793047] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xf1 <6>[ 0.799370] nand: Hynix NAND 128MiB 3,3V 8-bit <6>[ 0.803811] nand: 128MiB, SLC, page size: 2048, OOB size: 64 <6>[ 0.809451] Scanning device for bad blocks <5>[ 0.895887] 2 ofpart partitions found on MTD device 41000000.nand <5>[ 0.902000] Creating 2 MTD partitions on "41000000.nand": <5>[ 0.907376] 0x000000000000-0x000000e00000 : "boot" <5>[ 0.913582] 0x000000e00000-0x000008000000 : "ubi" <6>[ 0.920637] stmmaceth 40400000.ethernet: no reset control found <6>[ 0.926540] stmmac - user ID: 0x12, Synopsys ID: 0x35 <6>[ 0.931591] Ring mode enabled <6>[ 0.934627] DMA HW capability register supported <6>[ 0.939128] Enhanced/Alternate descriptors <6>[ 0.943472] Enabled extended descriptors <6>[ 0.947458] RX Checksum Offload Engine supported (type 2) <6>[ 0.952921] TX Checksum insertion supported <6>[ 0.957163] Wake-Up On Lan supported <6>[ 0.960816] Enable RX Mitigation via HW Watchdog Timer <6>[ 0.969428] libphy: stmmac: probed <6>[ 0.972871] eth0: PHY ID 001cc914 at 0 IRQ POLL (stmmac-0:00) active <6>[ 0.979197] eth0: PHY ID 001cc914 at 3 IRQ POLL (stmmac-0:03) <6>[ 0.985612] TCP: cubic registered <6>[ 0.988930] NET: Registered protocol family 17 <6>[ 0.993525] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this. <5>[ 1.007063] Bridge firewalling registered <6>[ 1.011074] 8021q: 802.1Q VLAN Support v1.8 <5>[ 1.017968] UBI: auto-attach mtd1 <5>[ 1.021278] UBI: attaching mtd1 to ubi0 <5>[ 1.171338] UBI: scanning is finished <4>[ 1.182758] UBI warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 9, need 20 <5>[ 1.194007] UBI: attached mtd1 (name "ubi", size 114 MiB) to ubi0 <5>[ 1.200081] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes <5>[ 1.206863] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 512 <5>[ 1.213457] UBI: VID header offset: 512 (aligned 512), data offset: 2048 <5>[ 1.220119] UBI: good PEBs: 912, bad PEBs: 0, corrupted PEBs: 0 <5>[ 1.226017] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128 <5>[ 1.233116] UBI: max/mean erase counter: 2/0, WL threshold: 4096, image sequence number: 0 <5>[ 1.241349] UBI: available PEBs: 0, total reserved PEBs: 912, PEBs reserved for bad PEB handling: 9 <3>[ 1.250488] drivers/rtc/hctosys.c: unable to open rtc device (rtc0) <5>[ 1.258199] UBI: background thread "ubi_bgt0d" started, PID 275 <6>[ 1.264256] Waiting 10 sec before mounting root device... <5>[ 11.274734] UBIFS: background thread "ubifs_bgt0_0" started, PID 278 <5>[ 11.308595] UBIFS: recovery needed <5>[ 11.401402] UBIFS: recovery completed <5>[ 11.405806] UBIFS: mounted UBI device 0, volume 0, name "rootfs" <5>[ 11.411816] UBIFS: LEB size: 129024 bytes (126 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes <5>[ 11.420925] UBIFS: FS size: 114573312 bytes (109 MiB, 888 LEBs), journal size 9033728 bytes (8 MiB, 71 LEBs) <5>[ 11.430720] UBIFS: reserved for root: 0 bytes (0 KiB) <5>[ 11.435745] UBIFS: media format: w4/r0 (latest is w4/r0), UUID FEE2A8B2-0DDE-49B4-BF18-BDDF61ACCE52, small LPT model <6>[ 11.446865] VFS: Mounted root (ubifs filesystem) on device 0:11. <6>[ 11.453089] Freeing unused kernel memory: 164K (c0419000 - c0442000) <3>[ 12.568770] rt3390sta: version magic '2.6.31.6_SMP_820 SMP mod_unload ARMv6 ' should be '3.18.11 SMP mod_unload ARMv6 p2v8 ' <6>[ 14.580172] stmmaceth 40400000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx <5>[ 16.895109] random: dropbear urandom read with 12 bits of entropy available <3>[ 17.087360] ufsd: version magic '2.6.31.6_SMP_820 SMP mod_unload ARMv6 ' should be '3.18.11 SMP mod_unload ARMv6 p2v8 ' <3>[ 17.109373] xce: version magic '2.6.31.6_SMP_820 SMP mod_unload ARMv6 ' should be '3.18.11 SMP mod_unload ARMv6 p2v8 ' ~ # uname -a Linux PogoplugPro 3.18.11 #1 SMP Tue May 5 18:17:24 UTC 2015 armv6l GNU/Linux ~ # df Filesystem 1K-blocks Used Available Use% Mounted on ubi0:rootfs 104524 11048 93476 11% / none 62620 4 62616 0% /tmp ~ #Here is the directory listings which confirms it is a PogoPlug filesystem. So, how did this happen?
/ # ls -la / drwxr-xr-x 16 root root 1128 Jan 1 00:01 . drwxr-xr-x 16 root root 1128 Jan 1 00:01 .. drwx------ 2 root root 232 Jan 1 00:01 .ssh drwxr-xr-x 2 root root 4408 Jan 1 00:02 bin drwxr-xr-x 5 root root 19016 Jun 10 2010 dev drwxr-xr-x 6 root root 1376 Jan 1 00:25 etc drwxr-xr-x 3 root root 2240 Nov 30 2010 lib drwx------ 2 root root 160 Nov 30 2010 lost+found drwxr-xr-x 2 root root 160 Jun 10 2010 mnt dr-xr-xr-x 44 root root 0 Jan 1 00:00 proc drwxr-xr-x 3 root root 224 Jan 1 00:02 root drwxr-xr-x 2 root root 2848 Nov 30 2010 sbin dr-xr-xr-x 12 root root 0 Jan 1 00:00 sys drwxrwxrwt 3 root root 80 Jan 1 00:00 tmp drwxr-xr-x 2 root root 720 Jan 1 1970 tmp1 drwxr-xr-x 7 root root 480 Nov 30 2010 usr lrwxrwxrwx 1 root root 8 Nov 30 2010 var -> /tmp/var / # ls -la /usr/ drwxr-xr-x 7 root root 480 Nov 30 2010 . drwxr-xr-x 16 root root 1128 Jan 1 00:01 .. drwxr-xr-x 2 root root 4584 Nov 30 2010 bin drwxr-xr-x 3 root root 376 Nov 30 2010 lib drwxr-xr-x 3 root root 232 Nov 30 2010 local drwxr-xr-x 2 root root 768 Nov 30 2010 sbin drwxr-xr-x 3 root root 224 Jan 6 2009 share / # ls -la /usr/local/ drwxr-xr-x 3 root root 232 Nov 30 2010 . drwxr-xr-x 7 root root 480 Nov 30 2010 .. drwxr-xr-x 5 root root 424 Nov 30 2010 cloudengines / # ls -la /usr/local/cloudengines/ drwxr-xr-x 5 root root 424 Nov 30 2010 . drwxr-xr-x 3 root root 232 Nov 30 2010 .. drwxr-xr-x 2 root root 1144 Nov 30 2010 bin drwxr-xr-x 3 root root 296 Jan 1 00:00 etc -rw-r--r-- 1 root root 49 Jan 1 00:00 hbplug.conf drwxr-xr-x 2 root root 1424 Nov 30 2010 lib / #
|
Re: OpenWRT for PogoPlug Pro rootfs tar May 06, 2015 07:18PM |
Admin Registered: 13 years ago Posts: 18,543 |
habibie,
Yes. It was OpenWrt kernel, but with Pogo rootfs. Simple: somehow the OpenWrt rootfs in NAND was not loaded, but the old Pogo rootfs in NAND was. The kernel uImage resides in a different partition. So either your installation of OpenWrt rootfs to NAND was bad and it fallbacked to the Pogo rootfs, or the load address was incorrect (I have not looked closely at your log above so I can't say).
To remove u-boot env, set it to nothing:
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Yes. It was OpenWrt kernel, but with Pogo rootfs. Simple: somehow the OpenWrt rootfs in NAND was not loaded, but the old Pogo rootfs in NAND was. The kernel uImage resides in a different partition. So either your installation of OpenWrt rootfs to NAND was bad and it fallbacked to the Pogo rootfs, or the load address was incorrect (I have not looked closely at your log above so I can't say).
To remove u-boot env, set it to nothing:
setenv dt_load_initrd
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: OpenWRT for PogoPlug Pro rootfs tar May 06, 2015 09:49PM |
Registered: 11 years ago Posts: 1,303 |
|
Re: OpenWRT for PogoPlug Pro rootfs tar May 06, 2015 10:26PM |
Registered: 11 years ago Posts: 1,303 |
Bodhi,
I think I am beginning to understand why my PogoPlug Pro 02 is booting off of the NAND storage. Remember this dt_bootm=bootm $uimage_addr - $dtb_addr. If you look at my environment settings, the uimage_addr is set to uimage_addr=0x60500000. Isn't that the address on NAND storage and not on an external USB storage?
What I ultimately want to achieve is to have replace the stock firmware with a self-built OpenWRT firmware. This way, I can have my device to boot either from NAND storage and/or any external storage, i.e. SATA or USB storage, etc., if they are available. I certainly will appreciate if anyone can help.
I think I am beginning to understand why my PogoPlug Pro 02 is booting off of the NAND storage. Remember this dt_bootm=bootm $uimage_addr - $dtb_addr. If you look at my environment settings, the uimage_addr is set to uimage_addr=0x60500000. Isn't that the address on NAND storage and not on an external USB storage?
What I ultimately want to achieve is to have replace the stock firmware with a self-built OpenWRT firmware. This way, I can have my device to boot either from NAND storage and/or any external storage, i.e. SATA or USB storage, etc., if they are available. I certainly will appreciate if anyone can help.
|
Re: OpenWRT for PogoPlug Pro rootfs tar May 06, 2015 11:17PM |
Registered: 11 years ago Posts: 165 |
habibie Wrote:
-------------------------------------------------------
> What I ultimately want to achieve is to have
> replace the stock firmware with a self-built
> OpenWRT firmware. This way, I can have my device
> to boot either from NAND storage and/or any
> external storage, i.e. SATA or USB storage, etc.,
> if they are available. I certainly will appreciate
> if anyone can help.
@habibie, what's wrong with my tutorial then?
OpenWRT on Pogoplug v3/Oxnas (Pro/Classic))
Just replace the snapshot files (openwrt-oxnas-pogoplug-pro-squashfs-sysupgrade.tar and zImage), with the rootfs and kernel from your build.
Not really sure why you feel the need to build your own image though. Typically, the biggest advantage to building your own OpenWRT build is to save space, but since the Pogoplug has 128MB, that shouldn't be a concern.
-grayman4hire
======================================
Pogoplug V2 and V3 Serial Connection
Tutorial - Pogoplug v4 (Series 4 and Mobile) with Linux (Debian or Arch)
OpenWRT on Pogoplug Mobile
Tutorial - Pogoplug E02/V4 with Arch Linux ARM
Hacking the Pogoplug v3/Oxnas (Pro/Classic) with Debian
OpenWRT on Pogoplug v3/Oxnas (Pro/Classic)
Edited 1 time(s). Last edit at 05/06/2015 11:19PM by grayman4hire.
-------------------------------------------------------
> What I ultimately want to achieve is to have
> replace the stock firmware with a self-built
> OpenWRT firmware. This way, I can have my device
> to boot either from NAND storage and/or any
> external storage, i.e. SATA or USB storage, etc.,
> if they are available. I certainly will appreciate
> if anyone can help.
@habibie, what's wrong with my tutorial then?
OpenWRT on Pogoplug v3/Oxnas (Pro/Classic))
Just replace the snapshot files (openwrt-oxnas-pogoplug-pro-squashfs-sysupgrade.tar and zImage), with the rootfs and kernel from your build.
Not really sure why you feel the need to build your own image though. Typically, the biggest advantage to building your own OpenWRT build is to save space, but since the Pogoplug has 128MB, that shouldn't be a concern.
-grayman4hire
======================================
Pogoplug V2 and V3 Serial Connection
Tutorial - Pogoplug v4 (Series 4 and Mobile) with Linux (Debian or Arch)
OpenWRT on Pogoplug Mobile
Tutorial - Pogoplug E02/V4 with Arch Linux ARM
Hacking the Pogoplug v3/Oxnas (Pro/Classic) with Debian
OpenWRT on Pogoplug v3/Oxnas (Pro/Classic)
Edited 1 time(s). Last edit at 05/06/2015 11:19PM by grayman4hire.
|
Re: OpenWRT for PogoPlug Pro rootfs tar May 07, 2015 01:44AM |
Admin Registered: 13 years ago Posts: 18,543 |
habibie,
> storage. Remember this dt_bootm=bootm
> $uimage_addr - $dtb_addr. If you look at my
> environment settings, the uimage_addr is
> set to uimage_addr=0x60500000. Isn't that
> the address on NAND storage and not on an external
> USB storage?
No, it is the RAM address of the region that you've loaded the image into. Just so happen that the base address is 0x60000000.
>
> What I ultimately want to achieve is to have
> replace the stock firmware with a self-built
> OpenWRT firmware. This way, I can have my device
> to boot either from NAND storage and/or any
> external storage, i.e. SATA or USB storage, etc.,
> if they are available. I certainly will appreciate
> if anyone can help.
As graymanforhire said, you could use his instruction, which is very well written and has most everything you need.
You just need to adapt it to your specific set up. Now if you want to boot from USB, and have the system on USB, then you'll need to modify the u-boot envs to load zImage from there, and make sure the env point to the USB rootfs (not NAND).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> storage. Remember this dt_bootm=bootm
> $uimage_addr - $dtb_addr. If you look at my
> environment settings, the uimage_addr is
> set to uimage_addr=0x60500000. Isn't that
> the address on NAND storage and not on an external
> USB storage?
No, it is the RAM address of the region that you've loaded the image into. Just so happen that the base address is 0x60000000.
>
> What I ultimately want to achieve is to have
> replace the stock firmware with a self-built
> OpenWRT firmware. This way, I can have my device
> to boot either from NAND storage and/or any
> external storage, i.e. SATA or USB storage, etc.,
> if they are available. I certainly will appreciate
> if anyone can help.
As graymanforhire said, you could use his instruction, which is very well written and has most everything you need.
You just need to adapt it to your specific set up. Now if you want to boot from USB, and have the system on USB, then you'll need to modify the u-boot envs to load zImage from there, and make sure the env point to the USB rootfs (not NAND).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
