 | [Other] Asterisk/openwrt on Seagate DockstarI am happy to report that asterisk is working on the Seagate Dockstar. I have tested the following: •Register on Sipgate •Route incoming call to a local extension I have no audio problems, although I had to set to get around one-way audio problems.
Remaining Issue(s): Dockstar always alternates between cloud-os and openwrt
Separated asterisk status from the Freeswitch on dockstar topic. See mazilo's posts on how to install openwrt on dockstar here.
-m |
|
|
|
 jjoshuaPremium join:2001-06-01 Scotch Plains, NJ kudos:1 | May you post your .config and config-default files. |
|
 | said by jjoshua:May you post your .config and config-default files. I customized the kernel with AFAIK the changes are not saved in config-default, rather they are in
build_dir/kirkwood/linux-2.6.30.10/.config
Having said that, I also made changes to the config-default. I am attaching all three config files. Hope it helps.
-m |
|
 | reply to voip_wire said by voip_wire:Remaining Issue(s): • Dockstar always alternates between cloud-os and openwrt This may fix the issue - »plugapps.com/forum/viewtopic.php···=20#p684 |
|
 maziloFrom MaziloPremium join:2002-05-30 Lilburn, GA kudos:1 | reply to voip_wire Excellent. At least, those who are familiar with Asterisk and have bought some Seagate DockStar devices can now let their device to host their Asterisk PBX system. Congrats! -- don't and stop are the ONLY two 4-letter words considered offensive to men, but not when used together. |
|
 jeffmlPremium join:2002-01-01 Apo, AE Reviews:
·Anveo
| reply to voip_wire Mazilo, First off thanks for the tip about the Dockstar. I've received my first one and have everything up and running.
Just one question. Why do you build the applications into the firmware versus using the openwrt distribution method:
opkg update
opkg install <application>
Are you applying patches to freeswitch and such that isn't provided in the package manager? |
|
 usa2kBlessedPremium,MVM join:2003-01-26 Canton, MI kudos:3 | reply to voip_wire Nice work!  |
|
 1 edit | reply to davidm00
I have already tested that approach and found that it does not work. See here. Once I am comfortable with my install, I will probably move it to on-board flash.
Mazilo & usa2k, Thanks.
Jeffml, For the to work, the packages have to be compiled first. I am not sure if there is an existing repository of packages compiled for kirkwood platform. Mixing different svn revisions of Openwrt may also lead to inconsistencies or issues. Finally, as we are installing it on a usb flash drive, there is no difference in compiling packages in, or installing them after the fact. We don't have to worry about squashfs versus jffs utlization.
At least that's my perspective, mazilo may have other reasons beyond this.
-m |
|
 maziloFrom MaziloPremium join:2002-05-30 Lilburn, GA kudos:1 | said by voip_wire:For the to work, the packages have to be compiled first. I am not sure if there is an existing repository of packages compiled for kirkwood platform. Mixing different svn revisions of Openwrt may also lead to inconsistencies or issues. Finally, as we are installing it on a usb flash drive, there is no difference in compiling packages in, or installing them after the fact. We don't have to worry about squashfs versus jffs utlization. At least that's my perspective, mazilo may have other reasons beyond this. Thank you for taking time to clarify the above and that's what I had in mind too. We all need to remember that the OpenWRT firmware I uploaded as shown on this post was compiled from OpenWRT SVN Development branch, i.e. not a released version, that may not be stable.
If one is concerned with a stability issue, then perhaps the released (Backfire) version provided by OpenWRT for a Marvell Kirkwood platform, i.e. a Seagate DockStar, etc., as seen here is a better option. AFAIK, the released (Backfire) version has all kernel drivers, i.e. USB, USB_storage, SCSI disk, etc., built as kernel modules. Since the new u-boot manager installed on the mtd3 partition (NAND space) of your Seagate DockStar device (after applying the PogoPlug SetBoot step-by-step instructions) has a support for an EXT2 filesystem (IIRC), perhaps the external USB partition may need be formatted with an EXT2 filesystem will work. Let's know what the outcome if you go with this route.
-- don't and stop are the ONLY two 4-letter words considered offensive to men, but not when used together. |
|
 jeffmlPremium join:2002-01-01 Apo, AE Reviews:
·Anveo
| reply to voip_wire said by voip_wire: to work, the packages have to be compiled first. I am not sure if there is an existing repository of packages compiled for kirkwood platform Ok. The first thing I did was update and pulled down packages (including asterisk) and they worked great (minimal testing). Freeswitch is also in there. I now understand why Mazilo decided to go his route. I might make a few minimalist builds (with patches) of the current stable version go from there.
Mazilo, Were there specific reasons you chose the development branch verus the stable. I don't want to miss any kirkwood patches that are needed.
-- Jeff |
|
 maziloFrom MaziloPremium join:2002-05-30 Lilburn, GA kudos:1 | said by jeffml:The first thing I did was update and pulled down packages (including asterisk) and they worked great (minimal testing). Freeswitch is also in there. If your device runs on a Backfire version, you can use opkg to remotely install the packages you want (no need to first download and install). If you just execute opkg on a login shell, it will print out all switches/parameters that it supports.
Were there specific reasons you chose the development branch verus the stable. Honestly, I don't know how to tell you. Perhaps, this will explain better. Some early adopters who didn't mind paying a hefty of dollars prefer to camp overnights in a long-line sidewalk for a new Apple iPhone 4 when it was on a sale debut. I do the same thing through GPLed software to test what new additional features and/or enhancements (or even bugs) are out there. -- don't and stop are the ONLY two 4-letter words considered offensive to men, but not when used together. |
|
 | reply to voip_wire said by voip_wire:I have already tested that approach and found that it does not work. See here. Once I am comfortable with my install, I will probably move it to on-board flash. Oops, forgot you were on Openwrt! I'm also following a thread on installing Debian on this unit. With Debian, shld hopefully be able to continue with the work done by PlugPbx (also on Debian) on this unit and have Asterisk/Freepbx running. This is a better route for me as I'm hoping to also get some of PIAF's stuffs installed once I get it up and running.
If anyone is interested in installing Debian - »jeff.doozan.com/debian/ |
|
 MartyT join:2004-09-03 Georgetown, SC | reply to voip_wire I was checking the prices of Dockstars on eBay last night (I already have two from the $25 deal that are waiting to be put into service) and actually saw someone selling a Dockstar with a preconfigured version of Asterisk on it.
The unique part was that it was designed to allow you to setup a Google Voice system with a Sipgate One number. It was being sold with the promise of free telephone service. Very interesting! |
|
 jjoshuaPremium join:2001-06-01 Scotch Plains, NJ kudos:1 | reply to voip_wire FYI. I'm trying to get plugpbx running on the dockstar. I managed to get the unit to boot but it runs into some problems. My dockstar is running setboot.
[ 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)
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)
|
|
 maziloFrom MaziloPremium join:2002-05-30 Lilburn, GA kudos:1 | said by jjoshua:[ 11.990000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) What filesystem did you format on your partition used for plugpbx software? -- don't and stop are the ONLY two 4-letter words considered offensive to men, but not when used together. |
|
 jjoshuaPremium join:2001-06-01 Scotch Plains, NJ kudos:1 | I didn't create any partitions - I just dd'd the image onto the USB. It creates 2 partitions which are mountable and readable. |
|
 usa2kBlessedPremium,MVM join:2003-01-26 Canton, MI kudos:3 | FWIW, dd didn't work for me. I had to use tar to get it working. |
|
 maziloFrom MaziloPremium join:2002-05-30 Lilburn, GA kudos:1 | reply to jjoshua said by jjoshua:I didn't create any partitions - I just dd'd the image onto the USB. It creates 2 partitions which are mountable and readable. I did this approach too and it didn't work for me neither. -- don't and stop are the ONLY two 4-letter words considered offensive to men, but not when used together. |
|
 | reply to jjoshua
said by jjoshua:FYI. I'm trying to get plugpbx running on the dockstar. I managed to get the unit to boot but it runs into some problems. My dockstar is running setboot. [ 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?)
It appears the kernel does not have USB support compiled in. Could you try replacing /boot/uImage with this one? You will have to rename it to uImage for uBoot to find it. -m |
|
 jjoshuaPremium join:2001-06-01 Scotch Plains, NJ kudos:1 | reply to usa2k said by usa2k:FWIW, dd didn't work for me. I had to use tar to get it working. So you did get it to work? How? |
|