are you using nfs v3 or 4 ?
↧
Re: Linux Kernel 3.6.11 Kirkwood package (Non Flatten Device Tree)
↧
Re: Linux Kernel 3.6.11 Kirkwood package (Non Flatten Device Tree)
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.
-------------------------------------------------------
> 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.
↧
↧
Re: Linux Kernel 3.6.11 Kirkwood package (Non Flatten Device Tree)
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 ...
↧
Re: Linux Kernel 3.13.1 Kirkwood package and rootfs (Non Flattened Device Tree)
@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
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
↧
Re: Linux Kernel 3.13.1 Kirkwood package and rootfs (Non Flattened Device Tree)
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):
>
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
-------------------------------------------------------
> @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
↧
↧
Re: Linux Kernel 3.13.1 Kirkwood package and rootfs (Non Flattened Device Tree)
notmine,
Thanks for your report about the CyberPower UPS! good to know it works.
Thanks for your report about the CyberPower UPS! good to know it works.
↧
Re: Linux Kernel 3.13.1 Kirkwood package and rootfs (Non Flattened Device Tree)
Heads up!
I'll release kernel 3.14 build hopefully in about a week.
http://www.phoronix.com/scan.php?page=news_item&px=MTYzNDg
I'll release kernel 3.14 build hopefully in about a week.
http://www.phoronix.com/scan.php?page=news_item&px=MTYzNDg
↧
Re: Linux Kernel 3.13.1 Kirkwood package and rootfs (Non Flattened Device Tree)
Can the dvb_demux.h header file be included in the header file? I need it to compile the dvbhdhomerun program...
http://sourceforge.net/apps/trac/dvbhdhomerun/wiki/Building
http://sourceforge.net/apps/trac/dvbhdhomerun/wiki/Building
↧
Re: Linux Kernel 3.13.1 Kirkwood package and rootfs (Non Flattened Device Tree)
Termo Wrote:
-------------------------------------------------------
> Can the dvb_demux.h header file be included in the
> header file? I need it to compile the dvbhdhomerun
> program...
>
> [url=http://sourceforge.net/apps/trac/dvbhdhomerun
> /wiki/Building]http://sourceforge.net/apps/trac/dv
> bhdhomerun/wiki/Building[/url]
It should be in there already.
-------------------------------------------------------
> Can the dvb_demux.h header file be included in the
> header file? I need it to compile the dvbhdhomerun
> program...
>
> [url=http://sourceforge.net/apps/trac/dvbhdhomerun
> /wiki/Building]http://sourceforge.net/apps/trac/dv
> bhdhomerun/wiki/Building[/url]
It should be in there already.
↧
↧
Re: Linux Kernel 3.13.1 Kirkwood package and rootfs (Non Flattened Device Tree)
Hi Bodhi.
I can't find it.
"find /usr/src/linux-headers-3.13.1-kirkwood-tld-2/ -name dvb_demux.h" return nothing...
anyhow I found a very nice updated fork of dvbhdhomerun that takes care of this change in the newer debian kernels, by pulling down the headers from https://github.com/torvalds/linux/
For others that need to compile the dvbhdhomerun module on newer kernels please use this fork:
https://github.com/h0tw1r3/dvbhdhomerun
The only problem I had now was that the <include mach/irqs.h> in /usr/src/linux-headers-3.13.1-kirkwood-tld-2/arch/arm/include/asm/irq.h points to a file that is not there. I found an irqs.h file for kirkwood and put it in /usr/src/linux-headers-3.13.1-kirkwood-tld-2/arch/arm/include/asm/mach/ and everything compiled...
Best regards
Termo
I can't find it.
"find /usr/src/linux-headers-3.13.1-kirkwood-tld-2/ -name dvb_demux.h" return nothing...
anyhow I found a very nice updated fork of dvbhdhomerun that takes care of this change in the newer debian kernels, by pulling down the headers from https://github.com/torvalds/linux/
For others that need to compile the dvbhdhomerun module on newer kernels please use this fork:
https://github.com/h0tw1r3/dvbhdhomerun
The only problem I had now was that the <include mach/irqs.h> in /usr/src/linux-headers-3.13.1-kirkwood-tld-2/arch/arm/include/asm/irq.h points to a file that is not there. I found an irqs.h file for kirkwood and put it in /usr/src/linux-headers-3.13.1-kirkwood-tld-2/arch/arm/include/asm/mach/ and everything compiled...
Best regards
Termo
↧
Re: Linux Kernel 3.13.1 Kirkwood package and rootfs (Non Flattened Device Tree)
Termo,
Could you post the lsmod output when you got your modules running? I might have missed some config options (I'm not running DVB on my plugs).
Thanks!
Could you post the lsmod output when you got your modules running? I might have missed some config options (I'm not running DVB on my plugs).
Thanks!
↧
Re: Linux Kernel 3.13.1 Kirkwood package and rootfs (Non Flattened Device Tree)
My lsmod output:
Module Size Used by dvb_hdhomerun_fe 5691 2 dvb_hdhomerun 11495 4 dvb_hdhomerun_core 1993 2 dvb_hdhomerun_fe,dvb_hdhomerun dvb_core 75539 1 dvb_hdhomerun ext4 447033 1 jbd2 86895 1 ext4 ipv6 288370 48 hmac 2441 0 orion_wdt 2993 0 sha1_generic 1760 0 sha1_arm 3397 0 mv_cesa 10625 0 ext2 58385 1 mbcache 5678 2 ext2,ext4 sg 20647 0 sd_mod 34456 4 crc_t10dif 1032 1 sd_mod crct10dif_common 1126 1 crc_t10dif usb_storage 36835 3 scsi_mod 157867 3 sg,usb_storage,sd_mod
↧
Re: Linux Kernel 3.13.1 Kirkwood package and rootfs (Non Flattened Device Tree)
Thanks Termo.
↧
↧
Re: Linux Kernel 3.14.0 Kirkwood package and rootfs (Non Flattened Device Tree)
Kernel 3.14.0-kirkwood-tld-1 package was uploaded. Please see 1st post for download link.
↧
cannot boot ... probably incompatible uboot and rootfs
My Pink Pogogplug hangs after the booting message.
For testing I installed
Debian-3.13.1-kirkwood-tld-2-rootfs-bodhi.tar.bz2 .
Before I was using Debian Wheezy with 3.2 kernel. Now I cannot even boot my old system.
Could anyone help please?
U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
Pogoplug E02
SoC: Kirkwood 88F6281_A0
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
88E1116 Initialized on egiga0
No link on egiga0
ping failed; host 192.168.2.2 is not alive
Hit any key to stop autoboot: 0
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/uImage" from usb device 0:1 (usbda1)
2399792 bytes read
Loading file "/uInitrd" from usb device 0:1 (usbda1)
6568066 bytes read
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-3.13.1-kirkwood-tld-2
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2399728 Bytes = 2.3 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-3.13.1-kirkwood-tld-2
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 6568002 Bytes = 6.3 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Using machid 0xdd6 from environment
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
#####
My environment variables
u-boot>> env print
arcNumber=3542
baudrate=115200
bootargs=console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfs=ext2
bootargs_console=console=ttyS0,115200
bootcmd=setenv bootargs $(bootargs_console); run bootcmd_usb; bootm 0x00800000 0
x01100000
bootcmd_usb=usb start; ext2load usb 0:1 0x00800000 /uImage; ext2load usb 0:1 0x0
1100000 /uInitrd
bootdelay=3
ceboardver=PPV2
cesvcid=2LMC9A3VZFLQTQ54Y6L26ZMW42
console=ttyS0,115200
ethact=egiga0
ethaddr=00:25:31:00:59:FB
fileaddr=1000000
filesize=DDC600
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /
rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd
; fi
if_netconsole=ping $serverip
ipaddr=192.168.2.10
led_error=orange blinking
led_exit=green off
led_init=green blinking
machid=dd6
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
preboot=run if_netconsole start_netconsole
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; na
nd read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs
ro rootfstype=ubifs $mtdparts $rescue_custom_params
serverip=192.168.2.2
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; se
tenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && u
bifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm
0x800000 0x1100000; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0
:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext
2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; el
se bootm 0x800000; fi
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_device=0:1
usb_init=run usb_scan
usb_root=/dev/sda1
usb_rootdelay=10
usb_rootfstype=ext2
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if t
est $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_
scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; se
tenv usb_root /dev/$dev; fi; done
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_scan_list=1 2 3 4
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_
rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
Environment size: 2859/131068 bytes
u-boot>>
For testing I installed
Debian-3.13.1-kirkwood-tld-2-rootfs-bodhi.tar.bz2 .
Before I was using Debian Wheezy with 3.2 kernel. Now I cannot even boot my old system.
Could anyone help please?
U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
Pogoplug E02
SoC: Kirkwood 88F6281_A0
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
88E1116 Initialized on egiga0
No link on egiga0
ping failed; host 192.168.2.2 is not alive
Hit any key to stop autoboot: 0
(Re)start USB...
USB: Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/uImage" from usb device 0:1 (usbda1)
2399792 bytes read
Loading file "/uInitrd" from usb device 0:1 (usbda1)
6568066 bytes read
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-3.13.1-kirkwood-tld-2
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2399728 Bytes = 2.3 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-3.13.1-kirkwood-tld-2
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 6568002 Bytes = 6.3 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Using machid 0xdd6 from environment
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
#####
My environment variables
u-boot>> env print
arcNumber=3542
baudrate=115200
bootargs=console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfs=ext2
bootargs_console=console=ttyS0,115200
bootcmd=setenv bootargs $(bootargs_console); run bootcmd_usb; bootm 0x00800000 0
x01100000
bootcmd_usb=usb start; ext2load usb 0:1 0x00800000 /uImage; ext2load usb 0:1 0x0
1100000 /uInitrd
bootdelay=3
ceboardver=PPV2
cesvcid=2LMC9A3VZFLQTQ54Y6L26ZMW42
console=ttyS0,115200
ethact=egiga0
ethaddr=00:25:31:00:59:FB
fileaddr=1000000
filesize=DDC600
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /
rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd
; fi
if_netconsole=ping $serverip
ipaddr=192.168.2.10
led_error=orange blinking
led_exit=green off
led_init=green blinking
machid=dd6
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
preboot=run if_netconsole start_netconsole
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; na
nd read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs
ro rootfstype=ubifs $mtdparts $rescue_custom_params
serverip=192.168.2.2
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; se
tenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && u
bifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm
0x800000 0x1100000; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0
:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext
2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; el
se bootm 0x800000; fi
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_device=0:1
usb_init=run usb_scan
usb_root=/dev/sda1
usb_rootdelay=10
usb_rootfstype=ext2
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if t
est $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_
scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; se
tenv usb_root /dev/$dev; fi; done
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_scan_list=1 2 3 4
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_
rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
Environment size: 2859/131068 bytes
u-boot>>
↧
Re: cannot boot ... probably incompatible uboot and rootfs
elcaramba,
Do these 2 things:
1. Make sure you have extracted the rootfs to a USB drive as root user, as stated in the instruction (sudo won't work). If you did not, then redo the rootfs.
2. Take your rootfs drive to anothe Linux box and fsck it for errors.
Do these 2 things:
1. Make sure you have extracted the rootfs to a USB drive as root user, as stated in the instruction (sudo won't work). If you did not, then redo the rootfs.
2. Take your rootfs drive to anothe Linux box and fsck it for errors.
↧
Re: cannot boot ... probably incompatible uboot and rootfs
Hi bodhi,
thank you for the quick reply.
I checked your recommendations.
1) the rootfs was extracted from a livecd as running user root.
2) fsck -f on the usb partition was run with success and no errors.
BTW: In the provided rootfs I had to copy uInitrd and uImage from /boot to / to start with the predefined boot command as defined in the environment variables.
I wonder if the environment variables arcNumber and machid have any effect. I also tried with different arcNumbers {2097, 2998, 3542} and machid {dd6, bb6}
Any other ideas? I also tried finding another version of u-boot binary, but I could not find anything which would fit to the pinkpogo.
thank you for the quick reply.
I checked your recommendations.
1) the rootfs was extracted from a livecd as running user root.
2) fsck -f on the usb partition was run with success and no errors.
BTW: In the provided rootfs I had to copy uInitrd and uImage from /boot to / to start with the predefined boot command as defined in the environment variables.
I wonder if the environment variables arcNumber and machid have any effect. I also tried with different arcNumbers {2097, 2998, 3542} and machid {dd6, bb6}
Any other ideas? I also tried finding another version of u-boot binary, but I could not find anything which would fit to the pinkpogo.
↧
↧
Re: cannot boot ... probably incompatible uboot and rootfs
elcaramba,
bootargs env looks wrong. Substitue $(bootargs_console) then you got only console=ttyS0,115200
bootargs env looks wrong. Substitue $(bootargs_console) then you got only console=ttyS0,115200
bootargs=console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfs=ext2 bootargs_console=console=ttyS0,115200 bootcmd=setenv bootargs $(bootargs_console); run bootcmd_usb; bootm 0x00800000 0x01100000
↧
Re: cannot boot ... probably incompatible uboot and rootfs
Hello bodhi,
indeed the bootargs were wrong.
I had to adjust them. Now I can boot even my old system again.
I appreciate your support! Thank you!
During the recovery process I observed that most of the time the boot process of linux was interrupted by failed fsck checks. (Here caused by unavailable USB disk which were referenced in the fstab)
Is there a way to have a netconsole active during the boot process. This would make the maintenance task much easier.
Best,
elcaramba
indeed the bootargs were wrong.
I had to adjust them. Now I can boot even my old system again.
I appreciate your support! Thank you!
During the recovery process I observed that most of the time the boot process of linux was interrupted by failed fsck checks. (Here caused by unavailable USB disk which were referenced in the fstab)
Is there a way to have a netconsole active during the boot process. This would make the maintenance task much easier.
Best,
elcaramba
↧
Re: Linux Kernel 3.14.0 Kirkwood package and rootfs (Non Flattened Device Tree)
Hi bodhi,
on the iConnect I was able to test the 3.14 kernel this weekend, everything is
running smoothly, however the dvb-usb-dw2102 driver was not able to recognize the usb-id of the tt-s2-4600,..
(i.e 0b48:3011 from Technotrend ),
the other device I could test is the 0ccd:00a8 TerraTec dvb-s2 usb card, this is working fine so far,..
when I applied the linux-3.14.0-tld-1-kirkwood.patch in a dry run on a plain
3.14 source tree, in this combined patch everything applied well, except that the part for the dw2102.c patch was missing,
(which explains the missing usb id's),..
the test of my tt-s2-4600 patch on the 3.14 kernel revealed rejects with dw2102.c,..
I am going to have a closer look into that in the next days and will resend the patch to you when the
problems are solved,
best wishes pbg4
on the iConnect I was able to test the 3.14 kernel this weekend, everything is
running smoothly, however the dvb-usb-dw2102 driver was not able to recognize the usb-id of the tt-s2-4600,..
(i.e 0b48:3011 from Technotrend ),
the other device I could test is the 0ccd:00a8 TerraTec dvb-s2 usb card, this is working fine so far,..
when I applied the linux-3.14.0-tld-1-kirkwood.patch in a dry run on a plain
3.14 source tree, in this combined patch everything applied well, except that the part for the dw2102.c patch was missing,
(which explains the missing usb id's),..
the test of my tt-s2-4600 patch on the 3.14 kernel revealed rejects with dw2102.c,..
I am going to have a closer look into that in the next days and will resend the patch to you when the
problems are solved,
best wishes pbg4
↧