Modify

Opened 7 years ago

Last modified 4 years ago

#9305 new defect

TP-Link WR841ND WiFi LED missing in LuCI

Reported by: philip.petev@… Owned by: developers
Priority: normal Milestone: Barrier Breaker 14.07
Component: base system Version: Trunk
Keywords: Cc:

Description

Hi
I've recently installed the latest trunk build on my TP-Link WR841ND v7 and I've noticed, that one of the LEDs is missing in the configuration. The SYS and QSS LED are configurable from LuCI, but the WiFi LED is missing in the drop-down menu of the LED Configuration page. One other thing I've noticed, it seems this firmware is based on the WR741ND's firmware, because all LED names begins with "tl-wr741nd" and the recognized model on the main status page is "TP-Link TL-WR741ND"

Attachments (0)

Change History (11)

comment:1 Changed 7 years ago by Nilfred <nilfred@…>

Weird. 741's WLAN led name is ath9k-phy0

dmesg|grep " led "

Registered led device: tl-wr741nd:green:system

Registered led device: tl-wr741nd:green:qss

Registered led device: ath9k-phy0

I also agree that led names should be called the same on all similar TP-LINK devices (all dot), but if you managed to flash 741 firmware on 841 device, please don't go away, you just has found gold!

comment:2 follow-ups: Changed 7 years ago by jow

I just want to point out here that LuCI takes the led info from sysfs so the ui is not involved here.

comment:3 in reply to: ↑ 2 Changed 7 years ago by anonymous

Replying to Nilfred <nilfred@…>:

Weird. 741's WLAN led name is ath9k-phy0

dmesg|grep " led "

Registered led device: tl-wr741nd:green:system

Registered led device: tl-wr741nd:green:qss

Registered led device: ath9k-phy0

I also agree that led names should be called the same on all similar TP-LINK devices (all dot), but if you managed to flash 741 firmware on 841 device, please don't go away, you just has found gold!

Well, maybe it's gold, but this isn't solve my problem. Can you be more specific? I've tried to make this device (ath9k-phy0) working, but with no luck so far.

Replying to jow:

I just want to point out here that LuCI takes the led info from sysfs so the ui is not involved here.

Ok, but can you explain to me how to make it works? I'm kinda newbie.

comment:4 in reply to: ↑ 2 Changed 7 years ago by Nilfred <nilfred@…>

Are you able to get the output of 'dmesg|grep " led "' as I did?

If not, try hard to find the line 'Registered led device: ath9k-phy0' in Status -> Kernel Log

Replying to jow:

I just want to point out here that LuCI takes the led info from sysfs so the ui is not involved here.

Where it looks exactly? sysfs is bug prone:

ls /sys/devices/platform/leds-gpio/leds/
tl-wr741nd:green:qss     tl-wr741nd:green:system

ls /sys/devices/platform/leds-gpio/leds/
tl-mr3x20:green:3g      tl-mr3x20:green:qss     tl-mr3x20:green:system

dmesg|grep " led "
Registered led device: tl-mr3x20:green:system
Registered led device: tl-mr3x20:green:qss
Registered led device: tl-mr3x20:green:3g
Registered led device: ath9k-phy0

I do have the entry on Kamikaze r25302 ar71xx (I'm currently playing with orion without official led support and will take time to switch back to ar71xx/ath79)

comment:5 Changed 7 years ago by philip.petev@…

Here is what it looks on my WR841N v7 with the latest trunk:

root@OpenWrt:~# dmesg | grep "led"
ath: Failed to stop TX DMA!
root@OpenWrt:~# ls /sys/devices/platform/leds-gpio/leds
tl-wr741nd:green:qss     tl-wr741nd:green:system

The SYS and QSS LED are working, but, as you can see, the WiFi LED is missing.

comment:6 follow-up: Changed 7 years ago by Nilfred <nilfred@…>

You dmesg is flooded with 'ath: Failed to stop TX DMA!' (bug #8343) so there is no more indication of any led detected. reboot and be 'dmesg|grep " led "' the first thing you do after reboot.

grep machine /proc/cpuinfo
machine			: TP-LINK TL-MR3420

find /sys -name ath9k-phy0
/sys/devices/pci0000:00/0000:00:00.0/leds/ath9k-phy0
/sys/class/leds/ath9k-phy0

ls /sys/class/leds
ath9k-phy0              tl-mr3x20:green:qss
tl-mr3x20:green:3g      tl-mr3x20:green:system

comment:7 in reply to: ↑ 6 Changed 7 years ago by philip.petev@…

Replying to Nilfred <nilfred@…>:

You dmesg is flooded with 'ath: Failed to stop TX DMA!' (bug #8343) so there is no more indication of any led detected. reboot and be 'dmesg|grep " led "' the first thing you do after reboot.

grep machine /proc/cpuinfo
machine			: TP-LINK TL-MR3420

find /sys -name ath9k-phy0
/sys/devices/pci0000:00/0000:00:00.0/leds/ath9k-phy0
/sys/class/leds/ath9k-phy0

ls /sys/class/leds
ath9k-phy0              tl-mr3x20:green:qss
tl-mr3x20:green:3g      tl-mr3x20:green:system

I did it. And here is the current picture:

root@OpenWrt:~# dmesg | grep " led "
Registered led device: tl-wr741nd:green:system
Registered led device: tl-wr741nd:green:qss
Registered led device: ath9k-phy0
root@OpenWrt:~# grep machine /proc/cpuinfo
machine                 : TP-LINK TL-WR741ND
root@OpenWrt:~# find /sys -name ath9k-phy0
/sys/devices/pci0000:00/0000:00:00.0/leds/ath9k-phy0
/sys/class/leds/ath9k-phy0
root@OpenWrt:~# ls /sys/class/leds
ath9k-phy0               tl-wr741nd:green:qss     tl-wr741nd:green:system

Now what?

comment:8 follow-up: Changed 7 years ago by Nilfred <nilfred@…>

Enough, just lets devs work. In the meanwhile play with the remaining LEDs, sys heartbeat and... and... soon you will get bored about LEDs ;)

uci show system

will reflect changes made to LEDs, learn uci on the wiki, then configure other led and rename:

uci set system.@led[X].sysfs=ath9k-phy0
uci commit system

Just for the record: Are you verified ath9k-phy0 is missing from drop-down menu after upgrade to latest trunk? Your device looks like a UFO and has 2 (two) removable antennas?

The remaining bug looks like a leftover not cleared from previous make.

comment:9 in reply to: ↑ 8 Changed 7 years ago by philip.petev@…

Replying to Nilfred <nilfred@…>:

Enough, just lets devs work. In the meanwhile play with the remaining LEDs, sys heartbeat and... and... soon you will get bored about LEDs ;)

uci show system

will reflect changes made to LEDs, learn uci on the wiki, then configure other led and rename:

uci set system.@led[X].sysfs=ath9k-phy0
uci commit system

Just for the record: Are you verified ath9k-phy0 is missing from drop-down menu after upgrade to latest trunk? Your device looks like a UFO and has 2 (two) removable antennas?

The remaining bug looks like a leftover not cleared from previous make.

No, it's not missing, it's there, it always was (at least on the latest two or three trunks I've tested), but whatever trigger I choose for this device (no matter via the web panel or the console), this LED just don't want to work. The other LEDs (SYS, QSS) works ok with any trigger. Yes, my router is TL-WR841N v7, with UFO-like case and non-detachable antennas. The other model, TL-WR841ND v7 is the model with detachable antennas, but if you ignore this, there is no other difference, they are based on one and the same board. You know, I've noticed one more thing - I have two installed wifi drivers - kmod-ath and kmod-ath9k. Is that normal? As far as I know, ath is legacy driver.

comment:10 Changed 7 years ago by Nilfred <nilfred@…>

Invalid: Contradict yourself

Invalid: This is not a support channel

Duplicate: WLAN led again...

WontFix: #8630 defines WLAN led for 741 differently, but your 841 has been detected as 741

Default profile contains all drivers.

comment:11 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

Add Comment

Modify Ticket

Action
as new .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.