DIR-300 revb build 18687 breaks LAN

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Ralink SoC based Hardware
Goto page 1, 2, 3, 4  Next
Author Message
cybero2912
DD-WRT Guru


Joined: 18 Jun 2006
Posts: 1177
Location: Berlin

PostPosted: Mon Mar 12, 2012 10:28    Post subject: DIR-300 revb build 18687 breaks LAN Reply with quote
LAN ports down after upgrade to r18687
also LED off
flashed back to 18007 via WIFI and LAN is back again
Sponsor
netcaster
DD-WRT Novice


Joined: 14 Mar 2012
Posts: 3

PostPosted: Wed Mar 14, 2012 16:11    Post subject: Reply with quote
I can confim the LAN problem on two DIR-300b routers!

tryed both dd-wrt build 18687 versions.
the update version from 18007 to 18687 and the factory version from original d-link firmware to 18687.

After flash the switch seems to be dead, like described above. I tryed a reset to dd-wrt defaults = same problem.

i remember, that the 18024 (the one before 18687) version had the same problem.

brainslayer said: that he tested it on a dir-600b (same hardware) and it worked.
http://svn.dd-wrt.com:8000/ticket/2426

it seems that there is still a problem with the switch. so I'm a litte bit confused about the things he said: "its working with that build. so i will not care about it forever".

did that mean we have to stuck with 18007 or a broken switch?

maybe someone have a clue - how we can bring to switch to work?
cybero2912
DD-WRT Guru


Joined: 18 Jun 2006
Posts: 1177
Location: Berlin

PostPosted: Wed Mar 14, 2012 16:30    Post subject: Reply with quote
netcaster wrote:
it seems that there is still a problem with the switch. so I'm a litte bit confused about the things he said: "its working with that build. so i will not care about it forever".

did that mean we have to stuck with 18007 or a broken switch?

hopefully not Sad
I reopened the ticket..
LOM
DD-WRT Guru


Joined: 28 Dec 2008
Posts: 7020

PostPosted: Wed Mar 14, 2012 16:36    Post subject: Reply with quote
Someone should do a log of the boot up sequence, preferably with via a serial terminal connection, for the latest build and for the latest working build.

The comment that he doesn't care about it since it works for him tells me that you will need to find the problem yourself and then convince him that he is wrong.
You will need strong evidence..

There are a bunch of 600b and 300b users reporting this problem so I don't doubt that the problem is real.
LOM
DD-WRT Guru


Joined: 28 Dec 2008
Posts: 7020

PostPosted: Wed Mar 14, 2012 16:52    Post subject: Reply with quote
cybero2912 wrote:
netcaster wrote:
it seems that there is still a problem with the switch. so I'm a litte bit confused about the things he said: "its working with that build. so i will not care about it forever".

did that mean we have to stuck with 18007 or a broken switch?

hopefully not Sad
I reopened the ticket..


Reopening the ticket without supplying any additional information for Brainslayer to go on is not very constructive.
It is a developers nightmare when it "works for me" but not for others and then not getting any hints of where the problem could be.
BrainSlayer
Site Admin


Joined: 06 Jun 2006
Posts: 5969
Location: Dresden, Germany

PostPosted: Wed Mar 14, 2012 20:45    Post subject: Reply with quote
okay. different approach. could someone setup such a device as wifi client and provide me remote login with ssh. so i can review it from the console. a computer should be connected on the lan port (or another ethernet device). so i can check the switch functions. just contact me with email with the connection details and i will do my best to get this resolved
_________________
one cigarette costs 2 minutes of your life.
one bottle of beer costs 4 minutes of your life.
one working day costs 8 hours of your life.

DD-WRT supported Concerts @ Bunker Dresden
6.4. - Black Celebration Depeche Mode Fanmeeting LIVE: Blind Passenger vs. Modular Majesty
28.6. - Fixmer & McCarthy
17.8. - Frontline Assembly & Haujobb
Pondera
DD-WRT Novice


Joined: 14 Mar 2012
Posts: 24
Location: Italy

PostPosted: Wed Mar 14, 2012 22:33    Post subject: Reply with quote
There is the same switch issue on DIR-300/600 Bx and DIR-615 Dx.
With a DIR-615 D1 I noticed that WAN port is fully operative when LAN switch doesn't work. So you can reassign the WAN port to LAN port and you can do a downgrade to a working LAN switch firmware version.
I don't know if it helps.
netcaster
DD-WRT Novice


Joined: 14 Mar 2012
Posts: 3

PostPosted: Wed Mar 14, 2012 22:36    Post subject: Reply with quote
well, I grabbed the logfile over wlan (wlan is working).

It's from a DIR-600b (same Hardware + Problem as DIR-300b).

Hope you can see where the problem is.

If you still need ssh access, I guess I can setup one for you. Just let me know, I set it up and check if the ssh access to the broken device works.

cheers & THX for your support!


build 18007 - switch working:

Code:
Jan  1 00:00:05 DD-WRT syslog.info syslogd started: BusyBox v1.19.3
Jan  1 00:00:05 DD-WRT user.info syslog: syslogd : syslog daemon successfully started
Jan  1 00:00:05 DD-WRT user.info syslog: klogd : klog daemon successfully started
Jan  1 00:00:05 DD-WRT kern.notice kernel: klogd started: BusyBox v1.19.3 (2011-12-14 09:24:30 CET)
Jan  1 00:00:05 DD-WRT kern.notice kernel: Linux version 2.6.23.17 (root@dd-wrt) (gcc version 4.5.4 20110526 (prerelease) (Linaro GCC 4.5-2011.06-0) ) #2571 Wed Dec 14 09:22:18 CET 2011
Jan  1 00:00:05 DD-WRT kern.warn kernel:  The CPU frequency set to 320 MHz
Jan  1 00:00:05 DD-WRT kern.info kernel: 32M RAM Detected!
Jan  1 00:00:05 DD-WRT kern.warn kernel: CPU revision is: 0001964c
Jan  1 00:00:05 DD-WRT kern.warn kernel: Determined physical RAM map:
Jan  1 00:00:05 DD-WRT kern.warn kernel:  memory: 02000000 @ 00000000 (usable)
Jan  1 00:00:05 DD-WRT kern.debug kernel: On node 0 totalpages: 8192
Jan  1 00:00:05 DD-WRT kern.debug kernel:   Normal zone: 64 pages used for memmap
Jan  1 00:00:05 DD-WRT kern.debug kernel:   Normal zone: 0 pages reserved
Jan  1 00:00:05 DD-WRT kern.debug kernel:   Normal zone: 8128 pages, LIFO batch:0
Jan  1 00:00:05 DD-WRT kern.debug kernel:   Movable zone: 0 pages used for memmap
Jan  1 00:00:05 DD-WRT kern.warn kernel: Built 1 zonelists in Zone order.  Total pages: 8128
Jan  1 00:00:05 DD-WRT kern.notice kernel: Kernel command line: console=ttyS1,57600n8 root=/dev/mtdblock4 rootfstype=squashfs noinitrd
Jan  1 00:00:05 DD-WRT kern.warn kernel: Primary instruction cache 16kB, physically tagged, 4-way, linesize 32 bytes.
Jan  1 00:00:05 DD-WRT kern.warn kernel: Primary data cache 16kB, 4-way, linesize 32 bytes.
Jan  1 00:00:05 DD-WRT kern.info kernel: Synthesized TLB refill handler (20 instructions).
Jan  1 00:00:05 DD-WRT kern.info kernel: Synthesized TLB load handler fastpath (32 instructions).
Jan  1 00:00:05 DD-WRT kern.info kernel: Synthesized TLB store handler fastpath (32 instructions).
Jan  1 00:00:05 DD-WRT kern.info kernel: Synthesized TLB modify handler fastpath (31 instructions).
Jan  1 00:00:05 DD-WRT kern.info kernel: Cache parity protection disabled
Jan  1 00:00:05 DD-WRT kern.warn kernel: cause = 10800020, status = 1100ff00
Jan  1 00:00:05 DD-WRT kern.warn kernel: PID hash table entries: 128 (order: 7, 512 bytes)
Jan  1 00:00:05 DD-WRT kern.warn kernel: calculating r4koff... 0030d400(3200000)
Jan  1 00:00:05 DD-WRT kern.warn kernel: CPU frequency 320.00 MHz
Jan  1 00:00:05 DD-WRT kern.warn kernel: Using 160.000 MHz high precision timer.
Jan  1 00:00:05 DD-WRT kern.info kernel: console [ttyS1] enabled
Jan  1 00:00:05 DD-WRT kern.info kernel: Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Jan  1 00:00:05 DD-WRT kern.info kernel: Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Jan  1 00:00:05 DD-WRT kern.info kernel: Memory: 29532k/32768k available (2121k kernel code, 3236k reserved, 318k data, 112k init, 0k highmem)
Jan  1 00:00:05 DD-WRT kern.debug kernel: Calibrating delay loop... 212.99 BogoMIPS (lpj=1064960)
Jan  1 00:00:05 DD-WRT kern.info kernel: PPPoL2TP kernel driver, V1.0
Jan  1 00:00:05 DD-WRT kern.info kernel: tun: Universal TUN/TAP device driver, 1.6
Jan  1 00:00:05 DD-WRT kern.info kernel: tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jan  1 00:00:05 DD-WRT kern.notice kernel: ralink flash device: 0x1000000 at 0xbf000000
Jan  1 00:00:05 DD-WRT kern.info kernel: Ralink SoC physically mapped flash: Found 1 x16 devices at 0x0 in 16-bit bank
Jan  1 00:00:05 DD-WRT kern.debug kernel: Ralink SoC physically mapped flash: Found an alias at 0x400000 for the chip at 0x0
Jan  1 00:00:05 DD-WRT kern.debug kernel: Ralink SoC physically mapped flash: Found an alias at 0x800000 for the chip at 0x0
Jan  1 00:00:05 DD-WRT kern.debug kernel: Ralink SoC physically mapped flash: Found an alias at 0xc00000 for the chip at 0x0
Jan  1 00:00:05 DD-WRT kern.warn kernel:  Amd/Fujitsu Extended Query Table at 0x0040
Jan  1 00:00:05 DD-WRT kern.notice kernel: number of CFI chips: 1
Jan  1 00:00:05 DD-WRT kern.notice kernel: cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
Jan  1 00:00:05 DD-WRT kern.warn kernel: found squashfs at 127000
Jan  1 00:00:05 DD-WRT kern.notice kernel: Creating 6 MTD partitions on "Ralink SoC physically mapped flash":
Jan  1 00:00:05 DD-WRT kern.notice kernel: 0x00000000-0x00030000 : "uboot"
Jan  1 00:00:05 DD-WRT kern.notice kernel: 0x00030000-0x00040000 : "uboot-config"
Jan  1 00:00:05 DD-WRT kern.notice kernel: 0x00040000-0x00050000 : "factory-defaults"
Jan  1 00:00:05 DD-WRT kern.notice kernel: 0x00050000-0x003f0000 : "linux"
Jan  1 00:00:05 DD-WRT kern.notice kernel: 0x00127000-0x003f0000 : "rootfs"
Jan  1 00:00:05 DD-WRT kern.warn kernel: mtd: partition "rootfs" doesn't start on an erase block boundary -- force read-only
Jan  1 00:00:05 DD-WRT kern.notice kernel: 0x003f0000-0x00400000 : "nvram"
Jan  1 00:00:05 DD-WRT kern.info kernel: Ralink APSoC Hardware Watchdog Timer
Jan  1 00:00:05 DD-WRT kern.warn kernel: u32 classifier
Jan  1 00:00:05 DD-WRT kern.warn kernel:     Actions configured
Jan  1 00:00:05 DD-WRT kern.warn kernel: Netfilter messages via NETLINK v0.30.
Jan  1 00:00:05 DD-WRT kern.warn kernel: nf_conntrack version 0.5.0 (1024 buckets, 4096 max)
Jan  1 00:00:05 DD-WRT kern.warn kernel: ctnetlink v0.93: registering with nfnetlink.
Jan  1 00:00:05 DD-WRT kern.info kernel: IPv4 over IPv4 tunneling driver
Jan  1 00:00:05 DD-WRT kern.info kernel: GRE over IPv4 tunneling driver
Jan  1 00:00:05 DD-WRT kern.info kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Jan  1 00:00:05 DD-WRT kern.info kernel: IPP2P v0.8.2 loading
Jan  1 00:00:05 DD-WRT kern.notice kernel: ClusterIP Version 0.8 loaded successfully
Jan  1 00:00:05 DD-WRT kern.info kernel: TCP bic registered
Jan  1 00:00:05 DD-WRT kern.warn kernel: NAPI enable, weight = 0, Tx Ring = 256, Rx Ring = 256
Jan  1 00:00:05 DD-WRT kern.warn kernel: MAC_ADRH -- : 0x0000000c
Jan  1 00:00:05 DD-WRT kern.warn kernel: MAC_ADRL -- : 0x43305077
Jan  1 00:00:05 DD-WRT kern.emerg kernel: decode /dev/mtdblock4
Jan  1 00:00:05 DD-WRT kern.warn kernel: VFS: Mounted root (squashfs filesystem) readonly.
Jan  1 00:00:05 DD-WRT kern.info kernel: Mounted devfs on /dev
Jan  1 00:00:05 DD-WRT kern.info kernel: Freeing unused kernel memory: 112k freed
Jan  1 00:00:05 DD-WRT kern.warn kernel: rt2860v2_ap: module license 'unspecified' taints kernel.
Jan  1 00:00:05 DD-WRT kern.warn kernel: MAC_ADRH -- : 0x00001cbd
Jan  1 00:00:05 DD-WRT kern.warn kernel: MAC_ADRL -- : 0xb990c256
Jan  1 00:00:05 DD-WRT kern.warn kernel: phy_tx_ring = 0x01c63000, tx_ring = 0xa1c63000
Jan  1 00:00:05 DD-WRT kern.info kernel: br0: topology change detected, propagating
Jan  1 00:00:05 DD-WRT kern.info kernel: br0: port 2(ra0) entering forwarding state
Jan  1 00:00:05 DD-WRT user.info syslog: dnsmasq : dnsmasq daemon successfully started
Jan  1 00:00:05 DD-WRT cron.info cron[864]: (CRON) STARTUP (fork ok)
Jan  1 00:00:05 DD-WRT user.info syslog: cron : cron daemon successfully started
Jan  1 00:00:05 DD-WRT cron.info cron[864]: (crontabs) ORPHAN (no passwd entry)
Jan  1 00:00:06 DD-WRT kern.info kernel: device vlan2 entered promiscuous mode
Jan  1 00:00:06 DD-WRT kern.info kernel: device vlan2 left promiscuous mode
Jan  1 00:00:06 DD-WRT user.info syslog: ttraff : traffic counter daemon successfully started
Jan  1 00:00:07 DD-WRT user.info syslog: klogd : kernel log daemon successfully stopped
Jan  1 00:00:07 DD-WRT kern.notice kernel: klogd: exiting
Jan  1 00:00:07 DD-WRT user.info syslog: httpd : http daemon successfully stopped
Jan  1 00:00:10 DD-WRT user.info syslog: klogd : kernel log daemon hanging, send SIGKILL
Jan  1 00:00:10 DD-WRT user.info syslog: syslogd : syslog daemon successfully stopped
Jan  1 00:00:10 DD-WRT syslog.info syslogd exiting
Jan  1 00:00:10 DD-WRT syslog.info syslogd started: BusyBox v1.19.3
Jan  1 00:00:10 DD-WRT kern.notice kernel: klogd started: BusyBox v1.19.3 (2011-12-14 09:24:30 CET)
Jan  1 00:00:10 DD-WRT kern.info kernel: etherip: Ethernet over IPv4 tunneling driver
Jan  1 00:00:10 DD-WRT user.info syslog: klogd : klog daemon successfully started
Jan  1 00:00:10 DD-WRT user.info syslog: reset button : resetbutton daemon successfully started
Jan  1 00:00:16 DD-WRT authpriv.info dropbear[1126]: Running in background
Jan  1 00:00:16 DD-WRT user.info syslog: dropbear : ssh daemon successfully started
Jan  1 00:00:39 DD-WRT authpriv.info dropbear[1140]: Child connection from 192.168.1.100:51787
Jan  1 00:00:46 DD-WRT authpriv.notice dropbear[1140]: Password auth succeeded for 'root' from 192.168.1.100:51787
Jan  1 00:00:46 DD-WRT authpriv.info dropbear[1140]: Exit (root): Exited normally
Jan  1 00:00:51 DD-WRT authpriv.info dropbear[1150]: Child connection from 192.168.1.100:51795
Jan  1 00:01:02 DD-WRT authpriv.notice dropbear[1150]: Password auth succeeded for 'root' from 192.168.1.100:51795
Jan  1 00:01:03 DD-WRT authpriv.info dropbear[1150]: Exit (root): Exited normally
Jan  1 00:01:08 DD-WRT authpriv.info dropbear[1165]: Child connection from 192.168.1.100:51808
Jan  1 00:01:10 DD-WRT authpriv.notice dropbear[1165]: Password auth succeeded for 'root' from 192.168.1.100:51808
Jan  1 00:01:11 DD-WRT authpriv.info dropbear[1165]: Exit (root): Exited normally
Jan  1 00:01:39 DD-WRT authpriv.info dropbear[1189]: Child connection from 192.168.1.100:51831
Jan  1 00:01:44 DD-WRT authpriv.notice dropbear[1189]: Password auth succeeded for 'root' from 192.168.1.100:51831
Jan  1 00:02:01 DD-WRT user.info syslog: process_monitor successfully started
Jan  1 00:02:01 DD-WRT daemon.err process_monitor[1221]: Last update failed, we need to re-update after 30 seconds
Jan  1 00:02:01 DD-WRT daemon.debug process_monitor[1221]: We need to re-update after 3600 seconds
Jan  1 00:02:01 DD-WRT daemon.info process_monitor[1221]: set timer: 3600 seconds, callback: ntp_main()




build 18687 - switch broken

Code:
Jan  1 00:00:05 DD-WRT syslog.info syslogd started: BusyBox v1.19.4
Jan  1 00:00:05 DD-WRT user.info syslog: wland : WLAN daemon successfully started
Jan  1 00:00:05 DD-WRT kern.notice kernel: klogd started: BusyBox v1.19.4 (2012-03-08 08:50:06 CET)
Jan  1 00:00:05 DD-WRT kern.notice kernel: Linux version 3.2.9-svn18668 (root@dd-wrt) (gcc version 4.6.3 20120201 (prerelease) (Linaro GCC 4.6-2012.02) ) #260 Thu Mar 8 08:43:04 CET 2012
Jan  1 00:00:05 DD-WRT kern.debug kernel: prom: fw_arg0=00000001, fw_arg1=01f5bfb0, fw_arg2=01f5c3b0, fw_arg3=00000000
Jan  1 00:00:05 DD-WRT kern.debug kernel: argv[0]=  (null) is invalid, skipping
Jan  1 00:00:05 DD-WRT kern.debug kernel: env[0]: memsize=32
Jan  1 00:00:05 DD-WRT kern.debug kernel: env[1]: initrd_start=0x00000000
Jan  1 00:00:05 DD-WRT kern.debug kernel: env[2]: initrd_size=0x0
Jan  1 00:00:05 DD-WRT kern.debug kernel: env[3]: flash_start=0xBF000000
Jan  1 00:00:05 DD-WRT kern.debug kernel: env[4]: flash_size=0x800000
Jan  1 00:00:05 DD-WRT kern.debug kernel: env[0]: memsize=32
Jan  1 00:00:05 DD-WRT kern.debug kernel: env[1]: initrd_start=0x00000000
Jan  1 00:00:05 DD-WRT kern.debug kernel: env[2]: initrd_size=0x0
Jan  1 00:00:05 DD-WRT kern.debug kernel: env[3]: flash_start=0xBF000000
Jan  1 00:00:05 DD-WRT kern.debug kernel: env[4]: flash_size=0x800000
Jan  1 00:00:05 DD-WRT kern.info kernel: bootconsole [early0] enabled
Jan  1 00:00:05 DD-WRT kern.info kernel: CPU revision is: 0001964c (MIPS 24Kc)
Jan  1 00:00:05 DD-WRT kern.info kernel: Ralink RT3350   id:1 rev:2 running at 320.00 MHz
Jan  1 00:00:05 DD-WRT kern.info kernel: Determined physical RAM map:
Jan  1 00:00:05 DD-WRT kern.info kernel:  memory: 02000000 @ 00000000 (usable)
Jan  1 00:00:05 DD-WRT kern.warn kernel: Zone PFN ranges:
Jan  1 00:00:05 DD-WRT kern.warn kernel:   Normal   0x00000000 -> 0x00002000
Jan  1 00:00:05 DD-WRT kern.warn kernel: Movable zone start PFN for each node
Jan  1 00:00:05 DD-WRT kern.warn kernel: early_node_map[1] active PFN ranges
Jan  1 00:00:05 DD-WRT kern.warn kernel:     0: 0x00000000 -> 0x00002000
Jan  1 00:00:05 DD-WRT kern.debug kernel: On node 0 totalpages: 8192
Jan  1 00:00:05 DD-WRT kern.debug kernel: free_area_init_node: node 0, pgdat 8026de10, node_mem_map 81000000
Jan  1 00:00:05 DD-WRT kern.debug kernel:   Normal zone: 64 pages used for memmap
Jan  1 00:00:05 DD-WRT kern.debug kernel:   Normal zone: 0 pages reserved
Jan  1 00:00:06 DD-WRT user.info syslog: klogd : klog daemon successfully started
Jan  1 00:00:06 DD-WRT kern.info kernel: TCP established hash table entries: 1024 (order: 1, 8192 bytes)
Jan  1 00:00:06 DD-WRT kern.info kernel: TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
Jan  1 00:00:06 DD-WRT kern.info kernel: TCP: Hash tables configured (established 1024 bind 1024)
Jan  1 00:00:06 DD-WRT kern.info kernel: TCP reno registered
Jan  1 00:00:06 DD-WRT kern.info kernel: UDP hash table entries: 256 (order: 0, 4096 bytes)
Jan  1 00:00:06 DD-WRT kern.info kernel: UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
Jan  1 00:00:06 DD-WRT kern.info kernel: NET: Registered protocol family 1
Jan  1 00:00:06 DD-WRT kern.info kernel: squashfs: version 3.0 (2006/03/15) Phillip Lougher
Jan  1 00:00:06 DD-WRT kern.info kernel: msgmni has been set to 57
Jan  1 00:00:06 DD-WRT kern.info kernel: io scheduler noop registered
Jan  1 00:00:06 DD-WRT kern.info kernel: io scheduler deadline registered (default)
Jan  1 00:00:06 DD-WRT kern.info kernel: Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
Jan  1 00:00:06 DD-WRT kern.info kernel: serial8250: ttyS0 at MMIO 0x10000500 (irq = 13) is a 16550A
Jan  1 00:00:06 DD-WRT kern.info kernel: serial8250: ttyS1 at MMIO 0x10000c00 (irq = 20) is a 16550A
Jan  1 00:00:06 DD-WRT kern.warn kernel: Ralink gpio driver initialized
Jan  1 00:00:06 DD-WRT kern.info kernel: system type: RT3350
Jan  1 00:00:06 DD-WRT kern.info kernel: boot type: 0
Jan  1 00:00:06 DD-WRT kern.notice kernel: ralink flash device: 0x1000000 at 0xbf000000
Jan  1 00:00:06 DD-WRT kern.info kernel: Ralink SoC physically mapped flash: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer ID 0x000001 Chip ID 0x001a00
Jan  1 00:00:06 DD-WRT kern.debug kernel: Ralink SoC physically mapped flash: Found an alias at 0x400000 for the chip at 0x0
Jan  1 00:00:06 DD-WRT kern.debug kernel: Ralink SoC physically mapped flash: Found an alias at 0x800000 for the chip at 0x0
Jan  1 00:00:06 DD-WRT kern.debug kernel: Ralink SoC physically mapped flash: Found an alias at 0xc00000 for the chip at 0x0
Jan  1 00:00:06 DD-WRT kern.info kernel: Amd/Fujitsu Extended Query Table at 0x0040
Jan  1 00:00:06 DD-WRT kern.info kernel:   Amd/Fujitsu Extended Query version 1.3.
Jan  1 00:00:06 DD-WRT kern.info kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Jan  1 00:00:06 DD-WRT kern.info kernel: IPP2P v0.8.2 loading
Jan  1 00:00:06 DD-WRT kern.warn kernel: RT305x_ESW: Link Status Changed
Jan  1 00:00:06 DD-WRT kern.warn kernel: CDMA_CSG_CFG = 81000007
Jan  1 00:00:06 DD-WRT kern.warn kernel: GDMA1_FWD_CFG = 710000
Jan  1 00:00:06 DD-WRT kern.info kernel: device br0 entered promiscuous mode
Jan  1 00:00:06 DD-WRT kern.info kernel: device vlan1 entered promiscuous mode
Jan  1 00:00:06 DD-WRT kern.info kernel: device eth2 entered promiscuous mode
Jan  1 00:00:06 DD-WRT kern.info kernel: br0: port 1(vlan1) entering forwarding state
Jan  1 00:00:06 DD-WRT kern.info kernel: br0: port 1(vlan1) entering forwarding state
Jan  1 00:00:06 DD-WRT kern.info kernel: device br0 left promiscuous mode
Jan  1 00:00:06 DD-WRT kern.info kernel: device br0 entered promiscuous mode
Jan  1 00:00:06 DD-WRT kern.info kernel: device br0 left promiscuous mode
Jan  1 00:00:06 DD-WRT kern.info kernel: device br0 entered promiscuous mode
Jan  1 00:00:06 DD-WRT kern.warn kernel: RtmpOSNetDevDetach(): RtmpOSNetDeviceDetach(), dev->name=ra0!
Jan  1 00:00:06 DD-WRT kern.warn kernel: 0x1300 = 00064380
Jan  1 00:00:06 DD-WRT kern.info kernel: br0: port 1(vlan1) entering forwarding state
Jan  1 00:00:06 DD-WRT kern.warn kernel: 0x1300 = 00064380
Jan  1 00:00:06 DD-WRT kern.info kernel: device ra0 entered promiscuous mode
Jan  1 00:00:06 DD-WRT kern.info kernel: br0: port 2(ra0) entering forwarding state
Jan  1 00:00:06 DD-WRT kern.info kernel: br0: port 2(ra0) entering forwarding state
Jan  1 00:00:06 DD-WRT kern.info kernel: br0: port 2(ra0) entering forwarding state
Jan  1 00:00:06 DD-WRT user.info syslog: cron : cron daemon successfully started
Jan  1 00:00:06 DD-WRT cron.info cron[588]: (CRON) STARTUP (fork ok)
Jan  1 00:00:06 DD-WRT cron.info cron[588]: (crontabs) ORPHAN (no passwd entry)
Jan  1 00:00:06 DD-WRT user.info syslog: dnsmasq : dnsmasq daemon successfully started
Jan  1 00:00:06 DD-WRT kern.info kernel: device vlan2 entered promiscuous mode
Jan  1 00:00:06 DD-WRT kern.info kernel: device vlan2 left promiscuous mode
Jan  1 00:00:07 DD-WRT user.info syslog: ttraff : traffic counter daemon successfully started
Jan  1 00:00:07 DD-WRT user.info syslog: dropbear : ssh daemon successfully started
Jan  1 00:00:07 DD-WRT authpriv.info dropbear[624]: Running in background
Jan  1 00:00:08 DD-WRT user.info syslog: klogd : kernel log daemon successfully stopped
Jan  1 00:00:08 DD-WRT kern.notice kernel: klogd: exiting
Jan  1 00:00:08 DD-WRT user.info syslog: httpd : http daemon successfully stopped
Jan  1 00:00:11 DD-WRT user.info syslog: klogd : kernel log daemon hanging, send SIGKILL
Jan  1 00:00:11 DD-WRT user.info syslog: syslogd : syslog daemon successfully stopped
Jan  1 00:00:11 DD-WRT syslog.info syslogd exiting
Jan  1 00:00:12 DD-WRT syslog.info syslogd started: BusyBox v1.19.4
Jan  1 00:00:12 DD-WRT user.info syslog: klogd : klog daemon successfully started
Jan  1 00:00:12 DD-WRT kern.notice kernel: klogd started: BusyBox v1.19.4 (2012-03-08 08:50:06 CET)
Jan  1 00:02:00 DD-WRT user.info syslog: process_monitor successfully started
Jan  1 00:02:01 DD-WRT daemon.err process_monitor[913]: Last update failed, we need to re-update after 30 seconds
Jan  1 00:02:01 DD-WRT daemon.debug process_monitor[913]: We need to re-update after 3600 seconds
Jan  1 00:02:01 DD-WRT daemon.info process_monitor[913]: set timer: 3600 seconds, callback: ntp_main()
Jan  1 00:07:24 DD-WRT authpriv.notice dropbear[985]: Password auth succeeded for 'root' from 192.168.1.11:50223
Jan  1 00:07:24 DD-WRT authpriv.info dropbear[985]: Exit (root): Exited normally
Jan  1 00:07:32 DD-WRT authpriv.notice dropbear[993]: Password auth succeeded for 'root' from 192.168.1.11:50228
Jan  1 00:07:32 DD-WRT authpriv.info dropbear[993]: Exit (root): Exited normally
Jan  1 00:07:51 DD-WRT authpriv.notice dropbear[1002]: Password auth succeeded for 'root' from 192.168.1.11:50235

_________________
Reality Has Always Been Too Small For Human Imagination...
netcaster
DD-WRT Novice


Joined: 14 Mar 2012
Posts: 3

PostPosted: Wed Mar 14, 2012 22:49    Post subject: Reply with quote
@ Pondera
the DIR-300b / DIR-600b have an EASY Recovery Function build into the Ralink Chip itself.

1. power off Device, connect network to LAN-1
2. press & hold Reset Button while plug in the power
3. hold the Reset still for some seconds and then relase it
4. the power LED is blinking orange and you can connect to 192.168.0.1 to upgrade the firmware

cheers

_________________
Reality Has Always Been Too Small For Human Imagination...
cybero2912
DD-WRT Guru


Joined: 18 Jun 2006
Posts: 1177
Location: Berlin

PostPosted: Thu Mar 15, 2012 10:05    Post subject: Reply with quote
I could provide bootlog
but I have to solder pinheader first for connectig a serial cable

pls inform if needed

edit: tried r18740 - same problem
vasek00
DD-WRT Guru


Joined: 06 Nov 2010
Posts: 1850

PostPosted: Fri Mar 16, 2012 9:40    Post subject: Reply with quote
Probably problem in initialization switch for Ralink.

Set build 18007 or more low where works
http://192.168.1.1/Diagnostics.asp
1. To adjust wi-fi and LAN
2. WEB
Command Shell -> Commands
switch reg r 90 > /tmp/var/tmp/switch_LAN
3. Save StartUP -> reboot
4. To be connected to the device
5. cat /tmp/var/tmp/switch_LAN

Update through WEB
- build 18687
1. To be connected to the device wi-fi(telnet)
2. cat /tmp/var/tmp/switch_LAN

Should be 00007f7f or 10007f7f

Or as to check up through mii_mrg value of adjustments of ports LAN:
mii_mgr -g -p [REG] -r 0

REG - 0, 1, 2, 3, 4
Ric03
DD-WRT User


Joined: 11 Apr 2011
Posts: 61

PostPosted: Fri Mar 16, 2012 18:16    Post subject: Reply with quote
Same (old) issue on senao 9752.
Build 16214 that works shows:

root@Senao:~# switch reg r 90
switch reg read offset=90, value=7f7f
root@Senao:~# mii_mgr -g -p 0 -r 0
Get: phy[0].reg[0] = 3100
root@Senao:~# mii_mgr -g -p 1 -r 0
Get: phy[1].reg[0] = 3100
root@Senao:~# mii_mgr -g -p 2 -r 0
Get: phy[2].reg[0] = 3100
root@Senao:~# mii_mgr -g -p 3 -r 0
Get: phy[3].reg[0] = 3100
root@Senao:~# mii_mgr -g -p 4 -r 0
Get: phy[4].reg[0] = 3100

Build 18740 that does NOT work shows:
root@Senao:~# switch reg r 90
switch reg read offset=90, value=3f807f7f
root@Senao:~# mii_mgr -g -p 0 -r 0
Get: phy[0].reg[0] = 3100
root@Senao:~# mii_mgr -g -p 1 -r 0
Get: phy[1].reg[0] = 3100
root@Senao:~# mii_mgr -g -p 2 -r 0
Get: phy[2].reg[0] = 3100
root@Senao:~# mii_mgr -g -p 3 -r 0
Get: phy[3].reg[0] = 3100
root@Senao:~# mii_mgr -g -p 4 -r 0
Get: phy[4].reg[0] = 3100

I think we're on something here. There is a difference. Can I do something to "make it work" by hand? May be write r90 with 7f7f? or is this just too simple to work?

Update: looking at the data sheet of RT3050 it shows that all the 5 phy ports are disabled. Enabling the phy ports should be done at the initialization of the processor so I don't think it would be enough to write the register with the correct value.
BrainSlayer please can you check the initialization of the RT3052 for the ESR-9752SC kernel and possibily also the ones mentioned above? I think this may be the issue.

Update2: I've compared the raeth initialization code in the revision 18740 sources in rt305x_esw_init() and the content of the registers after the boot and I've found they are quite different:

*(unsigned long *)(0xb0110008) = 0xC8A07850;
*(unsigned long *)(0xb01100E4) = 0x00000000;
*(unsigned long *)(0xb0110014) = 0x00405555;
*(unsigned long *)(0xb0110050) = 0x00002001;
*(unsigned long *)(0xb0110090) = 0x00007f7f;
*(unsigned long *)(0xb0110098) = 0x00007f3f; //disable VLAN
*(unsigned long *)(0xb01100CC) = 0x0002500c;
*(unsigned long *)(0xb011009C) = 0x0008a301; //hashing algorithm=XOR48, aging interval=300sec
*(unsigned long *)(0xb011008C) = 0x02404040;

and the running router:

root@Senao:~# switch reg r 8
switch reg read offset=8, value=ffc86e5a
root@Senao:~# switch reg r e4
switch reg read offset=e4, value=3f
root@Senao:~# switch reg r 14
switch reg read offset=14, value=405555
root@Senao:~# switch reg r 50
switch reg read offset=50, value=2001
root@Senao:~# switch reg r 90
switch reg read offset=90, value=3f807f7f
root@Senao:~# switch reg r 98
switch reg read offset=98, value=7f3f
root@Senao:~# switch reg r cc
switch reg read offset=cc, value=a30c
root@Senao:~# switch reg r 9c
switch reg read offset=9c, value=8a101
root@Senao:~# switch reg r 8c
switch reg read offset=8c, value=27f7f7f
vasek00
DD-WRT Guru


Joined: 06 Nov 2010
Posts: 1850

PostPosted: Sat Mar 17, 2012 3:38    Post subject: Reply with quote
Ric03 wrote:
Same (old) issue on senao 9752.
Build 16214 that works shows:

root@Senao:~# switch reg r 90
switch reg read offset=90, value=7f7f

Build 18740 that does NOT work shows:
root@Senao:~# switch reg r 90
switch reg read offset=90, value=3f807f7f



Command Shell -> Commands

switch reg w 90 00007f7f
or
switch reg w 90 10007f7f

Also will work.

Initialization switch depends from uboot devices in which there are given commands to bring in the register the given values.
On native uboot Ralink all should be normal.
Ric03
DD-WRT User


Joined: 11 Apr 2011
Posts: 61

PostPosted: Sat Mar 17, 2012 7:42    Post subject: Reply with quote
vasek00 wrote:
Ric03 wrote:
Same (old) issue on senao 9752.
Build 16214 that works shows:

root@Senao:~# switch reg r 90
switch reg read offset=90, value=7f7f

Build 18740 that does NOT work shows:
root@Senao:~# switch reg r 90
switch reg read offset=90, value=3f807f7f



Command Shell -> Commands

switch reg w 90 00007f7f
or
switch reg w 90 10007f7f

Also will work.

Initialization switch depends from uboot devices in which there are given commands to bring in the register the given values.
On native uboot Ralink all should be normal.


No it doesn't work. I tried, TBH without much hope, your suggestion but whatever screwed the register 90 also screwed something else and as I was supposing, just writing the right value to the register doesn't work.

Uboot is just the boot block/code. It's the kernel that initializes the chip to start ethernet operations properly. Unfortunately I've been far from kernel development for too long and now it's too hard with the few spare time that I have to dig deeper into this issue: it took more than one hour to find the raether.c and the 305x initialization. Looking at the kernel sources the initialization seems to be OK, or at least, by diffing with working 16214, it has not been changed for very long time, but for some reason during, or after, the kernel boot something changes the registers after their initialization.

BrainSlayer, we need your help ... please.

If needed I'm available for whatever investigation I can do in my system.
vasek00
DD-WRT Guru


Joined: 06 Nov 2010
Posts: 1850

PostPosted: Sat Mar 17, 2012 10:57    Post subject: Reply with quote
Speech about the beginning went about DIR300/B1.

In the beginning we have uboot and only then a kernel dd-wrt.
Quote:
uboot
*(unsigned long *)(0xb0110050) = 0x00002001;
*(unsigned long *)(0xb0110090) = 0x00007f7f;
*(unsigned long *)(0xb0110098) = 0x00007f3f; //disable VLAN
*(unsigned long *)(0xb01100CC) = 0x0002500c;
*(unsigned long *)(0xb011009C) = 0x0008a301; //hashing algorithm=XOR48, aging interval=300sec
*(unsigned long *)(0xb011008C) = 0x02404040;


But it is the data from native SDK Ralink, and that there actually in uboot the given device the manufacturer of the device knows only.
After working off uboot then control it will be transferred in a kernel dd-wrt. And here we matter:
Quote:
root@Senao:~# switch reg r 90
switch reg read offset=90, value=3f807f7f


Has checked up operation here such script on the worker ralink 305x:
Code:
#!/bin/sh
switch reg r 90 > sw_1
sleep 2
switch reg w 90 3f807f7f
sleep 2
switch reg r 90 > sw_2
sleep 10
switch reg w 90 00007f7f
sleep 2
switch reg r 90 > sw_3


After 3f807f7f die away LAN ports (disable), but after 00007f7f start to work (enable).
Just values 3f8 speak:
Code:
3 - DIS_GMII_PORT_1 и DIS_GMII_PORT_0 – disable
F8 – WAN, LAN1-LAN4 – disable
Goto page 1, 2, 3, 4  Next Display posts from previous:    Page 1 of 4
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Ralink SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum