Once I figured out the syntax, it took me about 5 minutes to setup the filters on the QNAP and the messages are now completely gone from the viewable log file. I managed to get it to filter both the "ampdu" and "check ba" messages as well as the message that precedes them:
mwl_fwcmd_check_ba: 4 callbacks suppressed
MrDoh wrote:
htismaqe wrote:
MrDoh wrote:
JohnnySL wrote:
MrDoh wrote:
Turns out I'm also seeing a kernel log full of these errors:
[ 5379.158180] ieee80211 phy0: check ba result error 1
[ 5379.163192] ieee80211 phy0: ampdu start error code: -22
which I just noticed...hopefully the newer patch fixes this.
We'll see.
nope i've added a hack on my build to remove the spam.
Interesting. Now that I've done a little reading about this error, I've gone back to the WRT1900AC with the same firmware (with the latency apparently fixed). What I'm reading is that this error doesn't itself indicate that there's anything broken. And someone has just added a patch to disappear this error altogether, which furthers this idea.
So I'm going to see what the result of these errors is for me. I'm not expecting anything, just really curious to see what happens downstream.
I think at some point I'll write a filter on my QNAP to suppress those messages.
Well, the absolute flood of these messages is gone in a later patch of the wireless driver, which is available via openWRT. Now I see groups of 5-10 of these messages every few hours. And the Marvell wireless driver guy says that those can be ignored and will be filtered soon. So I don't see any problem with filtering them out of the log one way or the other. I'm thinking that I may write a script that runs via cron that reads the log, and re-writes it without those messages until the patch that the Marvell guy is going to do gets to firmware. Sounds like a fun programming project, as well *smile*.
root@1900acs:~# wget -O - http://pkg.entware.net/binaries/armv7/installer/entwar
e_install.sh | sh
Connecting to pkg.entware.net (81.4.123.217:80)
Info: Checking for prerequisites and creating folders...
Warning: Folder /opt exists!
mkdir: can't create directory '/opt/bin': Read-only file system
mkdir: can't create directory '/opt/etc/': Read-only file system
mkdir: can't create directory '/opt/lib/opkg': Read-only file system
mkdir: can't create directory '/opt/sbin': Read-only file system
mkdir: can't create directory '/opt/share': Read-only file system
mkdir: can't create directory '/opt/tmp': Read-only file system
mkdir: can't create directory '/opt/usr': Read-only file system
mkdir: can't create directory '/opt/var/': Read-only file system
mkdir: can't create directory '/opt/var/': Read-only file system
mkdir: can't create directory '/opt/var/': Read-only file system
Info: Opkg package manager deployment...
Connecting to pkg.entware.net (81.4.123.217:80)
wget: can't open '/opt/bin/opkg': No such file or directory
chmod: /opt/bin/opkg: No such file or directory
Connecting to pkg.entware.net (81.4.123.217:80)
wget: can't open '/opt/etc/opkg.conf': No such file or directory
Connecting to pkg.entware.net (81.4.123.217:80)
wget: can't open '/opt/lib/ld-2.23.so': Read-only file system
Connecting to pkg.entware.net (81.4.123.217:80)
wget: can't open '/opt/lib/libc-2.23.so': Read-only file system
Connecting to pkg.entware.net (81.4.123.217:80)
wget: can't open '/opt/lib/libgcc_s.so.1': Read-only file system
chmod: ld-2.23.so: No such file or directory
ln: ld-linux.so.3: Read-only file system
ln: libc.so.6: Read-only file system
Info: Basic packages installation...
sh: /opt/bin/opkg: not found
sh: /opt/bin/opkg: not found
Connecting to pkg.entware.net (81.4.123.217:80)
wget: can't open '/opt/usr/lib/locale/locale-archive': No such file or directory
Info: Congratulations!
Info: If there are no errors above then Entware-ng was successfully initialized.
Info: Add /opt/bin & /opt/sbin to your PATH variable
Info: Add '/opt/etc/init.d/rc.unslung start' to startup script for Entware-ng services to start
Info: Found a Bug? Please report at https://github.com/Entware-ng/Entware-ng/issues
root@1900acs:~#
Posted: Wed Jun 22, 2016 22:50 Post subject: Huawei E8372 as USB Modem on WRT1900AC V2
The dmesg output is as follows:
[ 28.574470] usbcore: registered new interface driver cdc_acm
[ 28.580159] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 28.591346] usbcore: registered new interface driver cdc_wdm
[ 28.632388] usbcore: registered new interface driver qmi_wwan
[ 28.651205] usbcore: registered new interface driver usbserial
[ 28.657094] usbcore: registered new interface driver usbserial_generic
[ 28.663686] usbserial: USB Serial support registered for generic
[ 28.686276] usbcore: registered new interface driver sierra
[ 28.691916] usbserial: USB Serial support registered for Sierra USB modem
[ 28.711512] usbcore: registered new interface driver option
[ 28.717142] usbserial: USB Serial support registered for GSM modem (1-port)
[ 28.749117] usbcore: registered new interface driver qcserial
[ 28.754934] usbserial: USB Serial support registered for Qualcomm USB modem
[ 29.661127] br0: port 4(ath1) entered forwarding state
[ 95.131012] usbcore: registered new interface driver usb-storage
[ 95.163525] ehci-orion: EHCI orion driver
[ 95.167665] orion-ehci f1058000.usb: EHCI Host Controller
[ 95.173124] orion-ehci f1058000.usb: new USB bus registered, assigned bus number 3
[ 95.180928] orion-ehci f1058000.usb: irq 50, io mem 0xf1058000
[ 95.201148] orion-ehci f1058000.usb: USB 2.0 started, EHCI 1.00
[ 95.207755] hub 3-0:1.0: USB hub found
[ 95.211656] hub 3-0:1.0: 1 port detected
[ 95.223036] usbcore: registered new interface driver usblp
[ 95.531137] usb 3-1: new high-speed USB device number 2 using orion-ehci
[ 95.798871] usb-storage 3-1:1.2: USB Mass Storage device detected
[ 95.805225] scsi host2: usb-storage 3-1:1.2
[ 96.807087] scsi 2:0:0:0: Direct-Access HUAWEI TF CARD Storage 2.31 PQ: 0 ANSI: 2
[ 96.818830] sd 2:0:0:0: [sda] Attached SCSI removable disk
Download the image from linksys website and rename it like this " blk-mamba.128mb.img "
Install TerraT and set speed to 115200 baud.
Open TFTPD32 and select Linksys from the second tab and in first TAB click Brows and select the images that you downloaded and renamed from linksys website.
Now with TerraT open and TFTPD open, do the fallowing things !