Did you reboot after delete/create partitions?by bodhi - Debian
derdigge Wrote: ------------------------------------------------------- > bodhi Wrote: > -------------------------------------------------- > ----- > > derdigge Wrote: > > > -------------------------------------------------- > > > ----- > > > Thanks for that update man! > > > > > > Is it wanted that all dvb drivers were &gby bodhi - Debian
If your serial console doesn't show anything, it might be that your uBoot in mtd0 has been corrupted. You can try UART booting: http://forum.doozan.com/read.php?3,7852,7852 If this works, then reflash uBoot to mtd0 while in serial console.by bodhi - uBoot
dave.opc, you got it working :) (just what I've suspected, the machid was needed). The installation script must have detected your machine type. But current uBoot version still needs machid to work properly. dmesg > [ 20.993836] libata version 3.00 loaded. > [ 20.995642] sata_mv sata_mv.0: version 1.28 > [ 20.995733] sata_mv sata_mv.0: slots 32 ports > 1 > [by bodhi - Debian
@dave.opc, You are still running as Dockstar. The fw_setenv in Debian does work (optim is correct that in uBoot it is setenv and saveenv). In Debian prompt fw_printenv arcNumber will show if it is 3338. If is 3338, then you also need to set machid env: fw_setenv machid D0A Then reboot. I hope this will work. If not then you will need to reinstall uBoot. I asked above if duriby bodhi - Debian
derdigge Wrote: ------------------------------------------------------- > Thanks for that update man! > > Is it wanted that all dvb drivers were missing in > 3.6* and 3.8*? > No dvb*.ko were present and media build from git > failes on 3.8 with the provided headers > (timex.h). > > Steven Dvb drivers probably were not included in kernel config (I don'by bodhi - Debian
Did you try to stop uBoot during countdown (type ctrl-j repeatedly)? Make sure you can do that before changing arcNumber. If you can't interrupt uBoot, try this for second nc command nc -up 6666 192.168.11.22 6666 After stoping uBoot. At the prompt, to continue booting run the boot command boot Once you can boot it this way,then change arcNumber and reboot. Your IP is setby bodhi - Debian
Looks like when you ran the installation script, you've chosen Dockstar as the machine, not GoFlex Home? it is set to be a Dockstar now, that's why you can't see the SATA drive. You should remove the SATA drive, boot with the USB stick before doing the following: 1 .First, set up netconsole so you can recover from problem if any goes wrong later. Make sure you can see the netconby bodhi - Debian
Dave.opc, You can post output of your dmesg and envs, and we'll take a look: dmesg fw_printenvby bodhi - Debian
@gaogao, That response was for Der Freibeuter above. I don't have time to create a good howto, so I was hoping that you would have found the answer by searching the forum. So I did a search: http://forum.doozan.com/read.php?2,524,page=1by bodhi - Debian
I guess this has answered my quetion: http://archlinuxarm.org/forum/viewtopic.php?f=29&t=5665by bodhi - uBoot
berli, So did you resolve your network problem described in the other thread with these commands?by bodhi - uBoot
May be this will help: http://www.cyberciti.biz/tips/build-linux-kernel-module-against-installed-kernel-source-tree.htmlby bodhi - Debian
Looks like uBoot was installed OK. You can use Davy's NSA320 rootfs to to boot the box. After you can boot into Debian, you can either keep using that rootfs, or attempt the Debian squeeze installation again on a new USB thumb. See here for NSA320 rootfs: http://forum.doozan.com/read.php?2,7806by bodhi - Debian
Did you keep the log of what going on when you installed wheezy?by bodhi - Debian
mgiammarco Wrote: ------------------------------------------------------- > Hello, > I have a goflex net and I am trying to install > debian on flash. > > Unfortunately install scripts gave me errors. Now > I am able to boot the system only from a rescue > system in usb key. > I tried the script to install rescue in mtdblock > but I am not able to boot from iby bodhi - Debian
dave.opc Wrote: ------------------------------------------------------- > Hello > > I used the tutorial > http://projects.doozan.com/debian/ to install > Debian on my 2TB GoFlex Home. > I disconnected the SATA drive from cradle, > inserted ext3 formated usb flash into usb and > booted the device. > Logged in with my account, did sudo. > Then did steps froby bodhi - Debian
I've uploaded linux-headers-3.8.11-kirkwood-tld package. See 1st post for updates.by bodhi - Debian
WarheadsSE Wrote: ------------------------------------------------------- > as a Psst @bodhi > > We're working on 2012.10 uboot. Still no USB, but > NAND, net, sata. @WarheadsSE, Any new development on the new uBoot?by bodhi - uBoot
Congrats! You are in good shape! To solve the ssh problem, ask at Arch site: http://archlinuxarm.org/ There are settings in Arch roofs that need adjustment.by bodhi - Debian
berli, > som information about my pogoplug > CPU ARMv6l PLX 7820 700MHz dual Cores > Your Pogoplug is of OXNAS variant, not a Dockstar! you're running a wrong installation procedure. See this thread for Debian installation: http://forum.doozan.com/read.php?3,6336,page=1 If you are OK with ArchLinux then see the first few paragraphs of the avove post.by bodhi - Debian
Will see if I can build 2013.04 uBoot, which should have this patch. Still, I'm not sure if netconsole will work properly with this later uBoot version.by bodhi - uBoot
@cpe, I meant you can always rerun uBoot installation as described here: http://projects.doozan.com/uboot/ When prompted for restore environment, say yes to get the envs reset to the normal Debian setup, and then try to boot with Debian Squeeze stick. This way at least you can run Debian and worry about rescue system later.by bodhi - uBoot
Cool :) I am glad everybody found my contribution useful.by bodhi - Debian
I can upload it, but it will be a while, since I'm on the road for a couple weeks.by bodhi - Debian
Quite a few people has problem with the rescue systems lately. I'm not sure why. I don't use it because I don't have a need for it, so I can't really have a good feel for the problem. If you can't make it work then I would suggest abandoning it for now. Just rerun the complete installation, and force a uBoot update and uBoot envs reset so you can get back to a bootingby bodhi - uBoot
Every thing looks normal. Another possible reason could be the USB brand, what brand the stick is? and can you try the intallation on another stick?by bodhi - uBoot
1. What is your envs looks like? from serial console uBoot prompt: printenv 2. Mount the Squeeze USB on another Linux box, and run (assuming the USB drive is mounted as /media/sda1) ls -l /media/sda1/boot/ What is the output of this ls -l command? do you see uImage and uInitrd ? if not, you will need to boot back to rescue system and generate them. If you've saved the installation loby bodhi - uBoot
Since so your situation is you can log in to the rescue system, and you have problem with Davy NSA320 rootfs, you should rerun the installation to install Debian Squeeze , and then upgrade to Wheezy. - Log in to the rescue system. - Use an empty USB thumb drive (it will be erased during installation). - Follow the installation instruction: http://projects.doozan.com/debian (use this scriptby bodhi - uBoot
It won't work on NSA320. I did not include support for it, since I don't have the NSA320, and don't have the appropriate patch.by bodhi - Debian