OpenWrt Forum Archive

Topic: Update on Linksys WRT1900AC support

The content of this topic has been archived between 16 Sep 2014 and 7 May 2018. Unfortunately there are posts – most likely complete pages – missing.

l3333 wrote:

@doITright

doITright wrote:
pat30724 wrote:

How can i get it that it does download those? It only downloads the first.

cd ..
cd etc
vim opkg.conf

post what you see but I am betting on # at the beginning of every package line but the first....

Cheers

Do you have an idea why this is happening to some installations?

It's a build-time option. In menuconfig, Image configuration -> Separate feed repositories. So, it depends on which build the user has loaded. It could also depend on whether the user has a "correct" opkg.conf in their settings and upgraded with those preserved.

Again self built trunk has been working great! only had 2 issues 1) Hang on a nexus 5 (no internet until i turned off and on the wifi toggle) 2) hang on my macbook running 10.10.2 Yosemite which is overcome by turning off and on the wireless toggle. Odd, otherwise everything is solid and samba speeds are incredible (downloading a 3 gb app + streaming 21 jump street from my hdd connected esata to router + coping a file from said hdd to computer).

(Last edited by lifehacksback on 1 Apr 2015, 19:45)

l3333 wrote:

@doITright

doITright wrote:
pat30724 wrote:

How can i get it that it does download those? It only downloads the first.

cd ..
cd etc
vim opkg.conf

post what you see but I am betting on # at the beginning of every package line but the first....

Cheers

Do you have an idea why this is happening to some installations?

No idea....  I am just an interested spectator here smile

Since I stay strictly with the trunk, I do not see many of these... 
It has been quite a while since the location changed for packages and some of us had issues for example....

Cheers

Here you go guys! Trunk build 3.18 w/ leitec's patches he pushed to trunk and another build sporting kernel 4.0-rc6. Both with the new Marvell driver pushed to trunk and with a few other things (kmod-fs-btrfs, samba, mountpoint, luci-ssl, sqm, elliptical curve cryptography for dropbear). Other notable difference is that on the trunk build i enabled Image configuration -> Separate feed repositories while on the 4.0 i didn't.

I have tested 4.0 for a while and it is relatively stable (2 small hiccups)

http://tinyurl.com/Lifehacksback-Testing-CC

lifehacksback

Anyone know if we can patch the kernel to include the BFS?

(Last edited by lifehacksback on 1 Apr 2015, 19:56)

lifehacksback wrote:

Again self built trunk has been working great! only had 2 issues 1) Hang on a nexus 5 (no internet until i turned off and on the wifi toggle) 2) hang on my macbook running 10.10.2 Yosemite which is overcome by turning off and on the wireless toggle. Odd, otherwise everything is solid and samba speeds are incredible (downloading a 3 gb app + streaming 21 jump street from my hdd connected esata to router + coping a file from said hdd to computer).

I have a nexus 5 too. I used to get AC wifi hang with MCWRT when i would start a big file transfer (e.g 2gb). It would freeze during the transfer. Had to toggle wifi on and off to get it going.
I wonder if nexus 5 has some issues of its own smile

Anyone managed to build latest trunk? Im still getting this ennoying problem:

make[6]: Entering directory '/home/Belliash/openwrt/build_dir/target-arm_cortex-a9+vfpv3_uClibc-0.9.33.2_eabi/e2fsprogs-1.42.12/misc'
        CC mke2fs.c
        PROFILE_TO_C mke2fs.conf
        CC default_profile.c
        LD mke2fs
../lib/libext2fs.so: warning: the use of OBSOLESCENT `utime' is discouraged, use `utimes'
        LD badblocks
../lib/libext2fs.so: warning: the use of OBSOLESCENT `utime' is discouraged, use `utimes'
        LD tune2fs
../lib/libext2fs.so: warning: the use of OBSOLESCENT `utime' is discouraged, use `utimes'
        LD dumpe2fs
../lib/libext2fs.so: warning: the use of OBSOLESCENT `utime' is discouraged, use `utimes'
        LD blkid
../lib/libext2fs.so: warning: the use of OBSOLESCENT `utime' is discouraged, use `utimes'
        LD logsave
        LD e2image
../lib/libext2fs.so: warning: the use of OBSOLESCENT `utime' is discouraged, use `utimes'
        LD fsck
        LD e2undo
../lib/libext2fs.so: warning: the use of OBSOLESCENT `utime' is discouraged, use `utimes'
        LD chattr
        LD lsattr
        LD mklost+found
        LD filefrag
        LD e2freefrag
../lib/libext2fs.so: warning: the use of OBSOLESCENT `utime' is discouraged, use `utimes'
        CC e4defrag.c
e4defrag.c:197:2: error: #error sync_file_range not available!
 #error sync_file_range not available!
  ^
Makefile:393: recipe for target 'e4defrag.o' failed
make[6]: *** [e4defrag.o] Error 1
make[6]: Leaving directory '/home/Belliash/openwrt/build_dir/target-arm_cortex-a9+vfpv3_uClibc-0.9.33.2_eabi/e2fsprogs-1.42.12/misc'
Makefile:382: recipe for target 'all-progs-recursive' failed
make[5]: *** [all-progs-recursive] Error 1
make[5]: Leaving directory '/home/Belliash/openwrt/build_dir/target-arm_cortex-a9+vfpv3_uClibc-0.9.33.2_eabi/e2fsprogs-1.42.12'
Makefile:318: recipe for target 'all' failed
nyt wrote:

e2fsprogs still broke for armv7/mvebu sad

I just built it with a previous version.

diff --git a/package/utils/e2fsprogs/Makefile b/package/utils/e2fsprogs/Makefile
index 57e7aae..c9d55b2 100644
--- a/package/utils/e2fsprogs/Makefile
+++ b/package/utils/e2fsprogs/Makefile
@@ -8,8 +8,8 @@
 include $(TOPDIR)/rules.mk

 PKG_NAME:=e2fsprogs
-PKG_VERSION:=1.42.12
-PKG_MD5SUM:=68255f51be017a93f2f6402fab06c2bf
+PKG_VERSION:=1.42.8
+PKG_MD5SUM:=8ef664b6eb698aa6b733df59b17b9ed4
 PKG_RELEASE:=1

 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz

belliash wrote:

Anyone managed to build latest trunk? Im still getting this ennoying problem:

make[6]: Entering directory '/home/Belliash/openwrt/build_dir/target-arm_cortex-a9+vfpv3_uClibc-0.9.33.2_eabi/e2fsprogs-1.42.12/misc'
        CC mke2fs.c
        PROFILE_TO_C mke2fs.conf
        CC default_profile.c
        LD mke2fs
../lib/libext2fs.so: warning: the use of OBSOLESCENT `utime' is discouraged, use `utimes'
        LD badblocks
../lib/libext2fs.so: warning: the use of OBSOLESCENT `utime' is discouraged, use `utimes'
        LD tune2fs
../lib/libext2fs.so: warning: the use of OBSOLESCENT `utime' is discouraged, use `utimes'
        LD dumpe2fs
../lib/libext2fs.so: warning: the use of OBSOLESCENT `utime' is discouraged, use `utimes'
        LD blkid
../lib/libext2fs.so: warning: the use of OBSOLESCENT `utime' is discouraged, use `utimes'
        LD logsave
        LD e2image
../lib/libext2fs.so: warning: the use of OBSOLESCENT `utime' is discouraged, use `utimes'
        LD fsck
        LD e2undo
../lib/libext2fs.so: warning: the use of OBSOLESCENT `utime' is discouraged, use `utimes'
        LD chattr
        LD lsattr
        LD mklost+found
        LD filefrag
        LD e2freefrag
../lib/libext2fs.so: warning: the use of OBSOLESCENT `utime' is discouraged, use `utimes'
        CC e4defrag.c
e4defrag.c:197:2: error: #error sync_file_range not available!
 #error sync_file_range not available!
  ^
Makefile:393: recipe for target 'e4defrag.o' failed
make[6]: *** [e4defrag.o] Error 1
make[6]: Leaving directory '/home/Belliash/openwrt/build_dir/target-arm_cortex-a9+vfpv3_uClibc-0.9.33.2_eabi/e2fsprogs-1.42.12/misc'
Makefile:382: recipe for target 'all-progs-recursive' failed
make[5]: *** [all-progs-recursive] Error 1
make[5]: Leaving directory '/home/Belliash/openwrt/build_dir/target-arm_cortex-a9+vfpv3_uClibc-0.9.33.2_eabi/e2fsprogs-1.42.12'
Makefile:318: recipe for target 'all' failed
alirz wrote:

I have a nexus 5 too. I used to get AC wifi hang with MCWRT when i would start a big file transfer (e.g 2gb). It would freeze during the transfer. Had to toggle wifi on and off to get it going.
I wonder if nexus 5 has some issues of its own smile

What version are you running? 5.0.2 or 5.1? Maybe so hmm

lifehacksback wrote:

Here you go guys! Trunk build 3.18 w/ leitec's patches he pushed to trunk and another build sporting kernel 4.0-rc6. Both with the new Marvell driver pushed to trunk and with a few other things (kmod-fs-btrfs, samba, mountpoint, luci-ssl, sqm, elliptical curve cryptography for dropbear). Other notable difference is that on the trunk build i enabled Image configuration -> Separate feed repositories while on the 4.0 i didn't.

I have tested 4.0 for a while and it is relatively stable (2 small hiccups)

http://tinyurl.com/Lifehacksback-Testing-CC

lifehacksback

Very nice right out of the box.
Thank you.

lifehacksback wrote:
alirz wrote:

I have a nexus 5 too. I used to get AC wifi hang with MCWRT when i would start a big file transfer (e.g 2gb). It would freeze during the transfer. Had to toggle wifi on and off to get it going.
I wonder if nexus 5 has some issues of its own smile

What version are you running? 5.0.2 or 5.1? Maybe so hmm

If i remember correctly, I THINK at the time I was running 5.0.1 but to be honest it could have been 5.1 also. I was never on 5.0.2.
Back when i had the freezing issue, i had tried with an Ipad on AC wifi also and it DID NOT freeze.

@alirz

5.0.1 was plagued with issues. 5.0.2 fixed some but wifi was still meh. 5.1 should have fixed the wifi problems but i have to keep testing and this hiccup is not a good sign. 5.1 was released less than 3 weeks ago.

nyt wrote:
nyt wrote:

e2fsprogs still broke for armv7/mvebu sad

I just built it with a previous version.

diff --git a/package/utils/e2fsprogs/Makefile b/package/utils/e2fsprogs/Makefile
index 57e7aae..c9d55b2 100644
--- a/package/utils/e2fsprogs/Makefile
+++ b/package/utils/e2fsprogs/Makefile
@@ -8,8 +8,8 @@
 include $(TOPDIR)/rules.mk

 PKG_NAME:=e2fsprogs
-PKG_VERSION:=1.42.12
-PKG_MD5SUM:=68255f51be017a93f2f6402fab06c2bf
+PKG_VERSION:=1.42.8
+PKG_MD5SUM:=8ef664b6eb698aa6b733df59b17b9ed4
 PKG_RELEASE:=1

 PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz

belliash wrote:

Anyone managed to build latest trunk? Im still getting this ennoying problem:

make[6]: Entering directory '/home/Belliash/openwrt/build_dir/target-arm_cortex-a9+vfpv3_uClibc-0.9.33.2_eabi/e2fsprogs-1.42.12/misc'
        CC mke2fs.c
        PROFILE_TO_C mke2fs.conf
        CC default_profile.c
        LD mke2fs
../lib/libext2fs.so: warning: the use of OBSOLESCENT `utime' is discouraged, use `utimes'
        LD badblocks
../lib/libext2fs.so: warning: the use of OBSOLESCENT `utime' is discouraged, use `utimes'
        LD tune2fs
../lib/libext2fs.so: warning: the use of OBSOLESCENT `utime' is discouraged, use `utimes'
        LD dumpe2fs
../lib/libext2fs.so: warning: the use of OBSOLESCENT `utime' is discouraged, use `utimes'
        LD blkid
../lib/libext2fs.so: warning: the use of OBSOLESCENT `utime' is discouraged, use `utimes'
        LD logsave
        LD e2image
../lib/libext2fs.so: warning: the use of OBSOLESCENT `utime' is discouraged, use `utimes'
        LD fsck
        LD e2undo
../lib/libext2fs.so: warning: the use of OBSOLESCENT `utime' is discouraged, use `utimes'
        LD chattr
        LD lsattr
        LD mklost+found
        LD filefrag
        LD e2freefrag
../lib/libext2fs.so: warning: the use of OBSOLESCENT `utime' is discouraged, use `utimes'
        CC e4defrag.c
e4defrag.c:197:2: error: #error sync_file_range not available!
 #error sync_file_range not available!
  ^
Makefile:393: recipe for target 'e4defrag.o' failed
make[6]: *** [e4defrag.o] Error 1
make[6]: Leaving directory '/home/Belliash/openwrt/build_dir/target-arm_cortex-a9+vfpv3_uClibc-0.9.33.2_eabi/e2fsprogs-1.42.12/misc'
Makefile:382: recipe for target 'all-progs-recursive' failed
make[5]: *** [all-progs-recursive] Error 1
make[5]: Leaving directory '/home/Belliash/openwrt/build_dir/target-arm_cortex-a9+vfpv3_uClibc-0.9.33.2_eabi/e2fsprogs-1.42.12'
Makefile:318: recipe for target 'all' failed

Thank you very much for help. This worked.

Thanks for the help. I have my WRT1900AC working again big_smile.

Does anyone know how often is the "additional hosts files" loaded/kept active ? I ask because i have a "hosts.block" file set as the additional hosts file. Even though the files exists on my usb flash drive and few days ago it was in affect, today for some reason the router seemed to have been ignoring it, i.e i use this hosts file to block ads but today the websites had ads on them.

i restarted dnsmasq and i see in the logs that it read the addresses from the file and now its working fine.

My question is, why would it have stopped in the first place?

Is it possible to capture data frame and radio header when putting the radio in monitor mode?

Model    Linksys WRT1900AC (Mamba)
Firmware Version    OpenWrt Chaos Calmer r45176 / LuCI (git-15.090.50849-576e235)
Kernel Version    4.0.0-rc6

# create monitor int
iw wlan0 interface add mon0 type monitor
iw wlan1 interface add mon1 type monitor

# change channel to 36
iw phy phy1 set channel 36 HT40+

when I ran
tcpdump -p -i mon1

I only see radio frame but no data frame.
I setup an open SSID on channel 36(40mhz) and I am passing traffic to it.
2 router and client are all next to each other.

Any pointer is appreciated!!

Does anyone know if it matters whether port forward/traffic rules within uci/LuCI are in the order they should be applied or not?  I ask because openwrt utilizes a custom form of iptables to make it a more simplified homogeneous experience, of which the firewall rules are auto compiled into an iptables layout at boot or upon restarting/reloading the firewall.

For example, if I place two traffic rules, 1st being to deny all traffic from a specific IP subset, then a second rule that allows traffic from that subset as long as it comes from a specific MAC, does it matter which order they're in within the gui on LuCI or numbered via uci?

DavidMcWRT wrote:

the wiki really needs updating!

If someone has time, we need to:

1) change the McWRT entry to say it is out of date, no longer supported and has likely now been surpassed by Trunk.  Remove the .img link.

2) make the CC snapshot the current recommendation

3) remove lifehacksback builds

4) keep Kaloz's link

The "How to flash the firmware to device?" bit needs references to mcwrt (build 1 / 192.168.200.1) removed.

Need to add the luci/httpd instructions to trunk section.

The "disassoc_low_ack=0" fix section it now appears can also be removed.

Would it also make sense to put a redirect on the Github page at https://github.com/Chadster766/McWRT to point people to new sources of info?

And the "Where to get firmware" links at this page http://wiki.openwrt.org/toh/linksys/wrt1900ac still point to McWRT, etc. which may not be the latest...

(Last edited by richbhanover on 2 Apr 2015, 04:35)

Just sysupgraded to r45222. My usb flash drive wont mount in any usb port anymore. I have block-mount installed


usb 1/esata port:

Thu Apr  2 08:07:21 2015 kern.notice kernel: [  189.777929] scsi 2:0:0:0: Direct-Access     USB2.0   DISK             PMAP PQ: 0 ANSI: 0 CCS
Thu Apr  2 08:07:22 2015 kern.notice kernel: [  190.862208] sd 2:0:0:0: [sda] 3892224 512-byte logical blocks: (1.99 GB/1.85 GiB)
Thu Apr  2 08:07:22 2015 kern.notice kernel: [  190.865442] sd 2:0:0:0: [sda] Write Protect is off
Thu Apr  2 08:07:22 2015 kern.debug kernel: [  190.865471] sd 2:0:0:0: [sda] Mode Sense: 23 00 00 00
Thu Apr  2 08:07:22 2015 kern.err kernel: [  190.868692] sd 2:0:0:0: [sda] No Caching mode page found
Thu Apr  2 08:07:22 2015 kern.err kernel: [  190.874112] sd 2:0:0:0: [sda] Assuming drive cache: write through
Thu Apr  2 08:07:22 2015 kern.info kernel: [  190.928260]  sda: sda1
Thu Apr  2 08:07:22 2015 kern.notice kernel: [  190.938060] sd 2:0:0:0: [sda] Attached SCSI removable disk
Thu Apr  2 08:07:22 2015 daemon.err block: mounting /dev/sda1 (ext4) as /mnt/sda1 failed (-1) - Unknown error -1


usb 3:

Thu Apr  2 08:09:19 2015 kern.info kernel: [  307.683870] usb 2-2: new high-speed USB device number 2 using xhci_hcd
Thu Apr  2 08:09:19 2015 kern.info kernel: [  307.837614] usb-storage 2-2:1.0: USB Mass Storage device detected
Thu Apr  2 08:09:19 2015 kern.info kernel: [  307.838637] scsi host3: usb-storage 2-2:1.0
Thu Apr  2 08:09:20 2015 kern.notice kernel: [  308.869232] scsi 3:0:0:0: Direct-Access     USB2.0   DISK             PMAP PQ: 0 ANSI: 0 CCS
Thu Apr  2 08:09:20 2015 kern.notice kernel: [  309.288178] sd 3:0:0:0: [sda] 3892224 512-byte logical blocks: (1.99 GB/1.85 GiB)
Thu Apr  2 08:09:20 2015 kern.notice kernel: [  309.289142] sd 3:0:0:0: [sda] Write Protect is off
Thu Apr  2 08:09:20 2015 kern.debug kernel: [  309.289171] sd 3:0:0:0: [sda] Mode Sense: 23 00 00 00
Thu Apr  2 08:09:20 2015 kern.err kernel: [  309.290879] sd 3:0:0:0: [sda] No Caching mode page found
Thu Apr  2 08:09:20 2015 kern.err kernel: [  309.296297] sd 3:0:0:0: [sda] Assuming drive cache: write through
Thu Apr  2 08:09:20 2015 kern.info kernel: [  309.338938]  sda: sda1
Thu Apr  2 08:09:20 2015 kern.notice kernel: [  309.347813] sd 3:0:0:0: [sda] Attached SCSI removable disk
Thu Apr  2 08:09:20 2015 daemon.err block: mounting /dev/sda1 (ext4) as /mnt/sda1 failed (-1) - Unknown error -1

alirz wrote:

Just sysupgraded to r45222. My usb flash drive wont mount in any usb port anymore. I have block-mount installed


usb 1/esata port:

Thu Apr  2 08:07:21 2015 kern.notice kernel: [  189.777929] scsi 2:0:0:0: Direct-Access     USB2.0   DISK             PMAP PQ: 0 ANSI: 0 CCS
Thu Apr  2 08:07:22 2015 kern.notice kernel: [  190.862208] sd 2:0:0:0: [sda] 3892224 512-byte logical blocks: (1.99 GB/1.85 GiB)
Thu Apr  2 08:07:22 2015 kern.notice kernel: [  190.865442] sd 2:0:0:0: [sda] Write Protect is off
Thu Apr  2 08:07:22 2015 kern.debug kernel: [  190.865471] sd 2:0:0:0: [sda] Mode Sense: 23 00 00 00
Thu Apr  2 08:07:22 2015 kern.err kernel: [  190.868692] sd 2:0:0:0: [sda] No Caching mode page found
Thu Apr  2 08:07:22 2015 kern.err kernel: [  190.874112] sd 2:0:0:0: [sda] Assuming drive cache: write through
Thu Apr  2 08:07:22 2015 kern.info kernel: [  190.928260]  sda: sda1
Thu Apr  2 08:07:22 2015 kern.notice kernel: [  190.938060] sd 2:0:0:0: [sda] Attached SCSI removable disk
Thu Apr  2 08:07:22 2015 daemon.err block: mounting /dev/sda1 (ext4) as /mnt/sda1 failed (-1) - Unknown error -1


usb 3:

Thu Apr  2 08:09:19 2015 kern.info kernel: [  307.683870] usb 2-2: new high-speed USB device number 2 using xhci_hcd
Thu Apr  2 08:09:19 2015 kern.info kernel: [  307.837614] usb-storage 2-2:1.0: USB Mass Storage device detected
Thu Apr  2 08:09:19 2015 kern.info kernel: [  307.838637] scsi host3: usb-storage 2-2:1.0
Thu Apr  2 08:09:20 2015 kern.notice kernel: [  308.869232] scsi 3:0:0:0: Direct-Access     USB2.0   DISK             PMAP PQ: 0 ANSI: 0 CCS
Thu Apr  2 08:09:20 2015 kern.notice kernel: [  309.288178] sd 3:0:0:0: [sda] 3892224 512-byte logical blocks: (1.99 GB/1.85 GiB)
Thu Apr  2 08:09:20 2015 kern.notice kernel: [  309.289142] sd 3:0:0:0: [sda] Write Protect is off
Thu Apr  2 08:09:20 2015 kern.debug kernel: [  309.289171] sd 3:0:0:0: [sda] Mode Sense: 23 00 00 00
Thu Apr  2 08:09:20 2015 kern.err kernel: [  309.290879] sd 3:0:0:0: [sda] No Caching mode page found
Thu Apr  2 08:09:20 2015 kern.err kernel: [  309.296297] sd 3:0:0:0: [sda] Assuming drive cache: write through
Thu Apr  2 08:09:20 2015 kern.info kernel: [  309.338938]  sda: sda1
Thu Apr  2 08:09:20 2015 kern.notice kernel: [  309.347813] sd 3:0:0:0: [sda] Attached SCSI removable disk
Thu Apr  2 08:09:20 2015 daemon.err block: mounting /dev/sda1 (ext4) as /mnt/sda1 failed (-1) - Unknown error -1


Works for me on r45226.
However I cannot get WiFi 2.4 to work... Its starting up, but SSID is not broadcasted anyhow...

@belliash

What file system is your usb drive formatted in?

2.4and 5 ghz both wifi working fine for me

(Last edited by alirz on 2 Apr 2015, 13:31)

alirz wrote:

@belliash

What file system is your usb drive formatted in?

2 partitions: NTFS and EXT4.

belliash wrote:
alirz wrote:

@belliash

What file system is your usb drive formatted in?

2 partitions: NTFS and EXT4.


which usb port?..
do you have any other modules installed besides "block-mount" for usb storage?

It was SATA HDD in USB2 case connected to USB3 port ;-)
I dont have any additional modules, apart from FS.

Updated to (custom) r45230 with the back-ported cpu idle patches-- no issues thus far.

Quick tests with iperf from MBP mid-2009 (ie no AC) baselined at ~43 MBits/sec before the latest wifi patches. Post-wifi patches it came in at ~55 MBits/sec and post cpu idle it's coming in at 75 MBits/sec. Plus, peaks post cpu idle are much higher-- 85/90 MBits/sec. Or in other words, I'm seeing an increase from roughly 10MB to 20MB/sec.