Need a New Kernel > 4.4.0 and New Regulatory wifi!

[jbsky]

Improve stabilty and this next message disappear:
ieee80211 phy1: check ba result error 1
[17730.156783] ieee80211 phy1: ampdu start error code: -22
I followed this tuto, changed my regulator, now wifi is stable with iphone, no delay latency! Maybe thank to DFS.
country FR: DFS-ETSI
(2402 - 2482 @ 40), (N/A, 30), (N/A)
(5170 - 5250 @ 80), (N/A, 30), (N/A)
(5250 - 5330 @ 80), (N/A, 30), (N/A)
(5490 - 5730 @ 160), (N/A, 30), (N/A)
(5720 - 5835 @ 80), (N/A, 30), (N/A)
(57000 - 66000 @ 2160), (N/A, 40), (N/A)

I also patch hostapd. :)

Performance is good via smb when "Acrylic Wifi Home" is closed.

Iperf 5,2Ghz WIRELESS-AC 7260 INTEL-Windows 7

Server listening on 8282

Accepted connection from 192.168.10.7, port 52885
[ 5] local 192.168.10.10 port 8282 connected to 192.168.10.7 port 52886
[ ID] Interval Transfer Bandwidth
[ 5] 0.00-1.00 sec 27.4 MBytes 230 Mbits/sec
[ 5] 1.00-2.00 sec 35.8 MBytes 300 Mbits/sec
[ 5] 2.00-3.00 sec 36.1 MBytes 303 Mbits/sec
[ 5] 3.00-4.00 sec 34.5 MBytes 290 Mbits/sec
[ 5] 4.00-5.00 sec 36.5 MBytes 306 Mbits/sec
[ 5] 5.00-6.00 sec 34.8 MBytes 292 Mbits/sec
[ 5] 6.00-7.00 sec 34.3 MBytes 288 Mbits/sec
[ 5] 7.00-8.00 sec 34.1 MBytes 286 Mbits/sec
[ 5] 8.00-9.00 sec 34.0 MBytes 285 Mbits/sec
[ 5] 9.00-10.00 sec 33.2 MBytes 278 Mbits/sec
[ 5] 10.00-10.11 sec 4.21 MBytes 318 Mbits/sec

---

[ ID] Interval Transfer Bandwidth
[ 5] 0.00-10.11 sec 345 MBytes 286 Mbits/sec sender
[ 5] 0.00-10.11 sec 345 MBytes 286 Mbits/sec receiver

Iperf 2.4Ghz WIRELESS-AC 7260 INTEL Windows 7

Server listening on 8282

Accepted connection from 192.168.10.7, port 53048
[ 5] local 192.168.10.10 port 8282 connected to 192.168.10.7 port 53049
[ ID] Interval Transfer Bandwidth
[ 5] 0.00-1.00 sec 13.2 MBytes 111 Mbits/sec
[ 5] 1.00-2.00 sec 19.0 MBytes 160 Mbits/sec
[ 5] 2.00-3.00 sec 18.0 MBytes 151 Mbits/sec
[ 5] 3.00-4.00 sec 17.9 MBytes 150 Mbits/sec
[ 5] 4.00-5.00 sec 18.5 MBytes 155 Mbits/sec
[ 5] 5.00-6.00 sec 14.2 MBytes 119 Mbits/sec
[ 5] 6.00-7.00 sec 17.2 MBytes 144 Mbits/sec
[ 5] 7.00-8.00 sec 17.1 MBytes 143 Mbits/sec
[ 5] 8.00-9.00 sec 17.8 MBytes 149 Mbits/sec
[ 5] 9.00-10.00 sec 18.6 MBytes 156 Mbits/sec
[ 5] 10.00-10.19 sec 3.42 MBytes 151 Mbits/sec

---

[ ID] Interval Transfer Bandwidth
[ 5] 0.00-10.19 sec 175 MBytes 144 Mbits/sec sender
[ 5] 0.00-10.19 sec 175 MBytes 144 Mbits/sec receiver

---

We can do better! :)

Edit: Shit!
'févr. 21 00:24:50 WRT1900AC kernel: ieee80211 phy1: check ba result error 1
févr. 21 00:24:50 WRT1900AC kernel: ieee80211 phy1: ampdu start error code: -22
févr. 21 00:24:50 WRT1900AC kernel: ieee80211 phy1: check ba result error 1
févr. 21 00:24:50 WRT1900AC kernel: ieee80211 phy1: ampdu start error code: -22
févr. 21 00:24:50 WRT1900AC kernel: ieee80211 phy1: check ba result error 1
févr. 21 00:24:50 WRT1900AC kernel: ieee80211 phy1: ampdu start error code: -22
févr. 21 00:24:50 WRT1900AC kernel: ieee80211 phy1: check ba result error 1
févr. 21 00:24:50 WRT1900AC kernel: ieee80211 phy1: ampdu start error code: -22
févr. 21 00:24:50 WRT1900AC kernel: ieee80211 phy1: check ba result error 1
févr. 21 00:24:50 WRT1900AC kernel: ieee80211 phy1: ampdu start error code: -22
févr. 21 00:24:50 WRT1900AC kernel: ieee80211 phy1: check ba result error 1
févr. 21 00:24:50 WRT1900AC kernel: ieee80211 phy1: ampdu start error code: -22
févr. 21 00:24:50 WRT1900AC kernel: ieee80211 phy1: check ba result error 1
févr. 21 00:24:50 WRT1900AC kernel: ieee80211 phy1: ampdu start error code: -22
févr. 21 00:24:50 WRT1900AC kernel: ieee80211 phy1: check ba result error 1
févr. 21 00:24:50 WRT1900AC kernel: ieee80211 phy1: ampdu start error code: -22
'

[Chadster766]

With McDebian rootfs update V1.0.1 it's impossible to get the "ampdu start error code: -22" error to appear in your logs.

https://github.com/Chadster766/McDebian/wiki/X.-McDebian-rootfs-Updates

[Chadster766]

McDebian rootfs V1.0.0 has the Jan 11, 2016 official "Kernel.org" Wireless Regulatory Domain database updates. The only thing new since is country code "CU" and it's related wireless information has been added to the database.

[Chadster766]

I'm thinking about upgrading the firmware to a newer kernel stable release. Do you know if it will have issues with the current Debian package releases?

[jbsky]

Longterm release kernels
Version Maintainer Released Projected EOL
4.4 Greg Kroah-Hartman 2016-01-10 Feb, 2018
Please, update kernel to 4.4.2 or +.
As my USB key with McDebian fail, I use another kernel. If you update before this week-end, I return to McDebian to test your work ;).

[Chadster766]

Ok I'll look into it.

[Chadster766]

Below are kernel option changes between 4.2.4 and 4.4.2. Please check them over:

#New options that will be enabled by default:

CONFIG_FIX_EARLYCON_MEM
CONFIG_MEMBARRIER
CONFIG_ARM_HEAVY_MB
CONFIG_CPU_SW_DOMAIN_PAN
CONFIG_PM_GENERIC_DOMAINS
CONFIG_IP_VS_OVF
CONFIG_NF_DUP_IPV4
CONFIG_NF_DUP_IPV6
CONFIG_BT_HS
CONFIG_CFG80211_CRDA_SUPPORT
CONFIG_NET_VENDOR_SYNOPSYS
CONFIG_SERIAL_8250_FSL
CONFIG_LEDS_NS2
CONFIG_CLKSRC_PROBE
CONFIG_ARM_PMU
CONFIG_TRACING_EVENTS_GPIO
CONFIG_CRYPTO_NULL2

#New unused options:

CONFIG_CGROUP_PIDS
CONFIG_USERFAULTFD
CONFIG_SYSTEM_DATA_VERIFICATION
CONFIG_PCIE_ALTERA
CONFIG_VMSPLIT_3G_OPT
CONFIG_IDLE_PAGE_TRACKING
CONFIG_SUSPEND_SKIP_SYNC
CONFIG_IPV6_ILA
CONFIG_NFT_DUP_IPV4
CONFIG_NFT_DUP_IPV6
CONFIG_NET_L3_MASTER_DEV
CONFIG_LWTUNNEL
CONFIG_MTD_NAND_DENALI_PCI
CONFIG_MTD_NAND_DENALI_DT
CONFIG_CXL_EEH
CONFIG_AHCI_QORIQ
CONFIG_NET_VENDOR_AURORA
CONFIG_BNXT
CONFIG_HNS
CONFIG_HNS_DSAF
CONFIG_HNS_ENET
CONFIG_MLXSW_CORE
CONFIG_ENCX24J600
CONFIG_QED
CONFIG_SYNOPSYS_DWC_ETH_QOS
CONFIG_AQUANTIA_PHY
CONFIG_TERANETICS_PHY
CONFIG_DP83848_PHY
CONFIG_MICROCHIP_PHY
CONFIG_USB_LAN78XX
CONFIG_RTL8XXXU
CONFIG_NVM
CONFIG_USERIO
CONFIG_SERIAL_8250_RT288X
CONFIG_SERIAL_8250_MID
CONFIG_SERIAL_UARTLITE
CONFIG_I2C_EMEV2
CONFIG_GPIO_XILINX
CONFIG_GPIO_ZX
CONFIG_GPIO_MC33880
CONFIG_SENSORS_MAX31790
CONFIG_BCM7038_WDT
CONFIG_MFD_ATMEL_FLEXCOM
CONFIG_MFD_DA9062
CONFIG_REGULATOR_MT6311
!!!!CONFIG_HID_CORSAIR
CONFIG_HID_GEMBIRD
CONFIG_HID_GFRM
CONFIG_MMC_SDHCI_OF_AT91
CONFIG_RTC_DRV_RV8803
CONFIG_RTC_DRV_ZYNQMP
CONFIG_SOC_BRCMSTB
CONFIG_SECTION_MISMATCH_WARN_ONLY
CONFIG_TEST_PRINTF
CONFIG_TEST_STATIC_KEYS
CONFIG_CRYPTO_KEYWRAP
CONFIG_SYSTEM_TRUSTED_KEYRING
CONFIG_SG_SPLIT

#Removed options:

CONFIG_STOP_MACHINE
CONFIG_ARCH_SHMOBILE_LEGACY
CONFIG_PAGEFLAGS_EXTENDED
CONFIG_GENEVE_CORE
CONFIG_NF_CT_NETLINK_HELPER
CONFIG_BT_HCIBPA10X
CONFIG_MTD_NAND_DENALI
CONFIG_BLK_DEV_NVME
CONFIG_SCSI_MPT3SAS
CONFIG_IP1000
CONFIG_GPIO_GENERIC
CONFIG_GPIO_SCH311X
CONFIG_GPIO_MC33880
CONFIG_MMC_CLKGATE
CONFIG_LEDS_PM8941_WLED
!!!!!!!CONFIG_MWLWIFI
CONFIG_EXT3_DEFAULTS_TO_ORDERED
CONFIG_EXT3_FS_XATTR
CONFIG_RCU_CPU_STALL_INFO
CONFIG_JBD
CONFIG_PERCPU_RWSEM
CONFIG_AVERAGE

[francispereira]

@jbsky I am curious - which make and model of USB key were you using for the rootfs ?

[jbsky]

@francispereira, I used Kingston datatraveler G4. First, I made my own kernel with .config provided in this repository. Secondly, I followed instruction recommended by Chadster, and run the router with McDebian. But, my secondary fs failed. So, I return to my first fs and I recompiled with 4.4.2 kernel.
@Chadster766 CONFIG_HID_CORSAIR, not need, is for a keyboad.
For CONFIG_MWLWIFI, as usual, you need to include it into Makefile and kconfig manually in order to recognise it by menuconfig. It's possible to use MWL8K instead of CONFIG_MWLWIFI but bye bye mac80211.

[jbsky]

Add IKCONFIG [=y]

IKCONFIG_PROC [=y]
x Depends on: IKCONFIG [=y] && PROC_FS [=y]

[Chadster766]

Will do, testing kernel 4.4.2 now. I should have a firmware and rootfs test file ready soon.

[francispereira]

@jbsky use a Sandisk or Corsair USB key as suggested in the wiki. I have been using a Sandisk Cruzer for the past month or so. Haven't run into issues. @Chadster766 reported bad blocks on a Kingston too. I have been running a stress for the past week on one of these little things; so far its in suprisingly good shape.

[Chadster766]

The WRT1900AC V1 fan doesn't work on kernel 4.4.2 with the McDebian gpio fancontrol script because the dts has changed to a pwm driver.

arch/arm/boot/dts/armada-xp-linksys-mamba.dts:

  pwm_fan {
          compatible = "pwm-fan";
          pwms = <&gpio0 24 4000 0>;

Have you figured out how to activate the pwm driver to control the fan in kernel 4.4.2?

[Chadster766]

Are you getting the below startup errors in your journalctl with 4.4.2?

kernel: cpu: dev_pm_opp_of_cpumask_add_table: couldn't find opp table for cpu:0, -19
kernel: cpu: dev_pm_opp_of_cpumask_add_table: couldn't find opp table for cpu:1, -19

[Chadster766]

4.4.2 at startup tries to mount the rootfs as ext3 first and if it's formatted ext4 it fails. Then it mounts the rootfs as ext4.

kernel: EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibilities

Are you formatting your rootfs USB Drive as ext3 or ext4? (McDebian recommends ext4)

[jbsky]

I installed lm-sensors and fancontrol. I perform a sensors-detect and a pwmconfig.
Fan can just make "stop or run".

[Chadster766]

Ok I will give the fan process a shot.

[jbsky]

you getting the below startup errors in your journalctl with 4.4.2?
Yes
Are you formatting your rootfs USB Drive as ext3 or ext4?
ext4

[ValCher1961]

Has collected 4.4.3 and too has received-
[ 1.395907] cpu: dev_pm_opp_of_cpumask_add_table: couldn't find opp table for cpu:0, -19
[ 1.404143] cpu: dev_pm_opp_of_cpumask_add_table: couldn't find opp table for cpu:1, -19

  ounting /home...

[ OK ] Started Load/Save Random Seed.
[ 11.220952] EXT4-fs (sda3): warning: mounting fs with errors, running e2fsck is recommended
[ 11.238171] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)

[Chadster766]

With kernel 4.4.2, 4.4.2 DTS, Marvell switch driver and DSA we can take advantage of Port Based VLAN.

root@MCDEBIAN:~# ls /sys/class/net
br0  eth0  eth1  internet  lan1  lan2  lan3  lan4  lo  wlan0  wlan1

More investigation into how iptables and systemd persistent naming service are going to work with this but it is promising.

[Chadster766]

On a WRT1900AC V1 the 4.4.2 firmware loads fine and has no problems when McDebian is rebooted with reboot command.

When the router is powered off using the switch or command systemctl poweroff the router will fail to load the firmware on power up:

AND read: device 0 offset 0x3200000, size 0x400000
 4194304 bytes read: OK
## Booting kernel from Legacy Image at 02000000 ...
   Image Name:   linux
   Created:      2016-03-01   3:57:06 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4264475 Bytes = 4.1 MiB
   Load Address: 00200000
   Entry Point:  00200000
   Verifying Checksum ... Bad Data CRC
ERROR: can't get kernel image!
Marvell>>

Anyone else having this issue with 4.4.2?

[Chadster766]

It looks like once the kernel goes over 4mb it fails to load on the WRT1900AC V1.

[ValCher1961]

No, for WRT1900 V1 I had options kernel superior to 4mb, and everything starts. It looks like you have a problem with the NAND.
It is sad.
If we compare one bit NAND read from the original, you can try to calculate the damaged unit and manually transfer it to BAD.

[Chadster766]

I don't know how to manually set blocks as bad in u-boot. I thought running nand erase.part should mark blocks but I guess it doesn't. What about erase.chip?

[ValCher1961]

Erase.chip Will erase everything, after it will be necessary to restore U-boot.
By the way, there is a probability that new table Bad in which all will be constructed will be considered.
U-boot it is restored easily.

[Chadster766]

I know how to restore u-boot on the WRT1900AC V1 but do you know how to do it on the WRT1200AC?

[ValCher1961]

I think similar, but I shall not confirm. (

[Chadster766]

I "nand scrub.chip" the WRT1900AC V1 and reloaded u-boot. This should have marked any bad blocks that might have existed on the nand. It even forced loading for boot part 1 and 2 with it still failing to load Kernel 4.4.2 when it's over 4mb.

[Chadster766]

I'm working on updating u-boot.

[jbsky]

On 4.6.3, I think dsa switch cant start with nfs root.

[ValCher1961]

No, I have not tried.

[ValCher1961]

@ALL.
Do you find useful to build a new kernel 4.6.4 or wait for a new release?

[Chadster766]

I've decided that I'm going to move forward with the latest long term releases and it's patches because a new kernel version keeps coming out every week. It's to hard to keep up with.

[ValCher1961]

Yes, of course you're right, the more recent version contains changes crumbs.

[Chadster766]

@ValCher1961 I was mistaken. I would like to use the longterm kernel releases but the last one doesn't have some code required for the latest mwlwifi release.

I was implementing kernel version 4.6.3 for McDebian when I noticed that the USB drive was failing with a repeating error that eventually crashes the Debian system:

[   54.952009] usb 3-1: reset SuperSpeed USB device number 2 using xhci-hcd
[   54.972720] usb usb3-port1: config error
[   99.521074] usb 3-1: reset SuperSpeed USB device number 2 using xhci-hcd
[   99.542329] usb usb3-port1: config error
[   99.552408] sd 2:0:0:0: [sda] 120933888 512-byte logical blocks: (61.9 GB/57.7 GiB)
[  102.041021] usb 3-1: reset SuperSpeed USB device number 2 using xhci-hcd
[  108.370839] usb 3-1: USB disconnect, device number 2
[  108.377609] EXT4-fs warning (device sda1): ext4_end_bio:315: I/O error -5 writing to inode 2883594 (offset 0 size 4096 starting block 11567513)
[  108.390537] Buffer I/O error on device sda1, logical block 11567256
[  108.396853] EXT4-fs warning (device sda1): ext4_end_bio:315: I/O error -5 writing to inode 2885476 (offset 0 size 0 starting block 11611906)
[  108.409511] Buffer I/O error on device sda1, logical block 11611649
[  108.416057] JBD2: Detected IO errors while flushing file data on sda1-8
[  108.423250] Aborting journal on device sda1-8.
[  108.427736] JBD2: Error -5 detected when updating journal superblock for sda1-8.
[  108.459793] EXT4-fs error (device sda1): ext4_find_entry:1451: inode #2097153: comm kworker/u4:0: reading directory lblock 0
[  108.471096] EXT4-fs (sda1): previous I/O error to superblock detected
[  108.790856] usb 3-1: new SuperSpeed USB device number 3 using xhci-hcd
[  108.812464] usb-storage 3-1:1.0: USB Mass Storage device detected
[  108.818692] scsi host3: usb-storage 3-1:1.0
[  109.490814] usb 3-1: USB disconnect, device number 3
[  109.770916] usb 3-1: Device not responding to setup address.
[  109.980909] usb 3-1: Device not responding to setup address.
[  110.143133] EXT4-fs error (device sda1): ext4_find_entry:1451: inode #2883585: comm smbd: reading directory lblock 0
[  110.154053] EXT4-fs error (device sda1): ext4_journal_check_start:56: Detected aborted journal
[  110.162760] EXT4-fs (sda1): Remounting filesystem read-only
[  110.168358] ------------[ cut here ]------------
[  110.173007] WARNING: CPU: 0 PID: 4638 at fs/fs-writeback.c:2110 __mark_inode_dirty+0x15c/0x1ec
[  110.181664] bdi-block not registered
[  110.185251] Modules linked in: nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter xt_conntrack iptable_filter iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_nat iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat ip_tables bridge stp llc mwlwifi mvmdio mvneta cifs dns_resolver fscache nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack ip6_tables mv88e6xxx_drv dsa_core ipv6
[  110.220706] CPU: 0 PID: 4638 Comm: smbd Not tainted 4.6.3 #1
[  110.226387] Hardware name: Marvell Armada 380/385 (Device Tree)
[  110.232340] [<c010f4c4>] (unwind_backtrace) from [<c010b2e0>] (show_stack+0x10/0x14)
[  110.240118] [<c010b2e0>] (show_stack) from [<c03275c4>] (dump_stack+0x90/0xa4)
[  110.247372] [<c03275c4>] (dump_stack) from [<c011d31c>] (__warn+0xe8/0x100)
[  110.254363] [<c011d31c>] (__warn) from [<c011d36c>] (warn_slowpath_fmt+0x38/0x48)
[  110.261878] [<c011d36c>] (warn_slowpath_fmt) from [<c0217e2c>] (__mark_inode_dirty+0x15c/0x1ec)
[  110.270616] [<c0217e2c>] (__mark_inode_dirty) from [<c02095f0>] (generic_update_time+0x70/0xac)
[  110.279353] [<c02095f0>] (generic_update_time) from [<c0209764>] (file_update_time+0xb8/0x10c)
[  110.288001] [<c0209764>] (file_update_time) from [<c01a8d54>] (__generic_file_write_iter+0x90/0x1fc)
[  110.297174] [<c01a8d54>] (__generic_file_write_iter) from [<c0255a58>] (ext4_file_write_iter+0x16c/0x47c)
[  110.306784] [<c0255a58>] (ext4_file_write_iter) from [<c01f069c>] (__vfs_write+0xa8/0xd8)
[  110.314996] [<c01f069c>] (__vfs_write) from [<c01f137c>] (vfs_write+0x94/0x154)
[  110.322336] [<c01f137c>] (vfs_write) from [<c01f2030>] (SyS_write+0x40/0x94)
[  110.329415] [<c01f2030>] (SyS_write) from [<c0107640>] (ret_fast_syscall+0x0/0x3c)
[  110.337042] ---[ end trace 690af4bbb8818309 ]---

A few days ago another kernel was released 4.6.4 that has some USB 3.0 fixes but I don't see the specific error I listed above.

[ValCher1961]

@Chadster766
With version 4.5 kernels I use SSD with the SATA connection.
Tonight is I will try re-create your configuration with SSD connection with Debian to USB.
My version 4.6.3.

[ValCher1961]

I have no error, but I used the USB 2.0

root@wrt1900ac:~# uname -a
Linux wrt1900ac 4.6.3 #2 SMP Sat Jun 25 01:42:45 MSK 2016 armv7l GNU/Linux
root@wrt1900ac:~# dmesg |grep -i usb
[    0.076591] usbcore: registered new interface driver usbfs
[    0.076650] usbcore: registered new interface driver hub
[    0.076698] usbcore: registered new device driver usb
[    1.211705] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.232270] orion-ehci f1050000.usb: EHCI Host Controller
[    1.237700] orion-ehci f1050000.usb: new USB bus registered, assigned bus number 1
[    1.245371] orion-ehci f1050000.usb: irq 26, io mem 0xf1050000
[    1.267987] orion-ehci f1050000.usb: USB 2.0 started, EHCI 1.00
[    1.274557] hub 1-0:1.0: USB hub found
[    1.288081] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
[    1.304727] hub 2-0:1.0: USB hub found
[    1.318236] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 3
[    1.325740] usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
[    1.334432] hub 3-0:1.0: USB hub found
[    1.343022] usbcore: registered new interface driver usb-storage
[    1.421583] usbcore: registered new interface driver usbhid
[    1.427172] usbhid: USB HID core driver
[    1.598085] usb 1-1: new high-speed USB device number 2 using orion-ehci
[    1.750650] usb-storage 1-1:1.0: USB Mass Storage device detected
[    1.757366] scsi host1: usb-storage 1-1:1.0
root@wrt1900ac:~#

[Chadster766]

The error occurred with USB 3.0 device in the USB3 Port.

[ValCher1961]

I have included in the port USB3 device USB ver 2.0
Unfortunately no drive USB 3.0

[Chadster766]

Can you try with a USB3 device in the USB3 port?

[Chadster766]

I had to "systemctl restart hostapd" to trigger the issue.

[ValCher1961]

Yes, now I stand the system on a flash drive USB3.0

[Chadster766]

The journalctl doesn't show any errors when you restart hostapd?

[ValCher1961]

Strangely, I have not installed the USB3.0 driver, or the way it should be?

root@wrt1900ac:~# dmesg |grep -i usb
[    0.076568] usbcore: registered new interface driver usbfs
[    0.076610] usbcore: registered new interface driver hub
[    0.076659] usbcore: registered new device driver usb
[    1.211029] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.231599] orion-ehci f1050000.usb: EHCI Host Controller
[    1.237029] orion-ehci f1050000.usb: new USB bus registered, assigned bus number 1
[    1.244699] orion-ehci f1050000.usb: irq 26, io mem 0xf1050000
[    1.267878] orion-ehci f1050000.usb: USB 2.0 started, EHCI 1.00
[    1.274439] hub 1-0:1.0: USB hub found
[    1.287915] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
[    1.304572] hub 2-0:1.0: USB hub found
[    1.318084] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 3
[    1.325591] usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
[    1.334289] hub 3-0:1.0: USB hub found
[    1.342875] usbcore: registered new interface driver usb-storage
[    1.420470] usbcore: registered new interface driver usbhid
[    1.426059] usbhid: USB HID core driver
[    1.647994] usb 2-2: new high-speed USB device number 2 using xhci_hcd
[    1.792819] usb-storage 2-2:1.0: USB Mass Storage device detected
[    1.810240] scsi host1: usb-storage 2-2:1.0
root@wrt1900ac:~#

[Chadster766]

This is what shows for me:

    1.276503] xhci-hcd f10f8000.usb3: xHCI Host Controller
[    1.281857] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus numb
[    1.289474] xhci-hcd f10f8000.usb3: hcc params 0x0a000990 hci version 0x100 q            0010
[    1.298069] xhci-hcd f10f8000.usb3: irq 43, io mem 0xf10f8000
[    1.304219] hub 2-0:1.0: USB hub found
[    1.307999] hub 2-0:1.0: 1 port detected
[    1.312063] xhci-hcd f10f8000.usb3: xHCI Host Controller
[    1.317424] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus numb
[    1.324972] usb usb3: We don't know the algorithms for LPM for this host, dis
[    1.332632] ata1: SATA link down (SStatus 0 SControl 300)
[    1.332652] ata2: SATA link down (SStatus 0 SControl 300)
[    1.344221] hub 3-0:1.0: USB hub found
[    1.347998] hub 3-0:1.0: 1 port detected
[    1.352323] input: gpio_keys as /devices/platform/gpio_keys/input/input0
[    1.359180] armada38x-rtc f10a3800.rtc: setting system clock to 2016-07-14 04            1468470097)
[    1.368889] ALSA device list:
[    1.371867]   No soundcards found.
[    1.375552] Waiting 5 sec before mounting root device...
[    1.662114] usb 3-1: new SuperSpeed USB device number 2 using xhci-hcd
[    1.683467] usb-storage 3-1:1.0: USB Mass Storage device detected
[    1.689704] scsi host2: usb-storage 3-1:1.0
[    2.692709] scsi 2:0:0:0: Direct-Access     Corsair  Slider 3.0       000E PQ
[    2.701379] sd 2:0:0:0: [sda] 120933888 512-byte logical blocks: (61.9 GB/57.
[    2.709269] sd 2:0:0:0: [sda] Write Protect is off
[    2.714281] sd 2:0:0:0: [sda] Write cache: disabled, read cache: enabled, doe             DPO or FUA
[    3.051813]  sda: sda1
[    3.055035] sd 2:0:0:0: [sda] Attached SCSI removable disk
[    6.383032] EXT4-fs (sda1): couldn't mount as ext3 due to feature incompatibi
[    6.764135] EXT4-fs (sda1): recovery complete
[    6.770988] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts:
[    6.778701] VFS: Mounted root (ext4 filesystem) on device 8:1.

[Chadster766]

Testing on a WRT1900AC V2.

[ValCher1961]

There are differences V1 and V2, but I also want so)

[ValCher1961]

I do not know I'm right or not, but I think to remove from the kernel -
USB_EHCI_HCD_ORION [= y]
and leave -
USB_XHCI_PLATFORM [= y]

[ValCher1961]

It seems XHCI driver is backward compatible with the EHCI and OHCI,
In any case, USB2.0 and USB1.1 devices operate.

[Chadster766]

Well I update the mwlwifi drivers to the latest version and made a McDebian firmware kernel 4.6.4. I've also implemented the DSA switch.

The Corsair Slider 3.0 no longer works in the USB3.0 plug but work fine in the USB2.

I will monitor performance\stability and report back.

[Chadster766]

I don't understand why the USB updates are only occurring in the 4.7 RC kernel release. Isn't kernel.org getting troubled by USB device issues in 4.6?

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=e80dac114c63dd54398c3c785a6431622c320e87

[ValCher1961]

It may give notice of the problem in the kernel 4.6 or wait for the stable release 4.7.

[ValCher1961]

@ALL
Maybe this is a very long branch will close and open a new one. My IExplorer high latency opens the page.

[Chadster766]

Please do 😄

[jbsky]

Can I?

[Chadster766]

Yes that would be great. This thread was taking a long time to load.

[Redferne]

Wonderful work! Thank you! Finally got multicast (mdns) working on the bridge br0 👍 😸