bodhi & daviddyer I see a special firmware (###ubifs-ubinized.bin). Not what I understood the 1rst time. I thought there was an "extract " process of the original OpenWrt firmware. Well I will leave it there, no reason to soft-brick again my Goflex Home. I thanks two all for your time here. At the moment I am very happy with the changes performed to my Goflex Home. Neby cayoenrique - Debian
Note to the readers: We are talking about OpenWrt on NAND. This is not Debian on USB or HDD. If you are a newbie like me, PLEASE note that playing with the NAND is dangerous. If you change mtd0 your device will not boot. mtd0 holds Uboot. So 1rst try to understand UART Booting HowTo for Selected Kirkwood Devices @daviddyer Honestly, have the minimal installation for with the help of bodhiby cayoenrique - Debian
bodhi You are a good guy. You do put a lot of effort in answering. At any newbie reading this. I may be s7up!d or slow. But I could not finished those tutorials. The answer is there 4a. CLI upgrade: (wont work anymore, you will run out of space with newer Lede or openwrt - use 4b) And I am sorry could not find Upgrade device/router in 4.b So I was stuck. I know it most be thereby cayoenrique - Debian
Interesting forum behaviour. I try for 1rst time a quote response, And I see for first time where > >> come from. It is added by the system. Normally we see [ qoute ] .... [ / qoute ] Now I did went ahead with Openwrt Installation using procedures suggested. Most of my attempt failed after 1rst LEDE boot in ram. I am unable to install with opkg as new packages would not fitby cayoenrique - Debian
Honey I am backkkkk! Well I am in the process to Install Openwrt as I mention. So I decided to do a NAND backup and found that now after Kernel Update 5.16.5-kirkwood-tld-1 I get: # cat /proc/mtd dev: size erasesize name mtd0: 00100000 00020000 "u-boot" mtd1: 00400000 00020000 "uImage" mtd2: 02000000 00020000 "rootfs" mtd3: 0db00000 00020000 "by cayoenrique - Debian
I am so tired.... This been the weirdest of my projects. So many things went wrong preventing me to be successful. HE HE HE. But at last netconsole is working. 1rst my NAND was corrupted. Battery is dead. The device did not hold the date. Device seems to failed to connect to Ethernet. I guess all this was cause by the bad battery. Then my PC Firewall prevented communications. I keepby cayoenrique - Debian
bodhi I do not have a real battery substitute. I will try to see how it behave with a 1000uf capacitor. I should keep hardware clock a few minutes a live when I remove power. Allowing me to do test without any interruptions due to lost of time. I let you know if it works. "allow-hotplug eth0" was my attempt to correct the device to fail to connect to my lan. As from time tby cayoenrique - Debian
Now lets start with where I need help: wiki's link to Use netconsole to troubleshoot Debian kernel booting 1rst I notice that once we apply the steps we lose the real Serial Console!. Is this how it is supposed to be? Now my ip are as follow: 192.168.3.62 = This is my Arm device (Goflex Home) where I am installing Debian 192.168.3.14 = This is my PCs where I work. And for the reby cayoenrique - Debian
bodhi I am still not been able to do wiki's link to Use netconsole to troubleshoot Debian kernel booting . Let me start from what I done: I decided for the time been to remove my PC Firewall. Then I see the device not picking the IP always. From time to time it fails , resulting in me failing to be able to do ssh. After analysis I hound eth0 hutplug is not enable. And I guess Iby cayoenrique - Debian
HE HE HE I miss wiki's Booting with uEnv.txt. Thanks for the link https://forum.doozan.com/read.php?4,42279. I will be reading on it. Regards Firewall preventing netconsole. I did an analysis with tcpdump . And found all communication stop after Debian on device sent 18:57:44.357479 IP 192.168.3.62 > 192.168.3.14: ICMP echo request, id 0, seq 0, length 8 So I removed iptablby cayoenrique - Debian
bodhi Nice explanation on forum history. Save me a couple of questions. No need for any forum changes. I was only offering my testimony as a newbie. Giving the reasons as why I did not started my own debian on device hack, 5 years ago. >No, it won't work. It was created in the old Wheezy days and now is obsolete. > It would result in an inconsistency in the box that needs tby cayoenrique - Debian
As is. How do I rate this forum, from 1 to 10? I give it 20!! Yes double its value. Thanks. I will follow with my question next. But 1rst some suggestions for possible improvement. I am a user that loves to follow rules. Admin please let me know if I violate any of forum rule. I am new user, I do not intent to ask forum to be like I want. But I love to provide my experience. 1rst sby cayoenrique - Debian
Due to *** Warning - bad CRC, using default environment I wanted to verify that my corrupted environment will not conflict with new U-Boot. So I did 1rst UART Booting HowTo for Selected Kirkwood Devices http://forum.doozan.com/read.php?3,7852,7852 Lucky enough my old U-Boot was BootROM version 1.2.1 ff00003c: 00000121 Once I proved new U-boot booted from UART and Debian booted froby cayoenrique - uBoot
I found my USB2serial device. So I do have now a serial console. So as you found no mayor issues, I will continue with: 2017.07 U-Boot Kirkwood - GoFlexNet, GoFlexHome, PogoE02, Dockstar, iConnect, NetgearStora, PogoV4/Mobile, Sheevaplug, NSA325, NSA320, NSA310S, NSA320S, NSA310, HP T5325, Dreamplug https://forum.doozan.com/read.php?3,12381,page=1 One last question. Please do not feelby cayoenrique - uBoot
Questions from newbie - 2017.07 U-Boot Kirkwood : GoFlex Home 1) My Experience: 1rst timer on Hacking GoFlex Home. But I been in Linux from some time. Experience in Openwrt with routers. So new to doozan tutorials but I hope to be able to manage the Debian to Goflex Home hack. 2) What I done so far: I read & follow: Install Latest Kirkwood Debian rootfs and U-boot from stock OSby cayoenrique - uBoot