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
@Rat, Sorry, Off Topic for a moment, did you get the heartbeat implemented in the later kernel version? some kernel version (e.g. 3.x.x) does not generate the delay on/off trigger. I hope the heartbeat LED is going to be put back, I surely miss it :-) Here is the old thread, in case you want to revisit it: http://forum.doozan.com/read.php?2,3521,3545#msg-3545 Thanksby bodhi - Debian
I've updated the first post to pull all information together and clean up the installation steps.by bodhi - uBoot
Vlad posted about iConnect: http://forum.doozan.com/read.php?2,6624,7041#msg-7041by bodhi - Debian
kraqh3d, I thought you might find this problem interesting and could give me some help. I've changed the automount rules to do these: - async/sync (we took care of this) - mount Mac OSX HFS+ partitions as read/write and ignore the EFI boot partition on those HFS+ drives. The part that I can't make it work is forcing the HFS+ partition to be mounted as read-write, using pmount.by bodhi - Debian
Suggestion: I would try to remove the HDD from fstab and mount it manually later to see what'll happen (keep the Colby attached). If that solve the problem then it will be easier to figure out what was causing the behavior. The worst case, you can automate the HDD mounting in rc.local. I have a GoFlex Net that boots from USB flash, and no fstab entry for any HDD, so I mount whatever HDDby bodhi - Debian
Funtoy, Looks like the net console output was when you put the boot USB drive on the top port (with the adapter)? and it did boot the kernel. How long did you wait after that? I would wait at least 5 minutes! to see if the kernel eventually finishes coming up. I ran into a weird problem that a warm boot took 5 minutes, and the extra 4 minutes was after rc.local has been completed. Addendumby bodhi - Debian
I think the USB hub counts as devices? The Dockstar has 1 root hub and 1 4-port hub. So that would make the total 6. And you have 2 storage devices, which would be the only candidates in the booting sequence.by bodhi - Debian
skyrail Wrote: ------------------------------------------------------- > I got kernel 3.9 ready (still squeeze) at boot, > and check some common commands with success. You probably forgot to change apt sources list? Starting from Debian squeeze, change sources list to wheezy first. I have only one line in my apt sources: # cat /etc/apt/sources.list deb http://ftp.us.debian.org/dby bodhi - Debian
In this thread, these 2 posts have the links to kernel packages that can be installed using dpkg. Also, it has been pointed out that if flash-kernel was installed before the upgrade, then uImage and uInitrd will be automatically created. Kernel package 3.1.0 (archive) http://forum.doozan.com/read.php?2,5746,7124#msg-7124 Kernel package 3.1.9 (built by davygravy) http://forum.doozan.com/reby bodhi - Debian
What was the version after you did the apt-get dist-upgrade ? if it is 3.2.x then it won't boot: http://forum.doozan.com/read.php?3,6965by bodhi - Debian
Thanks Dpffan!by bodhi - Debian
Does anybody know if the patch for GoFlex Net and GoFlex Home have been incorporated in the main line? i.e. Debian 3.x.x?by bodhi - Debian
I think it's probably because the HDD is coming up faster than the flash drive. The Pogoplug USB port right next to the Ethernet port usually assigned SDA, if no HDD drive attached. But it's really unpredictable. Unlike the Dockstar, where the top mini USB port always assigned SDA if there is a drive attached, regardless of the type.by bodhi - Debian
Same here! I've been using an old Sparc-based NAS box for the same purpose for awhile. But these days, I've acquired a few pogoplug/dockstar boxes to do all the chores. Considering the cost and how little power usage go into the 24/7 operation and the capabilities, I think it is amazing we can do that. My goal is to run the same Debian USB stick on all these ARM devices, so when one faiby bodhi - Debian
@davy, Would it also work for the Pogo V4 series? that would be great!by bodhi - uBoot
@restamp, I think a clean solution (kraqh3d's) is to modify UBoot envs to force UBoot to find the correct boot drive (i.e. the first USB drive that has a unique label, for example,rootfs). See this post: http://forum.doozan.com/read.php?2,5233,5957#msg-5957 bodhiby bodhi - Debian
davygravy Wrote: ------------------------------------------------------- > Yes, and it should be a pretty transparent drop-in > replacement. > > It will boot older kernels, newer kernels, and in > case there is no USB rootfs detected, it will then > try to boot whatever rootfs that it can find in > NAND (pogoplug software or the rescue system). Awesome! I canby bodhi - uBoot
I'm not sure I have what you're looking for (my Pogoplug Pink E02 is still a basic plug, using older kernel). But in case it's helpful, here is the info: 1) root@PogoPink1:~# dmesg | egrep '(Machine:)|( NAND )|(Memory)|(Feroceon L2:)|( Linux version )' [ 0.000000] Linux version 2.6.32-5-kirkwood (Debian 2.6.32-30) (ben@decadent.org.uk) (gcc version 4.3.5 (Debian 4by bodhi - Debian
Is there anybody running wheezy kernel having these error messages from fdisk? My Google searches turned up several similar reports from way back (months ago) with different kernel versions, but nobody had an explanation for it! I'm wondering if this is just a bug in fdisk reporting? On top of 3.1.9, I've have installed flash-kernel package, and run "apt-get update" and &quby bodhi - Debian
Cool! I'm glad you did not give up because of those bad blocks. I think they have been emptying inventory, hence we have lot of pogo plugs with bad blocks show up lately :-) And you're right about the installation steps. I will try to edit the first post to annotate with appropriate information. The level of details is OK, I think.by bodhi - uBoot
1. We have to use WarheadsSE kernel for OXNAS on the PogoPro (armV6), so we must instal Arch using his installation procedure first. 2. Or you can use varkey rootfs. It should work: http://www.varkey.in/2011/06/boot-debian-from-sata-seagate-goflex-net/ 3. After you've installed ArchLinux ARM, your UBoot has been updated to boot the ArchLinux ARM kernel. So just need to mount the Debiby bodhi - uBoot
Every thing seems to be OK running kernel 3.1.9. Then I ran "fdisk -l" to check for before mounting another USB thumb drive. I got the following errors: root@Ds1:~# fdisk -l Disk /dev/mtdblock0: 1 MB, 1048576 bytes 255 heads, 63 sectors/track, 0 cylinders, total 2048 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O sizeby bodhi - Debian