Dear hammer,
thank you for your input. I will try your statement later. I hope it will work. I will give you a feedback.
Andy_x
I have soldered 3 pins to the board of my Xiaomi 3G router. I buy in Aliexpress an USB TTL cp2102.
I have followed the following tutorial for Linux:
https://elinux.org/Communicate_with_hardware_using_USB_cable_for_Ubuntu
Everything seems Ok.
But I try.
Power on the router.... then conect the usb to de pc... them
sudo gtkterm
Configuration -> Port -> /dev/ttyUSB0 -> baud rate 115200
But the screen of gtkterm is black. What am I doing wrong?
In windows i install the drivers. Open putty -> COM0 -> 115200 => Black screen
RX <—> TX — correctly
TX <—> RX — correctly
TX <—> TX — wrong
RX <—> RX — wrong
Seems ar71xx (big endian MIPS) is affected as well. I'm saying kernel bug at this point.
1 Like
Thanks all. I see some light :). I put in the console:
setenv flag_try_sys1_failed 0
setenv flag_last_success 0
saveenv
reset
But do not work :(. Then I try:
setenv ssh_en 1
setenv uart_en 1
saveenv
reset
But it do not work. This is what I get in console (Pardon for the format):
[ 4.381281] 8021q: 802.1Q VLAN Support v1.8
[ 4.388554] UBI: auto-attach mtd9
[ 4.391885] ubi0: attaching mtd9
[ 5.503402] ubi0: scanning is finished
[ 5.523224] ubi0: attached mtd9 (name "ubi", size 117 MiB)
[ 5.528728] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
[ 5.535581] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
[ 5.542334] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
[ 5.549272] ubi0: good PEBs: 940, bad PEBs: 0, corrupted PEBs: 0
[ 5.555263] ubi0: user volume: 0, internal volumes: 1, max. volumes count: 128
[ 5.562452] ubi0: max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 2105747779
[ 5.571549] ubi0: available PEBs: 916, total reserved PEBs: 24, PEBs reserved for bad PEB handling: 20
[ 5.580843] ubi0: background thread "ubi_bgt0d" started, PID 375
[ 5.580861] hctosys: unable to open rtc device (rtc0)
[ 5.592400] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
[ 5.599891] Please append a correct "root=" boot option; here are the available partitions:
[ 5.608235] 1f00 512 mtdblock0 [ 5.612222] (driver?)
[ 5.614572] 1f01 256 mtdblock1 [ 5.618566] (driver?)
[ 5.620917] 1f02 256 mtdblock2 [ 5.624899] (driver?)
[ 5.627267] 1f03 256 mtdblock3 [ 5.631251] (driver?)
[ 5.633600] 1f04 256 mtdblock4 [ 5.637594] (driver?)
[ 5.639945] 1f05 256 mtdblock5 [ 5.643927] (driver?)
[ 5.646295] 1f06 256 mtdblock6 [ 5.650280] (driver?)
[ 5.652629] 1f07 4096 mtdblock7 [ 5.656623] (driver?)
[ 5.658974] 1f08 4096 mtdblock8 [ 5.662956] (driver?)
[ 5.665327] 1f09 120320 mtdblock9 [ 5.669312] (driver?)
[ 5.671661] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 5.682169] Rebooting in 1 seconds..
===================================================================
MT7621 stage1 code 10:33:11 (ASIC)
CPU=50000000 HZ BUS=12500000 HZ
==================================================================
Change MPLL source from XTAL to CR...
do MEMPLL setting..
MEMPLL Config : 0x11100000
3PLL mode + External loopback
=== XTAL-40Mhz === DDR-1200Mhz ===
PLL3 FB_DL: 0xc, 1/0 = 676/348 31000000
PLL4 FB_DL: 0x10, 1/0 = 547/477 41000000
PLL2 FB_DL: 0x14, 1/0 = 749/275 51000000
do DDR setting..[00320381]
Apply DDR3 Setting...(use customer AC)
0 8 16 24 32 40 48 56 64 72 80 88 96 104 112 120
--------------------------------------------------------------------------------
0000:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0001:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0002:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0003:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0004:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0005:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0006:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0007:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0008:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0009:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
000A:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
000B:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
000C:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
000D:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1
000E:| 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1
000F:| 0 0 0 0 1 1 1 1 1 1 1 1 1 1 0 0
0010:| 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0
0011:| 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0
0012:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0013:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0014:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0015:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0016:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0017:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0018:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0019:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
001A:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
001B:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
001C:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
001D:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
001E:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
001F:| 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
rank 0 coarse = 15
rank 0 fine = 72
B:| 0 0 0 0 0 0 0 0 0 0 1 1 1 0 0 0
opt_dle value:11
DRAMC_R0DELDLY[018]=0000211F
==================================================================
RX DQS perbit delay software calibration
==================================================================
1.0-15 bit dq delay value
==================================================================
bit| 0 1 2 3 4 5 6 7 8 9
--------------------------------------
0 | 10 6 9 9 7 7 9 5 6 7
10 | 8 9 9 10 7 11
--------------------------------------
==================================================================
2.dqs window
x=pass dqs delay value (min~max)center
y=0-7bit DQ of every group
input delay:DQS0 =31 DQS1 = 33
==================================================================
bit DQS0 bit DQS1
0 (1~60)30 8 (1~58)29
1 (1~59)30 9 (1~58)29
2 (1~62)31 10 (1~61)31
3 (1~60)30 11 (1~59)30
4 (1~60)30 12 (1~62)31
5 (1~62)31 13 (1~61)31
6 (1~62)31 14 (1~60)30
7 (1~60)30 15 (3~63)33
==================================================================
3.dq delay value last
==================================================================
bit| 0 1 2 3 4 5 6 7 8 9
--------------------------------------
0 | 11 7 9 10 8 7 9 6 10 11
10 | 10 12 11 12 10 11
==================================================================
==================================================================
TX perbyte calibration
==================================================================
DQS loop = 15, cmp_err_1 = ffff0000
dqs_perbyte_dly.last_dqsdly_pass[0]=15, finish count=1
dqs_perbyte_dly.last_dqsdly_pass[1]=15, finish count=2
DQ loop=15, cmp_err_1 = ffff01a2
DQ loop=14, cmp_err_1 = ffff0080
dqs_perbyte_dly.last_dqdly_pass[1]=14, finish count=1
DQ loop=13, cmp_err_1 = ffff0080
DQ loop=12, cmp_err_1 = ffff0000
dqs_perbyte_dly.last_dqdly_pass[0]=12, finish count=2
byte:0, (DQS,DQ)=(9,8)
byte:1, (DQS,DQ)=(8,8)
20,data:89
[EMI] DRAMC calibration passed
===================================================================
MT7621 stage1 code done
CPU=50000000 HZ BUS=12500000 HZ
===================================================================
U-Boot 1.1.3 (Jul 13 2017 - 17:10:56)
Board: Ralink APSoC DRAM: 256 MB
Power on memory test. Memory size= 256 MB...OK!
relocate_code Pointer at: 8ffac000
Config XHCI 40M PLL
******************************
Software System Reset Occurred
******************************
Allocate 16 byte aligned buffer: 8ffdff50
Enable NFI Clock
# MTK NAND # : Use HW ECC
NAND ID [C8 D1 80 95 40]
Device not found, ID: c8d1
Not Support this Device!
chip_mode=00000001
Support this Device in MTK table! c8d1
select_chip
[NAND]select ecc bit:4, sparesize :64 spare_per_sector=16
Signature matched and data read!
load_fact_bbt success 1023
load fact bbt success
[mtk_nand] probe successfully!
mtd->writesize=2048 mtd->oobsize=64, mtd->erasesize=131072 devinfo.iowidth=8
..============================================
Ralink UBoot Version: 5.0.0.0
--------------------------------------------
ASIC MT7621A DualCore (MAC to MT7530 Mode)
DRAM_CONF_FROM: Auto-Detection
DRAM_TYPE: DDR3
DRAM bus: 16 bit
Xtal Mode=5 OCP Ratio=1/4
Flash component: NAND Flash
Date:Jul 13 2017 Time:17:10:56
============================================
icache: sets:256, ways:4, linesz:32 ,total:32768
dcache: sets:256, ways:4, linesz:32 ,total:32768
##### The CPU freq = 880 MHZ ####
estimate memory size =256 Mbytes
#Reset_MT7530
set LAN/WAN LWLLL
Please choose the operation:
1: Load system code to SDRAM via TFTP.
2: Load system code then write to Flash via TFTP.
3: Boot system code via Flash (default).
4: Entr boot command line interface.
7: Load Boot Loader code then write to Flash via Serial.
9: Load Boot Loader code then write to Flash via TFTP.
3
You choosed 4
0
4: System Enter Boot Command Line Interface.
U-Boot 1.1.3 (Jul 13 2017 - 17:10:56)
MT7621 #Thanks to @guilhermehnog:
I’ve been able to unbrick, what i did was:
"1 - Conect to Serial
2 - type 4 to enter command prompt
3 - type this commands:
setenv flag_try_sys1_failed=0 (check if flag name is correct with printenv)
setenv flag_try_sys2_failed=0 (check if flag name is correct with printenv)
setenv flag_last_success=0
saveenv
4 - connect pendrive with original stock dev firmware renamed to miwifi.bin
5 - default brick recovery process: reboot pressing reset button until yellow led start flashing, then release reset button.
6 - wait completion
7 - Done.
Thanks Hammer and Rising_sun for the help."
Works!!!!
OpenWrt SNAPSHOT r6150-dc7a1e8
signal strength: -60dbm
I use just only one client to connect router: a ipad air2.
When wlan just start:
I'm a newuser of this forum , I can post just one image, so I delete this image.
ping value is mostly below 100ms at this time.
After play game for some time, network get stucked, at the same place, close all programs on pad, ping value increase huge, won't decrease untill restart wlan on router, after restart ping value decrease to normal:
sometimes, ping value is huge just at first connect.
I'm sure it's mt76 driver's problem, because it's never happen at wndr3800 openwrt system, when totally at same conditons.
Looks pretty normal, I think you have a huge beacon intervall setting.
Here with standard beacon intervall :
PING 192.168.178.54 (192.168.178.54): 56 data bytes
64 bytes from 192.168.178.54: seq=4 ttl=64 time=255.147 ms << screen already on
64 bytes from 192.168.178.54: seq=5 ttl=64 time=2.927 ms
64 bytes from 192.168.178.54: seq=6 ttl=64 time=125.018 ms
64 bytes from 192.168.178.54: seq=7 ttl=64 time=37.873 ms
64 bytes from 192.168.178.54: seq=8 ttl=64 time=50.598 ms
64 bytes from 192.168.178.54: seq=9 ttl=64 time=66.231 ms
64 bytes from 192.168.178.54: seq=10 ttl=64 time=80.357 ms
64 bytes from 192.168.178.54: seq=11 ttl=64 time=93.982 ms
64 bytes from 192.168.178.54: seq=12 ttl=64 time=108.623 ms
64 bytes from 192.168.178.54: seq=13 ttl=64 time=122.140 ms
64 bytes from 192.168.178.54: seq=14 ttl=64 time=134.786 ms
64 bytes from 192.168.178.54: seq=15 ttl=64 time=534.684 ms
64 bytes from 192.168.178.54: seq=16 ttl=64 time=162.722 ms
64 bytes from 192.168.178.54: seq=17 ttl=64 time=176.963 ms
64 bytes from 192.168.178.54: seq=18 ttl=64 time=192.263 ms
64 bytes from 192.168.178.54: seq=19 ttl=64 time=206.420 ms
64 bytes from 192.168.178.54: seq=20 ttl=64 time=218.882 ms
64 bytes from 192.168.178.54: seq=21 ttl=64 time=232.816 ms
64 bytes from 192.168.178.54: seq=22 ttl=64 time=248.760 ms
64 bytes from 192.168.178.54: seq=23 ttl=64 time=261.155 ms
64 bytes from 192.168.178.54: seq=24 ttl=64 time=1.559 ms << used wifi on my iphone
64 bytes from 192.168.178.54: seq=25 ttl=64 time=2.284 ms
64 bytes from 192.168.178.54: seq=26 ttl=64 time=1.342 ms
64 bytes from 192.168.178.54: seq=27 ttl=64 time=1.739 ms
64 bytes from 192.168.178.54: seq=28 ttl=64 time=2.394 ms
64 bytes from 192.168.178.54: seq=29 ttl=64 time=2.915 ms
64 bytes from 192.168.178.54: seq=30 ttl=64 time=104.120 ms
64 bytes from 192.168.178.54: seq=31 ttl=64 time=118.033 ms
64 bytes from 192.168.178.54: seq=32 ttl=64 time=1.323 ms
64 bytes from 192.168.178.54: seq=33 ttl=64 time=1.315 ms
64 bytes from 192.168.178.54: seq=34 ttl=64 time=1.332 ms
64 bytes from 192.168.178.54: seq=35 ttl=64 time=2.730 ms
64 bytes from 192.168.178.54: seq=36 ttl=64 time=2.804 ms
64 bytes from 192.168.178.54: seq=37 ttl=64 time=3.635 ms << put screen to off
64 bytes from 192.168.178.54: seq=38 ttl=64 time=217.033 ms
64 bytes from 192.168.178.54: seq=39 ttl=64 time=2.900 ms
64 bytes from 192.168.178.54: seq=40 ttl=64 time=1.859 ms
64 bytes from 192.168.178.54: seq=41 ttl=64 time=3.371 ms
64 bytes from 192.168.178.54: seq=42 ttl=64 time=17.241 ms
64 bytes from 192.168.178.54: seq=43 ttl=64 time=31.232 ms
64 bytes from 192.168.178.54: seq=44 ttl=64 time=45.347 ms
64 bytes from 192.168.178.54: seq=45 ttl=64 time=59.348 ms
.... << no answer anymore
Now with 2500ms as beacon intervall :
64 bytes from 192.168.178.54: seq=176 ttl=64 time=300.258 ms << screen already on
64 bytes from 192.168.178.54: seq=177 ttl=64 time=1835.747 ms
64 bytes from 192.168.178.54: seq=178 ttl=64 time=825.881 ms
64 bytes from 192.168.178.54: seq=179 ttl=64 time=3.251 ms
64 bytes from 192.168.178.54: seq=180 ttl=64 time=2745.522 ms
64 bytes from 192.168.178.54: seq=181 ttl=64 time=1735.636 ms
64 bytes from 192.168.178.54: seq=182 ttl=64 time=725.718 ms
64 bytes from 192.168.178.54: seq=183 ttl=64 time=1.354 ms
64 bytes from 192.168.178.54: seq=184 ttl=64 time=1369.269 ms
64 bytes from 192.168.178.54: seq=185 ttl=64 time=359.392 ms
64 bytes from 192.168.178.54: seq=186 ttl=64 time=183.468 ms
64 bytes from 192.168.178.54: seq=187 ttl=64 time=1.801 ms
64 bytes from 192.168.178.54: seq=188 ttl=64 time=1.388 ms
64 bytes from 192.168.178.54: seq=189 ttl=64 time=674.256 ms
64 bytes from 192.168.178.54: seq=190 ttl=64 time=1329.445 ms
64 bytes from 192.168.178.54: seq=191 ttl=64 time=319.563 ms
64 bytes from 192.168.178.54: seq=192 ttl=64 time=1.359 ms
64 bytes from 192.168.178.54: seq=193 ttl=64 time=1.321 ms
64 bytes from 192.168.178.54: seq=194 ttl=64 time=9.719 ms
64 bytes from 192.168.178.54: seq=195 ttl=64 time=2.946 ms
64 bytes from 192.168.178.54: seq=196 ttl=64 time=551.672 ms
64 bytes from 192.168.178.54: seq=197 ttl=64 time=837.358 ms
64 bytes from 192.168.178.54: seq=198 ttl=64 time=3.050 ms
64 bytes from 192.168.178.54: seq=199 ttl=64 time=77.710 ms
64 bytes from 192.168.178.54: seq=200 ttl=64 time=1627.863 ms
64 bytes from 192.168.178.54: seq=201 ttl=64 time=618.004 ms
64 bytes from 192.168.178.54: seq=202 ttl=64 time=4700.818 ms
64 bytes from 192.168.178.54: seq=203 ttl=64 time=3690.964 ms
64 bytes from 192.168.178.54: seq=204 ttl=64 time=2682.227 ms
64 bytes from 192.168.178.54: seq=205 ttl=64 time=1672.348 ms
64 bytes from 192.168.178.54: seq=206 ttl=64 time=662.512 ms
64 bytes from 192.168.178.54: seq=207 ttl=64 time=2.810 ms
64 bytes from 192.168.178.54: seq=208 ttl=64 time=1228.982 ms
64 bytes from 192.168.178.54: seq=209 ttl=64 time=219.114 ms
64 bytes from 192.168.178.54: seq=210 ttl=64 time=1.200 ms << used wifi on iphone
64 bytes from 192.168.178.54: seq=211 ttl=64 time=1.940 ms
64 bytes from 192.168.178.54: seq=212 ttl=64 time=1.478 ms
64 bytes from 192.168.178.54: seq=213 ttl=64 time=2.280 ms
64 bytes from 192.168.178.54: seq=214 ttl=64 time=3.137 ms
64 bytes from 192.168.178.54: seq=215 ttl=64 time=3.010 ms
64 bytes from 192.168.178.54: seq=216 ttl=64 time=830.521 ms
64 bytes from 192.168.178.54: seq=217 ttl=64 time=2.988 ms
64 bytes from 192.168.178.54: seq=218 ttl=64 time=258.152 ms
64 bytes from 192.168.178.54: seq=219 ttl=64 time=357.862 ms
64 bytes from 192.168.178.54: seq=220 ttl=64 time=201.423 ms
64 bytes from 192.168.178.54: seq=221 ttl=64 time=2.967 ms
64 bytes from 192.168.178.54: seq=222 ttl=64 time=67.781 ms
64 bytes from 192.168.178.54: seq=223 ttl=64 time=2.833 ms
64 bytes from 192.168.178.54: seq=224 ttl=64 time=428.884 ms
64 bytes from 192.168.178.54: seq=225 ttl=64 time=166.965 ms
64 bytes from 192.168.178.54: seq=226 ttl=64 time=3.050 ms
64 bytes from 192.168.178.54: seq=227 ttl=64 time=2.789 ms << screen off somewhere here
64 bytes from 192.168.178.54: seq=240 ttl=64 time=1.360 ms
64 bytes from 192.168.178.54: seq=241 ttl=64 time=295.652 ms
64 bytes from 192.168.178.54: seq=242 ttl=64 time=129.838 ms
64 bytes from 192.168.178.54: seq=243 ttl=64 time=423.607 ms
64 bytes from 192.168.178.54: seq=244 ttl=64 time=271.309 ms
64 bytes from 192.168.178.54: seq=245 ttl=64 time=3.209 ms
64 bytes from 192.168.178.54: seq=246 ttl=64 time=6793.239 ms
64 bytes from 192.168.178.54: seq=247 ttl=64 time=5783.348 ms
64 bytes from 192.168.178.54: seq=248 ttl=64 time=4776.219 ms
64 bytes from 192.168.178.54: seq=249 ttl=64 time=3766.335 ms
64 bytes from 192.168.178.54: seq=250 ttl=64 time=2756.420 ms
64 bytes from 192.168.178.54: seq=251 ttl=64 time=1746.496 ms
64 bytes from 192.168.178.54: seq=252 ttl=64 time=736.554 ms
64 bytes from 192.168.178.54: seq=253 ttl=64 time=3.134 ms
64 bytes from 192.168.178.54: seq=254 ttl=64 time=1466.780 ms
64 bytes from 192.168.178.54: seq=255 ttl=64 time=456.913 ms
64 bytes from 192.168.178.54: seq=256 ttl=64 time=4881.948 ms
64 bytes from 192.168.178.54: seq=257 ttl=64 time=3872.095 ms
64 bytes from 192.168.178.54: seq=258 ttl=64 time=2862.241 ms
64 bytes from 192.168.178.54: seq=259 ttl=64 time=1852.294 ms
64 bytes from 192.168.178.54: seq=260 ttl=64 time=842.311 ms
64 bytes from 192.168.178.54: seq=261 ttl=64 time=2.997 ms
64 bytes from 192.168.178.54: seq=262 ttl=64 time=450.499 ms
.... << no answer anymore
But having one small issue at 5Ghz, device cant transfer anything at bad wifi reception anymore, iPhone and router shows as connected, and does not recover for a long time eventhough standing in front of the router after the event. Wifi down, up (command "wifi") helps instantly. Maybe it has something with the iPhone -70dbm management. And I think does only happen with my iPhone 7 and not iPhone 5s. The biggest difference I see between the devices is one stream vs two streams for the wifi stream.
2.4Ghz is broken for my iPhones with this router.
Running great otherweise with 5Ghz. Thanks to nbd and the openwrt developers. Great work. 
Edit: Ofcourse not normal if you have not changed dtim at all.
Edit2:I mean beacon intervall not dtim.
no, I have not set beacon interval at all. and I check /var/run/hostapd-phy1.conf, beacon_int=100.
on the contrary, my 2.4g is good with this ipad, so I use 2.4g currently. 5g is buggy and unuseable.
whatever you do on ipad, 5g turns to high ping value >1000ms .
I think problem is in 7612 driver, if problem is in ipad or ios, 2.4g would suffer either. but 2.4g and wndr3800’s 5g are good at same conditions.
hi!
sorry , i have exactly same issue. I have upgraded my xiaomi 3g from here with sysupgrade:
and when i try to install samba i got following error:
Installing luci-app-samba (git-18.047.57952-461df8b-1) to root...
Downloading http://downloads.lede-project.org/snapshots/packages/mipsel_24kc/luci/luci-app-samba_git-18.047.57952-461df8b-1_all.ipk
Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for luci-app-samba:
* samba36-server *
* opkg_install_cmd: Cannot install package luci-app-samba.
and:
opkg install samba36*
Unknown package 'samba36*'.
Collected errors:
* opkg_install_cmd: Cannot install package samba36*.Hello everyone, thank you very much in advance
Sorry for my english but I'm using google translate
I have connected a 3.0 usb disk formatted in ext4 to the usb port of the router, I am doing tests on sftp but I have very bad data transfer, the maximum that achievement is 2.1 MB / Sec. connected over the 5 GB network
That same disk I connect to another computer on the same network and achieve speeds close to 10 MB / Sec
I have loaded the modules kmod-usb3, kmod-usb-core, kmod-usb-ledtrig-usbport, kmod-usb-storage, kmod-usb-storage-uas, kmod-usb3
Can someone tell me if the transfer works on a USB 3.0 disk connected directly to the router's USB?
OpenWrt SNAPSHOT r6223-3cb3836
Thank you
Check "top" on the router during the transfer? sftp uses encryption. Router's cpu might be limiting the speed. I'd try something like http or ftp server as a test instead of sftp.
Thank you very much for the answer, I have tested with an ftp server and the transfer speed is much higher,
@neheb Hy did you try the 4.14 kernel? Is it also affected by the hdd corruption bug? I know its just preliminary support.
By the way anybody tried the new mt76x2 driver which is committed today?https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=608c84b96ea6b4501b9f64d3f9103a6ec8e7a144
4.14 is also affected
A friend of mine has tried a pen drive on a dlink dir860l rev b1 which has the same SoC and he couldn't recreate this bug. Maybe it is a target specific problem or just affected the rotational drives? I'll ask him to try it with a hdd.
That...is a big hint if true. I'll need to test this out when I have time.
This is extremely late by this point, however I had once (before I knew about Padavan's licensing), distributed an image for the Mi3 router over Telegram (and I had seen others distributing over the web during that time).
This was done about a year ago, and while I do not condone this kind of behavior for community products (even if they are not fully in line with Stallman's views (which I do not completely agree with, though I do respect many of them)), I also prefer LEDE's and OpenWRT's views over Padavan's.