Linux Kernel 6.7.5 Kirkwood package and Debian rootfs

pbg4,

> p.s. when I send you the patch for the
> s2-liplianin dvb-usb-dw2102 per pm, would it be
> possible to include that
> in further updates?? of course with maintenance on
> my side, perhaps it would make some users out
> there happy,..

Definitely, please do.

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

Hi bodhi, thank you very much for this!

I'm building my own kernel for the sheevaplug using your patch. I saw that in arch/arm/mach-kirkwood/Makefile you removed this line: obj-$(CONFIG_PM) += pm.o
I re-added it to my makefile because i need runtime power management (for usb autosuspend primarily) and installed the resulting kernel in my sheevaplug.
So far so good. I can't see any problem, so i was asking myself why you removed that. Issues with some other kirkwood platform, maybe? Just curious :)

Iome,

Thanks for your report. It was indeed an oversight of mine :) I believe it's because this Kirkwood pm module was introduced only in 3.13.x, I've missed it in the patch.
Will make sure that it will be added back in the next version.

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

pbg4,

> ..., definitely, but after the dist-upgrade I have
> to get a couple of wheezeboxes to sound right,..
> :)

Cool :)) I like my iConnect, too bad they're not availble anymore at $55-75 range which was when I bought! IMO, It's right at the top of the Kirkwood plugs for me (256MB RAM and large 512MB NAND, Wifi).

You might want to try my new iConnect uBoot build, just uploaded.

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

Hi bodhi,

exactly, the iConnect definitely has its merits with respect to NAND size and compact design
and in the combination of features,.. as I have my iConnect attached to the GB net the mini pcie
card slot is empty at the moment, because I have detached the Ralink wlan card to save some energy,..

though it's only a half length card I have both a mini pcie sata card and an usb 3.0 full size card which
I am going to test with your new uBoot build , do you think the mini pcie sata card in AHCI mode would be able to boot
some device ??, will these cards get initialised over the pci bus in uBoot or only later with full OS booted??

best wishes pbg4



Edited 2 time(s). Last edit at 02/23/2014 04:37PM by pbg4.

Looks like we have the same idea :) I got this recently but have not got around to try it yet:
http://store.123greetings.com/catalog/product/view/id/85162

Let us know if you to try the PCIe SATA with new u-Boot, how it goes. I hope to get u-Boot recognizing and booting with this PCIe card. The chipset ASM1061 seems to be very popular.

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

pbg4,

BTW, you could try UART booting on another Kirkwood box first for sanity check . Even though it will not boot correctly, it will boot into Debian (no eth0, though).

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

pbg4, looks like it's not going to work with PCIe HDD in this version.

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

Hi bodhi,

my card also has the ASM1061 controller and the other a usb 3.0 chip from NEC,
of course will start with UART booting and report back here,..

best wishes pbg4

Hi, Bodhi,
I made a new SD card containing your rootfs. Everything works fine for pogo/mobile. The SD card boot setting is done in Uboot, independent of rootfs. I found this in my previous posting and just forgot about that.
Have you every tried using Dockstar and similar with wifi? I always have trouble to do that lately. If you did, can you provide, or point me to, the procedure that was tested working? Thanks.

twinclouds,

Not exactly to your question, but this thread from davygravy contains a wealth of information re wifi:
http://forum.doozan.com/read.php?2,6300

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

Bodhi:
Thanks. The post you referenced is for a specific wifi adapter that I don't have and it is for make the Dockstar to be a AP, different from what I need.
I am able to install what needed for my USB Wifi adapters to work and it looked working. However, I cannot access the device through wifi without the ethernet attached. This defeated the whole purpose. For RastPi, there's no problem and just works. Not sure why. I had made it worked before but never for Squeeze and Wheezy. I hope there are people on this board had successful hand-on experience for Wheezy.

twinclouds,

Perhaps you should check routing table. It's been a while, so I don't remember all the details. This is my routing table on a Pogo Pro running Debian wheezy roofs.

# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.0.0     *               255.255.255.0   U     0      0        0 eth0
192.168.0.0     *               255.255.255.0   U     0      0        0 ra0
default         192.168.0.1     0.0.0.0         UG    0      0        0 eth0

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

Bodhi:
Eventually I made it work following what described here for Rasp Pi. I don't know why it didn't work before but at least it works now. Thanks for the help from you.
Edit: Well it stop working once I remove the ethernet cable



Edited 2 time(s). Last edit at 02/27/2014 11:06PM by twinclouds.

Hi bodhi,

please have a look into your pm's, I just sent you the patch for the dvb-usb-dw2102 driver
including support for the tt-s2-4600 and some other dvb-usb S2 devices not in
mainline kernel land until now,

perhaps the patch is suited for inclusion into forthcoming kernel versions of your thread here,...

there has been some discussion in early november last year between antti and manu in linux-media
wether the older ds3103 and ts2022 frontend and decoder drivers from s2-liplianin-v39 were better
than the frontend and decoder drivers which came in kernel 3.14 with the git pull from antti's repository,
(because ds3103 and ts2022 are needed to support new devices as the tt-s2-4600 and others
in dvb-usb-dw2102)

but as I think that manu is right with his view, I have based my patch on the s2-liplianin-v39 repo,
(they are also named differently in kernel 3.14 with m88.. placed in front and aiming to serve a different
device, the pinnacle pctv dvb-s2 461e, so hopefully there won't be a conflicting situation)

if you find some problems concerning the patch please let me know via pm and I am going to try to find a solution,..

of course CONFIG_DVB_DS3103=m and CONFIG_DVB_TS2022=m
have to be enabled in .config,

best wishes pbg4

p.s this patch has been tested with your 3.13.1 kernel on my iConnect and until now has an uptime of 14 days without errors,...



Edited 1 time(s). Last edit at 03/03/2014 03:48PM by pbg4.

Pbg4,

Great! I'll be glad to include your patch in the next build.

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

Is it possible to run nfs-server ?

I am not "newbie" with nfs, I very frequently use NFS but this problems which I found with this kernel are very strange...

summary: Anyway I configure exports I everytime have got error:

> exportfs: /folder does not support NFS export

What is wrong ?

Even so simple config:
/b *(ro,sync,no_subtree_check)
...doesn't work.

I have ext3 filesystem everywhere, NSA325V2 hardware (Marwell),
root@debian:/boot# uname -a
Linux debian 3.13.1-kirkwood-tld-2 #1 PREEMPT Tue Feb 4 03:19:07 PST 2014 armv5tel GNU/Linux

root@debian:/boot# mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=63258,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=51268k,mode=755)
/dev/disk/by-label/rootfs on / type ext3 (rw,noatime,errors=remount-ro,user_xattr,acl,barrier=1,data=ordered)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=102520k)
tmpfs on /tmp type tmpfs (rw,relatime)
rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
/dev/sdb1 on /boot type ext2 (rw,relatime,errors=continue,user_xattr,acl)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)

I found that problems could be ext4 (imho rather not possible but ...) I migrated all my disks to ext3... the same problems.

Read "tons of documentation" ... no result... I give up, please help me...

marcint43,

> Is it possible to run nfs-server ?

It does work. Both as exported shares and rootfs. You could post more details of what you did.

Other thought: Did you make sure that it is exporting nfsv3 ?

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



Edited 1 time(s). Last edit at 03/05/2014 08:06PM by bodhi.

I revert back all my changes to clear debian wheezy (from first post) install. Nothing changed.

So, basicaly, I typed:
# mkdir /b
and next in the order in /etc/exports file I put line:
/b *(ro,sync,no_subtree_check)

Finaly run command: # exportfs -r (or -a) command.

None is exported, and exportfs command returns message above "exportfs: /b does not support NFS export"

/etc/init.d/nfs-kernel-server restart (...the same error because there is exportfs used)
/etc/init.d/nfs-common restart

It doesn't matter if I exporting /b from rootfs, or mounted devices

hardware: Zyxel NSA 325V2, hardware (Uboot) prepared exactly in way described by Buttzy10169 in post:
http://forum.doozan.com/read.php?2,14351
System booted from pendrive /dev/sda1 = boot partition (not mounted in OS), /de/sda2 - ext3 mounted as rootfs

I dont' have idea what is wrong ... I suspect booting from pendrive ... but why ? doesn't seems to has sense...

For next test, I downgraded nfs-kernel-server and nfs-common and all depedned libs to squeeze version - NOTHING CHANGED.

libevent-1.4-2_1.4.13-stable-1_armel.deb
libnfsidmap2_0.25-5_armel.deb
librpcsecgss3_0.19-6_armel.deb
nfs-common_1.2.2-4squeeze2_armel.deb
nfs-kernel-server_1.2.2-4squeeze2_armel.deb


so this seems to be permanent problem with zyxel and way it uses filesystems ?

nobody is able to help me ?

marcint43 Wrote:
-------------------------------------------------------
> For next test, I downgraded nfs-kernel-server and
> nfs-common and all depedned libs to squeeze
> version - NOTHING CHANGED.
>
> libevent-1.4-2_1.4.13-stable-1_armel.deb
> libnfsidmap2_0.25-5_armel.deb
> librpcsecgss3_0.19-6_armel.deb
> nfs-common_1.2.2-4squeeze2_armel.deb
> nfs-kernel-server_1.2.2-4squeeze2_armel.deb
>
>
> so this seems to be permanent problem with zyxel
> and way it uses filesystems ?
>
> nobody is able to help me ?

Try different syntax, and see if you can share different folder, on different host mask. For example:

/usr/src   192.168.0.0/255.255.255.0(rw,sync,no_root_squash,no_subtree_check,insecure)

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

this was first thing I was try to do.

I tried combinations:
/boot - which is ext2 (ext3?) filesystem (mounted directly from /dev/sdb2)
/ - ext4
/ - ext3 (I reinstalled OS (tar/untar) to ext3 filesystem as I found that there could be a problem (2012year))
/mnt/lvmdisk/folder - ext4
/mnt/lvmdisk/folder - ext3 (i recreated all my storage disks from ext4 to ext3 ... 24hours hdd copying ;/ )

any combination of option, even when I defined fsid=0 or fsid=<uuid genrated> ...

when there are any errors in /etc/exports file - exportfs command return errors, so, exportfs command works good, problem seems to be in kernel/nfsd layer

I downgraded NFSd to the "newest" nfsd in squeeze version (package listed before),

Started nfs v3 (switched off all nfs4 daemons and start up nfs3 needed)

never,ever...

PS.
I was not trying option "insecure", but the other hand I dont' think that this should be source problem

Today I will try to use old kernel 2.6 instead od 3.13 ... but I am afraid that this is not that ...

That is strange. I know you're running 3.13.1-kirkwood-tld-2. But with what rootfs? have you done

apt-get update
apt-get upgrade

and what is in your /etc/apt/sources.list ?

I'm running the same kernel, and sharing several nfs shares. Some for browsing and several for rootfs (as in nfs cluster).

So I think it is something else, don't bother trying squeeze.

Other thoughts: what is the output of

ps -deaf

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



Edited 2 time(s). Last edit at 03/07/2014 03:28AM by bodhi.

NAS boot proces: uboot -> bootable device USB :/dev/sdb1 (files from /boot directory) -> (initrd) mount "rootfs" labeled disk which is on /dev/sdb2 ... and there is my debian.
HOWTO do it:http://forum.doozan.com/read.php?2,14351

physicaly:
my rootfs this is /dev/sdb2 (pendrive)
sda - hdd1
sdc - hdd2

under "df" I see sth like that:
/dev/disk/by-label/rootfs .... /

under "mount"
rootfs on / type ext3 (rw,.....)


> apt-get update
> apt-get upgrade

of course.
Moreover I tested nfs from "debian testing" repo - no result
revert back to squeeze version (uninstal purge, manual install of deb packets,) - no result


> I'm running the same kernel, and sharing several nfs shares.
> Some for browsing and several for rootfs (as in nfs cluster).

Wow! so this is possible :) Thats very good news :)
So this is possible...

> ps -deaf

now I have no access to this hardware, I will put that today evening ( in about 8 hours...)

are you using nfs v3 or 4 ?

marcint43 Wrote:
-------------------------------------------------------
> are you using nfs v3 or 4 ?

I'm using nfs v3 (because compatibility with uBoot booting rootfs). But I recall nfs v4 worked for me before (same server version). And looks like you've tried nfs v3 share.

I'd suggested you move this NFS topic to a new thread. Much better to troubleshoot your problem in a more visible topic so others can post ideas.

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

root@debian:~# egrep -v '^#|^$' /etc/default/nfs-common 
NEED_STATD=no
STATDOPTS=
NEED_IDMAPD=no
NEED_GSSD=no

root@debian:~# egrep -v '^#|^$' /etc/default/nfs-kernel-server 
RPCNFSDCOUNT=8
RPCNFSDPRIORITY=0
RPCMOUNTDOPTS="--manage-gids --no-nfs-version 4"
NEED_SVCGSSD=no
RPCSVCGSSDOPTS=

root@debian:~# egrep -v '^#|^$' /etc/exports 
/usr/src   192.168.0.0/255.255.255.0(rw,sync,no_root_squash,no_subtree_check,insecure)


root@debian:~# exportfs -a
exportfs: /usr/src does not support NFS export
root@debian:~# exportfs -r
exportfs: /usr/src does not support NFS export


...I disabled NFS4 ... but .... this is first strange thing:

root@debian:~# rpcinfo  -u localhost nfs
program 100003 version 2 ready and waiting
program 100003 version 3 ready and waiting
program 100003 version 4 ready and waiting

UID        PID  PPID  C STIME TTY          TIME CMD
root         1     0  0 00:59 ?        00:00:01 init [2]  
root         2     0  0 00:59 ?        00:00:00 [kthreadd]
root         3     2  0 00:59 ?        00:00:00 [ksoftirqd/0]
root         5     2  0 00:59 ?        00:00:00 [kworker/0:0H]
root         6     2  0 00:59 ?        00:00:00 [kworker/u2:0]
root         7     2  0 00:59 ?        00:00:00 [rcu_preempt]
root         8     2  0 00:59 ?        00:00:00 [rcu_sched]
root         9     2  0 00:59 ?        00:00:00 [rcu_bh]
root        10     2  0 00:59 ?        00:00:00 [watchdog/0]
root        11     2  0 00:59 ?        00:00:00 [khelper]
root        12     2  0 00:59 ?        00:00:00 [kdevtmpfs]
root        13     2  0 00:59 ?        00:00:00 [netns]
root        14     2  0 00:59 ?        00:00:00 [writeback]
root        15     2  0 00:59 ?        00:00:00 [kintegrityd]
root        16     2  0 00:59 ?        00:00:00 [bioset]
root        17     2  0 00:59 ?        00:00:00 [kblockd]
root        18     2  0 00:59 ?        00:00:00 [khubd]
root        19     2  0 00:59 ?        00:00:00 [kworker/0:1]
root        20     2  0 00:59 ?        00:00:00 [rpciod]
root        21     2  0 00:59 ?        00:00:00 [khungtaskd]
root        22     2  0 00:59 ?        00:00:00 [kswapd0]
root        23     2  0 00:59 ?        00:00:00 [ksmd]
root        24     2  0 00:59 ?        00:00:00 [fsnotify_mark]
root        25     2  0 00:59 ?        00:00:00 [nfsiod]
root        26     2  0 00:59 ?        00:00:00 [crypto]
root        32     2  0 01:00 ?        00:00:00 [kworker/u2:1]
root        37     2  0 01:00 ?        00:00:00 [deferwq]
root        85     2  0 01:00 ?        00:00:00 [ata_sff]
root        86     2  0 01:00 ?        00:00:00 [scsi_eh_0]
root        87     2  0 01:00 ?        00:00:00 [usb-storage]
root        88     2  0 01:00 ?        00:00:00 [scsi_eh_1]
root        89     2  0 01:00 ?        00:00:00 [scsi_eh_2]
root       108     2  0 01:00 ?        00:00:00 [kworker/0:2]
root       116     2  0 01:00 ?        00:00:00 [kworker/0:1H]
root       168     2  0 01:00 ?        00:00:00 [kjournald]
root       305     1  0 01:00 ?        00:00:00 udevd --daemon
root       379     2  0 01:00 ?        00:00:00 [mv_crypto]
root       470   305  0 01:00 ?        00:00:00 udevd --daemon
root       471   305  0 01:00 ?        00:00:00 udevd --daemon
root       616     2  0 01:00 ?        00:00:00 [md]
root       632     2  0 01:00 ?        00:00:00 [bioset]
root       633     2  0 01:00 ?        00:00:00 [md13_raid1]
root       642     2  0 01:00 ?        00:00:00 [bioset]
root       643     2  0 01:00 ?        00:00:00 [md12_raid1]
root       653     2  0 01:00 ?        00:00:00 [bioset]
root       654     2  0 01:00 ?        00:00:00 [md11_raid1]
root       667     2  0 01:00 ?        00:00:00 [bioset]
root       668     2  0 01:00 ?        00:00:00 [md10_raid1]
root       677     2  0 01:00 ?        00:00:00 [bioset]
root       678     2  0 01:00 ?        00:00:00 [md9_raid1]
root       687     2  0 01:00 ?        00:00:00 [bioset]
root       688     2  0 01:00 ?        00:00:00 [md8_raid1]
root       700     2  0 01:00 ?        00:00:00 [bioset]
root       701     2  0 01:00 ?        00:00:00 [md7_raid1]
root       711     2  0 01:00 ?        00:00:00 [bioset]
root       712     2  0 01:00 ?        00:00:00 [md6_raid1]
root       722     2  0 01:00 ?        00:00:00 [bioset]
root       723     2  0 01:00 ?        00:00:00 [md5_raid1]
root      2205     1  0 01:00 ?        00:00:00 /usr/sbin/acpid
root      2224     1  0 01:00 ?        00:00:00 /sbin/klogd
root      2248     1  0 01:00 ?        00:00:00 /sbin/syslogd -C128
root      2283     1  0 01:00 ?        00:00:00 /sbin/mdadm --monitor --pid-file /run/mdadm/monitor.pid --daemonise --scan --syslog
102       2310     1  0 01:00 ?        00:00:00 /usr/bin/dbus-daemon --system
ntp       2384     1  0 01:00 ?        00:00:00 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 104:106
avahi     2388     1  0 01:00 ?        00:00:00 avahi-daemon: running [debian.local]
avahi     2389  2388  0 01:00 ?        00:00:00 avahi-daemon: chroot helper
root      2491     1  0 01:00 ?        00:00:00 /usr/sbin/sshd
root      2539     1  0 01:00 ttyS0    00:00:00 /sbin/getty -L ttyS0 115200 linux
root      2540  2491  0 01:00 ?        00:00:01 sshd: root@pts/0 
root      2542  2540  0 01:00 pts/0    00:00:00 -bash
root      3447     1  0 01:15 ?        00:00:00 dhclient eth0
statd     4197     1  0 01:18 ?        00:00:00 /sbin/rpc.statd
root      4209     1  0 01:18 ?        00:00:00 /usr/sbin/rpc.idmapd
root      4947     1  0 01:29 ?        00:00:00 /sbin/rpcbind -w
root      5054     2  0 01:32 ?        00:00:00 [kworker/0:0]
root      5068     2  0 01:32 ?        00:00:00 [nfsd4]
root      5069     2  0 01:32 ?        00:00:00 [nfsd4_callbacks]
root      5070     2  0 01:32 ?        00:00:00 [lockd]
root      5071     2  0 01:32 ?        00:00:00 [nfsd]
root      5072     2  0 01:32 ?        00:00:00 [nfsd]
root      5073     2  0 01:32 ?        00:00:00 [nfsd]
root      5074     2  0 01:32 ?        00:00:00 [nfsd]
root      5075     2  0 01:32 ?        00:00:00 [nfsd]
root      5076     2  0 01:32 ?        00:00:00 [nfsd]
root      5077     2  0 01:32 ?        00:00:00 [nfsd]
root      5078     2  0 01:32 ?        00:00:00 [nfsd]
root      5083     1  0 01:32 ?        00:00:00 /usr/sbin/rpc.mountd --manage-gids --no-nfs-version 4
root      5104  2542  0 01:33 pts/0    00:00:00 ps -deaf


strange processes:
root      5068     2  0 01:32 ?        00:00:00 [nfsd4]
root      5069     2  0 01:32 ?        00:00:00 [nfsd4_callbacks]


root@debian:~# mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=63258,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=51268k,mode=755)
/dev/disk/by-label/rootfs on / type ext3 (rw,noatime,errors=remount-ro,user_xattr,acl,barrier=1,data=ordered)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /run/shm type tmpfs (rw,nosuid,nodev,noexec,relatime,size=102520k)
tmpfs on /tmp type tmpfs (rw,relatime)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)

root@debian:~# df -h
Filesystem                 Size  Used Avail Use% Mounted on
rootfs                     442M  377M   43M  90% /
udev                        10M     0   10M   0% /dev
tmpfs                       51M  260K   50M   1% /run
/dev/disk/by-label/rootfs  442M  377M   43M  90% /
tmpfs                      5.0M     0  5.0M   0% /run/lock
tmpfs                      101M     0  101M   0% /run/shm
tmpfs                      251M     0  251M   0% /tmp

root@debian:~# rpcinfo  
   program version netid     address                service    owner
    100000    4    tcp       0.0.0.0.0.111          portmapper superuser
    100000    3    tcp       0.0.0.0.0.111          portmapper superuser
    100000    2    tcp       0.0.0.0.0.111          portmapper superuser
    100000    4    udp       0.0.0.0.0.111          portmapper superuser
    100000    3    udp       0.0.0.0.0.111          portmapper superuser
    100000    2    udp       0.0.0.0.0.111          portmapper superuser
    100000    4    local     /var/run/rpcbind.sock  portmapper superuser
    100000    3    local     /var/run/rpcbind.sock  portmapper superuser
    100024    1    udp       0.0.0.0.143.148        status     105
    100024    1    tcp       0.0.0.0.136.135        status     105
    100024    1    udp6      ::.137.241             status     105
    100024    1    tcp6      ::.216.13              status     105
    100003    2    tcp       0.0.0.0.8.1            nfs        superuser
    100003    3    tcp       0.0.0.0.8.1            nfs        superuser
    100003    4    tcp       0.0.0.0.8.1            nfs        superuser
    100227    2    tcp       0.0.0.0.8.1            -          superuser
    100227    3    tcp       0.0.0.0.8.1            -          superuser
    100003    2    udp       0.0.0.0.8.1            nfs        superuser
    100003    3    udp       0.0.0.0.8.1            nfs        superuser
    100003    4    udp       0.0.0.0.8.1            nfs        superuser
    100227    2    udp       0.0.0.0.8.1            -          superuser
    100227    3    udp       0.0.0.0.8.1            -          superuser
    100021    1    udp       0.0.0.0.164.201        nlockmgr   superuser
    100021    3    udp       0.0.0.0.164.201        nlockmgr   superuser
    100021    4    udp       0.0.0.0.164.201        nlockmgr   superuser
    100021    1    tcp       0.0.0.0.221.124        nlockmgr   superuser
    100021    3    tcp       0.0.0.0.221.124        nlockmgr   superuser
    100021    4    tcp       0.0.0.0.221.124        nlockmgr   superuser
    100021    1    udp6      ::.210.94              nlockmgr   superuser
    100021    3    udp6      ::.210.94              nlockmgr   superuser
    100021    4    udp6      ::.210.94              nlockmgr   superuser
    100021    1    tcp6      ::.234.113             nlockmgr   superuser
    100021    3    tcp6      ::.234.113             nlockmgr   superuser
    100021    4    tcp6      ::.234.113             nlockmgr   superuser
    100005    1    udp       0.0.0.0.190.126        mountd     superuser
    100005    1    tcp       0.0.0.0.140.136        mountd     superuser
    100005    2    udp       0.0.0.0.193.15         mountd     superuser
    100005    2    tcp       0.0.0.0.162.137        mountd     superuser
    100005    3    udp       0.0.0.0.212.179        mountd     superuser
    100005    3    tcp       0.0.0.0.207.219        mountd     superuser

If you do not find what's wrong I create new thread on forum ...

@BigRon,
I took a look. And unfortunately I'm not familiar with I2S so I can't figure out exactly what config switches should be included. Perhaps you can find out the information, and I'll be glad to include them later.
http://forum.doozan.com/read.php?2,12096,15042#msg-15042


@lome,
Regarding the CONFIG_PM. I don't think I will include this, because it will probably mess up some NAS (which is most users want to run these plugs as).
http://forum.doozan.com/read.php?2,12096,15202#msg-15202

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



Edited 1 time(s). Last edit at 03/11/2014 12:02AM by bodhi.

bodhi Wrote:
-------------------------------------------------------
> @Dave & Ron,
> I'll include the requested config options in the
> next release. You can test it, then!
>
> @Dave,
> I saw some unchecked config switches under HID.
> Perhaps include them will cover your UPS. But out
> of curiousity, if you still have the older kernel
> files, could you get the output of this grep and
> post it here? (where config-3.xx.x-kirkwood-xx is
> that kernel config file):
>

> cat config-3.xx.x-kirkwood-xx | grep -i hid
>

I am running 3.13-tld2 release (fresh install, not an "upgrade" install) on a Pink POGO E02 device with a CyberPower UPS attached.

root@pogo2:~# uname -a
Linux pogo2 3.13.1-kirkwood-tld-2 #1 PREEMPT Tue Feb 4 03:19:07 PST 2014 armv5tel GNU/Linux

I boot this POGO from an attached USB key (the A-DATA device shown below).

root@pogo2:~# lsusb
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS
Bus 001 Device 004: ID 125f:cb10 A-DATA Technology Co., Ltd.

I am using the "nut-client" and "nut-server" packages from the Debian "armel" repository; these packages might "behave differently" compared to the "apcupsd" package used by Dave. The only issue I encountered was with "ownership" of the USB port; an occasional problem encountered during the installation of the "nut" package.

This command fixed the "ownership" issue: chown -R root:nut /dev/bus/usb/001/003

For reference, this physical USB port (001/003) is located immediately above the AC power connector.

I use the "nut-server" package so that 3 separate Windows 7 physical machines can read the UPS status from this POGO using the Windows version of "nut"; all 3 are powered by this UPS. The Windows version (currently derived from NUT 2.6.5) of "nut" happens to work with some effort, but I have yet to run it through any UPS-related tests ("ups shutdown", "ups low battery", etc.). I read the UPS status in a web interface via another Linux machine across the network so POGO doesn't have to run a web server app or require the "nut-cgi" package (and the packages that go with "nut-cgi").

This POGO install also uses little memory as shown by "free -h":

root@pogo2:~# free -h
total used free shared buffers cached
Mem: 246M 53M 192M 0B 5.5M 23M
-/+ buffers/cache: 24M 222M
Swap: 0B 0B 0B

I have seen the "used" value drop to as low as 26M.

POGO itself uses very little power, about 10W or less based on my own measurements. When POGO is the only device powered up on this UPS, the UPS reports "0" in it's "load" output. Here's a little detail about this UPS from a "verbose lsusb" output:

idVendor 0x0764 Cyber Power System, Inc.
idProduct 0x0501 CP1500 AVR UPS
bcdDevice 0.01
iManufacturer 3 CPS
iProduct 1 CP 1500D

In the "nut" package, this UPS uses the "usbhid-sys" driver provided by "nut", and I suspect that communicates with the UPS via the "usbhid" and "hid" kernel modules.

root@pogo2:~# lsmod
Module Size Used by
orion_wdt 2993 0
hmac 2441 0
sha1_generic 1760 0
sha1_arm 3397 0
mv_cesa 10625 0
ext2 58385 1
mbcache 5678 1 ext2
sg 20647 0
sd_mod 34456 2
crc_t10dif 1032 1 sd_mod
crct10dif_common 1126 1 crc_t10dif
usb_storage 36835 1
usbhid 34005 0
hid 75867 1 usbhid
scsi_mod 157867 3 sg,usb_storage,sd_mod

notmine,

Thanks for your report about the CyberPower UPS! good to know it works.

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