Hi guys, to have support for both SATA disks, all you have to do is more or less replicate the "env code" for USB for the situation of the two disks, where you have to keep in mind that the disks are called "ide". You can find the relevant part in this post of mine, but I will repeat it here for convenience (however, beware that this is for using a separate boot partition bby chessplayer - Debian
bodhi Wrote: ------------------------------------------------------- ... snip ... > > Yes, commenting out "/etc/init.d/hbmgr.sh start" > in '/etc/init.d/rcS" is a common mistake for those > of us who have been familiar with the Dockstar > procedure (we do that and it works fine). What we > should do here is to just kill Pogoplug processes > everyby chessplayer - Debian
bodhi Wrote: ------------------------------------------------------- > @chessplayer, ... snip ... > with rootfs label for / , you can make it > consistent, too. ... snip ... > > -bodhi You are, of course, absolutely right. That is what the labels are for. I wasn't thinking straight before. Cheers, chessplayerby chessplayer - Debian
Regarding the two partitions, I wrote that up in this post for a USB-Stick. Concerning my uBoot environment for this setup, you can find that here. However, if you want boot and rootfs on separate devices, that is going to be tough, I think, since you probably cannot be sure about which gets the "a", which the "b" and so on. Cheers, chessplayerby chessplayer - Debian
Hi everyone, while trying to fool around with the LEDs on my POGO E02, I stumbled upon a blog post by Obihörnchen and had a look at paragraph 13: "Enable color in Bash prompt". ---> WOW, I thought, this really does look nice. But why should the Archlinux guys have all the fun? So the next thing I did was google for debian ASCII art in order to replace the (amazing) ALARM logo,by chessplayer - Debian
Just a quick thank you for this kernel package. Putting lincomatic's toggle into /etc/rc.local now gives me a green LED after boot. Nice, the dockstar feeling on a pink plug ...by chessplayer - Debian
shv Wrote: ------------------------------------------------------- ... snip > > With the kernel of the rescue system and > arcNumber/machid set to 3542/dd6 the LED is > controled. The color is green if it is switched > on. The same behaviour I have with bodhys kernel > 3.2.28. With 3.3.2 kernel and arcNumber/machid set > to 2097/831 this LED seam to be controled asby chessplayer - Debian
bodhi Wrote: ------------------------------------------------------- > @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. > Thanks, bodhi, I will consider tby chessplayer - Debian
Ok, so I took bodhi's advice and set the machid using the rescue system. With rescue, the answers to the questions are now as follows: 1: e02-rescue:~# dmesg | egrep '(Machine:)|( NAND )|(Memory)|(Feroceon L2:)|( Linux version )' [ 0.000000] Linux version 3.3.2-kirkwide (davygravy@bitbaker64) (gcc version 4.3.5 (Buildroot 2010.08) ) #1 Mon Oct 29 17:52:07 CDT 2012 [by chessplayer - Debian
bodhi Wrote: ------------------------------------------------------- > 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. Hi bodhi, I'm sorry, but you lost me hereby chessplayer - Debian
And here are my 2 cents worth: 1: [ 0.000000] Linux version 3.3.2-kirkwood-dg (davygravy@bitbaker64) (gcc version 4.6.1 (Sourcery CodeBench Lite 2011.09-70) ) #1 Mon Apr 23 17:09:27 CDT 2012 [ 0.000000] Machine: Marvell SheevaPlug Reference Board [ 0.000000] Memory policy: ECC disabled, Data cache writeback [ 0.000000] Memory: 256MB = 256MB total [ 0.000000] Memory: 247748kby chessplayer - Debian
Hi bodhi, without having tried your kernel (though I might still do that): is there a reason you go for 3.2.x instead of 3.3.x like, e.g., davygravy or shyd did? I know, their solution was for Dockstar (and GoFlex, Zyxel), but still, for a kernel illiterate like me, the question remains ...by chessplayer - Debian
shv Wrote: ------------------------------------------------------- > > @chessplayer: Did you set the arcNumber to 2097 or > 3542 or something else? I just booted it up to check (currently, I am collecting and I hope to put all these to use at some point ...): arcNumber is 3542. I am using a separate boot partition. As I said, LED support is sub-optimal: during boot, nothing at alby chessplayer - Debian
shv Wrote: ------------------------------------------------------- > The 3.3.2 kernel which is linked in the first post > doesn't contain support for Pogoplug devices > (arcNumber 3542). But the rescue system contains a > 3.3.2 kernel with support for pogoplug devices. Is > a 3.3.2 kernel with support for Pogoplug devices > (arcNumbers 3542 and 3960) available for doby chessplayer - Debian
@iSKUNK!, thanks a lot. I have meanwhile been able to get everything I need working with davygravy's Kernel and what not, but it is always good to have something running cleanly out of the box. Tried it out and with a little extra work for my separate boot partition, everything worked like a charm!by chessplayer - Debian
Thanks, me (or you?), for this deep insight and extremely useful comment! We have all been waiting for constructive contributions like this one. Keep up the good work! Oh, I guess the latter was meant more for people like bodhi, davygravy, shyd, varkey, rudolf (to mention just a few), people at archlinuxarm and many others and above all Jeff, who are really trying to help people with getting tby chessplayer - Debian
Hi pemmafr, a) yes, you are right, I am using the kernel from the Zyxel et. post. b) Yes, it can boot from SATA and you can have your pick as to whether you want SATA or USB to be tested for bootable images first. For this, you have to fiddle a bit with the uBoot environment and be absoultely sure to work with labelled partitions. If you are interested in what uBoot environment I use whichby chessplayer - Debian
derdigge Wrote: ------------------------------------------------------- > hehe theese Device are meaning so much fun ;) > > vdr is also my plan ;)) > i will stay on booting fom usb so i can carry the > Harddisk arround then. > > But this really is an GoFlex Home. We are getting off topic. If you want to discuss the VDR-Option further (mine has been up and runningby chessplayer - Debian
So, in fact, you have a SheevaPlug ;-))by chessplayer - Debian
Hi, all I can tell you is that I used Jeff's standard uBoot install. In addition, I installed the updated rescue system and then made modifications to allow booting from HDD. For me, this worked for for both the GoFlex Net (which will become my VDR) and the GoFlex Home 3TB (which is my NAS and will be used for backup as well) and also the Dockstar.by chessplayer - Debian
Hi, it looks like you forgot to set the right arcNumber in your uBoot environment. Boot the GFH with the rescue system and say fw_setenv arcNumber 3338 Try again then. Cheers, chessplayerby chessplayer - Debian
Hi Rudolf, thanks for making this effort. I have been thinking of doing very much the same, but haven't yet found the time to do so. There is one thing, however, which I do not understand at all, and that is the issue of cloning a USB stick. The solution you are suggesting is way too complicated in my eyes and actually relies on stick to either have the same size or else you will haveby chessplayer - Debian
Hello everybody, having just read once again how to clone a USB-stick and seeing the hassle involved in doing so, I thought I would share my way of doing it, as this has several advantages, which, I hope, will become clear in the course of my post. I have a separate boot partition (as suggested in this German blog), which makes things a little harder, but still, I believe, quite easy. For tby chessplayer - Debian
Hi pemmafr, first of all: what kind of HDD do you have? Like myself, you might have a problem with the MBR if the drive has 3TB. If so, try to start from this post. My own uBoot-environment might not help you, because I am using a separate boot partition, but if you want to know, you can also find my environment in the GFH 3TB post I linked above (and the necessary changes should be prettyby chessplayer - Debian
------------------- So, before handy1 or anybody else reads this rather long post: I have just been able to solve my problem as well by reading a post on the archlinuxarm.org forum. It really is all about answering the questions correctly when hybridizing the MBR. So, I can finally go about installing Open Media Vault and using LVM along with it ... ------------------- Hi handy1, soby chessplayer - uBoot
Hi trigati, you probably solved your problems already, but I had a similar problem yesterday. I updated uBoot on the GoFlex Home and after that it did not boot into the pogoplug anymore. I did try to set some environment variables right after I had done the update, but fw_setenv/fw_printenv was not recognized ... Then, I tried to boot debian from Sticks I have (which work on both Dockstarby chessplayer - uBoot
Script does not work anymore! Hi again (after quite some time), having managed to buy two HDDs for the GoFlex Net, I wanted to test it today. First problem is that the USB-drive I made in July will boot, but won't let me ssh to the machine, while rescue will ... Ok, so I try to make another stick according to this post with all the bells and whistles like removing old debootsrap andby chessplayer - Debian
Hi davygravy, thanks a lot for this debian install, as it saved my day yesterday. Anyway, now my situation is the following: a) I have Jeff's standard uBoot installed b) I have your rescue V2.8 installed c) I just created a USB drive as per the REAME.quickstart... in your tarball above. This (normally) boots just fine, BUT: it will always ask me to modify the password! Any idea whby chessplayer - Debian
Hi everyone, last year I produced some flash drives for the Dockstar (tvheadend, vdr), which will not boot with the new uBoot. However, I need to revive at least one of those flash drives, since something goes wrong when I run tvheadend on the new Wheezy system. Unfortunately, this is what I get: U-Boot 2011.12 (Feb 12 2012 - 21:33:07) Seagate FreeAgent DockStar arm-none-linux-gnueabi-gby chessplayer - uBoot
Hi, the reason is that Gorgone's kernel does not work with the new uBoot. I noticed that when I tried to run a stick I had produced about a year ago with a newly adapted Dockstar. In the meantime I successfully adapted everything based on Wheezy install script (where I also use a separate Boot-Partition) and this works just fine. It was necessary to adapt Gorgone's prepare-scripby chessplayer - Debian