51 Odpowiedź przez panpas44

  • Zarejestrowany: 2019-01-06
  • Posty: 11

Odp: Gargoyle 1.11 na Xiaomi 3G Router

Podepnę się z małym pytaniem.
Czy nowe obrazy  openwrt i garoygle rozwiązały problem na mir3g z USB 3.0?

52 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 116,015

Odp: Gargoyle 1.11 na Xiaomi 3G Router

A jaki był problem? Jeżeli to że zakłóca 2.4 to nie, i programowo tego nie masz jak rozwiązać (poza używaniem usb 2.0).

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

53 Odpowiedź przez panpas44

  • Zarejestrowany: 2019-01-06
  • Posty: 11

Odp: Gargoyle 1.11 na Xiaomi 3G Router

Problem był z  podłączeniem dysku przez hub usb 3.0
Transmission i dysk działa, ale tylko przez hub 2.0

54 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 116,015

Odp: Gargoyle 1.11 na Xiaomi 3G Router

Zainstaluj, podłącz przez hub 3.0 i pokaż

logread
cat /sys/kernel/debug/usb/devices

Ciekawy jestem co się działo.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

55 Odpowiedź przez sebastan

  • Zarejestrowany: 2012-10-05
  • Posty: 452

Odp: Gargoyle 1.11 na Xiaomi 3G Router

Dobrze, wróciłem do zabawy. Przyszedł nowy egzemplarz. Wifi wystartowało normalnie na 1.11.0.1, będę obserwował inne rzeczy, bo być może miałem popsuty model i stąd były wszystkie zmartwienia.

56 Odpowiedź przez sebastan (edytowany przez sebastan 2019-03-21 15:11:14)

  • Zarejestrowany: 2012-10-05
  • Posty: 452

Odp: Gargoyle 1.11 na Xiaomi 3G Router

Wifi na 2.4 działa kiepsko, na 5 dobrze. Czy jest możliwość wyłączenia USB 3.0? Taki ruch na padavanie poprawiał sprawę, ale tam było w gui.

Kiepsko oznacza, że Note8, S8 i telewizor samsunga gubią sieć.

57 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 116,015

Odp: Gargoyle 1.11 na Xiaomi 3G Router

Tu masz całą historyjkę: https://forum.openwrt.org/t/how-to-disa … e/30473/13

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

58 Odpowiedź przez sebastan

  • Zarejestrowany: 2012-10-05
  • Posty: 452

Odp: Gargoyle 1.11 na Xiaomi 3G Router

no tak, łatwiej i pewniej wylutować smile

59 Odpowiedź przez ad2014

  • ad2014
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2014-07-04
  • Posty: 1,139

Odp: Gargoyle 1.11 na Xiaomi 3G Router

sebastan napisał/a:

Wifi na 2.4 działa kiepsko, na 5 dobrze. Czy jest możliwość wyłączenia USB 3.0? Taki ruch na padavanie poprawiał sprawę, ale tam było w gui.

Kiepsko oznacza, że Note8, S8 i telewizor samsunga gubią sieć.

mam kilka rzeczy podłączonych przez hub aktywny usb 3.0  i nie zauważyłem u siebie , jakieś różnicy w działaniu radia 2.4 , hub ma dość długi kabel około 60 cm  i  mam to oddalone od routera   - zero problemów

60 Odpowiedź przez sebastan

  • Zarejestrowany: 2012-10-05
  • Posty: 452

Odp: Gargoyle 1.11 na Xiaomi 3G Router

Nie używam wcale USB. Zawsze miałem tak, że wifi na obu pasmach miałem tą samą nazwę i hasło, więc łączyło się różnie. Przy czym te 3 słabo działające sprzęty (przypadkiem wszystkie samsunga) jak gubiły sieć (wykrzyknik przy zasięgu) to zawsze miałem pewność, że zestawiły się na 2.4. Odkąd zostawiłem tylko 5 Mhz żaden problem nie miał ani razu miejsca.
Pasmo też jest luźne, nie mieszkam w mieście w wieżowcu, ze 3-4 sieci widzę.
Chyba muszę to po prostu zaakceptować, lub kupić inny sprzęt.

61 Odpowiedź przez piotrek_r

  • Zarejestrowany: 2014-03-11
  • Posty: 15

Odp: Gargoyle 1.11 na Xiaomi 3G Router

Ten typ tak ma - było kilka wątków już o problemach z 2.4G w tym modelu. Ja używałem od początku 2018 roku obrazy Cezarego i faktycznie z ostatnimi jest lepiej.
2.4GHz używam tylko w urządzeniach IoT, teraz nie gubią WiFi i da się do nich dostać. Z telefonami też jakby lepiej (choć pojawiają się czasem wykrzykniki) ale staram się używać 5GHz tam gdzie się da więc nie ma tragedii smile
Wcześniej do 2.4 używałem karty na USB - dawała radę smile

62 Odpowiedź przez tptomek

  • Zarejestrowany: 2014-10-20
  • Posty: 431

Odp: Gargoyle 1.11 na Xiaomi 3G Router

Pany wifi mi się wyłącza nie wiem czy to wina oprogramowania czy mojego sprzętu idzie to jakoś sprawdzić ??

63 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 116,015

Odp: Gargoyle 1.11 na Xiaomi 3G Router

W logach, w logach...

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

64 Odpowiedź przez tptomek

  • Zarejestrowany: 2014-10-20
  • Posty: 431

Odp: Gargoyle 1.11 na Xiaomi 3G Router

Trzeba się znać aby umieć je odczytać
Coś takiego mam ostatnie linie

Mon Mar 25 13:37:30 2019 kern.err kernel: [14934.962309] ath: phy0: Unable to reset channel, reset status -5
Mon Mar 25 13:39:12 2019 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 82:fe:ed:e8:17:f4
Mon Mar 25 13:39:12 2019 daemon.info hostapd: wlan0: STA 82:fe:ed:e8:17:f4 IEEE 802.11: disassociated due to inactivity
Mon Mar 25 13:39:13 2019 daemon.info hostapd: wlan0: STA 82:fe:ed:e8:17:f4 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Mon Mar 25 13:42:52 2019 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 30:8f:4c:f2:a0:66
Mon Mar 25 13:42:52 2019 daemon.info hostapd: wlan0: STA 30:8f:4c:f2:a0:66 IEEE 802.11: disassociated due to inactivity
Mon Mar 25 13:42:53 2019 daemon.info hostapd: wlan0: STA 30:8f:4c:f2:a0:66 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)

65 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 116,015

Odp: Gargoyle 1.11 na Xiaomi 3G Router

Te ostatnie linie to rozłączyło klienta z powodu nieaktywności, ale ta pierwsza ath: phy0: Unable to reset channel, reset status -5 to już źle. Ponieważ gargoyle oparte jest na openwrt 18.06 to zainstaluj czyste openwrt z openwrt.org i jak coś się takiego pojawi to zgłaszaj buga na bugs.openwrt.org

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

66 Odpowiedź przez tptomek

  • Zarejestrowany: 2014-10-20
  • Posty: 431

Odp: Gargoyle 1.11 na Xiaomi 3G Router

Mam też coś takiego Mon Mar 25 15:05:31 2019 daemon.err uhttpd[1976]: sh: write error: Broken pipe

Jest szansa żebyś zrobił obraz pod 1043ND V3 z 1.6.2.2 bo to działało idealnie pod V2 jednak wymieniłem na V3 i są problemy to samo miałem na 1.10 nie wiem jak z 1.9.2.3 ale z tego co pamiętam to na V2 chodziło bez problemu z wifi jak nie da rady z 1.6.2.2 to może to 1.9.2.3 udało by się pod V3 zrobić.

67 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 116,015

Odp: Gargoyle 1.11 na Xiaomi 3G Router

To "sh: write error: Broken pipe" się pojawia i będzie jeszcze przez chwilę się pojawiało.

1.6 to AA. Tego czegoś nie ma, nie żyje, nie rozwijane, zakopane głęboko pod ziemią. Nie. Zainstaluj na tym 1043 normalną wersję 1.11.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

68 Odpowiedź przez pablo.see

  • Skąd: Augustów
  • Zarejestrowany: 2010-10-18
  • Posty: 177

Odp: Gargoyle 1.11 na Xiaomi 3G Router

Też nie mam wifi na ostatnim wydaniu Gargoyle by Cezary. Na OpenWRT działa bez problemu wifi 2,4 oraz 5 GHz. Na Gargoyle przełącznik wifi ma tylko opcję "wyłączone" i w bonusie nie przekazuje Internetu (sam router widzi Internet).

Modem: Huawei HG8245Q2  (Servire.net)
Router: Xiaomi AX3000T,          Soft: OpenWrt 24.10-SNAPSHOT r29077-f415748

69 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 116,015

Odp: Gargoyle 1.11 na Xiaomi 3G Router

Standardowo - pokaż wynik

uci show wireless

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

70 Odpowiedź przez pablo.see

  • Skąd: Augustów
  • Zarejestrowany: 2010-10-18
  • Posty: 177

Odp: Gargoyle 1.11 na Xiaomi 3G Router

Zrobię wieczorem jak będę w domu. W logu było głucho, nic na temat wifi.

Natomiast na OpenWRT jest też ciekawie. Nie chce zmienić adresu IP lan routera. Miele i miele i zmiany są oczekujące. A logowanie przez SSH to też ciekawostka: "access denied" chociaż podaje prawidłowe hasło.

Modem: Huawei HG8245Q2  (Servire.net)
Router: Xiaomi AX3000T,          Soft: OpenWrt 24.10-SNAPSHOT r29077-f415748

71 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 116,015

Odp: Gargoyle 1.11 na Xiaomi 3G Router

Jeżeli robisz to w luci to zapomnij, bo nie zmienia adresu w pasku. Zrób w konsoli, zrestartuj router i upewnij się że komputer pobrał nowy adres.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

72 Odpowiedź przez sebastan

  • Zarejestrowany: 2012-10-05
  • Posty: 452

Odp: Gargoyle 1.11 na Xiaomi 3G Router

Ja teraz mam dwa routery i na tym nowo kupionym wifi działa a na tamtym wcześniejszym nie. Te same pliki te same procedury. Na 1.11.0.0 działają oba, na 1.11.0.1 tylko ten nowo kupiony.
MOŻE były jakieś drobne różnice sprzętowe pomiędzy partiami.

73 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 116,015

Odp: Gargoyle 1.11 na Xiaomi 3G Router

Akurat pomiędzy 1.11.0.0 i 1.11.0.1 była aktualizacja sterowników mt76. Zainstaluj moje openwrt 18.06 i zobacz. Jak nie działa  - zgłoś buga. Jak działa to i gargoyle musi bo z tych samych źródeł korzysta.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona

74 Odpowiedź przez pablo.see

  • Skąd: Augustów
  • Zarejestrowany: 2010-10-18
  • Posty: 177

Odp: Gargoyle 1.11 na Xiaomi 3G Router

Oto obiecany log

Using username "root".


BusyBox v1.28.4 () built-in shell (ash)


  _____                             _         _____  _
 |  __ \                           | |       |  __ \| |
 | |  \/ __ _ _ __ __ _  ___  _   _| | ___   | |__) | |
 | | __ / _` | '__/ _` |/ _ \| | | | |/ _ \  |  ___/| |
 | |_\ \ (_| | | | (_| | (_) | |_| | |  __/  | |    | |__
  \____/\__,_|_|  \__, |\___/ \__, |_|\___|  |_|    |____|
                   __/ |       __/ |
                  |___/       |___/

 -----------------------------------------------------------------------------
 |                                                                           |
 | Gargoyle PL 1.11.0.1 (0aa74ad0)                                           |
 | OpenWrt 18.06-SNAPSHOT, r7714-4918fe0291                                  |
 |                                                                           |
 | Build time: 2019-03-10 13:16 CET                                          |
 | Cezary Jackiewicz (obsy), http://eko.one.pl                               |
 |                                                                           |
 -----------------------------------------------------------------------------
 | Machine: Xiaomi Mi Router 3G                                              |
 | Uptime: 0d, 00:01:14                                                      |
 | Load: 0.23 0.10 0.03                                                      |
 | Flash: total: 95.1MB, free: 90.3MB, used: 0%                              |
 | Memory: total: 247.6MB, free: 225.6MB, used: 8%                           |
 | WAN:                                                                      |
 | LAN: 192.168.0.245, leases: 0                                             |
 -----------------------------------------------------------------------------
root@Gargoyle:~# uci show wireless
uci: Entry not found
root@Gargoyle:~# logread
Fri Mar  8 17:00:46 2019 kern.notice kernel: [    0.000000] Linux version 4.14.107 (prometeus@prometeus-VirtualBox) (gcc version 7.4.0 (OpenWrt GCC 7.4.0 r9681-503edc9)) #0 SMP Sun Mar 24 11:10:15 2019
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.000000] SoC Type: MediaTek MT7621 ver:1 eco:3
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.000000] bootconsole [early0] enabled
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.000000] CPU0 revision is: 0001992f (MIPS 1004Kc)
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.000000] MIPS: machine is Xiaomi Mi Router 3G
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.000000] Determined physical RAM map:
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.000000]  memory: 10000000 @ 00000000 (usable)
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.000000] Initrd not found or empty - disabling initrd
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.000000] VPE topology {2,2} total 4
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    0.000000] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    0.000000] Primary data cache 32kB, 4-way, PIPT, no aliases, linesize 32 bytes
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    0.000000] MIPS secondary cache 256kB, 8-way, linesize 32 bytes.
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.000000] Zone ranges:
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.000000]   Normal   [mem 0x0000000000000000-0x000000000fffffff]
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.000000]   HighMem  empty
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.000000] Movable zone start for each node
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.000000] Early memory node ranges
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.000000]   node   0: [mem 0x0000000000000000-0x000000000fffffff]
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000000fffffff]
Fri Mar  8 17:00:46 2019 kern.debug kernel: [    0.000000] On node 0 totalpages: 65536
Fri Mar  8 17:00:46 2019 kern.debug kernel: [    0.000000] free_area_init_node: node 0, pgdat 805980e0, node_mem_map 81003000
Fri Mar  8 17:00:46 2019 kern.debug kernel: [    0.000000]   Normal zone: 512 pages used for memmap
Fri Mar  8 17:00:46 2019 kern.debug kernel: [    0.000000]   Normal zone: 0 pages reserved
Fri Mar  8 17:00:46 2019 kern.debug kernel: [    0.000000]   Normal zone: 65536 pages, LIFO batch:15
Fri Mar  8 17:00:46 2019 kern.notice kernel: [    0.000000] random: get_random_bytes called from start_kernel+0x90/0x4a4 with crng_init=0
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.000000] percpu: Embedded 14 pages/cpu @81211000 s26192 r8192 d22960 u57344
Fri Mar  8 17:00:46 2019 kern.debug kernel: [    0.000000] pcpu-alloc: s26192 r8192 d22960 u57344 alloc=14*4096
Fri Mar  8 17:00:46 2019 kern.debug kernel: [    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 65024
Fri Mar  8 17:00:46 2019 kern.notice kernel: [    0.000000] Kernel command line: console=ttyS0,115200n8 rootfstype=squashfs,jffs2
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.000000] Writing ErrCtl register=00052a80
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.000000] Readback ErrCtl register=00052a80
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.000000] Memory: 253360K/262144K available (4497K kernel code, 230K rwdata, 1000K rodata, 212K init, 248K bss, 8784K reserved, 0K cma-reserved, 0K highmem)
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.000000] Hierarchical RCU implementation.
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.000000] NR_IRQS: 256
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.000000] CPU Clock: 880MHz
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.000000] clocksource: GIC: mask: 0xffffffffffffffff max_cycles: 0xcaf478abb4, max_idle_ns: 440795247997 ns
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 4343773742 ns
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.000010] sched_clock: 32 bits at 440MHz, resolution 2ns, wraps every 4880645118ns
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.007806] Calibrating delay loop... 586.13 BogoMIPS (lpj=2930688)
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.073976] pid_max: default: 32768 minimum: 301
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.078744] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.085253] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.094068] Hierarchical SRCU implementation.
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.099236] smp: Bringing up secondary CPUs ...
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    5.754978] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    5.754987] Primary data cache 32kB, 4-way, PIPT, no aliases, linesize 32 bytes
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    5.754999] MIPS secondary cache 256kB, 8-way, linesize 32 bytes.
Fri Mar  8 17:00:46 2019 kern.info kernel: [    5.755143] CPU1 revision is: 0001992f (MIPS 1004Kc)
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.163985] Synchronize counters for CPU 1: done.
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    5.782285] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    5.782293] Primary data cache 32kB, 4-way, PIPT, no aliases, linesize 32 bytes
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    5.782300] MIPS secondary cache 256kB, 8-way, linesize 32 bytes.
Fri Mar  8 17:00:46 2019 kern.info kernel: [    5.782375] CPU2 revision is: 0001992f (MIPS 1004Kc)
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.255075] Synchronize counters for CPU 2: done.
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    5.871584] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    5.871592] Primary data cache 32kB, 4-way, PIPT, no aliases, linesize 32 bytes
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    5.871600] MIPS secondary cache 256kB, 8-way, linesize 32 bytes.
Fri Mar  8 17:00:46 2019 kern.info kernel: [    5.871683] CPU3 revision is: 0001992f (MIPS 1004Kc)
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.340253] Synchronize counters for CPU 3: done.
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.370118] smp: Brought up 1 node, 4 CPUs
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.378027] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.387819] futex hash table entries: 1024 (order: 3, 32768 bytes)
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.394119] pinctrl core: initialized pinctrl subsystem
Fri Mar  8 17:00:46 2019 kern.info kernel: [    0.400752] NET: Registered protocol family 16
Fri Mar  8 17:00:46 2019 kern.debug kernel: [    0.414633] FPU Affinity set after 11720 emulations
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    0.415317] pull PCIe RST: RALINK_RSTCTRL = 0
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    0.719996] release PCIe RST: RALINK_RSTCTRL = 7000000
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    0.725050] ***** Xtal 40MHz *****
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    0.728399] release PCIe RST: RALINK_RSTCTRL = 7000000
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    0.733497] Port 0 N_FTS = 1b105000
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    0.736963] Port 1 N_FTS = 1b105000
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    0.740412] Port 2 N_FTS = 1b102800
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    1.895481] PCIE2 no card, disable it(RST&CLK)
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    1.899844]  -> 21007f2
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    1.902246] PCIE0 enabled
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    1.904835] PCIE1 enabled
Fri Mar  8 17:00:46 2019 kern.info kernel: [    1.907440] PCI host bridge /pcie@1e140000 ranges:
Fri Mar  8 17:00:46 2019 kern.info kernel: [    1.912213]  MEM 0x0000000060000000..0x000000006fffffff
Fri Mar  8 17:00:46 2019 kern.info kernel: [    1.917368]   IO 0x000000001e160000..0x000000001e16ffff
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    1.922572] PCI coherence region base: 0xbfbf8000, mask/settings: 0x60000000
Fri Mar  8 17:00:46 2019 kern.info kernel: [    1.937857] mt7621_gpio 1e000600.gpio: registering 32 gpios
Fri Mar  8 17:00:46 2019 kern.info kernel: [    1.943677] mt7621_gpio 1e000600.gpio: registering 32 gpios
Fri Mar  8 17:00:46 2019 kern.info kernel: [    1.949341] mt7621_gpio 1e000600.gpio: registering 32 gpios
Fri Mar  8 17:00:46 2019 kern.info kernel: [    1.956880] PCI host bridge to bus 0000:00
Fri Mar  8 17:00:46 2019 kern.info kernel: [    1.960925] pci_bus 0000:00: root bus resource [mem 0x60000000-0x6fffffff]
Fri Mar  8 17:00:46 2019 kern.info kernel: [    1.967779] pci_bus 0000:00: root bus resource [io  0xffffffff]
Fri Mar  8 17:00:46 2019 kern.info kernel: [    1.973610] pci_bus 0000:00: root bus resource [??? 0x00000000 flags 0x0]
Fri Mar  8 17:00:46 2019 kern.info kernel: [    1.980366] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
Fri Mar  8 17:00:46 2019 kern.debug kernel: [    1.988263] pci 0000:00:00.0: [0e8d:0801] type 01 class 0x060400
Fri Mar  8 17:00:46 2019 kern.debug kernel: [    1.988304] pci 0000:00:00.0: reg 0x10: [mem 0x00000000-0x7fffffff]
Fri Mar  8 17:00:46 2019 kern.debug kernel: [    1.988317] pci 0000:00:00.0: reg 0x14: [mem 0x60300000-0x6030ffff]
Fri Mar  8 17:00:46 2019 kern.debug kernel: [    1.988383] pci 0000:00:00.0: supports D1
Fri Mar  8 17:00:46 2019 kern.debug kernel: [    1.988392] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
Fri Mar  8 17:00:46 2019 kern.debug kernel: [    1.988652] pci 0000:00:01.0: [0e8d:0801] type 01 class 0x060400
Fri Mar  8 17:00:46 2019 kern.debug kernel: [    1.988693] pci 0000:00:01.0: reg 0x10: [mem 0x00000000-0x7fffffff]
Fri Mar  8 17:00:46 2019 kern.debug kernel: [    1.988712] pci 0000:00:01.0: reg 0x14: [mem 0x60310000-0x6031ffff]
Fri Mar  8 17:00:46 2019 kern.debug kernel: [    1.988777] pci 0000:00:01.0: supports D1
Fri Mar  8 17:00:46 2019 kern.debug kernel: [    1.988787] pci 0000:00:01.0: PME# supported from D0 D1 D3hot
Fri Mar  8 17:00:46 2019 kern.debug kernel: [    1.989269] pci 0000:01:00.0: [14c3:7603] type 00 class 0x028000
Fri Mar  8 17:00:46 2019 kern.debug kernel: [    1.989327] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x000fffff]
Fri Mar  8 17:00:46 2019 kern.debug kernel: [    1.989459] pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
Fri Mar  8 17:00:46 2019 kern.debug kernel: [    1.989664] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
Fri Mar  8 17:00:46 2019 kern.debug kernel: [    1.989890] pci 0000:02:00.0: [14c3:7662] type 00 class 0x028000
Fri Mar  8 17:00:46 2019 kern.debug kernel: [    1.989955] pci 0000:02:00.0: reg 0x10: [mem 0x00000000-0x000fffff 64bit]
Fri Mar  8 17:00:46 2019 kern.debug kernel: [    1.990002] pci 0000:02:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
Fri Mar  8 17:00:46 2019 kern.debug kernel: [    1.990098] pci 0000:02:00.0: PME# supported from D0 D3hot D3cold
Fri Mar  8 17:00:46 2019 kern.debug kernel: [    1.990302] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
Fri Mar  8 17:00:46 2019 kern.debug kernel: [    1.990326] pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 02
Fri Mar  8 17:00:46 2019 kern.info kernel: [    1.990468] pci 0000:00:00.0: BAR 0: no space for [mem size 0x80000000]
Fri Mar  8 17:00:46 2019 kern.info kernel: [    1.996983] pci 0000:00:00.0: BAR 0: failed to assign [mem size 0x80000000]
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.003919] pci 0000:00:01.0: BAR 0: no space for [mem size 0x80000000]
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.010458] pci 0000:00:01.0: BAR 0: failed to assign [mem size 0x80000000]
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.017392] pci 0000:00:00.0: BAR 8: assigned [mem 0x60000000-0x600fffff]
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.024118] pci 0000:00:01.0: BAR 8: assigned [mem 0x60100000-0x601fffff]
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.030875] pci 0000:00:01.0: BAR 9: assigned [mem 0x60200000-0x602fffff pref]
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.038026] pci 0000:00:00.0: BAR 1: assigned [mem 0x60300000-0x6030ffff]
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.044782] pci 0000:00:01.0: BAR 1: assigned [mem 0x60310000-0x6031ffff]
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.051508] pci 0000:01:00.0: BAR 0: assigned [mem 0x60000000-0x600fffff]
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.058263] pci 0000:00:00.0: PCI bridge to [bus 01]
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.063166] pci 0000:00:00.0:   bridge window [mem 0x60000000-0x600fffff]
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.069936] pci 0000:02:00.0: BAR 0: assigned [mem 0x60100000-0x601fffff 64bit]
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.077176] pci 0000:02:00.0: BAR 6: assigned [mem 0x60200000-0x6020ffff pref]
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.084346] pci 0000:00:01.0: PCI bridge to [bus 02]
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.089257] pci 0000:00:01.0:   bridge window [mem 0x60100000-0x601fffff]
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.096011] pci 0000:00:01.0:   bridge window [mem 0x60200000-0x602fffff pref]
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.104524] clocksource: Switched to clocksource GIC
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.111016] NET: Registered protocol family 2
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.115953] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.122838] TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.129287] TCP: Hash tables configured (established 2048 bind 2048)
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.135695] UDP hash table entries: 256 (order: 1, 8192 bytes)
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.141457] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.147933] NET: Registered protocol family 1
Fri Mar  8 17:00:46 2019 kern.debug kernel: [    2.152253] PCI: CLS 0 bytes, default 32
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.384474] 4 CPUs re-calibrate udelay(lpj = 2924544)
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    2.390968] Crashlog allocated RAM at address 0x3f00000
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.396535] workingset: timestamp_bits=30 max_order=16 bucket_order=0
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.410170] squashfs: version 4.0 (2009/01/31) Phillip Lougher
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.415980] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
Fri Mar  8 17:00:46 2019 kern.notice kernel: [    2.427466] random: fast init done
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.432525] io scheduler noop registered
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.436392] io scheduler deadline registered (default)
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.442430] Serial: 8250/16550 driver, 3 ports, IRQ sharing disabled
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.450211] console [ttyS0] disabled
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.453755] 1e000c00.uartlite: ttyS0 at MMIO 0x1e000c00 (irq = 18, base_baud = 3125000) is a 16550A
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.462766] console [ttyS0] enabled
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.469637] bootconsole [early0] disabled
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    2.478253] cacheinfo: Unable to detect cache hierarchy for CPU 0
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    2.485148] MediaTek Nand driver init, version v2.1 Fix AHB virt2phys error
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    2.492219] Enable NFI Clock
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    2.495138] # MTK NAND # : Use HW ECC
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.498803] Device not found, ID: c8d1
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    2.502528] Not Support this Device!
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    2.506267] chip_mode=00000001
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    2.509306] Support this Device in MTK table! c8d1
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    2.514252] [NAND]select ecc bit:4, sparesize :64 spare_per_sector=16
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.520721] nand: device found, Manufacturer ID: 0xc8, Chip ID: 0xd1
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.527054] nand: ESMT NAND 128MiB 3,3V 8-bit
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.531391] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.538955] Scanning device for bad blocks
Fri Mar  8 17:00:46 2019 kern.notice kernel: [    2.688438] 10 fixed-partitions partitions found on MTD device MT7621-NAND
Fri Mar  8 17:00:46 2019 kern.notice kernel: [    2.695293] Creating 10 MTD partitions on "MT7621-NAND":
Fri Mar  8 17:00:46 2019 kern.notice kernel: [    2.700588] 0x000000000000-0x000000080000 : "Bootloader"
Fri Mar  8 17:00:46 2019 kern.notice kernel: [    2.706986] 0x000000080000-0x0000000c0000 : "Config"
Fri Mar  8 17:00:46 2019 kern.notice kernel: [    2.712894] 0x0000000c0000-0x000000100000 : "Bdata"
Fri Mar  8 17:00:46 2019 kern.notice kernel: [    2.718784] 0x000000100000-0x000000140000 : "Factory"
Fri Mar  8 17:00:46 2019 kern.notice kernel: [    2.724858] 0x000000140000-0x000000180000 : "crash"
Fri Mar  8 17:00:46 2019 kern.notice kernel: [    2.730685] 0x000000180000-0x0000001c0000 : "crash_syslog"
Fri Mar  8 17:00:46 2019 kern.notice kernel: [    2.737192] 0x0000001c0000-0x000000200000 : "reserved0"
Fri Mar  8 17:00:46 2019 kern.notice kernel: [    2.743396] 0x000000200000-0x000000600000 : "kernel_stock"
Fri Mar  8 17:00:46 2019 kern.notice kernel: [    2.749934] 0x000000600000-0x000000a00000 : "kernel"
Fri Mar  8 17:00:46 2019 kern.notice kernel: [    2.755949] 0x000000a00000-0x000007f80000 : "ubi"
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    2.762553] [mtk_nand] probe successfully!
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    2.767391] Signature matched and data read!
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    2.771638] load_fact_bbt success 1023
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.776076] libphy: Fixed MDIO Bus: probed
Fri Mar  8 17:00:46 2019 kern.info kernel: [    2.847088] libphy: mdio: probed
Fri Mar  8 17:00:46 2019 kern.info kernel: [    4.250657] mtk_soc_eth 1e100000.ethernet: loaded mt7530 driver
Fri Mar  8 17:00:46 2019 kern.info kernel: [    4.257286] mtk_soc_eth 1e100000.ethernet eth0: mediatek frame engine at 0xbe100000, irq 20
Fri Mar  8 17:00:46 2019 kern.info kernel: [    4.267715] NET: Registered protocol family 10
Fri Mar  8 17:00:46 2019 kern.info kernel: [    4.273503] Segment Routing with IPv6
Fri Mar  8 17:00:46 2019 kern.info kernel: [    4.277288] NET: Registered protocol family 17
Fri Mar  8 17:00:46 2019 kern.info kernel: [    4.281753] 8021q: 802.1Q VLAN Support v1.8
Fri Mar  8 17:00:46 2019 kern.notice kernel: [    4.288747] UBI: auto-attach mtd9
Fri Mar  8 17:00:46 2019 kern.notice kernel: [    4.292075] ubi0: attaching mtd9
Fri Mar  8 17:00:46 2019 kern.notice kernel: [    5.402517] ubi0: scanning is finished
Fri Mar  8 17:00:46 2019 kern.notice kernel: [    5.422367] ubi0: attached mtd9 (name "ubi", size 117 MiB)
Fri Mar  8 17:00:46 2019 kern.notice kernel: [    5.427869] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
Fri Mar  8 17:00:46 2019 kern.notice kernel: [    5.434725] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
Fri Mar  8 17:00:46 2019 kern.notice kernel: [    5.441479] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
Fri Mar  8 17:00:46 2019 kern.notice kernel: [    5.448417] ubi0: good PEBs: 940, bad PEBs: 0, corrupted PEBs: 0
Fri Mar  8 17:00:46 2019 kern.notice kernel: [    5.454393] ubi0: user volume: 2, internal volumes: 1, max. volumes count: 128
Fri Mar  8 17:00:46 2019 kern.notice kernel: [    5.461593] ubi0: max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 700208569
Fri Mar  8 17:00:46 2019 kern.notice kernel: [    5.470609] ubi0: available PEBs: 0, total reserved PEBs: 940, PEBs reserved for bad PEB handling: 20
Fri Mar  8 17:00:46 2019 kern.notice kernel: [    5.479817] ubi0: background thread "ubi_bgt0d" started, PID 372
Fri Mar  8 17:00:46 2019 kern.info kernel: [    5.481500] block ubiblock0_0: created from ubi0:0(rootfs)
Fri Mar  8 17:00:46 2019 kern.notice kernel: [    5.491291] ubiblock: device ubiblock0_0 (rootfs) set to be root filesystem
Fri Mar  8 17:00:46 2019 kern.info kernel: [    5.498242] hctosys: unable to open rtc device (rtc0)
Fri Mar  8 17:00:46 2019 kern.info kernel: [    5.503524] usb_vbus: disabling
Fri Mar  8 17:00:46 2019 kern.info kernel: [    5.512756] VFS: Mounted root (squashfs filesystem) readonly on device 254:0.
Fri Mar  8 17:00:46 2019 kern.info kernel: [    5.520415] Freeing unused kernel memory: 212K
Fri Mar  8 17:00:46 2019 kern.warn kernel: [    5.524897] This architecture does not have kernel memory protection.
Fri Mar  8 17:00:46 2019 user.info kernel: [    6.026307] init: Console is alive
Fri Mar  8 17:00:46 2019 user.info kernel: [    6.029946] init: - watchdog -
Fri Mar  8 17:00:46 2019 user.info kernel: [    6.104898] init: - preinit -
Fri Mar  8 17:00:46 2019 kern.info kernel: [    7.091899] mtk_soc_eth 1e100000.ethernet: PPE started
Fri Mar  8 17:00:46 2019 kern.info kernel: [    8.440794] mtk_soc_eth 1e100000.ethernet eth0: port 3 link up
Fri Mar  8 17:00:46 2019 user.info kernel: [   10.317861] mount_root: loading kmods from internal overlay
Fri Mar  8 17:00:46 2019 user.err kernel: [   10.329112] mount_root: failed to launch kmodloader from internal overlay
Fri Mar  8 17:00:46 2019 kern.notice kernel: [   10.865821] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" started, PID 430
Fri Mar  8 17:00:46 2019 kern.notice kernel: [   10.905697] random: procd: uninitialized urandom read (4 bytes read)
Fri Mar  8 17:00:46 2019 kern.notice kernel: [   10.940244] UBIFS (ubi0:1): recovery needed
Fri Mar  8 17:00:46 2019 kern.notice kernel: [   11.077963] UBIFS (ubi0:1): recovery completed
Fri Mar  8 17:00:46 2019 kern.notice kernel: [   11.082515] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name "rootfs_data"
Fri Mar  8 17:00:46 2019 kern.notice kernel: [   11.090327] UBIFS (ubi0:1): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Fri Mar  8 17:00:46 2019 kern.notice kernel: [   11.100216] UBIFS (ubi0:1): FS size: 108564480 bytes (103 MiB, 855 LEBs), journal size 5459968 bytes (5 MiB, 43 LEBs)
Fri Mar  8 17:00:46 2019 kern.notice kernel: [   11.110790] UBIFS (ubi0:1): reserved for root: 4952683 bytes (4836 KiB)
Fri Mar  8 17:00:46 2019 kern.notice kernel: [   11.117392] UBIFS (ubi0:1): media format: w4/r0 (latest is w5/r0), UUID 6871FFBA-AB2A-4257-A2FB-07002BBF89FA, small LPT model
Fri Mar  8 17:00:46 2019 user.info kernel: [   11.131351] block: attempting to load /tmp/ubifs_cfg/upper/etc/config/fstab
Fri Mar  8 17:00:46 2019 user.info kernel: [   11.147845] block: extroot: not configured
Fri Mar  8 17:00:46 2019 kern.notice kernel: [   11.184771] UBIFS (ubi0:1): un-mount UBI device 0
Fri Mar  8 17:00:46 2019 kern.notice kernel: [   11.189485] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" stops
Fri Mar  8 17:00:46 2019 kern.notice kernel: [   11.201879] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" started, PID 433
Fri Mar  8 17:00:46 2019 kern.notice kernel: [   11.384942] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name "rootfs_data"
Fri Mar  8 17:00:46 2019 kern.notice kernel: [   11.392757] UBIFS (ubi0:1): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Fri Mar  8 17:00:46 2019 kern.notice kernel: [   11.402719] UBIFS (ubi0:1): FS size: 108564480 bytes (103 MiB, 855 LEBs), journal size 5459968 bytes (5 MiB, 43 LEBs)
Fri Mar  8 17:00:46 2019 kern.notice kernel: [   11.413302] UBIFS (ubi0:1): reserved for root: 4952683 bytes (4836 KiB)
Fri Mar  8 17:00:46 2019 kern.notice kernel: [   11.419907] UBIFS (ubi0:1): media format: w4/r0 (latest is w5/r0), UUID 6871FFBA-AB2A-4257-A2FB-07002BBF89FA, small LPT model
Fri Mar  8 17:00:46 2019 user.info kernel: [   11.792821] block: attempting to load /tmp/ubifs_cfg/upper/etc/config/fstab
Fri Mar  8 17:00:46 2019 user.info kernel: [   11.807567] block: extroot: not configured
Fri Mar  8 17:00:46 2019 user.info kernel: [   11.847467] mount_root: switching to ubifs overlay
Fri Mar  8 17:00:46 2019 user.warn kernel: [   11.870828] urandom-seed: Seeding with /etc/urandom.seed
Fri Mar  8 17:00:46 2019 kern.info kernel: [   11.966675] mtk_soc_eth 1e100000.ethernet: 0x100 = 0x6060000c, 0x10c = 0x80818
Fri Mar  8 17:00:46 2019 user.info kernel: [   11.981508] procd: - early -
Fri Mar  8 17:00:46 2019 user.info kernel: [   11.984567] procd: - watchdog -
Fri Mar  8 17:00:46 2019 user.info kernel: [   12.634751] procd: - watchdog -
Fri Mar  8 17:00:46 2019 user.info kernel: [   12.638306] procd: - ubus -
Fri Mar  8 17:00:46 2019 kern.notice kernel: [   12.748061] random: ubusd: uninitialized urandom read (4 bytes read)
Fri Mar  8 17:00:46 2019 kern.notice kernel: [   12.851912] random: ubusd: uninitialized urandom read (4 bytes read)
Fri Mar  8 17:00:46 2019 kern.notice kernel: [   12.858842] random: ubusd: uninitialized urandom read (4 bytes read)
Fri Mar  8 17:00:46 2019 user.info kernel: [   12.866213] procd: - init -
Fri Mar  8 17:00:46 2019 kern.warn kernel: [   15.022111] urandom_read: 5 callbacks suppressed
Fri Mar  8 17:00:46 2019 kern.notice kernel: [   15.022123] random: jshn: uninitialized urandom read (4 bytes read)
Fri Mar  8 17:00:46 2019 user.notice dnsmasq: DNS rebinding protection is active, will discard upstream RFC1918 responses!
Fri Mar  8 17:00:46 2019 user.notice dnsmasq: Allowing 127.0.0.0/8 responses
Fri Mar  8 17:00:46 2019 user.notice dnsmasq: Allowing RFC1918 responses for domain free.aero2.net.pl
Fri Mar  8 17:00:46 2019 user.notice dnsmasq: Allowing RFC1918 responses for domain .bit
Fri Mar  8 17:00:46 2019 user.notice dnsmasq: Allowing RFC1918 responses for domain .glue
Fri Mar  8 17:00:46 2019 user.notice dnsmasq: Allowing RFC1918 responses for domain .parody
Fri Mar  8 17:00:46 2019 user.notice dnsmasq: Allowing RFC1918 responses for domain .dyn
Fri Mar  8 17:00:46 2019 user.notice dnsmasq: Allowing RFC1918 responses for domain .bbs
Fri Mar  8 17:00:46 2019 user.notice dnsmasq: Allowing RFC1918 responses for domain .free
Fri Mar  8 17:00:46 2019 user.notice dnsmasq: Allowing RFC1918 responses for domain .fur
Fri Mar  8 17:00:46 2019 user.notice dnsmasq: Allowing RFC1918 responses for domain .geek
Fri Mar  8 17:00:46 2019 user.notice dnsmasq: Allowing RFC1918 responses for domain .gopher
Fri Mar  8 17:00:46 2019 user.notice dnsmasq: Allowing RFC1918 responses for domain .indy
Fri Mar  8 17:00:46 2019 user.notice dnsmasq: Allowing RFC1918 responses for domain .ing
Fri Mar  8 17:00:46 2019 user.notice dnsmasq: Allowing RFC1918 responses for domain .null
Fri Mar  8 17:00:46 2019 user.notice dnsmasq: Allowing RFC1918 responses for domain .oss
Fri Mar  8 17:00:46 2019 user.notice dnsmasq: Allowing RFC1918 responses for domain .micro
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: started, version 2.80 cachesize 150
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: DNS service limited to local subnets
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC no-ID loop-detect inotify dumpfile
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using local addresses only for domain test
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using local addresses only for domain onion
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using local addresses only for domain localhost
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using local addresses only for domain local
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using local addresses only for domain invalid
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using local addresses only for domain bind
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using nameserver 95.142.171.235#53 for domain micro
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using nameserver 95.211.32.162#53 for domain micro
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using nameserver 66.244.95.20#53 for domain micro
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using nameserver 95.142.171.235#53 for domain oss
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using nameserver 95.211.32.162#53 for domain oss
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using nameserver 66.244.95.20#53 for domain oss
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using nameserver 95.142.171.235#53 for domain null
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using nameserver 95.211.32.162#53 for domain null
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using nameserver 66.244.95.20#53 for domain null
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using nameserver 95.142.171.235#53 for domain ing
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using nameserver 95.211.32.162#53 for domain ing
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using nameserver 66.244.95.20#53 for domain ing
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using nameserver 95.142.171.235#53 for domain indy
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using nameserver 95.211.32.162#53 for domain indy
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using nameserver 66.244.95.20#53 for domain indy
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using nameserver 95.142.171.235#53 for domain gopher
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using nameserver 95.211.32.162#53 for domain gopher
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using nameserver 66.244.95.20#53 for domain gopher
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using nameserver 95.142.171.235#53 for domain geek
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using nameserver 95.211.32.162#53 for domain geek
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using nameserver 66.244.95.20#53 for domain geek
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using nameserver 95.142.171.235#53 for domain fur
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using nameserver 95.211.32.162#53 for domain fur
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using nameserver 66.244.95.20#53 for domain fur
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using nameserver 95.142.171.235#53 for domain free
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using nameserver 95.211.32.162#53 for domain free
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using nameserver 66.244.95.20#53 for domain free
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using nameserver 95.142.171.235#53 for domain bbs
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using nameserver 95.211.32.162#53 for domain bbs
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using nameserver 66.244.95.20#53 for domain bbs
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: using 12 more nameservers
Fri Mar  8 17:00:47 2019 daemon.warn dnsmasq[757]: no servers found in /tmp/resolv.conf.auto, will retry
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: read /etc/hosts - 5 addresses
Fri Mar  8 17:00:47 2019 daemon.info dnsmasq[757]: read /tmp/hosts/dhcp.cfg01411c - 0 addresses
Fri Mar  8 17:00:47 2019 authpriv.info dropbear[784]: Not backgrounding
Fri Mar  8 17:00:50 2019 user.notice : Added device handler type: tunnel
Fri Mar  8 17:00:50 2019 user.notice : Added device handler type: Network device
Fri Mar  8 17:00:50 2019 user.notice : Added device handler type: bridge
Fri Mar  8 17:00:50 2019 user.notice : Added device handler type: veth
Fri Mar  8 17:00:50 2019 user.notice : Added device handler type: macvlan
Fri Mar  8 17:00:50 2019 user.notice : Added device handler type: 8021ad
Fri Mar  8 17:00:50 2019 user.notice : Added device handler type: 8021q
Fri Mar  8 17:00:51 2019 daemon.err block: /dev/ubiblock0_0 is already mounted on /rom
Fri Mar  8 17:00:51 2019 daemon.err block: /dev/ubi0_1 is already mounted on /overlay
Fri Mar  8 17:00:52 2019 kern.info kernel: [   21.615037] mtk_soc_eth 1e100000.ethernet: PPE started
Fri Mar  8 17:00:52 2019 kern.info kernel: [   21.624231] device eth0 entered promiscuous mode
Fri Mar  8 17:00:52 2019 kern.info kernel: [   21.631357] br-lan: port 1(eth0.1) entered blocking state
Fri Mar  8 17:00:52 2019 kern.info kernel: [   21.636883] br-lan: port 1(eth0.1) entered disabled state
Fri Mar  8 17:00:52 2019 kern.info kernel: [   21.642918] device eth0.1 entered promiscuous mode
Fri Mar  8 17:00:52 2019 kern.info kernel: [   21.651508] br-lan: port 1(eth0.1) entered blocking state
Fri Mar  8 17:00:52 2019 kern.info kernel: [   21.656956] br-lan: port 1(eth0.1) entered forwarding state
Fri Mar  8 17:00:52 2019 kern.info kernel: [   21.662989] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
Fri Mar  8 17:00:52 2019 daemon.notice netifd: Interface 'lan' is enabled
Fri Mar  8 17:00:52 2019 daemon.notice netifd: Interface 'lan' is setting up now
Fri Mar  8 17:00:52 2019 daemon.notice netifd: Interface 'lan' is now up
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: reading /tmp/resolv.conf.auto
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using local addresses only for domain test
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using local addresses only for domain onion
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using local addresses only for domain localhost
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using local addresses only for domain local
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using local addresses only for domain invalid
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using local addresses only for domain bind
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using nameserver 95.142.171.235#53 for domain micro
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using nameserver 95.211.32.162#53 for domain micro
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using nameserver 66.244.95.20#53 for domain micro
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using nameserver 95.142.171.235#53 for domain oss
Fri Mar  8 17:00:52 2019 daemon.notice netifd: Interface 'loopback' is enabled
Fri Mar  8 17:00:52 2019 daemon.notice netifd: Interface 'loopback' is setting up now
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using nameserver 95.211.32.162#53 for domain oss
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using nameserver 66.244.95.20#53 for domain oss
Fri Mar  8 17:00:52 2019 daemon.notice netifd: Interface 'loopback' is now up
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using nameserver 95.142.171.235#53 for domain null
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using nameserver 95.211.32.162#53 for domain null
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using nameserver 66.244.95.20#53 for domain null
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using nameserver 95.142.171.235#53 for domain ing
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using nameserver 95.211.32.162#53 for domain ing
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using nameserver 66.244.95.20#53 for domain ing
Fri Mar  8 17:00:52 2019 daemon.notice netifd: Interface 'wan' is enabled
Fri Mar  8 17:00:52 2019 daemon.notice netifd: Interface 'wan6' is enabled
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using nameserver 95.142.171.235#53 for domain indy
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using nameserver 95.211.32.162#53 for domain indy
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using nameserver 66.244.95.20#53 for domain indy
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using nameserver 95.142.171.235#53 for domain gopher
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using nameserver 95.211.32.162#53 for domain gopher
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using nameserver 66.244.95.20#53 for domain gopher
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using nameserver 95.142.171.235#53 for domain geek
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using nameserver 95.211.32.162#53 for domain geek
Fri Mar  8 17:00:52 2019 daemon.notice netifd: bridge 'br-lan' link is up
Fri Mar  8 17:00:52 2019 daemon.notice netifd: Interface 'lan' has link connectivity
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using nameserver 66.244.95.20#53 for domain geek
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using nameserver 95.142.171.235#53 for domain fur
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using nameserver 95.211.32.162#53 for domain fur
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using nameserver 66.244.95.20#53 for domain fur
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using nameserver 95.142.171.235#53 for domain free
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using nameserver 95.211.32.162#53 for domain free
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using nameserver 66.244.95.20#53 for domain free
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using nameserver 95.142.171.235#53 for domain bbs
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using nameserver 95.211.32.162#53 for domain bbs
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using nameserver 66.244.95.20#53 for domain bbs
Fri Mar  8 17:00:52 2019 daemon.warn dnsmasq[757]: ignoring nameserver 192.168.0.245 - local interface
Fri Mar  8 17:00:52 2019 daemon.info dnsmasq[757]: using 12 more nameservers
Fri Mar  8 17:00:52 2019 daemon.notice netifd: Network device 'eth0' link is up
Fri Mar  8 17:00:52 2019 daemon.notice netifd: VLAN 'eth0.1' link is up
Fri Mar  8 17:00:52 2019 daemon.notice netifd: Network device 'lo' link is up
Fri Mar  8 17:00:52 2019 daemon.notice netifd: Interface 'loopback' has link connectivity
Fri Mar  8 17:00:52 2019 daemon.notice netifd: VLAN 'eth0.2' link is up
Fri Mar  8 17:00:52 2019 daemon.notice netifd: Interface 'wan' has link connectivity
Fri Mar  8 17:00:52 2019 daemon.notice netifd: Interface 'wan' is setting up now
Fri Mar  8 17:00:52 2019 daemon.notice netifd: Interface 'wan6' has link connectivity
Fri Mar  8 17:00:52 2019 daemon.notice netifd: Interface 'wan6' is setting up now
Fri Mar  8 17:00:52 2019 daemon.notice netifd: Interface 'wan6' is now up
Fri Mar  8 17:00:52 2019 daemon.notice netifd: wan (1040): udhcpc: started, v1.28.4
Fri Mar  8 17:00:52 2019 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Fri Mar  8 17:00:52 2019 daemon.notice netifd: wan (1040): udhcpc: sending discover
Fri Mar  8 17:00:53 2019 kern.info kernel: [   22.635163] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
Fri Mar  8 17:00:53 2019 kern.notice kernel: [   22.732468] random: crng init done
Fri Mar  8 17:00:54 2019 user.err : error starting threads: errno 89 (Function not implemented)
Fri Mar  8 17:00:54 2019 daemon.notice procd: /etc/rc.d/S60nfsd: exportfs: could not open /var/lib/nfs/.xtab.lock for locking: errno 2 (No such file or directory)
Fri Mar  8 17:00:54 2019 daemon.notice procd: /etc/rc.d/S60nfsd: exportfs: could not open /var/lib/nfs/.etab.lock for locking: errno 2 (No such file or directory)
Fri Mar  8 17:00:54 2019 daemon.notice procd: /etc/rc.d/S60nfsd: exportfs: can't lock /var/lib/nfs/etab for writing
Fri Mar  8 17:00:54 2019 daemon.notice procd: /etc/rc.d/S60nfsd: exportfs: could not open /var/lib/nfs/.xtab.lock for locking: errno 2 (No such file or directory)
Fri Mar  8 17:00:54 2019 daemon.notice procd: /etc/rc.d/S60nfsd: exportfs: can't lock /var/lib/nfs/xtab for writing
Fri Mar  8 17:00:54 2019 daemon.notice procd: /etc/rc.d/S60nfsd: Command failed: Not found
Fri Mar  8 17:00:54 2019 user.notice dnsmasq: found already running DHCP-server on interface 'br-lan' refusing to start, use 'option force 1' to override
Fri Mar  8 17:00:54 2019 daemon.notice procd: /etc/rc.d/S90ddns_gargoyle: ERROR: No valid dynamic DNS service configurations defined
Fri Mar  8 17:00:54 2019 daemon.notice procd: /etc/rc.d/S90ddns_gargoyle: (Did you specify correct configuration file path?)
Fri Mar  8 17:00:54 2019 daemon.info dnsmasq[757]: read /etc/hosts - 5 addresses
Fri Mar  8 17:00:54 2019 daemon.info dnsmasq[757]: read /tmp/hosts/dhcp.cfg01411c - 0 addresses
Fri Mar  8 17:00:55 2019 daemon.notice netifd: wan (1040): udhcpc: sending discover
Fri Mar  8 17:00:58 2019 daemon.notice netifd: wan (1040): udhcpc: sending discover
Fri Mar  8 17:01:20 2019 user.notice root: vsftpd init: mounted = 0
Fri Mar  8 17:01:20 2019 daemon.notice procd: /etc/rc.d/S90vsftpd: ERROR: No drives attached, no directories to share!
Fri Mar  8 17:01:20 2019 daemon.info procd: - init complete -
Fri Mar  8 17:01:29 2019 user.notice firewall: Reloading firewall due to ifup of wan6 (eth0.2)
Fri Mar  8 17:01:43 2019 authpriv.info dropbear[1678]: Child connection from 192.168.0.1:58498
Fri Mar  8 17:01:44 2019 authpriv.notice dropbear[1678]: Password auth succeeded for 'root' from 192.168.0.1:58498
root@Gargoyle:~#
Modem: Huawei HG8245Q2  (Servire.net)
Router: Xiaomi AX3000T,          Soft: OpenWrt 24.10-SNAPSHOT r29077-f415748

75 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 116,015

Odp: Gargoyle 1.11 na Xiaomi 3G Router

Co ty zainstalowałeś? To nie jest mój kernel - to jakaś staroć i na dodatek to nie mój kompilat. Jak ty zrobiłeś aktualizację? Widać że zostawiłeś kernel w prometeusza.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

Cezary's Strona