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.

Kaloz wrote:
gufus wrote:
Nihilanth wrote:

New WiFi driver on github

The 88W8897 wifi chip is in the WRT1200AC (I think)

Nope, same chip as in the Mamba.

Ah.

Okay, It was just a assumption. Wonder why there adding support for the 88W8897.

Kaloz wrote:
lifehacksback wrote:

@Kaloz

I'm guessing the patches weren't accepted to 3.18.13 hmm

The maintainer didn't even reply to my mail about it.. Oracle < *

RATS!

I have DHCP set to 72h Leases

IPv6 is all screwed up sad


Connection-specific DNS Suffix: lan
Description: ASIX AX88179 USB 3.0 to Gigabit Ethernet Adapter
Physical Address: 00-24-9B-08-E6-1B
DHCP Enabled: Yes
IPv4 Address: 192.168.1.161
IPv4 Subnet Mask: 255.255.255.0
Lease Obtained: Thursday, May 14, 2015 10:50:32 AM
Lease Expires: Sunday, May 17, 2015 10:50:30 AM
IPv4 Default Gateway: 192.168.1.1
IPv4 DHCP Server: 192.168.1.1
IPv4 DNS Server: 192.168.1.1
IPv4 WINS Server:
NetBIOS over Tcpip Enabled: Yes
IPv6 Address: fda4:e5c6:93a8::3fd
Lease Obtained: Thursday, May 14, 2015 10:50:33 AM
Lease Expires: Sunday, June 20, 2151 8:22:51 PM, fda4:e5c6:93a8:0:712a:a3b:31fc:9979
Temporary IPv6 Address: fda4:e5c6:93a8:0:5824:210:e66a:42bb
Link-local IPv6 Address: fe80::712a:a3b:31fc:9979%17
IPv6 Default Gateway:
IPv6 DNS Server: fda4:e5c6:93a8::1

(Last edited by gufus on 14 May 2015, 23:11)

gufus wrote:
doITright wrote:

hmm...  who messed with the leds?

Power flashes non-stop, and internet is off period.

Wireless and wired leds work same as before...

Firmware Version OpenWrt Chaos Calmer r45674 / LuCI (git-15.128.67453-cc99288) 
Kernel Version 3.18.11
Local Time Wed May 13 19:14:53 2015
Uptime 1d 2h 4m 4s
Load Average 0.00, 0.01, 0.05

Cheers

Check...

luci > system > LED Configuration

I had a look but never paid attention to what was there before.... 

Anyhow...  Just jumped to latest trunk and the power led is solid (not flashing as before)

The wan led is off (not sure how to configure it in terms of trigger etc.) and all I see is:

Name WAN
LED Name mamba:white:wan
Default state 1
Trigger none

Thoughts?

Cheers

Let's START here:

Why is it that what is read on this board is GROSSLY different when you log into this web site AND after you log in as a member.

This web site software SUKS!

I took a swipe at this software a 100 or more pages ago.

Enough of this crap! Can this web site BUY an a credible piece of software that is NOT GARBAGE.

WHY do I see posts when I login that DO NOT SHOW UP when I LOG?????????????????

I never thought THAT I HAD TO LOGIN to get ALL the posts here!

doITright wrote:
gufus wrote:
doITright wrote:

hmm...  who messed with the leds?

Power flashes non-stop, and internet is off period.

Wireless and wired leds work same as before...

Firmware Version OpenWrt Chaos Calmer r45674 / LuCI (git-15.128.67453-cc99288) 
Kernel Version 3.18.11
Local Time Wed May 13 19:14:53 2015
Uptime 1d 2h 4m 4s
Load Average 0.00, 0.01, 0.05

Cheers

Check...

luci > system > LED Configuration

I had a look but never paid attention to what was there before.... 

Anyhow...  Just jumped to latest trunk and the power led is solid (not flashing as before)

The wan led is off (not sure how to configure it in terms of trigger etc.) and all I see is:

Name WAN
LED Name mamba:white:wan
Default state 1
Trigger none

Thoughts?

Cheers

My WAN setup smile
http://www.gypsy-designs.com/99.jpg

RickStep wrote:

Let's START here:

Why is it that what is read on this board is GROSSLY different when you log into this web site AND after you log in as a member.

This web site software SUKS!

I took a swipe at this software a 100 or more pages ago.

Enough of this crap! Can this web site BUY an a credible piece of software that is NOT GARBAGE.

WHY do I see posts when I login that DO NOT SHOW UP when I LOG?????????????????

I never thought THAT I HAD TO LOGIN to get ALL the posts here!

While I respect that the respondent needs time to sleep; this an international site and MUST be responded  to in real time.  WHO responds when the specific person is tired!

RickStep wrote:

While I respect that the respondent needs time to sleep; this an international site and MUST be responded  to in real time.  WHO responds when the specific person is tired!

no need to double post, this isn't an issue for me...nor the 4 other devices and 2 networks I have immediate access to.  I would imagine you are having a caching issue, I would normally recommend trying a different browser.

In any case, the forum software they are using isn't "junk" or "trash" it is PunBB which works fine.
http://punbb.informer.com/

Please try from now on to stay on topic when in a thread IE talk about the WRT1900AC in this thread and if you want to discuss the discussion board software choice of OpenWRT either search for another topic like that or post a new topic.

Have a good one.

gufus wrote:
doITright wrote:
gufus wrote:

Check...

luci > system > LED Configuration

I had a look but never paid attention to what was there before.... 

Anyhow...  Just jumped to latest trunk and the power led is solid (not flashing as before)

The wan led is off (not sure how to configure it in terms of trigger etc.) and all I see is:

Name WAN
LED Name mamba:white:wan
Default state 1
Trigger none

Thoughts?

Cheers

My WAN setup smile
http://www.gypsy-designs.com/99.jpg

yup...  that did the trick smile

Thanks Gufus

Cheers

Just got a CPU hang after 1d 20h.

You can see rcu_sched self-detected stall on CPU about 10 lines into the syslog below:

Thu May 14 17:38:00 2015 daemon.info hostapd: wlan1: STA c8:bc:c8:xx:xx:xx WPA: group key handshake completed (RSN)
Thu May 14 17:39:02 2015 daemon.info hostapd: wlan0: STA 8c:29:37:xx:xx:xx WPA: group key handshake completed (RSN)
Thu May 14 17:39:03 2015 daemon.info hostapd: wlan0: STA ac:fd:ec:xx:xx:xx WPA: group key handshake completed (RSN)
Thu May 14 17:40:00 2015 cron.info crond[1185]: USER root pid 12899 cmd /sbin/fan_ctrl.sh
Thu May 14 17:45:00 2015 cron.info crond[1185]: USER root pid 13038 cmd /sbin/fan_ctrl.sh
Thu May 14 17:48:00 2015 daemon.info hostapd: wlan1: STA c8:bc:c8:xx:xx:xx WPA: group key handshake completed (RSN)
Thu May 14 17:49:02 2015 daemon.info hostapd: wlan0: STA 8c:29:37:xx:xx:xx WPA: group key handshake completed (RSN)
Thu May 14 17:49:02 2015 daemon.info hostapd: wlan0: STA ac:fd:ec:xx:xx:xx WPA: group key handshake completed (RSN)
Thu May 14 17:50:00 2015 cron.info crond[1185]: USER root pid 13044 cmd /sbin/fan_ctrl.sh
Thu May 14 17:51:22 2015 kern.err kernel: [162837.503596] INFO: rcu_sched self-detected stall on CPU { 0}  (t=6000 jiffies g=310369 c=310368 q=72)
Thu May 14 17:51:22 2015 kern.info kernel: [162837.512926] Task dump for CPU 0:
Thu May 14 17:51:22 2015 kern.info kernel: [162837.516265] kworker/u4:2    R running      0   325      2 0x00000002
Thu May 14 17:51:22 2015 kern.info kernel: [162837.522794] Workqueue: phy0 mwl_watchdog_ba_events [mwlwifi]
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.528580] Backtrace:
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.531157] [<c001acb0>] (dump_backtrace) from [<c001b018>] (show_stack+0x18/0x1c)
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.538849]  r6:c042fb40 r5:c042fc00 r4:cfa08000 r3:00000006
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.544704] [<c001b000>] (show_stack) from [<c0045d74>] (sched_show_task+0xcc/0x100)
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.552574] [<c0045ca8>] (sched_show_task) from [<c00480c0>] (dump_cpu_task+0x40/0x44)
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.560613]  r5:c042fc00 r4:00000000
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.564354] [<c0048080>] (dump_cpu_task) from [<c0061694>] (rcu_dump_cpu_stacks+0x70/0xb4)
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.572735]  r4:00000000 r3:00000001
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.576468] [<c0061624>] (rcu_dump_cpu_stacks) from [<c0064500>] (rcu_check_callbacks+0x29c/0x79c)
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.585553]  r9:c042fb40 r8:c04284f8 r7:c042fb40 r6:0f9b6000 r5:c0428dc8 r4:c0424840
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.593504] [<c0064264>] (rcu_check_callbacks) from [<c006673c>] (update_process_times+0x40/0x6c)
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.602502]  r10:c0450d08 r9:c0450d08 r8:c0450c80 r7:cfb59800 r6:cfdd9428 r5:00000000
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.610536]  r4:cfa08000
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.613197] [<c00666fc>] (update_process_times) from [<c0074cd8>] (tick_sched_timer+0x210/0x254)
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.622108]  r5:00009419 r4:0f31a860
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.625845] [<c0074ac8>] (tick_sched_timer) from [<c0067124>] (__run_hrtimer.isra.35+0xa8/0x144)
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.634756]  r10:00000001 r9:cfdd9220 r8:00000000 r7:cfdd9220 r6:cfdd9220 r5:cfdd9258
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.642779]  r4:cfdd9428
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.645450] [<c006707c>] (__run_hrtimer.isra.35) from [<c0067794>] (hrtimer_interrupt+0x118/0x28c)
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.654535]  r7:cfdd9220 r6:cfdd9230 r5:00009419 r4:0f319d98
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.660381] [<c006767c>] (hrtimer_interrupt) from [<c025cfa8>] (armada_370_xp_timer_interrupt+0x4c/0x54)
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.669989]  r10:c0468e60 r9:000003ff r8:cfddcd80 r7:00000010 r6:cf80a380 r5:c0433524
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.678022]  r4:cfddcd80
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.680681] [<c025cf5c>] (armada_370_xp_timer_interrupt) from [<c005d288>] (handle_percpu_devid_irq+0x74/0x8c)
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.690810]  r4:cf803c40 r3:c025cf5c
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.694545] [<c005d214>] (handle_percpu_devid_irq) from [<c00595b8>] (generic_handle_irq+0x34/0x44)
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.703718]  r8:cf805000 r7:00000001 r6:00000000 r5:00000000 r4:00000010 r3:c005d214
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.711663] [<c0059584>] (generic_handle_irq) from [<c00598d0>] (__handle_domain_irq+0xa0/0xb4)
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.720487]  r4:c04237b0 r3:0000005f
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.724223] [<c0059830>] (__handle_domain_irq) from [<c00086bc>] (armada_370_xp_handle_irq+0x64/0xe0)
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.733561]  r8:cfb59800 r7:00000001 r6:c0468e78 r5:20000153 r4:c0011ddc r3:cfb59800
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.741518] [<c0008658>] (armada_370_xp_handle_irq) from [<c00097c0>] (__irq_svc+0x40/0x54)
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.749996] Exception stack(0xcfb59800 to 0xcfb59848)
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.755180] 9800: ceb52838 00000000 00001666 00001665 ce0a8280 00000060 ce02e620 00000000
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.763484] 9820: 00000000 00f7e88f 00000001 cfb59854 cfb59858 cfb59848 bf36d658 c0011ddc
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.771787] 9840: 20000153 ffffffff
Thu May 14 17:51:22 2015 kern.warn kernel: [162837.775391]  r10:00000001 r9:00f7e88f r8:00000000 r7:cfb59834 r6:ffffffff r5:20000153

I am running 4.0.2, r45669.

I can't seem to get beyond 2 days of uptime. (I had this lockup previously the day I left for vacation)

(Last edited by webdestroya on 15 May 2015, 04:06)

Not too shabby tongue

Firmware Version    OpenWrt Chaos Calmer r45675 / LuCI Master (git-15.128.67453-cc99288)
Kernel Version    4.0.2
Local Time    Thu May 14 20:01:16 2015
Uptime    3d 2h 43m 35s

Also thanks to Openwrt I've been getting acquainted to cryptography! I've been learning a lot and hope to contribute back to openwrt in the near future.

(Last edited by lifehacksback on 15 May 2015, 06:06)

leitec wrote:
Transpiror wrote:

I flashed Kaloz's latest build for the WRT1900AC V1 tonight and for some reason I'm having issues setting up VLAN tagging for the WAN port, so essentially the router can communicate with the ONT. I was previously using McWRT v1.08 and simply set WAN to eth1.10 and that seemed to work fine however on this build I seem to be having no success. I presume the switch sub menu under network might have something to do with this? I tried fiddling with settings there but that seems to only affect eth0.xxx etc. rather than eth1.xxx

Any suggestions or general help would be greatly appreciated smile

In addition to creating eth1.10, you'll have to create a new switch VLAN with ID 10, and set ports 4 and 6 to output tagged frames on it. Port 4 is the physical WAN port and port 6 is the CPU port for eth1.

It should end up something like this in /etc/config/network:

config switch_vlan
   option device 'switch0'
   option vlan '10'
   option ports '4t 6t'

Ok, total noob question but how does one implement that code tongue? I've had no success accessing that folder via putty

gufus wrote:
Kaloz wrote:
gufus wrote:

The 88W8897 wifi chip is in the WRT1200AC (I think)

Nope, same chip as in the Mamba.

Ah.

Okay, It was just a assumption. Wonder why there adding support for the 88W8897.


It is very odd and an interesting choice for adding support.

WLAN 802.11ac(Draft), Bluetooth 4.0 HS+LE, and NFC
http://www.marvell.com/wireless/avastar/88W8897/

Looks like the only devices on record that are using the chip is AzureWave's AW-CB178NF and one of the WiFi chips for the Xbox One.

Kaloz wrote:
bmork wrote:

FWIW I tried to figure out which patches you're talking about by scanning the stable@vger list, but couldn't find any such request there.  Are you sure it actually went out?

http://thread.gmane.org/gmane.linux.ker … ble/127243

Thanks.  There's my problem:  I assumed you were the one sending it smile

Transpiror wrote:
leitec wrote:
Transpiror wrote:

I flashed Kaloz's latest build for the WRT1900AC V1 tonight and for some reason I'm having issues setting up VLAN tagging for the WAN port, so essentially the router can communicate with the ONT. I was previously using McWRT v1.08 and simply set WAN to eth1.10 and that seemed to work fine however on this build I seem to be having no success. I presume the switch sub menu under network might have something to do with this? I tried fiddling with settings there but that seems to only affect eth0.xxx etc. rather than eth1.xxx

Any suggestions or general help would be greatly appreciated smile

In addition to creating eth1.10, you'll have to create a new switch VLAN with ID 10, and set ports 4 and 6 to output tagged frames on it. Port 4 is the physical WAN port and port 6 is the CPU port for eth1.

It should end up something like this in /etc/config/network:

config switch_vlan
   option device 'switch0'
   option vlan '10'
   option ports '4t 6t'

Ok, total noob question but how does one implement that code tongue? I've had no success accessing that folder via putty

/etc/config/network is not a folder but a file, you can use vi to edit it like this:

$ vi /etc/config/network

See 'editing files' in this page: http://wiki.openwrt.org/doc/howto/user.beginner.cli

Could someone help me configure the switch for setting up a DMZ on one of the ports? What would that switch config look like?

RickStep wrote:

While I respect that the respondent needs time to sleep; this an international site and MUST be responded  to in real time.  WHO responds when the specific person is tired!

Wow, you're acting like you're actually paying for support?  Would you like a refund for your free software?  Let me get that processed for you right here in real time...


Cluttering this thread with off topic posts about the forum software and other issues isn't helping anything.

gufus wrote:
grimley wrote:

Questions re: fan control
Is there any way to control fan operations via the command line?

Yes.

Specifically: 

Fan off:
echo 0> /sys/devices/pwm_fan/hwmon/hwmon0/pwm1

Fan full speed:
echo 255 > /sys/devices/pwm_fan/hwmon/hwmon0/pwm1

Substitute a different value in there for some partial speed.  As far as I know, this speed will get reset the next time that the /sbin/fan_ctrl.sh script is called.

JimWright wrote:
gufus wrote:
grimley wrote:

Questions re: fan control
Is there any way to control fan operations via the command line?

Yes.

Specifically: 

Fan off:
echo 0> /sys/devices/pwm_fan/hwmon/hwmon0/pwm1

Fan full speed:
echo 255 > /sys/devices/pwm_fan/hwmon/hwmon0/pwm1

Substitute a different value in there for some partial speed.  As far as I know, this speed will get reset the next time that the /sbin/fan_ctrl.sh script is called.

Much appreciated.
Thank you.

JimWright wrote:
RickStep wrote:

While I respect that the respondent needs time to sleep; this an international site and MUST be responded  to in real time.  WHO responds when the specific person is tired!

Wow, you're acting like you're actually paying for support?  Would you like a refund for your free software?  Let me get that processed for you right here in real time...


Cluttering this thread with off topic posts about the forum software and other issues isn't helping anything.

;-\ Seconded.

grimley wrote:
JimWright wrote:
gufus wrote:

Yes.

Specifically: 

Fan off:
echo 0> /sys/devices/pwm_fan/hwmon/hwmon0/pwm1

Fan full speed:
echo 255 > /sys/devices/pwm_fan/hwmon/hwmon0/pwm1

Substitute a different value in there for some partial speed.  As far as I know, this speed will get reset the next time that the /sbin/fan_ctrl.sh script is called.

Much appreciated.
Thank you.

I probably should have added that if you install the lm-sensors package, there will be a 'sensors' command available to show the actual temp from the sensors on this router, which can be handy to check status of the sensors.

You can also edit the fan_crtl.sh script if you like to put different setpoints in there, but be aware that this script will get overwritten when you upgrade the firmware.

Builder mvebu has been restarted smile

Sorry, posts 5026 to 5025 are missing from our archive.