Thanks Joey! it's a very good test. Net: Could not get PHY for egiga0: addr 8 phy_connect failed Could not get PHY for egiga1: addr 9 phy_connect failed egiga0, egiga1 MV88E1310 PHY initialized Hit any key to stop autoboot: 0 ON100_K9> version That addr 8 is for the openrd. Obvious ly this box has a different PHY address.by bodhi - Debian
@Gravelrash, > I think its more to do with CISCO's modifications > than anything marvell I think you might be right. I'm switching to a new approach for Ethernet. Version 2.10 above.by bodhi - Debian
OK then. This is plan B (which I really wanted to get to eventually, but been trusting stock ethernet code too much). Please try this version 2.10. Do the same test 1 and 2. And the left port is MON, right port is LAN, looking from the rear edge.by bodhi - Debian
Thanks. I'll start with the Pogo V4. I think I can boot back to stock with this box. And the next will be Pogo E02.by bodhi - uBoot
Chuck99 Wrote: ------------------------------------------------------- > It is booting fine.has one error can not find > uEnv.txt on boot. Ignore this. It is not an error, just warning that you are not using uEnv.txt. > Other problem now is no ssh > access. That is the rootfs mounting problem that I showed you how to fix above. There is a Search button for this forumby bodhi - uBoot
You've seen it: http://forum.doozan.com/read.php?3,16789,16789#msg-16789by bodhi - uBoot
SirK79 Wrote: ------------------------------------------------------- > Hi bodhi > > Thanks very much for full explanation of my > problems. I have done what you've suggested and it > worked perfectly ! > > I am in debian now :) Cool!by bodhi - Debian
I still have a plan B on this Ethernet bring up problem, depending on what Joey will tell how the LEDs behave.by bodhi - Debian
Chuck, Everything looks good, except this problem I mentioned above 2. Your rootfs still have the goflexnet DTB embedded inside uImage. You need to restore the orignal uImage came with the rootfs tarball in /boot. I've pointed this out before in this tread. Mount this HDD on another Linux box (assuming it's mounted as /media/sdb1) cd /media/sdb1/boot mv uImage uImage.gofby bodhi - uBoot
> I can see why stock firmwares would do the same. > In case they decide to change on-flash partitions > they only need to change dts and push a firmware > update, without touching the bootloader. As long > as the kernel image is in the same place (usually > just after uboot and wifi calibration firmware), > it will still boot fine. Right. They only deal with one boxby bodhi - Rescue System
warsmith Wrote: ------------------------------------------------------- > Thank you so much! I've been tearing my hair out > for almost a month trying to search for > alternatives. I finally stumbled across this > forum last night. I know :) it's hard to google this problem. You might want to put some tags or description in your first post and then see if it will tby bodhi - uBoot
SirK79, There are a few problems: 1. Your envs are still set to boot from USB. And the DTB is the GoflexNet NSA310> setenv load_dtb 'ext2load usb 0:1 0x1c00000 /boot/dts/kirkwood-goflexnet.dtb' NSA310> setenv load_initrd 'ext2load usb 0:1 0x1100000 /boot/uInitrd' NSA310> setenv load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage' So, they muby bodhi - Debian
Thanks Joey, According to your Test2, eth0 is the MON port, and the link is alive. Test 2 repeated on MON port Net: egiga0, egiga1 MV88E1310 PHY initialized on egiga0 ON100_K9> printenv ethact ethact=egiga0 ON100_K9> ping 192.168.178.1 Using egiga0 device ARP Retry count exceeded; starting again ping failed; host 192.168.178.1 is not alive Can you tell: - wby bodhi - Debian
OK. Let's try this version 2.9 Test 1: with ethernet cable connected to MON port Boot with kwboot, interrupt serial console version printenv ethact setenv ipaddr 192.168.178.110 setenv gatewayip 192.168.178.1 setenv netmask 255.255.255.0 ping 192.168.178.1 ping 8.8.8.8 Test 2: with ethernet cable connected to the LAN port Boot with kwboot, interrupt serial console veby bodhi - Debian
Joey, I forgot to ask: did you observe the fron LED behavior during booting? and did you observe the Ethernet port LED behavior during booting? It would be important. to know both.by bodhi - Debian
See this thread: http://forum.doozan.com/read.php?2,28710,28711#msg-28711by bodhi - uBoot
Thanks Joey, ON100_K9> ping 192.168.178.1 Using egiga0 device ARP Retry count exceeded; starting again ping failed; host 192.168.178.1 is not alive Is encouraging because the link is alive. But strange that MON port is egiga0. In Ray's stock uboot log, LAN is egiga0! perhaps Ray's report was switched MON/LAN. "ARP Retry count exceeded" might indicate some RGMby bodhi - Debian
Chuck, 1. Some of your u-boot envs are not correct in this box. That's why you have kernel booting probelm. Boot SATA again, and this time, interrupt serial console when it counts down and get the listing of envs printenv and then boot Please capture serial console log again and post here. 2. Your rootfs still have the goflexnet DTB embedded inside uImage. You need to restorby bodhi - uBoot
Here I reformulate. Test 1: with ethernet cable connected to MON port Boot with kwboot, interrupt serial console version setenv ipaddr 192.168.178.110 setenv gatewayip 192.168.178.1 setenv netmask 255.255.255.0 setenv ethaddr <the MAC address of the MON port> printenv ping 192.168.178.1 Test 2: with ethernet cable connected to LAN port Boot with kwboot, interrupt serialby bodhi - Debian
Joey, Just for completeness, do these tests again, but add these 2 setenvs after setenv ipaddr: setenv ipaddr 192.168.178.110 setenv gatewayip 192.168.178.1 setenv netmask 255.255.255.0 Your Test 2 did not make sense! The cable is in LAN port right?by bodhi - Debian
Chuck, Please post the entire serial console log. It is OK with the default envs to boot SATA, should be no problem. So it might be problem in how you created the HDD rootfs. And if you could, use txt file. Sometime people read this forum on portable devices that can't read .odt.by bodhi - uBoot
wolf Wrote: ------------------------------------------------------- > All right, Bodhi—parts ordered. I'll let you > know how it goes when they come in (should be a > month or so). Slow boat from China?:) That's why I always have 2 (CP2xx and Nokia CA cable). And the Nokia cable can be bought very quicky from where ever you are, just a thought. > Once again, greaby bodhi - uBoot
SirK79, > I used to have Zyxel NSA310 with debian but my hdd > failed recently and I am struggling to find > documentation on how to install it on fresh HDD ? > > Can you point me to such howto ? The same procedure is used whether you use USB or HDD. http://forum.doozan.com/read.php?2,12096 Use Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (20 Feb 2016) rootfsby bodhi - Debian
> After some work and many Thanks Obama since LEDE > devs don't cough up their secrets even after > waterboarding, :)) > This system allows them to hard-code mtdparts in > the dtb file so their kernel will ignore what > uboot gives them, and their rootfs will be able to > occupy the whole flash space instead of using only > a pre-made mtd partition andby bodhi - Rescue System
bobafetthotmail Wrote: ------------------------------------------------------- > I just posted a beta of a recovery firmware based > off LEDE, in the recovery section, can you sticky > it (act quickly, before it's covered by the > massive activity in that section :) ) Good job :) > > I should be able to post an updated version of the > script with what youby bodhi - uBoot
Chuck99 Wrote: ------------------------------------------------------- > Thanks.. I was going over this forum and found > you saying there is a work a round for bad block > in mtd0. I have bad address 0x0. What can I do? > When you flash it, post the log and I'll tell you if it went OK. The "work around" is really no trick. Just depending on the NAND spaceby bodhi - uBoot
wolf, > I think I would have freaked out if the flash went > wrong, so I don't believe the command gave any > feedback, nevertheless anything negative. If that's the case then uboot is running, blinking green. > > v4 but I have another Mobile I was planning to > flash after this one. Is that script ready for > use? Not yet. > I'm fine wiby bodhi - uBoot
mike, Then after booting into Debian, fw_setenv dtb_file '/boot/dts/kirkwood-pogoplug_v4.dtb' And move uEnv.txt to uEnv.txt.bak. If you still can't boot without uEnv.txt then use picocom to monitor serial console, capture the log and post here. If you don't have picocom, then in Debian, apt-get install picocomby bodhi - uBoot
8th perhaps is the charm :) Please try this 2.8 version. Test 1: with ethernet cable connected to MON port Boot with kwboot, interrupt serial console version setenv ipaddr <IP address of the ON100> setenv ethaddr <the MAC address of the MON port> ping <your router IP> Test 2: with ethernet cable connected to LAN port Boot with kwboot, interrupt serial consoleby bodhi - Debian
Chuck, I guess you have never used link shortening before? When you use Ubuntu browser to click on the link, bitly.com redirects your request to a real Dropbox link. And you have no problem. When you wget (at command line) using that shorten link, wget stores the file using the shorten link name as the file name, even if it was redirect to the real file. So whatever you are downloading, just rby bodhi - uBoot