1 Temat przez r44

  • r44
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2018-01-26
  • Posty: 45

Temat: Xiaomi WiFi Router 3G i Seagate Backup Plus Hub - Mediatek SOC USB3.0

Po podłączeniu powyższego dysku nie mam go w /dev/sd*

Zgłasza się tylko hub usb:
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.426954] xhci-mtk 1e1c0000.xhci: xHCI Host Controller
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.432354] xhci-mtk 1e1c0000.xhci: new USB bus registered, assigned bus number 1
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.450958] xhci-mtk 1e1c0000.xhci: hcc params 0x01401198 hci version 0x96 quirks 0x00210010
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.459434] xhci-mtk 1e1c0000.xhci: irq 19, io mem 0x1e1c0000
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.466275] hub 1-0:1.0: USB hub found
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.470099] hub 1-0:1.0: 2 ports detected
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.474622] xhci-mtk 1e1c0000.xhci: xHCI Host Controller
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.479932] xhci-mtk 1e1c0000.xhci: new USB bus registered, assigned bus number 2
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.487575] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.496546] hub 2-0:1.0: USB hub found
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.500359] hub 2-0:1.0: 1 port detected
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.510080] usbcore: registered new interface driver usb-storage
Tue Jan 30 20:24:53 2018 user.info kernel: [    7.516443] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
Tue Jan 30 20:24:53 2018 user.info kernel: [    7.531042] init: - preinit -
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.871000] usb 2-1: new SuperSpeed USB device number 2 using xhci-mtk
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.926425] hub 2-1:1.0: USB hub found
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.930517] hub 2-1:1.0: 3 ports detected
Tue Jan 30 20:24:53 2018 kern.info kernel: [    8.060845] usb 1-1: new high-speed USB device number 2 using xhci-mtk
Tue Jan 30 20:24:53 2018 kern.info kernel: [    8.234850] hub 1-1:1.0: USB hub found
Tue Jan 30 20:24:53 2018 kern.info kernel: [    8.238927] hub 1-1:1.0: 3 ports detected
Tue Jan 30 20:24:53 2018 kern.info kernel: [    8.350880] usb 2-1.1: new SuperSpeed USB device number 3 using xhci-mtk

Czy problemem może być kontroler usb3..0 mediatec'a?
usb 1-1: new high-speed USB device number 2 using xhci-mtk

2 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,915

Odp: Xiaomi WiFi Router 3G i Seagate Backup Plus Hub - Mediatek SOC USB3.0

cat /sys/kernel/debug/usb/devices

pokaż.

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

Cezary's Strona

3 Odpowiedź przez r44

  • r44
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2018-01-26
  • Posty: 45

Odp: Xiaomi WiFi Router 3G i Seagate Backup Plus Hub - Mediatek SOC USB3.0

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 2
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev= 4.09
S:  Manufacturer=Linux 4.9.76 xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=1e1c0000.xhci
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480  MxCh= 3
D:  Ver= 2.10 Cls=09(hub  ) Sub=00 Prot=02 MxPS=64 #Cfgs=  1
P:  Vendor=0bc2 ProdID=ab44 Rev=48.85
S:  Manufacturer=Seagate
S:  Product=Backup+ Hub
S:  SerialNumber=01CB6342B0JL
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=01 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   1 Ivl=256ms
I:* If#= 0 Alt= 1 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=02 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   1 Ivl=256ms

T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=5000 MxCh= 1
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 3.00 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
P:  Vendor=1d6b ProdID=0003 Rev= 4.09
S:  Manufacturer=Linux 4.9.76 xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=1e1c0000.xhci
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

T:  Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=5000 MxCh= 3
D:  Ver= 3.00 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
P:  Vendor=0bc2 ProdID=ab45 Rev=48.85
S:  Manufacturer=Seagate
S:  Product=Backup+ Hub
S:  SerialNumber=01CB6342B0JL
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=83(I) Atr=13(Int.) MxPS=   2 Ivl=16ms

T:  Bus=02 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#=  3 Spd=5000 MxCh= 0
D:  Ver= 3.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 9 #Cfgs=  1
P:  Vendor=0bc2 ProdID=ab38 Rev= 1.00
S:  Manufacturer=Seagate
S:  Product=Backup+ Hub BK
S:  SerialNumber=NA8T1B9F
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=(none)
E:  Ad=81(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
I:  If#= 0 Alt= 1 #EPs= 4 Cls=08(stor.) Sub=06 Prot=62 Driver=(none)
E:  Ad=81(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=83(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=04(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms

4 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,915

Odp: Xiaomi WiFi Router 3G i Seagate Backup Plus Hub - Mediatek SOC USB3.0

Sterowników nie masz.  Zainstaluj kmod-usb-storage-uas

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

Cezary's Strona

5 Odpowiedź przez r44

  • r44
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2018-01-26
  • Posty: 45

Odp: Xiaomi WiFi Router 3G i Seagate Backup Plus Hub - Mediatek SOC USB3.0

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 2
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev= 4.09
S:  Manufacturer=Linux 4.9.76 xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=1e1c0000.xhci
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480  MxCh= 3
D:  Ver= 2.10 Cls=09(hub  ) Sub=00 Prot=02 MxPS=64 #Cfgs=  1
P:  Vendor=0bc2 ProdID=ab44 Rev=48.85
S:  Manufacturer=Seagate
S:  Product=Backup+ Hub
S:  SerialNumber=01CB6342B0JL
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=01 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   1 Ivl=256ms
I:* If#= 0 Alt= 1 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=02 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   1 Ivl=256ms

T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=5000 MxCh= 1
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 3.00 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
P:  Vendor=1d6b ProdID=0003 Rev= 4.09
S:  Manufacturer=Linux 4.9.76 xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=1e1c0000.xhci
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

T:  Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=5000 MxCh= 3
D:  Ver= 3.00 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
P:  Vendor=0bc2 ProdID=ab45 Rev=48.85
S:  Manufacturer=Seagate
S:  Product=Backup+ Hub
S:  SerialNumber=01CB6342B0JL
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=83(I) Atr=13(Int.) MxPS=   2 Ivl=16ms

T:  Bus=02 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#=  3 Spd=5000 MxCh= 0
D:  Ver= 3.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 9 #Cfgs=  1
P:  Vendor=0bc2 ProdID=ab38 Rev= 1.00
S:  Manufacturer=Seagate
S:  Product=Backup+ Hub BK
S:  SerialNumber=NA8T1B9F
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=uas
E:  Ad=81(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
I:* If#= 0 Alt= 1 #EPs= 4 Cls=08(stor.) Sub=06 Prot=62 Driver=uas
E:  Ad=81(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=83(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=04(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms

pojawił się
dev/sda
a na dysku są 2 partycje, więc powinno wg mnie być
sda1 i sda2

próba montowania nieudana:
mount /dev/sda /mnt/Seagate/
Error opening '/dev/sda': No medium found
Failed to mount '/dev/sda': No medium found
mount: mounting /dev/sda on /mnt/Seagate/ failed: No medium found

6 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,915

Odp: Xiaomi WiFi Router 3G i Seagate Backup Plus Hub - Mediatek SOC USB3.0

Teraz to go zrestartuj po prostu i zobacz co będzie.

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

Cezary's Strona

7 Odpowiedź przez r44

  • r44
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2018-01-26
  • Posty: 45

Odp: Xiaomi WiFi Router 3G i Seagate Backup Plus Hub - Mediatek SOC USB3.0

Po resecie /dev/sda zniknęło sad


T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480  MxCh= 2
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev= 4.09
S:  Manufacturer=Linux 4.9.76 xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=1e1c0000.xhci
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480  MxCh= 3
D:  Ver= 2.10 Cls=09(hub  ) Sub=00 Prot=02 MxPS=64 #Cfgs=  1
P:  Vendor=0bc2 ProdID=ab44 Rev=48.85
S:  Manufacturer=Seagate
S:  Product=Backup+ Hub
S:  SerialNumber=01CB6342B0JL
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=01 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   1 Ivl=256ms
I:* If#= 0 Alt= 1 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=02 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   1 Ivl=256ms

T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=5000 MxCh= 1
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 3.00 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
P:  Vendor=1d6b ProdID=0003 Rev= 4.09
S:  Manufacturer=Linux 4.9.76 xhci-hcd
S:  Product=xHCI Host Controller
S:  SerialNumber=1e1c0000.xhci
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=256ms

T:  Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=5000 MxCh= 3
D:  Ver= 3.00 Cls=09(hub  ) Sub=00 Prot=03 MxPS= 9 #Cfgs=  1
P:  Vendor=0bc2 ProdID=ab45 Rev=48.85
S:  Manufacturer=Seagate
S:  Product=Backup+ Hub
S:  SerialNumber=01CB6342B0JL
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=83(I) Atr=13(Int.) MxPS=   2 Ivl=16ms

T:  Bus=02 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#=  3 Spd=5000 MxCh= 0
D:  Ver= 3.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 9 #Cfgs=  1
P:  Vendor=0bc2 ProdID=ab38 Rev= 1.00
S:  Manufacturer=Seagate
S:  Product=Backup+ Hub BK
S:  SerialNumber=NA8T1B9F
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=uas
E:  Ad=81(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
I:* If#= 0 Alt= 1 #EPs= 4 Cls=08(stor.) Sub=06 Prot=62 Driver=uas
E:  Ad=81(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=83(I) Atr=02(Bulk) MxPS=1024 Ivl=0ms
E:  Ad=04(O) Atr=02(Bulk) MxPS=1024 Ivl=0ms

8 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,915

Odp: Xiaomi WiFi Router 3G i Seagate Backup Plus Hub - Mediatek SOC USB3.0

Tu jest ok, sterownik masz. Patrz w logi od początku.

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

Cezary's Strona

9 Odpowiedź przez r44

  • r44
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2018-01-26
  • Posty: 45

Odp: Xiaomi WiFi Router 3G i Seagate Backup Plus Hub - Mediatek SOC USB3.0

Zrobiłem tak, podłączyłem opisywany dysk, log jak poniżej (nie zgłasza się).
Miałem jeszcze dostęp do drugiego dysku Seagate i też się nie zgłosił.

Tue Jan 30 20:24:53 2018 kern.notice kernel: [    0.000000] Linux version 4.9.76 (cezary@eko.one.pl) (gcc version 5.5.0 (OpenWrt GCC 5.5.0 r5485-d23e1e1) ) #0 SMP Thu Jan 18 10:39:42 2018
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.000000] SoC Type: MediaTek MT7621 ver:1 eco:3
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.000000] bootconsole [early0] enabled
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.000000] CPU0 revision is: 0001992f (MIPS 1004Kc)
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.000000] MIPS: machine is Xiaomi Mi Router 3G
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.000000] Determined physical RAM map:
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.000000]  memory: 10000000 @ 00000000 (usable)
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.000000] Initrd not found or empty - disabling initrd
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.000000] VPE topology {2,2} total 4
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    0.000000] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    0.000000] Primary data cache 32kB, 4-way, PIPT, no aliases, linesize 32 bytes
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    0.000000] MIPS secondary cache 256kB, 8-way, linesize 32 bytes.
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.000000] Zone ranges:
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.000000]   Normal   [mem 0x0000000000000000-0x000000000fffffff]
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.000000]   HighMem  empty
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.000000] Movable zone start for each node
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.000000] Early memory node ranges
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.000000]   node   0: [mem 0x0000000000000000-0x000000000fffffff]
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x000000000fffffff]
Tue Jan 30 20:24:53 2018 kern.debug kernel: [    0.000000] On node 0 totalpages: 65536
Tue Jan 30 20:24:53 2018 kern.debug kernel: [    0.000000] free_area_init_node: node 0, pgdat 80519c20, node_mem_map 81003000
Tue Jan 30 20:24:53 2018 kern.debug kernel: [    0.000000]   Normal zone: 512 pages used for memmap
Tue Jan 30 20:24:53 2018 kern.debug kernel: [    0.000000]   Normal zone: 0 pages reserved
Tue Jan 30 20:24:53 2018 kern.debug kernel: [    0.000000]   Normal zone: 65536 pages, LIFO batch:15
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.000000] percpu: Embedded 12 pages/cpu @8120f000 s17744 r8192 d23216 u49152
Tue Jan 30 20:24:53 2018 kern.debug kernel: [    0.000000] pcpu-alloc: s17744 r8192 d23216 u49152 alloc=12*4096
Tue Jan 30 20:24:53 2018 kern.debug kernel: [    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 65024
Tue Jan 30 20:24:53 2018 kern.notice kernel: [    0.000000] Kernel command line: console=ttyS0,115200n8 rootfstype=squashfs,jffs2
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.000000] Writing ErrCtl register=0001b803
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.000000] Readback ErrCtl register=0001b803
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.000000] Memory: 253888K/262144K available (4082K kernel code, 221K rwdata, 920K rodata, 204K init, 272K bss, 8256K reserved, 0K cma-reserved, 0K highmem)
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.000000] Hierarchical RCU implementation.
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.000000] NR_IRQS:256
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.000000] clocksource: GIC: mask: 0xffffffffffffffff max_cycles: 0xcaf478abb4, max_idle_ns: 440795247997 ns
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.000000] clocksource: MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 4343773742 ns
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.000009] sched_clock: 32 bits at 440MHz, resolution 2ns, wraps every 4880645118ns
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.007797] Calibrating delay loop... 586.13 BogoMIPS (lpj=2930688)
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.070423] pid_max: default: 32768 minimum: 301
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.075156] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.081681] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    0.104863] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    0.104876] Primary data cache 32kB, 4-way, PIPT, no aliases, linesize 32 bytes
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    0.104888] MIPS secondary cache 256kB, 8-way, linesize 32 bytes.
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.105046] CPU1 revision is: 0001992f (MIPS 1004Kc)
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.177455] Synchronize counters for CPU 1:
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    0.177457] done.
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    0.200408] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    0.200417] Primary data cache 32kB, 4-way, PIPT, no aliases, linesize 32 bytes
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    0.200426] MIPS secondary cache 256kB, 8-way, linesize 32 bytes.
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.200510] CPU2 revision is: 0001992f (MIPS 1004Kc)
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.269496] Synchronize counters for CPU 2:
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    0.269497] done.
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    0.288899] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    0.288907] Primary data cache 32kB, 4-way, PIPT, no aliases, linesize 32 bytes
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    0.288915] MIPS secondary cache 256kB, 8-way, linesize 32 bytes.
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.289011] CPU3 revision is: 0001992f (MIPS 1004Kc)
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.354680] Synchronize counters for CPU 3:
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    0.354681] done.
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.360924] Brought up 4 CPUs
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.367856] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.377652] futex hash table entries: 1024 (order: 3, 32768 bytes)
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.383897] pinctrl core: initialized pinctrl subsystem
Tue Jan 30 20:24:53 2018 kern.info kernel: [    0.389792] NET: Registered protocol family 16
Tue Jan 30 20:24:53 2018 kern.debug kernel: [    0.402930] FPU Affinity set after 11720 emulations
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    0.449663] pull PCIe RST: RALINK_RSTCTRL = 4000000
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    0.754836] release PCIe RST: RALINK_RSTCTRL = 7000000
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    0.759885] ***** Xtal 40MHz *****
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    0.763240] release PCIe RST: RALINK_RSTCTRL = 7000000
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    0.768336] Port 0 N_FTS = 1b102800
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    0.771809] Port 1 N_FTS = 1b102800
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    0.775247] Port 2 N_FTS = 1b102800
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    1.930006] PCIE2 no card, disable it(RST&CLK)
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    1.934364]  -> 21007f2
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    1.936764] PCIE0 enabled
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    1.939357] PCIE1 enabled
Tue Jan 30 20:24:53 2018 kern.info kernel: [    1.941953] PCI host bridge /pcie@1e140000 ranges:
Tue Jan 30 20:24:53 2018 kern.info kernel: [    1.946737]  MEM 0x0000000060000000..0x000000006fffffff
Tue Jan 30 20:24:53 2018 kern.info kernel: [    1.951891]   IO 0x000000001e160000..0x000000001e16ffff
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    1.957092] PCI coherence region base: 0x60000000, mask/settings: 0xf0000002
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.008626] mt7621_gpio 1e000600.gpio: registering 32 gpios
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.014511] mt7621_gpio 1e000600.gpio: registering 32 gpios
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.020244] mt7621_gpio 1e000600.gpio: registering 32 gpios
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.027277] PCI host bridge to bus 0000:00
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.031313] pci_bus 0000:00: root bus resource [mem 0x60000000-0x6fffffff]
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.038155] pci_bus 0000:00: root bus resource [io  0xffffffff]
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.043997] pci_bus 0000:00: root bus resource [??? 0x00000000 flags 0x0]
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.050753] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
Tue Jan 30 20:24:53 2018 kern.debug kernel: [    2.058656] pci 0000:00:00.0: [0e8d:0801] type 01 class 0x060400
Tue Jan 30 20:24:53 2018 kern.debug kernel: [    2.058685] pci 0000:00:00.0: reg 0x10: [mem 0x00000000-0x7fffffff]
Tue Jan 30 20:24:53 2018 kern.debug kernel: [    2.058697] pci 0000:00:00.0: reg 0x14: [mem 0x00000000-0x0000ffff]
Tue Jan 30 20:24:53 2018 kern.debug kernel: [    2.058762] pci 0000:00:00.0: supports D1
Tue Jan 30 20:24:53 2018 kern.debug kernel: [    2.058771] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
Tue Jan 30 20:24:53 2018 kern.debug kernel: [    2.059011] pci 0000:00:01.0: [0e8d:0801] type 01 class 0x060400
Tue Jan 30 20:24:53 2018 kern.debug kernel: [    2.059031] pci 0000:00:01.0: reg 0x10: [mem 0x00000000-0x7fffffff]
Tue Jan 30 20:24:53 2018 kern.debug kernel: [    2.059044] pci 0000:00:01.0: reg 0x14: [mem 0x00000000-0x0000ffff]
Tue Jan 30 20:24:53 2018 kern.debug kernel: [    2.059091] pci 0000:00:01.0: supports D1
Tue Jan 30 20:24:53 2018 kern.debug kernel: [    2.059100] pci 0000:00:01.0: PME# supported from D0 D1 D3hot
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.059327] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.067250] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
Tue Jan 30 20:24:53 2018 kern.debug kernel: [    2.075352] pci 0000:01:00.0: [14c3:7603] type 00 class 0x028000
Tue Jan 30 20:24:53 2018 kern.debug kernel: [    2.075386] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x000fffff]
Tue Jan 30 20:24:53 2018 kern.debug kernel: [    2.075513] pci 0000:01:00.0: PME# supported from D0 D3hot D3cold
Tue Jan 30 20:24:53 2018 kern.debug kernel: [    2.075714] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
Tue Jan 30 20:24:53 2018 kern.debug kernel: [    2.075889] pci 0000:02:00.0: [14c3:7662] type 00 class 0x028000
Tue Jan 30 20:24:53 2018 kern.debug kernel: [    2.075927] pci 0000:02:00.0: reg 0x10: [mem 0x00000000-0x000fffff 64bit]
Tue Jan 30 20:24:53 2018 kern.debug kernel: [    2.075971] pci 0000:02:00.0: reg 0x30: [mem 0x00000000-0x0000ffff pref]
Tue Jan 30 20:24:53 2018 kern.debug kernel: [    2.076059] pci 0000:02:00.0: PME# supported from D0 D3hot D3cold
Tue Jan 30 20:24:53 2018 kern.debug kernel: [    2.076263] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
Tue Jan 30 20:24:53 2018 kern.debug kernel: [    2.076281] pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 02
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.076348] pci 0000:00:00.0: BAR 0: no space for [mem size 0x80000000]
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.082889] pci 0000:00:00.0: BAR 0: failed to assign [mem size 0x80000000]
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.089776] pci 0000:00:01.0: BAR 0: no space for [mem size 0x80000000]
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.096349] pci 0000:00:01.0: BAR 0: failed to assign [mem size 0x80000000]
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.103257] pci 0000:00:00.0: BAR 8: assigned [mem 0x60000000-0x600fffff]
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.110006] pci 0000:00:01.0: BAR 8: assigned [mem 0x60100000-0x601fffff]
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.116728] pci 0000:00:01.0: BAR 9: assigned [mem 0x60200000-0x602fffff pref]
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.123921] pci 0000:00:00.0: BAR 1: assigned [mem 0x60300000-0x6030ffff]
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.130646] pci 0000:00:01.0: BAR 1: assigned [mem 0x60310000-0x6031ffff]
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.137401] pci 0000:01:00.0: BAR 0: assigned [mem 0x60000000-0x600fffff]
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.144124] pci 0000:00:00.0: PCI bridge to [bus 01]
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.149059] pci 0000:00:00.0:   bridge window [mem 0x60000000-0x600fffff]
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.155789] pci 0000:02:00.0: BAR 0: assigned [mem 0x60100000-0x601fffff 64bit]
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.163070] pci 0000:02:00.0: BAR 6: assigned [mem 0x60200000-0x6020ffff pref]
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.170211] pci 0000:00:01.0: PCI bridge to [bus 02]
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.175149] pci 0000:00:01.0:   bridge window [mem 0x60100000-0x601fffff]
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.181878] pci 0000:00:01.0:   bridge window [mem 0x60200000-0x602fffff pref]
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    2.189073] BAR0 at slot 0 = 0
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    2.192061] bus=0x0, slot = 0x0
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    2.195177] BAR0 at slot 1 = 0
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    2.198199] bus=0x0, slot = 0x1
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    2.201333] bus=0x1, slot = 0x0, irq=0xff
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    2.205291] bus=0x2, slot = 0x1, irq=0xff
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.210641] clocksource: Switched to clocksource GIC
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.217081] NET: Registered protocol family 2
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.222223] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.229114] TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.235545] TCP: Hash tables configured (established 2048 bind 2048)
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.241896] UDP hash table entries: 256 (order: 1, 8192 bytes)
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.247656] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.254125] NET: Registered protocol family 1
Tue Jan 30 20:24:53 2018 kern.debug kernel: [    2.258446] PCI: CLS 80 bytes, default 32
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.490562] 4 CPUs re-calibrate udelay(lpj = 2924544)
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    2.496751] Crashlog allocated RAM at address 0x3f00000
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.502316] workingset: timestamp_bits=30 max_order=16 bucket_order=0
Tue Jan 30 20:24:53 2018 kern.notice kernel: [    2.512298] random: fast init done
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.515293] squashfs: version 4.0 (2009/01/31) Phillip Lougher
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.515300] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.534428] io scheduler noop registered
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.538267] io scheduler deadline registered (default)
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.543891] gpio-export gpio_export: 1 gpio(s) exported
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.549566] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.558829] console [ttyS0] disabled
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.562418] 1e000c00.uartlite: ttyS0 at MMIO 0x1e000c00 (irq = 18, base_baud = 3125000) is a 16550A
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.571397] console [ttyS0] enabled
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.578253] bootconsole [early0] disabled
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    2.587432] MediaTek Nand driver init, version v2.1 Fix AHB virt2phys error
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.594532] Allocate 16 byte aligned buffer: 80588360
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    2.599559] Enable NFI Clock
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    2.602444] # MTK NAND # : Use HW ECC
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.606105] Device not found, ID: c8d1
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    2.609828] Not Support this Device!
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    2.613572] chip_mode=00000001
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    2.616618] Support this Device in MTK table! c8d1
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    2.621584] [NAND]select ecc bit:4, sparesize :64 spare_per_sector=16
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.628042] nand: device found, Manufacturer ID: 0xc8, Chip ID: 0xd1
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.634381] nand: ESMT NAND 128MiB 3,3V 8-bit
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.638717] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.646280] Scanning device for bad blocks
Tue Jan 30 20:24:53 2018 kern.notice kernel: [    2.795712] 10 ofpart partitions found on MTD device MT7621-NAND
Tue Jan 30 20:24:53 2018 kern.notice kernel: [    2.801708] Creating 10 MTD partitions on "MT7621-NAND":
Tue Jan 30 20:24:53 2018 kern.notice kernel: [    2.807001] 0x000000000000-0x000000080000 : "Bootloader"
Tue Jan 30 20:24:53 2018 kern.notice kernel: [    2.813622] 0x000000080000-0x0000000c0000 : "Config"
Tue Jan 30 20:24:53 2018 kern.notice kernel: [    2.819667] 0x0000000c0000-0x000000100000 : "Bdata"
Tue Jan 30 20:24:53 2018 kern.notice kernel: [    2.825720] 0x000000100000-0x000000140000 : "Factory"
Tue Jan 30 20:24:53 2018 kern.notice kernel: [    2.831949] 0x000000140000-0x000000180000 : "crash"
Tue Jan 30 20:24:53 2018 kern.notice kernel: [    2.837885] 0x000000180000-0x0000001c0000 : "crash_syslog"
Tue Jan 30 20:24:53 2018 kern.notice kernel: [    2.844783] 0x0000001c0000-0x000000200000 : "reserved0"
Tue Jan 30 20:24:53 2018 kern.notice kernel: [    2.851918] 0x000000200000-0x000000600000 : "kernel_stock"
Tue Jan 30 20:24:53 2018 kern.notice kernel: [    2.858731] 0x000000600000-0x000000a00000 : "kernel"
Tue Jan 30 20:24:53 2018 kern.notice kernel: [    2.865248] 0x000000a00000-0x000007f80000 : "ubi"
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    2.872374] [mtk_nand] probe successfully!
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    2.877191] Signature matched and data read!
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    2.881490] load_fact_bbt success 1023
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.885908] libphy: Fixed MDIO Bus: probed
Tue Jan 30 20:24:53 2018 kern.info kernel: [    2.953218] libphy: mdio: probed
Tue Jan 30 20:24:53 2018 kern.info kernel: [    4.355990] mtk_soc_eth 1e100000.ethernet: loaded mt7530 driver
Tue Jan 30 20:24:53 2018 kern.info kernel: [    4.362795] mtk_soc_eth 1e100000.ethernet eth0: mediatek frame engine at 0xbe100000, irq 20
Tue Jan 30 20:24:53 2018 kern.info kernel: [    4.373390] NET: Registered protocol family 10
Tue Jan 30 20:24:53 2018 kern.info kernel: [    4.379401] NET: Registered protocol family 17
Tue Jan 30 20:24:53 2018 kern.info kernel: [    4.383963] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
Tue Jan 30 20:24:53 2018 kern.info kernel: [    4.396875] 8021q: 802.1Q VLAN Support v1.8
Tue Jan 30 20:24:53 2018 kern.notice kernel: [    4.404065] UBI: auto-attach mtd9
Tue Jan 30 20:24:53 2018 kern.notice kernel: [    4.407395] ubi0: attaching mtd9
Tue Jan 30 20:24:53 2018 kern.notice kernel: [    5.519538] ubi0: scanning is finished
Tue Jan 30 20:24:53 2018 kern.notice kernel: [    5.539812] ubi0: attached mtd9 (name "ubi", size 117 MiB)
Tue Jan 30 20:24:53 2018 kern.notice kernel: [    5.545318] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
Tue Jan 30 20:24:53 2018 kern.notice kernel: [    5.552172] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
Tue Jan 30 20:24:53 2018 kern.notice kernel: [    5.558925] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
Tue Jan 30 20:24:53 2018 kern.notice kernel: [    5.565864] ubi0: good PEBs: 940, bad PEBs: 0, corrupted PEBs: 0
Tue Jan 30 20:24:53 2018 kern.notice kernel: [    5.571858] ubi0: user volume: 2, internal volumes: 1, max. volumes count: 128
Tue Jan 30 20:24:53 2018 kern.notice kernel: [    5.579047] ubi0: max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 345029443
Tue Jan 30 20:24:53 2018 kern.notice kernel: [    5.588060] ubi0: available PEBs: 0, total reserved PEBs: 940, PEBs reserved for bad PEB handling: 20
Tue Jan 30 20:24:53 2018 kern.notice kernel: [    5.597267] ubi0: background thread "ubi_bgt0d" started, PID 376
Tue Jan 30 20:24:53 2018 kern.info kernel: [    5.599287] block ubiblock0_0: created from ubi0:0(rootfs)
Tue Jan 30 20:24:53 2018 kern.notice kernel: [    5.599295] ubiblock: device ubiblock0_0 (rootfs) set to be root filesystem
Tue Jan 30 20:24:53 2018 kern.info kernel: [    5.599311] hctosys: unable to open rtc device (rtc0)
Tue Jan 30 20:24:53 2018 kern.info kernel: [    5.626616] VFS: Mounted root (squashfs filesystem) readonly on device 254:0.
Tue Jan 30 20:24:53 2018 kern.info kernel: [    5.634214] Freeing unused kernel memory: 204K
Tue Jan 30 20:24:53 2018 kern.warn kernel: [    5.638646] This architecture does not have kernel memory protection.
Tue Jan 30 20:24:53 2018 user.info kernel: [    6.154173] init: Console is alive
Tue Jan 30 20:24:53 2018 user.info kernel: [    6.157805] init: - watchdog -
Tue Jan 30 20:24:53 2018 user.info kernel: [    7.234584] kmodloader: loading kernel modules from /etc/modules-boot.d/*
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.350948] usbcore: registered new interface driver usbfs
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.356522] usbcore: registered new interface driver hub
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.362056] usbcore: registered new device driver usb
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.390703] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Tue Jan 30 20:24:53 2018 kern.notice kernel: [    7.403955] SCSI subsystem initialized
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.411219] ehci-platform: EHCI generic platform driver
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.424368] xhci-mtk 1e1c0000.xhci: xHCI Host Controller
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.429702] xhci-mtk 1e1c0000.xhci: new USB bus registered, assigned bus number 1
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.440859] xhci-mtk 1e1c0000.xhci: hcc params 0x01401198 hci version 0x96 quirks 0x00210010
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.449342] xhci-mtk 1e1c0000.xhci: irq 19, io mem 0x1e1c0000
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.456225] hub 1-0:1.0: USB hub found
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.460046] hub 1-0:1.0: 2 ports detected
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.464523] xhci-mtk 1e1c0000.xhci: xHCI Host Controller
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.469827] xhci-mtk 1e1c0000.xhci: new USB bus registered, assigned bus number 2
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.477521] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.486530] hub 2-0:1.0: USB hub found
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.490343] hub 2-0:1.0: 1 port detected
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.500228] usbcore: registered new interface driver usb-storage
Tue Jan 30 20:24:53 2018 user.info kernel: [    7.506556] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
Tue Jan 30 20:24:53 2018 user.info kernel: [    7.520908] init: - preinit -
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.850849] usb 2-1: new SuperSpeed USB device number 2 using xhci-mtk
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.887294] hub 2-1:1.0: USB hub found
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.891398] hub 2-1:1.0: 3 ports detected
Tue Jan 30 20:24:53 2018 kern.info kernel: [    8.020705] usb 1-1: new high-speed USB device number 2 using xhci-mtk
Tue Jan 30 20:24:53 2018 kern.info kernel: [    8.205182] hub 1-1:1.0: USB hub found
Tue Jan 30 20:24:53 2018 kern.info kernel: [    8.209327] hub 1-1:1.0: 3 ports detected
Tue Jan 30 20:24:53 2018 kern.info kernel: [    8.330728] usb 2-1.1: new SuperSpeed USB device number 3 using xhci-mtk
Tue Jan 30 20:24:53 2018 user.info kernel: [   11.437056] mount_root: loading kmods from internal overlay
Tue Jan 30 20:24:53 2018 user.info kernel: [   11.468703] kmodloader: loading kernel modules from //etc/modules-boot.d/*
Tue Jan 30 20:24:53 2018 user.info kernel: [   11.476985] kmodloader: done loading kernel modules from //etc/modules-boot.d/*
Tue Jan 30 20:24:53 2018 kern.notice kernel: [   12.036730] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" started, PID 500
Tue Jan 30 20:24:53 2018 kern.notice kernel: [   12.111131] UBIFS (ubi0:1): recovery needed
Tue Jan 30 20:24:53 2018 kern.notice kernel: [   12.314486] UBIFS (ubi0:1): recovery completed
Tue Jan 30 20:24:53 2018 kern.notice kernel: [   12.319031] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name "rootfs_data"
Tue Jan 30 20:24:53 2018 kern.notice kernel: [   12.326842] UBIFS (ubi0:1): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Tue Jan 30 20:24:53 2018 kern.notice kernel: [   12.336732] UBIFS (ubi0:1): FS size: 109834240 bytes (104 MiB, 865 LEBs), journal size 5459968 bytes (5 MiB, 43 LEBs)
Tue Jan 30 20:24:53 2018 kern.notice kernel: [   12.347302] UBIFS (ubi0:1): reserved for root: 4952683 bytes (4836 KiB)
Tue Jan 30 20:24:53 2018 kern.notice kernel: [   12.353913] UBIFS (ubi0:1): media format: w4/r0 (latest is w4/r0), UUID F3F672C1-42AC-4718-890A-176994DC27BE, small LPT model
Tue Jan 30 20:24:53 2018 user.info kernel: [   12.366669] block: attempting to load /tmp/ubifs_cfg/upper/etc/config/fstab
Tue Jan 30 20:24:53 2018 user.info kernel: [   12.382673] block: extroot: not configured
Tue Jan 30 20:24:53 2018 kern.notice kernel: [   12.430860] UBIFS (ubi0:1): un-mount UBI device 0
Tue Jan 30 20:24:53 2018 kern.notice kernel: [   12.435572] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" stops
Tue Jan 30 20:24:53 2018 kern.notice kernel: [   12.447701] UBIFS (ubi0:1): background thread "ubifs_bgt0_1" started, PID 503
Tue Jan 30 20:24:53 2018 kern.notice kernel: [   12.595073] UBIFS (ubi0:1): UBIFS: mounted UBI device 0, volume 1, name "rootfs_data"
Tue Jan 30 20:24:53 2018 kern.notice kernel: [   12.602936] UBIFS (ubi0:1): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
Tue Jan 30 20:24:53 2018 kern.notice kernel: [   12.612884] UBIFS (ubi0:1): FS size: 109834240 bytes (104 MiB, 865 LEBs), journal size 5459968 bytes (5 MiB, 43 LEBs)
Tue Jan 30 20:24:53 2018 kern.notice kernel: [   12.623463] UBIFS (ubi0:1): reserved for root: 4952683 bytes (4836 KiB)
Tue Jan 30 20:24:53 2018 kern.notice kernel: [   12.630051] UBIFS (ubi0:1): media format: w4/r0 (latest is w4/r0), UUID F3F672C1-42AC-4718-890A-176994DC27BE, small LPT model
Tue Jan 30 20:24:53 2018 user.info kernel: [   12.647221] mount_root: loading kmods from internal overlay
Tue Jan 30 20:24:53 2018 user.info kernel: [   12.746981] kmodloader: loading kernel modules from /tmp/overlay/upper/etc/modules-boot.d/*
Tue Jan 30 20:24:53 2018 kern.info kernel: [   12.782955] scsi host0: uas
Tue Jan 30 20:24:53 2018 kern.err kernel: [   12.786827] xhci-mtk 1e1c0000.xhci: ERROR Transfer event for disabled endpoint or incorrect stream ring
Tue Jan 30 20:24:53 2018 kern.err kernel: [   12.796195] xhci-mtk 1e1c0000.xhci: @000000000f426680 0f322000 00000000 05000000 03078001
Tue Jan 30 20:24:53 2018 kern.err kernel: [   12.804335] xhci-mtk 1e1c0000.xhci: ERROR Transfer event for disabled endpoint or incorrect stream ring
Tue Jan 30 20:24:53 2018 kern.err kernel: [   12.813685] xhci-mtk 1e1c0000.xhci: @000000000f426690 0f322100 00000000 05000000 03038001
Tue Jan 30 20:24:53 2018 kern.info kernel: [   34.460635] scsi 0:0:0:0: tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN
Tue Jan 30 20:24:53 2018 kern.info kernel: [   34.468187] scsi 0:0:0:0: tag#0 CDB: opcode=0x12 12 00 00 00 24 00
Tue Jan 30 20:24:53 2018 kern.err kernel: [   35.510615] scsi host0: uas_eh_bus_reset_handler FAILED to get lock err -16
Tue Jan 30 20:24:53 2018 kern.info kernel: [   35.517551] scsi 0:0:0:0: Device offlined - not ready after error recovery
Tue Jan 30 20:24:53 2018 kern.info kernel: [   35.524881] usbcore: registered new interface driver uas
Tue Jan 30 20:24:53 2018 user.info kernel: [   35.530475] kmodloader: done loading kernel modules from /tmp/overlay/upper/etc/modules-boot.d/*
Tue Jan 30 20:24:53 2018 user.info kernel: [   35.894941] block: attempting to load /tmp/ubifs_cfg/upper/etc/config/fstab
Tue Jan 30 20:24:53 2018 user.info kernel: [   35.906257] block: extroot: not configured
Tue Jan 30 20:24:53 2018 user.info kernel: [   35.942936] mount_root: switching to ubifs overlay
Tue Jan 30 20:24:53 2018 user.warn kernel: [   35.972747] urandom-seed: Seeding with /etc/urandom.seed
Tue Jan 30 20:24:53 2018 user.info kernel: [   36.089089] procd: - early -
Tue Jan 30 20:24:53 2018 user.info kernel: [   36.092165] procd: - watchdog -
Tue Jan 30 20:24:53 2018 user.info kernel: [   36.810843] procd: - watchdog -
Tue Jan 30 20:24:53 2018 user.info kernel: [   36.814480] procd: - ubus -
Tue Jan 30 20:24:53 2018 user.info kernel: [   36.872922] procd: - init -
Tue Jan 30 20:24:53 2018 user.info kernel: [   37.383663] kmodloader: loading kernel modules from /etc/modules.d/*
Tue Jan 30 20:24:53 2018 kern.info kernel: [   37.520422] tun: Universal TUN/TAP device driver, 1.6
Tue Jan 30 20:24:53 2018 kern.info kernel: [   37.525632] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Tue Jan 30 20:24:53 2018 kern.info kernel: [   37.536047] ip6_tables: (C) 2000-2006 Netfilter Core Team
Tue Jan 30 20:24:53 2018 kern.info kernel: [   37.553572] fuse init (API version 7.26)
Tue Jan 30 20:24:53 2018 kern.info kernel: [   37.564154] usbcore: registered new interface driver cdc_acm
Tue Jan 30 20:24:53 2018 kern.info kernel: [   37.569826] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
Tue Jan 30 20:24:53 2018 kern.info kernel: [   37.579302] usbcore: registered new interface driver cdc_wdm
Tue Jan 30 20:24:53 2018 kern.info kernel: [   37.586098] Loading modules backported from Linux version wt-2017-11-01-0-gfe248fc2c180
Tue Jan 30 20:24:53 2018 kern.info kernel: [   37.594146] Backport generated by backports.git v4.14-rc2-1-31-g86cf0e5d
Tue Jan 30 20:24:53 2018 kern.info kernel: [   37.603314] ip_tables: (C) 2000-2006 Netfilter Core Team
Tue Jan 30 20:24:53 2018 kern.info kernel: [   37.616421] nf_conntrack version 0.5.0 (4096 buckets, 16384 max)
Tue Jan 30 20:24:53 2018 kern.info kernel: [   37.712861] usbcore: registered new interface driver ums-alauda
Tue Jan 30 20:24:53 2018 kern.info kernel: [   37.720256] usbcore: registered new interface driver ums-cypress
Tue Jan 30 20:24:53 2018 kern.info kernel: [   37.727809] usbcore: registered new interface driver ums-datafab
Tue Jan 30 20:24:53 2018 kern.info kernel: [   37.735244] usbcore: registered new interface driver ums-freecom
Tue Jan 30 20:24:53 2018 kern.info kernel: [   37.743319] usbcore: registered new interface driver ums-isd200
Tue Jan 30 20:24:53 2018 kern.info kernel: [   37.751273] usbcore: registered new interface driver ums-jumpshot
Tue Jan 30 20:24:53 2018 kern.info kernel: [   37.759270] usbcore: registered new interface driver ums-karma
Tue Jan 30 20:24:53 2018 kern.info kernel: [   37.768339] usbcore: registered new interface driver ums-sddr09
Tue Jan 30 20:24:53 2018 kern.info kernel: [   37.775740] usbcore: registered new interface driver ums-sddr55
Tue Jan 30 20:24:53 2018 kern.info kernel: [   37.783251] usbcore: registered new interface driver ums-usbat
Tue Jan 30 20:24:53 2018 kern.info kernel: [   37.791804] usbcore: registered new interface driver usblp
Tue Jan 30 20:24:53 2018 kern.info kernel: [   37.807907] usbcore: registered new interface driver usbserial
Tue Jan 30 20:24:53 2018 kern.info kernel: [   37.813969] usbcore: registered new interface driver usbserial_generic
Tue Jan 30 20:24:53 2018 kern.info kernel: [   37.820769] usbserial: USB Serial support registered for generic
Tue Jan 30 20:24:53 2018 kern.info kernel: [   37.840475] xt_time: kernel timezone is -0000
Tue Jan 30 20:24:53 2018 kern.info kernel: [   37.846802] usbcore: registered new interface driver cdc_ether
Tue Jan 30 20:24:53 2018 kern.info kernel: [   37.855451] usbcore: registered new interface driver cdc_ncm
Tue Jan 30 20:24:53 2018 kern.info kernel: [   37.882792] usbcore: registered new interface driver huawei_cdc_ncm
Tue Jan 30 20:24:53 2018 kern.info kernel: [   37.933741] mt7603e 0000:01:00.0: ASIC revision: 76030010
Tue Jan 30 20:24:53 2018 kern.info kernel: [   37.985088] mt7603e 0000:01:00.0: Firmware Version: ap_pcie
Tue Jan 30 20:24:53 2018 kern.info kernel: [   37.990709] mt7603e 0000:01:00.0: Build Time: 20160107100755
Tue Jan 30 20:24:53 2018 kern.warn kernel: [   38.030721] firmware init done
Tue Jan 30 20:24:53 2018 kern.debug kernel: [   38.205380] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Tue Jan 30 20:24:53 2018 kern.info kernel: [   38.212646] mt76x2e 0000:02:00.0: ASIC revision: 76120044
Tue Jan 30 20:24:53 2018 kern.info kernel: [   38.240726] mt76x2e 0000:02:00.0: ROM patch already applied
Tue Jan 30 20:24:53 2018 kern.info kernel: [   38.247467] mt76x2e 0000:02:00.0: Firmware Version: 0.0.00
Tue Jan 30 20:24:53 2018 kern.info kernel: [   38.253040] mt76x2e 0000:02:00.0: Build: 1
Tue Jan 30 20:24:53 2018 kern.info kernel: [   38.257135] mt76x2e 0000:02:00.0: Build Time: 201507311614____
Tue Jan 30 20:24:53 2018 kern.info kernel: [   38.290716] mt76x2e 0000:02:00.0: Firmware running!
Tue Jan 30 20:24:53 2018 kern.debug kernel: [   38.297152] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
Tue Jan 30 20:24:53 2018 kern.info kernel: [   38.308839] PPP generic driver version 2.4.2
Tue Jan 30 20:24:53 2018 kern.info kernel: [   38.314778] NET: Registered protocol family 24
Tue Jan 30 20:24:53 2018 kern.info kernel: [   38.321601] usbcore: registered new interface driver qmi_wwan
Tue Jan 30 20:24:53 2018 kern.info kernel: [   38.329483] usbcore: registered new interface driver rndis_host
Tue Jan 30 20:24:53 2018 kern.info kernel: [   38.337338] usbcore: registered new interface driver sierra
Tue Jan 30 20:24:53 2018 kern.info kernel: [   38.343234] usbserial: USB Serial support registered for Sierra USB modem
Tue Jan 30 20:24:53 2018 kern.info kernel: [   38.352772] usbcore: registered new interface driver sierra_net
Tue Jan 30 20:24:53 2018 kern.info kernel: [   38.364111] usbcore: registered new interface driver cdc_mbim
Tue Jan 30 20:24:53 2018 kern.info kernel: [   38.372051] usbcore: registered new interface driver option
Tue Jan 30 20:24:53 2018 kern.info kernel: [   38.377838] usbserial: USB Serial support registered for GSM modem (1-port)
Tue Jan 30 20:24:53 2018 kern.info kernel: [   38.389656] usbcore: registered new interface driver qcserial
Tue Jan 30 20:24:53 2018 kern.info kernel: [   38.395632] usbserial: USB Serial support registered for Qualcomm USB modem
Tue Jan 30 20:24:53 2018 user.info kernel: [   38.402925] kmodloader: done loading kernel modules from /etc/modules.d/*
Tue Jan 30 20:24:55 2018 user.notice : Added device handler type: tunnel
Tue Jan 30 20:24:55 2018 user.notice : Added device handler type: Network device
Tue Jan 30 20:24:55 2018 user.notice : Added device handler type: bridge
Tue Jan 30 20:24:55 2018 user.notice : Added device handler type: veth
Tue Jan 30 20:24:55 2018 user.notice : Added device handler type: macvlan
Tue Jan 30 20:24:55 2018 user.notice : Added device handler type: 8021ad
Tue Jan 30 20:24:55 2018 user.notice : Added device handler type: 8021q
Tue Jan 30 20:24:56 2018 daemon.err block: /dev/ubiblock0_0 is already mounted on /rom
Tue Jan 30 20:24:56 2018 daemon.err block: /dev/ubi0_1 is already mounted on /overlay
Tue Jan 30 20:24:56 2018 kern.notice kernel: [   43.063206] random: crng init done
Tue Jan 30 20:24:57 2018 authpriv.info dropbear[1402]: Not backgrounding
Tue Jan 30 20:24:58 2018 daemon.warn netifd: You have delegated IPv6-prefixes but haven't assigned them to any interface. Did you forget to set option ip6assign on your lan-interfaces?
Tue Jan 30 20:24:58 2018 kern.info kernel: [   44.304675] device eth0 entered promiscuous mode
Tue Jan 30 20:24:58 2018 kern.info kernel: [   44.311079] br-lan: port 1(eth0.1) entered blocking state
Tue Jan 30 20:24:58 2018 kern.info kernel: [   44.316477] br-lan: port 1(eth0.1) entered disabled state
Tue Jan 30 20:24:58 2018 kern.info kernel: [   44.323103] device eth0.1 entered promiscuous mode
Tue Jan 30 20:24:58 2018 kern.info kernel: [   44.334467] br-lan: port 1(eth0.1) entered blocking state
Tue Jan 30 20:24:58 2018 kern.info kernel: [   44.339933] br-lan: port 1(eth0.1) entered forwarding state
Tue Jan 30 20:24:58 2018 kern.info kernel: [   44.346101] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
Tue Jan 30 20:24:58 2018 daemon.notice netifd: Interface 'lan' is enabled
Tue Jan 30 20:24:58 2018 daemon.notice netifd: Interface 'lan' is setting up now
Tue Jan 30 20:24:58 2018 daemon.notice netifd: Interface 'lan' is now up
Tue Jan 30 20:24:58 2018 daemon.notice netifd: Interface 'loopback' is enabled
Tue Jan 30 20:24:58 2018 daemon.notice netifd: Interface 'loopback' is setting up now
Tue Jan 30 20:24:58 2018 daemon.notice netifd: Interface 'loopback' is now up
Tue Jan 30 20:24:58 2018 daemon.notice netifd: Interface 'wan' is setting up now
Tue Jan 30 20:24:58 2018 daemon.notice netifd: Interface 'wan6' is enabled
Tue Jan 30 20:24:58 2018 daemon.notice netifd: bridge 'br-lan' link is up
Tue Jan 30 20:24:58 2018 daemon.notice netifd: Interface 'lan' has link connectivity
Tue Jan 30 20:24:58 2018 daemon.notice netifd: Network device 'eth0' link is up
Tue Jan 30 20:24:58 2018 daemon.notice netifd: VLAN 'eth0.1' link is up
Tue Jan 30 20:24:58 2018 daemon.notice netifd: Network device 'lo' link is up
Tue Jan 30 20:24:58 2018 daemon.notice netifd: Interface 'loopback' has link connectivity
Tue Jan 30 20:24:58 2018 daemon.notice netifd: VLAN 'eth0.2' link is up
Tue Jan 30 20:24:58 2018 daemon.notice netifd: Interface 'wan6' has link connectivity
Tue Jan 30 20:24:58 2018 daemon.notice netifd: Interface 'wan6' is setting up now
Tue Jan 30 20:24:58 2018 daemon.notice netifd: Interface 'wan' is now down
Tue Jan 30 20:24:58 2018 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Tue Jan 30 20:24:59 2018 kern.info kernel: [   45.338378] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
Tue Jan 30 20:24:59 2018 daemon.err odhcp6c[1533]: Failed to send DHCPV6 message to ff02::1:2 (Address not available)
Tue Jan 30 20:24:59 2018 daemon.notice procd: /etc/rc.d/S95done:
Tue Jan 30 20:24:59 2018 daemon.notice procd: /etc/rc.d/S95done:
Tue Jan 30 20:24:59 2018 daemon.notice procd: /etc/rc.d/S95done: Selected modem port: /dev/ttyUSB1
Tue Jan 30 20:24:59 2018 daemon.notice procd: /etc/rc.d/S95done: Setting LTE only - all bands...
Tue Jan 30 20:24:59 2018 daemon.notice procd: /etc/rc.d/S95done: Can't open device /dev/ttyUSB1.
Tue Jan 30 20:24:59 2018 daemon.notice procd: /etc/rc.d/S96led: setting up led WAN (amber)
Tue Jan 30 20:24:59 2018 daemon.notice procd: /etc/rc.d/S96led: setting up led LAN1 (amber)
Tue Jan 30 20:24:59 2018 daemon.notice procd: /etc/rc.d/S96led: setting up led LAN2 (amber)
Tue Jan 30 20:25:00 2018 daemon.info procd: - init complete -
Tue Jan 30 20:25:00 2018 daemon.err hostapd: Configuration file: /var/run/hostapd-phy1.conf
Tue Jan 30 20:25:00 2018 daemon.err hostapd: Configuration file: /var/run/hostapd-phy0.conf
Tue Jan 30 20:25:01 2018 kern.info kernel: [   47.553132] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
Tue Jan 30 20:25:01 2018 kern.info kernel: [   47.563021] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Tue Jan 30 20:25:01 2018 kern.info kernel: [   47.569896] br-lan: port 2(wlan1) entered blocking state
Tue Jan 30 20:25:01 2018 kern.info kernel: [   47.575316] br-lan: port 2(wlan1) entered disabled state
Tue Jan 30 20:25:01 2018 kern.info kernel: [   47.581563] device wlan1 entered promiscuous mode
Tue Jan 30 20:25:01 2018 kern.info kernel: [   47.586722] br-lan: port 3(wlan0) entered blocking state
Tue Jan 30 20:25:01 2018 daemon.notice hostapd: wlan1: interface state UNINITIALIZED->COUNTRY_UPDATE
Tue Jan 30 20:25:01 2018 kern.info kernel: [   47.592102] br-lan: port 3(wlan0) entered disabled state
Tue Jan 30 20:25:01 2018 kern.info kernel: [   47.598457] device wlan0 entered promiscuous mode
Tue Jan 30 20:25:01 2018 daemon.notice hostapd: wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
Tue Jan 30 20:25:01 2018 daemon.notice hostapd: wlan1: interface state COUNTRY_UPDATE->HT_SCAN
Tue Jan 30 20:25:01 2018 daemon.err hostapd: Using interface wlan0 with hwaddr 50:64:2b:14:e0:11 and ssid "mi3g2"
Tue Jan 30 20:25:01 2018 daemon.err hostapd: Using interface wlan1 with hwaddr 50:64:2b:14:e0:12 and ssid "mi3g5"
Tue Jan 30 20:25:01 2018 kern.info kernel: [   47.947930] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Tue Jan 30 20:25:01 2018 kern.info kernel: [   47.954624] br-lan: port 3(wlan0) entered blocking state
Tue Jan 30 20:25:01 2018 kern.info kernel: [   47.959915] br-lan: port 3(wlan0) entered forwarding state
Tue Jan 30 20:25:01 2018 daemon.notice hostapd: wlan0: interface state COUNTRY_UPDATE->ENABLED
Tue Jan 30 20:25:01 2018 daemon.notice hostapd: wlan0: AP-ENABLED
Tue Jan 30 20:25:01 2018 daemon.notice netifd: Network device 'wlan0' link is up
Tue Jan 30 20:25:02 2018 kern.info kernel: [   48.603014] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
Tue Jan 30 20:25:02 2018 kern.info kernel: [   48.609625] br-lan: port 2(wlan1) entered blocking state
Tue Jan 30 20:25:02 2018 kern.info kernel: [   48.614963] br-lan: port 2(wlan1) entered forwarding state
Tue Jan 30 20:25:02 2018 daemon.notice hostapd: wlan1: interface state HT_SCAN->ENABLED
Tue Jan 30 20:25:02 2018 daemon.notice hostapd: wlan1: AP-ENABLED
Tue Jan 30 20:25:02 2018 daemon.notice netifd: Network device 'wlan1' link is up
Tue Jan 30 20:25:04 2018 daemon.info dnsmasq[2063]: started, version 2.78 cachesize 150
Tue Jan 30 20:25:04 2018 daemon.info dnsmasq[2063]: DNS service limited to local subnets
Tue Jan 30 20:25:05 2018 daemon.info dnsmasq[2063]: 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
Tue Jan 30 20:25:05 2018 daemon.info dnsmasq-dhcp[2063]: DHCP, IP range 192.168.1.100 -- 192.168.1.249, lease time 12h
Tue Jan 30 20:25:05 2018 daemon.info dnsmasq[2063]: using local addresses only for domain test
Tue Jan 30 20:25:05 2018 daemon.info dnsmasq[2063]: using local addresses only for domain onion
Tue Jan 30 20:25:05 2018 daemon.info dnsmasq[2063]: using local addresses only for domain localhost
Tue Jan 30 20:25:05 2018 daemon.info dnsmasq[2063]: using local addresses only for domain local
Tue Jan 30 20:25:05 2018 daemon.info dnsmasq[2063]: using local addresses only for domain invalid
Tue Jan 30 20:25:05 2018 daemon.info dnsmasq[2063]: using local addresses only for domain example.net
Tue Jan 30 20:25:05 2018 daemon.info dnsmasq[2063]: using local addresses only for domain example.org
Tue Jan 30 20:25:05 2018 daemon.info dnsmasq[2063]: using local addresses only for domain example.com
Tue Jan 30 20:25:05 2018 daemon.info dnsmasq[2063]: using 3 more local addresses
Tue Jan 30 20:25:05 2018 daemon.warn dnsmasq[2063]: no servers found in /tmp/resolv.conf.auto, will retry
Tue Jan 30 20:25:05 2018 daemon.info dnsmasq[2063]: read /etc/hosts - 4 addresses
Tue Jan 30 20:25:05 2018 daemon.info dnsmasq[2063]: read /tmp/hosts/dhcp.cfg01411c - 1 addresses
Tue Jan 30 20:25:05 2018 daemon.info dnsmasq-dhcp[2063]: read /etc/ethers - 0 addresses
Tue Jan 30 20:36:14 2018 daemon.info hostapd: wlan0: STA 6c:88:14:ee:82:b4 IEEE 802.11: authenticated
Tue Jan 30 20:36:14 2018 daemon.info hostapd: wlan0: STA 6c:88:14:ee:82:b4 IEEE 802.11: associated (aid 1)
Tue Jan 30 20:36:14 2018 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 6c:88:14:ee:82:b4
Tue Jan 30 20:36:14 2018 daemon.info hostapd: wlan0: STA 6c:88:14:ee:82:b4 WPA: pairwise key handshake completed (RSN)
Tue Jan 30 20:36:14 2018 daemon.info dnsmasq-dhcp[2063]: DHCPREQUEST(br-lan) 192.168.1.118 6c:88:14:ee:82:b4
Tue Jan 30 20:36:14 2018 daemon.info dnsmasq-dhcp[2063]: DHCPACK(br-lan) 192.168.1.118 6c:88:14:ee:82:b4 HP-8770W
Tue Jan 30 20:36:14 2018 daemon.warn odhcpd[1319]: DHCPV6 SOLICIT IA_NA from 0001000119aa32d7a45d365a91de on br-lan: no addresses available
Tue Jan 30 20:36:14 2018 daemon.info dnsmasq[2063]: read /etc/hosts - 4 addresses
Tue Jan 30 20:36:14 2018 daemon.info dnsmasq[2063]: read /tmp/hosts/odhcpd - 0 addresses
Tue Jan 30 20:36:14 2018 daemon.info dnsmasq[2063]: read /tmp/hosts/dhcp.cfg01411c - 1 addresses
Tue Jan 30 20:36:14 2018 daemon.info dnsmasq-dhcp[2063]: read /etc/ethers - 0 addresses
Tue Jan 30 20:36:15 2018 daemon.warn odhcpd[1319]: DHCPV6 SOLICIT IA_NA from 0001000119aa32d7a45d365a91de on br-lan: no addresses available
Tue Jan 30 20:36:15 2018 daemon.warn odhcpd[1319]: DHCPV6 SOLICIT IA_NA from 0001000119aa32d7a45d365a91de on br-lan: no addresses available
Tue Jan 30 20:36:15 2018 daemon.warn odhcpd[1319]: DHCPV6 SOLICIT IA_NA from 0001000119aa32d7a45d365a91de on br-lan: no addresses available
Tue Jan 30 20:36:15 2018 daemon.warn odhcpd[1319]: DHCPV6 SOLICIT IA_NA from 0001000119aa32d7a45d365a91de on br-lan: no addresses available
Tue Jan 30 20:36:15 2018 daemon.warn odhcpd[1319]: DHCPV6 SOLICIT IA_NA from 0001000119aa32d7a45d365a91de on br-lan: no addresses available
Tue Jan 30 20:36:15 2018 daemon.warn odhcpd[1319]: DHCPV6 SOLICIT IA_NA from 0001000119aa32d7a45d365a91de on br-lan: no addresses available
Tue Jan 30 20:36:17 2018 daemon.info dnsmasq-dhcp[2063]: DHCPINFORM(br-lan) 192.168.1.118 6c:88:14:ee:82:b4

Wziąłem na próbę jeszcze jeden dysk z LG i voila:
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.466150] hub 1-0:1.0: USB hub found
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.469970] hub 1-0:1.0: 2 ports detected
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.474445] xhci-mtk 1e1c0000.xhci: xHCI Host Controller
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.479748] xhci-mtk 1e1c0000.xhci: new USB bus registered, assigned bus number 2
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.487430] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.496433] hub 2-0:1.0: USB hub found
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.500247] hub 2-0:1.0: 1 port detected
Tue Jan 30 20:24:53 2018 kern.info kernel: [    7.510153] usbcore: registered new interface driver usb-storage
Tue Jan 30 20:24:53 2018 user.info kernel: [    7.516492] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
Tue Jan 30 20:24:53 2018 user.info kernel: [    7.540916] init: - preinit -
Tue Jan 30 20:24:53 2018 kern.info kernel: [    8.000625] usb 1-1: new high-speed USB device number 2 using xhci-mtk
Tue Jan 30 20:24:53 2018 kern.info kernel: [    8.173134] usb-storage 1-1:1.0: USB Mass Storage device detected
Tue Jan 30 20:24:53 2018 kern.info kernel: [    8.179783] scsi host0: usb-storage 1-1:1.0
Tue Jan 30 20:24:53 2018 kern.notice kernel: [    9.241511] scsi 0:0:0:0: Direct-Access     Hitachi  HTS545050B9A300       PQ: 0 ANSI: 2 CCS
Tue Jan 30 20:24:53 2018 kern.notice kernel: [    9.251673] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB)
Tue Jan 30 20:24:53 2018 kern.notice kernel: [    9.259634] sd 0:0:0:0: [sda] Write Protect is off
Tue Jan 30 20:24:53 2018 kern.debug kernel: [    9.264446] sd 0:0:0:0: [sda] Mode Sense: 28 00 00 00
Tue Jan 30 20:24:53 2018 kern.err kernel: [    9.264826] sd 0:0:0:0: [sda] No Caching mode page found
Tue Jan 30 20:24:53 2018 kern.err kernel: [    9.270117] sd 0:0:0:0: [sda] Assuming drive cache: write through
Tue Jan 30 20:24:53 2018 kern.info kernel: [    9.296688]  sda: sda1
Tue Jan 30 20:24:53 2018 kern.notice kernel: [    9.301285] sd 0:0:0:0: [sda] Attached SCSI disk

Ten jest i da się go podmontować.

Czyżby dyski Seagate były źle rozpoznawane/nie rozpoznawane pod OpenWrt/Lede/LiCI?

10 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,915

Odp: Xiaomi WiFi Router 3G i Seagate Backup Plus Hub - Mediatek SOC USB3.0

Albo mają problem z usb 3.0

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

Cezary's Strona

11 Odpowiedź przez r44

  • r44
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2018-01-26
  • Posty: 45

Odp: Xiaomi WiFi Router 3G i Seagate Backup Plus Hub - Mediatek SOC USB3.0

oba dyski Seagate są USB3.0
ten LG to USB2.0

Próbowałem przez HUB2.0
ale dalej są nie wykrywane.

Czy na tą chwilę jestem w stanie coś jeszcze zrobić?

12 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,915

Odp: Xiaomi WiFi Router 3G i Seagate Backup Plus Hub - Mediatek SOC USB3.0

Raczej nic.

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

Cezary's Strona

13 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,915

Odp: Xiaomi WiFi Router 3G i Seagate Backup Plus Hub - Mediatek SOC USB3.0

Tue Jan 30 20:24:53 2018 kern.info kernel: [   34.460635] scsi 0:0:0:0: tag#0 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN
Tue Jan 30 20:24:53 2018 kern.info kernel: [   34.468187] scsi 0:0:0:0: tag#0 CDB: opcode=0x12 12 00 00 00 24 00
Tue Jan 30 20:24:53 2018 kern.err kernel: [   35.510615] scsi host0: uas_eh_bus_reset_handler FAILED to get lock err -16

To wskazuje na błąd na magistrali usb z tym urządzeniem.

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

Cezary's Strona

14 Odpowiedź przez r44 (edytowany przez r44 2018-01-31 22:52:09)

  • r44
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2018-01-26
  • Posty: 45

Odp: Xiaomi WiFi Router 3G i Seagate Backup Plus Hub - Mediatek SOC USB3.0

Znalazłem takie coś:
https://bbs.archlinux.org/viewtopic.php?id=125831

Ok, i've finally figured it out.  If I understand it correctly, the problem lies in the slow initialization of the drive's firmware to be ready to be scanned by the usb_storage kernel module. If you look at the output of "cat /sys/module/usb_storage/parameters/delay_use" it shows the value "1" (second). The default value for the kernel 3.3 should be "5" as stated here: http://www.mjmwired.net/kernel/Document … s.txt#2713. So you can either add the parameter "usb-storage.delay_use=5" to the kernel or add "options usb_storage delay_use=5" to some custom .conf file in the modprobe.d directory. If you chose the latter method and have the module usb_storage put in the MODULES array in mkinitcpio.conf (because of the booting process being stuck while the drive is attached) at the same time, don't forget to also uncomment the FILES array and have the custom file from modprobe.d be incorporated there otherwise the delay_use option won't apply since the usb_storage module is already loaded by intiramfs with default options. Now I can re-attach the drive how many times i want and the drive is allways detected by fdisk, parted and thus by KDE device notifier too. And what more I don't have to have the drive attached during boot but I can do it later when system is already on and it still gets detected.

Tylko jak zmienić opisana wartość z 1(taka teraz jest)  na 5.
Pytanie jest w zasadzie takie co muszę w używanym firmware pozmieniać i jak?

------------------------------------------------------------------------------------------------------
wysłałem komendę:
echo 15 > /sys/module/usb_storage/parameters/delay_use

i potem podłączyłem dysk:
[  657.891023] usb 1-1: new high-speed USB device number 15 using xhci-mtk
[  658.074959] hub 1-1:1.0: USB hub found
[  658.079089] hub 1-1:1.0: 3 ports detected
[  658.211314] usb 2-1: new SuperSpeed USB device number 8 using xhci-mtk
[  658.247320] hub 2-1:1.0: USB hub found
[  658.251727] hub 2-1:1.0: 3 ports detected
[  659.211543] usb 1-1-port2: Cannot enable. Maybe the USB cable is bad?
[  659.311202] usb 2-1.1: new SuperSpeed USB device number 9 using xhci-mtk
[  659.345654] scsi host0: uas
[  659.350330] xhci-mtk 1e1c0000.xhci: ERROR Transfer event for disabled endpoint or incorrect stream ring
[  659.359738] xhci-mtk 1e1c0000.xhci: @000000000f01d800 0f368200 00000000 05000000 04078000
[  659.367921] xhci-mtk 1e1c0000.xhci: ERROR Transfer event for disabled endpoint or incorrect stream ring
[  659.377298] xhci-mtk 1e1c0000.xhci: @000000000f01d810 0f368100 00000000 05000000 04038000
[  664.651142] usb 1-1.3: new high-speed USB device number 18 using xhci-mtk
[  664.785668] usb-storage 1-1.3:1.0: USB Mass Storage device detected
[  664.792819] scsi host1: usb-storage 1-1.3:1.0
[  665.126368] usb 1-1.3: USB disconnect, device number 18

Nie zadziałało.
Niestety po resecie routera, wartość domyślna delay_use=1
------------------------------------------------------------------------------------------------------
https://forums.linuxmint.com/viewtopic. … 80#p502932
Jak zrobić czarną listę na ten dysk wg tego linku?
Ludzie tu piszą, że problemem jest uas, jak usunąłem pakiet  kmod-usb-storage-uas
to niestety system pisał że błędny kabelek etc, więc przywróciłem pakiet.

15 Odpowiedź przez r44

  • r44
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2018-01-26
  • Posty: 45

Odp: Xiaomi WiFi Router 3G i Seagate Backup Plus Hub - Mediatek SOC USB3.0

W akcie desperacji podłączyłem dysk przez hub USB2.0 i dysk jest wreszcie widziany.
Planuje jeszcze zrobić taką próbę z hub'e, USB3.0.
Czy te najtańsze huby, takie z wyłącznikami do każdego wyjścia z osobno to działają z OPENWRT/LEDE/LUCI?

16 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,915

Odp: Xiaomi WiFi Router 3G i Seagate Backup Plus Hub - Mediatek SOC USB3.0

Nie spotkałem jeszcze huba który by nie działał. Inna sprawa JAK działa...

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

Cezary's Strona

17 Odpowiedź przez r44

  • r44
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2018-01-26
  • Posty: 45

Odp: Xiaomi WiFi Router 3G i Seagate Backup Plus Hub - Mediatek SOC USB3.0

Sprawdzone na nowym HUB USB3.0 - nie działa, błędy jak wcześniej opisywałem.
Do tego HUB USB3.0 podłączonego do routera, podłączyłem HUB USB2.0 i do niego
posiadany Seagate (USB3.0) - działa.
Ktoś może powiedzieć czy działa mu jakikolwiek dysk USB3.0 podłączony do ww routera?

Cezary,
widzę że pojawiła się Twoja nowa kompilacja w
http://dl.eko.one.pl/luci/lede/snapshot … ps/mt7621/

Czy da się gdzieś wyczytać czym ona różni się od poprzedniej co mam teraz w routerze?
Czy np wrzucając do /tmp to co poniżej i wywołując komendę będę miał nową wersję (sory za lamerskie pytanie)
sysupgrade -n luci-snapshot-r6007-e7469d5-ramips-mt7621-mir3g-squashfs-sysupgrade.tar
Czy po takim "update" moje ustawienia i skrypty pozostaną?

18 Odpowiedź przez tymmej

  • tymmej
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2011-01-27
  • Posty: 110

Odp: Xiaomi WiFi Router 3G i Seagate Backup Plus Hub - Mediatek SOC USB3.0

Ja mam na dysku Lacie podłączonym przez USB 3 coś takiego: https://bugs.lede-project.org/index.php … sk_id=1305

Obejście problemu: niewtykanie USB do końca do routera. Dzięki temu tylko piny od USB 2 mają kontakt i dysk działa.

19 Odpowiedź przez Cezary

  • Skąd: Warszawa
  • Zarejestrowany: 2006-02-25
  • Posty: 115,915

Odp: Xiaomi WiFi Router 3G i Seagate Backup Plus Hub - Mediatek SOC USB3.0

r44 napisał/a:

Cezary,
widzę że pojawiła się Twoja nowa kompilacja w
http://dl.eko.one.pl/luci/lede/snapshot … ps/mt7621/

Czy da się gdzieś wyczytać czym ona różni się od poprzedniej co mam teraz w routerze?

Tu masz co się zmieniło: https://github.com/openwrt/openwrt/commits/master

r44 napisał/a:

Czy np wrzucając do /tmp to co poniżej i wywołując komendę będę miał nową wersję (sory za lamerskie pytanie)
sysupgrade -n luci-snapshot-r6007-e7469d5-ramips-mt7621-mir3g-squashfs-sysupgrade.tar
Czy po takim "update" moje ustawienia i skrypty pozostaną?

Będziesz miał nową wersję ale nic z ustawień nie zostanie. Skrypty też nie zostają. Nigdy w sumie.

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

Cezary's Strona

20 Odpowiedź przez c#Hunter (edytowany przez c#Hunter 2018-02-08 08:33:00)

  • Zarejestrowany: 2017-10-16
  • Posty: 59

Odp: Xiaomi WiFi Router 3G i Seagate Backup Plus Hub - Mediatek SOC USB3.0

Jak wam dobrze działa wszystko to nie wgrywajcie najnowszej wersji bo na forum developerskim co chwila płacz że coś nie działa komuś. Za dużo mieszają w sterownikach od 2,4GHz i jest jakiś problem z obsługa dysków po USB.

Edit: problem z dyskiem rozwiązuje użycie kernela 4.4... Poszukajcie pomocy na tym forum developerskim.

21 Odpowiedź przez kipronar (edytowany przez kipronar 2018-02-10 19:28:06)

  • Zarejestrowany: 2017-10-22
  • Posty: 186

Odp: Xiaomi WiFi Router 3G i Seagate Backup Plus Hub - Mediatek SOC USB3.0

@r44
USB 3 to chyba bardziej powszechny problem- z Raspberry Pi Zero mam ten sam kłopot.
Rozwiązanie znalazłem tu:
https://askubuntu.com/questions/457901/ … 3-0-system
Wystarczyło wpiąć kawałek przedłużacza USB 2 pomiędzy  Pi Zero a hub  (NEC uPD720200) USB 3.
Ale w moim przypadku prędkość USB 3 była fanaberią, którą mogłem odpuścić.

22 Odpowiedź przez marcinw788

  • Zarejestrowany: 2017-10-27
  • Posty: 41

Odp: Xiaomi WiFi Router 3G i Seagate Backup Plus Hub - Mediatek SOC USB3.0

A ten hub 3.0 był aktywny (z zasilaczem)? Mam podobny problem z tym że nie mam jeszcze huba 3.0 (na 2.0 wszystko hula). Po podłączeniu dysku bezpośrednio do mir3g wykrywa, ale wyskakują błędy. Może za mało prądu?

Bo już sam nie wiem czy inwestować w nowy hub czy nie...

23 Odpowiedź przez r44

  • r44
  • Użytkownik
  • Nieaktywny
  • Zarejestrowany: 2018-01-26
  • Posty: 45

Odp: Xiaomi WiFi Router 3G i Seagate Backup Plus Hub - Mediatek SOC USB3.0

Hub ma wejście do podłączenia zasilenia.
Niestety czy z zasilaczem czy bez to dysk 2.5cala usb3.0 nie zadziałał.
Więc to nie problem zasilania.
Dysk 3.5cala ma swój zasilacz i z ww hubem również nie działa.
Za to działa przez hub2.0. Czyli jak bezpośrednio podłącze hub2.0 do routera
to router widzi dysk i dysk jest podmontowywany.
Jak podłączę Hub3.0 i do niego Hub2.0 i do niego z kolei dysk usb3.0 to też dysk się podmontowuje.
Dysk Usb2.0 działa dało się podmontować.

Bardziej boli mnie że dysk po czasie znika z systemu....

24 Odpowiedź przez ad2014

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

Odp: Xiaomi WiFi Router 3G i Seagate Backup Plus Hub - Mediatek SOC USB3.0

@r44 a jak masz przez usb 2.0 podłaczone  to jaki masz parametr ustawiony  w  /sys/module/usb_storage/parameters/delay_use
- pytam z ciekawości  bo jak mam dysk usb3.0  podlaczony do tunera sat do usb 2.0  i  ustawia  się  na  5

25 Odpowiedź przez marcinw788

  • Zarejestrowany: 2017-10-27
  • Posty: 41

Odp: Xiaomi WiFi Router 3G i Seagate Backup Plus Hub - Mediatek SOC USB3.0

Kurcze, tez mnie kusi ten dysk, ale czytam sporo opini na amzonie, ze są z nim problemy nawet na Mac-u. Znalazłem też recenzję (chyba na cnet), w ktorej go chwalą, ale piszą, że nie zawsze jest wykrywany (czy wlasciwie urzadzenia podpiete do huba) gdy jest podłączony przez... usb 2.

U siebie probowałem podłączyć 2,5 calowy hdd do mir3g, ale bez dodatkowego zasialnai, wiec w sumie nie miało prawa zadziałać. Stary dysk na usb2 działa bez problemu, ale chciałoby się większe transfery... Więc już sam nie wiem.

Testowałeś tego Seagate bezpośrednio z kompem (czy też bywają problemy z widocznością  w systemie)?