I'm currently running the latest uBoot (2017.07) for my GoFlex Home with Debian-5.2.9-kirkwood-tld-1 but I can't get ZFS to install. I've been following the OpenZFS Instructions but DKMS outputs: configure: error: *** None of the expected "bdi_setup" interfaces were detected. *** This may be because your kernel version is newer than what is *** supported, or yby shayan123 - Debian
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 stock firmware to the NAND? The firmware provided by Seagate includes 3 files: uImage initrd hipserv2_seagateplug-20120508.ubi If so, how would this be done on the GoFlex Home via serial console?by shayan123 - uBoot
Alright, I tried what's described in the guide and i'm having a few issues: Since my stock envs are bad and im booting off of rootfs, do I still need to save the outputs of fw_printenv? If so, fw_printenv has no mention of mtdparts root@debian:~# fw_printenv mtdparts Warning: Bad CRC, using default environment ## Error: "mtdparts" not defined The guide mentions to sby shayan123 - uBoot
bodhi Wrote: ------------------------------------------------------- > kwboot will help you booting into Debian rootfs on > USB. After that you can flash new u-boot and its > default envs image. That will solve your problem. Yes! Debian boots perfectly from rootfs with kwboot! Now I assume I need to flash the uboot.2017.07 for GoFlexHome as described by this post? https://forum.by shayan123 - uBoot
bodhi Wrote: ------------------------------------------------------- > shayan123, > > That's the wrong command syntax to use. The > correct one is: > > > sudo ./kwboot -t -B 115200 /dev/ttyUSB0 -b > /home/ubuntu/Downloads/uboot.2017.07-tld-1.goflexhome.mtd0.kwb > -p > My bad. Alright, I'm able to send the boot image now, but the new boot imaby shayan123 - uBoot
bodhi Wrote: ------------------------------------------------------- > This is the time when you can kwboot the box then > everything is solved! so try that again. Alright, I gave kwboot another try. This time on Ubuntu instead of MacOS, which fixed my previous issue ("stuck at Please Reboot Target").. However, this is what happens now: ubuntu@ubuntu:~/Downloads$ sudoby shayan123 - uBoot
balanga Wrote: ------------------------------------------------------- > shayan123 Wrote: > ------------------------------------------------------- > > It's the internet mate, everything's there, > just > > takes a bit of searching! Check this one out: > > 10-pin > > connector on AliExpress (and its barely a > > dollar) > > >by shayan123 - uBoot
The guide here describes how to install Debian over SSH but currently, I can't get SSH to work. I think I need to fix my envs before attempting to install Debian. bodhi Wrote: ------------------------------------------------------- > For choice 1, I don't have this FW version (my GFH > boxes are much older so what I have in my old > notes might not work). I wouldnby shayan123 - uBoot
bodhi Wrote: > Create the USB rootfs first; > https://forum.doozan.com/read.php?2,12096 > > After you’ve done with rootfs, I will be back to > show you which envs you need. Okay, I have the tarball on a FAT32 (MBR) formatted USB. I assume I can't access the /boot unless I correct my envs?by shayan123 - uBoot
The main reason I started tinkering with my GFH was because I wanted CUPS on it. So I suppose Debian is a better choice. I'm not sure how to proceed (considering that my envs are currently messed up). If I decide to install Debian, do I need to fix the envs first? Also, is it possible to run CUPS and avahi on stock firmware?by shayan123 - uBoot
bodhi Wrote: > At this point you can run some commands such > as > printenv at stock u-boot prompt? Yes, I can. But the real issue is, I can't get it to boot successfully, This is what I always get: -- NAS EXPLORER -- _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/ |____by shayan123 - uBoot
bodhi Wrote: ------------------------------------------------------- > Please post the log of your kwboot attempt here > (copy/paste the entire terminal session). Shayans-MacBook-Air:~ shayan$ kwboot -t -B 115200 /dev/tty.SLAB_USBtoUART -b /Volumes/HDD/Users/shayan/Desktop/Projects/GoFlex/UART/uboot.2017.07-tld-1.goflexhome.mtd0.kwb -p Please reboot the target into UART boot modby shayan123 - uBoot
bodhi Wrote: ------------------------------------------------------- > Of course, it is impossible to send command to the > GF Home if you don't connect its RXD pin. From the > pic you posted above, only GND and TX are > connected. > > If that RX pin was burnt out and cannot be used, > then you cannot boot with kwboot. Okay, I've managed to fix the bby shayan123 - uBoot
balanga Wrote: > I know what you mean by tilting paper clips at an > angle but sometimes you need to hold on to them > whilst connecting and if you let go you break the > connection.... > > ....and sometimes you just can't find the right > angle :(... Like I said, a bit of excessive solder or a dab of hot glue on the tips should help hold it in place. I'by shayan123 - uBoot
balanga > What sort of connector > do you use? The Dupont connectors I have are loose > and need to held in place - the slightest knock > and they fall out... just wondered if the was a > specific ten pin connector which would stay firmly > in place... Lol, I really don’t do a lot of this serial console stuff so I don’t even have the right dupont connectors. I had tby shayan123 - uBoot
That is the entire log (4 posts above) I can’t give any user input so I can’t interrupt the boot. I’m not sure if it’s due to a software side issue or the burnt PCB connector. From the log above: ... CPU : Marvell Feroceon (Rev 1) Streaming disabled Write allocate disabled ... Right there: "Write allocate disabled". Does that have anything to do with this?by shayan123 - uBoot
Write allocate disabled Does this have anything to do with the GoFlex not being able to accept input? I can see U-boot outputting it’s banners and all, but I can’t send commands to the device. I assume it’s either the “Write allocate disabled” message during boot or the burnt PCB hole.by shayan123 - uBoot
Havent used your firmware link yet, I was looking at the booting of the current stock firmware via serial console. There is no mention of Kirkwood. It is definitely a Seagate GoFlex Home (REV 01) but U-boot says: -- NAS EXPLORER -- _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/ |____/by shayan123 - uBoot
Okay, obtained the kwb and set up kwboot. I put in the kwboot command and it says "Please reboot the target into UART boot mode". How do I do that? I've tried executing the command when the GoFlex is off, on and in recovery. Neither of them work. Also, correction: serial console doesn't show the Tx or Rx indicator as active. (Previously, the metal plate below the GoFlexby shayan123 - uBoot
I have a GoFlex Home that won't boot. I've connected it to a terminal via a USB to UART, but I can't get any output from the device. (I've tested that the CP2102 interface works, because messing with the TxD and RxD gives me junk values on the screen. Also, all the indicators on my CP2102 interface are active so there's nothing wrong with the physical connection.)by shayan123 - uBoot