restamp Wrote: ------------------------------------------------------- > About two weeks ago, my Asterisk implementation > used to interface to Google Voice (Asterisk server > 1.8.9.2, built as described in this forum) started > leaving me high-and-dry (would place calls, but > I'd never get a ring tone) the first thing every > morning. Waiting about 20 minutes afteby twinclouds - Debian
optim Wrote: ------------------------------------------------------- > I was not able to get any version to work for > incoming calls via google voice. I believe I had > one successful incoming call ever. > > Maybe I will try again with a clean slate of > config files and only change my login and > password. I don't have much problem with incoming call evenby twinclouds - Debian
syong Wrote: ------------------------------------------------------- > That is the link. But they used to ship the > mk802ii like this: > > http://rickyzhang.dyndns.org/blog/wp-content/uploa > ds/2012/12/photo.jpg Did you bought the MK802 II from the same link? Mine shows "Mini TV for Android, Dualcore A9 Processor" on case. What is the device model showing inby twinclouds - Allwinner A10
syong Wrote: ------------------------------------------------------- > The ``faked'' mk802ii with 8188eu wireless is THE > BEST according to my experience. Which one? Can you let me know? I bought one MK802II from IT Specialties on Amazon http://www.amazon.com/gp/product/B0091UHMHO/ref=oh_details_o02_s00_i00?ie=UTF8&psc=1. It turned out to be an Google mini TV (MK808)by twinclouds - Allwinner A10
I tried to experiment with A10 based device. Bought twice from Amazon.com of those specifically stated as MK802/Allwinner A10, etc. However, none of these works with rescue/LUbuntu. Both of them are fake ones from iPazzPort. I am just wondering if there are any reasonably priced ($30-40) MK802 (real or true compatible) on the market that will work as we discussed in the forum?by twinclouds - Allwinner A10
I try to buy and MK802 on Amazon. However, instead I received a "Mini TV for android, Dual-Core A9 Processor", covered by a label "Mini Android PC. The device information shows it is an MK808 with Android 4.1. I found there is a step by step instruction to install Picuntu Linux. Just wondering if anybody have tried this one yet? One question I have is if I follow the instructioby twinclouds - Allwinner A10
Yes. I agree. If it is a rootfs image that can be used in Pogo-4/Mobile, it will be useful for others. I can generate another one but if you already have it for uploading, please just do so.by twinclouds - Debian
@t3ch42. I went through the same process just a couple of weeks ago on my Pogoplug Mobile. I think it should be the same as the series 4. With the help from Bodhi and others, I eventually succeeded. You can read the thread that Bodhi mentioned and should have all the information that you need. The only issue I had was that I still need a rootfs to start with but cannot do direct installationby twinclouds - Debian
@michapixel: Do have a backup copy of the previous working USB for device a? If you do, just plug it in. Does it still work? I don't see how upgrade and restarting, even incorrectly, will brick your device. If you don't have one, you probably should in the first place. I think using JTAG is over kill. If you have access to the serial port, I think using UART booting is probably aby twinclouds - Debian
Yes. It does look like an antenna. The Pogo Mobile mainboard is very similar in this portion. How, I cannot find if the Marvell 88f6 chip has wifi built in. It has a miniport wifi interface pin but I don't see the miniport board in the Pogo Mobile.by twinclouds - Debian
I meant that the title says: "... Wireless Backup...". I thought it is wifi. Maybe I misunderstood. BTW, I check the both sides of the board, I can't find anything remotely like a rt2870 wifi chip. Maybe it cannot do wifi after all.by twinclouds - Debian
Will this rescue system work on Pogoplug Mobile? or we do have one for it?by twinclouds - Rescue System
Will this rescue system work on Pogoplug Mobile? or we do have one for it? (Not sure if this is the right place, so I posted it on another thread also.)by twinclouds - Rescue System
bodhi Wrote: ------------------------------------------------------- > I think there must be a wireless chip built in, > but disable somehow. The hard part is to find out > how to enable it. I think you are right. However, even if we can enable it, it still need the RF frontend to receive and transmit. If the RF frontend is not built in already, it will not work if we can enable tby twinclouds - Debian
Just found one more thing, the swap space is not enabled for SD card boot. To enable it, you will need to edit the /etc/fstab and replace the line /dev/sda2 none swap sw 0 0 with /dev/mmcblk0p2 none swap sw 0 0 or add it if not exist. It will be important considering the small ram space available for Pogoplug Mobile.by twinclouds - Debian
chessplayer Wrote: ------------------------------------------------------- > It is: > > > ┌──[~] > └──> lsmod | grep rt2 > rt2800usb 11906 0 > rt2x00usb 7590 1 rt2800usb > rt2800lib 39393 1 rt2800usb > rt2x00lib 30207 3 > rt2800lib,rt2x00usb,rt2800usb > mac80211 170by twinclouds - Debian
No. I didn't looked the board that carefully either. Somehow, I remember J&R advertised it has the wireless capability when I bought it. I got the same dmesg results as bodhi from the original Pogo firmware but I don't see rt2870 in the Wheezy installation. Not sure why. I found this link. It might give some hints.by twinclouds - Debian
With the help from Bodhi, ChessPlayer and others, I installed Wheezy on the Pogo Mobile and it can boot from either the USB port or the SD card. However, even though the device includes a rt2870STA wifi chip, Debian cannot really use it. Modprobe rt2870 or rt2870STA cannot find anything. Does anybody know how to enable the wifi function for Pogo Mobile? Please share if you can. Thanks.by twinclouds - Debian
Indeed, it works for me! However, in my case, the machid is F78 for Pogo Mobile. Now next step is to make the wifi work. Any references/suggestions?*by twinclouds - Debian
I see. It is written in flash by doing mkimage stuff. I rebooted with out change the arcNumber (still 2097) and it boots with no complaint. Now what I supposed to do to trigger the leds? I tried "echo default-on >/sys/class/leds/status\:green\:health/trigger" on the login terminal window but got: "-bash: /sys/class/leds/status:blue:health/trigger: No such file or directory&qby twinclouds - Debian
But what does "not writing it to flash" mean?by twinclouds - Debian
Still didn't work after I generated new /boot/uImage and /boot/uInitrd. I got the following output: root@debian:/# dpkg -i linux-image-3.2.28-kirkwood-tld_11.0_armel.deb (Reading database ... 12660 files and directories currently installed.) Preparing to replace linux-image-3.2.28-kirkwood-tld 11.0 (using linux-image-3.2.28-kirkwood-tld_11.0_armel.deb) ... Examining /etc/kernel/preby twinclouds - Debian
bodhi Wrote: ------------------------------------------------------- > Great! > > If you can boot with the Dockstar USB, then your > arcNumber is set at 2097. To be able to control > the LEDs correctly, you'll need a kernel that > supports arch number 3960 (and machid F78). See > here: http://forum.doozan.com/read.php?2,11601. > > Once you have the apprby twinclouds - Debian
O.K. Eventually, I made it work after I modified the envs given by dhead666 in here: http://archlinuxarm.org/forum/viewtopic.php?f=18&t=4987! Specifically, I added some envs related to mmc and changed mmc_bootcmd according dhead666 by doing the following: fw_setenv mmc_root /dev/mmcblk0p1 fw_setenv mmc_set_bootargs 'setenv bootargs console=$console root=$mmc_root' fw_setenvby twinclouds - Debian
bodhi Wrote: ------------------------------------------------------- > Let's see your output of fw_printenv! Here it is the fw_printenv output: Again, I don't these are needed anymore.by twinclouds - Debian
I generated a new wheezy installation on Dockstar and then used on Pogo Mobile. The serial interface works fine now. I will try to see if it will work on SD card and let you guys know. Thank you all for your help. I tried the SD card boot. It still didn't work. This is what I tried. First, I use a microSD card in a USB adapter and put the wheezy rootfs on it. I plugged USB adapterby twinclouds - Debian
Chessplayer: Yes, it was the serial connection. As for what you suggested, I did that already but no joy. What happened was that, after some short time, the output stopped. I hit the return and no response. If I disconnect and then connect, there's no responce anyway. The funny thing is it only happen for pogo mobile. Connecting to Dockstar and anything else, e.g., TP-Link routers, usby twinclouds - Debian
Bodhi: The USB always booted fine. However, I cannot make the SD card work. I tried to use serial console to see what's things going on, then I found that at some stage of booting, the output become random characters. It then stoped somewhere and hit return didn't do anything. I tried the good booting USB, the results were the same (random ouput) even though it still worked. I triby twinclouds - Debian
Bodhi: Good suggestions. Thanks. I have USBs that can boot into Dockstar. Will that work? Edit: Yes, it does. I plugged in a Dockstar USB and it booted fine. Thank you and others for your patiant guidance. The LED doesn't light. Any information on the LED setting?by twinclouds - Debian
Bodhi: Everything seems installed without error. A couple more questions: (1) If I want still boot the default pogo linux or Arch Linux, do I need to set "# fw_setenv arcNumber 3960 # fw_setenv machid F78" as you said in previous post? (2) Which script should I use to install Debian on USB drive or SD/MMC card? Thanks.by twinclouds - Debian