Tushar Wrote: ------------------------------------------------------- > Hi Bodhi, > > I'm using a pogoplug v4. Now, I want to setup my > system with only one external USB HDD where I like > to keep rootfs on first partition while 2nd > partition should hold my (NAS/SAMBA) files. What > should I do? any suggestion? > > Thanks. Please post this questioby bodhi - uBoot
marcogaio Wrote: ------------------------------------------------------- > First post here, sorry me if i say some dumb > thing. I'm a rather log linux/debian user, but > i've a little experience on ARM, mostly OpenWRT. > > Someone gift me a ix4-200d. The machine was in > decent shape, who land me say that was retired > because ''does not workby bodhi - Debian
ElMariachi Wrote: ------------------------------------------------------- > I don't know if one of the three GFNs I got here > is 'unbrickable', but I got UART and also an old > JTAG lying around. And I'm planning on buying the > bus pirate soon, btw. I think we are ready for > some serious trouble here ;) If you can boot with kwboot (UART) then there iby bodhi - uBoot
To start, look at this thread for the Pogo V4: http://forum.doozan.com/read.php?3,16789,16789#msg-16789 So, you will need to do a very similar procedure for the GoFlex Net. Take a stab at listing the commands as you think it should be, and I'll correct it. First, list the MTDs, and you will need to do nanddump for each of these to a file: cat /proc/mtdby bodhi - uBoot
Gravelrash Wrote: ------------------------------------------------------- > @bodhi - you are experiencing the same issues that > i had. only thing i didnt try was connecting the > device to a network. > > From reading the thread again, it seems that the > device "wants" to be connect to a network before > it will boot. > > i imagine that looping aby bodhi - Debian
ElMariachi, > Again for the backup question that I had: > I would like to clone the GFN I am currently > working on to another one, for making the other > one stock again. The other one is completely > modded including rescue system. So that's why I > need to backup more than mtd0. I could use the > older GFN then for more testing with stock > formware and sby bodhi - uBoot
rayknight Wrote: ------------------------------------------------------- > bodhi Wrote: > -------------------------------------------------- > ----- > > Anybody who has connected serial console, > please > > post pintouts. > > J4 J6 3.3V | RXD | TXD | > GND > JTAG X|X|X|X|X|X|X|X|X|X| JP1 > X|by bodhi - Debian
bobafetthotmail, > To use the older uboot again we need to have also > stock uboots somewhere, > Jeff copied the original u-boot to stock rootfs. But we are strict about messing with stock. So I would dump it to /tmp only (1MB or less). And then at the end, copy the image to the new Debian rootfs /boot.by bodhi - uBoot
bobafetthotmail, > We can simply try to use ext3 for the rootfs > without making changes to the script, but I'm not > very happy with that compromise (and I'm sure > there will be devices that lack a ext3 driver > too). On the contrary, ext3 rootfs should be used, IMO. This has ramification: backward compatibility (see my instruction for installing rootfs). Ext4by bodhi - uBoot
Rainer, > One suggestion: could this script be extended to > also install the Rescue system upon request? I > think this would be a nice addition. Negative. This script only installs u-boot and Debian. Rescue system should not be part of this installation.by bodhi - Off-Topic
> I wonder if that will only work temporarily as it > should be using your own authentication for that > link. I think boba is right, I got 403 error trying today.by bodhi - Debian
bobafetthotmail, > Any ideas? One foolproof solution would be reversing the installation. And we only need a small toolbox. Let's try creating the basic rootfs first using ext3, and then chroot into that and do u-boot installation. The things to watch for if we doing this: we need to gather the mtds info, ethaddr, ... things that in the rootfs chroot we can't see.by bodhi - uBoot
@Ray, > https://drive.google.com/file/d/0B9BuGVh30LKyek5IZ > Fk3d090ZUE/view?usp=sharing > I could not use wget to download this.by bodhi - Debian
rayknight Wrote: ------------------------------------------------------- > HP T5325 appears to have an issue with > fw_printenv. I've booted a USB drive prepared > with > Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 > according to instructions and the following > contents in the fw_env.config file: > > > /dev/mtd0 0x00000 0x10000 0x10000 > >by bodhi - uBoot
rayknight Wrote: ------------------------------------------------------- > Solved my problem by using another USB drive. > The cheap 8GB Emtec stick I used appears to have > been the issue. Now using a 4GB SanDisk drive > with no issues. > > Ray Cool! Sandisk USB brand is always the best for booting.by bodhi - uBoot
You need to set in serial console: setenv console 'console=ttyS0,115200 mtdparts=orion_nand:0xc0000@0(uboot)ro,0xff00000@0x100000(root)' And boot into Debian, you will see there are 2 mtds (mtd0, and mtd1). But I'm not sure where the stock Netgear envs are located. Why don't you get the mtdparts corrected, and then flash the new u-boot: http://forum.doozan.com/reby bodhi - Debian
bobafetthotmail, > Well, I agree on it but I'll also say that I don't > like to work on things in my free time then being > told you don't want it made like that or that you > use things you don't like just to not offend me or > something. > So yeah, maybe not very in depth, but having some > feedback from you would be nice. > It is already stby bodhi - uBoot
freestyle, Post outtput of dmesg cat /proc/mtd cat /etc/fw_env.configby bodhi - Debian
bobafetthotmail, > It's more annoying when a firmware > change/difference breaks my script out of the blue > and I have to troubleshoot stuff over a forum in > inappropriate moments. We are not in any hurry for a deadline :) > Btw, also the original script from jeff also had a > large amount of code dealing with making a chroot > to install debian from scraby bodhi - uBoot
bobafetthotmail, > Will have to make a chroot I'm not sure I understand why would we need to chroot? the tools are static, and the only thing need to be written to / is /etc/fw_env.config? One more thing I forgot to mention: we need to check if the user is root and bail out if s/he is not root.by bodhi - uBoot
> Could you please point me to the easiest way for > making a full backup of stock bootloader + > firmware + env (everything) and restoring this > data to another GoFlexNet device before converting > it? Wiki - Debian on ARM Topics and Tutorials QuoteBooting Debian on Pogoplug How to set up U-Boot for booting in multiple drives configuration Backup and Restore NANby bodhi - uBoot
Everything looks good. Your current env for mtdparts is: console=console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0xff00000@0x100000(root) So when you list the envs in Debian, you probably got some errors fw_printenv mtdparts should be console=console=ttyS0,115200 mtdparts=orion_nand:0xc0000@0(uboot)ro,0xff00000@0x100000(root)by bodhi - Debian
ElMariachi, > and flexible with no problem regarding the SSD's > choice. In general, it works for any SATA drive, whether it is SDD or HDD. But you got one SSD that falls into the exceptional case. So the idea is you need to find the work around for that SSD. If you can use a different SSD/HDD then you should use that, and not bother with finding a workaround.by bodhi - uBoot
rayknight Wrote: ------------------------------------------------------- > bodhi Wrote: > -------------------------------------------------- > ----- > > Anybody who has connected serial console, > please > > post pintouts. > > J4 J6 3.3V | RXD | TXD | > GND > JTAG X|X|X|X|X|X|X|X|X|X| JP1 > X|by bodhi - Debian
Try both cases: 2. Power up, interrupt serial console setenv bootcmd 'run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_pogo; reset' boot 2. Power up, interrupt serial console setenv bootcmd 'run bootcmd_uenv; sleep 15; run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_pogo; reset' bootby bodhi - uBoot
armless, > (1) the Debian USB stick is ext3 but there's such > module in the initrd and the ext3 fsck failed, but > it managed to mount the rootfs using ext4's > backward compatibility, and to fsck it then: This is normal. Ext3 has been deprecated. Ext4 module is always used whether the rootfs is Ext3 or Ext4. > (2) some kernel error about the Kirkwood hardwarby bodhi - uBoot
> Where would I need to store these commands for > making this work for booting? Ah. So now you know it does work, but need some extra period to settle down. You can change your bootcmd to take out the uenv loading, just leaving the scandisk in: setenv sleep_period 15 setenv bootcmd 'run scan_disk; sleep $sleep_period; run set_bootargs; run bootcmd_exec; run bootcmd_pogo; resby bodhi - uBoot
ElMariachi, > I am using screen in mint 17.3 MATE. Don't use screen. Install picocom and use that. Screen is the worst to use with serial console.by bodhi - uBoot
Laris Wrote: ------------------------------------------------------- > it's appreciated! > > I was struggling with the egg-chicken problems for > many days and cannot found the valid Arch Arm URL > int the stick list. > I already flashed the latest Uboot according > bodhi's post in offical openwrt, but cannot boot > any debian system to install latest kby bodhi - Debian
Try in serial console setenv bootcmd_usb 'usb start; ext2load usb 0:1 0x800000 /boot/uImage; ext2load usb 0:1 0x1100000 /boot/uInitrd setenv bootcmd 'setenv bootargs $(console) root=LABEL=rootfs rootdelay=10; run bootcmd_usb; bootm 0x800000 0x1100000; reset' boot And pls post the log here. There is more to do in your u-boot envs. But let's get you boot the rootfs iby bodhi - Debian