Migration to 5.1.4 works on emmc but fails on msata and EXTREMLY SLOW ON WLAN. In-depth knowledge needed for firmware loading errors & wan degradation

Hi,

Today I started upgrade to TOS 5 through foris and it started the upgrade. The problem is that since 2 hours it’s sitting there alle LEDS are lit except WAN is blinking. I cannot connect through foris or luci nor through SSH (it asks for password but then I get “PTY allocation request failed on channel 0”)

I still have internet access but apart from that Turris is more or less dead no incoming ports or anything all else is dead. I don’t know if I should wait any longer or reboot the device or have to go through medkit restore or anything.

Any advice is greatly appreciated as I don’t know how to best remedy this situation.

[UPDATE] Well, as no one answered on this post I tried a reset. Of course didn’t work then I even lost internet access interestingly guest wlan started properly.

So I went on the journey of regaining internet access one way or the other. I started flashing medkits of TOS 5.x HBS branch without success. Then I flashed medkit of my old 3.11.22 schnapps backups (yes I always copy them onto a usb stick weekly) with and without info file. Still no luck.

So thought, ok let’s try factory reset. Still no success and still my guest wireless networks were starting with their names & passwords which I really didn’t understand.

At the end I opened the turris and connected it via serial cable. I saw that it had started TOS 5.3 but with lots of errors on startup. I didn’t even have a eth0 or other eth interfaces, it only had br_guest_turris and wlan0, wlan1, etc.

With serial console I was then able to rollback to the schnapps snapshot before the update and now I’m back on 3.11.21 but my big fear is that once 5.3 is beeing distributed automatically it will break in exactly the same way!

What I think had broken the whole thing was that I’m using /dev/sda3 to boot turris (not eMMC) but why did no one of the recovery methods set the boot mode back to eMMC? To my knowledge at least the factory reset should do the trick but apparently I also didn’t switch from the broken ssd install to emmc which probably contained the proper medkit.

My big fear now is of course what will happen when 5.3 gets distributed automatically. Will it again kill my OS beyound repair?

And how do I finally install 5.3 onto ssd (maybe first install on emmc and then copy everything over?)

And does anyone of the mods like pepe or vcunat have any clue why TOS 5.3 upgrade bricked the ssd installation and why factory reset didn’t set boot mode back to eMMC?

These were the things that actually took me hours to get it back working and still not having 5.3 in the end but my family relies on having a properply working router.

So as long as there’s no explanation what happened here I think automatic updates of TOS 5.3 are NOT READY to be distributed yet as the ssd install had absolutely nothing special in configurations apart from some DHCP stuff for an internal samba4 domain which forwarded everything for that domain to the domain controller. But this should not kill the automatic upgrade.

The upgrade success really depends on what features did you have enabled in Foris software packages tab and whether you did some changes to configuration via Luci/commandline. It seems that the most of Foris-only configs are already supported. If you have other configuration, it may not be (yet) supported. Also make sure you have enough free RAM before the upgrade - e.g. stop LXC containers, suricata, nextcloud…

Have a look at issue https://gitlab.nic.cz/turris/turris-os-packages/-/issues/344 and I guess you already saw https://docs.turris.cz/geek/tos3-migration/ .

The symptoms you describe really look like the config of the switch chip was not migrated correctly. Did you have any kind of custom configuration of the switch chip or VLANs?

Also, when you run the sytem from an mSATA drive, the reset button doesn’t work at all (except the single-press for reboot). That is documented here: https://doc.turris.cz/doc/en/howto/omnia_booting_from_external_storage#problems_ahead .

Some time ago I created configuration for “NordVPN” access. There are 2 VLAN’s with ID 1 (Port 0-3 & CPU all untagged) and ID 2 (Port 4 & 6 both untagged) which results in eth0.1 and eth0.2

There is also a tun0 interface named “NordVPN” and in the pysical entries I see that there’s also some interface “teql0”.

I don’t know it this causes problems but I could remove all of this additional VLANs and interfaces if you think it causes the migration to fail.

You think then it would be successful?

Another thing which I’ve added through commandline is a “3G” and a “NCM” interface for wireless sticks as fallback if wan is down. Could they also interfere with the switch migration or is it mainly the VLANs which are messing things up?

I’m not sure how you managed to upgrade to TOS 5.3. If you kicked off the upgrade through Foris then it should use the hbs branch which currently equals TOS 5.1.4, if I’m not mistaken. TOS 5.3 is an unstable development version.

1 Like

Well that’s even more interesting question then as I did the update through Foris. And if I’m not completely mistaken when I was logging in through serial console it said on the welcome logo TOS 5.3

So why is Foris updating to 5.3 instead of 5.1.4 and I did not mess up with the updater afaik or how can I check if I have the stable branch? But even then would Foris update to some unstable branch depending on updater settings?

There is no setting on Foris to upgrade to unstable versions. Foris updates to the next version of the branch you are on. Example, if you are on the test branch, it will update to the next test branch, if you are on that developer, it will update on that one, if you are on the stable, it will update on the stable. The way to switch between branches is via the command line only. Please make sure:
of the version it came from and the version you switched to by updating from Foris.

The output of cat /etc/turris-version should help clarify which version you have installed. If it’s not TOS 5.3 (which I assume) please update your posts accordingly.

@lucenera The way to switch between branches is via the command line only. Please make sure:
of the version it came from and the version you switched to by updating from Foris.

Just to be sure that I’m not on the wrong branch I googled and executed the command ‘switch-branch deploy’ but it was already on deploy I could see from the ‘sed’ output.

@dhopfm The output of cat /etc/turris-version should help clarify which version you have installed. If it’s not TOS 5.3 (which I assume) please update your posts accordingly.

Of course it does not as I had to revert with schnapps as the update to 5.x failed completely making the router unusable and inaccessible, so atm I’m back on 3.11.21 trying to figure out how to safely update on next try. And actually I don’t care what the current version number of the stable branch is, I though I have seen 5.3, maybe I’m wrong.

The point is the update from stable branch from 3.11.21 to 5.x through foris failed. That’s the point of this thread and how to overcome this problem especially if other people have the same issues.

I will probably try to remove all VLAN stuff and special interfaces that I created back then for NordVPN, I guess that could fix the migration failure (switch config not properly updated)

That’s weird, I haven’t heard about ‘deploy’ branch. You should be on branch called hbs (Here-be-snails, Stable).

This is the procedure for Turris 3.x.

How and why to test Turris OS

Ah, forgot that already :slight_smile: Thanks for pointing that out.

Ok, I did another try. So I first removed all openvpn & tun0 related stuff from NordVPN. Then I thought let’s now try with cleaned up config on emmc first. So I created medkit, flashed it with 4 LED option to internal emmc and then switched with fw_setenv -s boot_emmc.

This worked like a charm and so I started the TOS 5.1.4 (yes it’s actually 5.1.3 not 5.3 sorry for the confusion there) and migration worked perfectly. Had 1-2 small glithes in luci with wifi networks and /etc/fw_config.env beeing erased but that was quickly repaired.

So I thought ok, if the cleanup of my tun0 interface and openvpn did the trick let’s do the exactly same thing when booting from ssd.

But now is where the trouble really begins! It again fucked up the migration of the switch. So currently my 5.1.4 on external ssd still again has no eth0 and you cannot connect to it therefore.

I backup the output of the boot_process from serial console which looks like this jand as you can see there is errors loading firmwares which I don’t get. This is now really beyound my scope:

U-Boot SPL 2015.10-rc2 (Aug 18 2016 - 20:43:35)
High speed PHY - Version: 2.0
SERDES0 card detect: SATA

Initialize Turris board topology
Detected Device ID 6820
board SerDes lanes topology details:
 | Lane #  | Speed |  Type       |
 --------------------------------
 |   0    |  6   |  SATA0       |
 |   1    |  5   |  USB3 HOST0  |
 |   2    |  5   |  PCIe1       |
 |   3    |  5   |  USB3 HOST1  |
 |   4    |  5   |  PCIe2       |
 |   5    |  0   |  SGMII2      |
 --------------------------------
poll_op_execute: TIMEOUT
:** Link is Gen1, check the EP capability
PCIe, Idx 2: remains Gen1
High speed PHY - Ended Successfully
DDR3 Training Sequence - Ver TIP-1.29.0
Memory config in EEPROM: 0x02
DDR3 Training Sequence - Switching XBAR Window to FastPath Window
DDR3 Training Sequence - Ended Successfully


U-Boot 2015.10-rc2 (Aug 18 2016 - 20:43:35 +0200), Build:
jenkins-omnia-master-2
           3

SoC:   MV88F6820-A0
       Watchdog enabled
I2C:   ready
SPI:   ready
DRAM:  2 GiB (ECC not enabled)
Enabling Armada 385 watchdog.
Disabling MCU startup watchdog.
Regdomain set to **
MMC:   mv_sdh: 0
SF: Detected S25FL164K with page size 256 Bytes, erase size 64 KiB,
total 8 MiB
PCI:
  00:01.0     - 168c:0040 - Network controller
PCI:
  01:00.0     - 11ab:6820 - Memory controller
  01:01.0     - 168c:002e - Network controller
Model: Marvell Armada 385 GP
Board: Turris Omnia SN: 0000000B0000F2FD
Regdomain set to **
SCSI:  MVEBU SATA INIT
Target spinup took 0 ms.
SATA link 1 timeout.
AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
flags: 64bit ncq led only pmp fbss pio slum part sxs
Net:   neta2
Hit any key to stop autoboot:  0
Setting bus to 1
BOOT eMMC FS
scanning bus for devices...
  Device 0: (0:0) Vendor: ATA Prod.: KINGSTON SMS200S Rev: 60AA
            Type: Hard Disk
            Capacity: 114473.4 MB = 111.7 GB (234441648 x 512)
Found 1 device(s).
BtrFS init: Max node or leaf size 16384
3349336 bytes read in 134 ms (23.8 MiB/s)
BtrFS init: Max node or leaf size 16384
18773 bytes read in 108 ms (168.9 KiB/s)
Kernel image @ 0x1000000 [ 0x000000 - 0x331b58 ]
## Flattened Device Tree blob at 02000000
   Booting using the fdt blob at 0x2000000
   Loading Device Tree to 0fff8000, end 0ffff954 ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.14.206 (packaging@turris.cz) (gcc version
7.5.0 (
OpenWrt GCC 7.5.0 589c3cf)) #0 SMP Fri Nov 13 04:11:07 2020
[    0.000000] CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7),
cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing
instructio
n cache
[    0.000000] OF: fdt: Machine model: Turris Omnia
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] random: get_random_bytes called from
start_kernel+0x8c/0x4cc with
                  crng_init=0
[    0.000000] percpu: Embedded 11 pages/cpu s15372 r8192 d21492 u45056
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 522560
[    0.000000] Kernel command line: earlyprintk console=ttyS0,115200
rootfstype=
btrfs rootwait root=/dev/sda1 rootflags=subvol=@,commit=5 rw
cfg80211.freg=**
[    0.000000] Bootloader command line not present
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288
bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144
bytes)
[    0.000000] Memory: 2066968K/2097152K available (7168K kernel code,
239K rwda
ta, 1676K rodata, 1024K init, 257K bss, 30184K reserved, 0K
cma-reserved, 131072
         0K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xf0800000 - 0xff800000   ( 240 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xf0000000   ( 768 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc0800000   (8160 kB)
[    0.000000]       .init : 0xc0a00000 - 0xc0b00000   (1024 kB)
[    0.000000]       .data : 0xc0b00000 - 0xc0b3bc00   ( 239 kB)
[    0.000000]        .bss : 0xc0b3bc00 - 0xc0b7c3d8   ( 258 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000]  RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[    0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] L2C: DT/platform modifies aux control register:
0x06070000 -> 0x1
      6070000
[    0.000000] L2C-310 enabling early BRESP for Cortex-A9
[    0.000000] L2C-310 full line of zeros enabled for Cortex-A9
[    0.000000] L2C-310 D prefetch enabled, offset 1 lines
[    0.000000] L2C-310 dynamic clock gating enabled, standby mode enabled
[    0.000000] L2C-310 Coherent cache controller enabled, 16 ways, 1024 kB
[    0.000000] L2C-310 Coherent: CACHE_ID 0x410054c9, AUX_CTRL 0x56070001
[    0.000006] sched_clock: 64 bits at 800MHz, resolution 1ns, wraps
every 43980
46511103ns
[    0.000016] clocksource: arm_global_timer: mask: 0xffffffffffffffff
max_cycle
s: 0xb881274fa3, max_idle_ns: 440795210636 ns
[    0.000029] Switching to timer-based delay loop, resolution 1ns
[    0.000159] Ignoring duplicate/late registration of
read_current_timer delay
[    0.000166] clocksource: armada_370_xp_clocksource: mask: 0xffffffff
max_cycl
es: 0xffffffff, max_idle_ns: 76450417870 ns
[    0.000335] Console: colour dummy device 80x30
[    0.000353] Calibrating delay loop (skipped), value calculated using
timer fr
equency.. 1600.00 BogoMIPS (lpj=8000000)
[    0.000360] pid_max: default: 32768 minimum: 301
[    0.000421] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000426] Mountpoint-cache hash table entries: 2048 (order: 1, 8192
bytes)
[    0.000708] CPU: Testing write buffer coherency: ok
[    0.000720] CPU0: Spectre v2: using BPIALL workaround
[    0.000840] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.000970] Setting up static identity map for 0x100000 - 0x100060
[    0.001046] mvebu-soc-id: MVEBU SoC ID=0x6820, Rev=0x4
[    0.001124] mvebu-pmsu: Initializing Power Management Service Unit
[    0.001175] Hierarchical SRCU implementation.
[    0.001370] smp: Bringing up secondary CPUs ...
[    0.001504] Booting CPU 1
[    0.001660] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.001663] CPU1: Spectre v2: using BPIALL workaround
[    0.001713] smp: Brought up 1 node, 2 CPUs
[    0.001718] SMP: Total of 2 processors activated (3200.00 BogoMIPS).
[    0.001721] CPU: All CPU(s) started in SVC mode.
[    0.002258] devtmpfs: initialized
[    0.003867] VFP support v0.3: implementor 41 architecture 3 part 30
variant 9
rev 4
[    0.003923] clocksource: jiffies: mask: 0xffffffff max_cycles:
0xffffffff, ma
   x_idle_ns: 19112604462750000 ns
[    0.003931] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.003998] xor: measuring software checksum speed
[    0.100067]    arm4regs  :  2392.000 MB/sec
[    0.200067]    8regs     :  1861.600 MB/sec
[    0.300065]    32regs    :  2047.600 MB/sec
[    0.400066]    neon      :  1837.200 MB/sec
[    0.400070] xor: using function: arm4regs (2392.000 MB/sec)
[    0.400076] pinctrl core: initialized pinctrl subsystem
[    0.400445] NET: Registered protocol family 16
[    0.400952] DMA: preallocated 256 KiB pool for atomic coherent
allocations
[    0.401502] cpuidle: using governor ladder
[    0.401595] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1
watchpoint
registers.
[    0.401599] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.401722] mvebu-pmsu: CPU hotplug support is currently broken on
Armada 38x
: disabling
[    0.401728] mvebu-pmsu: CPU idle is currently broken on Armada 38x:
disabling
[    0.570265] raid6: int32x1  gen()   171 MB/s
[    0.740169] raid6: int32x1  xor()   243 MB/s
[    0.910170] raid6: int32x2  gen()   255 MB/s
[    1.080084] raid6: int32x2  xor()   290 MB/s
[    1.250249] raid6: int32x4  gen()   304 MB/s
[    1.420082] raid6: int32x4  xor()   252 MB/s
[    1.590138] raid6: int32x8  gen()   328 MB/s
[    1.760114] raid6: int32x8  xor()   229 MB/s
[    1.930101] raid6: neonx1   gen()  1111 MB/s
[    2.100090] raid6: neonx1   xor()  1058 MB/s
[    2.270094] raid6: neonx2   gen()  1303 MB/s
[    2.440070] raid6: neonx2   xor()  1351 MB/s
[    2.610094] raid6: neonx4   gen()  1070 MB/s
[    2.780078] raid6: neonx4   xor()  1328 MB/s
[    2.950105] raid6: neonx8   gen()  1014 MB/s
[    3.120071] raid6: neonx8   xor()   914 MB/s
[    3.120074] raid6: using algorithm neonx2 gen() 1303 MB/s
[    3.120077] raid6: .... xor() 1351 MB/s, rmw enabled
[    3.120080] raid6: using neon recovery algorithm
[    3.120371] SCSI subsystem initialized
[    3.120587] usbcore: registered new interface driver usbfs
[    3.120617] usbcore: registered new interface driver hub
[    3.120646] usbcore: registered new device driver usb
[    3.121318] clocksource: Switched to clocksource arm_global_timer
[    3.125223] NET: Registered protocol family 2
[    3.125491] TCP established hash table entries: 8192 (order: 3, 32768
bytes)
[    3.125529] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    3.125590] TCP: Hash tables configured (established 8192 bind 8192)
[    3.125637] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    3.125663] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    3.125758] NET: Registered protocol family 1
[    3.126090] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7
counter                                                              s
available
[    3.127072] Crashlog allocated RAM at address 0x3f00000
[    3.127198] workingset: timestamp_bits=14 max_order=19 bucket_order=5
[    3.129130] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    3.129140] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME)
(CMODE_PRIORIT
   Y) (c) 2001-2006 Red Hat, Inc.
[    3.130860] bounce: pool size: 64 pages
[    3.130870] io scheduler noop registered
[    3.130874] io scheduler deadline registered (default)
[    3.131378] armada-38x-pinctrl f1018000.pinctrl: registered pinctrl
driver
[    3.132706] mvebu-pcie soc:pcie: PCI host bridge to bus 0000:00
[    3.132719] pci_bus 0000:00: root bus resource [io  0x1000-0xfffff]
[    3.132724] pci_bus 0000:00: root bus resource [mem
0xe0000000-0xe7ffffff]
[    3.132729] pci_bus 0000:00: root bus resource [bus 00-ff]
[    3.132979] PCI: bus0: Fast back to back transfers disabled
[    3.132987] pci 0000:00:01.0: bridge configuration invalid ([bus
00-00]), rec
 onfiguring
[    3.132994] pci 0000:00:02.0: bridge configuration invalid ([bus
00-00]), rec
 onfiguring
[    3.132999] pci 0000:00:03.0: bridge configuration invalid ([bus
00-00]), rec
 onfiguring
[    3.133034] PCI: bus1: Fast back to back transfers enabled
[    3.133235] PCI: bus2: Fast back to back transfers disabled
[    3.133469] PCI: bus3: Fast back to back transfers disabled
[    3.133495] pci 0000:00:02.0: BAR 8: assigned [mem 0xe0000000-0xe01fffff]
[    3.133501] pci 0000:00:03.0: BAR 8: assigned [mem 0xe0200000-0xe02fffff]
[    3.133506] pci 0000:00:01.0: PCI bridge to [bus 01]
[    3.133516] pci 0000:02:00.0: BAR 0: assigned [mem
0xe0000000-0xe01fffff 64bi
               t]
[    3.133525] pci 0000:00:02.0: PCI bridge to [bus 02]
[    3.133530] pci 0000:00:02.0:   bridge window [mem 0xe0000000-0xe01fffff]
[    3.133537] pci 0000:03:00.0: BAR 0: assigned [mem
0xe0200000-0xe020ffff 64bi
               t]
[    3.133546] pci 0000:00:03.0: PCI bridge to [bus 03]
[    3.133551] pci 0000:00:03.0:   bridge window [mem 0xe0200000-0xe02fffff]
[    3.133787] mv_xor f1060800.xor: Marvell shared XOR driver
[    3.191779] mv_xor f1060800.xor: Marvell XOR (Descriptor Mode): ( xor
cpy int                                                              r )
[    3.191902] mv_xor f1060900.xor: Marvell shared XOR driver
[    3.251757] mv_xor f1060900.xor: Marvell XOR (Descriptor Mode): ( xor
cpy int                                                              r )
[    3.251982] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[    3.253145] console [ttyS0] disabled
[    3.273216] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 22,
base_baud =
 15625000) is a 16550A
[    4.151364] console [ttyS0] enabled
[    4.175114] f1012100.serial: ttyS1 at MMIO 0xf1012100 (irq = 23,
base_baud =
 15625000) is a 16550A
[    4.185929] loop: module loaded
[    4.189391] ahci-mvebu f10a8000.sata: AHCI 0001.0000 32 slots 2 ports
6 Gbps                                                               0x3
impl platform mode
[    4.198480] ahci-mvebu f10a8000.sata: flags: 64bit ncq sntf led only
pmp fbs
pio slum part sxs
[    4.207644] scsi host0: ahci-mvebu
[    4.211191] scsi host1: ahci-mvebu
[    4.214675] ata1: SATA max UDMA/133 mmio [mem 0xf10a8000-0xf10a9fff]
port 0x1                                                              00
irq 44
[    4.222620] ata2: SATA max UDMA/133 mmio [mem 0xf10a8000-0xf10a9fff]
port 0x1                                                              80
irq 44
[    4.231360] m25p80 spi0.0: s25fl164k (8192 Kbytes)
[    4.236233] 2 fixed-partitions partitions found on MTD device spi0.0
[    4.242619] Creating 2 MTD partitions on "spi0.0":
[    4.247421] 0x000000000000-0x000000100000 : "U-Boot"
[    4.252729] 0x000000100000-0x000000800000 : "Rescue system"
[    4.258781] libphy: Fixed MDIO Bus: probed
[    4.263228] libphy: orion_mdio_bus: probed
[    4.267838] mv88e6085 f1072004.mdio-mii:10: switch 0x1760 detected:
Marvell 8
8E6176, revision 1
[    4.419503] libphy: mv88e6xxx SMI: probed
[    4.427319] mvneta f1070000.ethernet eth0: Using hardware mac address
d8:58:d
7:00:5c:d5
[    4.436087] mvneta f1030000.ethernet eth1: Using hardware mac address
d8:58:d
7:00:5c:d3
[    4.444784] mvneta f1034000.ethernet eth2: Using hardware mac address
d8:58:d
7:00:5c:d4
[    4.452969] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    4.459513] ehci-pci: EHCI PCI platform driver
[    4.464001] ehci-platform: EHCI generic platform driver
[    4.469302] ehci-orion: EHCI orion driver
[    4.473418] orion-ehci f1058000.usb: EHCI Host Controller
[    4.478839] orion-ehci f1058000.usb: new USB bus registered, assigned
bus num                                                              ber 1
[    4.486479] orion-ehci f1058000.usb: irq 40, io mem 0xf1058000
[    4.521323] orion-ehci f1058000.usb: USB 2.0 started, EHCI 1.00
[    4.527545] hub 1-0:1.0: USB hub found
[    4.531330] hub 1-0:1.0: 1 port detected
[    4.535613] xhci-hcd f10f0000.usb3: xHCI Host Controller
[    4.540945] xhci-hcd f10f0000.usb3: new USB bus registered, assigned
bus numb                                                              er 2
[    4.548515] xhci-hcd f10f0000.usb3: hcc params 0x0a000990 hci version
0x100 q
uirks 0x0000000000010010
[    4.557784] xhci-hcd f10f0000.usb3: irq 46, io mem 0xf10f0000
[    4.563785] hub 2-0:1.0: USB hub found
[    4.567511] ata2: SATA link down (SStatus 0 SControl 300)
[    4.567557] hub 2-0:1.0: 1 port detected
[    4.576994] xhci-hcd f10f0000.usb3: xHCI Host Controller
[    4.582331] xhci-hcd f10f0000.usb3: new USB bus registered, assigned
bus numb                                                              er 3
[    4.589839] xhci-hcd f10f0000.usb3: Host supports USB 3.0  SuperSpeed
[    4.596334] usb usb3: We don't know the algorithms for LPM for this
host, dis
abling LPM.
[    4.604654] hub 3-0:1.0: USB hub found
[    4.608424] hub 3-0:1.0: 1 port detected
[    4.612526] xhci-hcd f10f8000.usb3: xHCI Host Controller
[    4.617857] xhci-hcd f10f8000.usb3: new USB bus registered, assigned
bus numb                                                              er 4
[    4.625415] xhci-hcd f10f8000.usb3: hcc params 0x0a000990 hci version
0x100 q
uirks 0x0000000000010010
[    4.634681] xhci-hcd f10f8000.usb3: irq 47, io mem 0xf10f8000
[    4.640660] hub 4-0:1.0: USB hub found
[    4.644459] hub 4-0:1.0: 1 port detected
[    4.648487] xhci-hcd f10f8000.usb3: xHCI Host Controller
[    4.653827] xhci-hcd f10f8000.usb3: new USB bus registered, assigned
bus numb                                                              er 5
[    4.661338] xhci-hcd f10f8000.usb3: Host supports USB 3.0  SuperSpeed
[    4.667831] usb usb5: We don't know the algorithms for LPM for this
host, dis
abling LPM.
[    4.676140] hub 5-0:1.0: USB hub found
[    4.679910] hub 5-0:1.0: 1 port detected
[    4.684059] usbcore: registered new interface driver usb-storage
[    4.690503] armada38x-rtc f10a3800.rtc: registered as rtc0
[    4.696143] i2c /dev entries driver
[    4.710134] (NULL device *): hwmon_device_register() is deprecated.
Please co
nvert the driver to use hwmon_device_register_with_info().
[    4.722617] orion_wdt: Initial timeout 171 sec
[    4.727325] sdhci: Secure Digital Host Controller Interface driver
[    4.733531] sdhci: Copyright(c) Pierre Ossman
[    4.741340] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    4.754549] ata1.00: ATA-8: KINGSTON SMS200S3120G, 60AABBF0, max UDMA/133
[    4.761416] ata1.00: 234441648 sectors, multi 1: LBA48 NCQ (depth 31/32)
[    4.773091] ata1.00: configured for UDMA/133
[    4.777550] scsi 0:0:0:0: Direct-Access     ATA      KINGSTON SMS200S
BBF0 PQ                                                              : 0
ANSI: 5
[    4.786108] sd 0:0:0:0: [sda] 234441648 512-byte logical blocks: (120
GB/112                                                               GiB)
[    4.793655] sd 0:0:0:0: [sda] Write Protect is off
[    4.798493] sd 0:0:0:0: [sda] Write cache: enabled, read cache:
enabled, does
  n't support DPO or FUA
[    4.801320] mmc0: SDHCI controller on f10d8000.sdhci [f10d8000.sdhci]
using A                                                              DMA
[    4.815015]  sda: sda1 sda2 sda3
[    4.815089] sdhci-pltfm: SDHCI platform and OF driver helper
[    4.818737] sd 0:0:0:0: [sda] Attached SCSI removable disk
[    4.830035] marvell-cesa f1090000.crypto: CESA device successfully
registered
[    4.837675] NET: Registered protocol family 10
[    4.842712] Segment Routing with IPv6
[    4.846410] NET: Registered protocol family 17
[    4.850878] bridge: filtering via arp/ip/ip6tables is no longer
available by
  default. Update your scripts to load br_netfilter if you need this.
[    4.864085] 8021q: 802.1Q VLAN Support v1.8
[    4.868357] Registering SWP/SWPB emulation handler
[    4.877532] Btrfs loaded, crc32c=crc32c-generic
[    4.883006] mv88e6085 f1072004.mdio-mii:10: switch 0x1760 detected:
Marvell 8
8E6176, revision 1
[    4.977981] mmc0: new high speed MMC card at address 0001
[    4.983558] mmcblk0: mmc0:0001 H8G4a▒ 7.28 GiB
[    4.988177] mmcblk0boot0: mmc0:0001 H8G4a▒ partition 1 4.00 MiB
[    4.994189] mmcblk0boot1: mmc0:0001 H8G4a▒ partition 2 4.00 MiB
[    5.000180] mmcblk0rpmb: mmc0:0001 H8G4a▒ partition 3 4.00 MiB,
chardev (250:
  0)
[    5.008834]  mmcblk0: p1
[    5.011436] usb 4-1: new high-speed USB device number 2 using xhci-hcd
[    5.080906] libphy: mv88e6xxx SMI: probed
[    5.084989] DSA: switch 0 0 parsed
[    5.088403] DSA: tree 0 parsed
[    5.192963] usb-storage 4-1:1.0: USB Mass Storage device detected
[    5.199197] scsi host2: usb-storage 4-1:1.0
[    5.795414] mv88e6085 f1072004.mdio-mii:10 lan0 (uninitialized): PHY
[mv88e6x
xx-1:00] driver [Marvell 88E1540]
[    5.917650] mv88e6085 f1072004.mdio-mii:10 lan1 (uninitialized): PHY
[mv88e6x
xx-1:01] driver [Marvell 88E1540]
[    6.035416] mv88e6085 f1072004.mdio-mii:10 lan2 (uninitialized): PHY
[mv88e6x
xx-1:02] driver [Marvell 88E1540]
[    6.155420] mv88e6085 f1072004.mdio-mii:10 lan3 (uninitialized): PHY
[mv88e6x
xx-1:03] driver [Marvell 88E1540]
[    6.231890] scsi 2:0:0:0: Direct-Access     Corsair  Voyager Mini
0.00 PQ                                                              : 0
ANSI: 2
[    6.240950] sd 2:0:0:0: [sdb] 31582352 512-byte logical blocks: (16.2
GB/15.1                                                               GiB)
[    6.248800] sd 2:0:0:0: [sdb] Write Protect is off
[    6.253861] sd 2:0:0:0: [sdb] Asking for cache data failed
[    6.259360] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[    6.277674] mv88e6085 f1072004.mdio-mii:10 lan4 (uninitialized): PHY
[mv88e6x
xx-1:04] driver [Marvell 88E1540]
[    6.297942] armada38x-rtc f10a3800.rtc: setting system clock to
2021-01-03 17
  :31:27 UTC (1609695087)
[    6.697954]  sdb: sdb1
[    7.276027] sd 2:0:0:0: [sdb] Attached SCSI removable disk
[    7.287994] F2FS-fs (sda1): Magic Mismatch, valid(0xf2f52010) - read(0x0)
[    7.294814] F2FS-fs (sda1): Can't find valid F2FS filesystem in 1th
superbloc                                                              k
[    7.302175] F2FS-fs (sda1): Magic Mismatch, valid(0xf2f52010) - read(0x0)
[    7.308978] F2FS-fs (sda1): Can't find valid F2FS filesystem in 2th
superbloc                                                              k
[    7.316230] F2FS-fs (sda1): Magic Mismatch, valid(0xf2f52010) - read(0x0)
[    7.323044] F2FS-fs (sda1): Can't find valid F2FS filesystem in 1th
superbloc                                                              k
[    7.330282] F2FS-fs (sda1): Magic Mismatch, valid(0xf2f52010) - read(0x0)
[    7.337089] F2FS-fs (sda1): Can't find valid F2FS filesystem in 2th
superbloc                                                              k
[    7.344786] BTRFS: device fsid f80a2b71-e64c-4b82-8663-338426af3b3d
devid 1 t
ransid 31350 /dev/root
[    7.354218] BTRFS info (device sda1): disk space caching is enabled
[    7.360501] BTRFS info (device sda1): has skinny extents
[    7.375802] BTRFS info (device sda1): enabling ssd optimizations
[    7.385979] VFS: Mounted root (btrfs filesystem) on device 0:12.
[    7.392641] devtmpfs: mounted
[    7.396185] Freeing unused kernel memory: 1024K
[    7.454645] init: Console is alive
[    7.458114] init: - watchdog -
[    7.489426] random: fast init done
[    7.538818] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[    7.548995] usbcore: registered new interface driver uas
[    7.554402] kmodloader: done loading kernel modules from
/etc/modules-boot.d/
         *
[    7.564251] init: - preinit -
[    7.625133] random: jshn: uninitialized urandom read (4 bytes read)
[    7.642266] random: jshn: uninitialized urandom read (4 bytes read)
ls: /sys/bus/pci/devices/0000:00:01.0/000*/iee*/phy*: No such file or
directory
ls: /sys/bus/pci/devices/0000:00:02.0/000*/iee*/phy*: No such f[
7.674615] ra
 ndom: jshn: uninitialized urandom read (4 bytes read)
ile or directory
ls: /sys/bus/pci/devices/0000:00:03.0/000*/iee*/phy*: No such file or
directory
RTNETLINK answers: Network is down
sendto(): Network unreachable
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
[   10.772934] mount_root: mounting /dev/root
[   10.777522] BTRFS info (device sda1): disk space caching is enabled
Failed to find nls_cp437. Maybe it is a built in module ?
Failed to find nls_iso8859-1. Maybe it is a built in module ?
Failed to find fat. Maybe it is a built in module ?
Failed to find vfat. Maybe it is a built in module ?
Log: api: open_ni2c_dev: Couldn't open native I2C device.
Device couldn't be opened.
Log: api: open_ni2c_dev: Couldn't open native I2C device.
Device couldn't be opened.
Log: api: open_ni2c_dev: Couldn't open native I2C device.
Device couldn't be opened.
Log: api: open_ni2c_dev: Couldn't open native I2C device.
Device couldn't be opened.
Log: api: open_ni2c_dev: Couldn't open native I2C device.
Device couldn't be opened.
Log: api: open_ni2c_dev: Couldn't open native I2C device.
Device couldn't be opened.
Log: api: open_ni2c_dev: Couldn't open native I2C device.
Device couldn't be opened.
Log: api: open_ni2c_dev: Couldn't open native I2C device.
Device couldn't be opened.
Log: api: open_ni2c_dev: Couldn't open native I2C device.
Device couldn't be opened.
Log: api: open_ni2c_dev: Couldn't open native I2C device.
Device couldn't be opened.
Log: api: open_ni2c_dev: Couldn't open native I2C device.
Device couldn't be opened.
Log: api: open_ni2c_dev: Couldn't open native I2C device.
Device couldn't be opened.
Log: api: open_ni2c_dev: Couldn't open native I2C device.
Device couldn't be opened.
Log: api: open_ni2c_dev: Couldn't open native I2C device.
Device couldn't be opened.
Log: api: open_ni2c_dev: Couldn't open native I2C device.
Device couldn't be opened.
Log: api: open_ni2c_dev: Couldn't open native I2C device.
Device couldn't be opened.
Scanning for Btrfs filesystems
[   11.433283] BTRFS: device fsid cbadfbf2-ae27-4c41-97d4-e1ec7ab947d5
devid 1 t
ransid 488 /dev/mmcblk0p1
[   11.442747] BTRFS: device label srv devid 1 transid 104 /dev/sda3
[   11.457484] procd: - early -
[   11.460396] procd: - watchdog -
[   12.077782] procd: - watchdog -
[   12.081035] procd: - ubus -
[   12.087775] urandom_read: 2 callbacks suppressed
[   12.087778] random: ubusd: uninitialized urandom read (4 bytes read)
[   12.134125] random: ubusd: uninitialized urandom read (4 bytes read)
[   12.140634] random: ubusd: uninitialized urandom read (4 bytes read)
[   12.147411] procd: - init -
Please press Enter to activate this console.
[   12.301212] kmodloader: loading kernel modules from /etc/modules.d/*
[   12.313220] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[   12.323170] ip6_tables: (C) 2000-2006 Netfilter Core Team
[   12.333677] Netfilter messages via NETLINK v0.30.
[   12.339246] ip_set: protocol 6
[   12.370746] i2c i2c-0: Added multiplexed i2c bus 1
[   12.376024] i2c i2c-0: Added multiplexed i2c bus 2
[   12.386245] i2c i2c-0: Added multiplexed i2c bus 3
[   12.391599] i2c i2c-0: Added multiplexed i2c bus 4
[   12.405196] i2c i2c-0: Added multiplexed i2c bus 5
[   12.410414] i2c i2c-0: Added multiplexed i2c bus 6
[   12.417228] i2c i2c-0: Added multiplexed i2c bus 7
[   12.422816] pca953x 8-0071: 8-0071 supply vcc not found, using dummy
regulato                                                              r
[   12.441546] i2c i2c-0: Added multiplexed i2c bus 8
[   12.446354] pca954x 0-0070: registered 8 multiplexed busses for I2C
mux pca95                                                              47
[   12.460320] Mirror/redirect action on
[   12.477364] u32 classifier
[   12.480080]     input device check on
[   12.483791]     Actions configured
[   12.490860] sch_cake: Unknown symbol nf_conntrack_find_get (err 0)
[   12.497206] sch_cake: Unknown symbol nf_ct_get_tuplepr (err 0)
[   12.524098] Bridge firewalling registered
[   12.528845] usbcore: registered new interface driver cdc_wdm
[   12.539777] Loading modules backported from Linux version
v4.19.137-0-gc076c7
        9e03c6
[   12.547482] Backport generated by backports.git v4.19.137-1-0-g60c3a249
[   12.558982] Ebtables v2.0 registered
[   12.563835] ip_tables: (C) 2000-2006 Netfilter Core Team
[   12.575019] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[   12.583457] ctnetlink v0.93: registering with nfnetlink.
[   12.590700] random: crng init done
[   12.594163] random: 2 urandom warning(s) missed due to ratelimiting
[   12.605541] usbcore: registered new interface driver ums-alauda
[   12.611946] usbcore: registered new interface driver ums-cypress
[   12.618399] usbcore: registered new interface driver ums-datafab
[   12.624983] usbcore: registered new interface driver ums-freecom
[   12.631374] usbcore: registered new interface driver ums-isd200
[   12.637775] usbcore: registered new interface driver ums-jumpshot
[   12.644531] usbcore: registered new interface driver ums-karma
[   12.650951] usbcore: registered new interface driver ums-sddr09
[   12.657388] usbcore: registered new interface driver ums-sddr55
[   12.663988] usbcore: registered new interface driver ums-usbat
[   12.673177] usbcore: registered new interface driver usbserial
[   12.679081] usbcore: registered new interface driver usbserial_generic
[   12.685692] usbserial: USB Serial support registered for generic
[   12.703195] xt_time: kernel timezone is -0000
[   12.708895] at24 1-0054: 8192 byte 24c64 EEPROM, writable, 1 bytes/write
[   12.716792] usbcore: registered new interface driver cdc_ncm
[   12.734436] usbcore: registered new interface driver huawei_cdc_ncm
[   12.758871] PPP generic driver version 2.4.2
[   12.764022] NET: Registered protocol family 24
[   12.780047] pci 0000:00:02.0: enabling device (0140 -> 0142)
[   12.786095] ath10k_pci 0000:02:00.0: pci irq msi oper_irq_mode 2
irq_mode 0 r
 eset_mode 0
[   12.962726] ath10k_pci 0000:02:00.0: Direct firmware load for
ath10k/pre-cal-
    pci-0000:02:00.0.bin failed with error -2
[   12.973488] ath10k_pci 0000:02:00.0: Falling back to user helper
[   14.806899] firmware ath10k!pre-cal-pci-0000:02:00.0.bin:
firmware_loading_st
        ore: map pages failed
[   14.816015] ath10k_pci 0000:02:00.0: Direct firmware load for
ath10k/cal-pci-
    0000:02:00.0.bin failed with error -2
[   14.826430] ath10k_pci 0000:02:00.0: Falling back to user helper
[   14.837017] firmware ath10k!cal-pci-0000:02:00.0.bin:
firmware_loading_store:
             map pages failed
[   14.845824] ath10k_pci 0000:02:00.0: Direct firmware load for
ath10k/QCA99X0/
    hw2.0/firmware-6.bin failed with error -2
[   14.856565] ath10k_pci 0000:02:00.0: Falling back to user helper
[   14.867097] firmware ath10k!QCA99X0!hw2.0!firmware-6.bin:
firmware_loading_st
        ore: map pages failed
[   14.885870] ath10k_pci 0000:02:00.0: qca99x0 hw2.0 target 0x01000000
chip_id
0x003b01ff sub 168c:0002
[   14.895143] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1
tracing 0 dfs
   1 testmode 1
[   14.905896] ath10k_pci 0000:02:00.0: firmware ver 10.4.1.00030-1 api
5 featur                                                              es
no-p2p crc32 d2901e01
[   16.362757] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id 1:1
crc32 08fa09                                                              f2
[   18.956156] ath10k_pci 0000:02:00.0: htt-ver 2.2 wmi-op 6 htt-op 4
cal otp ma
x-sta 512 raw 0 hwcrypto 1
[   19.061494] usbcore: registered new interface driver option
[   19.067126] usbserial: USB Serial support registered for GSM modem
(1-port)
[   19.076364] usbcore: registered new interface driver qcserial
[   19.082210] usbserial: USB Serial support registered for Qualcomm USB
modem
[   19.095187] pci 0000:00:03.0: enabling device (0140 -> 0142)
[   19.203373] ieee80211 phy1: Atheros AR9287 Rev:2 mem=0xf10e0000, irq=79
[   19.211413] kmodloader: done loading kernel modules from /etc/modules.d/*
Router Turris successfully started.

So now I have 2 questions:

  1. can it easily be fixe by adjusting some paths or something as I left the non-working 5.1.4 on the ssd intact?
  2. if not, will erasing the ssd contents and re-deploying a fresh medkit from emmc solve the problem or will it show the same broken firmware loading issues?

Oh and btw. Upgrading to TOS 5.1.4 kills the file /etc/fw_env.config which I think is a very bad thing cause you have to hunt the forums afterwards to recreate it before you can again switch from emmc to ssd and back.

So any help in fixing those firmware loading errors I would really appreciate as it goes beyound my knowledge. Maybe @vcunat or @Pepe can shed some light here or some other dev that is familiar with boot process and devices initizialisation.

Here’s a quick collection of bugs I’ve found so far after migrating to TOS 5.1.4 from 3.11.26

1.) The KILLER BUG is WAN recv down to ~13MBit, with TOS 3.11.26 it was around 800-900MB. send performance is interestingly ok. It is 100Mbit Upstream with TOS 5.1.4 & 3.11.26. I have checked the Speed on the Network ports but all is set to 1000Mbit LAN & WAN Ports. So why on earth is the downstream so extremly slow. As soon as I switch from TOS 5.1.4 (emmc) to TOS 3.11.26 (sata) performance is back at around 800-900MBit.
2.) wget package not installed so installing new packages failes completely and you have to manually download and install
3.) file /etc/fw_env.config get’s removed if it was present before which kills fw_printenv, fw_setenv etc. commands must be manually recreated

Hope this errors especially downstream is (especially wget) fixed soon and I don’t know why such huge impact errors like extremly slow performance and loosing wget package have gone to hbs branch.

In general I’m a patient man and I’m willing to fix some minor glitches or so if the core functionality is at least working.

But for the moment I’m done with 5.1.4 and 5.x in general. Before there is no feedback from the devs that these major fuck ups like 13 ~mbit downstream after migration are fixed I will not contribute at all to this anymore. I’ve now spent 2 full days trying to get 5.1.4 working without much success and now it’s enough. My last 2 Sundays were literally wasted with this and I’m again back at 3.11.26.

Unfortunately it seems that the migration is still completely broken, really badly. Might be that a fresh 5.1.4 is running fine, but I will not try. I wasted enough time and my wife is already complaining.

You want to enable migration soon you’re saying in the sticky? Atm the only thing I can say is: test this really really thoroughly. If most people are experiencing problems like I have, then you can expect a shit storm here in the forums.

@marcerlser I completely understand your frustration. But please understand you asked this question on 30 Dec. Most people take vacations in this time. So it’s not that the admins would not want to look into your issue, it is that you asked it at the wrong time… I guess somebody will pop up here with some ideas in a few days.

The problem with WAN speed has to be something specific for your installation. My WAN (pppoe) worked without a glitch after upgrade. To help you more, you need to post here your /etc/config/network from 3.x and after migration (don’t forget to redact credentials), and maybe tell us a bit more about how you are connected. Didn’t the failover wireless sticks somehow kick in for download?

Regarding the firmware load errors - they’re pretty much okay, nothing to worry about. I see them too on my 5.x Omnia and wireless works okay.

here are the configs. I think they are similar except that wan is now eth2 and switch configs are missing:

here’s network config from 3.11.26

config interface 'loopback'
        option ifname 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'fda6:7fef:b222::/48'

config interface 'lan'
        option ifname 'eth0 eth2'
        option force_link '1'
        option type 'bridge'
        option proto 'static'
        option netmask '255.255.255.0'
        option ip6assign '60'
        option ipaddr '192.168.10.1'

config interface 'wan'
        option ifname 'eth1'
        option proto 'dhcp'
        option metric '10'
        option peerdns '0'
        option hostname 'turris'
        option ipv6 '1'
        option dns '8.8.8.8 8.8.4.4'

config interface 'wan6'
        option ifname '@wan'
        option noserverunicast '1'
        option proto '6to4'

config switch
        option name 'switch0'
        option reset '1'
        option enable_vlan '1'

config switch_vlan
        option device 'switch0'
        option vlan '1'
        option ports '0 1 2 3 5'

config switch_vlan
        option device 'switch0'
        option vlan '2'
        option ports '4 6'

config interface 'guest_turris'
        option enabled '1'
        option type 'bridge'
        option ifname 'guest_turris_0 guest_turris_1'
        option proto 'static'
        option ipaddr '10.111.222.1'
        option netmask '255.255.255.0'
        option bridge_empty '1'

config interface 'ncm'
        option proto 'ncm'
        option apn 'gprs.swisscom.ch'
        option metric '20'
        option username 'gprs'
        option password 'gprs'
        option device '/dev/cdc-wdm0'
        option ipv6 '0'
        option peerdns '0'
        option auto '0'

config interface '3g'
        option proto '3g'
        option apn 'gprs.swisscom.ch'
        option metric '20'
        option username 'gprs'
        option password 'gprs'
        option service 'umts'
        option device '/dev/ttyUSB0'
        option ipv6 '0'
        option maxwait '60'
        option peerdns '0'
        option dns '54.93.173.153 81.17.17.170'
        option enabled '0'
        option auto '0'

and here’s the config from 5.1.4

config interface 'loopback'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'
        option ifname 'lo'

config globals 'globals'
        option ula_prefix 'fda6:7fef:b222::/48'

config interface 'lan'
        option force_link '1'
        option type 'bridge'
        option proto 'static'
        option netmask '255.255.255.0'
        option ip6assign '60'
        option ipaddr '192.168.10.1'
        list ifname 'lan0'
        list ifname 'lan1'
        list ifname 'lan2'
        list ifname 'lan3'
        list ifname 'lan4'

config interface 'wan'
        option proto 'dhcp'
        option metric '10'
        option peerdns '0'
        option hostname 'turris'
        option ipv6 '1'
        option dns '8.8.8.8 8.8.4.4'
        option ifname 'eth2'

config interface 'wan6'
        option noserverunicast '1'
        option proto '6to4'
        option ifname '@wan'

config interface 'guest_turris'
        option enabled '1'
        option type 'bridge'
        option proto 'static'
        option ipaddr '10.111.222.1'
        option netmask '255.255.255.0'
        option bridge_empty '1'
        list ifname 'guest_turris_0'
        list ifname 'guest_turris_1'

config interface 'ncm'
        option proto 'ncm'
        option apn 'gprs.swisscom.ch'
        option metric '20'
        option username 'gprs'
        option password 'gprs'
        option device '/dev/cdc-wdm0'
        option ipv6 '0'
        option peerdns '0'
        option auto '0'
        option ifname '/dev/cdc-wdm0'

config interface '3g'
        option proto '3g'
        option apn 'gprs.swisscom.ch'
        option metric '20'
        option username 'gprs'
        option password 'gprs'
        option service 'umts'
        option device '/dev/ttyUSB0'
        option ipv6 '0'
        option maxwait '60'
        option peerdns '0'
        option dns '54.93.173.153 81.17.17.170'
        option enabled '0'
        option auto '0'
        option ifname '/dev/ttyUSB0'

And this time I pulled out the 3G stick and WAN connection is still just 14Mbps. So still totally screwed up.

Any help here would be greatly appreciated if I can at least solve this totally screwed wan port then I could at least start to us Turris OS 5.x but without fixing this it’s totally impossible.

BTW: Here also a small output from ethtool for eth2

Settings for eth2:
        Supported ports: [ TP MII FIBRE ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supported pause frame use: Symmetric
        Supports auto-negotiation: Yes
        Supported FEC modes: Not reported
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised pause frame use: Symmetric
        Advertised auto-negotiation: Yes
        Advertised FEC modes: Not reported
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
                                             1000baseT/Full
        Link partner advertised pause frame use: Symmetric Receive-only
        Link partner advertised auto-negotiation: Yes
        Link partner advertised FEC modes: Not reported
        Speed: 1000Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: g
        Wake-on: d
        Link detected: yes

I don’t see anything weird there. I guess it’s time to collect logs on 5.1 and send them over to the support email.

I opened a support ticket for this case. Meanwhile I found out that actually it’s not the WAN port itself. When you run a speedtest on the router itself it maxes out as expected. And also interesting the LAN4 Port which is not attached to the switch also gives full speed.

So it’s the switch that’s actually broken in some way. I checked the switch ports lan 0-3 in foris and with ethtool and also eth0 but all are set to 1000Mbps. So I don’t see any reason for this behaviour.

If I have time I might try to import an official 5.1.4 medkit and start from scratch and see if the switch behaves normally when it’s not migrated from 3.11.26.

But after asking a few questions I also don’t get any response anymore on this topic.

It very much depends on how you do this test. In most cases, the kernel will short-circuit the data path to loopback (even if the interfaces are in different subnets or whatever). The only way I was able to test port-to-port communication on the same computer without this short-circuit was to connect the ports via a cable and use network namespaces (but I think that’s a thing using nmcli on Ubuntu, not sure it’s possible with Turris OS).