Linux Device Hacking - Debian

Best way to revive my Pogoplug E02? (1 reply)

ian — Sun, 12 May 2013 15:16:51 -0400

Hi everybody!

I'm a bit clueless what might be the problem with my Pogoplug E02.

Here is what I did:
* installed squeeze from Pogo OS following http://projects.doozan.com/debian/
* updated to wheezy
* installed some packages using apt
* purge-removed proftp using apt

Here's what happend:
* after rebooting debian the LED is on but I get a "connection refused" via ssh
* the device answers ping-requests

As I could not figure out what might be the problem I rebooted without the USB-drive hoping to get back into the Pogo-environment and be able to reinstall debian but:
* the LED is steady green
* the device does not answer ping-requests
* ssh-connects time out
* the device displayed as "offline" in the manufacturer's webservice-UI

If boot with the USB-drive reattached I get the same as before:
* after rebooting I get a "connection refused" via ssh
* the device answers ping-requests

What might be the best way to revive my device of if the installed debian is still working - how do I get in?

TIA

Citadal Mail Server on Dockstar (no replies)

twinclouds — Sat, 11 May 2013 19:04:43 -0400

Hi,
I would like to set up my own email server using my domain, say "mydomain.com" hosted on zoneedit on Dockstar. I followed the instructions for Citadel on Raspberry Pi given in this link. Everything went smoothly. Now, come to configuration, because I have no experience of email server, I am a little confused.
First, what should I enter in the "Local host aliases section" section? Should I simply enter "mydomain.com"?
Secondly, for setting MX record, what should I use as the Host? Also "mydomain.com"?
Do I need specify any port number and forward that port on my router?
Hopefully someone had done the same thing and can help.
Thanks in advance.

[SOLVED] [dockstar] Booting stops with "Starting Kernel" (netconsole) (no replies)

moddy — Mon, 06 May 2013 06:18:30 -0400

Hi.
I got another dockstar and tried to install debian Squeeze with Jeff's script, but this time it does not work.
I used the netconsole from my firsz dochstar and this is how it boots:

root@dockstar:~# nc -l -u -p 6666

U-Boot 2011.12 (Feb 12 2012 - 21:33:07)
Seagate FreeAgent DockStar
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
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 "/rescueme" from usb device 0:1 (usbda1)
** File not found /rescueme
reading /rescueme.txt

** Unable to read "/rescueme.txt" from usb 0:1 **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000010000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: attached mtd1 to ubi0
UBI: MTD device name:            "mtd=3"
UBI: MTD device size:            219 MiB
UBI: number of good PEBs:        1749
UBI: number of bad PEBs:         3
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     0
UBI: available PEBs:             1728
UBI: total number of reserved PEBs: 21
UBI: number of PEBs reserved for bad PEB handling: 17
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1 bytes read
Found bootable drive on usb 0:1
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1437200 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
4536155 bytes read
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-2.6.32-5-kirkwood
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1437136 Bytes = 1.4 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-2.6.32-5-kirkwood
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4536091 Bytes = 4.3 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Here it seems to stop or loose cennection.

There are two errors.
1. The rescueme-error and
2. the UBIFS-Error (19).

Is one (or both) of them the source of the problem?

Regards...

[EDIT]
1. The "Starting Kernel" at the end of the netconsole-output is normal, because there the dockstar changes the IP
2. I used the wrong fw_setenv usb_rootfstype: ext3 but ext2

After i changed it back to ext2 debain booted!
:)

Debian 7.0 has been released! (5 replies)

gee-man — Fri, 10 May 2013 14:28:54 -0400

I made the update last night for my goflex net running squeezeplug (Debian 6.0), and everything is working fine. I had to tweak some of my config files, but other than that, it was a smooth update. I feel as if the OS is running a little bit faster off of my usb drive.

Pogoplug v2 hang at booting debian squeeze at "NET: Registered protocol family 10" (no replies)

basti523 — Sat, 04 May 2013 12:00:35 -0400

Hi,

i have installed on my Pogoplug Archlinux first and it boots up fine. Then i installed the Rescue System from here "https://dl.dropbox.com/u/1015928/Kirkwood/rescue/RescueV2.8.2-10292012.tar.gz"; and it works fine.

Then i would give debian a try. In Installed the squeeze Version from here "http://dev.shyd.de/dockstar/dockstar.debian-squeeze.sh"; on a USB Stick.
It installed without errors. On reboot, netcat is showing the following output:

U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
Pogoplug E02
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
Hit any key to stop autoboot:  0
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
** Block device usb 0 not supported

** Invalid boot device **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000008000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: attached mtd1 to ubi0
UBI: MTD device name:            "mtd=3"
UBI: MTD device size:            91 MiB
UBI: number of good PEBs:        728
UBI: number of bad PEBs:         0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     0
UBI: available PEBs:             717
UBI: total number of reserved PEBs: 11
UBI: number of PEBs reserved for bad PEB handling: 7
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
** Block device usb 0 not supported
** Block device usb 1 not supported
** Block device usb 2 not supported
** Block device usb 3 not supported
** Block device usb 0 not supported
** Block device usb 0 not supported
Wrong Image Format for bootm command
ERROR: can't get kernel image!
stopping USB..

NAND read: device 0 offset 0x100000, size 0x400000
 4194304 bytes read: OK
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.3.2-kirkwide
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3627768 Bytes = 3.5 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

For me, this looks all right!?

After waiting 5 Minutes, no ip is showed up in my router (dhcp). I can not ping the ip for my pogo and no ssh login.

I put the San Disk Cruzer Micro USB stick 2GB (arch boots up from it and other people mentioned it should work) into a virtual linux system and look into the /var/log/dmesg of the USB stick.


[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 3.2.0-4-kirkwood (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-12) ) #1 Debian 3.2.35-2
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: Marvell SheevaPlug Reference Board
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] On node 0 totalpages: 65536
[    0.000000] free_area_init_node: node 0, pgdat c043fa44, node_mem_map c04a6000
[    0.000000]   Normal zone: 512 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 65024 pages, LIFO batch:15
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
[    0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfstype=ext3 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
[    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Memory: 256MB = 256MB total
[    0.000000] Memory: 248496k/248496k available, 13648k reserved, 0K highmem
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xd0800000 - 0xfe800000   ( 736 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc03e3130   (3949 kB)
[    0.000000]       .init : 0xc03e4000 - 0xc0408000   ( 144 kB)
[    0.000000]       .data : 0xc0408000 - 0xc0442520   ( 234 kB)
[    0.000000]        .bss : 0xc0442544 - 0xc04a5b84   ( 398 kB)
[    0.000000] NR_IRQS:114
[    0.000000] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474ms
[    0.000000] Console: colour dummy device 80x30
[   13.531415] Calibrating delay loop... 1191.11 BogoMIPS (lpj=5955584)
[   13.621302] pid_max: default: 32768 minimum: 301
[   13.621426] Security Framework initialized
[   13.621502] Mount-cache hash table entries: 512
[   13.621839] Initializing cgroup subsys cpuacct
[   13.621865] Initializing cgroup subsys memory
[   13.621889] Initializing cgroup subsys devices
[   13.621899] Initializing cgroup subsys freezer
[   13.621907] Initializing cgroup subsys net_cls
[   13.621915] Initializing cgroup subsys blkio
[   13.621936] Initializing cgroup subsys perf_event
[   13.622026] CPU: Testing write buffer coherency: ok
[   13.623310] devtmpfs: initialized
[   13.625155] print_constraints: dummy: 
[   13.625403] NET: Registered protocol family 16
[   13.626202] Kirkwood: MV88F6281-A0, TCLK=200000000.
[   13.626215] Feroceon L2: Enabling L2
[   13.626251] Feroceon L2: Cache support initialised.
[   13.626842] initial MPP regs: 01111111 11113322 00001111 00100000 00000000 00000000 00000000
[   13.626864]   final MPP regs: 01111111 11113322 00001111 00000000 00000000 00000000 00000000
[   13.629103] bio: create slab  at 0
[   13.629477] vgaarb: loaded
[   13.630018] Switching to clocksource orion_clocksource
[   13.644164] NET: Registered protocol family 2
[   13.644370] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
[   13.644981] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[   13.645165] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
[   13.645260] TCP: Hash tables configured (established 8192 bind 8192)
[   13.645269] TCP reno registered
[   13.645279] UDP hash table entries: 256 (order: 0, 4096 bytes)
[   13.645306] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[   13.645516] NET: Registered protocol family 1
[   13.645546] PCI: CLS 0 bytes, default 32
[   13.645699] Unpacking initramfs...
[   14.193184] Freeing initrd memory: 6600K
[   14.193199] NetWinder Floating Point Emulator V0.97 (double precision)
[   14.193745] audit: initializing netlink socket (disabled)
[   14.193787] type=2000 audit(0.650:1): initialized
[   14.195187] VFS: Disk quotas dquot_6.5.2
[   14.195272] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[   14.195393] JFFS2 version 2.2. (NAND) (SUMMARY)  \xffffffc2\xffffffa9 2001-2006 Red Hat, Inc.
[   14.195730] msgmni has been set to 498
[   14.197254] alg: No test for stdrng (krng)
[   14.197366] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[   14.197379] io scheduler noop registered
[   14.197386] io scheduler deadline registered
[   14.197440] io scheduler cfq registered (default)
[   14.197518] mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
[   14.197552] mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
[   14.230087] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[   14.270086] mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
[   14.310085] mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
[   14.350084] mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
[   14.350468] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[   14.371009] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
[   14.798163] console [ttyS0] enabled
[   14.802638] ONFI flash detected
[   14.806039] NAND device: Manufacturer ID: 0xad, Chip ID: 0xf1 (Hynix NAND 128MiB 3,3V 8-bit)
[   14.814545] Scanning device for bad blocks
[   14.894217] 4 cmdlinepart partitions found on MTD device orion_nand
[   14.900522] Creating 4 MTD partitions on "orion_nand":
[   14.905687] 0x000000000000-0x000000100000 : "u-boot"
[   14.911505] 0x000000100000-0x000000500000 : "uImage"
[   14.917279] 0x000000500000-0x000002500000 : "rootfs"
[   14.923123] 0x000002500000-0x000008000000 : "data"
[   14.929464] mousedev: PS/2 mouse device common for all mice
[   15.940072] rtc-mv rtc-mv: internal RTC not ticking
[   15.945072] i2c /dev entries driver
[   15.948724] cpuidle: using governor ladder
[   15.952983] cpuidle: using governor menu
[   15.957063] Registered led device: plug:red:misc
[   15.957167] Registered led device: plug:green:health
[   15.957910] TCP cubic registered
[   15.961172] NET: Registered protocol family 17
[   15.965646] Registering the dns_resolver key type
[   15.970415] Gating clock of unused units
[   15.970424] before: 0x00dfc3fd
[   15.970431]  after: 0x00c701d9
[   15.970858] registered taskstats version 1
[   15.975413] /build/buildd-linux_3.2.35-2-armel-th89m3/linux-3.2.35/drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[   15.986576] Initializing network drop monitor service
[   15.992259] Freeing init memory: 144K
[   16.050604] udevd[48]: starting version 175
[   16.137957] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[   16.202736] mv643xx_eth smi: probed
[   16.246343] mv643xx_eth_port mv643xx_eth_port.0: eth0: port 0 with MAC address 00:25:31:04:8e:ad
[   16.265834] usbcore: registered new interface driver usbfs
[   16.287709] mmc0: mvsdio driver initialized, lacking card detect (fall back to polling)
[   16.302581] usbcore: registered new interface driver hub
[   16.327744] usbcore: registered new device driver usb
[   16.356688] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   16.392845] orion-ehci orion-ehci.0: Marvell Orion EHCI
[   16.398156] orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1
[   16.450075] orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000
[   16.470053] orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00
[   16.476068] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[   16.482905] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   16.490170] usb usb1: Product: Marvell Orion EHCI
[   16.494893] usb usb1: Manufacturer: Linux 3.2.0-4-kirkwood ehci_hcd
[   16.501200] usb usb1: SerialNumber: orion-ehci.0
[   16.506743] hub 1-0:1.0: USB hub found
[   16.510549] hub 1-0:1.0: 1 port detected
[   16.830068] usb 1-1: new high-speed USB device number 2 using orion-ehci
[   16.981457] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[   16.988185] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[   16.995366] usb 1-1: Product: USB2.0 Hub
[   17.003533] hub 1-1:1.0: USB hub found
[   17.013495] hub 1-1:1.0: 4 ports detected
[   17.290353] usb 1-1.1: new high-speed USB device number 3 using orion-ehci
[   17.400956] usb 1-1.1: New USB device found, idVendor=0781, idProduct=5151
[   17.407862] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   17.415216] usb 1-1.1: Product: Cruzer Micro
[   17.419501] usb 1-1.1: Manufacturer: SanDisk
[   17.423823] usb 1-1.1: SerialNumber: 0000A9709012037D
[   17.454315] SCSI subsystem initialized
[   17.462979] Initializing USB Mass Storage driver...
[   17.468184] scsi0 : usb-storage 1-1.1:1.0
[   17.473764] usbcore: registered new interface driver usb-storage
[   17.479798] USB Mass Storage support registered.
[   18.471050] scsi 0:0:0:0: Direct-Access     SanDisk  Cruzer Micro     6.51 PQ: 0 ANSI: 0 CCS
[   18.495386] sd 0:0:0:0: [sda] 3910655 512-byte logical blocks: (2.00 GB/1.86 GiB)
[   18.503353] sd 0:0:0:0: [sda] Write Protect is off
[   18.508171] sd 0:0:0:0: [sda] Mode Sense: 45 00 00 08
[   18.508602] sd 0:0:0:0: [sda] No Caching mode page present
[   18.514130] sd 0:0:0:0: [sda] Assuming drive cache: write through
[   18.523602] sd 0:0:0:0: [sda] No Caching mode page present
[   18.529113] sd 0:0:0:0: [sda] Assuming drive cache: write through
[   18.538609]  sda: sda1 sda2
[   18.544728] sd 0:0:0:0: [sda] No Caching mode page present
[   18.550261] sd 0:0:0:0: [sda] Assuming drive cache: write through
[   18.556381] sd 0:0:0:0: [sda] Attached SCSI removable disk
[   18.571517] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   26.577937] kjournald starting.  Commit interval 5 seconds
[   26.583607] EXT3-fs (sda1): mounted filesystem with ordered data mode
[   27.787125] udevd[242]: starting version 175
[   29.089212] Adding 251776k swap on /dev/sda2.  Priority:-1 extents:1 across:251776k 
[   29.427904] EXT3-fs (sda1): using internal journal
[   36.067922] mv643xx_eth_port mv643xx_eth_port.0: eth0: link up, 1000 Mb/s, full duplex, flow control disabled
[   54.387527] NET: Registered protocol family 10

I do not know where could be a problem. I found this "topic" but in the fstab i cant see any wrong code:

# /etc/fstab: static file system information.
#
#                                        
/dev/root                     /               ext2        noatime,errors=remount-ro        0             1
/dev/sda2               none            swap       sw                                              0             0

uname -a on the pogoplug rescue system shows:

Linux rescue 3.3.2-kirkwide #1 Mon Oct 29 17:52:07 CDT 2012 armv5tel GNU/Linux

what can i do?

ssh / telnet session are closed immediately (no replies)

ringprince — Sun, 28 Apr 2013 18:20:17 -0400

Hi all,

I have problems loggin in to my pogoplug with debian installed. I can not start an interactive session (neither via ssh nor via telnet).

I have asked a question about this on the debian-users list already here where you can find the long story until now:
http://comments.gmane.org/gmane.linux.debian.user/454878

Quick summary: I still have no clue what is wrong.

Long summary:
Neither root nor an ordinary user can log into the pogo interactively. The problem occurs both on ssh and telnet, thus, I suspect the problem not to be an sshd misconfiguration.
What I can do is executing commands via ssh access (as in 'ssh root@192.168.2.109 bash' which gives me a crippled bash).

Latest guess was it is sth related to the (pseudo-)ttys.

I also followed the commit related to a similar error in geexbox:
http://www.geexbox.org/forum/topic/telnet-connection-closed-by-foreign-host/
and re-compiled a kernel with
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=16
but that did not help either.

So, my question is: Is this somehow known to anybody here? And is there anything I can do about this?

I can provide any file that might be of interest.

Any help on this is greatly appreciated.

Regards,
Andreas

No UVC modules with kernel 3.6.11-kirkwood-tld (12 replies)

richard-g8jvm — Sat, 27 Apr 2013 17:33:45 -0400

Hi
still trying to get a web cam running on the pogoplug.
New webcam Logitech C270, works fine on the laptop, but /dev/video0 is not being created when its plugged in.

hwifo --usb shows

03: USB 00.0: 0000 Unclassified device
[Created at usb.122]
Unique ID: dwDZ.VY6alo95Db5
Parent ID: ADDn.d7FDLX76qXB
SysFS ID: /devices/platform/orion-ehci.0/usb1/1-1/1-1.3/1-1.3:1.0
SysFS BusID: 1-1.3:1.0
Hardware Class: unknown
Model: "Logitech Unclassified device"
Hotplug: USB
Vendor: usb 0x046d "Logitech, Inc."
Device: usb 0x0825
Revision: "0.10"
Serial ID: "DE626B20"
Speed: 480 Mbps
Module Alias: "usb:v046Dp0825d0010dcEFdsc02dp01ic0Eisc01ip00in00"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #8 (Hub)

The module alias doesn't help a lot

starting motion -s doesn't show which module its loaded either

root@debian:/# motion -s
[0] Processing thread 0 - config file /etc/motion/motion.conf
[0] Motion 3.2.12 Started
[0] ffmpeg LIBAVCODEC_BUILD 3482368 LIBAVFORMAT_BUILD 3478785
[0] Motion running in setup mode.
[0] Thread 1 is from /etc/motion/motion.conf
[0] Thread 1 is device: /dev/video0 input 8
[0] Webcam port 7661
[0] Waiting for threads to finish, pid: 1885
[0] motion-httpd/3.2.12 running, accepting connections
[0] motion-httpd: waiting for data on port TCP 7660
[1] Thread 1 started
[1] Failed to open video device /dev/video0: No such file or directory
[1] Could not fetch initial image from camera
[1] Motion continues using width and height from config file(s)
[1] Resizing pre_capture buffer to 1 items
[1] Started stream webcam server in port 7661

Plugging the webcam in on the laptop shows it as a UVC camera

lsmod | grep uvc shows nothing

root@debian:/# locate uvc
/lib/modules/2.6.32-5-kirkwood/kernel/drivers/media/video/uvc
/lib/modules/2.6.32-5-kirkwood/kernel/drivers/media/video/uvc/uvcvideo.ko
/lib/modules/3.2.0-4-kirkwood/kernel/drivers/media/video/uvc
/lib/modules/3.2.0-4-kirkwood/kernel/drivers/media/video/uvc/uvcvideo.ko
/usr/include/linux/uvcvideo.h

I suspect I will need v4l2 modules as well , and they aren't there either.

root@debian:/dev# locate v4l
/lib/modules/2.6.32-5-kirkwood/kernel/drivers/media/video/v4l1-compat.ko
/lib/modules/2.6.32-5-kirkwood/kernel/drivers/media/video/v4l2-common.ko
/lib/modules/2.6.32-5-kirkwood/kernel/drivers/media/video/v4l2-int-device.ko
/lib/modules/3.2.0-4-kirkwood/kernel/drivers/media/video/v4l2-common.ko
/lib/modules/3.2.0-4-kirkwood/kernel/drivers/media/video/v4l2-int-device.ko
/lib/udev/v4l_id
/lib/udev/rules.d/60-persistent-v4l.rules
/usr/include/linux/v4l2-mediabus.h
/usr/include/linux/v4l2-subdev.h
/usr/lib/arm-linux-gnueabi/directfb-1.2-9/interfaces/IDirectFBVideoProvider/libidirectfbvideoprovider_v4l.so
root@debian:/dev# uname -r
3.6.11-kirkwood-tld
root@debian:/dev# cd /lib/modules/3.6.11-kirkwood-tld/kernel/drivers
root@debian:/lib/modules/3.6.11-kirkwood-tld/kernel/drivers# ls
ata bcma cdrom crypto hwmon input md mfd mtd pci ptp scsi staging uio video
atm block char firewire i2c isdn memstick misc net power regulator spi target usb w1
base bluetooth connector hid ieee802154 leds message mmc parport pps rtc ssb tty uwb watchdog

Can the modules that are missing be copied from kernel 3.2, or are the signed ??????
or is it grab the kernel source and build the modules, and the last time I did that was on a 2.0 kernel , so I forgotten how.

Thanks

Thanks

SSH latency (4 replies)

richard-g8jvm — Fri, 26 Apr 2013 16:18:13 -0400

Hi
Is there anyway of improving the SSH latency on a PogplugE02.
No problem with scp up and downloads, but when typing on CLI it seems to hang for several seconds at a time.
characters sent are received but not shown , then appear after a few seconds. other times no delay.
Top shows nothing taking more than 5%.
A ping shows times less than 3ms
Is this normal with a pogoplug ?

Howto edit /remove a fw_env entry (2 replies)

richard-g8jvm — Thu, 25 Apr 2013 15:56:36 -0400

Hi
I need to remove an entry from fw_env
I had just got to the stage of interchangeable USB flash drives one with debian one with Arch

As both booted up with the orange LED on I added fw_env machid dd6

Green Led on Arch when it boots up and now Debian will not boot.

Does the debian kernel not like machid dd6 ???

I need to delete that entry , How ?????

thanks

###########################################################
It is definately the fw_env entry machid dd66 that will stop Debian from booting
Removing it allows both Debian and Arch to be used by just changing USB flash drives
Its the entry Arch use to set the LEDs to the selected colour

I changede the entry by deleting them all , but thats a bit drastic

motion and opening ports Debian Wheezy pogoE02 (6 replies)

richard-g8jvm — Thu, 25 Apr 2013 15:52:15 -0400

Hi
having a few problems getting motion running, the daemon is up and running , but ports 8080 & 8081 are closed.
I've loaded iptables , but haven't set up iptables for years, so it start again from scatch :(
There are plenty of Arch blogs on Motion and webcams, but so far googling is failing with Debian.
Is there a ncurses gui or anything for setting up firewall or just getting ports open
Which app by default sets which ports are open ?, its not iptables as thats not in the inital install

Is there a armel deb for web min, which might make things easier ?
Thanks
Richard

is there any real diffrenece between a pinkpogoE02 and a blackpogoE02 (no replies)

richard-g8jvm — Wed, 24 Apr 2013 07:04:10 -0400

Hi, new here so no flames for the first 10 posts please
The subject says it all.
I got a new pogo E02 , loaded debian, then tried Arch, which no matter what I did would not boot,
So back to Debian, which wouldn't boot until I forced a reload of uboot.
So far using it as intendend as a print server. I'm toying with using it also as an audio server using pulseaudio and an external USB sound card.
Outa intererest does the LED on the front ever do anything apart from staying amber. ?

fw_printenv shows the green led should be on, and :-
root@debian:/sys/class/leds/plug:green:health# cat trigger
none nand-disk timer [default-on] mmc0

Thats why I ask is there a firmware difference or something ?
Thanks
Richard

NFS 4.1 support in Kirkwood kernel? (2 replies)

pogoomane — Sat, 13 Apr 2013 17:18:19 -0400

Hi,

I'm trying to set up a NFS server on my Pogoplug v2 and can't get NFS 4.1 to work (which I need for Windows compatibility). From what I gather, NFS 4.1 should be supported by Debian wheezy, but on my Pogoplug it looks like it isn't:

cat /proc/fs/nfsd/versions
+2 +3 +4 -4.1

Is this a problem with the Kirkwood kernel or should I start asking around in "general" Debian forums?

Debian not booting on Pink E02 (8 replies)

cyablo — Fri, 26 Apr 2013 04:41:27 -0400

Hello,

Ive got a Pink Pogoplug E02 on wich i tried to install Debian. The wheezy Installer fails with "kernel too old", so i tried squeeze. The installer runs trough but the Pogoplug did always boot into original os. i controlled the boot with netconsole, and it said that it couldn't find uImage and uInitrd, so i did:

http://forum.doozan.com/read.php?2,12006,12036#msg-12036

Now it runs trough the uBoot process:

U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
Pogoplug E02
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
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 "/rescueme" from usb device 0:1 (usbda1)
** File not found /rescueme
reading /rescueme.txt

** Unable to read "/rescueme.txt" from usb 0:1 **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000008000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: attached mtd1 to ubi0
UBI: MTD device name:            "mtd=3"
UBI: MTD device size:            91 MiB
UBI: number of good PEBs:        727
UBI: number of bad PEBs:         1
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     0
UBI: available PEBs:             716
UBI: total number of reserved PEBs: 11
UBI: number of PEBs reserved for bad PEB handling: 7
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1 bytes read
Found bootable drive on usb 0:1
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
1437200 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
4536158 bytes read
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-2.6.32-5-kirkwood
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1437136 Bytes = 1.4 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   Initrd-2.6.32-5-kirkwood
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    4536094 Bytes = 4.3 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

But ends up with a orange LED and no network connection is coming up :(

Somebody a idea?

greets

Daniel

Can't boot debian from Pogoplug v2 (6 replies)

pogoomane — Sat, 06 Apr 2013 17:09:41 -0400

Hi,

I know I'm not the first one with this problem, but after following a couple of solutions from other threads etc. I still can't get my Pogoplug to boot debian.

This is what I did:

1. I unpacked my brand new Pogoplug POGO-E02, registered at my.pogoplug.com, enabled SSH and checked which CPU I had - ARM5TE.

2. I followed these instructions and installed ArchARM http://archlinuxarm.org/platforms/armv5/pogoplug-v2-pinkgray Everything went well, I had Archlinux running, but found it too confusing and wanted to install Debian instead as I have a bit more experience with it and it is more beginner-friendly.

3. I pulled out the USB stick while Arch was running (this might just not have been the best idea)

4. I rebooted the Pogoplug without a USB stick and logged in as root using the password I set when I registered

5. I then tried installing Debian following these two instructions:
http://mehl.co/articles/installing_debian_on_the_pogoplug/index.html
http://projects.doozan.com/debian/

None of them worked - the first link and the wheezy script from the second link got me a yellow light and no ssh and squeeze from the second link just booted in the Popoplug system.

I tried installing the debian with each script a few times and also a few more things (changing fdisk options, reinstalling uboot etc) and every now and then during installs I got an error message, which I resolved after a bit of googling and the install then went through without problems, but debian just isn't booting :(

I'm trying to boot using Transcend JetFlash 700 16GB TS16GJF700. I read mixed things in the "working usb sticks" thread in this forum about Transcend, some work, some don't, but couldn't find anyone stating something about this exact model. I found this though, which seems to be running using my model https://wiki.mytrackdays.eu/index.php?title=Pogoplug_E02_specifications and Archlinux did boot without a problem, so I think the stick isn't the problem.

I hope you people can head me of to the right directions finally getting my Pogoplug up and running with debian

External USB drives and Load Cycle Counts (11 replies)

restamp — Mon, 08 Apr 2013 23:59:45 -0400

I have recently been investigating the suitability of small 2.5" pocket disk drives in a 24/7 application as the main drive on an Arm (Pogoplug, Dockstar, etc.) server. These drives are nice to use because they are self-contained, take little power, and require only one connection to the outside world -- the USB cable. I have one such server which I set up in January using an old Western Digital 160GB pocket drive I had lying around. It has worked flawlessly, but the drive itself seemed to make a slightly worrysome reset sound on a regular basis. With the aid of the smartmontool smartctl, I noticed the drive was racking up a huge number of Load_Cycle_Count events. Further investigation (via Google) revealed that this drive, like many pocket drives, is designed to park the heads by default if the drive has not been accessed for 5 seconds. This may make sense in a typical applcation where the drive is subject to being physically knocked around, but Unix on a quiescent box has background tasks which can still result in disk accesses several times a minute. In a server application, the net result is that the heads are constantly being parked and unparked. The drive keeps tabs on how many times this occurs and the smartctl command can be used to view this and other data. In approximately 3 months of run time, my little WD drive had parked and unparked its heads over a quarter million times, and most drives are lifetime speced at 300-600k head parks. Thus, these drives could easily exceed their lifetime design in the respect in well within a year of normal use.

One solution is to forego the use of these pocket drives in this application. A conventional 3.5" drive in an external enclosure will typically not have this sort of programming. Another option is to turn off this head-parking function in the drive. The most recent smartctl program has a facility to do this, but unfortunately, the version packaged with Debian Squeeze and Wheezy predates the addition of this code. It is fairly straightforward to download the latest smartmontools tarball from sourceforge and compile your own copy, though.

My question: Is anyone else here using 2.5" portable drives as their storage device on their Plug servers? If so, what sort experience have you had with these drives? Have you taken any steps to deal with this problem? Finally, it's late here, but if people are interested I can give you more specific details at a later point in time as to how I've worked around this problem. But, I'm mainly curious whether others have seen any problems with these small drives in the application.

YMMV.

Debian Squeeze on Pogoplug Pink: Sudden Segmentation Faults (2 replies)

darethehair — Sat, 27 Apr 2013 08:17:42 -0400

I had been running Debian Squeeze on my pink Pogoplug since 2011 quite happily. Occasionally, for no reason that I could see, a 'lockup' would occur, and my solution was typically to force a power-down, remove my USB stick, run 'fsck' repairs required, plug back in, and reboot. I learned that some USB brands were more resilient than others. Yes, a bit tedious at times but mostly amazing to watch my 4 watt wonder webserver...

Then, about 2 weeks ago, something weird happened. Some of the programs were failing with 'segmentation faults'. I suspected that maybe the binaries had been corrupted by USB stick errors -- but 'fsck' told me that everything was clean! I had no idea what to do, and didn't want to run in circles for days, so I did an emergency transfer of my webserver environment to an old Fujitsu laptop (slower benchmarks than the Pogoplug!). So far it is working fine in its new role...

So now I don't know what to do next with my Pogoplug. How can I avoid this mystery 'segmentation fault' failure in the future? Should I avoid USB sticks and use portable USB hard drives instead? Should I use the new 'wheezy' scripts and start over again?

Kirkwood benchmark results needed (no replies)

gnexus — Tue, 02 Apr 2013 10:21:04 -0400

I have started a Phoronix Test Suite Openbenchmark thread in the A10 forum:
http://forum.doozan.com/read.php?6,12066
that compares the performance under Ubuntu/Fedora of several of the Android-based HDMI mini-PCs. It also includes Linux benchmarks of some other devices including the Samsung Exnos 5 Chromebook, ODROID-U2, Intel i7-950, Intel C2D T7300, and the Acer C7 Chromebook.

It would be nice to have a benchmark of a Kirkwood-based device as a baseline. I would run it on my GoFlex Net, but I'm moving next week and my GoFlex Net's are being mothballed into storage for a year.

Please post a Kirkwood-based device benchmark. Any Kirkwood-based device would suffice. Thanks!

Why tmux think screen's serial feature is bloated? (no replies)

syong — Tue, 02 Apr 2013 00:46:39 -0400

Here is my guess:

(%8)(23:42)(punk)~> cat bin/serial 
#!/bin/sh

if [ $# -ne 2 -o ! -c $1 ]; then
        echo "`basename $0`  "
else
        stty -F $1 $2 line 0 kill ^H min 100 time 2 brkint -icrnl -imaxbel -opost -onlcr -isig -icanon -echo
        cat $1 &
        trap "kill $?" INT
        while read _C
        do
                echo "$_C" > $1
        done
fi
(%8)(23:42)(punk)~>

Debian install on pogoplug series 4-need help (10 replies)

t3ch42 — Sun, 07 Apr 2013 15:35:13 -0400

Hello.
After searching the forums and other sites on the Internet, I still haven't found a direct way to install a debian fs on my ppv4.
I have a freshly reverted pp after trying out archlinux. I'm looking for stability, and the general feeling from archlinux is more "cutting edge".
I am more comfortable with debian, as I have been using Ubuntu systems for years.

I found http://forum.doozan.com/read.php?3,7477,page=2
which seems to be a somewhat direct install, but I can't tell if it is doable from a pogo os.

Is there a howto or some direction that one could give me for a uboot and debian install? I'd like to get the rescue working also, but wanted to concentrate on the main debian install first.

Thanks for reading.

Linux Kernel 3.8.11 Kirkwood package (Non Flattened Device Tree) (40 replies)

bodhi — Fri, 17 May 2013 11:01:15 -0400

Updated 17 May 2013:

Kernel 3.8.11 package was uploaded. Same installation instruction as 3.6.11 below. This tarball contains 3 files: kernel 3.8.11 deb package, config file, and kirkwood patch.

Download at Dropbox:
linux-3.8.11-kirkwood-bodhi.tar.bz2
MD5:
4f4f75eb4a4099f0fa2b017c003aac3d

-------------------------------------------------------

I have uploaded a Debian kernel package for 3.6.11-kirkwood which I've built with a collection of patches for GoFlex Home/Net, Pogoplug E02/Mobile/V4, iConnect, Dockstar, Sheevaplug and a few other Kirkwood plugs are already in the mainline. Since we don't have all Kirkwood FDT board files available yet (mainline has GoFlex Net and iConnect), I thought it would be useful for users who are looking to run kernel 3.6.x on Kirkwood boxes and can't wait for their board files to be submitted. This patched kernel basically de-selected FDT option in kernel config, and also has changed some FDT-only initialization code to remove compile problem. With this kernel we can run the Kirkwood boxes with arcNumber (i.e. mach-types implementation) like we've been doing.

Download at Dropbox:
linux-3.6.11-kirkwood-bodhi.tar.bz2
MD5:
f11c9d4a0df55bed38f5bfee2d5081a1

To install:

- Backup your current uImage and uInitrd. In the /boot directory, these are files for your current kernel (xx.xx.xx is the version number):

uInitrd
uImage
initrd.img-xx.xx.xx-kirkwood
System.map-xx.xx.xx-kirkwood
vmlinuz-xx.xx.xx-kirkwood
config-xx.xx.xx-kirkwood

- Extract the kernel in the archive and install it

tar -xjf linux-3.6.11-kirkwood-bodhi.tar.bz2
dpkg -i linux-image-3.6.11-kirkwood-tld_1.0_armel.deb

- Ignore the error messages about can't not flash-kernel, and create the uImage and uInitrd manually

mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-3.6.11-kirkwood-tld -d /boot/vmlinuz-3.6.11-kirkwood-tld /boot/uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-3.6.11-kirkwood-tld  -d /boot/initrd.img-3.6.11-kirkwood-tld /boot/uInitrd

- The new uImage and uInitrd files should be created in /boot directory now. You're ready to reboot the system

sync
shutdown -r now

Note:
For completeness, create symlinks for the kernel in your / directory (in case the rootfs is ever used with different bootloader). But it is not necessary to do this for uBoot.

cd /
ln -s boot/vmlinuz-3.6.11-kirkwood-tld vmlinuz
ln -s boot/initrd.img-3.6.11-kirkwood-tld initrd.img

Enjoy! and let me know if there is any problem.

I've attached the patch and the kernel config file here for anybody wants to build their own kernel.

Addendum:

The patch was cleanup and reattached.

Help needed with wifi bridge setup (3 replies)

dubanks — Wed, 03 Apr 2013 10:01:58 -0400

Folks,

I am trying to setup dockstar as wifi bridge. I am running stock wheezy with 3.2.0-4-kirkwood kernel.

Main_Router ------> [WiFi link] <-----Dockstar-----Linksys switch----multiple PCs

My /etc/network/interfaces is given below:


auto lo ra0
iface lo inet loopback
iface eth0 inet manual

allow-hotplug ra0
iface ra0 inet manual
pre-up wpa_supplicant -Dwext -i ra0 -c /etc/wpa.conf -B


auto br0
iface br0 inet dhcp
      bridge_ports ra0 eth0
      bridge_stp off
      bridge_maxwait 5
wpa-bridge br0

With this I am not seeing DHCP from dockstar or any PC connected to the switch. I do see wifi link established between router and dockstar.

Can anyone help?

TIA
D Banks

OpenMediaVault On GoFlex Net (no replies)

tabernacle — Sat, 30 Mar 2013 15:08:54 -0400

Hi there,

After a lot of messing (days rather than minutes) around I finally managed to get OpenMediaVault running on my GoFlex Net, wasn't easy, certainly took a lot longer than I expected with a multitude of things to learn/fix, quite frustrating at times. I thought I'd share what I learnt, perhaps useful for others. I'm not much skilled at Howtos etc, so you'll have to do your own googling/trawling same as I had to, mostly just wanted to share that it's possible and some of the considerations.

Flash memory and Linux filesystems - SD cards and micro SD cards don't seem to like Linux filesystems. I have a preference for Sandisk as I have found them reliable in the past. I was NOT ABLE to get a bootable rootfs on SD card, and have had problems with Linux on SD card before. Article I found said that basically SD card designed to be FAT or FAT32 filesystem formatted, and if formatted with anything else well not good, it messes with their Chi or something, who knows, bottom line it doesn't work. So I ended up with a Sandisk Cruzer 4GB (USB Flash drive) which seems to work OK with ext2 or ext3. I have now replaced this with a Sandisk Cruzer Fit 8GB, which seems to be working OK at the moment on ext3.

Jeff Doozan's put debian on your GoFlexNet - Basically it doesn't work. It reflashed my GoFlex so possible to boot off USB, but neither the wheezy or squeeze installers produced a bootable USB stick, and I remember both crapping out with errors. After a lot of messing around I found davygravy's rootfs for his NSA320 and was able to get my GoFlex Net to boot off that, so I had a working SSH again, phew it wasn't bricked after all.

I'm not quite ready to dispense with the built in PogoPlug linux, so didn't want to install the Rescue System (although probably possible to back it up and reflash it later ?). I wasn't sure that OMV would work with newer linux kernel, wheezy rather than squeeze.

I found a post that described how to put GoFlex Net back to original U-Boot, which enables me to boot into the pogoplug linux, if I wish (http://forum.doozan.com/read.php?2,11070,11085#msg-11085 this is the goflex net original uboot, should use this rather than the doozan u-boot page which says for dockstar)

Initally I tried to install OMV onto davygravy's NSA320 rootfs (http://forum.doozan.com/read.php?2,7806), but had a lot of package problems so eventually abandoned, days of my life I will never get back ! At the time it didn't make sense to me having a 3.x linux kernel on squeeze installation, but may have missed something here?

Then I found vlad's built your own rootfs guide (http://forum.doozan.com/read.php?2,5986), very thorough well written, although there are a couple of inconsistencies towards the end (I'm still chroot'ed in Ubuntu and he's asking me to run commands on the GoFlex). I managed to build a rootfs using vlad's script. But again I got doozan'ed the doozan kernel referenced in vlad's post just didn't boot. He also mentioned varkey's kernel, so I downloaded the varkey .deb package and installed that kernel, whilst chroot'ed into the rootfs .img file. So I managed to produce a working rootfs squeeze debian/varkey kernel. All of this done in Ubuntu installation in VirtualBox VM on Windows 7.

OMV vault had a couple of issues with install, collectd daemon is a bit crap, needs to have IP address and hostname in /etc/hosts file or it freaks out, so needed to do this (it's described on the OMV pogoplug howto). Also there's some messing around with getting a version of xmlstartlet that works with OMV, that is on the OMV/pogoplug howto (http://forums.openmediavault.org/viewtopic.php?f=12&t=514)

Once I had OMV up and running, I wanted the miniDLNA. To get this I needed to do some messing around with installing a plugin for OMV-Plugins.org which are some plugins that are maintained outside of OMV.

OpenMediaVault, so far seems to work quite well on GoFlex Net. Linux also doesnt seem to get on very well with NTFS, so transfer speeds I have tried so far were up 20MB/s which is OK. What I am doing now is setting up Raid 1 with a couple of Seagate 1TB backup plus drives.

The fw_setenv to 3089 seems to be important for things to work properly, well at least for the LED to tell you when it's booted OK. Oh and vlad's calling the rootfs partition "rootfs" and updating the U-Boot fw_setenv to force boot off USB "rootfs" a good idea, otherwise soon as you connect SATA drives doesnt boot off USB anymore.

Be interested to know if anyone else managed to get OMV up and running and what their experiences are ...

OMV in my understanding only runs on squeeze, has anyone tried on wheezy, does it work ? which kernel did you use ?

OK, hopefully helpful to someone, save them a bit of time or give them a bit of hope that it does actually work :)

Cheers,

Mastrov Muppez

PS. I'm experienced IT wise, but not much knowledgable about linux or embedded systems. It would have been really useful if someone could have torrented a working rootfs for GoFlex Net with a tested known good kernel, a short howto of how to get it on a USB stick. I really don't have the experience to know what's good and what's not, so wouldn't want to do it myself. Anyone ?

Unable to boot Debian on Dockstar (1 reply)

David — Thu, 28 Mar 2013 20:26:33 -0400

First, thanks to all who did this possible, it's a great work! :)

I got my dockstar from ebay, I think it was not updated, as I could SSH to it and disable the pogoplug updater:
killall hbwd
mount -o remount,rw /
vi /etc/init.d/rcS
and change "/etc/init.d/hbmgr.sh start" to "#/etc/init.d/hbmgr.sh start"

Then, I tried the scripts for lenny, squeeze and wheezy, but none worked at all.
Those were the scripts I tried until now:

http://projects.doozan.com/debian/kirkwood.debian-wheezy.sh
http://projects.doozan.com/debian/dockstar.debian-squeeze.sh
http://ss4200.homelinux.com/dockstar/gogo-dock.sh
http://dev.shyd.de/dockstar/dockstar.debian-squeeze.sh
http://projects.doozan.com/debian/dockstar.debian-lenny.sh

I tried with different USB drives, but nothing changed.

Basically, what I did for each install was:

export PATH=$PATH:/usr/sbin:/sbin

mount -o remount,rw /
rm /usr/sbin/debootstrap
rm -r /usr/share/debootstrap
(This was to ensure that there was a clean installation of debootstrap for each script)

wget http://script_name
chmod 777 script_name
./script_name
blah blah type warning are your sure, type "ok"--> ok
blah blah lots of stuff but no errors or warnings
Want to reboot? Y/n -->Y

After the reboot, the led blinks green, then blinks orange while it loads from the USB drive (the drive's led blinks too), after 15 seconds it stops and remains solid green.
But I can't connect to it, my router doesn't have anything than my computer on DHCP leases. Tried a network scan but nothing was found.
Reading my router log shows the LAN port where the dockstar is connected going up and down every few minutes.

I tried editing /etc/network/interfaces in the USB contents and set this: (my router address is set to 192.168.1.2)
# iface eth0 inet dhcp
iface eth0 inet static
address 192.168.1.100
netmask 255.255.255.0
gateway 192.168.1.2
dns-nameserver 192.168.1.2
But still doesn't work. I can't ping nor SSH to dockstar.
I remove the USB and reboot, and I'm again on pogoplug firm.

Any hints? Currently I don't have any serial adapter (It broke down), so I'm waiting for them coming from ebay (china)...still 3 weeks left, or so.

Thanks!

GoFlex NET: SATA disk not visible (9 replies)

azeera — Wed, 15 May 2013 03:13:49 -0400

Hi,

with great help from the forum I installed wheezy on a stick and can sucessfully boot it. When I plug in a SATA disk I hear that the motor starts spinning but it is not recognized by the kernel. Is there anything else that needs to be done in order to use a SATA disk?

Regards,
azeera

Linux Kernel 3.6.x Reboot [SOLVED] (16 replies)

bodhi — Sun, 31 Mar 2013 17:45:40 -0400

I've compiled kernel 3.6.11 (with Device Tree turn off), and can run on a Dockstar without problem (cold start, warm start, ...everything works great) . Some of the new features are quite interesting:
http://forum.doozan.com/read.php?2,8177,8332#msg-8332

Currently, I'm seeing a strange behavior. I cloned the USB stick to another in order to boot it on a Pogo E02, and it cold started everytime, no problem. However, a "shutdown -r now" would hang the system.

It seems it could not shutdown, and got stuck somewhere before the halt command in "/etc/rc0.d/K07halt" (I have LED light off command insert before the halt command).

It's a puzzle, since I'm sure the cloning of the stick was successful because the cold start never fails, only the warm start. And it only occurs with the cloned stick.

I guess it's serial console time :) but if anybody knows why please post.

trying to reanimate bricked Dockstar (2 replies)

michapixel — Wed, 27 Mar 2013 19:22:59 -0400

My situation is as followed:

i am by no means an expert on this field, so bear with me, if i sound a little confusing here and there :-)

I have 2 Dockstars here. One (a) did run Debian for quite some time (~2years), until i bricked it by updating it and not restarting it correctly (i guess), so the Dockstar did not boot completely (cannot verify this, cause on this one i changed the led-functions a bit). The other one (b) was laying around for some time, i experimented a little bit with it, but had no luck with some USB-Sticks i had laying around, so i decided to have it as a backup.
It seems it's time has come.

At first i tried to connect my jtag with Dockstar a) and i succeeded to get all the messages. It did boot into uboot, but there were checksum errors. I followed some links on how to solve that problem, but that seemed to be way over my head :-) so i gave up to follow this route.
then i tried to let it boot into debian from it's stick, but it never reached networking status. i tried to nmap it but no luck.
i then connected it again via serial/jtag and made my self a little comfortable with the pre-boot or uboot environment.
i finally found the ipaddress it gave itself with the help of this incredible forum and some other links / sites i found. but other than that i did not find out.

so i thought to myself: why not give dockstar b) a chance, at least that's what i decided once it was meant for.

but since it seems to have the same illness like a) - not showing up on my routers network, i connected it directly to my desktop - via jtag and network - and tried to find out what it did on it's booting-process.
So far i can say: it boots fine into pogoplug system, but fails to unknow reason to get an ip-address on my home network. i can ssh into it on it's 169.* address. so i though: i should bridge the network from my desktop to the dockstar, so i can at least install debian (or try to) on another stick.
but even that fails:

# Starting debootstrap installation
E: unrecognized or invalid option --no-check-gpg
debootstrap failed.
See /tmp/debian/debootstrap/debootstrap.log for more information.

but there is no debootstrap.log. inside /tmp/debian there's only a "lost+found" folder.

if anyone has an idea, what i could do now, i'd be very happy if you could lead me on this way.
if you need more information, please ask, as i am definately not an expert,

Install script stops with "debootstrap failed." (13 replies)

azeera — Mon, 25 Mar 2013 17:21:19 -0400

Hi,

I tried to install debian wheezy on my new FreeAgent GoFlex Net. When I run ./kirkwood.debian-wheezy.sh it installs uBoot but later stops with:

# Starting debootstrap installation
I: Retrieving InRelease
debootstrap failed.
See /tmp/debian/debootstrap/debootstrap.log for more information.

cat /tmp/debian/debootstrap/debootstrap.log shows

-bash-3.2# cat /tmp/debian/debootstrap/debootstrap.log
Connecting to cdn.debian.net (149.20.20.135:80)
debootstrap.invalid_ 100% |*****************************************************************************************************| 218k 00:00:00 ETA
/usr/share/debootstrap/functions: line 534: gpg: command not found

Any hint?

Thanks Azeera

ntp stopped working - here's the workaround (4 replies)

punxsutawney-phil — Sat, 23 Mar 2013 11:14:36 -0400

Hi

I am running Linux GoFlexNet 3.3.2-kirkwood-dg #1 Mon Apr 23 17:09:27 CDT 2012 armv5tel and noticed that newly copied files to my harddisks connected to my GoFlexNet (smb shares) had shown no date and time anymore in Windows-Explorer.
They were set to 1970-01-01 ...

The GoFlexNet has no HWCLOCK so it had to be ntpd that failed.
Somwhere else on the net I found the advice to remove the ntp-package with 'apt-get purge ntp' and re-install it afterwards.
That guy had the same symptoms I was having.

GoFlexNet:~# ntpq
ntpq>as
ind assid status  conf reach auth condition  last_event cnt
===========================================================
  1 19693  941a   yes   yes  none candidate    sys_peer  1
  2 19694  961a   yes   yes  none  sys.peer    sys_peer  1

querying ntpq with 'as' - whatever that means - showed only: (reach: no) (condition reject) or something similar. (sorry, now that it's working again - I can't post the former results) So it became clear to me that ntpd could not reach any NTP-servers.

after reinstalling ntp I changed only the following lines in /etc/ntp.conf :

server 0.debian.pool.ntp.org iburst
server 1.debian.pool.ntp.org iburst
server 2.debian.pool.ntp.org iburst
server 3.debian.pool.ntp.org iburst

#server 0.debian.pool.ntp.org iburst
#server 1.debian.pool.ntp.org iburst
#server 2.debian.pool.ntp.org iburst
#server 3.debian.pool.ntp.org iburst
server fritz.box
server ptbtime1.ptb.de
server ptbtime2.ptb.de

now it works fine again :)

I did not add the lines

restricted ... fritz.box

(one line per server) at the end of ntp.conf as described in this post

phil

dockstar: update from squeeze to wheezy? (2 replies)

edinger — Wed, 20 Mar 2013 18:05:07 -0400

Hi,

I have installed squeeze on my dockstar and want to update to wheezy without loosing my settings and installed packets.
What do I have to do ? New kernel and then a dist-upgrade?

Kind regards,
Dieter

Dockstar Overheating (3 replies)

okigan — Mon, 08 Apr 2013 03:34:09 -0400

Dockstar overheats when performing long running operations (ex. rsync of large folders).

Is there a way to make it idle/throttle activity?

Thanks,
Igor