Could you post your UBoot envs? I'm going to dig out the log when I still boot the GFHome with SATA. Hope I can find it :-)by bodhi - Debian
Snerler Wrote: ------------------------------------------------------- > Figured out how to use "fw_printenv." I had to put > this line in my /etc/fw_env.config: > > /dev/mtd0 0xa0000 0x20000 > 0x20000 > > This is the what I get by running fw_printenv: > > > baudrate=115200 > loads_echo=0 > ipaddr=169.254by bodhi - uBoot
@floodo, I looked at the kirwood initialization code briefly. Running the GF Home with GF Net initialization code could cause problem during SATA device registration (i.e. the GoFlex Net has 2 ports, the GF Home has only 1 port). Since 2nd device's data structure could contain garbage at some point, it's possible that the kernel choke while trying to register the 2nd SATA device. Jusby bodhi - Debian
Yeah, I got that from your other posts, you're actually running the GF Net using the GF Home hardware! I think that's why the heartbeat LED is available. EDIT: strange, I don't see the heartbeat in GoFlex Net LEDs, either!by bodhi - Debian
floodo, One thing I've noticed that both you and Sagitarius have arcNumber 3089, which is the GoFlex Net, not GoFlex Home (they are supposed to work for both boxes but there are differences ). You could try to set it to the correct one, which is 3338. I'm running the GoFlex Homes with Jeff's UBoot, arcNumber 3338, and a self compiled kernel (3.2.18), with USB flash as bootby bodhi - Debian
Which Debian version are you using (uname -a)? what is your arcNumber ? also, is your UBoot the latest (Davy's) or Jeff's?by bodhi - Debian
If you're using Ext2 for the SATA drive, then I would plug the SATA drive into a USB interface, connect it to another Linux box and check the file system with e2fsck to see if it was corrupted.by bodhi - Debian
What is your archNumber? is it 3338 ?by bodhi - Debian
To turn on the green LED, add controls statements to end of your /etc/rc.local, right before exit 0, as shown below: if [ -d /sys/class/leds/status:green:health ]; then echo default-on > /sys/class/leds/status:green:health/trigger fi if [ -d /sys/class/leds/dockstar:green:health ]; then echo default-on > /sys/class/leds/dockstar:green:health/trigger echo none > /syby bodhi - Debian
Vlad, I ran into the same problem with that patch compiling 3.2.18. And I could not find any patch that works. So I went back to the Arch Linux ARRM July 2011 patch for goflex Net and goflex Home (it does not have the Pogoplug V4, though). It would be nice to have a good up-to-date patch for Wheezy we can all use! I've attached the file here in case you want to take a look. Updateby bodhi - Debian
arcNumber 3119 Iomega StorCenter ix2-200by bodhi - Debian
@floodo1, Use the information about seting rootfs label and UBoot envs in optim's post (read a few posts before that). It's foolproof, you'll never worry about booting the wrong drive again! Besides, this rootfs label convention is used widely, good to follow it. -bodhiby bodhi - uBoot
That's really strange! the Dockstar is 2998. I'm wondering whether you have somehow inadvertenly flashed an incorrect UBoot?by bodhi - Debian
I saw you're booting OK now with 2998?. The last unsuccessful reboot could have been something to do with the network udev rules after you've done apt-get upgrade (I am guessing). If you're curious, you could mount the stick on a different box and look at the log files or the udev rules to see if it was reset or messed up.by bodhi - Debian
@funtoy, As optim said, your kernel probably does not have LED supports. arcNumber 2998 for Dockstar requires a kernel with LED supports. What is the output of uname -a and the content of your apt source list ? -bodhiby bodhi - Debian
cyb, You could download davygravy's kernel deb for 3.1.9 and use his config http://ppl.ug/cnl1R63ZOBM/ Note: In the linked post, I compiled natively on the Pogoplug E02. And leaving out "-arch armel" parameter works OK as mentioned. -bodhiby bodhi - Debian
Daniel, That's the expected behavior. Once you installed new UBoot and boot with USB/HDD drive with ALARM on it, it's a basic Linux system you're running. So you will need to install SAMBA to make the shared folders appear in the local network. You could now try the Debian rootfs provided by Dave (posted in this forum, username davygravy). Just create a USB stick in the sameby bodhi - uBoot
Daniel, iirc, with ALARM fresh rootfs, the login is user: root, password: root. You can ssh in using root/root. After logged in, change root password to something else, and to verify to make sure the success installation: do a reboot (warm start): shutdown -r now and then later shutdown: shutdown -h now then power up (cold start) -bodhiby bodhi - uBoot
p_preston_s Wrote: ------------------------------------------------------- > I'm just hoping that someone, anyone, out there > can help. I need DETAILS!! If you're just going > to tell me to search, then PLEASE don't respond. > I am tired of vague and hateful people when I do > not understand something. Just looking for a good > solid answer with plentyby bodhi - Debian
Daniel, If you have completed all the steps for Arch Linux ARM then reflashing stock FW most likely wont work. And you have flashed different uboot. Probably the easiest way to get it to boot again, without resorting to serial console is to create a fresh Arch Linux ARM rootfs on a flash drive. After you can boot with Arch, you can then install Debian if you want to. Use your Ubuntu box anby bodhi - uBoot
@Daniel, Did you get past step 14 in your attempt? If you did not, then the reflashing stock FW should work. It is just a little bit flaky, you could try a different flash drive, and pushing the reset button with a paperclip seems to work well. If you did then how far did you get (i.e. which steps were executed)? Also, it would be best to keep the log of your installation for future troubleby bodhi - uBoot
Daniel, You could try to reflash factory firmware: http://support.goflexhome.hipserv.com/en/reflash/index.html Once you restore back to the stock FW. The rest is easy, just use Jeff installation script and you will get UBoot and Debian installed. bodhiby bodhi - uBoot
I hope eventually it will be easier to follow when the posts will be consolidated in some fashion :-) I'm trying to follow the thought process, and feel a little lost, too, with a massive amount of information. It could be my own lack of knowledge. But thanks gnexus for all the hard works and sharing.by bodhi - Allwinner A10
pek Wrote: ------------------------------------------------------- > Hi all, > > Thanks for your help, I could connect to my GoFlex > Net again using the rootfs for the Zyxell NSA320 > :) Cool:-) > > I have few questions for my understanding: > > What is the purpose of fw_setenv arcNumber > 3089? This is relevant to the differences between theseby bodhi - uBoot
varkey Wrote: ------------------------------------------------------- > @bodhi - I didn't have a rootfs for the GoFlex > Net. It was for the Pogoplug Pro I believe! ;) > > The guide you followed also uses the jeff's uboot > installer so you should be having the latest > uboot. This rootfs will be fine -- > http://forum.doozan.com/read.php?2,7806 Really?by bodhi - uBoot
gnexus Wrote: ------------------------------------------------------- > Quotedockstar says no though: > > dmesg |grep rtc > [ 11.146183] rtc-mv rtc-mv: internal RTC not > ticking > [ 11.181620] drivers/rtc/hctosys.c: unable to open > rtc device (rtc0) > > dockstar has no rtc. That's common knowledge. > Interesting that GoFlex Home has one. More thanby bodhi - Debian
You need to go to Varkey's site and get rootfs for GoFlex Net. http://www.varkey.in/2011/06/boot-debian-from-sata-seagate-goflex-net/ I'm not sure if Varkey still hosts this rootfs at his site, though (I downloaded it once long ago). But the idea is that if you can put a GoFlex rootfs on a USB flash drive, then recovery is painless. Format your USB flash drive, and untar that rby bodhi - uBoot
gnexus Wrote: ------------------------------------------------------- > I'm seriously shocked that any *Plug has a RTC. I > didn't even remember Kirkwood had a RTC input. The GoFlex Home has RTC, too :-)by bodhi - Debian
The first thing I've noticed reading the specs is that it has a 10/100 Mbs ethernet. It's adequate for 1080p, but wonder why? is the cost saving that significant nowadays? It would be a little slow for network file transfers.by bodhi - Allwinner A10
Jeff Wrote: ------------------------------------------------------- > I've created a new 'Platforms' subforum with A10 > and Kirkwood forums. Enjoy :) Thank you :-)by bodhi - Debian