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
mari8b, > root@debian:~# cat /proc/mtd > dev: size erasesize name Ok. That's what I expected. > 2. printenv (is it what you need?) Yes, it is. > bootargs=root=/dev/sda1 console=ttyS0,115200 > elevator=cfq mem=256M poweroutage=yes > mac_adr=0x00,0xd0,0xb8,0x19,0x34,0x6b The bootargs need to have mtdparts env in it. Power up, interrupt serial cby bodhi - uBoot
Note the 1st step Quote1. uBoot envs config and mtd partitions must be defined as followed in your rootfs cat /etc/fw_env.config # pogoplug v3 /dev/mtd0 0x00100000 0x20000 0x20000 cat /proc/mtd dev: size erasesize name mtd0: 00e00000 00020000 "boot" mtd1: 07200000 00020000 "data" If you don't have /etc/fw_env.configby bodhi - uBoot
spindles7, For whatever reason, the bootcmd_unenv was never executed before the scandisk bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi; sleep 3 GoFlexHome> boot Reset IDE: Bus 0: OK Bus 1: not available Device 0: Model: ST1000DM000-9TS15E Firm: CC92 Ser#: 5YA0FYGYby bodhi - Debian
Ok so it is a Pogoplug Pro V3 clone. You can proceed to install uboot.2015.10-tld-2: https://forum.doozan.com/read.php?3,16017 and if desired, a new rootfs Debian-4.4.54-oxnas-tld-1-rootfs-bodhi.tar.bz2: https://forum.doozan.com/read.php?2,16044 Note: the current rootfs you have is OK to use, and you can upgrade the kernel to linux-4.4.133-oxnas-tld-1 (tarball linux-4.4.133-oxnas-tld-1by bodhi - uBoot
Try setenv devices ide setenv bootdev ide printenv bootby bodhi - Debian
rayknight Wrote: ------------------------------------------------------- > If I recall correctly the OX820 will try to boot > from SATA first, although it appears that OpenWRT > uses a chain-loaded U-Boot to boot the current > kernel on this hardware. You may find some useful > information at > https://github.com/olderzeus/Iomega-HMNHDCE that > would help get a newerby bodhi - uBoot
ElMariachi, > because the driver > might need some patches for working with the > current kernel. I have not tried comple it to see for myself, but looks like this is the case. > Why > are the header files not matching each other, > regarding their search pathes? It is typical to see problem like this when header files are not found because the driver build didby bodhi - Debian
spindles7, QuoteIs the uEnv.txt file read some other way? No, the envs just did not seem to execute correctly. Let's try again: setenv devices ide setenv bootdev ide bootby bodhi - Debian
mari8b, > In the thread "2015.10 U-Boot for Pogoplug V3 > (OXNAS OX820)" DaveP mentioned, that this U-Boot > breath new life into Iomega HMNHDCE NAS. Is there > somebody, who knew how to do it? Please post link to the post you've quoted above. Update: I found it. Unfortunately DaveP did not post the boot log with new u-boot.by bodhi - uBoot
mari8b, > Starting kernel ... There should be more after this (the kernel boot log).by bodhi - uBoot
spindles7, Make sure the /boot/uEnv.txt file exists on the SATA rootfs. Power up, interrupt serial console, and setenv devices 'ide usb' setenv bootdev ide bootby bodhi - Debian
juandbotiva, > Hi bodhi, it worked! Cool! > Now, in order to update uBoot, should I follow the > steps in the uBoot sticky post ? Or do I have to > do something specific for my PogoPlug ? > Yes, follow instruction the sticky post to install u-boot-2017-tld-1. Make sure that you do step 8 to flash the new default envs image from uboot.2016.05-tld-1.environment.bodhi.by bodhi - Debian
spindles7, Power up, interrupt serial console, and printenv boot Please post the entire serial console log here.by bodhi - Debian
Please create a new Debian ttread for question or problem with installation.by bodhi - Debian
Please create a new Debian ttread for question or problem with installation.by bodhi - Debian
This thread is temporarily closed until the next release. Please create a new thread for installation problem.by bodhi - uBoot
spindles7, custom_params=init=/bin/systemd ipv6.disable=1 to enable systemd and disable IP v6 is correct. No other redefition is needed. No other env should be added, unless you want redefine an existing env. New env cannot be defined in uEnv.txt.by bodhi - Debian
ElMariachi, Have you tried apt-get update apt-get upgrade before compiling the module?by bodhi - Debian
juandbotiva, Your envs are now a mix of uboot.2014.07-tld-1 and uboot.2016.05-tld-1. So it is a little messy! Try this procedure to make sure they are back to a correct set and boot with it. ====== Download the attached uboot.2014.07-tld-3.environment.scr script file. Mount your USB rootfs on another Linux box. Assuming it is mounted as /media/sdb1. Copy this script file to the USby bodhi - Debian
juandbotiva, > the u-boot envs to 2014.07-tld-1. And I got back > to the initital error I was getting, which was: Since you have down graded to 2014.07-tld-1, your envs are different, so let see what they are. At the u-boot prompt, get the listing of u-boot envs and pos there Pogov4> printenvby bodhi - Debian
spindles7., QuoteSeems to be working perfectly now though. I assume I can now create additional partitions on the SATA drive for data etc? Right! that's a great plan. Don't worry about systemd for now. Once you got everything working, booting the rootfs as you want, then worry about that set up.by bodhi - Debian
balanga Wrote: ------------------------------------------------------- > shayan123 Wrote: > ------------------------------------------------------- > > bodhi, > > > > Thank you for all the support. I can now > > successfully boot Debian on my GoFlex Home! > > > > However, just out of curiosity, is it possible > to > > write > >by bodhi - uBoot
I think the inconsistency between your Arch u-boot and envs is too cumbersome to get it working. So the steps to do: - Boot with kwboot using the latest GoFlex Home u-boot from this tarball: uboot.2017.07-tld-1.goflexhome.bodhi.tar https://forum.doozan.com/read.php?3,12381 -The procedure is similar to this post (which use the NSA310S u-boot). https://forum.doozan.com/read.php?3,51739,519by bodhi - Debian
habibie Wrote: ------------------------------------------------------- > bodhi Wrote: > ------------------------------------------------------- > > habibie Wrote: > > > ------------------------------------------------------- > > > My understanding is OP tried to use systemd to > boot a Pogoplug Pro using uEnv.txt. Can we do this > using the above approby bodhi - Debian
spindles7, > > U-Boot 2016.09.01-1 (Oct 10 2016 - 23:11:39 -0600) > Arch Linux ARM > Seagate GoFlex Home This Arch u-boot is older than your current envs. A few commands are not available in this u-boot version. Thay's why it had trouble booting. I'll be back and recommend the next step.by bodhi - Debian
habibie Wrote: ------------------------------------------------------- > bodhi Wrote: > ------------------------------------------------------- > > habibie Wrote: > > > ------------------------------------------------------- > > > Bodhi, this just caught my attention. My > question is will this work on any device other > than a Pogoplug Pro? > >by bodhi - Debian
Perhaps not. I could not find the ID 818b in staging driver folder. Only 8192u driver.by bodhi - Debian
ElMariachi, > Hello Bodhi, yes it is an 8192eu for sure. It is already supported in the mainline kernel. Not sure which module you can load, though. I need to look at the source code to find out. Perhaps also I need to configure it in 4.17.2-kirkwood-tld-1.by bodhi - Debian