mari8b Wrote: ------------------------------------------------------- > I think, I'm starting to understand... > > There's no NAND flash on the Iomega Home Media CE > (HMNHDCE). Everything (including U-boot) is > written on the HDD. So if I understand it right, > there's no need for MTD partitions support... > > Description of the first 32MB of tby bodhi - uBoot
balanga Wrote: ------------------------------------------------------- > bodhi, > > I'm not really sure what has happened but it seems > to have booted up using Stock. Cool! so the error on mtd2 was not that bad. > I have been able to > ping it and would be able to ssh but can't get > past the password prompt - have tried all the > methods Iby bodhi - uBoot
balanga, > Unfortunately I had a power cut and the GoFlex > Home unit rebooted to a flashing green light, so I > guess that is the end of the experiment. You have flashed mtd0 succesfully, so the box is not bricked. Without mtd2, stock OS is not running. Connect serial console and all will be OK. Once you have console, interrupt u-boot at count down and post back.by bodhi - uBoot
mari8b, > I have an empty HDD, so I don't care about > touching my current HDD rootfs, I don't need to > boot from USB now, but if it's necessary, I would > do it. > I have read many threads, but didn't find instructions to boot the Iomega HMNHDCE another way than the first 32MB. Once you've installed the new u-boot, this particular HDD schemeby bodhi - uBoot
balanga, > Looks like the typo crept in again. I take it that > should have been > > > ./flash_erase /dev/mtd0 0 0 > Right! > > The mtd0 worked OK, so I wrote mtd1 which also > worked OK, For mtd2. Execute each command at command line, not in a script: ./flash_erase /dev/mtd2 0 0 ./nandwrite -n /dev/mtd2 /mnt/usb/mtd/mtd2 If the error occuby bodhi - uBoot
mari8b, I meant to create the Debian-4.4.54-oxnas-tld-1-rootfs-bodhi.tar.bz2 rootfs on USB. And then in serial console, enter a set of new u-boot envs to boot with USB rootfs. This will be a little slow (I don't have my old notes with me so I will need to either find the instruction in forum old threads, or write them from scratch). But booting from USB is safer, so that you canby bodhi - uBoot
balanga, Quote# cd /mnt/usb/mtd # ls -larth mtd* -rw-r--r-- 1 nobody nobody 1.0M Aug 11 12:15 mtd0 -rw-r--r-- 1 nobody nobody 6.0M Aug 11 12:15 mtd1 -rw-r--r-- 1 nobody nobody 249M Aug 11 12:17 mtd2 This told us the dumps were fine. Without OOB data. So change your commands to the following. And execute it one by one by copy/paste these commands. Don't run them in a script. Stopby bodhi - uBoot
So the kernel on your rootfs is not good. No NAND mtd support. [ 0.000000] Linux version 3.12.6_OXNAS+ (root@PogoplugPro) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Sun Jan 12 08:07:56 CST 2014 Time to try booting with Debian-4.4.54-oxnas-tld-1-rootfs-bodhi.tar.bz2, as I mentioned: https://forum.doozan.com/read.php?3,64624,64754#msg-64754by bodhi - uBoot
Take a look at the MTD dumps again: cd /mnt/usb/mtd ls -larth mtd* And see what option this nandwrite provides cd /mnt/usb/tools ./nandwrite --helpby bodhi - uBoot
Power up, interrupt serial console, and execute: setenv bootargs 'root=/dev/sda1 console=ttyS0,115200 mtdparts=41000000.nand:14m(boot),-(data)' run bootcmd Login into Debian, and cat /proc/mtd and post the entired log (from u-boot banner until the last line you see in your terminal) here.by bodhi - uBoot
balanga Wrote: ------------------------------------------------------- > > Script started on 2018-08-13 07:24:14+00:00 > ^[]0;root@alarm:/mnt/smb/gfh^G# sh > restore > Erasing 128 Kibyte @ 0 -- 0 % complete Erasing > 128 Kibyte @ 20000 -- 12 % complete Erasing 128 > Kibyte @ 40000 -- 25 % complete Erasing 128 Kibyte > @ 60000 -- 37 % comple > Input file is nby bodhi - uBoot
balanga Wrote: ------------------------------------------------------- > bodhi Wrote: > ------------------------------------------------------- > > > > And your script looks OK > > > > > > cd /mnt/usb/tools > > ./flash_erase /dev/mtd0 > > ./nandwrite -on /dev/mtd0 /mnt/usb/mtd/mtd0 > > ./flash_erase /dev/mtd1 > > ./nandwriby bodhi - uBoot
Your Arch mtds now is the same as stock. So yes, you are ready to flash the nanddumped mtds. # cat /proc/mtd dev: size erasesize name mtd0: 00100000 00020000 "u-boot" mtd1: 00600000 00020000 "uImage" mtd2: 0f900000 00020000 "root" Now for sanity. Recall you listed the mtds in stock OS this way. bash-3.2# ls -al mtd total 262424 drwxr-xr-x 2by bodhi - uBoot
bodhi Wrote: ------------------------------------------------------- > balanga > > I expected the envs contains mtdparts definition, > so we don't have to calculate it. But it was > apparently not available so I need to define the > layout. Log in to Arch, and set mtdparts: fw_setenv mtdparts 'mtdparts=orion_nand:1M(u-boot),6M(uImage),-(root)'by bodhi - uBoot
igrblkv, 1. When hacking, ie. installing u-boot and rootfs, you should be root. Never use sudo. sudo is for a standard user. 2. Can I load the old system (aka stock OS) with the new uBoot? No it will not work with stock OS. 3. See here for Debian rootfs installation: https://forum.doozan.com/read.php?2,12096 QuoteLatest released kernel:linux-4.17.2-kirkwood-tld-1-bodhi.tar.bz2 (by bodhi - uBoot
igrblkv, Problem no.1 and Problem no.2 are OK. You are in stock OS, and the fw_printenv/setenv are not available. The bad blocks are far away from mtd0, where u-boot is. Problem no.3 New u-boot installation does not require mtdparts and ethaddr. A local MAC address will be used. And then you can set it to the real one later.by bodhi - uBoot
Please create new thread in U-boot subforum for problem or question with the installation.by bodhi - uBoot
balanga Wrote: ------------------------------------------------------- > What is preventing me re-installing Stock from a > USB stick? > > http://support.goflexhome.hipserv.com/en/reflash/index.html Have you tried that factory restore?by bodhi - uBoot
QuoteI've checked the uImage of the original system but it doesn't have a dtb file appended. This stock kernel is too old to have DTB in it. Flatten Device Tree was introduced into the Linux kernel circa 3.16. In a non-FDT kernek, all hardware devices were defined in the source code. Therefore GPL is an easy way to find info.by bodhi - Debian
balanga I expected the envs contains mtdparts definition, so we don't have to calculate it. But it was apparently not available so I need to define the layout.by bodhi - uBoot
Koen, > according to this document it should have 1Gbs. > http://www.netsolutionworks.com/datasheets/Dell-Wyse-T-class-IA.pdf. Yes. It is 1Gbs. > My last comment isn't meant as a complaint, I > wouldn't have got this far without your help. Just > hoping that someone reading the forum may have > some clever ideas how to continue from here on. > Theby bodhi - Debian
Derek, > Yea, I have tested another SD card briefly, and > seems to have the same results... Try Sandisk. > > Do you recall which version of uBoot you started > with the 'improved' MMC access? I am thinking of > downgrading the uBoot to make sure it boots > everytime... That would be the version before 2017.07-tld-1: https://forum.doozan.com/reaby bodhi - uBoot
balanga, > Just out of interest will the MAC address for the > Arch box remain as it is? It should be the MAC address of the stock box. So save this ethaddr=00:10:75:2C:A9:58. You need to change the ethaddr env on this box after flashing the mtds. One more info to get. Log in to the stock GFH, or if you have serial console connected, get the envs listing of this stock GFH. - inby bodhi - uBoot
> On Arch box: > > # cat /proc/mtd > dev: size erasesize name > mtd0: 00100000 00020000 "u-boot" > mtd1: 0ff00000 00020000 "rootfs" It does not match. We need to change mtdparts back to stock definition. So please get the envs listing at the prompt fw_printenvby bodhi - uBoot
Pretty cool news: https://www.phoronix.com/forums/forum/software/mobile-linux/1039376-lora-being-worked-on-for-the-linux-kernel-allows-long-range-low-power-wireless Open source world is calling Joey :)by bodhi - Off-Topic
balanga Wrote: ------------------------------------------------------- > bodhi Wrote: > ------------------------------------------------------- > > Here is a better tools binaries tarball to > > download: > > > > https://forum.doozan.com/read.php?3,27280 > > > > And before backing up the mtds you need to list > > them in stock OS (not Arby bodhi - uBoot
ElMariachi, Look in the release thread: https://forum.doozan.com/read.php?2,12096 Try this rootfs QuoteUpdated 20 Feb 2016: This Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 is to keep in sync with kernel Linux-4.4.0-kirkwood-tld-1.by bodhi - Debian
Here is a better tools binaries tarball to download: https://forum.doozan.com/read.php?3,27280 And before backing up the mtds you need to list them in stock OS (not Arch system): cat /proc/mtd cd /tmp mkdir usb mount /dev/sda1 /tmp/usb cd /tmp/usb And then use this format: nanddump --noecc --omitoob -f mtd0 /dev/mtd0 nanddump --noecc --omitoob -f mtd1 /dev/mtd1by bodhi - uBoot
spindles7, Ah. You did everything by the book and still it did not work. > a) it works OK if booting from a USB device > b) it doesn't work if booting from the drive in > the SATA interface. I will need to test this IDE uEnv.txt myself and let you know (in about 2-3 weeks when I get back to my development rig). Please remind me! In the mean time, if you are going to boby bodhi - Debian
Derek, > I hope this is not an unresonable request... :) > Is it possible to have an option in future version > of uBoot to switch back to the previous version of > MMC driver It is indeed unreasonable :) usually I try to use mainline version if possible, since it is widely used and tested. My testing on a Sandisk SD card with Pogo V4 and Sheevaplug was without problem. Raby bodhi - uBoot