jedie Wrote: ------------------------------------------------------- > My old USB Stick is broken and my dockstar debian > system is away... (I can connect to the dockstar > into the rescue system.) > > My question is, how can i create a new debian on a > new USB stick? Exist here anywhere a simple Image > that i can put on a USB Drive? Something like > http://arby bodhi - Debian
Vlad Wrote: ------------------------------------------------------- > Hi bodhi, > > does it also boot without > > General setup -> Embedded System -> Enable > Patch physical to virtual translations at runtime > -> Disable > and setting PHYS_OFFSET to 0x00? Hi Vlad, You got me curious, so I rebuilt 3.2.26 without these 3 parameters. It boots on myby bodhi - Debian
It does not need to since the bootm has no second parameter.by bodhi - uBoot
You could find the definition easily, google for UBoot, uImage, uInitrd. Basically, uImage is the kernel image that UBoot expects to find, uInitrd is the ram disk image. Debian uImage is built to work with UBoot. uInitrd contains the initial roofts (not the real one), which usually contain drivers that are needed at boot time. The rest of the drivers are loaded as modules later (I've simplifby bodhi - uBoot
Just a thought to show what is possible :-) a variable contains true/false after a certain condition is met. So that could be used in the bootcmd. No I did not use different label for SATA partition, since I only want to boot exclusively when a drive is attached. iIf USB drive is attached, I only want to boot from there using a SATA drive that does not have "rootfs" label. (note thatby bodhi - uBoot
Just some suggestion and random thought on multiboot. Let's dissect this envs listing from a GoFlex Net. Basically, we see 5 relevant parts: 1. USB Boot 2. SATA Boot 3. Netconsole 4. Rootfs label 5. bootcmd To tell UBoot to boot from a correct partition, a rootfs label is the most elegant way. It can be used to set each boot partition to a label and tell UBoot to find it. To creby bodhi - uBoot
Hi Vlad, I have not tried that yet! I set these values so that I can use the same 3.2.x build on my other plugs, which still have Jeff's original UBoot on them. If you want to confirm that, I could rebuild another version without these parameters and try them? bodhiby bodhi - Debian
Regarding patch rejected the machine_types, l've figured out the reason: the code were just different enough that patch has problem reconcile the diffs so it rejected the file. I manually modify the machine types and it built pass that. However, the build encountered other problems in davy's patch, I ended up modifying several of the kirwood devices setup files in order to build. Aby bodhi - Debian
beeryourself Wrote: ------------------------------------------------------- > thankyou for answering! > i know that ext3 boot drive will recover from > power outage with no problem and I am trying to > figure out what's the best between this and lack > of journaling with ext2 for a more durable usb > drive. > > by the way I already tried to format the stickby bodhi - Debian
Vlad Wrote: ------------------------------------------------------- > Edit: Ok, now I finally found davygravy's patch > for 3.3.x > https://www.dropbox.com/sh/nwt2kbvetvgvroo/iUjYHep > 7VX/Kirkwood/kernel/patches > I'll check if that one will perform better with > Debian's 3.2. Vlad, I've tried Davy's patch with 3.2.26. The new machine typby bodhi - Debian
@beeryourself, Make a clone of your stick and change it back to Ext2 file system. Try booting with it first to make sure everything works. With Jeff's script, UBoot env for the rootfs type is set to Ext2. Afer you booted successfully into Debian, you can see that with fw_printenv. You can change the UBoot rootfs type to Ext3 and change your USB stick file system to Ext3. But I wouldby bodhi - Debian
@cyb, Concurred with what Davy said, I'd suggest that you label the rootfs that you want to boot with, and set the UBoot env to find it. # fw_setenv usb_init "run usb_scan; setenv usb_root LABEL=rootfs"by bodhi - uBoot
Assuming you have multiboot , a menu would be presented and wait for input, you have to select which system to boot anyway. So what is the benefit of not having to physically remove the USB stick? is there a use-case that you can describe?by bodhi - uBoot
Thanks Davy!by bodhi - uBoot
davygravy Wrote: ------------------------------------------------------- > NAND-flash uboot.kwb file, for flashing to NAND > Tested extensively on a Pogoplug Series 4. Works > well for me, but use at your own risk. > > Don't use on a Pogoplug Mobile. It will > require a slightly different setup. > > Will post full patch set in the coming weeks, andby bodhi - uBoot
Thanks gnexus! can you believe it's already sold out?!by bodhi - Allwinner A10
Take a look at this thread: http://forum.doozan.com/read.php?2,5775,page=1by bodhi - Debian
Debian method of upgrading (in summary): 1. Specify in apt sources.list what distribution to get the packages from. Below is "wheezy" example. Currently your 2.6.x is stable and it's "squeeze". So you should see the mirror name URL and "squeeze" in /etc/apt/sources.list # cat /etc/apt/sources.list deb http://ftp.us.debian.org/debian wheezy main 2. Runby bodhi - uBoot
6pack Wrote: ------------------------------------------------------- > Q1 - Migrating old disk to new one > I have installed debian on a sandisk 4GB usb disk. > The debian partiton is 2GB and swap is 512MB i > think. > I want to move this to a larger 1TB usb hdd. I > made a 2Gb partition for rootfs with label rootfs, > 512MB saw with no label and rest might be ntfs/by bodhi - uBoot
I think you can just run Jeff's Wheezy install script and it should work. But I have not tried it (I have never used the UBit install scripts), so I can't say if it will detect the old installtion and deal with it successfully.by bodhi - uBoot
Kurlon has submitted this patch for 3.5.1: https://github.com/archlinuxarm/PKGBUILDs/blob/master/core/linux-kirkwood/archlinuxarm.patchby bodhi - Debian
I digged out an old spared SATA HDD, and put my current Debian rootfs on it. This is the info from my GoFlex Home booting with SATA as the boot drive (and the only drive). I shutdown and cold started several times (more than 5 times just to be sure). Hope this helps. netconsole output: U-Boot 2010.09 (Oct 23 2010 - 11:53:10) Marvell-GoflexNet by Jeff Doozan, Peter Carmichael Hit any keyby bodhi - Debian
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