No one cares about NFSv2. https://forum.openwrt.org/viewtopic.php?id=68632 The compile command is in openwrt/package/kernel/linux/modules/fs.mk define KernelPackage/fs-nfsd SUBMENU:=$(FS_MENU) TITLE:=NFS kernel server support DEPENDS:=+kmod-fs-nfs-common +kmod-fs-exportfs KCONFIG:= \ CONFIG_NFSD \ CONFIG_NFSD_FAULT_INJECTION=n FILES:=$(LINUX_DIR)/fs/nfsd/by SiliCAT - uBoot
bodhi Wrote: ------------------------------------------------------- > SiliCAT, > > You should find out why your OpenWrt share does > not support nfs v2/3. Booting kernel with tftp is > OK, but it is another extra part that is > uneccessary and make your backup little bit more > akward. Hi bodhi, I'll try to figure this out when I have some free time.by SiliCAT - uBoot
Just set console fw_setenv console 'ttyS0,115200' And the script also works now.by SiliCAT - uBoot
Hi bodhi, You are right. Your env works. setenv bootcmd_nfs 'setenv serverip "192.168.101.101"; setenv nfs_server "192.168.101.101"; setenv nfs_path "/srv/nfs/hosts/PogoplugV4"; setenv nfs_bootcmd "run nfs_set_bootargs; run nfs_boot"; setenv nfs_ipconfig "192.168.101.10:192.168.101.101:192.168.101.101:255.255.255.0:PogoplugV4::off"by SiliCAT - uBoot
The script to set the envs: #!/bin/bash fw_setenv autoload 'no' fw_setenv net_bootcmd 'run net_check_dhcp_c; run net_check_dhcp_s; run net_set_bootargs; run net_boot' fw_setenv net_boot 'tftp 0x1c00000 $net_tftp_dtb; tftp 0x800000 $net_tftp_kernel; echo; echo ** Kernel Boot Arguments: $bootargs; echo;if tftp 0x1100000 $net_tftp_initrd; then bootm 0x800000 0x11by SiliCAT - uBoot
Meanwhile, the boot process can complete without uInitrd. U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700) Pogoplug V4 SoC: Kirkwood 88F6192_A1 DRAM: 128 MiB WARNING: Caches not enabled NAND: 128 MiB MMC: kwsdio: 0 In: serial Out: serial Err: serial Net: egiga0 Using egiga0 device ARP Retry count exceeded; starting again ping failed; host 172.16.16.118 is nby SiliCAT - uBoot
Hi bodhi, My entire serial boot log is: U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700) Pogoplug V4 SoC: Kirkwood 88F6192_A1 DRAM: 128 MiB WARNING: Caches not enabled NAND: 128 MiB MMC: kwsdio: 0 In: serial Out: serial Err: serial Net: egiga0 Using egiga0 device ARP Retry count exceeded; starting again ping failed; host 172.16.16.118 is not alive Using eby SiliCAT - uBoot
bodhi Wrote: ------------------------------------------------------- > > OpenWrt does not use uInitrd, so booting that > uImage is enough. Booting Debian or Arch or any > other distro with normal drives, uInitrd is > strongly recommended. Even with a bare bone > initrd, it's very useful. In some configuration, > you must have initrd to make it work. Hi bodhby SiliCAT - uBoot
I have to use tftp to load the uImage setenv net_boot 'tftp 0x1c00000 $net_tftp_dtb; tftp 0x800000 $net_tftp_kernel; echo; echo ** Kernel Boot Arguments: $bootargs; echo;if tftp 0x1100000 $net_tftp_initrd; then bootm 0x800000 0x1100000 0x1c00000;else bootm 0x800000 - 0x1c00000;fi' It works. For the new U-Boot 2016.05, if the uInitrd is loaded, the boot process will break. If juby SiliCAT - uBoot
root@OpenWrt:~# cat /proc/fs/nfsd/versions -2 +3 It seems the nfs v2 is disabled. I'm not very sure.by SiliCAT - uBoot
I tried a simple command nfs 0x1c00000 172.16.16.101:/tmp/nfs/kirkwood-pogoplug_v4.dtb It doesn't work. Using egiga0 device File transfer via NFS from server 172.16.16.101; our IP address is 172.16.16.117 Filename '/tmp/nfs/kirkwood-pogoplug_v4.dtb'. Load address: 0x1c00000 Loading: *** ERROR: File lookup fail I can get the remote nfs file 172.16.16.101:/tmp/nfs/kirkby SiliCAT - uBoot
bodhi Wrote: ------------------------------------------------------- > > Modify bootcmd_nfs above for OpenWrt : > > - take out the uInitrd related stuff. > - adjust the path of uImage and the DTB > - adjust the hostname and IP addresses to conform > with your environment. Hi bodhi, Thanks for your help. I tried this: setenv bootcmd_nfs_test 'seby SiliCAT - uBoot
TEST1: Old uBoot, Old rootfs Failed. NFS Server: OpenWrt Chaos Calmer 15.05.1 @ TP-Link TL-WR1043N/ND v2 rootfs: 4.2.0-kirkwood-tld-1 NFS Client: U-Boot 2014.07-tld-1 @ Pogoplug V4 Pogov4> run net_bootcmd BOOTP broadcast 1 DHCP client bound to address 172.16.16.221 ** net_dhcp_c = 1 --> Getting IP Settings by DHCP ** IP Address: 172.16.16.221 ** Subnet Mask: 255.255.255.0by SiliCAT - uBoot
Hi bodhi, Thanks a lot. Very appreciate for your help. I'm going to test my envs recently when I get some spare time. I'll update my test later.by SiliCAT - uBoot
With the new uBoot, the default env var bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec According to some tutorial about NFS boot, Bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run net_bootcmd; run rescue_bootcmd; run pogo_bootcmd; reset or bootcmd=run bootcmd_usb; run bootcmd_mmc; run bootcmd_sata; run net_bootcmby SiliCAT - uBoot
bodhi Wrote: ------------------------------------------------------- > See this Wiki thread: > http://forum.doozan.com/read.php?2,23630 > > Section > > QuoteBackup > > CrashPlan 4.3.0 > Backup/Restore rootfs using tar command Hi bodhi, Thanks for your kind help. I didn't know theres is a wiki. So helpful! Seems I have a lot to read:)by SiliCAT - Debian
Box: Pogoplug V4 As we all know, the SD cards wear out quickly. I’m thinking of backing up the whole system occasionally. I used this command to backup once, but when I extracted the package to another SD card, the system on the new card didn’t work, the boot process failed. I mounted the SD card at the mountpoint /tmp/rootfs on my PC, then root@debian:/tmp/rootfs# tar -cvpzf ~/Backuby SiliCAT - Debian
Hi bodhi, Thank you for your reply. This is a more feasible and practicable plan. Maybe It's time for me to give up on finding a perfect approach.by SiliCAT - Debian
Box: Pogoplug V4 I installed Debian on the SD card. I have an external usb hard disk, I want to achieve this: every time when the disk is connected, the system will provide file service and start some programs. So I use udev rules and scripts. The scripts works well when I plug in the disk driver or unplug it from the usb port. But when the system reboot, the scripts do not work during theby SiliCAT - Debian
Hi bodhi, Sorry for report late. These two days, I have done reboot for nearly 20 times, but only 1 time, It couldn't find the usb device, and just at the same time, the sd card corrupted. I'm confused, because the day before, it lost usb device almost every time.by SiliCAT - Debian
bodhi Wrote: ------------------------------------------------------- > If this is a USB hard drive then it is a common > issue. > > If you have serial console or net console, reboot, > interrupt console and, > > > ver > printenv > usb start > boot > > and post the entire log here. Yes, it is a USB hard drive. Thank you for your help. Iby SiliCAT - Debian
Box: Pogoplug V4 Kernel 4.8 with kernel 4.6 DTB Problem: After reboot (shutdown -r now), Can not see usb device. -- It didn't happen every time. But it happened most of the time. But if shutdown and turn the power off, then turn it on, the device may come back.by SiliCAT - Debian
It works [ 163.384855] usb 3-2: new SuperSpeed USB device number 2 using xhci_hcd [ 163.415893] usb 3-2: New USB device found, idVendor=174c, idProduct=1153 [ 163.422583] usb 3-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 163.430079] usb 3-2: Product: AS2115 [ 163.433646] usb 3-2: Manufacturer: ASMedia [ 163.438082] usb 3-2: SerialNumber: 00000000000000000000 [ 16by SiliCAT - Debian
Thank you, bodhi. I'll try the attached kirkwood-pogoplug_v4.dtb of that post.by SiliCAT - Debian
Box: Pogoplug V4 Just updated to Kernel 4.8 Kirkwood (10 Oct 2016). Nothing happened when plugged in usb external hard drive.by SiliCAT - Debian
Hi bodhi, You are right. I labeled the file system as "rootfs", and it worked. Now I have a box running with the latest uBoot and the recent Debian. Just one thing maybe I need to mention. After the first "apt-get update && apt-get upgrade" perhaps we have to reboot the box. My Debian got messed up when I executed "apt-get update && apt-get upgradby SiliCAT - Debian
Hi bodhi, Very appreciated for your help. I tried 5 times today, repeated the steps of making a new rootfs, but each time I failed to boot into the system. I even tried to use a new SD card, but got the same result. Is there any way to log the booting process? Thanks again. I made the rootfs in an old Pogoplug box with the uboot.2014.07. root@Pogoplug:~# mkfs -t ext3 /dev/mmcblk0p1by SiliCAT - Debian
Box: Pogoplug V4 Just flashed the 2016.05 U-Boot and the default envs. and make a Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi rootfs on sdcard according to the 20-Feb-2016 tutorial. The green LED blinked for a while longer than normal. And when the LED blink stopped, I could't find the box on the local LAN. Could you give me some advice? Thanks the netconsole: $ nc -l -u -p 66by SiliCAT - Debian
Very appreciated for your help. I see, Next time when I ask I will post more info. Thanks again.by SiliCAT - uBoot