Show all posts by user

Re: New rootfs for Pogo V4 doesn't work - 8 months ago

LeggoMyEggo Wrote: ------------------------------------------------------- > Did you label your boot drive "rootfs" > > e2label /dev/sd(x) rootfs > > or when you format the drive > > mkfs.ext3 -L rootfs /dev/sd(x) > > You can check the existing drive if it has a label > by > > e2label /dev/sd(x) Thank you for your reply. I'

by SiliCAT - Debian

New rootfs for Pogo V4 doesn't work - 8 months ago

Tested 6.5.7 and 6.6.3 New installation from the downloaded bodhi.tar.bz2 files. UART: ...... ...... [ 13.409141][ T1] Run /init as init process Loading, please wait... Starting systemd-udevd version 252.19-1~deb12u1 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-t

by SiliCAT - Debian

Re: Use uEnv.txt for Testing - 6 years ago

Hi bodhi, It is different. ii libnfsidmap2:armhf 0.25-5 armhf NFS idmapping library ii nfs-common 1:1.2.8-9ubuntu12.1 armhf NFS support files common to client and server ii nfs-kernel-server 1:1.2.8-9ubuntu12.1 armhf support for NFS kern

by SiliCAT - uBoot

Re: CUPS printing is very slow on Debian stretch - 6 years ago

Upgraded to 4.12.1, the CUPS works fine. Tested 4.14.1, it was frozen again. Didn't test 4.13.5 and 4.12.8

by SiliCAT - Debian

Re: Use uEnv.txt for Testing - 6 years ago

Hi bodih, On the server: silicat@odroid:/srv/nfs-export/Testbed/pogoplug.hosts/rootfs/4.4.0$ cd silicat@odroid:~$ ls -l /srv total 4 drwxr-xr-x 3 root root 4096 Jan 26 07:46 nfs-export silicat@odroid:~$ ls -l /srv/nfs-export total 4 drwxr-xr-x 3 root root 4096 Jan 26 07:44 Testbed silicat@odroid:~$ ls -l /srv/nfs-export/Testbed/pogoplug.hosts/rootfs/4.4.0/ total 4 drwxr-xr-x 21 roo

by SiliCAT - uBoot

Re: Use uEnv.txt for Testing - 6 years ago

Hi bodhi, I managed to get a nfs server on Ubuntu 16.04.3 LTS (Xenial Xerus) Settings on the server: /srv/nfs-export *(rw,sync,no_subtree_check,no_root_squash) Without the rw option, it still got a read-only rootfs on the pogo client. silicat@pogotest:~$ touch test touch: cannot touch 'test': Read-only file system My uEnv.txt: autoload=no nfs_server=172.16.16.207

by SiliCAT - uBoot

CUPS printing is very slow on Debian stretch - 6 years ago

Pogo kept hanging when received print jobs. kworker consumed almost all the resources on the Pogo and that caused no response of the windows 10 apps. Have to downgrade to 4.8.3-kirkwood-tld-1

by SiliCAT - Debian

Re: Use uEnv.txt for Testing - 6 years ago

Hi bodhi, I don't have a Debian stretch NFS server yet. I think you are right. I believe there are some differences between the NFS on WRT and on the Debian, which lead to different result. - SiliCAT

by SiliCAT - uBoot

Re: Use uEnv.txt for Testing - 6 years ago

Hi bodhi, Looks like there is no root user in asuswrt-merlin. admin is Asuswrt's UID 1. It's root, but with a different name. and admin will be replaced by a login ID which is chosen by the user. There is a root group.

by SiliCAT - uBoot

Re: Use uEnv.txt for Testing - 6 years ago

Hi bodhi, The top level on the router: SiliCAT@RT-AC68U:/tmp/mnt/sda1/nfs/pogo.hosts# ls -l drwxr-xr-x 21 SiliCAT root 4096 Jan 24 13:00 PogoplugV4 All my envs in the uEnv.txt are autoload=no nfs_server=192.168.1.1 nfs_path=/tmp/mnt/sda1/nfs/pogo.hosts/PogoplugV4 tftp_load_uimage=tftp 0x800000 uImage tftp_load_uinitrd=tftp 0x1100000 uInitrd tftp_load_dtb=tftp 0x1c0000

by SiliCAT - uBoot

Re: Use uEnv.txt for Testing - 6 years ago

There might be a mistake in the Wiki. root=/dev/nfs rw without the rw, the filesystem is mounted as read-only.

by SiliCAT - uBoot

Re: Use uEnv.txt for Testing - 6 years ago

Hi bodhi, Making the whole booting process on NFSv3, is elegant and perfect. But I met another problem, the Pogo is able to boot, but the rootfs is read-only. (I can mount the NFS rootfs on my rpi and it's a rw filesystem) I've changed fstab to # <file system> <mount point> <type> <options> <dump> <pass> /dev/root /

by SiliCAT - uBoot

Re: Use uEnv.txt for Testing - 6 years ago

Hi bodhi, I tried, but it was not what I expected. U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:34:01 -0700) Pogoplug V4 SoC: Kirkwood 88F6192_A1 DRAM: 128 MiB WARNING: Caches not enabled NAND: 128 MiB MMC: MVEBU_MMC: 0 In: serial Out: serial Err: serial Net: egiga0 No link on egiga0 ping failed; host 172.16.16.118 is not alive Using egiga0 device ARP Retry count

by SiliCAT - uBoot

Re: Use uEnv.txt for Testing - 6 years ago

Hi bodhi, Very good reference and very clear guidance. But I encountered the same problem, as I was using the old uboot. nfs_load_uimage=nfs 0x800000 $nfs_server:$nfs_path/boot/uImage nfs_load_uinitrd=nfs 0x1100000 $nfs_server:$nfs_path/boot/uInitrd nfs_load_dtb=nfs 0x1c00000 $nfs_server:$nfs_path/boot/dts/kirkwood-pogo_e02.dtb These will make the booting process hang up. Luckily Merlin p

by SiliCAT - uBoot

Use uEnv.txt for Testing - 6 years ago

My Pogo server have run on the NFS for more than 1 year, and I never worry about the lifespan of the SD card. An old IDE hard disk is attached to the Openwrt router by USB 2.0 and provide a stable rootfs for the Pogo. Several months ago I got a new ASUS-merlin router, I am going to move the rootfs to the new one. This time, I'll try using uEnv.txt to test the NFS booting. I put all tsunu

by SiliCAT - uBoot

Re: Update uboot from 2016.05 - 6 years ago

I made a stupid mistake, I carelessly flashed the environment file instead of the environment.img Is there any potential damage for my Pogo? root@Pogoplug:~/burn# ~/tools/nandwrite -s 786432 /dev/mtd0 uboot.2016.05-tld-1.environment Input file is not page-aligned. Use the padding option. nandwrite: error!: Data was only partially written due to error error 0 (Success)

by SiliCAT - uBoot

Re: Update uboot from 2016.05 - 6 years ago

Hi bodhi, Thank you for caring for my to-do-list. I will burn the nand these days. - SiliCAT

by SiliCAT - uBoot

Update uboot from 2016.05 - 6 years ago

A list of only 6 checked items, that is what I need to do: ☐ Check /etc/fw_env.config and /proc/mtd ☐ Set ethaddr ☑ Dump NAND mtd0 and Save envs ☑ No bad block ──────────── ☑ Extract the archive ☑ Erase mtd0 ☑ Write image to NAND ──────────── ☐ Flashing default u-boot envs image ──────────── ☑

by SiliCAT - uBoot

Re: Can not connect to the network - 6 years ago

It's my fault caused the problem. I unpacked the rootfs.tar.bz2 file on an ext4 partition. Now I've got a brand new rootfs-4.12.1 with kernel-4.14.1, I'm going to update the uboot.

by SiliCAT - Debian

Re: Can not connect to the network - 6 years ago

The problem showed up again and I'm testing.

by SiliCAT - Debian

Re: Can not connect to the network - 6 years ago

Hi bodhi, Thank you for your suggestions and with them finally the Pogo is back to work now. In fact I've tried the 4.12.1 rootfs (24 Jul 2017) yesterday, and failed. So, today when I saw the light became solid green and there was no new client showed up on the list of the router, I turned the power off quickly. I had to check the uboot environment again to see if I can find something wr

by SiliCAT - Debian

Re: Can not connect to the network - 6 years ago

I tried to use netconsole but I couldn't interact with uBoot. nc -l -u -p 6666 & nc -u 172.16.16.117 6666 U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700) Pogoplug V4 gcc (Debian 4.9.2-10) 4.9.2 GNU ld (GNU Binutils for Debian) 2.25 Hit any key to stop autoboot: 3 I used MintLinux LiveCD on a USB Flash Drives at my laptop. I remembered I was able to enter interactive

by SiliCAT - Debian

Re: Can not connect to the network - 6 years ago

The result of the file system checking: root@raspberrypi:~# e2fsck /dev/sda1 e2fsck 1.43.4 (31-Jan-2017) rootfs: clean, 14297/3907584 files, 419724/15630080 blocks A static IP doesn't work. root@raspberrypi:/mnt/flash.tmp/etc/network# cat interfaces auto lo eth0 iface lo inet loopback #iface eth0 inet dhcp iface eth0 inet static address 172.16.16.117 netmask

by SiliCAT - Debian

Re: Can not connect to the network - 6 years ago

Hi bodhi, Thank you for your help. 1. Three or four minutes after the Pogoplug was turned on, the green LED stopped blink and became solid green. But could not see it from the ASUS-Merlin route. The log of Dnsmasq showed that there was no DHCPREQUEST. 2. The rootfs is on the MicroSD card. It is mounted on another linux box as /dev/sda1 root@raspberrypi:~# e2label /dev/sda1 rootfs roo

by SiliCAT - Debian

Re: Can not connect to the network - 6 years ago

I can't believe its network hardware is damaged for I just used it for several times and it worked fine. And just now I got some solid evidence for I remembered I set the uboot ipaddr as 172.16.16.117. fw_setenv ipaddr '172.16.16.117' After it booted, I was able to ping 172.16.16.117 for two or three minutes. So, the network adapter works.

by SiliCAT - Debian

Re: Can not connect to the network - 6 years ago

Yes, I can use it to boot another V4 (without USB3.0) device, with network connect. But perhaps the two devices don't have the same uboot.

by SiliCAT - Debian

Can not connect to the network - 6 years ago

I had two Pogoplug Mobile devices, one is used as NAS and one is for testing. The first one runs daily routine tasks for more than 1 year and everything is OK. and recently I'm thinking about upgrading its uboot and rootfs and kernel. So I found out the one I used for testing which I have laid aside for a long time, and planned to give the upgrading procedure a try. But the box couldn'

by SiliCAT - Debian

Re: What is the correct "bootcmd" value for NFS with the new uBoot? - 7 years ago

bodhi Wrote: ------------------------------------------------------- > I will post my shell script for upgrading kernel > in NFS rootfs using chroot. Remind me if I forget > :) Cool! Waiting for the upgrading script:)

by SiliCAT - uBoot

Re: What is the correct "bootcmd" value for NFS with the new uBoot? - 7 years ago

> I've been using the same Sandisk flash drives as > rootfs for 4,5 years on most of my plugs, running > 24/7. What I did to make sure they last: > http://forum.doozan.com/read.php?2,13702,13704#msg > -13704 > > And I always have a master backup for all Kirkwood > plugs. I just use that to create a new one, tweak > a few thing: hostname, static ip address,

by SiliCAT - uBoot

Re: What is the correct "bootcmd" value for NFS with the new uBoot? - 7 years ago

I think this is the reasons why I use OpenWrt for the NFS server: 1. I found using the SD card or the Flash Drive as the rootfs is unreliable, and I have to worry about the lifespan of the memory chips. 2. I don't want an extra device and extra energy consumption. An OpenWRT router is always power on.

by SiliCAT - uBoot