Show all posts by user

Re: Zyxel NAS326 - Debian / Boot from USB? - Today

jave, > KEY_133:shutdown -h now > KEY_116:<what You need or wish> Thanks for the info about the key. It seems esekeyd has some problem and need to be updated to properly recognize standard Linux keys. > - biggest problem of the NAS326 - is not > working WOL (working well for my NSA325v1) > - Bodhi, are You please able to summarize Your > statements relatin

by bodhi - Debian

Re: armada 370 (88f6710) mainline uboot support - 2 days ago

wacke, I see. This does not help. linuxpro's version is the old approach that does not fully activate the DSA switch the way we want it. mvsw61xx { compatible = "marvell,mv88e6085"; status = "okay"; reg = <0x10>; mii-bus = <0xc>; cpu-port-0 = <0x5>; cpu-port-1 = <0x6>; is-indirect; }; The OpenWrt Linksys EA4500 s

by bodhi - uBoot

Re: armada 370 (88f6710) mainline uboot support - 2 days ago

wacke, > The oem system was a customized openwrt(AA) that > build from marvell sdk. > The bootlog see: > https://forum.archive.openwrt.org/viewtopic.php?id=50173&p=17#p237049 Can you search the current OpenWrt forum for this user's posts In the archive link https://forum.archive.openwrt.org/viewtopic.php?id=50173&p=17#p237049 This post seems to tell th

by bodhi - uBoot

Re: armada 370 (88f6710) mainline uboot support - 2 days ago

wacke, > I've booted up my box with this dts: > // SPDX-License-Identifier: (GPL-2.0+ OR MIT) > /* > * Device Tree file for Marvell Armada 370 > Reference Design board > * (RD-88F6710-A1) Why do you choose this DTS? is it closer to your box than one you used before? > I'm confusing about the 6171 switch's base > address, my box must set to 0

by bodhi - uBoot

Re: armada370 serial port that can send but not receive - 2 days ago

Perhaps there is generic IRQ mapping going on here, so [ 1.231269] d0012000.serial: ttyS0 at MMIO 0xd0012000 (irq = 19, base_baud = 12500000) is a 16550A [ 2.039621] d0012100.serial: ttyS1 at MMIO 0xd0012100 (irq = 20, base_baud = 12500000) is a 16550A are actually 41 and 42.

by bodhi - Debian

Re: armada 370 (88f6710) mainline uboot support - 3 days ago

wacke, I'm not saying this is the problem. But usually we avoid doing this if we can. The ethernet nodes were already defined in the DTSI. If you redefine them, you could inadvertenly change some characteristics of the device in the node. The basic rule is: we always take the DTSI definition, and modify some attributes for the box. internal-regs { ..... ethernet@70000

by bodhi - uBoot

Re: armada370 serial port that can send but not receive - 3 days ago

Ah! stock is always correct, of course. And the DTSI is using that. armada-370-xp.dtsi uart0: serial@12000 { compatible = "snps,dw-apb-uart"; reg = <0x12000 0x100>; reg-shift = <2>; interrupts = <41>;

by bodhi - Debian

Re: armada 370 (88f6710) mainline uboot support - 3 days ago

wacke, Please post your full DTS file.

by bodhi - uBoot

Re: armada370 serial port that can send but not receive - 3 days ago

That uart1 pins are mpp41, mmp42 and I too did not see anything in your DTS that grabs the pin. What are bout IRQ? uart1 IRQ is 42.

by bodhi - Debian

Re: armada370 serial port that can send but not receive - 3 days ago

> Even if it was I would still find this odd, at > least if it were stdout/stderr since those are all > "output" and output is what is succeeding for me. I am a little bit unclear. I though you can execute commands but did not get any output back?

by bodhi - Debian

Re: NSA 325 V2 Debian Is Possible! - 3 days ago

szucsati, > Well, I should try to find that memory stick then > :). At some point I will want to sell this, and > would be useful to have the chance to get back to > the official (and outdated) software. > Isn't mtd0 only the uBoot partition? If I erased > that, wouldn't I still have the OS? Yes, it you've erased mtd only, then stock OS is still intact

by bodhi - Debian

Re: armada370 serial port that can send but not receive - 3 days ago

> Has anyone run into a similar situation where they > could only send data one-way like this? I have seen it, but only when one of these scenarios is true: - The serial console command has a different settings (baud rate,...) that the box is expecting. - u-boot envs for stdin/stdout/stderr were set to wrong values. If stock FW works for both directions, then you should at least

by bodhi - Debian

Re: Buffalo Terastation III TS-X4.0L/r5 (Sakura) From Stock 1.71(Buffalo Latest FW) ==>Debian Jessie/Stretch - 3 days ago

jeremy, You're limited your options quite a bit without changing u-boot envs. Assuming you have full serial, as with other boxes, you can do setenv without saving for testing purpose until you know that it works. And then save it. So it is very safe to do. There are certain u-boot envs that you want to avoid changing, but things like kernel load addresses and bootargs are quite safe t

by bodhi - Debian

Re: armada 370 (88f6710) mainline uboot support - 3 days ago

wacke, Here is the full dmesg for the EA4500. Perhaps so you can compare it with yours to see if there is any clue. root@EA4500:~# dmesg [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.19.0-kirkwood-tld-1 (root@tldDebian) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)) #1 PREEMPT Mon Oct 22 17:08:01 PDT 2018 [ 0.000000] CPU: Feroceon 88FR131

by bodhi - uBoot

Re: armada 370 (88f6710) mainline uboot support - 3 days ago

wacke, > Hi bodhi, > Did the EA4500 using the kernel DSA switch driver > or using the mvsw61xx driver? It has an almost identical DTS as your RT NAS DTS. It uses the same DSA driver. You can compare yours with the EA4500 DTS (in my kernel realease tarball).

by bodhi - uBoot

Re: NSA 325 V2 Debian Is Possible! - 3 days ago

szucsati, > Oh, it's good to know, I don't know why I thought > it would. Is there a way to set it up though to > fall back to NAND of there's no usb or sata device > with rootfs? Or at least to manually configure it > to boot from there should one would like to boot > stock FW? As I said, not possible at the moment. Typically, stock OS is on NAND. The

by bodhi - Debian

Re: Buffalo Terastation III TS-X4.0L/r5 (Sakura) From Stock 1.71(Buffalo Latest FW) ==>Debian Jessie/Stretch - 4 days ago

Here is the good load address for uInitrd: 32MB. 0x2100000

by bodhi - Debian

Re: armada 370 (88f6710) mainline uboot support - 4 days ago

Here is the benchmark. Linksys EA4500 has the Marvell DSA switch 6171R, Kirkwood SoC 88F6282. Linksys EA4500 [ 8.646156] mv88e6085 f1072004.mdio-bus-mii:10: switch 0x1710 detected: Marvell 88E6171, revision 2 [ 30.802804] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled [ 34.436399] mv88e6085 f1072004.mdio-bus-mii:10 ethernet1:

by bodhi - uBoot

Re: Buffalo Terastation III TS-X4.0L/r5 (Sakura) From Stock 1.71(Buffalo Latest FW) ==>Debian Jessie/Stretch - 4 days ago

1000001101000 Wrote: ------------------------------------------------------- > i'm still scratching my head with the initrd > issue. I don't think it's getting truncated and I > think I have the relavant kernel settings > enabled. > Initrd was corrupted. That was due to the memory reallocation (or lack thereof) by this old stock uboot. So either change to

by bodhi - Debian

Re: NSA 325 V2 Debian Is Possible! - 4 days ago

szucsati Wrote: ------------------------------------------------------- > First of all, big thank you for all who > contributed to this project. It's awesome to have > Debian running on this old hardware. > > I have one question (or problem) though. I have > the latest uBoot installed, should it boot the > factory software if no rootfs partition is found? >

by bodhi - Debian

Re: Buffalo Terastation III TS-X4.0L/r5 (Sakura) From Stock 1.71(Buffalo Latest FW) ==>Debian Jessie/Stretch - 4 days ago

> The uImage was ~2.5M. That hopefully will make it easy to solve the rootfs mounting problem by using uInitrd. > It looks like that defconfig doesn't include > initrd support for some reason, which explains > alot. Admittedly the initrd I was trying to use > would have caused it's own problems but I'm > working on that. I think you should make a s

by bodhi - Debian

Re: Buffalo Terastation III TS-X4.0L/r5 (Sakura) From Stock 1.71(Buffalo Latest FW) ==>Debian Jessie/Stretch - 4 days ago

Cool! What is the size of your uImage? And can you post the serial console boot log (if you have it).

by bodhi - Debian

Re: armada 370 (88f6710) mainline uboot support - 4 days ago

But you are reasonable to suspect that the CPU got involve too much in this. I wlll boot up the Linksys EA4500 when I have some free time.

by bodhi - uBoot

Re: armada 370 (88f6710) mainline uboot support - 4 days ago

wacke, I dont think so. Look back at the iperf test I did for Mirabox. It is Armada 370, which has no HW IO coherency, like your box. But the result is more than twice faster.

by bodhi - uBoot

Re: Buffalo Terastation III TS-X4.0L/r5 (Sakura) From Stock 1.71(Buffalo Latest FW) ==>Debian Jessie/Stretch - 5 days ago

Error: unrecognized/unsupported machine ID (r1 = 0x00000a89). Available machine support: ID (hex) NAME This told me it expects a device tree appended to it. So you probably need to remove any DT config switches.

by bodhi - Debian

Re: Buffalo Terastation III TS-X4.0L/r5 (Sakura) From Stock 1.71(Buffalo Latest FW) ==>Debian Jessie/Stretch - 5 days ago

Sure, if that happens to be too time consuming. Then QuoteIf necessary i can even change uboot parameters from userspace under the stock firmware to enable verbose kernel output/etc. I'm just hesitant to do so since I don't have a way to fix it if I screw something up sufficiently badly, and because getting that working will be a bit of a pain. To be able to set envs in stock would

by bodhi - Debian

Re: Goflex net upgrade went awry - 5 days ago

jj, > There are some boot env settings that need to be > set when installing LEDE. Could you please shed me > some light upon what will be the correct boot env. > settings for gfn, especially the mtdparts > variable? In the procedure that I mentioned: https://forum.doozan.com/read.php?4,42279 The only thing you need to change is the file names for lede-kirkwood-

by bodhi - Debian

Re: /boot/uEnv.txt ignored - 5 days ago

balanga, I have answered this question before: https://forum.doozan.com/read.php?3,80444,80539#msg-80539 Basically, you can not redefine bootcmd and bootcmd_uenv using uEnv.txt. So define a bootcmd_bsd that piggy back to the default bootcmd like I suggested above. Actually you could, but I purposely exclude them in the current default envs (to ensure that users mistakes in setting env

by bodhi - uBoot

Re: Buffalo Terastation III TS-X4.0L/r5 (Sakura) From Stock 1.71(Buffalo Latest FW) ==>Debian Jessie/Stretch - 5 days ago

1000001101000 Wrote: ------------------------------------------------------- > Looks like I need to add these options: > > CONFIG_ARCH_MV78XX0=y > CONFIG_MACH_TERASTATION_WXL=y > > Any chance one of your kernels already has them? Unfortunately, none of them has this turned on.

by bodhi - Debian

Re: Buffalo Terastation III TS-X4.0L/r5 (Sakura) From Stock 1.71(Buffalo Latest FW) ==>Debian Jessie/Stretch - 5 days ago

1000001101000 Wrote: > My new favorite is that they trigger a > watchdog timer in a separate microcontroller > before booting the kernel and then rely on the > firmware to turn it off if the system boots > successfully. It took me an embarrassingly long > time to figure out why the TS3400 was rebooting > every 4 hour hours like clockwork. Yeah, you could turn it o

by bodhi - Debian