Wladston Viana Wrote: ------------------------------------------------------- > Hello, > > Thanks for all the info here guys. > > I got a POGO-P24, with works using the Arch Linux > Pogoplug Pro/Video/v3. > > So after installing alarm I've extracted Varkey's > image to a second USB Flash, changed the Mac > address, and placed on the same USBby bodhi - uBoot
Thanks Dave, it is real! bought one and will see how it goes.by bodhi - Debian
Thanks for the tips Pazos! will try that.by bodhi - Debian
@pazos, That Arch Linux ARM patch does not compile with Debian kernel 3.x at all. The error below occurred if I enable goflex net, or goflex home. arch/arm/mach-kirkwood/goflexnet-setup.c:169:2: error: unknown field 'boot_params' specified in initializer make[2]: *** Error 1 make[1]: *** Error 2 make[1]: Leaving directory `/usr/src/linux-3.2.15' bodhiby bodhi - Debian
lewy1 Wrote: ------------------------------------------------------- > I'm using a flash drive (cruzer), Ext2. Thanks for > the response. Since it's Ext2, you might want to try running e2fsck for this stick on a different Linux box, just in case...by bodhi - uBoot
Davygravy: "Would the solution I'm encouraging be better?" For me it is a resounding YES! I wish I had the technical skills in UBoot area to lend you a hand or take up the challenge :-) Like you said, the U-Boot from ArchLinuxArm is very good and it serves its purpose. But I wish I can use Debian 3.x.x kernel with it.by bodhi - uBoot
Thanks Pazos. I've tried that recent archlinux arm patch before and had some problem compiling (warning about some routine was missing prototype). And I only needs the pogo E02 patch because I already had applied a smaller archlinux arm patch which included all other supports for dockstar and goflex. But thanks for your response! I will try again.by bodhi - Debian
Anybody? is this possible? or do I need to create a different source tree and going through the steps of creating patch?by bodhi - Debian
In that case, you need something like ENV{ID_FS_TYPE}=="exfat", ENV{cmd1}="/bin/mount" ENV{ID_FS_TYPE}!="exfat", ENV{cmd1}="/usr/bin/pmount" ENV{ID_FS_TYPE}=="exfat", ENV{fs1}="exfat-fuse" ENV{ID_FS_TYPE}!="exfat", ENV{fs1}=%E{ID_FS_TYPE}" ACTION=="add", RUN+="%E{cmd1} -t %E{fs1} %E{mode} --noatby bodhi - Debian
Right! sorry about the typo, I meant udevadm. The out put of udevadm shows that ID_FS_TYPE=exfat. So that's what pmount uses in kraqh3d's udev automount rules. How about trying both mount and pmount at the command line to verify : pmount -t exfat /dev/sdb1 /media/mountpoint mount -t exfat /dev/sdb1 /media/mountpoint If they fail, then I think the exfat module is not in theby bodhi - Debian
Gents, Suppose I want to patch my kernel 3.0.26 source with only the patch for the pogoplug E02 that Pazos has attached above. Is that possible? Is there a way to extract the info from that patch file to create a small patch just for pogoplug E02 only? Thanks, bodhiby bodhi - Debian
Please post the output of udevadmin info --query=all --name=/dev/sdxx where sdxx is the drive letter for your exfat drive.by bodhi - Debian
Thanks for the info laprjns!by bodhi - Debian
Chris, If you have installed UBoot and Debian on you Pink Pogoplug V2 with Jeff's script following this instruction: http://jeff.doozan.com/debian/ Then you could reinstall without risking hosing UBoot. Jeff's script detects UBoot version and if it's what the script expects to see, it will skip it. First try to reboot without the stick, see if you get back into Pogo OS. Oby bodhi - Debian
Hi guys, My Pogoplug Pink is currently Linux Debian 3.1.9-kirkwood #1 Mon Jan 16 13:45:21 UTC 2012 armv5tel GNU/Linux I'm trying to compile debian using this source: http://www.kernel.org/pub/linux/kernel/v3.0/linux-3.1.10.tar.bz2 I copied the config file from the current /boot directory to /usr/src/.config /boot/config-3.1.9-kirkwood and did not change anything relatedby bodhi - Debian
Jussi, I don't think it's a problem either. As long as you're certain that the router assigns the same IP addresses for the Dockstar and the Ubuntu desktop every time you boot up then the netconsole set up is OK. The fw_printenvs output looks fine to me also. Since you're new to Linux, perhaps you should go through the full installation for Debian first using a USB sticby bodhi - uBoot
Jussi, sorry I have to ask these basic questions re your netconsole setup. Sometime we just overlook these minor details! - Did you double check your Ubuntu desktop IP that it's really 192.168.1.181? - And also the Dockstar IP 192.168.1.142? Did you set your router to assign this IP to the Dockstar every time it's up?by bodhi - uBoot
Jussi, :-) If you have Ubuntu then just open a terminal, follow the Jeff's instruction above for netconsole. It should be straight forward for Ubuntu. It's on the desktop side. The harder part is setting it up on the Dockstar side. You will have to download the fw_env tools to be able to set it up. If you found it in /usr/sbin then the command should be Pogoplug:~$ /usr/sby bodhi - uBoot
Jussi, It's hard to tell. Usually if you see LED light flashing for a while during boot, and then turns off, it's "likely" that the booting is not a problem, but possibly there is some problem with the rootfs on the USB drive or the drive itself that UBoot does not like. Since you're booting the Pogo stock, you can set up netconsole to observe the booting process and sby bodhi - uBoot
Jussi, Sure, you can boot other other systems on the Dockstar using Jeff's UBoot. I looked the PirateBox instructions, very interesting! If you've done the USB installation for PirateBox, and still can't boot USB, then the next thing to try: At the Pogoplug OS command prompt, do warm reboot (i.e. /sbin/reboot, or shutdown -r now). Usually, if the USB stick's brand is onby bodhi - uBoot
Jussi, Did you use this instruction to install UBoot and Debian Squeeze from Jeff: http://jeff.doozan.com/debian/ If you did not then what system do you have on the USB stick?by bodhi - uBoot
I think that command prompt (Pogoplug:~$) most certainly is the Pogo stock system! Jussi, make sure you are in /tmp directory before downloading.by bodhi - uBoot
Hi Dave, Thank you for all the hard works! is there any plan to automate the installation (similar to Jeff's install_uboot_mtd0.sh)? bodhiby bodhi - uBoot
Actually it's not how you mounted the HDDs, it's because how the drives shared by samba under /media. Samba reports the size of the disk where /media is located, which is a "wrong" size to report. If you share the drives directly (in smb.conf) then they will be shown with the correct size from a remote PC. Look in /etc/init.d/samba/smb.conf to see if /media is the only folderby bodhi - Debian
TJ Wrote: ------------------------------------------------------- > JR just dropped their price for the P21 to 29.00 > with what appears to be free shipping... > J&R Item # PGG POGOP21 | UPC # 850877002245 | > Mfr. Part # POGO-P21 > > The text says "... there are no monthly fees." > http://www.jr.com/pogoplug/pe/PGG_POGOP21/ > > Mine fromby bodhi - Debian
Here is the work around I came up for aumounting HFSplus drive as Read/Write. It seems to work fine. I've only tested by transferring a few small and few large files. So far no problem with Writes. IMPORTANT: it is explicitly stated in the man page for Debian HFSplus package that Write capability is still experimental and unsupported. So my intention is to use the HFSplus formatted driveby bodhi - Debian
Did you capture the log of what was showing on the screen? It would be very helpful to know at which point the error occurred, and when you cancelled the script.by bodhi - Debian
I got it working. Hope this will help others looking for a solution. The real problem here was the WirelessMode. It was set to a default value of 9 (which is mixed g/b/n). My wireless network is n-only. So it was never get attached to the Access Point. Setting it to 6 (n only) got it running. ifconfig ra0 up sleep 3 #iwpriv ra0 set WirelessMode=Managed iwpriv ra0 set AuthMode=WPA2by bodhi - Debian
I've been trying too, without success either! here is my description of the problem (I posted this at the ArchLinux ARM site). Just to summarize my observation here: I finally figured out what might have been the problem, but no idea how to solve it. For some reason, these iwpriv commands were accepted by the driver, but not updated somehow (I have these commands in a script that execuby bodhi - Debian