1 Temat przez Juve (edytowany przez Juve 2015-07-05 10:07:25)

  • Juve
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2012-01-10
  • Posty: 62

Temat: WDR 4300 - uszkodzony?

Witam!
Firmware BB
Mój router miał nastepujące przejścia:
1. kiedy nie było mnie w domu routerowi się umyśliło (podczas mojej nieobecności - nie wiem czy było zasilanie cały czas), że się popsuje i na obudowie świeciła przysłowiowa choinka: pomógł serial.
2. ostatnio router się resetował co ok 1min - sam z siebie; na serialu były konkretne krzaki, ale www chodziło. Udało mi się przez www zaktualizować firmware do ostatniego: 1.6.2.2
3. na razie jest wszystko ok, ale niepokoi mnie ten fakt, że zaczyna mieć humory. Dodam jeszcze, że aktualnie na serialu są krzaki. Poprawić luty?
Poniżej daję log z aktualnie 'podniesionego' routera.

Jan  1 01:00:08 Gargoyle kern.info kernel: [    0.430000] msgmni has been set to 246
Jan  1 01:00:08 Gargoyle kern.info kernel: [    0.430000] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
Jan  1 01:00:08 Gargoyle kern.info kernel: [    0.440000] io scheduler noop registered
Jan  1 01:00:08 Gargoyle kern.info kernel: [    0.440000] io scheduler deadline registered (default)
Jan  1 01:00:08 Gargoyle kern.info kernel: [    0.450000] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
Jan  1 01:00:08 Gargoyle kern.info kernel: [    0.480000] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11) is a 16550A
Jan  1 01:00:08 Gargoyle kern.info kernel: [    0.490000] console [ttyS0] enabled, bootconsole disabled
Jan  1 01:00:08 Gargoyle kern.warn kernel: [    0.500000] m25p80 spi0.0: found s25fl064k, expected m25p80
Jan  1 01:00:08 Gargoyle kern.info kernel: [    0.510000] m25p80 spi0.0: s25fl064k (8192 Kbytes)
Jan  1 01:00:08 Gargoyle kern.notice kernel: [    0.510000] 5 tp-link partitions found on MTD device spi0.0
Jan  1 01:00:08 Gargoyle kern.notice kernel: [    0.520000] Creating 5 MTD partitions on "spi0.0":
Jan  1 01:00:08 Gargoyle kern.notice kernel: [    0.520000] 0x000000000000-0x000000020000 : "u-boot"
Jan  1 01:00:08 Gargoyle kern.notice kernel: [    0.530000] 0x000000020000-0x00000010ef78 : "kernel"
Jan  1 01:00:08 Gargoyle kern.warn kernel: [    0.530000] mtd: partition "kernel" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
Jan  1 01:00:08 Gargoyle kern.notice kernel: [    0.550000] 0x00000010ef78-0x0000007f0000 : "rootfs"
Jan  1 01:00:08 Gargoyle kern.warn kernel: [    0.550000] mtd: partition "rootfs" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
Jan  1 01:00:09 Gargoyle kern.notice kernel: [    0.570000] mtd: partition "rootfs" set to be root filesystem
Jan  1 01:00:09 Gargoyle kern.info kernel: [    0.570000] mtd: partition "rootfs_data" created automatically, ofs=680000, len=170000 
Jan  1 01:00:09 Gargoyle kern.notice kernel: [    0.580000] 0x000000680000-0x0000007f0000 : "rootfs_data"
Jan  1 01:00:09 Gargoyle kern.notice kernel: [    0.590000] 0x0000007f0000-0x000000800000 : "art"
Jan  1 01:00:09 Gargoyle kern.notice kernel: [    0.590000] 0x000000020000-0x0000007f0000 : "firmware"
Jan  1 01:00:09 Gargoyle kern.info kernel: [    0.730000] ag71xx_mdio: probed
Jan  1 01:00:09 Gargoyle kern.info kernel: [    0.730000] eth0: Atheros AG71xx at 0xb9000000, irq 4
Jan  1 01:00:09 Gargoyle kern.info kernel: [    1.310000] eth0: Atheros AR8327 switch driver attached.
Jan  1 01:00:09 Gargoyle kern.info kernel: [    2.470000] ag71xx ag71xx.0: eth0: connected to PHY at ag71xx-mdio.0:00 [uid=004dd034, driver=Atheros AR8216/AR8236/AR8316]
Jan  1 01:00:09 Gargoyle kern.info kernel: [    2.490000] TCP cubic registered
Jan  1 01:00:09 Gargoyle kern.info kernel: [    2.490000] NET: Registered protocol family 17
Jan  1 01:00:09 Gargoyle kern.notice kernel: [    2.490000] Bridge firewalling registered
Jan  1 01:00:09 Gargoyle kern.info kernel: [    2.500000] Ebtables v2.0 registered
Jan  1 01:00:09 Gargoyle kern.info kernel: [    2.500000] 8021q: 802.1Q VLAN Support v1.8
Jan  1 01:00:09 Gargoyle kern.info kernel: [    2.510000] VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
Jan  1 01:00:09 Gargoyle kern.info kernel: [    2.520000] Freeing unused kernel memory: 220k freed
Jan  1 01:00:09 Gargoyle kern.debug kernel: [    4.460000] Registered led device: tp-link:blue:qss
Jan  1 01:00:09 Gargoyle kern.debug kernel: [    4.460000] Registered led device: tp-link:blue:system
Jan  1 01:00:09 Gargoyle kern.debug kernel: [    4.460000] Registered led device: tp-link:green:usb1
Jan  1 01:00:09 Gargoyle kern.debug kernel: [    4.460000] Registered led device: tp-link:green:usb2
Jan  1 01:00:09 Gargoyle kern.debug kernel: [    4.460000] Registered led device: tp-link:blue:wlan2g
Jan  1 01:00:09 Gargoyle kern.info kernel: [    5.480000] eth0: link up (1000Mbps/Full duplex)
Jan  1 01:00:09 Gargoyle kern.info kernel: [    7.860000] eth0: link down
Jan  1 01:00:09 Gargoyle kern.info kernel: [    8.590000] Loading modules backported from Linux version master-2014-05-22-0-gf2032ea
Jan  1 01:00:09 Gargoyle kern.info kernel: [    8.600000] Backport generated by backports.git backports-20140320-37-g5c33da0
Jan  1 01:00:09 Gargoyle kern.info kernel: [    8.750000] cfg80211: Calling CRDA to update world regulatory domain
Jan  1 01:00:09 Gargoyle kern.info kernel: [    8.750000] cfg80211: World regulatory domain updated:
Jan  1 01:00:09 Gargoyle kern.info kernel: [    8.760000] cfg80211:  DFS Master region: unset
Jan  1 01:00:09 Gargoyle kern.info kernel: [    8.760000] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Jan  1 01:00:09 Gargoyle kern.info kernel: [    8.770000] cfg80211:   (2400000 KHz - 2483000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
Jan  1 01:00:09 Gargoyle kern.info kernel: [    8.780000] cfg80211:   (5140000 KHz - 5860000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
Jan  1 01:00:09 Gargoyle kern.info kernel: [    9.020000] NET: Registered protocol family 10
Jan  1 01:00:09 Gargoyle kern.notice kernel: [    9.410000] SCSI subsystem initialized
Jan  1 01:00:09 Gargoyle kern.info kernel: [    9.610000] usbcore: registered new interface driver usbfs
Jan  1 01:00:09 Gargoyle kern.info kernel: [    9.610000] usbcore: registered new interface driver hub
Jan  1 01:00:09 Gargoyle kern.info kernel: [    9.620000] usbcore: registered new device driver usb
Jan  1 01:00:09 Gargoyle kern.debug kernel: [   10.440000] ath: EEPROM regdomain: 0x0
Jan  1 01:00:09 Gargoyle kern.debug kernel: [   10.440000] ath: EEPROM indicates default country code should be used
Jan  1 01:00:09 Gargoyle kern.debug kernel: [   10.440000] ath: doing EEPROM country->regdmn map search
Jan  1 01:00:09 Gargoyle kern.debug kernel: [   10.440000] ath: country maps to regdmn code: 0x3a
Jan  1 01:00:09 Gargoyle kern.debug kernel: [   10.440000] ath: Country alpha2 being used: US
Jan  1 01:00:09 Gargoyle kern.debug kernel: [   10.440000] ath: Regpair used: 0x3a
Jan  1 01:00:09 Gargoyle kern.debug kernel: [   10.450000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Jan  1 01:00:09 Gargoyle kern.debug kernel: [   10.460000] Registered led device: ath9k-phy0
Jan  1 01:00:09 Gargoyle kern.info kernel: [   10.460000] ieee80211 phy0: Atheros AR9340 Rev:0 mem=0xb8100000, irq=47
Jan  1 01:00:09 Gargoyle kern.info kernel: [   16.430000] usbcore: registered new interface driver rndis_host
Jan  1 01:00:09 Gargoyle kern.info kernel: [   16.510000] USB Serial support registered for GSM modem (1-port)
Jan  1 01:00:09 Gargoyle kern.info kernel: [   16.520000] usbcore: registered new interface driver option
Jan  1 01:00:09 Gargoyle kern.info kernel: [   16.530000] option: v0.7.2:USB Driver for GSM modems
Jan  1 01:00:09 Gargoyle kern.info kernel: [   16.550000] USB Serial support registered for Qualcomm USB modem
Jan  1 01:00:09 Gargoyle kern.info kernel: [   16.560000] usbcore: registered new interface driver qcserial
Jan  1 01:00:09 Gargoyle kern.info kernel: [   16.680000] fuse init (API version 7.18)
Jan  1 01:00:11 Gargoyle kern.info kernel: [   30.300000] ADDRCONF(NETDEV_UP): eth0: link is not ready
Jan  1 01:00:13 Gargoyle kern.info kernel: [   31.750000] ADDRCONF(NETDEV_UP): eth0: link is not ready
Jan  1 01:00:13 Gargoyle kern.info kernel: [   31.760000] ADDRCONF(NETDEV_UP): eth0.1: link is not ready
Jan  1 01:00:13 Gargoyle kern.info kernel: [   31.760000] device eth0.1 entered promiscuous mode
Jan  1 01:00:13 Gargoyle kern.info kernel: [   31.770000] device eth0 entered promiscuous mode
Jan  1 01:00:13 Gargoyle daemon.notice netifd: Interface 'lan' is now up
Jan  1 01:00:13 Gargoyle daemon.notice netifd: Interface 'loopback' is now up
Jan  1 01:00:13 Gargoyle kern.info kernel: [   31.780000] ADDRCONF(NETDEV_UP): br-lan: link is not ready
Jan  1 01:00:13 Gargoyle kern.info kernel: [   31.800000] ADDRCONF(NETDEV_UP): eth0.2: link is not ready
Jan  1 01:00:13 Gargoyle daemon.notice netifd: wan (2601): udhcpc (v1.19.4) started
Jan  1 01:00:13 Gargoyle user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Jan  1 01:00:13 Gargoyle daemon.notice netifd: wan (2601): Sending discover...
Jan  1 01:00:14 Gargoyle kern.info kernel: [   32.810000] eth0: link up (1000Mbps/Full duplex)
Jan  1 01:00:14 Gargoyle kern.info kernel: [   32.830000] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Jan  1 01:00:14 Gargoyle kern.info kernel: [   32.850000] br-lan: port 1(eth0.1) entered forwarding state
Jan  1 01:00:14 Gargoyle kern.info kernel: [   32.850000] br-lan: port 1(eth0.1) entered forwarding state
Jan  1 01:00:14 Gargoyle kern.info kernel: [   32.860000] ADDRCONF(NETDEV_CHANGE): eth0.1: link becomes ready
Jan  1 01:00:14 Gargoyle kern.info kernel: [   32.860000] ADDRCONF(NETDEV_CHANGE): eth0.2: link becomes ready
Jan  1 01:00:14 Gargoyle kern.info kernel: [   32.880000] ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
Jan  1 01:00:14 Gargoyle user.notice dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses!
Jan  1 01:00:14 Gargoyle user.notice dnsmasq: Allowing 127.0.0.0/8 responses
Jan  1 01:00:14 Gargoyle user.notice dnsmasq: Allowing RFC1918 responses for domain free.aero2.net.pl
Jan  1 01:00:16 Gargoyle kern.info kernel: [   34.850000] br-lan: port 1(eth0.1) entered forwarding state
Jan  1 01:00:16 Gargoyle user.notice usb-modeswitch: 1-0:1.0: Manufacturer=Linux_3.3.8_ehci_hcd Product=Generic_Platform_EHCI_Controller Serial=ehci-platform
Jan  1 01:00:16 Gargoyle daemon.notice netifd: wan (2601): Sending discover...
Jan  1 01:00:18 Gargoyle daemon.info dnsmasq[2862]: started, version 2.66 cachesize 150
Jan  1 01:00:18 Gargoyle daemon.info dnsmasq[2862]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth
Jan  1 01:00:18 Gargoyle daemon.info dnsmasq-dhcp[2862]: DHCP, IP range 192.168.1.100 -- 192.168.1.249, lease time 12h
Jan  1 01:00:18 Gargoyle daemon.info dnsmasq[2862]: using local addresses only for domain lan
Jan  1 01:00:18 Gargoyle daemon.warn dnsmasq[2862]: no servers found in /tmp/resolv.conf.auto, will retry
Jan  1 01:00:18 Gargoyle daemon.info dnsmasq[2862]: read /etc/hosts - 2 addresses
Jan  1 01:00:18 Gargoyle daemon.info dnsmasq-dhcp[2862]: read /etc/ethers - 0 addresses
Jan  1 01:00:18 Gargoyle kern.info kernel: [   37.360000] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jan  1 01:00:18 Gargoyle kern.info kernel: [   37.370000] device wlan0 entered promiscuous mode
Jan  1 01:00:18 Gargoyle kern.info kernel: [   37.580000] br-lan: port 2(wlan0) entered forwarding state
Jan  1 01:00:18 Gargoyle kern.info kernel: [   37.590000] br-lan: port 2(wlan0) entered forwarding state
Jan  1 01:00:18 Gargoyle kern.info kernel: [   37.590000] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Jan  1 01:00:19 Gargoyle daemon.info dnsmasq-dhcp[2862]: DHCPREQUEST(br-lan) 192.168.0.229 d4:c9:ef:f7:a6:b1 
Jan  1 01:00:19 Gargoyle daemon.info dnsmasq-dhcp[2862]: DHCPNAK(br-lan) 192.168.0.229 d4:c9:ef:f7:a6:b1 wrong network
Jan  1 01:00:19 Gargoyle daemon.notice netifd: wan (2601): Sending discover...
Jan  1 01:00:20 Gargoyle kern.info kernel: [   39.590000] br-lan: port 2(wlan0) entered forwarding state
Jan  1 01:00:22 Gargoyle kern.info kernel: [   40.660000] ADDRCONF(NETDEV_UP): wlan1: link is not ready
Jan  1 01:00:22 Gargoyle kern.info kernel: [   40.660000] device wlan1 entered promiscuous mode
Jan  1 01:00:22 Gargoyle kern.info kernel: [   40.880000] br-lan: port 3(wlan1) entered forwarding state
Jan  1 01:00:22 Gargoyle daemon.info dnsmasq-dhcp[2862]: DHCPDISCOVER(br-lan) d4:c9:ef:f7:a6:b1 
Jan  1 01:00:22 Gargoyle daemon.info dnsmasq-dhcp[2862]: DHCPOFFER(br-lan) 192.168.1.133 d4:c9:ef:f7:a6:b1 
Jan  1 01:00:22 Gargoyle daemon.info dnsmasq-dhcp[2862]: DHCPREQUEST(br-lan) 192.168.1.133 d4:c9:ef:f7:a6:b1 
Jan  1 01:00:22 Gargoyle daemon.info dnsmasq-dhcp[2862]: DHCPACK(br-lan) 192.168.1.133 d4:c9:ef:f7:a6:b1 MAT-TAB
Jan  1 01:00:22 Gargoyle kern.info kernel: [   40.880000] br-lan: port 3(wlan1) entered forwarding state
Jan  1 01:00:22 Gargoyle kern.info kernel: [   40.890000] ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
Jan  1 01:00:24 Gargoyle kern.info kernel: [   42.880000] br-lan: port 3(wlan1) entered forwarding state
Jan  1 01:00:02 Gargoyle user.notice usb-modeswitch: 1-1:1.0: Manufacturer=? Product=USB2.0_Hub Serial=?
Jan  1 01:00:02 Gargoyle daemon.crit httpd_gargoyle[3057]: bind 0.0.0.0 - Address already in use
Jan  1 01:00:02 Gargoyle daemon.crit httpd_gargoyle[3057]: bind 0.0.0.0 - Address already in use
Jan  1 01:00:02 Gargoyle daemon.warn httpd_gargoyle[3080]: started as root without requesting chroot(), warning only
Jan  1 01:00:02 Gargoyle daemon.notice httpd_gargoyle[3080]: httpd_gargoyle/1.0 14mar2008 starting on Gargoyle, port 80
Jan  1 01:00:05 Gargoyle user.notice dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses!
Jan  1 01:00:05 Gargoyle user.notice dnsmasq: Allowing 127.0.0.0/8 responses
Jan  1 01:00:05 Gargoyle user.notice dnsmasq: Allowing RFC1918 responses for domain free.aero2.net.pl
Jan  1 01:00:09 Gargoyle user.err syslog: error starting threads: errno 89 (Function not implemented)
Jan  1 01:00:09 Gargoyle user.info sysinit: exportfs: could not open /var/lib/nfs/.etab.lock for locking: errno 2 (No such file or directory)
Jan  1 01:00:09 Gargoyle user.info sysinit: exportfs: can't lock /var/lib/nfs/etab for writing
Jan  1 01:00:09 Gargoyle user.info sysinit: exportfs: could not open /var/lib/nfs/.xtab.lock for locking: errno 2 (No such file or directory)
Jan  1 01:00:09 Gargoyle user.info sysinit: exportfs: can't lock /var/lib/nfs/xtab for writing
Jan  1 01:00:12 Gargoyle user.info sysinit: ERROR: No valid dynamic DNS service configurations defined
Jan  1 01:00:12 Gargoyle user.info sysinit: (Did you specify correct configuration file path?)
Jan  1 01:00:18 Gargoyle daemon.info dnsmasq-dhcp[2862]: DHCPREQUEST(br-lan) 192.168.1.133 d4:c9:ef:f7:a6:b1 
Jan  1 01:00:18 Gargoyle daemon.info dnsmasq-dhcp[2862]: DHCPACK(br-lan) 192.168.1.133 d4:c9:ef:f7:a6:b1 MAT-TAB
Jan  1 01:00:18 Gargoyle daemon.info dnsmasq-dhcp[2862]: DHCPREQUEST(br-lan) 192.168.1.133 d4:c9:ef:f7:a6:b1 
Jan  1 01:00:18 Gargoyle daemon.info dnsmasq-dhcp[2862]: DHCPACK(br-lan) 192.168.1.133 d4:c9:ef:f7:a6:b1 MAT-TAB
Jan  1 01:00:37 Gargoyle user.notice root: vsftpd init: mounted = 0
Jan  1 01:00:37 Gargoyle user.info sysinit: ERROR: No drives attached, no directories to share!
Jan  1 01:00:38 Gargoyle kern.warn kernel: [   80.500000] jffs2_scan_eraseblock(): End of filesystem marker found at 0x0
Jan  1 01:00:38 Gargoyle kern.warn kernel: [   80.510000] jffs2_build_filesystem(): unlocking the mtd device... done.
Jan  1 01:00:43 Gargoyle kern.warn kernel: [   80.510000] jffs2_build_filesystem(): erasing all blocks after the end marker... done.
Jan  1 01:00:43 Gargoyle kern.notice kernel: [   85.800000] JFFS2 notice: (3988) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
Jan  1 01:00:43 Gargoyle user.info sysinit: copying files ... done
Jan  1 01:00:45 Gargoyle user.info sysinit: setting up led USB1
Jan  1 01:00:45 Gargoyle user.info sysinit: setting up led USB2
Jan  1 01:00:45 Gargoyle user.info sysinit: setting up led WLAN2G
Jan  1 01:00:50 Gargoyle authpriv.info dropbear[4312]: Running in background
Jan  1 01:01:11 Gargoyle auth.info passwd: Password for root changed by root
Jan  1 01:01:11 Gargoyle authpriv.info dropbear[4312]: Early exit: Terminated by signal
Jan  1 01:01:11 Gargoyle authpriv.info dropbear[4424]: Running in background
Jan  1 01:00:50 Gargoyle authpriv.info dropbear[4649]: Child connection from 192.168.1.133:49883
Jan  1 01:00:57 Gargoyle authpriv.notice dropbear[4649]: Password auth succeeded for 'root' from 192.168.1.133:49883
Success
 ----------------------------------------------------------------
 |                                                              |
 | Gargoyle PL 1.6.2.2 (b70bfc1)                                |
 | OpenWrt Attitude Adjustment 12.09.1 (r42647)                 |
 | Build time: 2014-09-27 10:11 CEST                            |
 |                                                              |
 | Cezary Jackiewicz (obsy), http://eko.one.pl                  |
 |                                                              |
 ----------------------------------------------------------------
 | Machine: TP-Link TL-WDR4300 v1                               |
 | Uptime: 0d, 00:02:50                                         |
 | Load: 0.78 0.51 0.21                                         |
 | Flash: total: 1.4MB, free: 1.2MB, used: 17%                  |
 | Memory: total: 123.7MB, free: 106.8MB, used: 13%             |
 | WAN:                                                         |
 | LAN: 192.168.1.1                                             |
 | WLAN: mode: ap, ssid: Gargoyle, channel: 11, conn: 0         |
 | WLAN: mode: ap, ssid: Gargoyle, channel: 36, conn: 0         |
 ----------------------------------------------------------------

Może zasilacz uwalony (zasilacz pudełkowy, napięcie w jałowym 12,45V) ? co myślicie?

2 Odpowiedź przez pepe2k

  • pepe2k
  • pepe2k
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2012-10-29
  • Posty: 5,028

Odp: WDR 4300 - uszkodzony?

Czym i jak się podłączyłeś do konsoli?
Krzaki to zazwyczaj oznaka złego połączenia wspólnej masy albo złych ustawień transmisji.

3 Odpowiedź przez Juve

  • Juve
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2012-01-10
  • Posty: 62

Odp: WDR 4300 - uszkodzony?

Serialem. Zła prędkość była ustawiona hmm

4 Odpowiedź przez pepe2k

  • pepe2k
  • pepe2k
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2012-10-29
  • Posty: 5,028

Odp: WDR 4300 - uszkodzony?

Juve napisał/a:

Serialem. Zła prędkość była ustawiona hmm

Serialem czyli czym? Mam nadzieję, że nie RS232... w routerze masz UART, więc potrzebujesz jakiegoś adaptera, z odpowiednim poziomem napięć. I oczywiście podłączasz tylko 3 sygnały; RX, TX, GND.

W sprawie restartów... jak masz dostęp do konsoli szeregowej, to najlepiej "złap" logi z takiego restartu, może coś tam ciekawego będzie. I zrób sobie na początek test pamięci RAM, np. "memtester 32 3".

5 Odpowiedź przez Juve (edytowany przez Juve 2015-07-05 11:28:34)

  • Juve
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2012-01-10
  • Posty: 62

Odp: WDR 4300 - uszkodzony?

Nieeee, oczywiście, że UARTEM.

Są błędy pamięci:
przynajmniej od:
FAILURE: 0x00000000 != 0x00800000 at offset 0x003c6b79.
.
.
.
FAILURE: 0x00000000 != 0x00800000 at offset 0x003c8479.
FAILURE: 0x00000000 != 0x00800000 at offset 0x003c8601.

EDIT

memtester version 4.1.3 (32-bit)
Copyright (C) 2010 Charles Cazabon.
Licensed under the GNU General Public License version 2 (only).

pagesize is 4096
pagesizemask is 0xfffff000
want 32MB (33554432 bytes)
got  32MB (33554432 bytes), trying mlock ...locked.
Loop 1/3:
  Stuck Address       : ok
  Random Value        : ok
  Compare XOR         : ok
  Compare SUB         : ok
  Compare MUL         : ok
  Compare DIV         : ok
  Compare OR          : ok
  Compare AND         : ok
  Sequential Increment: ok
  Solid Bits          : ok
  Block Sequential    : ok
  Checkerboard        : ok
  Bit Spread          : testing  23  Bit Flip            : testing 184  Walking Ones        : ok
  Walking Zeroes      : ok

Loop 2/3:
  Stuck Address       : ok
  Random Value        : ok
  Compare XOR         : ok
  Compare SUB         : ok
  Compare MUL         : ok
  Compare DIV         : ok
  Compare OR          : ok
  Compare AND         : ok
  Sequential Increment: ok
  Solid Bits          : ok
  Block Sequential    : ok
  Checkerboard        : ok
  Bit Spread          : testing  23  Bit Flip            : testing 184  Walking Ones        : ok
  Walking Zeroes      : ok

Loop 3/3:
  Stuck Address       : ok
  Random Value        : ok
  Compare XOR         : ok
  Compare SUB         : ok
  Compare MUL         : ok
  Compare DIV         : ok
  Compare OR          : ok
  Compare AND         : ok
  Sequential Increment: ok
  Solid Bits          : ok
  Block Sequential    : ok
  Checkerboard        : ok
  Bit Spread          : testing  23  Bit Flip            : testing 184  Walking Ones        : ok
  Walking Zeroes      : ok

Done.

6 Odpowiedź przez pepe2k

  • pepe2k
  • pepe2k
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2012-10-29
  • Posty: 5,028

Odp: WDR 4300 - uszkodzony?

Juve napisał/a:

Nieeee, oczywiście, że UARTEM.

Są błędy pamięci:
przynajmniej od:
FAILURE: 0x00000000 != 0x00800000 at offset 0x003c6b79.
.
.
.
FAILURE: 0x00000000 != 0x00800000 at offset 0x003c8479.
FAILURE: 0x00000000 != 0x00800000 at offset 0x003c8601.

Uwalona pamięć RAM?

Niestety, spotkałem się z wieloma egzemplarzami nowiutkich, dopiero co wyjętych z pudełka WDR3600/4300 z podobnymi objawami, przy domyślnych zegarach. Pisałem kiedyś nawet o tym na forum OpenWrt: https://forum.openwrt.org/viewtopic.php … 52#p256252.

Problem można rozwiązać obniżając delikatnie (z doświadczenia, 10-20 MHz załatwia sprawę) zegar DDR (do tego będziesz potrzebować zmodyfikowanego U-Boot). Z wymianą w ramach gwarancji raczej się nie uda - w OFW nie ma nic, czym można przetestować RAM i pokazać, że jest problem (ja takie egzemplarze najczęściej po prostu oddawałem i brałem od dostawcy inne...). Poza tym, to wcale nie musi być (jedyna) przyczyna Twoich problemów - najlepiej jak złapiesz moment restartu na konsoli, może coś ciekawego tam będzie.

7 Odpowiedź przez Juve

  • Juve
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2012-01-10
  • Posty: 62

Odp: WDR 4300 - uszkodzony?

Jest do tego jakiś manual w necie?
Tak wstepnie szukałem to cienko, oj cienko...

8 Odpowiedź przez pepe2k

  • pepe2k
  • pepe2k
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2012-10-29
  • Posty: 5,028

Odp: WDR 4300 - uszkodzony?

Odezwij się do mnie na PW po weekendzie, skompiluję Ci obraz U-Boot z niższym zegarem na DDR i podeślę instrukcję jak to wgrać.