I gave this a try on a pogoplug following twinclouds tutorial. I also used the oauth2 instructions over on dslreports. I think i successfully compiled Asterisk 14.7.2 and then used the oauth2 script for google voice. When I run asterisk and enter the CLI, it shows me successfully connected to the obi under 'sip show peers'. When I try to dial out I get this error showing up in the CLI:by umd - Off-Topic
>Update: >Note: if you use netconsole, then the IP 192.168.0.xx should be the same one as defined in u-boot env for ipaddr. >-bodhi Makes sense. Would you recommend choosing a static IP somewhere within the DHCP range?by umd - uBoot
Thanks! Good to know. I had a couple plugs that I setup as mjpg streamer security cams for family and I thought I could make a couple sdcards ahead of time with everything setup. They didn't want to boot. Long story short, started with a fresh usb Debian stick and then created sdcard Debian and worked fine. Little more time to install everything over, but it worked. I had mjpg-streamer ruby umd - uBoot
Bodhi, I had the same issue crop up after flashing the newest uboot on a Pogo v4 Mobile. I flashed the envs and it wouldn't allow me to change the ethaddr initially. When I eventually changed it to the correct MAC from withing debian, then booted the device, it didn't receive an IP (the back lights on the ethernet port, only the orange is lit). When it has the default MAC from the flby umd - uBoot
Yep! That was it. When I started looking at what some of those other parameters were, -n stuck out as a culprit. I just kept the -p and eliminated the other variables and it booted right up. Thanks for your help and by the way, nice work on the project.by umd - Rescue System
Hello, I have a pogo v4 that I was going to install this rescue on. I have run into something that is stopping me. I first setup mtdparts to include a kernel and rootfs. Reboot. Verify the mtd looks good then I did this. flash_erase /dev/mtd2 0 0 Erasing 128 Kibyte @ 2e0000 -- 100 % complete nandwrite /dev/mtd2 uImage-kirkwood-pogoplug_v4 and that gives me this: Input file isby umd - Rescue System
bodhi, I just went ahead and made the entire drive a samba drive and used my existing rootfs. Easier that way and the drive will be able to spin down like Dave said. It's funny, when I was trying to get the new drive to boot, one time it actually did boot but I also had my thumb drive with the working rootfs in the 1st usb slot. So the Pogo must have got the necessary initial boot info frby umd - uBoot
bodhi Wrote: ------------------------------------------------------- > daviddyer Wrote: > -------------------------------------------------- > ----- > > Better don't put system on the 4tb drive. It won > 't > > be able to spin down with system on it. > > That's a very good point. But sometimes, taking t > he easy approach (having one parby umd - uBoot
No problem! One last question for you. I have a 4TB external drive. I was looking to create a 4GB boot partition and a second partition for data. I figured out that I need to use parted, but for some reason it is not booting and giving me this error in netconsole: loading uImage ... GPT: first_usable_lba incorrect: 22 > 0 part_get_info_efi: *** ERROR: Invalid GPT *** GUID Partitionby umd - uBoot
bodhi, Ok I think I figured it out. I also have a Pogo E02 that wasn't turned on. For some reason my router was taking the same IP address that was assigned to the E02. So I first booted up the E02 and it took its IP address. Then booted up the Pogoplug Mobile with the MAC on the bottom of the case and now my router assigned it a new IP address and it shows the correct MAC. Wacky and doesby umd - uBoot
Prior to flashing I entered ethaddr: fw_printenv ethaddr Warning: Bad CRC, using default environment. ## Error: "ethaddr" not defined I ignored it since I'd be flashing the envs anyway per the instructions. I flashed the new u-boot successfully changed all the corresponding envs except ethaddr. This time it said, Can't overwrite "ethaddr" I fby umd - uBoot
Bodhi, Yeah, the drive definitely seems finicky. I did try a bunch of different combinations of the bootcmd_uenv with no luck. Not a big deal as I have a very easy workaround with the netconsole. When I eventually buy a new hard drive, I can give that one a try as a boot drive. Thanks.by umd - uBoot
Unfortunately the same issue. I then tried it with sleep 45 and then sleep 60 and still the drive wouldn't boot until a reset. Weird.by umd - uBoot
Ok here you go. I x'd out the ethaddr: PogoE02> printenv printenv arcNumber=3542 bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $loadby umd - uBoot
Bodhi, I managed to get it to boot. In netconsole, I entered: setenv usb_ready_retry 30 usb start Then I tried: PogoE02> boot boot Still wouldn't find it. Then entered: PogoE02> reset reset resetting ... U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:23:43 -0700) Pogo E02 gcc (Debian 4.9.2-10) 4.9.2 GNU ld (GNU Binutils for Debian) 2.25 Hit any key to stop autoby umd - uBoot
The usb drive that it is not recognizing is a Western Digital My Passport 500gb hard drive. It's weird I have a couple of regular thumb drives (Sandisk thumb drive with Debian 4.4 and a Lexar thumb drive with Debian 3.14 and both boot without issue). It is the usb HDD that it is not recognizing. It was the main drive I used on the previous U-Boot without issue. For some reason it's notby umd - uBoot
Unfortunately same thing happens. U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:23:43 -0700) Pogo E02 gcc (Debian 4.9.2-10) 4.9.2 GNU ld (GNU Binutils for Debian) 2.25 Hit any key to stop autoboot: 0 starting USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... EHCI timed out on TD - token=0x80008c80 unable to get device descriptor (error=-1) 2 USB Device(s) found scanniby umd - uBoot
Ok that makes sense. Do you know why I am able to boot from the Debian 3.14 stick, but I can't seem to boot from the hdd with Debian 4.4? I did a new install extracting Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 on a 4gb partition that I created with mke2fs -L ROOTFS -j /dev/sdb1. Powered down and then boot the Pogo with only the hdd attached. The drive light flashes initially but rathby umd - uBoot
I had a usb stick with Debian 3.14 on it. I was able to boot and access through putty like normal. Phew! Still doesn't explain why the Pogoplug booting by itself flashes orange. My Debian 4.9 on the hdd might have to reinstall since I installed it with the step for older U-boots.by umd - uBoot
Ok I did it. When I rebooted back into Debian, I couldn't connect at all with putty. The light was green. I then unplugged it to boot with just the Pogoplug. The light was flashing orange. Here is the netconsole output: U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:23:43 -0700) Pogo E02 gcc (Debian 4.9.2-10) 4.9.2 GNU ld (GNU Binutils for Debian) 2.25 Hit any key to stop autoboot: 0 sby umd - uBoot
Oh ok. That's what I thought. Thanks!by umd - uBoot
When I got this Pogoplug, I followed the Qnology blog to modify the U-Boot. Using netconsole I got version of U-Boot that is currently installed: U-Boot 2011.12 (Feb 20 2012 - 21:21:59) Pogoplug E02 The Pogoplug works fine and I am running the latest Debian from this site on a hdd. Some of the features of the latest U-Boot like using >2TB drives would be nice. So can I do thisby umd - uBoot