-
Notifications
You must be signed in to change notification settings - Fork 346
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
low tx power m7610e #216
Comments
root@OpenWrt:~# cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower |
@leksmax : what device are you running? Could you please provide device eeprom partition? |
@leksmax are you referring to 2GHz or 5GHz band? |
@LorenzoBianconi i am referring stock 5g and mt76 driver 5g |
maybe sombady know how use fem sky11 in this driver ? |
with this driver wifi on mt7610 work well |
@leksmax ok, I will take a look, thx |
maybe i need turn on gpio to FEM working ? |
@LorenzoBianconi What is the probability that in the near future Fem support will appear for this chip? |
Could you please try to make a diff between MT7610E-V10-FEM.bin and device eeprom partition? (just wifi part) |
@LorenzoBianconi |
Similar issue with TP-LINK Archer T2UH (mt7610u). TX power limited to 16.0 dBm. |
could you please try this repo? https://github.com/LorenzoBianconi/wireless-drivers-next/tree/mt76x0_init_target_power |
Doesn't work (kernel 4.20.3 / 5.0-rc3 - INTEL core system, AMD Ryzen not tested because of iommu issue as described here https://bugzilla.kernel.org/show_bug.cgi?id=202241): Eprom not read correctly: Also, driver crashed under heavy load. Wiphy phy2 |
Doesn't work (kernel 4.20.3 / 5.0-rc3 - INTEL core system, AMD Ryzen not
tested because of iommu issue as described here
https://bugzilla.kernel.org/show_bug.cgi?id=202241):
phy#1
Interface wlp0s20f0u3
ifindex 4
wdev 0x100000001
addr da:20:99:ff:c0:34
type managed
txpower 14.00 dBm
shown: 14.00 dBm, but real tx power is much less.
Eprom not read correctly:
* 2484 MHz [14] (disabled)
Also, driver crashed under heavy load.
Described from here:
https://bugzilla.kernel.org/show_bug.cgi?id=202243#c89
up to here:
https://bugzilla.kernel.org/show_bug.cgi?id=202243#c102
Wiphy phy2
max # scan SSIDs: 4
max scan IEs length: 2243 bytes
max # sched scan SSIDs: 0
max # match sets: 0
max # scan plans: 1
max scan plan interval: -1
max scan plan iterations: 0
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Device supports RSN-IBSS.
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP-128 (00-0f-ac:4)
* CCMP-256 (00-0f-ac:10)
* GCMP-128 (00-0f-ac:8)
* GCMP-256 (00-0f-ac:9)
* CMAC (00-0f-ac:6)
* CMAC-256 (00-0f-ac:13)
* GMAC-128 (00-0f-ac:11)
* GMAC-256 (00-0f-ac:12)
Available Antennas: TX 0x1 RX 0x1
Supported interface modes:
* managed
* monitor
Band 1:
Capabilities: 0x17e
HT20/HT40
SM Power Save disabled
RX Greenfield
RX HT20 SGI
RX HT40 SGI
RX STBC 1-stream
Max AMSDU length: 3839 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 4 usec (0x05)
HT TX/RX MCS rate indexes supported: 0-7
Bitrates (non-HT):
* 1.0 Mbps (short preamble supported)
* 2.0 Mbps (short preamble supported)
* 5.5 Mbps (short preamble supported)
* 11.0 Mbps (short preamble supported)
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 2412 MHz [1] (14.0 dBm)
* 2417 MHz [2] (14.0 dBm)
* 2422 MHz [3] (14.0 dBm)
* 2427 MHz [4] (14.0 dBm)
* 2432 MHz [5] (14.0 dBm)
* 2437 MHz [6] (14.0 dBm)
* 2442 MHz [7] (14.0 dBm)
* 2447 MHz [8] (14.0 dBm)
* 2452 MHz [9] (14.0 dBm)
* 2457 MHz [10] (14.0 dBm)
* 2462 MHz [11] (14.0 dBm)
* 2467 MHz [12] (14.0 dBm)
* 2472 MHz [13] (14.0 dBm)
* 2484 MHz [14] (disabled)
Band 2:
Capabilities: 0x17e
HT20/HT40
SM Power Save disabled
RX Greenfield
RX HT20 SGI
RX HT40 SGI
RX STBC 1-stream
Max AMSDU length: 3839 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 4 usec (0x05)
HT TX/RX MCS rate indexes supported: 0-7
VHT Capabilities (0x01800120):
Max MPDU length: 3895
Supported Channel Width: neither 160 nor 80+80
short GI (80 MHz)
VHT RX MCS set:
1 streams: MCS 0-7
2 streams: not supported
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT RX highest supported: 0 Mbps
VHT TX MCS set:
1 streams: MCS 0-7
2 streams: not supported
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT TX highest supported: 0 Mbps
Bitrates (non-HT):
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 5180 MHz [36] (17.0 dBm)
* 5200 MHz [40] (17.0 dBm)
* 5220 MHz [44] (17.0 dBm)
* 5240 MHz [48] (17.0 dBm)
* 5260 MHz [52] (17.0 dBm) (radar detection)
* 5280 MHz [56] (17.0 dBm) (radar detection)
* 5300 MHz [60] (17.0 dBm) (radar detection)
* 5320 MHz [64] (17.0 dBm) (radar detection)
* 5500 MHz [100] (17.0 dBm) (radar detection)
* 5520 MHz [104] (17.0 dBm) (radar detection)
* 5540 MHz [108] (17.0 dBm) (radar detection)
* 5560 MHz [112] (17.0 dBm) (radar detection)
* 5580 MHz [116] (17.0 dBm) (radar detection)
* 5600 MHz [120] (17.0 dBm) (radar detection)
* 5620 MHz [124] (17.0 dBm) (radar detection)
* 5640 MHz [128] (17.0 dBm) (radar detection)
* 5660 MHz [132] (17.0 dBm) (radar detection)
* 5680 MHz [136] (17.0 dBm) (radar detection)
* 5700 MHz [140] (17.0 dBm) (radar detection)
* 5745 MHz [149] (17.0 dBm)
* 5765 MHz [153] (17.0 dBm)
* 5785 MHz [157] (17.0 dBm)
* 5805 MHz [161] (17.0 dBm)
* 5825 MHz [165] (17.0 dBm)
Supported commands:
* new_interface
* set_interface
* new_key
* start_ap
* new_station
* new_mpath
* set_mesh_config
* set_bss
* authenticate
* associate
* deauthenticate
* disassociate
* join_ibss
* join_mesh
* set_tx_bitrate_mask
* frame
* frame_wait_cancel
* set_wiphy_netns
* set_channel
* set_wds_peer
* probe_client
* set_noack_map
* register_beacons
* start_p2p_device
* set_mcast_rate
* connect
* disconnect
* set_qos_map
* set_multicast_to_unicast
Supported TX frame types:
* IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0
0xd0 0xe0 0xf0
* managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0
0xc0 0xd0 0xe0 0xf0
* AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0
0xd0 0xe0 0xf0
* AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0
0xc0 0xd0 0xe0 0xf0
* mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0
0xc0 0xd0 0xe0 0xf0
* P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0
0xc0 0xd0 0xe0 0xf0
* P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0
0xd0 0xe0 0xf0
* P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0
0xc0 0xd0 0xe0 0xf0
Supported RX frame types:
* IBSS: 0x40 0xb0 0xc0 0xd0
* managed: 0x40 0xd0
* AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* mesh point: 0xb0 0xc0 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* P2P-device: 0x40 0xd0
software interface modes (can always be added):
* monitor
interface combinations are not supported
HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing
Device supports TX status socket option.
Device supports HT-IBSS.
Device supports SAE with AUTHENTICATE command
Device supports low priority scan.
Device supports scan flush.
Device supports AP scan.
Device supports per-vif TX power setting
Driver supports full state transitions for AP/GO clients
Driver supports a userspace MPM
Device supports active monitor (which will ACK incoming frames)
Device supports configuring vdev MAC-addr on create.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#216 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABwNCcfHw6vlzJGLIaNeQ0WiEh_lTfDbks5vHIpggaJpZM4ZAfNn>
.
Are you using usb device or PCIe one?
Could you please provide the output of:
- cat /sys/kernel/debug/ieee80211/phy0/mt76/txpower
- cat /sys/kernel/debug/ieee80211/phy0/mt76/rate_txpower
Regards,
Lorenzo
…--
UNIX is Sexy: who | grep -i blonde | talk; cd ~; wine; talk; touch; unzip;
touch; strip; gasp; finger; gasp; mount; fsck; more; yes; gasp; umount;
make clean; sleep
|
USB device: |
and the other values: /sys/kernel/debug/ieee80211/phy1/mt76/rate_txpower looking not good, so far. running the first tests using iw and hcxdumptool |
I have device with mt7610e (tplink c2), but have no idea how to use this for openwrt? makefiile of mt76 is just a link to git (openwrt/mt76), so should I fork that and apply last few commits form there to it myself? |
Could you please provide me your eeprom data (/sys/kernel/debug/ieee80211/phy0/mt76/eeprom)? |
Of course: and linux- firmware is from: |
Hi Lorenzo. $ iw phy1 info $ iw dev the real tx output is still much lower than 20.0 dBm BTW: |
Also channel 14 isn't disabled, as from the driver reported:
phy#1 $ hcxdumptool -i wlp0s20f0u1 -C tx output power is the same as on ch 1...13 |
@LorenzoBianconi here we go: /sys/kernel/debug/ieee80211/phy1/mt76/txpower /sys/kernel/debug/ieee80211/phy1/mt76/rate_txpower Interface wlp0s20f0u3 /sys/kernel/debug/ieee80211/phy1/mt76/txpower /sys/kernel/debug/ieee80211/phy1/mt76/rate_txpower Please do not wonder about "type monitor". I'm using hcxdumptool to set channel. |
To make sure, we retrieve correct eeprom values from this driver |
Today I got the new devices. This are the values of the ASUS USB AC51: Interface wlp0s20f0u3 /sys/kernel/debug/ieee80211/phy1/mt76/rate_txpower /sys/kernel/debug/ieee80211/phy1/mt76/txpower Interface wlp0s20f0u3 /sys/kernel/debug/ieee80211/phy1/mt76/rate_txpower /sys/kernel/debug/ieee80211/phy1/mt76/txpower Compared to the values of the T2UH, we can assume the that driver issue is only partly VENDOR specific. |
it looks like ZerBea's bug is fixed but what about original bug for mt7610e? |
I'm going to look at it ... |
I have the same problem with 5GHz in the D-link DWR-118 A1 which have MediaTek MT7610E chip. On OpenWrt the 5GHz the signal is very weak. On original firmware, a signal is very good. From a distance, 8 meters have 20ms ping and 80Mbps download. |
Hi, the same issue is on every device with MT76xxx chipset. 5GHz support only works with very very low power. I tried this on Archer C20i, Archer C2, Lenovo Y1 alias Newifi Mini. They are all very very weak on 5 GHz independet on the values in the software. Actually I was able to selebt (398mW) which should be 26dbm in Luci, but no diffrence to lower values. - It is really annoying, because there is no proper device beside some very selected Atheros chipsets which work on Openwrt and most newer devices always have MT- or Realteak-Chipsets. - So it should pretty soon come a solution. - There are already some patches which should work, but it's a mess to compile it with them. Look here: https://www.kickstarter.com/projects/1327597961/better-support-for-mt7620a-n-in-openwrt-lede https://code.dopame.me/veonik/openwrt-mirror/commit/cb6a8aa584a2be62aeac9b5b1573303d5615c672 |
Guys, just a question to situate myself: are you testing using the mt76 driver or the mt6710e 'unnoficial' MediaTek feed or similar ? I have been trying over and over with mt76 from Snapshot version with zero improvements and I'm willing to perhaps try a different one and be able to report something different. Let me know which one is the best to try currently. |
Recently (like less then a month ago) @apr456 discovered a extra mt76 init settings, that used in mediatek mt7610e driver and not used in mt76, and a patch for it. |
No need for a fork, just use the latest version with my fix for that issue |
@nbd168 I have updated about 2 days ago to SNAPSHOT, r10307-629e653 and 4.14.128+2019-03-27-a11b6734-1 but the result seems pretty much what it has always been. The signal for 5 Ghz seems very weak in the same room and only work 1 meter or so from the router (using it on Auto or trying to set it manually). |
it's really fresh. like 8 hours ago fresh. |
The fix was pushed today, shortly before the issue was closed. You can
check the commits on the repo.
A terça, 25/06/2019, 21:52, Fernando Frediani <[email protected]>
escreveu:
… @nbd168 <https://github.com/nbd168> I have updated about 2 days ago to
SNAPSHOT, r10307-629e653 and 4.14.128+2019-03-27-a11b6734-1 but the result
seems pretty much what it has always been. The signal for 5 Ghz seems very
weak in the same room and only work 1 meter or so from the router (using it
on Auto or trying to set it manually).
Was the fix pushed after this version or should this have been fixed
already ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#216?email_source=notifications&email_token=ADDS4MMMIN7O2EDMZR6ISGTP4KAR7A5CNFSM4GIB6NT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYRR5IQ#issuecomment-505618082>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADDS4MKXOG5YMNK424OATJDP4KAR7ANCNFSM4GIB6NTQ>
.
|
Thanks folks. |
root@OpenWrt:~# iw phy
Wiphy phy1
max # scan SSIDs: 4
max scan IEs length: 2257 bytes
max # sched scan SSIDs: 0
max # match sets: 0
max # scan plans: 1
max scan plan interval: -1
max scan plan iterations: 0
Retry short long limit: 2
Coverage class: 0 (up to 0m)
Available Antennas: TX 0 RX 0
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* mesh point
Band 1:
Capabilities: 0x2fe
HT20/HT40
SM Power Save disabled
RX Greenfield
RX HT20 SGI
RX HT40 SGI
TX STBC
RX STBC 2-streams
Max AMSDU length: 3839 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 2 usec (0x04)
HT TX/RX MCS rate indexes supported: 0-15, 32
Frequencies:
* 2412 MHz [1] (20.0 dBm)
* 2417 MHz [2] (20.0 dBm)
* 2422 MHz [3] (20.0 dBm)
* 2427 MHz [4] (20.0 dBm)
* 2432 MHz [5] (20.0 dBm)
* 2437 MHz [6] (20.0 dBm)
* 2442 MHz [7] (20.0 dBm)
* 2447 MHz [8] (20.0 dBm)
* 2452 MHz [9] (20.0 dBm)
* 2457 MHz [10] (20.0 dBm)
* 2462 MHz [11] (20.0 dBm)
* 2467 MHz [12] (20.0 dBm) (no IR)
* 2472 MHz [13] (20.0 dBm) (no IR)
* 2484 MHz [14] (20.0 dBm) (no IR)
valid interface combinations:
* #{ managed, AP, mesh point } <= 8,
total <= 8, #channels <= 1
HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing
Wiphy phy0
max # scan SSIDs: 4
max scan IEs length: 2243 bytes
max # sched scan SSIDs: 0
max # match sets: 0
max # scan plans: 1
max scan plan interval: -1
max scan plan iterations: 0
Retry short limit: 7
Retry long limit: 4
Coverage class: 0 (up to 0m)
Available Antennas: TX 0x1 RX 0x1
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* mesh point
Band 1:
Capabilities: 0x17e
HT20/HT40
SM Power Save disabled
RX Greenfield
RX HT20 SGI
RX HT40 SGI
RX STBC 1-stream
Max AMSDU length: 3839 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 4 usec (0x05)
HT TX/RX MCS rate indexes supported: 0-7
Frequencies:
* 2412 MHz [1] (20.0 dBm)
* 2417 MHz [2] (20.0 dBm)
* 2422 MHz [3] (20.0 dBm)
* 2427 MHz [4] (20.0 dBm)
* 2432 MHz [5] (20.0 dBm)
* 2437 MHz [6] (20.0 dBm)
* 2442 MHz [7] (20.0 dBm)
* 2447 MHz [8] (20.0 dBm)
* 2452 MHz [9] (20.0 dBm)
* 2457 MHz [10] (20.0 dBm)
* 2462 MHz [11] (20.0 dBm)
* 2467 MHz [12] (20.0 dBm) (no IR)
* 2472 MHz [13] (20.0 dBm) (no IR)
* 2484 MHz [14] (20.0 dBm) (no IR)
Band 2:
Capabilities: 0x17e
HT20/HT40
SM Power Save disabled
RX Greenfield
RX HT20 SGI
RX HT40 SGI
RX STBC 1-stream
Max AMSDU length: 3839 bytes
No DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 4 usec (0x05)
HT TX/RX MCS rate indexes supported: 0-7
VHT Capabilities (0x01800120):
Max MPDU length: 3895
Supported Channel Width: neither 160 nor 80+80
short GI (80 MHz)
VHT RX MCS set:
1 streams: MCS 0-7
2 streams: not supported
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT RX highest supported: 0 Mbps
VHT TX MCS set:
1 streams: MCS 0-7
2 streams: not supported
3 streams: not supported
4 streams: not supported
5 streams: not supported
6 streams: not supported
7 streams: not supported
8 streams: not supported
VHT TX highest supported: 0 Mbps
Frequencies:
* 5180 MHz [36] (20.0 dBm)
* 5200 MHz [40] (20.0 dBm)
* 5220 MHz [44] (20.0 dBm)
* 5240 MHz [48] (20.0 dBm)
* 5260 MHz [52] (20.0 dBm) (no IR, radar detection)
* 5280 MHz [56] (20.0 dBm) (no IR, radar detection)
* 5300 MHz [60] (20.0 dBm) (no IR, radar detection)
* 5320 MHz [64] (20.0 dBm) (no IR, radar detection)
* 5500 MHz [100] (20.0 dBm) (no IR, radar detection)
* 5520 MHz [104] (20.0 dBm) (no IR, radar detection)
* 5540 MHz [108] (20.0 dBm) (no IR, radar detection)
* 5560 MHz [112] (20.0 dBm) (no IR, radar detection)
* 5580 MHz [116] (20.0 dBm) (no IR, radar detection)
* 5600 MHz [120] (20.0 dBm) (no IR, radar detection)
* 5620 MHz [124] (20.0 dBm) (no IR, radar detection)
* 5640 MHz [128] (20.0 dBm) (no IR, radar detection)
* 5660 MHz [132] (20.0 dBm) (no IR, radar detection)
* 5680 MHz [136] (20.0 dBm) (no IR, radar detection)
* 5700 MHz [140] (20.0 dBm) (no IR, radar detection)
* 5745 MHz [149] (20.0 dBm) (no IR)
* 5765 MHz [153] (20.0 dBm) (no IR)
* 5785 MHz [157] (20.0 dBm) (no IR)
* 5805 MHz [161] (20.0 dBm) (no IR)
* 5825 MHz [165] (20.0 dBm) (no IR)
valid interface combinations:
* #{ IBSS } <= 1, #{ managed, AP, mesh point } <= 8,
total <= 8, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz }
root@OpenWrt:
# iw# iwinfoiw iwinfo
root@OpenWrt:
wlan0 ESSID: "OpenWrt_5g"
Access Point: 00:0C:43:26:60:60
Mode: Master Channel: 36 (5.180 GHz)
Tx-Power: 11 dBm Link Quality: 21/70
Signal: -89 dBm Noise: unknown
Bit Rate: 58.5 MBit/s
Encryption: WPA2 PSK (CCMP)
Type: nl80211 HW Mode(s): 802.11bgnac
Hardware: 14C3:7650 14C3:7650 [Generic MAC80211]
TX power offset: unknown
Frequency offset: unknown
Supports VAPs: yes PHY name: phy0
wlan1 ESSID: "OpenWrt"
Access Point: 00:0C:43:76:20:20
Mode: Master Channel: 11 (2.462 GHz)
Tx-Power: 20 dBm Link Quality: 48/70
Signal: -62 dBm Noise: unknown
Bit Rate: 57.8 MBit/s
Encryption: WPA2 PSK (CCMP)
Type: nl80211 HW Mode(s): 802.11bgn
Hardware: unknown [Generic MAC80211]
TX power offset: unknown
Frequency offset: unknown
Supports VAPs: yes PHY name: phy1
root@OpenWrt:~# iwinfo
in stock i have 20dBm
The text was updated successfully, but these errors were encountered: