Cool! See if you can use the 2nd SATA port by plugging in another SATA disk. I think the sheevaplug patch has 2 SATA ports already, but it's good to confirm it. If you can access it, then perhaps there is no need to update kernel (you will only gain the LEDs control). You can make it a bit better by using an updated kernel with the GoFlex Net archNumber 3089. I've posted one here:by bodhi - Debian
Yes, it is OK to do apt-get upgrade. But as restamp said, should backup your system first. You can also change apt sources list to use wheezy before apt-get upgrade. But prepare for a massive amount of updates! a lot of packages will be kept at older version, because the kernel is still 2.6.x.by bodhi - uBoot
tmm68 Wrote: ------------------------------------------------------- > I took the disk out of the SATA-bay and connected > it to the USB-port. > After the restart, i entered the wheezy system > with succsess. > > A dmesg did not show me the SATA device. At this point, does dmesg show the SATA ports? since you're connecting the HDD to USB adapter, it mounts the diby bodhi - Debian
Hi restamp, Yes, this hobby is addictive :) I'm fortunate that it also helps me in my works. What I think will happen when you boot up with the serial console attached is you will see the uBoot count down, and you can interrupt it. Recently I had to do a somewhat similar hack for a Pogo Mobile. I think chances are the original uBoot on the Pogo E02 will have a count down (even if it isby bodhi - Off-Topic
Very nice :) Thanks for sharing!by bodhi - Debian
shv Wrote: ------------------------------------------------------- > Hello bodhi, > > Your kernel is working fine on Pogoplug E02 and > Pogoplug Series 4, thanks. > > I was not successful with building a working > kernel. I get a .deb file but the kernel doesn't > get access to /dev/root. How can I setup a working > cross toolchain on debian or ubuntu?by bodhi - Debian
beta Wrote: ------------------------------------------------------- > Hi there, > > Think my GFN is finally bricked. > Here is what I did, from scratch: > Main reason to order this device was to build a > SqueezePlug, so I followed the SqueezeboxWiki > instruction > SqueezeBoxWiki. Preparing the USB stick > was easy, the bootloader has been replaced > folby bodhi - Debian
Hi restamp, If you buy it on eBay, you could ask the seller could go to my.pogoplug.com and de-register the device, and then you can register it again. But if the seller does not do that (either unwilling or bought the device from somebody else in the first place) then it's a big hassle. I don't know if you call Pogoplug they will be willing to de-register the device, I'd doubtby bodhi - Off-Topic
@chessplayer, I've suspected that davy's rootfs (Linux version 3.3.2-kirkwide ) does not have E02 support. When I looked at that rootfs config file I did not see Pogoplug E02 or V4. But it was on the Dropbox so I can't be sure. So I guess you can do these: 1. Use netconsole to remove machid (use command setenv machid) so that you're back to old settings. 2. Afterby bodhi - Debian
thespacepope Wrote: ------------------------------------------------------- Quote> 1. Rather than copying over the > /etc/Wireless/RT2860STA/RTA2860STA.dat file, I did > this: > mkdir -p /etc/Wireless/RT2860STA > > then > touch /etc/Wireless/RT2860STA/RT2860STA.dat > I left the file empty, that's right no > values in the file. Cool. I guess there weby bodhi - uBoot
Twinclouds, You can download these tools from Jeff's site: cd /tmp wget http://download.doozan.com/uboot/nanddump wget http://download.doozan.com/uboot/nandwrite wget http://download.doozan.com/uboot/flash_erase wget http://download.doozan.com/uboot/fw_printenv wget http://download.doozan.com/uboot/fw_env.config wget http://download.doozan.com/uboot/files/environment/uboot.enviby bodhi - Debian
Sure, updated 1st post to attach config file.by bodhi - Debian
I don't think the revert will work once Davy's uBoot is installed. It does not hurt to try, though.by bodhi - uBoot
chackoc Wrote: ------------------------------------------------------- > Another thought I had was get a small usb thumb > drive just for swap and consider replacing it from > time to time as an operating cost. At least that > way I don't kill the entire OS if the drive dies > prematurely. Of course it's best to have HDD for swap, but this is a good approach,by bodhi - Debian
Hi chessplayer, The reason is the current uBoot has a glitch that it will ignore arcNumber 3542, and not passing it to the kernel. So we need to also set machid to dd6 using "fw_setenv machid dd6". I've posted it here: http://forum.doozan.com/read.php?2,11601,11637#msg-11637. And I really defer to davygravy for the effort to have a "universal kernel" :) I only wantby bodhi - Debian
chessplayer, you're not really running Pogo E02! it is running as a 2097 reference board. [ 0.000000] Machine: Marvell SheevaPlug Reference Board This is probably because of the machid env was not set to dd6.by bodhi - Debian
Hi chessplayer, There is really no special reason why I'm still on kernel 3.2.x. I tend to upgrade slowly to get the most stable kernel, and still get the latest packages for the OS. IMO, if you run Kirkwood, then you should use Kirwood-patched kernel 3.2.x. or later. This is because of discovery of problem in booting older uBoot with kernel 3.2.x, and also problem with chip timing. Theseby bodhi - Debian
duduke Wrote: ------------------------------------------------------- > bodhi, How can I revert to Arch uBoot if I've > already installed davy's uBoot on my PPV4? You could do it from Linux command line, if you have a saved mtd0 image (saved after you've installed Arch). Be careful to note the size and the mtdparts payout.by bodhi - uBoot
Updated 1st post to attach the patch file.by bodhi - Debian
Hi Twinclouds, Sorry I was a little too vague about the starting point! that was because post was copied from another thread, i.e. context:) I will update it to be a little more elaborate. 1. The goal is to flash this uBoot from Linux environment. Davy's instruction for this uBoot was written to show how he installed it from serial console. See here: http://forum.doozan.com/read.php?3by bodhi - Debian
thespacepope Wrote: ------------------------------------------------------- > I am trying to use the shv rootfs and it seems to > work fine with wired but I am having issues > getting the wireless to work. I followed the > hints in the post he linked over at the > archlinuxarm.org site: I copied over the RT2860 > from the pogoplug side, installed wireless-tools > andby bodhi - uBoot
@shv, I have consolidate patch that I can post here later, so you can try building your own kernel.by bodhi - Debian
Notice: this thread is now obsolete! Please use the new U-boot and Debian rootfs/kernel threads. Background: The installation starting point should be one of these 3 environments: 1. From inside Pogo OS with a brand new, unhacked Pogo Mobile/Series4. SSH into Pogo OS and start from there. 2. From Arch Linux command line. 3. From Debian command line. To install, you must have NANDby bodhi - Debian
Twinclouds, I've documented it here: http://forum.doozan.com/read.php?3,7477,10982#msg-10982 Perhaps it should be on a separate thread.by bodhi - Debian
Perhaps this thread will give you some ideas to get around this problem: http://forum.doozan.com/read.php?3,10966by bodhi - uBoot
bodhi Wrote: ------------------------------------------------------- > > Yes, the 3TB drives tend to cause problem booting. > Is the Ext3 formatted as whole GPT partition? If > it is then it's best to plug it in later, because > even though you don't have rootfs on it, I suspect > it still causes problem because uBoot must have > tried to scan it (current uby bodhi - uBoot
To trouble shoot netconsole problem, boot into the Rescue system, and run fw_printenv Pls post the output here.by bodhi - uBoot
Sure, you can the boot order for any these parts, except reset is independent so it should be last.by bodhi - uBoot