Now since it's working with the work around. I'd suggest the next step is to look at the DTS. In the DTS, these register values were specified already in eth PHY. What would be the difference that caused Debian to ignore these values? I am suspecting that the "compatible" field was the culprit. So I've added both chips to the list. However, we don't know for sureby bodhi - Debian
superelchi, > The "NSA-310S" is internally names "STG315" and I > assume it's mapped to a #define > "CONFIG_MitraStar_STG315" (didn't find out where > this is done so far). > > As you also found there is: > > STG315_Kernel.config:# CONFIG_ZYXEL_POWER_RESUME > is not set > and that's because in > trunk/linby bodhi - Debian
It seems as though you guys have different versions of the NSA310S :) Furthermore, I'm thinking even though GPIO 47 and 49 are common for NSA3xx, they might not be used in the 310S that is not working (I am still digging in GPL code, and we don't know if this GPL reflects the latest FW). Wish I have my NSA325 at home to double check this too. I've attached the GPIO tool binary iby bodhi - Debian
Vinay Wrote: ------------------------------------------------------- > Sorry. I think I messed up. I didn't do this part > you asked me to. > After booted into Debian successfuly, then > move on to install new u-boot. > > I'm also getting some locale errors. I tried > installing locales, but it does not go away. > Will look at how to install uboot firby bodhi - Debian
Nematocyst Wrote: ------------------------------------------------------- > Ok, I fixed it. Suspecting there might be a > problem with u-boot's decompression, I disabled > compression on that file. > > chattr -c /boot/uImage > cp /boot/uImage /tmp/uImage > cp /tmp/uImage /boot/uImage > lsattr /boot/uImage > > > 1) disable compression > 2) coby bodhi - Debian
Nematocyst Wrote: ------------------------------------------------------- > There are solutions I can do that sort of ignore > the details. Like I could set up uboot to use > tftp. or I could copy the filesystem to a flash > drive, and then reformat and copy back. Those > would probably both work. Just then I wouldn't > know what is going on and thus have no ideaby bodhi - Debian
pengu Wrote: ------------------------------------------------------- > done, now the device is shown as still up (1000 > baseT-FD) > this doesn't change when U-Boot is up and > running. > pinging is now possible. > > when powering up, the green LED flashes shortly > and goes of > booting into debian makes the amber LED flashing > when the driver isby bodhi - Debian
Nematocyst Wrote: ------------------------------------------------------- > I have debian installed on a UBIFS volume, and I > get this error when booting: > Loading file '/boot/uImage' to addr 0x00800000 > with size 2082196 (0x001fc594)... > UBIFS error (pid 0): read_block: bad data node > (block 508, inode 51788) > UBIFS error (pid 0): do_readpage: cannotby bodhi - Debian
If I am right, it looks like an oversight in Zyxel 310S build: root@tldDebian:/usr/src/nsa310s-gpl/trunk/linux-2.6.31.8# grep CONFIG_ZYXEL_POWER_RESUME *.config NSA310_Kernel.config:# CONFIG_ZYXEL_POWER_RESUME is not set NSA310OBM_Kernel.config:# CONFIG_ZYXEL_POWER_RESUME is not set NSA320_Kernel.config:CONFIG_ZYXEL_POWER_RESUME=y NSA325_Kernel.config:CONFIG_ZYXEL_POWER_RESUME=y SGW_Kerby bodhi - Debian
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