PlugPBX on a Seagate DockStar

[twinclouds]

I installed according to what mattmc97 outlined.  The installation went through without problem.  However, I cannot boot into Debian at all even after unplug and waiting.  It still boot into the original one. 
Another issue is that when I issued command "date", it give me something like "Sat Jan  1 00:01:56 UTC 2000."  It looks like the time server is not working.  Do I need to install a time server first?

[twinclouds]

O.K.  I set the date and time to the correct values.  Now looks like I can log into the Debian installation.  However, I cannot log into it.  The original password "stxadmin" does not work any more and the new password "root" suggested by Jeff does not work either.  Can you tell me which one I should use?

[PlugPBX Admin]

I've run Asterisk/FreePBX on a 128 meg Buffalo LS Pro without issues. This is lots of free space - looks very promising

If you manage to build an SD card image for the DockStar you want released to others to download, I'm happy to host it here for ya. Hell perhaps a flavor of PlugPBX for DockStar can live here if you want! I'm happy to hand out Blog Accounts to key contributors etc etc

Or else startup yer own site, call it DockPBX or some damn thing Har har.

Also of note - guys, feel free to post technical guides etc on the wiki as well, its there for you to use. Installer scripts is a great example of what should be hosted by a wiki.

wiki.plugpbx.org


  -Cheers!

[klingon]

Finally installed Debian and running.  But it has a weird boot procedure!

I have a serial term connected and noticed it kept going into kernel panic which explains why it does not boot all the time.  It appears to not be able to mount the USB drive within the 10 secs.  Logs below.

Stuck boot log :
Waiting 10sec before mounting root device...
usb 1-1.3: device descriptor read/64, error -71
usb 1-1.3: device descriptor read/64, error -71
usb 1-1.3: new high speed USB device using orion-ehci and address 5
usb 1-1.3: device not accepting address 5, error -71
usb 1-1.3: new high speed USB device using orion-ehci and address 6
usb 1-1.3: device not accepting address 6, error -71
hub 1-1:1.0: unable to enumerate USB device on port 3
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "sda1" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00            1024 mtdblock0 (driver?)
1f01            4096 mtdblock1 (driver?)
1f02          257024 mtdblock2 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)

Working boot log :
Waiting 10sec before mounting root device...
scsi 0:0:0:0: Direct-Access     WDC AC31 0200R            0811 PQ: 0 ANSI: 0
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 0:0:0:0: [sda] 20044080 512-byte logical blocks: (10.2 GB/9.55 GiB)
sd 0:0:0:0: [sda] Test WP failed, assume Write Enabled
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] Test WP failed, assume Write Enabled
sd 0:0:0:0: [sda] Assuming drive cache: write through
 sda: sda1 sda2
sd 0:0:0:0: [sda] Test WP failed, assume Write Enabled
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] Attached SCSI disk
VFS: Mounted root (ext2 filesystem) on device 8:1.

I then tried the following sequence of steps and it now boots every time to Debian by using the same steps but definitely not the way to go!!

- Disconnect USB drive and power
- Re-Connect power only - this will boot into pogoplug
- Once you're able to ssh into unit, connect USB drive and wait for 15 secs for it to initialize
- /sbin/reboot

I'm no Debian guru so hopefully someone can make sense from the log.  It looks like setting mounting time > 10 secs may help.

[mattmc97]

Good to know. I have not rebooted mine as I was afraid I could not get back in.

Interesting discussion over on plugapps forums about how to make it go straight into USB boot.

http://plugapps.com/forum/viewtopic.php?f=6&t=92&start=20#p684

I have not tried it because if there is an error, you have to have serial access to fix it. Since YOU have serial access, maybe you can test it for the rest of us. 

Read the whole thread but here is a snippet...

Proposed addition to the Pogoplug/DockStar guide:

After first boot, run the following:

Code: Select all
    pacman -Sy pogoplug-blparam
    echo "blparam 'bootcmd=run bootcmd1'" >> /etc/rc.local



Just as a reminder, we won't add this into the default distro users download since the Pogo and DockStar are the only devices that need this.

I don't know if this would only apply to the pogoplug distribution, but we are using the same bootloader, so I THINK it would work.

BTW, how did you setup SERIAL access?   Did you make a cable?

[klingon]

I was just about to try those settings!!

I built a RS232-TTL cable using some leftover parts.  You can also buy a CA-42 cable (with longish USB end) from Ebay ($4) and snip the phone connector end off and connect to the 3 pins on the Dockstar.

EDIT : Adding that one line - it appears to work somewhat! Cold power plug in boots me into pogoplug, then I have to reboot to get into Debian but at least dont have to plug/unplug!!  Then any warm reboots will need to be done twice to get back into Debian.  First time always boot into pogoplug.

echo "/usr/local/cloudengines/bin/blparam 'bootcmd=run bootcmd1'" >> /etc/rc.local

[mattmc97]

Well, we are getting closer. I thought that was supposed to eliminate having to boot twice. 

Can you tell me how you made your cable please?

I have several Usb -> serial adapters here, but I don't know what it is required after that.

Also, what is the serial output after the change?  Does it fix the problem you were seeing with the timeout?

[twinclouds]

Are the username/password for loging into Debian supposed to be root/root?

[mattmc97]

yes

[klingon]

Well, we are getting closer. I thought that was supposed to eliminate having to boot twice. 

Can you tell me how you made your cable please?

I have several Usb -> serial adapters here, but I don't know what it is required after that.

Also, what is the serial output after the change?  Does it fix the problem you were seeing with the timeout?

You cannot use any regular USB-Serial adapter or you may fry your Dockstar.  Regular RS232 signalling is 12V and USB is 5V but the Dockstar uses 3.3V for signalling.  What you need is a RS232-TTL adapter.  See this post for more info - http://buffalo.nas-central.org/index.php/Use_a_Nokia_Serial_Cable_on_an_ARM9_Linkstation

Now if you have a MAX232 chip and four 1uf caps and good at soldering, schematics at http://sodoityourself.com/max232-serial-level-converter/ else best to get the CA-42 cable from Ebay.  Much easier.

The serial output after the change looks normal.  First boot goes to pogoplug and second boot goes to Debian.  I'm trying to install Asterisk and Freepbx now!!  Hope it works

[mattmc97]

Good to know. I just hope I don't brick it then.

This thing will definitely need to go on a UPS then. A non-techie is not going to be able to SSH into and reboot when the guy who set it up is not around!

[Wheels turning, smoke coming out of head.....]

I read a link where a guy wrote a script that would issue a /sbin/reboot after two minutes.

Maybe I will try to come up with a script, if I do will you try it out since you have serial access?

Basically you would write a script that would go into the PlugOS rc.local that would wait 1-2 minutes, then issue the /sbin/reboot command. That would fix the reboot over SSH issue, while still allowing you to get into the PlugOS thru SSH if you had to, with the two minute window. Not the ideal solution, but better than now.

[jjoshua]

I'm trying to get plugpbx running on my dockstar.  My dockstar uses setboot to boot off of the USB port.

I installed the software onto a 4GB usb drive.  The first time booting, I ran into problems because u-boot expects uImage to be in /boot.  I created a link to /uImage and I can get the device to boot but then it fails trying to mount the root device.

[    1.950000] Waiting 10sec before mounting root device...
[   11.960000] VFS: Cannot open root device "sda1" or unknown-block(0,0)
[   11.960000] Please append a correct "root=" boot option; here are the available partitions:
[   11.970000] 1f00            1024 mtdblock0 (driver?)
[   11.980000] 1f01            4096 mtdblock1 (driver?)
[   11.980000] 1f02          257024 mtdblock2 (driver?)
[   11.990000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

Code:

U-Boot 1.1.4 (Jul 16 2009 - 21:02:16) Cloud Engines (3.4.16)

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 00690D60

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 128MB
DRAM Total size 128MB  16bit width
Flash:  0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:256 MB

CPU : Marvell Feroceon (Rev 1)
CLOUD ENGINES BOARD: REDSTONE:1.0

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0
Saving Environment to NAND...
Erasing Nand...Writing to Nand... done

NAND read: device 0 offset 0x2500000, size 0x40000

Reading data from 0x253f800 -- 100% complete.
 262144 bytes read: OK
## Starting application at 0x00C00000 ...


U-Boot 2009.11-00432-g1650ec9-dirty (Mar 07 2010 - 22:13:20)
PlugApps Pogoplug

SoC:   Kirkwood 88F6281_A0
DRAM:  128 MB
NAND:  256 MiB
Using default environment

In:    serial
Out:   serial
Err:   serial
Net:   egiga0
88E1116 Initialized on egiga0
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 "/boot/uImage" from usb device 0:1 (usbda1)
1811960 bytes read
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Debian kernel
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1811896 Bytes =  1.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 2.6.30-2-kirkwood (Debian 2.6.30-8) (waldi@debian.org) (gcc version 4.3.4 (Debian 4.3.4-3) ) #1 Sun Sep 27 22:57:55 UTC 2009
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053177
[    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] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda1 rootdelay=10 rootfstype=ext2
[    0.000000] NR_IRQS:114
[    0.000000] PID hash table entries: 512 (order: 9, 2048 bytes)
[    0.000000] Console: colour dummy device 80x30
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Memory: 128MB = 128MB total
[    0.000000] Memory: 125780KB available (3232K code, 548K data, 120K init, 0K highmem)
[    0.000000] Calibrating delay loop... 1192.75 BogoMIPS (lpj=5963776)
[    0.240000] Security Framework initialized
[    0.240000] SELinux:  Disabled at boot.
[    0.240000] Mount-cache hash table entries: 512
[    0.240000] Initializing cgroup subsys ns
[    0.240000] Initializing cgroup subsys cpuacct
[    0.240000] Initializing cgroup subsys devices
[    0.240000] Initializing cgroup subsys freezer
[    0.240000] Initializing cgroup subsys net_cls
[    0.240000] CPU: Testing write buffer coherency: ok
[    0.240000] net_namespace: 1076 bytes
[    0.240000] regulator: core version 0.5
[    0.240000] NET: Registered protocol family 16
[    0.240000] Kirkwood: MV88F6281-A0, TCLK=200000000.
[    0.240000] Feroceon L2: Cache support initialised.
[    0.250000] bio: create slab <bio-0> at 0
[    0.250000] NET: Registered protocol family 2
[    0.250000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.250000] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
[    0.250000] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[    0.250000] TCP: Hash tables configured (established 4096 bind 4096)
[    0.250000] TCP reno registered
[    0.250000] NET: Registered protocol family 1
[    0.250000] NetWinder Floating Point Emulator V0.97 (double precision)
[    0.250000] audit: initializing netlink socket (disabled)
[    0.250000] type=2000 audit(0.250:1): initialized
[    0.250000] VFS: Disk quotas dquot_6.5.2
[    0.250000] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.250000] JFFS2 version 2.2. (NAND) (SUMMARY)  Â© 2001-2006 Red Hat, Inc.
[    0.250000] msgmni has been set to 245
[    0.250000] alg: No test for stdrng (krng)
[    0.250000] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[    0.250000] io scheduler noop registered
[    0.250000] io scheduler anticipatory registered
[    0.250000] io scheduler deadline registered
[    0.250000] io scheduler cfq registered (default)
[    0.260000] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    0.260000] serial8250.0: ttyS0 at MMIO 0xf1012000 (irq = 33) is a 16550A
[    0.260000] console [ttyS0] enabled
[    0.570000] brd: module loaded
[    0.570000] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit)
[    0.580000] Scanning device for bad blocks
[    0.620000] Bad eraseblock 935 at 0x0000074e0000
[    0.660000] Bad eraseblock 1736 at 0x00000d900000
[    0.680000] Creating 3 MTD partitions on "orion_nand":
[    0.680000] 0x000000000000-0x000000100000 : "u-boot"
[    0.690000] uncorrectable error : <5>0x000000100000-0x000000500000 : "uImage"
[    0.700000] ftl_cs: FTL header not found.
[    0.700000] 0x000000500000-0x000010000000 : "root"
[    0.710000] ftl_cs: FTL header not found.
[    0.710000] mice: PS/2 mouse device common for all mice
[    1.730000] rtc-mv rtc-mv: internal RTC not ticking
[    1.730000] i2c /dev entries driver
[    1.730000] cpuidle: using governor ladder
[    1.740000] cpuidle: using governor menu
[    1.740000] Registered led device: plug:green:health
[    1.750000] mv_xor_shared mv_xor_shared.0: Marvell shared XOR driver
[    1.750000] mv_xor_shared mv_xor_shared.1: Marvell shared XOR driver
[    1.800000] mv_xor mv_xor.0: Marvell XOR: ( xor cpy )
[    1.840000] mv_xor mv_xor.1: Marvell XOR: ( xor fill cpy )
[    1.880000] mv_xor mv_xor.2: Marvell XOR: ( xor cpy )
[    1.920000] mv_xor mv_xor.3: Marvell XOR: ( xor fill cpy )
[    1.920000] TCP cubic registered
[    1.930000] NET: Registered protocol family 17
[    1.930000] registered taskstats version 1
[    1.930000] /build/buildd-linux-2.6_2.6.30-8-armel-esZiGi/linux-2.6-2.6.30/debian/build/source_armel_none/drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
[    1.950000] Waiting 10sec before mounting root device...
[   11.960000] VFS: Cannot open root device "sda1" or unknown-block(0,0)
[   11.960000] Please append a correct "root=" boot option; here are the available partitions:
[   11.970000] 1f00            1024 mtdblock0 (driver?)
[   11.980000] 1f01            4096 mtdblock1 (driver?)
[   11.980000] 1f02          257024 mtdblock2 (driver?)
[   11.990000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[   11.990000] [<c002cd68>] (unwind_backtrace+0x0/0xdc) from [<c0287000>] (panic+0x34/0x120)
[   12.000000] [<c0287000>] (panic+0x34/0x120) from [<c0008ebc>] (mount_block_root+0x25c/0x2b4)
[   12.010000] [<c0008ebc>] (mount_block_root+0x25c/0x2b4) from [<c00090e4>] (prepare_namespace+0x164/0x1c8)
[   12.020000] [<c00090e4>] (prepare_namespace+0x164/0x1c8) from [<c0008410>] (kernel_init+0xc0/0xf0)
[   12.030000] [<c0008410>] (kernel_init+0xc0/0xf0) from [<c0043000>] (do_exit+0x0/0x640)
[   12.040000] [<c0043000>] (do_exit+0x0/0x640) from [<c7814780>] (0xc7814780)

[mattmc97]

Read this post by klingon above...

http://forums.plugpbx.org/index.php?topic=97.msg555#msg555

He outlines steps on how he got it to boot. It looks like you error message is similar to his.

Also, you can try this...

EDIT : Adding that one line - it appears to work somewhat! Cold power plug in boots me into pogoplug, then I have to reboot to get into Debian but at least dont have to plug/unplug!!  Then any warm reboots will need to be done twice to get back into Debian.  First time always boot into pogoplug.

echo "/usr/local/cloudengines/bin/blparam 'bootcmd=run bootcmd1'" >> /etc/rc.local

Also, did you use Jeff Doozan's guide? That is what the two of us used that got debian working.

[PlugPBX Admin]

FYI, I posted this on the website to help direct traffic to the ongoing forum on DockStar fun!

http://www.plugpbx.org/?p=406

[lowkey]

Just finished installing. I left mine with the toggle boot intact, ie boot into original image, reboot into debian, reboot original image etc. One thing I did have to do for it to boot debian is to set the boot flag with fdisk:

/sbin/fdisk /dev/sda
a (then select 1)
w
/sbin/reboot