The correct spelling: lsusb Mnemonic: list commands always starts with ls (lsusb, lspci, lsblk,....).by bodhi - Debian
I think the problem as pbg4 described above is the most likely solution. Hence I suggested above to look at shutdown sequence differences, see if we can keep the PHY alive. The Power resume GPIO is not in the 320S DTS, but perhaps it can be found in the 310S GPL. Let's see if we can find all the GPIO definition in it :)by bodhi - Debian
Joey, apt-get install usbutils You can also use fdisk -l to list partitions, which will tell whether this USB is connected or not.by bodhi - Debian
Vinay, > How do i know the installation went right? Your envs look good. Are you booting with the new 3.16 rootfs on USB? If that is true then please reboot shutdown -r now And post the output of dmesg mountby bodhi - Debian
Did you do "shutdown -h now"? If you did, then let's wait for pengu and compare the 2 shutdown sequences.by bodhi - Debian
superelchi, In the script /etc/init.d/halt, try changing NETDOWN to not shutting down the ethernet. #! /bin/sh -x ### BEGIN INIT INFO # Provides: halt # Required-Start: # Required-Stop: # Default-Start: # Default-Stop: 0 # Short-Description: Execute the halt command. # Description: ### END INIT INFO NETDOWN=noby bodhi - Debian
superelchi Wrote: ------------------------------------------------------- > bodhi Wrote: > -------------------------------------------------- > ----- > > All, > > > > How about doing this test. We should compare > the > > shutdown sequence between the box that worked > > (pengu's) and the boxes that did not work > > (superlechi'by bodhi - Debian
All, How about doing this test. We should compare the Debian shutdown sequence between the box that worked (pengu's) and the boxes that did not work (superlechi's, Johnny's). In the 1st line of these scripts: /etc/init.d/halt /etc/init.d/reboot turn on the script echo so that we can see in the serial log whether the shutdown and reboot actions were the same in both cases:by bodhi - Debian
All, I'd like to see the whole boot log into stock Zyxel OS. Could someone pastebin?by bodhi - Debian
@pbg4, More research: regarding Marvell register initial values, it was accepted into the mainline 4.1! so this acceptable. grep -5 'reg-init' /usr/src/linux-4.1-tld/arch/arm/boot/dts/zynq-parallella.dts ethernet_phy: ethernet-phy@0 { /* Marvell 88E1318 */ compatible = "ethernet-phy-id0141.0e90", "ethernet-phy-ieee802.3-c22"; reby bodhi - Debian
JohnnyUSA Wrote: ------------------------------------------------------- > bodhi, > > tried the new dtb file: > > > > Starting kernel ... > > Uncompressing Linux... done, booting the kernel. > > Error: unrecognized/unsupported machine ID (r1 = > 0x0000020f). > > Available machine support: > > ID (hex) NAME > ffffby bodhi - Debian
Ok here is another DTB version to try :). I've made the 2 LAN chips compatible devices in the definition, and they have the same init sequence. I've included both DTB and DTS in this tarball.by bodhi - Debian
pbg4, > but the protocols pengu just posted show that they > are poking register settings on startup, to > activate the phy, > that's really weird,.. I think because their u-boot does not take care of this step. They have to do it in the OS. Zyxel (and other embedded manufacturers) has this pattern of development, i.e. they take a lot shortcuts like this. > becauby bodhi - Debian
Hi pbg4, > for the NSA310S you simply have to change the gpio > numbers, because of the different gpio numbering, > which you should look up and change accordingly, > and try if Zyxel used the same design on the > NSA310S,.. > Yes. I did use your post's idea, and I've asked Johnny to try GPIO 26. Looking at the DTS, that was the only one seems feasible.by bodhi - Debian
Sorry guys :) looks like we're back to square 1 :)) The dmesg superelchi posted above is very crucial. Exactly what Zyxel OS did to bring up the Ethernet. And it was what the NSA320S DTS specified. So even though it is a different LAN chip, the init sequence is the same!!! Please go back to use the 320S DTS in the mean time. I'll modify it and post another version.by bodhi - Debian
To add another data point to the Sandisk Ultra Fit 3.0 drives issue. If anyone has trouble using this drive, try to plug it in a Belkin USB 2.0 hub. It seems to work really well, perhaps it will test the theory of the drive timing problem that pepar and some of us has experienced.by bodhi - Debian
superelchi, > Would it be of any use if I try to get the Linux > GPL sources for the NSA-310S from ZyXel? Or is the > ethernet driver/init closed source? Yes, absolutely, if you can get it. If I have the GPL source, I could try to get new u-boot working, too.by bodhi - Debian
Hy3n4 Wrote: ------------------------------------------------------- > Hi bodhi and thank you for your reply. > > Unfortunately I can see nothing more than "Sending > boot message. Please reboot the target.../" and TX > led on UART is blinking like crazy. So it probably > tries to send boot code but no one is responding > on the other side. > > I tby bodhi - uBoot
t3ch42, > Are you required to flash the old uboot for the > pogo stock? If so, do you lose the option of > booting Debian? No, my educated guess that stock u-boot is not required (I know my u-boot image should be able to boot stock OS). However, I recall graymanforhire has written up instruction for Pogo V4 that chainboot stock Dockstar u-boot and that run Pogo OS from NAND. Iby bodhi - Rescue System
Davide, preboot=setenv stderr serial; setenv stdin serial; setenv stdout serial; setenv baudrate 115200; setenv console ttyS0,115200; setenv bootdelay 10 preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi preboot should be preboot=run preboot_nc Other thanby bodhi - uBoot
JohnnyUSA Wrote: ------------------------------------------------------- > @superelchi, could be my date/time modifications > to blame for that error of mine. That's why I've suggested to use static IP only, so to eliminate any other misleading errors!by bodhi - Debian
t3ch42 Wrote: ------------------------------------------------------- > With my issues of late, I was wondering if there > had been any progress or success with the pp v4. > Looking at some of the listed variants, it seems > to be enough room in the memory. > Can anyone confirm a working rescue or "other" > running from the nand? Definitely. I've beenby bodhi - Rescue System
Patrik, 1. Even though this SoC supports UART booting, there are several 88F6281 boxes don't have it. So it's not surprising that your box might be one. What do you see when running kwboot? does the box respond at all? or responded with error? 2. If booting with a working serial console, and seeing nothing comes out, then it means the u-boot in NAND did not start. Most likely a baby bodhi - uBoot
Davide, > @bodhi: which u-boot version should I rollback for > test? the one in this thread ? (tld-3 ?) Yes. tld-3 for NSA325.by bodhi - uBoot
superelchi Wrote: ------------------------------------------------------- > With the new DTB: > > > root@debian:~# ifconfig -a > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:65536 > Metric:1 > RX packets:0 errors:0 dropped:0by bodhi - Debian
Here is another version for the DTB. Please extract and recreate uImage with it. Cross fingers and reboot :).by bodhi - Debian
superelchi, > And another one: Wake On LAN works always - after > coldboot, reboot and poweroff. Does not matter if > network is working or not. This is a good one! it means no problem with router (it does know where the box is, based on MAC address). Now it should be stock u-boot where it occurs....by bodhi - Debian
@miksi, Yup, it is hard to tell what could have been the problem without the installation log. And if netconsole was not set up properly or can't connected now, then serial console is the only way to tell. The LED behavior indicates that u-boot did not attempt to load the kernel at all, so it is likely some u-boot env settings problem. See this thread for serial console hardware: httpby bodhi - uBoot
Vinay Wrote: ------------------------------------------------------- > So i should use a new usb stick? Can't i just > format the old non working one as ext3 partition > and use it? > Can't i use the 4.xx version build? Is it because > of old uboot? Any way to upgrade my old uboot to > new one? > Sorry if i sound like an irritating kid. :) You should booby bodhi - Debian