Modify these 2 files (the bold lines below). /etc/udev/rules.d/70-persistent-net.rules # This file was automatically generated by the /lib/udev/write_net_rules # program, run by the persistent-net-generator.rules rules file. # # You can modify it, as long as you keep each rule on a single # line, and change only the value of the NAME= key. # Unknown net device (/devices/platform/mv64by bodhi - Debian
JoeyPogoPlugE02 Wrote: ------------------------------------------------------- > * Incense on the solder iron and old people > fasting and praying... > > Test 1 MON > > > > U-Boot 2016.05-tld-2.13 (Sep 13 2016 - 22:03:11 > -0700) > Cisco ON100_K9 > > SoC: Kirkwood 88F6282_A1 > DRAM: 512 MiB > WARNING: Caches not enabled > NAND:by bodhi - Debian
lijianch Wrote: ------------------------------------------------------- > I am using the pogo through SATA boot which > bypasses the NAND. I want to use a usb drive to > host debian system rather than booting from SATA. > > > I know that Bodhi has an instruction to flash the > new u-boot. However, my > > # cat /proc/mtd > mtd0: 08000000 00020000 "by bodhi - Debian
Now we are talking :) good troubleshooting Chuck. Here is the instruction: http://forum.doozan.com/read.php?2,25683,25688#msg-25688by bodhi - uBoot
Is it the cloned rootfs? Ie. untarred from the working one? There are 2 files need adjustment after cloning.by bodhi - uBoot
SirK79 Wrote: ------------------------------------------------------- > Is esata working on > Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 > on NSA310? Yes. It should. BTW, there are 3 variations of the NSA310. You should use the right one. /boot/dts/kirkwood-nsa310a.dtb /boot/dts/kirkwood-nsa310b-lmsensor-redusbled.dtb /boot/dts/kirkwood-nsa310.dtbby bodhi - Debian
Thanks Joey! good progress. egiga1 Waiting for PHY auto negotiation to complete..... done egiga0 Waiting for PHY auto negotiation to complete..... done But my incantation did not work completely :) Could you do the same test but with stock u-boot? meaning running putty to connect, and interrupt serial console, run test 1 and 2.by bodhi - Debian
This is why: the uEnv.txt exists in your rootfs /boot folder. So it was read during u-boot booting, and overwrote your existing envs. loading envs from usb 0 ... 2773 bytes read in 334 ms (7.8 KiB/s) no IDE devices available importing envs ... Boot into Debian and remove it by rename to someting else, and reboot cd /boot mv uEnv.txt uEnv.txt.bak sync shutdown -r nowby bodhi - uBoot
OK here we go, version 2.13. Light your incense, bow to 8 directions, and run test 1 and 2 :))by bodhi - Debian
> Really I wonder if there's some simple > "key" scheme that we aren't aware of, like both > Ethernet jacks need to be plugged-in or something > needs to be in the USB slot. I think, nothing like that (but you'd never know...). I'm not using stock u-boot ethernet code anymore. The ethernet PHYs have initialized. But looks like the auto negotiationby bodhi - Debian
This sounds too much like a bug in the PHY driver.by bodhi - Debian
Here is the kernel config file version config-4.6-mvebu-tld-1. You can use my kernel linux-4.6.0-kirkwood-tld-1 patch with it. QuoteUpdated 20 May 2016: Kernel linux-4.6.0-kirkwood-tld-1 package has been uploaded. The following features were added/updated: - Supports for Linksys EA4500. Use kirkwood-ea4500.dtb to boot this box. DSA (kirkwood-ea4500-dsa.dtb) is still a work-in-progress.by bodhi - Debian
Here you go Joey. I've increased the Auto Negotiation timeout period. Same test 1 and 2.by bodhi - Debian
Peacemaker Wrote: ------------------------------------------------------- > @Bodhi: do you mind sharing the Kernel 4.6 Armada > 38x build and configs (maybe patches if needed) > > Cheers Carl Sure, let me find it.by bodhi - Debian
Build 2.12 is ready to be tested. It will be uploaded when the tester feel like continuing :)by bodhi - Debian
> I think it needs new DTB for v4. No, there is no need for new DTB. The DTB file we have is OK. Or perhaps I misundersootd what you said? > I have decided to start over on v4-a3. It is a > mess. Kwboot is ok. What is best way to get ssh > working again so I can get the files needed? If you have a Pogo Mobile running, then just clone that USB rootfs to another drive anby bodhi - uBoot
In mainline u-boot there is nothing similar in a way that it could be used to run temporarily.by bodhi - uBoot
> SysClock = 533Mhz Yes, it's DDR3 RAM speed. > TClock = 200Mhz It's the core clock (5ns). Usually the Marvell SoCs that have even speed like 1Hhz, 1.2Hz, and 1.6Ghz have the core clock of 200Mhz. For the SoCs that have slower CPU, the core clock is 166.xxx MHz (6ns).by bodhi - uBoot
> > The HDD doesnt spin up at all, USB doesnt seems to > work. However ping works. It's a good sign. Meaning the ethernet chip is probably the same one (you need to find out for sure). But, of course, GPIOs are different. So that info must be extracted either from the stock u-boot, or from the reference manual (none available). Now you know that this NSA325 u-boot can be usby bodhi - uBoot
> So I'll redouble my efforts, but let me prepare... Take your time Joey. There is no need to rush anything. It will be done when it's done (TM) :) So let me know when you feel like continuing the testing.by bodhi - Debian
SirK79, > Hdd and system work with below, only annoying > thing is that leds do not work during boot up > process U-Boot 2013.07 (Sep 20 2013 - 15:45:03) ZyXEL NSA310 1-Bay Power Media Server Which u-boot is this? your own build or from somewhere? that might be the reason. My latest released u-boot should blink the LED correctly.by bodhi - Debian
SirK79 Wrote: ------------------------------------------------------- > I see how to works :) > > > root@NSA310:/home/krzysiek# echo 1 > > /sys/class/leds/nsa310\:green\:hdd/brightness > root@NSA310:/home/krzysiek# echo 0 > > /sys/class/leds/nsa310\:green\:hdd/brightnes > > > > will update /etc/rc.local scripts and post it for > other dby bodhi - Debian
BTW, it looks we are in/on the right track. The PHY was initialized. But the timeout value will need to be increased for this chip in this box.by bodhi - Debian
SirK79 Wrote: ------------------------------------------------------- > Once have Debian working on my NSA310 is there > know way to fix front panel light to be working ? Yes. I did not add that to the rootfs, since I released this before some of our members provided the listing of the LED class triggers. If nobody post it, you can get this listing and set it easily in /etc/rc/local:by bodhi - Debian
Joey, > Test 2 LAN > Fail, the pins again. I can't get it to the first > stage really. Gets to "please reboot the target" > and toggling power doesn't do anything. This is > going in the trash. Sorry I'm out. Damn :) sorry to hear. Try taking out the clock battery, unplug serial wires, and leave it unpowered for a few hours and power on again.by bodhi - Debian
Looks very similar to the NSA325. Try kwboot with the NSA325 u-boot image again, and with a USB drive and an HDD plugged in. Interrupt u-boot at count down and usb start ide reset and ping <your router IP address> Please post serial console log for this. Also find out which Ethernet chip this box has. It seems this chip it is different from one in the NSA325.by bodhi - uBoot
protocold, There might be one similar enough that I can compile for you. Let me take a look.by bodhi - uBoot
AdamPL, You can use create a new basic rootfs: Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (20 Feb 2016) Updated 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. Basic minimal Debian Kirkwood rootfs for most Kirwood plugs: - tarball size: 137M - install size: 398M - a basic jessie rootfs. -by bodhi - Debian
Here is version 2.11. Same test 1 and 2.by bodhi - Debian