-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need a New Kernel > 4.4.0 and New Regulatory wifi! #7
Comments
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 |
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. |
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? |
Longterm release kernels |
Ok I'll look into it. |
Below are kernel option changes between 4.2.4 and 4.4.2. Please check them over:
|
@jbsky I am curious - which make and model of USB key were you using for the rootfs ? |
@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. |
Add IKCONFIG [=y] IKCONFIG_PROC [=y] |
Will do, testing kernel 4.4.2 now. I should have a firmware and rootfs test file ready soon. |
@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. |
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:
Have you figured out how to activate the pwm driver to control the fan in kernel 4.4.2? |
Are you getting the below startup errors in your journalctl with 4.4.2?
|
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.
Are you formatting your rootfs USB Drive as ext3 or ext4? (McDebian recommends ext4) |
I installed lm-sensors and fancontrol. I perform a sensors-detect and a pwmconfig. |
Ok I will give the fan process a shot. |
you getting the below startup errors in your journalctl with 4.4.2? |
Has collected 4.4.3 and too has received-
[ OK ] Started Load/Save Random Seed. |
With kernel 4.4.2, 4.4.2 DTS, Marvell switch driver and DSA we can take advantage of Port Based VLAN.
More investigation into how iptables and systemd persistent naming service are going to work with this but it is promising. |
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:
Anyone else having this issue with 4.4.2? |
It looks like once the kernel goes over 4mb it fails to load on the WRT1900AC V1. |
No, for WRT1900 V1 I had options kernel superior to 4mb, and everything starts. It looks like you have a problem with the NAND. |
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? |
Erase.chip Will erase everything, after it will be necessary to restore U-boot. |
I know how to restore u-boot on the WRT1900AC V1 but do you know how to do it on the WRT1200AC? |
I think similar, but I shall not confirm. ( |
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. |
I'm working on updating u-boot. |
On 4.6.3, I think dsa switch cant start with nfs root. |
No, I have not tried. |
@ALL. |
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. |
Yes, of course you're right, the more recent version contains changes crumbs. |
@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:
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. |
@Chadster766 |
I have no error, but I used the USB 2.0
|
The error occurred with USB 3.0 device in the USB3 Port. |
I have included in the port USB3 device USB ver 2.0 |
Can you try with a USB3 device in the USB3 port? |
I had to "systemctl restart hostapd" to trigger the issue. |
Yes, now I stand the system on a flash drive USB3.0 |
The journalctl doesn't show any errors when you restart hostapd? |
Strangely, I have not installed the USB3.0 driver, or the way it should be?
|
This is what shows for me:
|
Testing on a WRT1900AC V2. |
There are differences V1 and V2, but I also want so) |
I do not know I'm right or not, but I think to remove from the kernel - |
It seems XHCI driver is backward compatible with the EHCI and OHCI, |
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. |
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? |
It may give notice of the problem in the kernel 4.6 or wait for the stable release 4.7. |
@ALL |
Please do 😄 |
Can I? |
Yes that would be great. This thread was taking a long time to load. |
Wonderful work! Thank you! Finally got multicast (mdns) working on the bridge br0 👍 😸 |
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
'
The text was updated successfully, but these errors were encountered: