dave.opc, First, "sudo tar ..." might not work! you should do both steps (tar -c and tar -x) as root. Second, it's easier to clone a disk if it's not a system disk. So you should clone it using another Linux box. Doing this as root user: 1. Mount both to a running Linux machine (eg. laptop, desktop, or another plug if you have one) 2. Make sure the HDD is formatteby bodhi - Debian
Hi chessplayer, By "similar" I meant you can name your image in the parameter "-n" to whatever you want to call them, or just use the commands as they are! The other parameters should be the same. Furthermore, you won't brick your box with this, if it does not work, you can mount the USB on another Linux box, remove them, and boot the NSA back on, and then generate tby bodhi - Debian
chessplayer, That error can be ignored since the kernel naming convention is not standard (eg. 3.3.2-kirkwood-dg) . You should check your /boot directory to see if the file initrd.img-3.3.2-kirkwood-dg was generated. If it was, then you can go ahead and generate uInird (you don't have to generate uImage, but it goods to keep them updated in pair anyway). Something similar to this mkby bodhi - Debian
dave.opc, You can clone the USB stick to the HDD.by bodhi - Debian
metric, Quoterescue:/tmp# md5sum uboot.mtd0.kwb 77ce1df732843774e5257b615ba8a9db uboot.mtd0.kwb Is uboot.mtd0.kwb is a saved image of current good uBoot image? You could try to reflash mtd0 with a good uBoot image from Debian command line. First, verify your mtd partitions are what should be: # fw_printenv mtdparts mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(daby bodhi - uBoot
Ah! I forgot that our minimal Debian rootfs usually does not have automount enable. So I guess Davy's rootfs does not have udev rules defined for that. You could either change udev rules to automount the HDD, or add fstab entry to mount it when the kernel starts, or add a mount command to /etc/rc.local to mount it at the end of kernel startup. udev rules grammar is a little hard to get itby bodhi - Debian
Yes. Davy's Pogo E02 patch has been in mainline uBoot. I've compiled and flashed 2003.01 uBoot with Pogo E02 support already in mainline. And I also had to change the env address to 0xc0000 to be able to use current envs, as our standard location is at 0xc0000.by bodhi - uBoot
@chackoc, It is certainly feasible doing that. But the instruction in the link seems incomplete. Be careful, it might lock you out so do this only if you have serial console. Other topic: re uBoot patch, the latest uBoot and a few versions before that has the Pogo E02 patch in mainline. So it could be modified to set the env address at a different location.by bodhi - uBoot
derdigge Wrote: ------------------------------------------------------- > I used the "build" script from linux tv git repo > here: > > http://linuxtv.org/wiki/index.php/How_to_Obtain,_B > uild_and_Install_V4L-DVB_Device_Drivers Thanks for the link.by bodhi - Debian
With only the USB stick plugged in, boot into Debian, and 1. Use fw_setenv to set uBoot envs the same way you set arcNumber before (put the value in quote if there is space) fw_setenv usb_rootfstype ext2 fw_setenv usb_init 'run usb_scan ; setenv usb_root LABEL=rootfs' 2. Use tune2fs command to set label tune2fs -L rootfs /dev/sda1 3. Reboot to verify that it boots succby bodhi - Debian
dave.opc, Look back what I wrote above: ------------------------------------------------------- > 4. To boot with both drives attached, you will > need to change some uBoot envs. But worry about > that later after you got the SATA drive working. ------------------------------------------------------- First step is to format the SATA HDD, and then set some uBoot envs. You canby bodhi - Debian
nemmy Wrote: ------------------------------------------------------- > hey guys, i have the exact same error. > > > # Verifying uBoot environment > Block size 131072, page size 2048, OOB size 64 > Dumping data starting at 0x000c0000 and ending at > 0x000e0000... > Connecting to download.doozan.com > (50.116.34.13:80) > uboot.environment.md 100% > |**by bodhi - uBoot
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