Re: [OpenWrt-Devel] MV88E6060 switch

On Thu, Oct 12, 2017 at 2:05 AM, Nerijus Baliunas wrote: > On Thu, 12 Oct 2017 01:30:35 +0300 Sergey Ryazanov > wrote: > >> Try this patch, it should reduce the memory demand of the ethernet >> driver, so it will have the change to get

Re: [OpenWrt-Devel] MV88E6060 switch

On Thu, 12 Oct 2017 01:30:35 +0300 Sergey Ryazanov wrote: > Try this patch, it should reduce the memory demand of the ethernet > driver, so it will have the change to get started on your router. > > Just put it to target/linux/ixp4xx/patches-4.4 along with the previous

Re: [OpenWrt-Devel] MV88E6060 switch

On Thu, Oct 12, 2017 at 12:29 AM, Nerijus Baliunas wrote: > On Thu, 12 Oct 2017 00:15:15 +0300 Sergey Ryazanov > wrote: >> Can you boot in failsafe mode again, check free memory while the >> interface is Up, then bring it Down and check

Re: [OpenWrt-Devel] MV88E6060 switch

On Thu, 12 Oct 2017 00:15:15 +0300 Sergey Ryazanov wrote: > >> As a quick test, can you unload all kernel modules and try to set eth0 UP > >> again? > > > > Unfortunately rmmod with a list of modules does not work: > > # rmmod ip_tables ip6_tables ip6t_REJECT ... > >

Re: [OpenWrt-Devel] MV88E6060 switch

On Wed, Oct 11, 2017 at 11:44 PM, Nerijus Baliunas wrote: > On Wed, 11 Oct 2017 23:28:00 +0300 Sergey Ryazanov > wrote: > >> > root@LEDE:/# cat /proc/meminfo >> > MemTotal: 12232 kB >> > MemFree: 996 kB >> >> Looks like

Re: [OpenWrt-Devel] MV88E6060 switch

On Wed, 11 Oct 2017 23:28:00 +0300 Sergey Ryazanov wrote: > > root@LEDE:/# cat /proc/meminfo > > MemTotal: 12232 kB > > MemFree: 996 kB > > Looks like this ^^^ is the cause of the "ifconfig up" failure. Your > board really have not free RAM. > > As

Re: [OpenWrt-Devel] MV88E6060 switch

On Wed, Oct 11, 2017 at 11:01 PM, Nerijus Baliunas wrote: > On Wed, 11 Oct 2017 22:50:40 +0300 Sergey Ryazanov > wrote: > >> Khm, according to wikidevi your router is equipped with 16MB of RAM, >> the ethernet driver for xscale SoCs

Re: [OpenWrt-Devel] MV88E6060 switch

On Wed, Oct 11, 2017 at 7:17 PM, Nerijus Baliunas wrote: > On Wed, 11 Oct 2017 18:53:40 +0300 Sergey Ryazanov > wrote: > >> A-ha! The interface survives the down/up circle but does not survive >> the init procedure. >> >> Try to completely

Re: [OpenWrt-Devel] MV88E6060 switch

On Wed, 11 Oct 2017 18:53:40 +0300 Sergey Ryazanov wrote: > A-ha! The interface survives the down/up circle but does not survive > the init procedure. > > Try to completely avoid bridge usage, e.g.: > 1. boot in normal mode > 2. disable bridge usage on "lan": > #

Re: [OpenWrt-Devel] MV88E6060 switch

On Wed, Oct 11, 2017 at 3:17 PM, Nerijus Baliunas wrote: > On Wed, 11 Oct 2017 14:53:16 +0300 Sergey Ryazanov > wrote: >> Ok. At least we know now that the switch functioning (even without a >> dedicated driver). One question left: what

Re: [OpenWrt-Devel] MV88E6060 switch

On Wed, 11 Oct 2017 14:53:16 +0300 Sergey Ryazanov wrote: > Ok. At least we know now that the switch functioning (even without a > dedicated driver). One question left: what happens to the Ethernet > driver? > > Can you boot your router in failsafe mode again, and try

Re: [OpenWrt-Devel] MV88E6060 switch

On Wed, Oct 11, 2017 at 12:43 PM, Nerijus Baliunas wrote: > This works: > = FAILSAFE MODE active > # ifconfig -a > eth0 Link encap:Ethernet HWaddr 00:18:39:21:0D:AE > inet addr:192.168.1.1 Bcast:192.168.1.255

Re: [OpenWrt-Devel] MV88E6060 switch

On Wed, 11 Oct 2017 02:07:00 +0300 Sergey Ryazanov wrote: > Ok. I am starting to run out of ideas. Let's start guessing. > > eth0 works at least during preinit. You could check your switch > functioning in the failsafe mode: > 1. Power on router > 2. When the "Press the

Re: [OpenWrt-Devel] MV88E6060 switch

On Mon, Oct 9, 2017 at 1:58 AM, Nerijus Baliunas wrote: > On Mon, 9 Oct 2017 01:31:29 +0300 Sergey Ryazanov > wrote: > >> > Just tried: >> > # ifconfig eth0 192.168.0.10 up >> > ifconfig: SIOCSIFFLAGS: Out of memory >> > # dmesg|grep eth >>

Re: [OpenWrt-Devel] MV88E6060 switch

On Mon, 9 Oct 2017 01:31:29 +0300 Sergey Ryazanov wrote: > > Just tried: > > # ifconfig eth0 192.168.0.10 up > > ifconfig: SIOCSIFFLAGS: Out of memory > > # dmesg|grep eth > > [0.998445] eth0: MII PHY 32 on NPE-B > > [1.005134] eth1: MII PHY 1 on NPE-C > > [

Re: [OpenWrt-Devel] MV88E6060 switch

On Mon, Oct 9, 2017 at 12:00 AM, Nerijus Baliunas wrote: > On Sun, 8 Oct 2017 23:44:58 +0300 Sergey Ryazanov > wrote: >> > I assigned IP with a command >> > ip a a 192.168.0.10/24 dev eth0 >> > >> > but ping from PC does not answer. >> >>

Re: [OpenWrt-Devel] MV88E6060 switch

On Sun, 8 Oct 2017 23:44:58 +0300 Sergey Ryazanov wrote: > > I assigned IP with a command > > ip a a 192.168.0.10/24 dev eth0 > > > > but ping from PC does not answer. > > Have you bring eth0 UP? I mean, could you do "ifconfig eth0 > 192.168.0.10 up" and try pinging

Re: [OpenWrt-Devel] MV88E6060 switch

On Sun, Oct 8, 2017 at 11:12 PM, Nerijus Baliunas wrote: > I assigned IP with a command > ip a a 192.168.0.10/24 dev eth0 > > but ping from PC does not answer. > > ifconfig -a shows a few RX and TX packets: > eth0 Link encap:Ethernet HWaddr 00:18:39:21:0D:AE >

Re: [OpenWrt-Devel] MV88E6060 switch

On Tue, 3 Oct 2017 03:27:21 +0300 Sergey Ryazanov wrote: > After these lines, I carefully examine available data about WRT300Nv2 > and related code and found several interesting things. > > Usually SoC in the router have only one ethernet interface and vendors > pair it

Re: [OpenWrt-Devel] MV88E6060 switch

Hello Nerijus, On Fri, Sep 29, 2017 at 7:32 PM, Nerijus Baliunas wrote: > On Fri, 8 Sep 2017 22:50:13 +0300 Sergey Ryazanov > wrote: >> >> >> Did you see the "Marvell 88E6060 PHY driver attached" in kernel >> >> >> messages log?

Re: [OpenWrt-Devel] MV88E6060 switch

On Fri, Jul 28, 2017 at 1:03 AM, Nerijus Baliunas wrote: > On Thu, 27 Jul 2017 23:43:19 +0300 Sergey Ryazanov > wrote: > >> >> Did you see the "Marvell 88E6060 PHY driver attached" in kernel >> >> messages log? If not then the

Re: [OpenWrt-Devel] MV88E6060 switch

On Fri, 28 Jul 2017 01:03:16 +0300 Nerijus Baliunas wrote: > On Thu, 27 Jul 2017 23:43:19 +0300 Sergey Ryazanov > wrote: > > > >> Did you see the "Marvell 88E6060 PHY driver attached" in kernel > > >> messages log? If not then

Re: [OpenWrt-Devel] MV88E6060 switch

On Thu, 27 Jul 2017 23:43:19 +0300 Sergey Ryazanov wrote: > >> Did you see the "Marvell 88E6060 PHY driver attached" in kernel > >> messages log? If not then the mwswitch driver did not attached and > >> you should fix this first. And only then go to

Re: [OpenWrt-Devel] MV88E6060 switch

2017-07-21 01:41, Sergey Ryazanov rašė: You should disable CONFIG_NET_DSA_MV88E6060 and select only CONFIG_MVSWITCH_PHY=y option. This two different drivers, the first one is mainstream Linux driver, and the second one is OpenWRT specific driver, which is mach more simple and

Re: [OpenWrt-Devel] MV88E6060 switch

Hello Nerijus, Friday, July 21, 2017, 12:49:29 AM, you wrote: > 2017-07-21 00:36, Sergey Ryazanov rašė: >>> No received/sent packets on br-lan and eth0 before and after modprobe >>> mv88e6060.ko. >> >> Did you saw the "Marvel 88E6060 PHY driver attached" string in the >> kernel messages? If

Re: [OpenWrt-Devel] MV88E6060 switch

2017-07-21 00:36, Sergey Ryazanov rašė: No received/sent packets on br-lan and eth0 before and after modprobe mv88e6060.ko. Did you saw the "Marvel 88E6060 PHY driver attached" string in the kernel messages? If so then at least the driver detects switch chip. No. BTW, do I understand

Re: [OpenWrt-Devel] MV88E6060 switch

Hello Nerijus, Wednesday, July 19, 2017, 1:00:43 PM, you wrote: > 2017-07-19 04:02, Sergey Ryazanov rašė: >>> Linksys WRT300N v2.0 has Marvell 88e6060 switch. But ixp4xx arch does not >>> have >>> its driver enabled (ar71xx has it). I added CONFIG_NET_DSA_MV88E6060=m, >>> but when I modprobe

Re: [OpenWrt-Devel] MV88E6060 switch

2017-07-19 04:02, Sergey Ryazanov rašė: Linksys WRT300N v2.0 has Marvell 88e6060 switch. But ixp4xx arch does not have its driver enabled (ar71xx has it). I added CONFIG_NET_DSA_MV88E6060=m, but when I modprobe mv88e6060.ko, nothing happens. It seems driver does not hook on any hardware:

Re: [OpenWrt-Devel] MV88E6060 switch

Forgot CC lede-dev > Linksys WRT300N v2.0 has Marvell 88e6060 switch. But ixp4xx arch does not have > its driver enabled (ar71xx has it). I added CONFIG_NET_DSA_MV88E6060=m, > but when I modprobe mv88e6060.ko, nothing happens. It seems driver does not > hook > on any hardware: This happened

Re: [OpenWrt-Devel] MV88E6060 switch

On Mon, Jul 17, 2017 at 5:29 PM, Nerijus Baliunas wrote: > Linksys WRT300N v2.0 has Marvell 88e6060 switch. But ixp4xx arch does not have > its driver enabled (ar71xx has it). I added CONFIG_NET_DSA_MV88E6060=m, > but when I modprobe mv88e6060.ko, nothing happens.