Linux Kernel 5.15.158 Oxnas (OX820) Pogo V3 package and Debian rootfs

root@pogoplugpro:~# /usr/local/cloudengines/bin/blparam
bootdelay=2
baudrate=115200
autoload=n
netmask=255.255.0.0
bootfile="uImage"
kernflmode=s
load_nand=nboot 60500000 0 200000
load_nand2=nboot 60500000 0 800000
boot=bootm 60500000
boot_nand=run load_nand boot || run load_nand2 boot
stdin=serial
stdout=serial
stderr=serial
ethaddr=00:25:31:01:CC:A0
cesvcid=K6H9QRT45WB3EYT66YDWH5P7WN
ceboardver=PPRO1
serverip=192.168.33.2
ipaddr=192.168.33.195
bootargs_stock=root=ubi0:rootfs ubi.mtd=2,512 rootfstype=ubifs console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 mem=128M poweroutage=yes
load_custom_nand=nboot 60500000 0 500000
load_custom_nand2=nboot 60500000 0 B00000
boot_custom=run load_custom_nand boot || run load_custom_nand2 boot
bootargs=root=/dev/sda1 ubi.mtd=2,512 rootfstype=ext3 console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 mem=128M poweroutage=yes rootwait
bootcmd=run boot_custom
root@pogoplugpro:~#

wwchan,

It's been a while that we do this from stock OS. Usually you just install new u-boot and new rootfs at the same time.

Hopefully I can find the instruction or the log of what I did a few years ago.

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

Hi Bodhi,

Thanks, I hope it's not costing too much of your time. If you tell me it is safe enough to go straight to your latest rootfs and uboot at the same time for my situation. I will sure go ahead...

Cheers....

wwchan,

For this OXNAS plug, it is safe to do that (there is a rescue mechanism using internal SATA port if anything goes wrong).

And as always, if u-boot installation went OK, then with a serial console you would be able to fix any booting problem.

Create rootfs using USB, and then update u-boot. Before reboot, if you'd like, post the entire log here, I'll double check it for you.

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

Hi Bodhi,

I have well prepared by getting the serial console ready and tested working

Now I have done the following:
1) Installed latest uboot uboot.2015.10-tld-1.ox820.bodhi.tar
step through 1-14

root@pogoplugpro:~# fw_printenv
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm 0x60500000 0x60e00000 0x62c00000; else bootm 0x60500000 0x60e00000; fi; else if run load_dtb; then bootm 0x60500000 - 0x62c00000; else bootm 0x60500000; fi; fi
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; reset
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
bootdev=usb
usb_custom_params=zswap.enabled=1
device=0:1
devices=usb ide
disks=0 1 2 3
ethact=mii0
if_netconsole=ping $serverip
dtb_file=/boot/dts/ox820-pogoplug-pro.dtb
load_dtb=echo loading DTB $dtb_file ...; ext2load $bootdev $device 0x62c00000 $dtb_file
load_initrd=echo loading uInitrd ...; ext2load $bootdev $device 0x60e00000 /boot/uInitrd
load_uimage=echo loading uImage ...; ext2load $bootdev $device 0x60500000 /boot/uImage
mainlineLinux=yes
mtdids=nand0=41000000.nand
mtdparts=mtdparts=41000000.nand:14m(boot),-(data)
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start";  setenv scan_ide "ide reset";  setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if ext2load $dev $disknum:1 0x60500000 /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
uenv_import=echo importing envs ...; env import -t 0x60500000
uenv_init_devices=setenv init_usb "usb start";  setenv init_ide "ide reset";  setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices;  do for disknum in 0; do run uenv_read_disk; done; done;
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 0x60500000 /boot/uEnv.txt; then setenv uenv_loaded 1; fi
usb_ready_retry=15
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi
preboot=run preboot_nc
ethaddr=00:25:31:01:CC:XX
ipaddr=192.168.xxx.196
serverip=192.168.xxx.248

2) prepared USB using Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2
using steps "Updated 02 Nov 2014: " INSTALLATION step 1:

but don't know how to setup the uboot envs to the following example

set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
rootfstype=ext3

step 2-4 are ok

should I now proceed to step 5 "Done, take this USB rootfs to your plug and cold start."

should I do INSTALLATION step 1 like this?

fw_setenv set_bootargs_usb 'setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts'
fw_setenv rootfstype 'ext3'

but not sure how this fit into the existing uboot envs...



Edited 1 time(s). Last edit at 07/31/2017 05:55AM by wwchan.

wwchan,


> using steps "Updated 02 Nov 2014: " INSTALLATION s
> tep 1:
>
> but don't know how to setup the uboot envs to the
> following example
>
>

> set_bootargs_usb=setenv bootargs console=$console
> root=$usb_root rootdelay=$rootdelay rootfstype=$ro
> otfstype $mtdparts
> rootfstype=ext3
>

>
> step 2-4 are ok
>
> should I now proceed to step 5 "Done, take this US
> B rootfs to your plug and cold start."

Yes, that set env is Ok to skip. That was only an example.

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

wwchan Wrote:
-------------------------------------------------------
> should I do INSTALLATION step 1 like this?
>
>

> fw_setenv set_bootargs_usb 'setenv bootargs consol
> e=$console root=$usb_root rootdelay=$rootdelay roo
> tfstype=$rootfstype $mtdparts'
> fw_setenv rootfstype 'ext3'
>

No, you can skip it.

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

So I am all set to replace the USB and cold boot?

wwchan,

BTW, I will release a new stretch rootfs 4..4.54 within a week or so.

You should proceed and try booting with the 3.17 rootfs. But once you get it booting, don't do much with it.

Because you can repeat the USB rootfs creation easily and boot with the new one, without changing anything.

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

wwchan Wrote:
-------------------------------------------------------
> So I am all set to replace the USB and cold boot?

Yes. And post the entire serial console if you see anything abnormal.

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

something's wrong... but solid green light

Attempting to set PLLA to 850 MHz ...
  0
  plla_ctrl2 : 006                                                        US1  for device 0
ide_preit Sector        Num Sectors     UU      000105e2-02     82
l
 no IDE devices avSc0 ms (0 Bytes/s)
F09733 bytes read in 1970d-1
   Created:      2inux Kernel Image (unco
  t:  60000000
   VerifyOKl ...

   Created:      2017-07-26   9:02:03 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4109669 Bytes = 3.9 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 ... OK
## Flattened Device Tree blob at 62c00000
   Booting using the fdt blob at 0x62c00000
   Loading Kernel Image ... OK
   Loading Ramdisk to 67c4e000, end 67e2afd4 ... OK
   Loading Device Tree to 67c49000, end 67c4db74 ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

stay there forever and nothing found in the network...

redo another usb rootfs without step 4 made it work!!!



Edited 1 time(s). Last edit at 07/31/2017 09:15AM by wwchan.

wwchan,

Cool! now if there is any problem/questions, please open a new thread for troubleshooting/questions.

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

Rootfs Debian-4.4.54-oxnas-tld-1-rootfs-bodhi.tar.bz2 was uploaded. Please see 1st post for download link.

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

Kernel linux-4.4.79-oxnas-tld-1 package was uploaded. Please see 1st post for download link.

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

Last post moved here:

http://forum.doozan.com/read.php?2,35961

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

@Bodhi,
i am just testing your latest rootfs with kernel upgraded to 4.4.79 on two Pogoplug Pro devices, one with original RT3090 wifi card and one with AR9287 wifi card. With AR9287 the wifi works well. Both interfaces are working with your kernel. I am wondering that the device name is renamed from wlan0 to wlp0s0.

dmesg

[    3.378900] rt2800pci 0000:00:00.0 wlp0s0: renamed from wlan0

wpa_supplicant can't be used because rfkill device is not available. Can you please activate this function in your next kernel update?

rfkill: Cannot open RFKILL control device

- shv



Edited 6 time(s). Last edit at 09/17/2017 04:33AM by shv.

Hi shv,

Quote

I am wondering that the device name is renamed from wlan0 to wlp0s0.

dmesg
[ 3.378900] rt2800pci 0000:00:00.0 wlp0s0: renamed from wlan0

This is the new naming scheme in Debian stretch (predictable network device names). So any script that uses the old naming convention must be updated to use new names.

Quote

> wpa_supplicant can't be used because rfkill device
> is not available. Can you please activate this
> function in your next kernel update?

> rfkill: Cannot open RFKILL control device

Sure, I will take a look.

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

Hello bodhi,
I want to recommend to add multicore zip pakages lbzip2 and pigz if you will update the rootfs. Additionally you might add some links to these executables into /usr/local/bin:

lrwxrwxrwx  1 root staff     21 Sep 13 01:47 bunzip2 -> /usr//bin/lbzip2
lrwxrwxrwx  1 root staff     21 Sep 13 01:47 bzcat -> /usr/bin/lbzip2
lrwxrwxrwx  1 root staff     21 Sep 13 01:47 bzip2 -> /usr/bin/lbzip2
lrwxrwxrwx  1 root staff     13 Oct  5  2014 gzip -> /usr/bin/pigz
lrwxrwxrwx  1 root staff      6 May 26  2016 lbunzip2 -> /usr/bin/lbzip2
lrwxrwxrwx  1 root staff      6 May 26  2016 lbzcat -> /usr/bin/lbzip2

I just tried to replace the system on my SATA HDD root partition. It is an ext4 partition and the bootloader is configured to boot rootfs filesystem on ext4 partition. But your rootfs seams to have problems with ext4 rootfs partitions.

Begin: Loading essential drivers ... done.
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/sda1] fsck.ext4 -a -C0 /dev/sda1
rootfs-ide: clean, 14009/394352 files, 178893/1575424 blocks
done.
[   14.579809] EXT4-fs (sda1): 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.
findfs: unable to resolve 'LABEL=rootfs'
[....] Starting the hotplug events dispatcher: systemd-udevdstarting version 232
. ok
[ ok ] Synthesizing the initial hotplug events...done.
[   18.472811] random: nonblocking pool is initialized
[ ok ] Waiting for /dev to be fully populated...done.
findfs: unable to resolve 'LABEL=rootfs'
[ ok ] Activating swap...done.

Usage:
 mountpoint [-qd] /path/to/directory
 mountpoint -x /dev/device

Check whether a directory or file is a mountpoint.

Options:
 -q, --quiet        quiet mode - don't print anything
 -d, --fs-devno     print maj:min device number of the filesystem
 -x, --devno        print maj:min device number of the block device

 -h, --help     display this help and exit
 -V, --version  output version information and exit

For more details see mountpoint(1).
mount: can't find LABEL=rootfs
findfs: unable to resolve 'LABEL=rootfs'
[ ok ] Activating lvm and md swap...done.
[....] Checking file systems...fsck from util-linux 2.29.2
fsck.ext4: Unable to resolve 'LABEL=rootfs'
fsck exited with status code 8
failed (code 8).
[....] File system check failed. A log is being saved in /var/log/fsck/checkfs i[FAILt location is writable. Please repair the file system manually. ... failed!
[....] A maintenance shell will now be started. CONTROL-D will terminate this sh[warnnd resume system boot. ... (warning).
Give root password for maintenance

What can I do to resolve this problem?

Regards.
shv



Edited 3 time(s). Last edit at 09/19/2017 01:50PM by shv.

shv,

> findfs: unable to resolve 'LABEL=rootfs'

This is a Debian stretch change. You'll need to change fstab.

LABEL=rootfs    /               ext4    noatime,errors=remount-ro 0 1

And make sure to check if your label is rootfs

e2label /dev/sda1

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



Edited 1 time(s). Last edit at 09/19/2017 02:58PM by bodhi.

bodhi,

thanks for your hint. The problem seams to be caused by a different rootfs name. I am using "rootfs-ide". Therefore I must adapt fstab to this.

- shv

shv,

Right! If you don't care about fsck the rootfs at each boot, you can even remove that line from fstab. But if it is stated in fstab, then the label needs to be the same name. The behavior has changed slightly how Debian handle the rootfs in initscript.

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

bodhi,

your rootfs works well. I upgraded from Squeeze to Stretch. Just samba has much worse throughput compared to Squeeze. I am using some performace options which are shown within the following link expect xfs - I am using ext4:

http://falkhusemann.de/blog/2010/09/maximaldurchsatz-der-modifizierten-seagate-dockstar-optimieren

But these options don't improve the performance of samba server on Stretch.

Samba3 throughput on Squeeze: 35-40 MByte/s
Samba4 throughput on Stretch: 10-11 MByte/s

Do you have any ideas how this could be improved?

- shv



Edited 1 time(s). Last edit at 09/24/2017 05:32AM by shv.

shv,

When you upgraded to stretch,

1. Did you save your smb.conf?
2. Did you take the new smb.conf from Samba 4, and retrofit your shares definition to the new smb.conf?

Usually, in a substantial upgrade like this, it is best to save your local settings, and take the new smb.conf and apply all your saved settings to it.

You can also take a look at my smb.conf posted here:
https://forum.doozan.com/read.php?8,23223,23293#msg-23293

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

Kernel linux-4.4.89-oxnas-tld-1 package was uploaded. Please 1st post for download link.

Quote

New/Update features:

- Changed Wifi modules to be loadable (no longer kernel builtin). As the result, kernel image size has been reduced back to a little under 4M. These modules are loaded automatically in the initrd so there should be no change in the way the stock wireless PCI card is used (no need to do any setup). However, please report any changes in Wifi behavior you might encounter (I don't expect any problem, though). The folowing modules are now loadable and loaded automatically during kernel booting: ATH9K, RT2X00, RT2800PCI,CFG80211, MAC80211.
- Add RFKILL module
- Incorporated kernel 4.4.89 mainline security bugs fixes.

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

I have the Pogoplug-P21 ("version 3") without a wifi antenna inside. I used the steps provided in part "4." concatenating with "pogoplug-classic" then used mkimage to install in rootfs/boot on a fresh 4gig stick using ext3 format. First I used sudo to perform the 'mkimage". Once inserted in the pogoplug and rebooted the stick was read (multiple led flashes) by the P21 firmware but it did not take over control of the unit. Second I shifted to "su -" went into root mode and repeated the "4." steps with a refreshed stick (new partition and ext3 format). This time it was not read by the pogoplug. The stick's led blinked once as the usb port was tested with the P21's original firmware.

I hope this description is sufficient to identify an obvious error on my part.

All suggestions are both needed and appreciated.

Thanks for your effort and posts re linux on the Pogoplug-P21
I sure hope to benefit from all your experience.

Mike Wrote:
-------------------------------------------------------
> I have the Pogoplug-P21 ("version 3") without a
> wifi antenna inside. I used the steps provided in
> part "4." concatenating with "pogoplug-classic"
> then used mkimage to install in rootfs/boot on a
> fresh 4gig stick using ext3 format. First I used
> sudo to perform the 'mkimage". Once inserted in
> the pogoplug and rebooted the stick was read
> (multiple led flashes) by the P21 firmware but it
> did not take over control of the unit. Second I
> shifted to "su -" went into root mode and repeated
> the "4." steps with a refreshed stick (new
> partition and ext3 format). This time it was not
> read by the pogoplug. The stick's led blinked once
> as the usb port was tested with the P21's original
> firmware.
>
> I hope this description is sufficient to identify
> an obvious error on my part.
>
> All suggestions are both needed and appreciated.
>
> Thanks for your effort and posts re linux on the
> Pogoplug-P21
> I sure hope to benefit from all your experience.

You really should copy and paste what is typed and output on the screen and post here to really see what happened. There may have been a step or an error you missed and it greatly helps to help you.
Use the little box "Formatted Code" above to paste here to make for easier reading.